From owner-freebsd-current Sun Feb 8 05:15:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22512 for current-outgoing; Sun, 8 Feb 1998 05:15:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hi-ho.ne.jp (root@mail.hi-ho.ne.jp [202.224.128.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22506 for ; Sun, 8 Feb 1998 05:15:56 -0800 (PST) (envelope-from y-takeda@hi-ho.ne.jp) Received: from toki.osk2.threewebnet.or.jp (hkt193.osk.3web.ne.jp [202.235.243.193]) by hi-ho.ne.jp (8.8.8/3.6Wb7:Hi-HO) with SMTP id WAA21330 for ; Sun, 8 Feb 1998 22:15:52 +0900 (JST) Message-ID: <34DDB01C.4123@hi-ho.ne.jp> Date: Sun, 08 Feb 1998 22:16:12 +0900 From: takeda yoshiharu Reply-To: y-takeda@hi-ho.ne.jp X-Mailer: Mozilla 3.01Gold [ja] (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: (=?iso-2022-jp?B?GyRCTDVCahsoSg==?=) Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 05:48:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24971 for current-outgoing; Sun, 8 Feb 1998 05:48:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24919; Sun, 8 Feb 1998 05:47:47 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id QAA14402; Sun, 8 Feb 1998 16:30:29 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id QAA15578; Sun, 8 Feb 1998 16:36:12 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802081336.QAA15578@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: dyson@FreeBSD.ORG cc: mike@smith.net.au (Mike Smith), abial@nask.pl, tlambert@primenet.com, freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Custom init(8) (and some ideas) In-reply-to: Your message of "Fri, 06 Feb 1998 22:50:01 EST." <199802070350.WAA00681@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Feb 1998 16:36:12 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John S. Dyson" wrote: > I think that I might have misinformed here. Gzipped binaries need swap > backing store for each page in the image even for .text section, when > physical memory space needs to be freed for another page. Non-gzipped > binaries can depend on paging off of the a.out itself. Also, non-gzipped > binaries don't have to page out the .text for the initial freeing of the > .text space. Gzipped binaries need to page out the .text pages when they > are individually freed due to pageout daemon activity. Also, gzipped > binaries are not demand-loaded, but are loaded at startup. Also, (unpacked) .text section of gzipped binaries is not shared among several copies of same program, like in case of normal program. If I understand correctly, this is a big problem for Andrzej, since all his program is crunched together. If text and data were gzipped separately, the life, probably, could be easier. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 05:59:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25970 for current-outgoing; Sun, 8 Feb 1998 05:59:55 -0800 (PST) (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 FAA25961; Sun, 8 Feb 1998 05:59:49 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id IAA01104; Sun, 8 Feb 1998 08:52:33 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802081352.IAA01104@dyson.iquest.net> Subject: Re: Custom init(8) (and some ideas) In-Reply-To: <199802081336.QAA15578@tejblum.dnttm.rssi.ru> from Dmitrij Tejblum at "Feb 8, 98 04:36:12 pm" To: dima@tejblum.dnttm.rssi.ru (Dmitrij Tejblum) Date: Sun, 8 Feb 1998 08:52:33 -0500 (EST) Cc: dyson@FreeBSD.ORG, mike@smith.net.au, abial@nask.pl, tlambert@primenet.com, freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitrij Tejblum said: > "John S. Dyson" wrote: > > I think that I might have misinformed here. Gzipped binaries need swap > > backing store for each page in the image even for .text section, when > > physical memory space needs to be freed for another page. Non-gzipped > > binaries can depend on paging off of the a.out itself. Also, non-gzipped > > binaries don't have to page out the .text for the initial freeing of the > > .text space. Gzipped binaries need to page out the .text pages when they > > are individually freed due to pageout daemon activity. Also, gzipped > > binaries are not demand-loaded, but are loaded at startup. > > Also, (unpacked) .text section of gzipped binaries is not shared among several > copies of same program, like in case of normal program. If I understand > correctly, this is a big problem for Andrzej, since all his program is crunched > together. > > If text and data were gzipped separately, the life, probably, could be easier. > Yep, good observation. We can fix that seperately, by adding a mechanism for sharing such .text segments. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 06:20:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27886 for current-outgoing; Sun, 8 Feb 1998 06:20:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27872; Sun, 8 Feb 1998 06:20:13 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id PAA14109; Sun, 8 Feb 1998 15:54:49 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id QAA15324; Sun, 8 Feb 1998 16:01:18 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802081301.QAA15324@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Trenton Schulz cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Fat32 In-reply-to: Your message of "Fri, 06 Feb 1998 20:55:26 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Feb 1998 16:01:18 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Trenton Schulz wrote: > I was wondering whether FAT32 was implemented in -current. If that is so, > I would gladly be a tester for it or something. Official -current doesn't support FAT32. But there is a patch, ftp://ftp.freebsd.org/pub/FreeBSD/incoming/msdosfs-netbsd.diff.gz, that should add this feature. This patch merges NetBSD's msdosfs into FreeBSD-current. I don't have a FAT32 filesystem, so I didn't tested FAT32 support, but VFAT works. FAT32, apparently, works in NetBSD, so I believe it should work also in this patch. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 08:56:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09983 for current-outgoing; Sun, 8 Feb 1998 08:56:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp189.117.mmtl.videotron.net [207.253.117.189]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09973 for ; Sun, 8 Feb 1998 08:56:26 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost.videotron.ca [127.0.0.1]) by azimov.videotron.ca (8.8.8/8.8.8) with ESMTP id LAA20734 for ; Sun, 8 Feb 1998 11:56:51 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34DDE3D1.238B21EB@videotron.ca> Date: Sun, 08 Feb 1998 11:56:50 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <199802080747.AAA29050@usr02.primenet.com> 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: > Do this again with a radix of 16. When you find the damaged pointer > in memory, then examine the region of memory before it and after it > (again in hex). Found out that mclfree is causing the trap12. It's pointing somewhere in hyperspace when it makes my kernel crash. While I was digging around, I noticed something I find weird. Is it possible to have more free clusters than obtained clusers (mbstat.m_clfree > mbstat.m_clusters)? -- Stephane E. Potvin sepotvin@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 14:05:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10383 for current-outgoing; Sun, 8 Feb 1998 14:05:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (dyna2-162.acadiau.ca [131.162.2.162]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10376 for ; Sun, 8 Feb 1998 14:05:08 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id SAA00283 for ; Sun, 8 Feb 1998 18:04:49 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 8 Feb 1998 18:04:44 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: ACER CD910E/JAS IDE CDrom... 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 Running 3.0-current, I just got loaned the above CD player to use, but, after recompiling my kernel with ATAPI and wcd0 support, the system doesn't detect it on boot up... Can anyone suggest a way of getting this to work? Or am I just out of luck with this partciular model? Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 14:25:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13027 for current-outgoing; Sun, 8 Feb 1998 14:25:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13019 for ; Sun, 8 Feb 1998 14:25:35 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (wether.sas.com [192.35.83.7]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id RAA11586 for ; Sun, 8 Feb 1998 17:25:29 -0500 (EST) Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA00770; Sun, 8 Feb 1998 17:25:28 -0500 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA16196; Sun, 8 Feb 1998 17:25:31 -0500 Message-Id: <199802082225.AA16196@iluvatar.unx.sas.com> Subject: boot error. panic: vm_page_free: freeing free page To: freebsd-current@FreeBSD.ORG Date: Sun, 8 Feb 1998 17:25:31 -0500 (EST) 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 too am unable to install the latest snaps due to the following error from the boot floppy: rootfs is 1440 Kbyte compiled in MFS vm_page_free: pindex(12), busy(0), PG_BUSY(0), host(0) panic: vm_page_free: freeing free page. I have checked this against both my own 'make release' mechansim running locally and those on current.freebsd.org. 3.0-980207-SNAP 3.0-980208-SNAP Both die in the same manor. Comments? Stupid user error? Thanks, John -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 14:34:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14578 for current-outgoing; Sun, 8 Feb 1998 14:34:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14571; Sun, 8 Feb 1998 14:34:03 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA18652; Sun, 8 Feb 1998 15:33:58 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd018632; Sun Feb 8 15:33:53 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA20965; Sun, 8 Feb 1998 15:33:45 -0700 (MST) From: Terry Lambert Message-Id: <199802082233.PAA20965@usr05.primenet.com> Subject: Re: Custom init(8) (and some ideas) To: dima@tejblum.dnttm.rssi.ru (Dmitrij Tejblum) Date: Sun, 8 Feb 1998 22:33:45 +0000 (GMT) Cc: dyson@FreeBSD.ORG, mike@smith.net.au, abial@nask.pl, tlambert@primenet.com, freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG In-Reply-To: <199802081336.QAA15578@tejblum.dnttm.rssi.ru> from "Dmitrij Tejblum" at Feb 8, 98 04:36:12 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 > Also, (unpacked) .text section of gzipped binaries is not shared among > several copies of same program, like in case of normal program. If I > understand correctly, this is a big problem for Andrzej, since all his > program is crunched together. > > If text and data were gzipped separately, the life, probably, could be > easier. The pager approach would fix this as ell, though Mike is right about needing to keep a list around. Fundamentally, it's no different than trying to allw mmap's of files on an audio CD (the disk blocks are not some multiple of 512, and therefore not some factor of 4k, the page size). 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 current" in the body of the message From owner-freebsd-current Sun Feb 8 14:48:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17004 for current-outgoing; Sun, 8 Feb 1998 14:48:16 -0800 (PST) (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 OAA16998 for ; Sun, 8 Feb 1998 14:48:15 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA20263; Sun, 8 Feb 1998 15:48:14 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd020247; Sun Feb 8 15:48:13 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA21945; Sun, 8 Feb 1998 15:48:12 -0700 (MST) From: Terry Lambert Message-Id: <199802082248.PAA21945@usr05.primenet.com> Subject: Re: Current dying horribly when using lp0 To: sepotvin@videotron.ca Date: Sun, 8 Feb 1998 22:48:11 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <34DDE3D1.238B21EB@videotron.ca> from "Stephane E. Potvin" at Feb 8, 98 11:56:50 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 > > Do this again with a radix of 16. When you find the damaged pointer > > in memory, then examine the region of memory before it and after it > > (again in hex). > > Found out that mclfree is causing the trap12. It's pointing somewhere in > hyperspace when it makes my kernel crash. While I was digging around, I > noticed something I find weird. Is it possible to have more free clusters > than obtained clusers (mbstat.m_clfree > mbstat.m_clusters)? No. Does "someplace in hyperspace", when you look at the resion in memory, look like an ethernet hardware address? Are you running IP firewall? Do you have a reject rule? Are you getting TCP packets in that match the rule? There is (was?) a bug in the IP firewall code that resulted in an input ehter address structure being written to, effectively, random locations on the kernel stack. This is because the stack was used for a structure, and the calling code returned before the scheduled code completed. 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 current" in the body of the message From owner-freebsd-current Sun Feb 8 15:36:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23837 for current-outgoing; Sun, 8 Feb 1998 15:36:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp187.245.mmtl.videotron.net [207.96.245.187]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23821 for ; Sun, 8 Feb 1998 15:36:01 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost.videotron.ca [127.0.0.1]) by azimov.videotron.ca (8.8.8/8.8.8) with ESMTP id SAA15411 for ; Sun, 8 Feb 1998 18:35:21 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34DE4137.A2621124@videotron.ca> Date: Sun, 08 Feb 1998 18:35:19 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <199802082248.PAA21945@usr05.primenet.com> 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: > > > Do this again with a radix of 16. When you find the damaged pointer > > > in memory, then examine the region of memory before it and after it > > > (again in hex). > > > > Found out that mclfree is causing the trap12. It's pointing somewhere in > > hyperspace when it makes my kernel crash. While I was digging around, I > > noticed something I find weird. Is it possible to have more free clusters > > than obtained clusers (mbstat.m_clfree > mbstat.m_clusters)? > > No. Well, on my dump I've got mbstat.m_clfree == 39 and mbstat.m_clusters = 36 > Does "someplace in hyperspace", when you look at the resion in memory, > look like an ethernet hardware address? "someplace in hyperspace (mclfree)" == 0x30337a15and the ether address of my ed0 card is 00:00:c0:5c:24:d0 > Are you running IP firewall? Yes, it's an open one right new (as per rc.firewall definition) as I hadn't time to configure it yet. > Do you have a reject rule? No > Are you getting TCP packets in that match the rule? No. See above. > There is (was?) a bug in the IP firewall code that resulted in an > input ehter address structure being written to, effectively, random > locations on the kernel stack. This is because the stack was used for > a structure, and the calling code returned before the scheduled code > completed. Well, you never seem to be out of questions :) do you? Hope it will help you a little. right now, I'm still trying to figure out how m_clfree could have gotten higher that m_clusters. I'm gonna try with a kernel without IPFIREWALL enabled to check if that changes something. -- Stephane E. Potvin sepotvin@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 18:01:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10195 for current-outgoing; Sun, 8 Feb 1998 18:01:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10155; Sun, 8 Feb 1998 18:00:45 -0800 (PST) (envelope-from andrew@zeta.org.au) Received: from gurney.reilly.home (d65.syd2.zeta.org.au [203.26.11.65]) by godzilla.zeta.org.au (8.8.7/8.8.7) with ESMTP id MAA18212; Mon, 9 Feb 1998 12:53:33 +1100 Received: (from andrew@localhost) by gurney.reilly.home (8.8.7/8.8.5) id JAA03349; Mon, 9 Feb 1998 09:19:12 +1100 (EST) From: Andrew Reilly Message-Id: <199802082219.JAA03349@gurney.reilly.home> Date: Mon, 9 Feb 1998 09:19:11 +1100 (EST) Subject: Re: Custom init(8) (and some ideas) To: mike@smith.net.au cc: tlambert@primenet.com, dyson@FreeBSD.ORG, abial@nask.pl, freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG In-Reply-To: <199802070454.UAA03722@dingo.cdrom.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 6 Feb, Mike Smith wrote: > You would have to scan the entire image to locate the compression > blocks, which would be a chore. If this is likely to become a popular game (paging from compressed binaries), would it be useful to build a special "binary gzipper" that split and separately compressed independent 4k pages? I believe that the V.42 compression in modems forces blocking at 256-byte boundaries, to minimise the amount that needs to be re-transmitted on errors, and that still manages reasonable error rates. You would need to build a table of pointers to each of the blocks to avoid scanning the whole thing, but there could be some gain. Is there an obvious reason for this not to work? ('Ware traveller: this way lies general-purpose compressed swap and other monsters....) -- Andrew "The steady state of disks is full." -- Ken Thompson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 18:37:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14908 for current-outgoing; Sun, 8 Feb 1998 18:37:45 -0800 (PST) (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 SAA14893; Sun, 8 Feb 1998 18:37:38 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA13758; Sun, 8 Feb 1998 19:37:31 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp02.primenet.com, id smtpd013720; Sun Feb 8 19:37:26 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id TAA22548; Sun, 8 Feb 1998 19:37:20 -0700 (MST) From: Terry Lambert Message-Id: <199802090237.TAA22548@usr06.primenet.com> Subject: Re: Custom init(8) (and some ideas) To: reilly@zeta.org.au (Andrew Reilly) Date: Mon, 9 Feb 1998 02:37:20 +0000 (GMT) Cc: mike@smith.net.au, tlambert@primenet.com, dyson@FreeBSD.ORG, abial@nask.pl, freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG In-Reply-To: <199802082219.JAA03349@gurney.reilly.home> from "Andrew Reilly" at Feb 9, 98 09:19:11 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 > If this is likely to become a popular game (paging from compressed > binaries), would it be useful to build a special "binary gzipper" that > split and separately compressed independent 4k pages? I believe that > the V.42 compression in modems forces blocking at 256-byte boundaries, > to minimise the amount that needs to be re-transmitted on errors, and > that still manages reasonable error rates. You would need to build a > table of pointers to each of the blocks to avoid scanning the whole > thing, but there could be some gain. Is there an obvious reason for > this not to work? If you could be *guaranteed* that the compressed imaged of 8k would become at most 4k, then you could do page doubling. The problem is that you need a VM object for the executable to grab pages off of on page boundries, and you *also* need to grab pages off of disk in page boundries. The closest thing to this currently is the vn? devices configured by vnconfig. They just *happen* to present 4k as 4k; they could just as easily present a smaller amount as 4k (after uncompression). You would *still* have the block-boundry issues, though. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 21:47:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06533 for current-outgoing; Sun, 8 Feb 1998 21:47:38 -0800 (PST) (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 VAA06518 for ; Sun, 8 Feb 1998 21:47:35 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id FAA06351 for ; Mon, 9 Feb 1998 05:47:33 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id GAA02725; Mon, 9 Feb 1998 06:47:33 +0100 (MET) Message-ID: <19980209064733.56080@follo.net> Date: Mon, 9 Feb 1998 06:47:33 +0100 From: Eivind Eklund To: current@FreeBSD.ORG Subject: Heads up: static -ification Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm just about to commit a change that staticize close to everything that can be staticized and doesn't look unreasonable to staticize (almost 400 variables and functions). If anybody get problems with undefined symbols in some way, then please yell at me. GENERIC and LINT compiles and links as usual. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sun Feb 8 22:52:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21103 for current-outgoing; Sun, 8 Feb 1998 22:52:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kaos.atext.com (kaos.atext.com [204.62.245.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21098 for ; Sun, 8 Feb 1998 22:52:42 -0800 (PST) (envelope-from kingson@geocities.com) Received: from kingson-pc.atext.com (kingson-pc [204.62.245.181]) by kaos.atext.com (8.8.5/8.8.5) with SMTP id WAA01367 for ; Sun, 8 Feb 1998 22:51:44 -0800 (PST) Message-Id: <3.0.32.19691231160000.007ad420@mailhost.atext.com> X-Sender: kingson@mailhost.atext.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 08 Feb 1998 22:52:34 -0800 To: freebsd-current@FreeBSD.ORG From: Kingson Gunawan Subject: latest kernel NFS hang Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For some reasons (and this is very reproducible, at least on my system), everytime I tried to mount a remote NFS volume (SunOS), when the connection to the remote server failed (due to network problem), the current kernel freezes the system. The 'hang' machine is still responding to ping, but all login and command prompt activities freeze. Any idea? Here are the detail: Kernel: 980206-SNAP Dual P2/266 on Intel M/B (AMI BIOS) 512MB ram Adaptec 2940UW 4 IBM 4.1GB disks 3COM 905 NIC Kingson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 02:19:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02672 for current-outgoing; Mon, 9 Feb 1998 02:19:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02661 for ; Mon, 9 Feb 1998 02:19:15 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id LAA04897; Mon, 9 Feb 1998 11:19:23 +0100 (MET) (envelope-from sos) Message-Id: <199802091019.LAA04897@sos.freebsd.dk> Subject: Re: ACER CD910E/JAS IDE CDrom... In-Reply-To: from The Hermit Hacker at "Feb 8, 98 06:04:44 pm" To: scrappy@hub.org (The Hermit Hacker) Date: Mon, 9 Feb 1998 11:19:23 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to The Hermit Hacker who wrote: > > Running 3.0-current, I just got loaned the above CD player to use, but, > after recompiling my kernel with ATAPI and wcd0 support, the system > doesn't detect it on boot up... I need ALOT more info before I can help you out: A copy of the probe messages (dmesg output) Kernel config file What IDE device do you have (make, model, master/slave etc) Then I can give you an answer, the above is simply not enough info... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 current" in the body of the message From owner-freebsd-current Mon Feb 9 03:00:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA08352 for current-outgoing; Mon, 9 Feb 1998 03:00:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA08345 for ; Mon, 9 Feb 1998 03:00:34 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 3832 invoked by uid 100); 9 Feb 1998 08:24:11 -0000 Message-ID: <19980209002408.02309@top.worldcontrol.com> Date: Mon, 9 Feb 1998 00:24:08 -0800 To: freebsd-current@FreeBSD.ORG Subject: rxvt: can't load color "darkslateblue" ; aborting Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running -current. After working on my laptop for some time, I find that I can't create any more rxvt windows. Specifically I get: brian@top>rxvt rxvt: can't load color "darkslateblue" rxvt: can't load color "White" rxvt: aborting I found in /var/log/messages that apparently some other process has had similar complaints: Warning: Color name "black" is not defined Warning: Color name "Black" is not defined If I reboot the systems, the problem is gone, and then comes back later. What is happening? -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 03:09:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA10122 for current-outgoing; Mon, 9 Feb 1998 03:09:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA10115; Mon, 9 Feb 1998 03:09:10 -0800 (PST) (envelope-from abial@korin.warman.org.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id MAA19291; Mon, 9 Feb 1998 12:09:53 +0100 (CET) Date: Mon, 9 Feb 1998 12:09:52 +0100 (CET) From: Andrzej Bialecki To: Mike Smith cc: Andrzej Bialecki , Terry Lambert , freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Custom init(8) (and some ideas) In-Reply-To: <199802070332.TAA03469@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 6 Feb 1998, Mike Smith wrote: > > A bit of background, if you're interested: I'm working on the next version > > of PicoBSD, and after some shuffling with the layout and adding new > > features I found that I can no longer fit into 8MB RAM... I.e. it fits, > > but I can't start enough processes to make a dialup connection. > > What does the process listing look like? (use ddb and the 'ps' command > rather than try to squeeze 'ps' into the crunch image). I didn't have ddb in kernel - I thought it would take more space than mount_procfs and ls-like proggy (which I include anyway). But I'll try this. I have also sysctl(8) on the floppy, but I noticed that the most interesting thing for me (i.e. vmmeter) is unimplemented (I already sent PR on this, because this is actually vmtotal, not vmmeter). > Have you shrunk the kernel as much as possible? Yes. :-)) I even fiddled with NBUF and NMBCLUSTERS to save on buffer space. maxusers is 1, so that the various system tables become minimal. > For non-gzip binaries, execution starts by mmapping the entire text > section, and jumping to it. Nothing is "loaded" in any case. > > What you're suggesting really is "execute-in-place", which is quite a > tough thing to implement. I suppose that's what I was thinking about :-). The whole issue is a bit beyond my knowledge, but I'm learning... Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 03:19:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11283 for current-outgoing; Mon, 9 Feb 1998 03:19:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA11274; Mon, 9 Feb 1998 03:19:02 -0800 (PST) (envelope-from abial@korin.warman.org.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id MAA21892; Mon, 9 Feb 1998 12:20:45 +0100 (CET) Date: Mon, 9 Feb 1998 12:20:44 +0100 (CET) From: Andrzej Bialecki To: Dmitrij Tejblum cc: dyson@FreeBSD.ORG, Mike Smith , tlambert@primenet.com, freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Custom init(8) (and some ideas) In-Reply-To: <199802081336.QAA15578@tejblum.dnttm.rssi.ru> 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, 8 Feb 1998, Dmitrij Tejblum wrote: > "John S. Dyson" wrote: > > I think that I might have misinformed here. Gzipped binaries need swap > > backing store for each page in the image even for .text section, when > > physical memory space needs to be freed for another page. Non-gzipped > > binaries can depend on paging off of the a.out itself. Also, non-gzipped > > binaries don't have to page out the .text for the initial freeing of the > > .text space. Gzipped binaries need to page out the .text pages when they > > are individually freed due to pageout daemon activity. Also, gzipped > > binaries are not demand-loaded, but are loaded at startup. > > Also, (unpacked) .text section of gzipped binaries is not shared among > several copies of same program, like in case of normal program. If I > understand correctly, this is a big problem for Andrzej, since all his > program is crunched together. Yes, it hurts :-). That's why I conducted several tests with making a dynamic crunch, to save at least on libraries. But in reality it proved to take more space in case of minimal system, than statically linked binary (if you count the size of objects taken from libc for statical linking, it may be relatively small depending on functions used by program; while when dynamically linked we have to load the whole libc [ca. 450kB] whether we use all the parts or not). It would be very interesting to know (if it's at all possible) how much space is occupied on running system by libraries only. Is it somehow related to "shared" pages? BTW. if someone can use this (I mean, dynamic version of crunched binaries), I can send a patch to crunchgen - it's trivial anyway. It would allow for generating both kinds of crunches, depending on a command line switch. Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 05:46:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02735 for current-outgoing; Mon, 9 Feb 1998 05:46:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from master.inter-linc.net ([12.10.101.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02730 for ; Mon, 9 Feb 1998 05:46:05 -0800 (PST) (envelope-from cdillon@inter-linc.net) Received: from cheetah.inter-linc.net (12.10.101.18) by master.inter-linc.net (Worldmail 1.3.167); 9 Feb 1998 07:44:21 -0600 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980209002408.02309@top.worldcontrol.com> Date: Mon, 09 Feb 1998 07:44:04 -0600 (CST) From: Chris Dillon To: brian@worldcontrol.com Subject: RE: rxvt: can't load color "darkslateblue" ; aborting Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Feb-98 brian@worldcontrol.com wrote: >I'm running -current. After working on my laptop for some time, I >find that I can't create any more rxvt windows. > >Specifically I get: > >brian@top>rxvt >rxvt: can't load color "darkslateblue" >rxvt: can't load color "White" >rxvt: aborting > >I found in /var/log/messages that apparently some other process has >had similar complaints: > >Warning: Color name "black" is not defined >Warning: Color name "Black" is not defined > >If I reboot the systems, the problem is gone, and then comes back later. > >What is happening? Nothing is wrong, really. If you are using an 8-bit color depth (256 colors) not all applications can get the colors they want, and must share amongst what is available. Use a 16-bit or 24-bit color depth and those messages will disappear (not to mention everything will just generally look better). --- Chris Dillon --- cdillon@inter-linc.net --- Powered by FreeBSD, the best operating system on the planet for Intel x86 based computers (and soon Sparcs). ---- (http://www.freebsd.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 07:07:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17669 for current-outgoing; Mon, 9 Feb 1998 07:07:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from inet-user-gw-1.us.oracle.com (inet-user-gw-1.us.oracle.com [192.86.155.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17664 for ; Mon, 9 Feb 1998 07:07:48 -0800 (PST) (envelope-from HARAWAT.IN.oracle.com.ofcmail@in.oracle.com) Received: from dwarpal.in.oracle.com (dwarpal.in.oracle.com [152.69.176.11]) by inet-user-gw-1.us.oracle.com (8.8.5/8.8.5) with SMTP id HAA09303 for ; Mon, 9 Feb 1998 07:05:31 -0800 (PST) Received: by dwarpal.in.oracle.com (8.6.13/37.8) id KAA26931; Mon, 9 Feb 1998 10:23:58 -0500 Message-Id: <199802091523.KAA26931@dwarpal.in.oracle.com> Date: 09 Feb 98 18:04:47 +0330 From: "HARAWAT.IN.ORACLE.COM" To: freebsd-current@FreeBSD.ORG Subject: aio not working in FreeBSD 3.0-971208-SNAP MIME-Version: 1.0 X-Mailer: Oracle InterOffice (version 4.0.5.1.55) Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After registering the aio_read fn, SIGIO signal is generated but the aiocntl_blk->_aiocb_private.status is -1,and aiocntl_blk->_aiocb_private.errno is EINPROGRESS, aslo the values is the buffer shows the contents that were to be read, probably the user space values of status and errno fields of the aiocb_t are not updated. Harish ----------------------------------------------------------------------------- Harish Singh Rawat E-Mail : harawat@in.oracle.com Oracle Software India. Ltd. Voice : +91 (80) 228 3004/5 Indian Development Center ( IDC ) Fax : +91 (80) 225 - 6207/1591 Sona Towers No 71 Miller Road Bangalore-52 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 10:05:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14554 for current-outgoing; Mon, 9 Feb 1998 10:05:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [205.162.1.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14544 for ; Mon, 9 Feb 1998 10:05:45 -0800 (PST) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id KAA18225 for freebsd-current@freebsd.org; Mon, 9 Feb 1998 10:06:52 -0800 (PST) Date: Mon, 9 Feb 1998 10:06:52 -0800 (PST) From: Jim Shankland Message-Id: <199802091806.KAA18225@biggusdiskus.flyingfox.com> To: freebsd-current@FreeBSD.ORG Subject: Re: Custom init(8) (and some ideas) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki writes: > On Sun, 8 Feb 1998, Dmitrij Tejblum wrote: > > Also, (unpacked) .text section of gzipped binaries is not shared among > > several copies of same program, like in case of normal program. If I > > understand correctly, this is a big problem for Andrzej, since all his > > program is crunched together. > > Yes, it hurts :-). That's why I conducted several tests with making a > dynamic crunch, to save at least on libraries. But in reality it proved to > take more space in case of minimal system .... Is all this moot if you don't gzip the binaries (or single, crunched binary), but instead install the binaries in an MFS in the kernel, then kzip the kernel? You get the benefit of compression, but the uncompress is done once, at boot time, so the text section can still be mmap-ed at exec time. Or does it not work this way? On a related note, I did not understand the distinction between mmap-ing the text section and "execute-in-place." If someone could expand briefly, I'd appreciate it. Jim Shankland Flying Fox Computer Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 10:16:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16543 for current-outgoing; Mon, 9 Feb 1998 10:16:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from astral.elitenet.com.br (astral.elitenet.com.br [200.223.49.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16535; Mon, 9 Feb 1998 10:16:51 -0800 (PST) (envelope-from fredy@elitenet.com.br) Received: from Info01 (dial-015.elitenet.com.br [200.223.49.47]) by astral.elitenet.com.br (8.8.8/8.8.8) with SMTP id QAA05703; Mon, 9 Feb 1998 16:21:02 -0200 (EDT) (envelope-from fredy@elitenet.com.br) Message-ID: <34DF9D52.7E45@elitenet.com.br> Date: Mon, 09 Feb 1998 16:20:34 -0800 From: fredy Reply-To: fredy@elitenet.com.br X-Mailer: Mozilla 3.01 (Win95; I; 16bit) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG CC: current@FreeBSD.ORG Subject: How to Config Filter for Bj200 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I´ve already got the configuration to use gs with my printer Bj240 ... for print a file.ps I use the follow command gs -sDEVICE=bj200 -r360x180 -sOutputFile=\|lpr so I want to config a filter to use with lpr to print postscript files. What should I do??? And what options should I use after lpr to print .ps files. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 11:33:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06490 for current-outgoing; Mon, 9 Feb 1998 11:33:20 -0800 (PST) (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 LAA06485; Mon, 9 Feb 1998 11:33:17 -0800 (PST) (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 LAA03931; Mon, 9 Feb 1998 11:31:36 -0800 (PST) Message-Id: <199802091931.LAA03931@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrzej Bialecki cc: Mike Smith , Terry Lambert , freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Custom init(8) (and some ideas) In-reply-to: Your message of "Mon, 09 Feb 1998 12:09:52 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Feb 1998 11:31:36 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What you're suggesting really is "execute-in-place", which is quite a > > tough thing to implement. > > I suppose that's what I was thinking about :-). The whole issue is a bit > beyond my knowledge, but I'm learning... Consider putting all the binaries into a just-right-sized MFS inside the kernel, and then kzipping it. Then you can play with XIP. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 11:56:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12332 for current-outgoing; Mon, 9 Feb 1998 11:56:14 -0800 (PST) (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 LAA12292 for ; Mon, 9 Feb 1998 11:56:05 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA14556; Mon, 9 Feb 1998 12:56:03 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd014529; Mon Feb 9 12:56:02 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id MAA29539; Mon, 9 Feb 1998 12:55:59 -0700 (MST) From: Terry Lambert Message-Id: <199802091955.MAA29539@usr09.primenet.com> Subject: Re: Heads up: static -ification To: eivind@yes.no (Eivind Eklund) Date: Mon, 9 Feb 1998 19:55:59 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <19980209064733.56080@follo.net> from "Eivind Eklund" at Feb 9, 98 06:47:33 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm just about to commit a change that staticize close to everything that > can be staticized and doesn't look unreasonable to staticize (almost 400 > variables and functions). > > If anybody get problems with undefined symbols in some way, then please > yell at me. > > GENERIC and LINT compiles and links as usual. Remember that functions and variables are exported interfaces in many cases. This includes user space uses for "ps", "w", "netstat", and so on, as well as kernel space uses. For a potential kernel environment, you should be careful to not disallow dynamic replacement of kernel pieces using "generic" loadable modules (ie: if something is a function pointer, it should not be static'ed, unless there is an encapsulation function that can be used to modify its value, and then the encapsulation function should not be static). 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 current" in the body of the message From owner-freebsd-current Mon Feb 9 12:01:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13583 for current-outgoing; Mon, 9 Feb 1998 12:01:51 -0800 (PST) (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 MAA13577 for ; Mon, 9 Feb 1998 12:01:50 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id NAA16304; Mon, 9 Feb 1998 13:01:49 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd016280; Mon Feb 9 13:01:44 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id NAA29822; Mon, 9 Feb 1998 13:01:43 -0700 (MST) From: Terry Lambert Message-Id: <199802092001.NAA29822@usr09.primenet.com> Subject: Re: Custom init(8) (and some ideas) To: jas@flyingfox.com (Jim Shankland) Date: Mon, 9 Feb 1998 20:01:42 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199802091806.KAA18225@biggusdiskus.flyingfox.com> from "Jim Shankland" at Feb 9, 98 10:06:52 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 > On a related note, I did not understand the distinction between > mmap-ing the text section and "execute-in-place." If someone could > expand briefly, I'd appreciate it. In the first case, there is a backing object, so the pages can be discarded and recovered later to make room for dirty pages. In the second case, the backing object is compressed, and the pages are generated from decompressing the *entire* backing object, and appear as dirty pages (which can not be discarded, and some of which are never used). 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 current" in the body of the message From owner-freebsd-current Mon Feb 9 12:05:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14521 for current-outgoing; Mon, 9 Feb 1998 12:05:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14461 for ; Mon, 9 Feb 1998 12:05:26 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id VAA19287; Mon, 9 Feb 1998 21:05:09 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id VAA24116; Mon, 9 Feb 1998 21:03:44 +0100 (CET) Message-ID: <19980209210343.OU10756@@> Date: Mon, 9 Feb 1998 21:03:44 +0100 From: pb@fasterix.freenix.org (Pierre Beyssac) To: eivind@yes.no (Eivind Eklund) Cc: current@FreeBSD.ORG Subject: Re: Heads up: static -ification References: <19980209064733.56080@follo.net> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: <19980209064733.56080@follo.net>; from Eivind Eklund on Feb 9, 1998 06:47:33 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund writes: > I'm just about to commit a change that staticize close to everything that > can be staticized and doesn't look unreasonable to staticize (almost 400 > variables and functions). Just out of curiosity, what's the rationale for this? Smaller stack footprint? Faster access to said variables? -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 12:59:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21725 for current-outgoing; Mon, 9 Feb 1998 12:59:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp023.121.mmtl.videotron.net [207.253.121.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21719 for ; Mon, 9 Feb 1998 12:59:46 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost.videotron.ca [127.0.0.1]) by azimov.videotron.ca (8.8.8/8.8.8) with ESMTP id PAA01338 for ; Mon, 9 Feb 1998 15:59:42 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34DF6E3C.4A6C11B5@videotron.ca> Date: Mon, 09 Feb 1998 15:59:41 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <199802082248.PAA21945@usr05.primenet.com> 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: > Are you running IP firewall? I've tried a kernel (3.0-CURRENT #0: Mon Feb 9 14:25:19 EST 1998) with IPFIREWALL disabled and got the same trap 12. I doubt that it is hardware related as I have 2 computers experiencing the same problem. Is there anyone else able to reproduce it? If not then I'll begin to check my hardware for a defective part. -- Stephane E. Potvin sepotvin@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 13:17:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24788 for current-outgoing; Mon, 9 Feb 1998 13:17:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from unix.tfs.net (as1-p6.tfs.net [139.146.210.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24775 for ; Mon, 9 Feb 1998 13:17:16 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id PAA03613 for freebsd-current@freebsd.org; Mon, 9 Feb 1998 15:17:09 -0600 (CST) From: Jim Bryant Message-Id: <199802092117.PAA03613@unix.tfs.net> Subject: merging win95 and nt filesystem changes into msdosfs To: freebsd-current@FreeBSD.ORG Date: Mon, 9 Feb 1998 15:17:08 -0600 (CST) Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Thu Jan 1 19:03:58 CST 1998 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i've been looking at the netbsd diffs for msdosfs. are these going to be merged into the -current distribution? the current diffs don't apply to current, and are getting out of sync. i am tempted to go in and merge this by hand, but really don't want to duplicate someone's effort. shouldn't this merge become part of -current in order to keep in sync?! this is something that i personally find lacking in freebsd is the lack of ability to handle fat32 and long filenames on a msdog partition. i have also noticed a lack of response on any questions to this group dealing with this issue. i have previously asked about such support and received absolutely no answers in the [recent] past. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 13:35:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28327 for current-outgoing; Mon, 9 Feb 1998 13:35:12 -0800 (PST) (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 NAA28300 for ; Mon, 9 Feb 1998 13:34:56 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id VAA21691; Mon, 9 Feb 1998 21:34:53 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id WAA12610; Mon, 9 Feb 1998 22:34:52 +0100 (MET) Message-ID: <19980209223452.41056@follo.net> Date: Mon, 9 Feb 1998 22:34:52 +0100 From: Eivind Eklund To: Pierre Beyssac Cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: Heads up: static -ification References: <19980209064733.56080@follo.net> <19980209210343.OU10756@@> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19980209210343.OU10756@@>; from Pierre Beyssac on Mon, Feb 09, 1998 at 09:03:44PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 09, 1998 at 09:03:44PM +0100, Pierre Beyssac wrote: > Eivind Eklund writes: > > I'm just about to commit a change that staticize close to everything that > > can be staticized and doesn't look unreasonable to staticize (almost 400 > > variables and functions). > > Just out of curiosity, what's the rationale for this? Smaller stack > footprint? Faster access to said variables? There are a multitude of reasons; I'll list some of them: * The namespace was badly managed. E.g, a single driver had taken the global name 'devfs_token'. * Localization of state - to allow the programmer to see that his changes don't affect anything beyond that file. * Localization of state - to let the compiler do better optimizing. * Detection of unused variables. * Data hiding - this make better module boundaries, and make more certain that incestous relationships don't develop. It will make it easier to change the code later. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 14:02:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02826 for current-outgoing; Mon, 9 Feb 1998 14:02:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tesun1.trw.nl (obelix.trw.nl [195.193.64.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02815 for ; Mon, 9 Feb 1998 14:02:43 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from schizo.dk.trw.nl (schizo.dk.trw.nl [140.145.230.10]) by tesun1.trw.nl (8.8.8/8.8.8) with ESMTP id AAA28692; Tue, 10 Feb 1998 00:56:56 +0100 (MET) Received: from critter.freebsd.dk (critter.dk.trw.nl [140.145.230.252]) by schizo.dk.trw.nl (8.8.8/8.8.8) with ESMTP id WAA28985; Mon, 9 Feb 1998 22:58:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.dk.trw.nl [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id WAA05221; Mon, 9 Feb 1998 22:54:35 +0100 (CET) To: Eivind Eklund cc: Pierre Beyssac , current@FreeBSD.ORG Subject: Re: Heads up: static -ification In-reply-to: Your message of "Mon, 09 Feb 1998 22:34:52 +0100." <19980209223452.41056@follo.net> Date: Mon, 09 Feb 1998 22:54:34 +0100 Message-ID: <5219.887061274@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > I'm just about to commit a change that staticize close to everything that >> > can be staticized and doesn't look unreasonable to staticize (almost 400 >> > variables and functions). >> >> Just out of curiosity, what's the rationale for this? Smaller stack >> footprint? Faster access to said variables? > >There are a multitude of reasons; I'll list some of them: I'd just like to say thanks to Eivind for this effort. People should make use of the script in src/tools/tools/kernxref.sh in the future, unless some other file needs a particular symbol, it should be made static. There is no excuse now! Thanks again Eivind! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 14:06:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03988 for current-outgoing; Mon, 9 Feb 1998 14:06:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03942; Mon, 9 Feb 1998 14:06:03 -0800 (PST) (envelope-from gozer@ludd.luth.se) Received: from sister.ludd.luth.se (gozer@sister.ludd.luth.se [130.240.16.77]) by zed.ludd.luth.se (8.8.5/8.8.5) with SMTP id XAA07743; Mon, 9 Feb 1998 23:05:32 +0100 Date: Mon, 9 Feb 1998 23:05:31 +0100 (MET) From: Johan Larsson To: Dmitrij Tejblum cc: Trenton Schulz , freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Fat32 In-Reply-To: <199802081301.QAA15324@tejblum.dnttm.rssi.ru> 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 happened to this? Is there any development going on? Or did it just die? It would be very nice to see it in current. I am running this just now, and it seems to work fine. How much testing would it require before it gets commited. Johan On Sun, 8 Feb 1998, Dmitrij Tejblum wrote: > Trenton Schulz wrote: > > I was wondering whether FAT32 was implemented in -current. If that is so, > > I would gladly be a tester for it or something. > > Official -current doesn't support FAT32. But there is a patch, > ftp://ftp.freebsd.org/pub/FreeBSD/incoming/msdosfs-netbsd.diff.gz, > that should add this feature. This patch merges NetBSD's msdosfs into > FreeBSD-current. I don't have a FAT32 filesystem, so I didn't tested FAT32 > support, but VFAT works. FAT32, apparently, works in NetBSD, so I believe it > should work also in this patch. > > Dima > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe current" in the body of the message > > -- * mailto:gozer@ludd.luth.se * http://www.ludd.luth.se/users/gozer/ * * Powered by FreeBSD. http://www.se.freebsd.org/ +-+-+-+-+-+-+-+-+ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 14:24:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08155 for current-outgoing; Mon, 9 Feb 1998 14:24:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08112 for ; Mon, 9 Feb 1998 14:24:18 -0800 (PST) (envelope-from abial@korin.warman.org.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id XAA29659; Mon, 9 Feb 1998 23:10:53 +0100 (CET) Date: Mon, 9 Feb 1998 23:10:52 +0100 (CET) From: Andrzej Bialecki To: Jim Shankland cc: freebsd-current@FreeBSD.ORG Subject: Re: Custom init(8) (and some ideas) In-Reply-To: <199802091806.KAA18225@biggusdiskus.flyingfox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Feb 1998, Jim Shankland wrote: > Andrzej Bialecki writes: > > > On Sun, 8 Feb 1998, Dmitrij Tejblum wrote: > > > Also, (unpacked) .text section of gzipped binaries is not shared among > > > several copies of same program, like in case of normal program. If I > > > understand correctly, this is a big problem for Andrzej, since all his > > > program is crunched together. > > > > Yes, it hurts :-). That's why I conducted several tests with making a > > dynamic crunch, to save at least on libraries. But in reality it proved to > > take more space in case of minimal system .... > > Is all this moot if you don't gzip the binaries (or single, crunched > binary), but instead install the binaries in an MFS in the kernel, > then kzip the kernel? You get the benefit of compression, but the > uncompress is done once, at boot time, so the text section can still > be mmap-ed at exec time. Or does it not work this way? Ahh, well, the life would be SO easy then... Unfortunately, it takes ca. 1/3 more space that way. And this happens to be too much for 1.44MB floppy and 8MB RAM. And these constraints I'm going to keep, so it seems I must live with crunchies for now... This idea occurred to me some time ago, and the above quote depicts my (sad) experiences with it. Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 14:30:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09543 for current-outgoing; Mon, 9 Feb 1998 14:30:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adsdevelop2.autodebit.com ([204.50.245.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09474 for ; Mon, 9 Feb 1998 14:29:57 -0800 (PST) (envelope-from davidg@autodebit.com) Received: by ADSDEVELOP2 with Internet Mail Service (5.0.1457.3) id <1LTCJKWR>; Mon, 9 Feb 1998 14:31:31 -0800 Message-ID: <71D507C37988D11182ED0000F80462AC6977@ADSDEVELOP2> From: David Green-Seed To: "'Johan Larsson'" , Dmitrij Tejblum Cc: Trenton Schulz , freebsd-current@FreeBSD.ORG Subject: RE: Fat32 Date: Mon, 9 Feb 1998 14:31:30 -0800 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know the current status of this one, but I would gladly do some testing. I'm running 2.2.5-STABLE. If noone else is able, I can arrange to test FAT32, also. Dave. _________________________ David Green-Seed davidg@autodebit.com Automated Debit Systems > -----Original Message----- > From: Johan Larsson [SMTP:gozer@ludd.luth.se] > Sent: Monday, February 09, 1998 2:06 PM > To: Dmitrij Tejblum > Cc: Trenton Schulz; freebsd-questions@FreeBSD.ORG; > freebsd-current@FreeBSD.ORG > Subject: Re: Fat32 > > What happened to this? Is there any development going on? Or did it > just > die? It would be very nice to see it in current. I am running this > just > now, and it seems to work fine. How much testing would it require > before > it gets commited. > > Johan > > On Sun, 8 Feb 1998, Dmitrij Tejblum wrote: > > > Trenton Schulz wrote: > > > I was wondering whether FAT32 was implemented in -current. If > that is so, > > > I would gladly be a tester for it or something. > > > > Official -current doesn't support FAT32. But there is a patch, > > ftp://ftp.freebsd.org/pub/FreeBSD/incoming/msdosfs-netbsd.diff.gz, > > that should add this feature. This patch merges NetBSD's msdosfs > into > > FreeBSD-current. I don't have a FAT32 filesystem, so I didn't tested > FAT32 > > support, but VFAT works. FAT32, apparently, works in NetBSD, so I > believe it > > should work also in this patch. > > > > Dima > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe current" in the body of the message > > > > > > -- > * mailto:gozer@ludd.luth.se * http://www.ludd.luth.se/users/gozer/ * > * Powered by FreeBSD. http://www.se.freebsd.org/ +-+-+-+-+-+-+-+-+ * > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 15:45:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24788 for current-outgoing; Mon, 9 Feb 1998 15:45:20 -0800 (PST) (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 PAA24771 for ; Mon, 9 Feb 1998 15:45:10 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id XAA22986; Mon, 9 Feb 1998 23:43:44 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id AAA12952; Tue, 10 Feb 1998 00:43:43 +0100 (MET) Message-ID: <19980210004343.11745@follo.net> Date: Tue, 10 Feb 1998 00:43:43 +0100 From: Eivind Eklund To: Poul-Henning Kamp Cc: Eivind Eklund , Pierre Beyssac , current@FreeBSD.ORG Subject: Re: Heads up: static -ification References: <19980209223452.41056@follo.net> <5219.887061274@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <5219.887061274@critter.freebsd.dk>; from Poul-Henning Kamp on Mon, Feb 09, 1998 at 10:54:34PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 09, 1998 at 10:54:34PM +0100, Poul-Henning Kamp wrote: > People should make use of the script in src/tools/tools/kernxref.sh > in the future, unless some other file needs a particular symbol, > it should be made static. I'd like, at some point, to go longer than that. All symbols that should be exported should be separately specified, and we should have a hierarchical module system to limit exposure. But that's a bit longer into the future :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 16:12:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28944 for current-outgoing; Mon, 9 Feb 1998 16:12:48 -0800 (PST) (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 QAA28873 for ; Mon, 9 Feb 1998 16:12:43 -0800 (PST) (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 KAA00338; Tue, 10 Feb 1998 10:42:17 +1030 (CST) Message-Id: <199802100012.KAA00338@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: jbryant@unix.tfs.net cc: freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Mon, 09 Feb 1998 15:17:08 MDT." <199802092117.PAA03613@unix.tfs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 1998 10:42:17 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > i have also noticed a lack of response on any questions to this group > dealing with this issue. i have previously asked about such support > and received absolutely no answers in the [recent] past. Well, *I'd* like you to merge the changes :) I think the lack of response is because no-one else is doing it :) Someone started but they had to stop before it was finished :( --------------------------------------------------------------------- |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 current" in the body of the message From owner-freebsd-current Mon Feb 9 16:47:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04908 for current-outgoing; Mon, 9 Feb 1998 16:47:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04900 for ; Mon, 9 Feb 1998 16:47:22 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id DAA15854; Tue, 10 Feb 1998 03:43:19 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id DAA02713; Tue, 10 Feb 1998 03:49:58 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802100049.DAA02713@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: jbryant@unix.tfs.net cc: freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Mon, 09 Feb 1998 15:17:08 CST." <199802092117.PAA03613@unix.tfs.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Date: Tue, 10 Feb 1998 03:49:58 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Bryant wrote: > i've been looking at the netbsd diffs for msdosfs. > > are these going to be merged into the -current distribution? the > current diffs don't apply to current, and are getting out of sync. This is news to me. MSDOSFS in -current almost not changed since I produced this patch (msdosfs-netbsd.diff.gz). The only changes which I remember was: Bruce added #include to msdosfs_vnops.c Eivind added #include "opt_diagnostic.h" to 3 files Eivind backed out the previous change. Eivind staticized something. I haven't received this change yet. Is the diff you talk about called msdosfs-netbsd.diff? > i > am tempted to go in and merge this by hand, but really don't want to > duplicate someone's effort. Well, I "maintain" this changes locally and can regenerate the diffs. > shouldn't this merge become part of -current in order to keep in > sync?! this is something that i personally find lacking in freebsd is > the lack of ability to handle fat32 and long filenames on a msdog > partition. I should also point out that there is another diff, msdosfs-vfat.diff, in incoming. This diff is for 2.2. It is original and independent work of Luoqi Chen. It is not supposed to support FAT32. May be, now Luoqi did some further development of his work. > > i have also noticed a lack of response on any questions to this group > dealing with this issue. i have previously asked about such support > and received absolutely no answers in the [recent] past. I don't remember your _recent_ postings about it. These diffs is less than 2 months old. BTW, I got the idea of looking to NetBSD for long file names support from a discussion on -current. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 16:56:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06231 for current-outgoing; Mon, 9 Feb 1998 16:56:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06190 for ; Mon, 9 Feb 1998 16:56:07 -0800 (PST) (envelope-from pb@fasterix.frmug.org) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id BAA02501; Tue, 10 Feb 1998 01:55:43 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.8.8/8.8.5/pb-19970302) id BAA03469; Tue, 10 Feb 1998 01:55:31 +0100 (CET) Message-ID: <19980210015530.KY13839@@> Date: Tue, 10 Feb 1998 01:55:31 +0100 From: pb@fasterix.freenix.org (Pierre Beyssac) To: eivind@yes.no (Eivind Eklund) Cc: current@FreeBSD.ORG Subject: Re: Heads up: static -ification References: <19980209064733.56080@follo.net> <19980209210343.OU10756@@> <19980209223452.41056@follo.net> X-Mailer: Mutt 0.59.1e Mime-Version: 1.0 In-Reply-To: <19980209223452.41056@follo.net>; from Eivind Eklund on Feb 9, 1998 22:34:52 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund writes: > * Localization of state - to allow the programmer to see that his > changes don't affect anything beyond that file. > > * Data hiding - this make better module boundaries, and make more > certain that incestous relationships don't develop. It will make it > easier to change the code later. Wooops, thanks, I understand now. That's great! I'd gotten it all wrong: I was under the impression that you were converting auto variables to static, and I didn't see what was the point in doing that :-) -- Pierre Beyssac pb@fasterix.frmug.org pb@fasterix.freenix.org {Free,Net,Open}BSD, Linux : il y a moins bien, mais c'est plus cher Free domains: http://www.eu.org/ or mail dns-manager@EU.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 16:58:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06771 for current-outgoing; Mon, 9 Feb 1998 16:58:11 -0800 (PST) (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 QAA06730 for ; Mon, 9 Feb 1998 16:58:09 -0800 (PST) (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 QAA05622; Mon, 9 Feb 1998 16:54:52 -0800 (PST) Message-Id: <199802100054.QAA05622@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Dmitrij Tejblum cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 03:49:58 +0300." <199802100049.DAA02713@tejblum.dnttm.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Feb 1998 16:54:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I should also point out that there is another diff, msdosfs-vfat.diff, in > incoming. This diff is for 2.2. It is original and independent work of > Luoqi Chen. It is not supposed to support FAT32. May be, now Luoqi did some > further development of his work. I think that this is where things hit a logjam last time; there are two sets of incompatible patches to achieve two desirable things. Until the two sets of patches are _merged_, there is unlikely to be anything committed. Can you two perhaps get together and sort this out? -- \\ 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 current" in the body of the message From owner-freebsd-current Mon Feb 9 18:09:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17289 for current-outgoing; Mon, 9 Feb 1998 18:09:15 -0800 (PST) (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 SAA17251 for ; Mon, 9 Feb 1998 18:09:11 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id CAA24324; Tue, 10 Feb 1998 02:09:08 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id DAA13775; Tue, 10 Feb 1998 03:09:07 +0100 (MET) Message-ID: <19980210030906.20113@follo.net> Date: Tue, 10 Feb 1998 03:09:06 +0100 From: Eivind Eklund To: Terry Lambert Cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: Heads up: static -ification References: <19980209064733.56080@follo.net> <199802091955.MAA29539@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199802091955.MAA29539@usr09.primenet.com>; from Terry Lambert on Mon, Feb 09, 1998 at 07:55:59PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Feb 09, 1998 at 07:55:59PM +0000, Terry Lambert wrote: > > I'm just about to commit a change that staticize close to everything that > > can be staticized and doesn't look unreasonable to staticize (almost 400 > > variables and functions). > > > > If anybody get problems with undefined symbols in some way, then please > > yell at me. > > > > GENERIC and LINT compiles and links as usual. > > Remember that functions and variables are exported interfaces in > many cases. This includes user space uses for "ps", "w", "netstat", > and so on, as well as kernel space uses. I know. I hope I didn't break any of them; the suspicion that I might have was the reason for sending the heads-up in the first place. I though fixing this (the extreme spread of kernel symbols) was worth the potential trouble. BTW: Speaking of symbol spread - you once gave a reference to the ld manpage and implied that it was possible to create new object files included a specific subset of the symbols from the original object files. I tried to find out how to do this, as I wanted it both for the kernel and for libalias, but I've spent quite some time without finding out how to do it. Would you mind giving detailed instructions? (Re-creating object files is easy, the problem is controlling which symbols to include on a fine-grained basis). > For a potential kernel environment, you should be careful to not > disallow dynamic replacement of kernel pieces using "generic" > loadable modules (ie: if something is a function pointer, it > should not be static'ed, unless there is an encapsulation function > that can be used to modify its value, and then the encapsulation > function should not be static). I think I may have broken one of these. I'll look through my patches again. (I remember seeing something that looked like the above, and I don't remember what I did with it. I just remember being in doubt.) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 18:33:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20832 for current-outgoing; Mon, 9 Feb 1998 18:33:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20827 for ; Mon, 9 Feb 1998 18:33:40 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id SAA26932; Mon, 9 Feb 1998 18:33:24 -0800 (PST) To: jbryant@unix.tfs.net cc: freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Mon, 09 Feb 1998 15:17:08 CST." <199802092117.PAA03613@unix.tfs.net> Date: Mon, 09 Feb 1998 18:33:24 -0800 Message-ID: <26929.887078004@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > i have also noticed a lack of response on any questions to this group > dealing with this issue. i have previously asked about such support > and received absolutely no answers in the [recent] past. There's no one who currently "owns" MSDOSFS, that's why, and no one to do the work of integrating changes from NetBSD or any other OS. Any volunteers? Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 19:09:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28523 for current-outgoing; Mon, 9 Feb 1998 19:09:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (dyna2-163.acadiau.ca [131.162.2.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28385; Mon, 9 Feb 1998 19:08:59 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with ESMTP id XAA10545; Mon, 9 Feb 1998 23:08:49 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 9 Feb 1998 23:08:49 -0400 (AST) From: The Hermit Hacker To: Søren Schmidt cc: freebsd-current@FreeBSD.ORG Subject: Re: ACER CD910E/JAS IDE CDrom... In-Reply-To: <199802091019.LAA04897@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Feb 1998, Søren Schmidt wrote: > In reply to The Hermit Hacker who wrote: > > > > Running 3.0-current, I just got loaned the above CD player to use, but, > > after recompiling my kernel with ATAPI and wcd0 support, the system > > doesn't detect it on boot up... > > I need ALOT more info before I can help you out: > > A copy of the probe messages (dmesg output) > Kernel config file > What IDE device do you have (make, model, master/slave etc) > > Then I can give you an answer, the above is simply not enough info... Actually, not really the answer, but I did get it to work. I ended up downloading the boot.flp from the latest snapshot, then when that worked, building a GENERIC kernel...and when that worked, copied in anything that appeared pertinent...and now it works. I had: #controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ffa004 vector wdintr #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device wcd0 #IDE CD-ROM And now have: options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM I haven't investigated further, yet, about whether the problem is the missing CMD640 or the flags setting on wdc0...before I go through that, does anyone know if either should affect it? If its something known, no reason to go and test it...:) 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 current" in the body of the message From owner-freebsd-current Mon Feb 9 20:59:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14363 for current-outgoing; Mon, 9 Feb 1998 20:59:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from casa.plan.pixelogix.com (casagate.plan.pixelogix.com [206.129.249.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14358; Mon, 9 Feb 1998 20:59:34 -0800 (PST) (envelope-from phils@casa.plan.pixelogix.com) Received: (from phils@localhost) by casa.plan.pixelogix.com (8.8.8/8.8.5) id UAA01719; Mon, 9 Feb 1998 20:59:00 -0800 (PST) Date: Mon, 9 Feb 1998 20:59:00 -0800 (PST) Message-Id: <199802100459.UAA01719@casa.plan.pixelogix.com> From: Phil Staub To: fredy@elitenet.com.br CC: freebsd-current@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <34DF9D52.7E45@elitenet.com.br> (message from fredy on Mon, 09 Feb 1998 16:20:34 -0800) Subject: Re: How to Config Filter for Bj200 References: <34DF9D52.7E45@elitenet.com.br> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I´ve already got the configuration to use gs with my printer > Bj240 ... for print a file.ps I use the follow command > gs -sDEVICE=bj200 -r360x180 -sOutputFile=\|lpr > so I want to config a filter to use with lpr to print postscript files. > What should I do??? > And what options should I use after lpr to print .ps files. > I highly recommend apsfilter. When properly installed and with all required conversion programs in place, it can generally deal with virtually any file format with no switches required. You can print postscript, gif, tiff, pbm, etc., even compressed (.gz, .zip, etc.) without even uncompressing them. I've been using if for a couple of years, and wouldn't dream of using anything else. -- Phil Staub, KE7HC Senior Software Engineer phils@pixelogix.com Audio Precision, Inc. or phils@audioprecision.com Beaverton, OR 97075, (800) 231-7350 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 23:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28419 for current-outgoing; Mon, 9 Feb 1998 23:17:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28321; Mon, 9 Feb 1998 23:16:47 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id IAA01018; Tue, 10 Feb 1998 08:17:24 +0100 (MET) (envelope-from sos) Message-Id: <199802100717.IAA01018@sos.freebsd.dk> Subject: Re: ACER CD910E/JAS IDE CDrom... In-Reply-To: from The Hermit Hacker at "Feb 9, 98 11:08:49 pm" To: scrappy@hub.org (The Hermit Hacker) Date: Tue, 10 Feb 1998 08:17:24 +0100 (MET) Cc: sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to The Hermit Hacker who wrote: The problem is the '#' in front of all the lines in the section "I had", you have effectively disabled any ata/atapi support :) Or is this not an _exact_ copy of your config... The CMD640 might very well be the help you needed... > Actually, not really the answer, but I did get it to work. I > ended up downloading the boot.flp from the latest snapshot, then when that > worked, building a GENERIC kernel...and when that worked, copied in > anything that appeared pertinent...and now it works. > > I had: > > #controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ffa004 > vector wdintr > #disk wd0 at wdc0 drive 0 > #disk wd1 at wdc0 drive 1 > #options ATAPI #Enable ATAPI support for IDE bus > #options ATAPI_STATIC #Don't do it as an LKM > #device wcd0 #IDE CD-ROM > > And now have: > > options "CMD640" # work around CMD640 chip deficiency > controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr > disk wd0 at wdc0 drive 0 > disk wd1 at wdc0 drive 1 > > #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr > #disk wd2 at wdc1 drive 0 > #disk wd3 at wdc1 drive 1 > > options ATAPI #Enable ATAPI support for IDE bus > options ATAPI_STATIC #Don't do it as an LKM > device wcd0 #IDE CD-ROM > > I haven't investigated further, yet, about whether the problem is > the missing CMD640 or the flags setting on wdc0...before I go through > that, does anyone know if either should affect it? If its something > known, no reason to go and test it...:) > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 current" in the body of the message From owner-freebsd-current Mon Feb 9 23:20:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29087 for current-outgoing; Mon, 9 Feb 1998 23:20:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29012 for ; Mon, 9 Feb 1998 23:19:53 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id KAA19291; Tue, 10 Feb 1998 10:13:09 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id KAA01219; Tue, 10 Feb 1998 10:19:45 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802100719.KAA01219@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Jordan K. Hubbard" cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Mon, 09 Feb 1998 18:33:24 PST." <26929.887078004@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 1998 10:19:44 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > There's no one who currently "owns" MSDOSFS, that's why, and no one to > do the work of integrating changes from NetBSD or any other OS. Any > volunteers? Me. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Mon Feb 9 23:27:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00690 for current-outgoing; Mon, 9 Feb 1998 23:27:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00665 for ; Mon, 9 Feb 1998 23:27:21 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id XAA01765; Mon, 9 Feb 1998 23:25:52 -0800 (PST) To: Dmitrij Tejblum cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 10:19:44 +0300." <199802100719.KAA01219@tejblum.dnttm.rssi.ru> Date: Mon, 09 Feb 1998 23:25:52 -0800 Message-ID: <1760.887095552@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Great! You'll test this in -current and give one of the committers something to commit once you're comfortable with the testing, or what precisely? Jordan > "Jordan K. Hubbard" wrote: > > There's no one who currently "owns" MSDOSFS, that's why, and no one to > > do the work of integrating changes from NetBSD or any other OS. Any > > volunteers? > > Me. > > Dima > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 00:54:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12295 for current-outgoing; Tue, 10 Feb 1998 00:54:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rvc1.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12216; Tue, 10 Feb 1998 00:53:47 -0800 (PST) (envelope-from helbig@Informatik.BA-Stuttgart.DE) Received: (from helbig@localhost) by rvc1.informatik.ba-stuttgart.de (8.8.8/8.8.5) id JAA00421; Tue, 10 Feb 1998 09:53:26 +0100 (MET) From: Wolfgang Helbig Message-Id: <199802100853.JAA00421@rvc1.informatik.ba-stuttgart.de> Subject: Re: ACER CD910E/JAS IDE CDrom... In-Reply-To: <199802100717.IAA01018@sos.freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "Feb 10, 98 08:17:24 am" To: sos@FreeBSD.ORG Date: Tue, 10 Feb 1998 09:53:26 +0100 (MET) Cc: scrappy@hub.org, sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In reply to The Hermit Hacker who wrote: > > The problem is the '#' in front of all the lines in the section > "I had", you have effectively disabled any ata/atapi support :) > Or is this not an _exact_ copy of your config... > > The CMD640 might very well be the help you needed... In fact, it shouldn't, since only one IDE controller is defined. In that case the code shouldn't be changed by the CMD640 option. Wolfgang > > Actually, not really the answer, but I did get it to work. I > > ended up downloading the boot.flp from the latest snapshot, then when that > > worked, building a GENERIC kernel...and when that worked, copied in > > anything that appeared pertinent...and now it works. > > > > I had: > > > > #controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ffa004 You need to define an IDE controller to use an ATAPI CDROM. > > vector wdintr > > #disk wd0 at wdc0 drive 0 > > #disk wd1 at wdc0 drive 1 > > #options ATAPI #Enable ATAPI support for IDE bus > > #options ATAPI_STATIC #Don't do it as an LKM And you need to define ATAPI options. > > #device wcd0 #IDE CD-ROM > > > > And now have: > > > > options "CMD640" # work around CMD640 chip deficiency > > controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr > > disk wd0 at wdc0 drive 0 > > disk wd1 at wdc0 drive 1 In theory, you do not need those disk statements if you don't have an IDE disk. But they might help to successfully probe the CD. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 00:57:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12950 for current-outgoing; Tue, 10 Feb 1998 00:57:28 -0800 (PST) (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 AAA12935 for ; Tue, 10 Feb 1998 00:57:23 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id BAA28008; Tue, 10 Feb 1998 01:57:23 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd027981; Tue Feb 10 01:57:13 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id BAA22938; Tue, 10 Feb 1998 01:57:11 -0700 (MST) From: Terry Lambert Message-Id: <199802100857.BAA22938@usr05.primenet.com> Subject: Re: Heads up: static -ification To: eivind@yes.no (Eivind Eklund) Date: Tue, 10 Feb 1998 08:57:11 +0000 (GMT) Cc: tlambert@primenet.com, eivind@yes.no, current@FreeBSD.ORG In-Reply-To: <19980210030906.20113@follo.net> from "Eivind Eklund" at Feb 10, 98 03:09:06 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 > > Remember that functions and variables are exported interfaces in > > many cases. This includes user space uses for "ps", "w", "netstat", > > and so on, as well as kernel space uses. > > I know. I hope I didn't break any of them; the suspicion that I might > have was the reason for sending the heads-up in the first place. > > I though fixing this (the extreme spread of kernel symbols) was worth > the potential trouble. > > BTW: Speaking of symbol spread - you once gave a reference to the ld > manpage and implied that it was possible to create new object files > included a specific subset of the symbols from the original object > files. I tried to find out how to do this, as I wanted it both for > the kernel and for libalias, but I've spent quite some time without > finding out how to do it. Would you mind giving detailed > instructions? (Re-creating object files is easy, the problem is > controlling which symbols to include on a fine-grained basis). You should look at the man page again. Keep in hand a copy of the nm man page with reference to the "-g" option, and a copy of the modload source code. The modload source code works by linking an object (or ld -r'ed objects) against the kernel symbol table at a relative offset of zero to get the size of the resulting binary (aren't we lucky that the kernel is linked high? 8-)). Then space is allocated to contain the text and data, and the object is linked again, with the offest of the allocation. Finally, the data is pushed across the /usr/kernel boundry (at the time it was written, the cache was not unified, and kernel space mmap would not work; both that code, and all execution class loaders -- my name for ABI's when I originally released the LKM code, which I also wrote -- should be rewritten to use mmap()). > > For a potential kernel environment, you should be careful to not > > disallow dynamic replacement of kernel pieces using "generic" > > loadable modules (ie: if something is a function pointer, it > > should not be static'ed, unless there is an encapsulation function > > that can be used to modify its value, and then the encapsulation > > function should not be static). > > I think I may have broken one of these. I'll look through my patches > again. (I remember seeing something that looked like the above, and I > don't remember what I did with it. I just remember being in doubt.) If I don't miss my guess, this was either in the console code (World21 uses this to replace the console with an internalized console capable of displaying 21 different locales -- one at a time) or it's in the NFS lease function pointer management. Those are the two examples that spring to mind. If you can make sure when you build that the LKM's build as well, and then ld -A them against the kernel to see if there are unresolved externals (pretty easy). You may wish to explicitly contact binary driver vendors (like Dennis at ETINC), who may depend on unknown symbols. I definitely agree that the interfaces should be pruned, for what it's worth. I'm not quite to the point that I agree with the Linux/AIX or Microsoft link ".DEF" file approach to defining external interfaces to objects, but a directive to decide which symbol table in an ELF file, for instance, would probably be acceptable to everyone, especially if it were a macro wrapped storage class specifier or a #pragma of some kind (we will need these for marking things pageable and "non-load" for the kernel loader at some point, anyway). Once this is done, along with your other changes, then we will be a long way down the road of having a documentable DDI/DKI that we can stick with to get vendors to start writing binary drivers for their hardware for FreeBSD (I'm sure the aforementioned Dennis would be happy with this). A lot of problems like this come from subsystem exposure. Veto interfaces will definitely reduce the kernel symbol "footprint" of subsystems (my favorite hobby horse here is the VOP_ADVLOCK code in the FS's). Most of these are violations of the "downcalls only, no upcalls" rule that any beginning professional interface designer must know. In any case, keep up the good work; I only meant to caution you about the amount of exposure that was dependended upon; I in no way advocate it, nor do I hold it up as an example of "good engineering practice". ;-). In general, anything that links against libkvm is at risk, as far as user space goes. The "ps" and "vmstat" code are primary examples, since the symbols they reference aren't necessarily consumed directly without a bunch of arcane arguments to them on the command line. 8-(. You should be able to find the "at risk" programs by renaming and disabling the libkvm build, and doing a build world with make -i and then make -k (in case someone depends on something that isn't an explicit dependency). The output log should tell you where to look. The parameteric symbol uses are unfortunately the most complex to diagnose reliably. You may need to build shell scripts to exercise them individually. 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 01:02:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13881 for current-outgoing; Tue, 10 Feb 1998 01:02:57 -0800 (PST) (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 BAA13875 for ; Tue, 10 Feb 1998 01:02:56 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id CAA22367; Tue, 10 Feb 1998 02:02:55 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd022362; Tue Feb 10 02:02:49 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id CAA23314; Tue, 10 Feb 1998 02:02:47 -0700 (MST) From: Terry Lambert Message-Id: <199802100902.CAA23314@usr05.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 10 Feb 1998 09:02:47 +0000 (GMT) Cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <26929.887078004@time.cdrom.com> from "Jordan K. Hubbard" at Feb 9, 98 06:33:24 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > i have also noticed a lack of response on any questions to this group > > dealing with this issue. i have previously asked about such support > > and received absolutely no answers in the [recent] past. > > There's no one who currently "owns" MSDOSFS, that's why, and no one to > do the work of integrating changes from NetBSD or any other OS. Any > volunteers? If the FS framework were logically layered to eliminate upcalls and make all VOP's reflexive, I would be willing to take on this task. Without these prerequisites, it's practically impossible to support the necessary namespace changes for the Unicode namespace and the dual namespace for VFAT (the Windows95 collision avoidance algorithm depends on non-late-binding of short names for a given long name, as both the SAMBA maintainers and the MSDOSFS people who attempted the integration before have discovered). The same goes for Apple HFS (which has a second ProDOS namespace), OS/2 HPFS (which has a second longname namespace), and NTFS (which has multiple auxillary namespaces for both POSIX and MSDOS emulation support). 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 01:13:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15082 for current-outgoing; Tue, 10 Feb 1998 01:13:16 -0800 (PST) (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 BAA15073 for ; Tue, 10 Feb 1998 01:13:13 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id CAA29896; Tue, 10 Feb 1998 02:13:12 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd029882; Tue Feb 10 02:13:10 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id CAA23783; Tue, 10 Feb 1998 02:13:07 -0700 (MST) From: Terry Lambert Message-Id: <199802100913.CAA23783@usr05.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: dima@tejblum.dnttm.rssi.ru (Dmitrij Tejblum) Date: Tue, 10 Feb 1998 09:13:07 +0000 (GMT) Cc: jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199802100719.KAA01219@tejblum.dnttm.rssi.ru> from "Dmitrij Tejblum" at Feb 10, 98 10:19:44 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There's no one who currently "owns" MSDOSFS, that's why, and no one to > > do the work of integrating changes from NetBSD or any other OS. Any > > volunteers? > > Me. Please apply my nami/nameifree patches before attempting this. If you do not, the resulting created long file names will not be usable from Windows95. Specifically, 4DOS get a short name list, and then goes back and requests the long names given the short names. The previously discussed short name generation algorithm will fail to result in names that will work with this commonly used shareware shell. The MKS tools cwBourne shell does the same thing. Also, note that because the implementation of the pathname buffer representation is known to the FS's (the FS's must free the buffer on behalf of the caller in the current implementation), you will not be able to round-trip the Unicode via the pathname buffer. As a result, you will have to choose a specific locale to use to create the file names. The simplest of these will be the ISO 8859-1 locale, since it maps into code page 0 of the Unicode standard. Unfortunately, this will mean that VFAT names created in a different locale will be impossible to round-trip out to the user's current locale. You will also be unable to localize this support to a non-ISO 8859-1 using country. This is basically a result of your having to do the path data converision to Unicode under the covers of namei instead of over them, where you would have (putative) access to the user's environment. This in turn is a result of the non-inheritance of path component attributes across component lookups in the underlying FS. It's nice to see people becoming interested in FS hacking, but care should be taken: the framework in which you will be hacking is not as orthogonal as it first appears. 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 01:20:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16328 for current-outgoing; Tue, 10 Feb 1998 01:20:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16312 for ; Tue, 10 Feb 1998 01:20:04 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id BAA05685; Tue, 10 Feb 1998 01:19:47 -0800 (PST) To: Terry Lambert cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 09:02:47 GMT." <199802100902.CAA23314@usr05.primenet.com> Date: Tue, 10 Feb 1998 01:19:47 -0800 Message-ID: <5682.887102387@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If the FS framework were logically layered to eliminate upcalls and > make all VOP's reflexive, I would be willing to take on this task. Translation: "No." :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 01:29:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17645 for current-outgoing; Tue, 10 Feb 1998 01:29:37 -0800 (PST) (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 BAA17639 for ; Tue, 10 Feb 1998 01:29:34 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id CAA02043; Tue, 10 Feb 1998 02:29:34 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd002008; Tue Feb 10 02:29:26 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id CAA24285; Tue, 10 Feb 1998 02:29:22 -0700 (MST) From: Terry Lambert Message-Id: <199802100929.CAA24285@usr05.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 10 Feb 1998 09:29:22 +0000 (GMT) Cc: tlambert@primenet.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <5682.887102387@time.cdrom.com> from "Jordan K. Hubbard" at Feb 10, 98 01:19:47 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 > > If the FS framework were logically layered to eliminate upcalls and > > make all VOP's reflexive, I would be willing to take on this task. > > Translation: "No." :-) Translation: "Jordan should give me the same benefit of the doubt as he gives to complete strangers". 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 01:32:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18192 for current-outgoing; Tue, 10 Feb 1998 01:32:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18187 for ; Tue, 10 Feb 1998 01:32:05 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id BAA05771; Tue, 10 Feb 1998 01:31:48 -0800 (PST) To: Terry Lambert cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 09:29:22 GMT." <199802100929.CAA24285@usr05.primenet.com> Date: Tue, 10 Feb 1998 01:31:48 -0800 Message-ID: <5767.887103108@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > If the FS framework were logically layered to eliminate upcalls and > > > make all VOP's reflexive, I would be willing to take on this task. > > > > Translation: "No." :-) > > Translation: "Jordan should give me the same benefit of the doubt as > he gives to complete strangers". I think you misread that one. Consider the odds of "the FS framework being logically layered to eliminate upcalls and make all VOP's reflexive" as a prerequisite and you'll see the accuracy of my translation emerge. :) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 01:37:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19339 for current-outgoing; Tue, 10 Feb 1998 01:37:18 -0800 (PST) (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 BAA19306 for ; Tue, 10 Feb 1998 01:37:14 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.7/8.8.7) id UAA03998; Tue, 10 Feb 1998 20:41:55 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199802100941.UAA03998@cimlogic.com.au> Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <199802100929.CAA24285@usr05.primenet.com> from Terry Lambert at "Feb 10, 98 09:29:22 am" To: tlambert@primenet.com (Terry Lambert) Date: Tue, 10 Feb 1998 20:41:55 +1100 (EST) Cc: jkh@time.cdrom.com, tlambert@primenet.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > Translation: "Jordan should give me the same benefit of the doubt as > he gives to complete strangers". I guess he doubts incomplete strangers. 8-) -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 02:22:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA25344 for current-outgoing; Tue, 10 Feb 1998 02:22:20 -0800 (PST) (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 CAA25339 for ; Tue, 10 Feb 1998 02:22:17 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id DAA09827; Tue, 10 Feb 1998 03:22:17 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd009802; Tue Feb 10 03:22:10 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id DAA25240; Tue, 10 Feb 1998 03:22:06 -0700 (MST) From: Terry Lambert Message-Id: <199802101022.DAA25240@usr05.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 10 Feb 1998 10:22:06 +0000 (GMT) Cc: tlambert@primenet.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <5767.887103108@time.cdrom.com> from "Jordan K. Hubbard" at Feb 10, 98 01:31:48 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > If the FS framework were logically layered to eliminate upcalls and > > > > make all VOP's reflexive, I would be willing to take on this task. > > > > > > Translation: "No." :-) > > > > Translation: "Jordan should give me the same benefit of the doubt as > > he gives to complete strangers". > > I think you misread that one. Consider the odds of "the FS framework > being logically layered to eliminate upcalls and make all VOP's > reflexive" as a prerequisite and you'll see the accuracy of my > translation emerge. :) Well, I think Poul has honestly done a lot of work in this area, and I've done most of the rest of the work, if only people would take the code without insisting on understanding how it works, so long as it does (I'm willing to be called to account when it doesn't, and I'm in the Bay Area now, so if you are interested, I can whiteboard anything that isn't obvious, and save a lot of written hand-waving; some of these problems are hard, and you can't easily explain hard problems, or they wouldn't be hard problems. Worst case, you can just back it out, like you've done with other changes). Frankly, I don't pretend to understand all of the intracacies of everything in the VM system (only the parts I care about, and the others, only enough to get me into trouble). But I've been doing FS work professionally for about 10 years now, on a large number of platforms, and I've hacked on "Oh golly" code in Veritas and NetWare UNIX Client, and locking in AIX (I don't know anyone else who can do advisory locking from AIX kernel threads), and an SMP-safe FS for SVR4 and SunOS and Solaris. I certainly don't expect everyone to understand what I understand without putting in 10 years on the subject themselves (yes, I readily acknowledge that there are people who've done this, and people who've done a hell of a lot more, but I'm willing to contribute code and fixes to FreeBSD, and they are all off working on proprietary code). There is a dearth of real architecture work that's going on right now, and I have a real problem with this fact. The NFS breakage is one example of an architectural cascade failure that's out of control, despite the best efforts of those valiantly in the path of the avalanche. FreeBSD used to be able to point to the stability of it's networking and it's NFS as being "the reference implementations", and now it's being beaten up. This *must* stop. Apparently, very recently, it was decided that the primary reason stated against incorporating my FS architecture changes, divergence from other BSD's, no longer held as much force. Certainly, the *necessary* work Elvind is doing attests to that: the need for a clean workplace finally outweighed the need to prevent divergence from other dirtier workplaces (I would be happy for them to pick up my FS code from FreeBSD, just as FreeBSD picked up my LKM code from NetBSD). FS hackers need an equivalent "clean workplace" -- me among them. It would be a shame to lose this *wonderful* momentum towards actual, and IMO, necessary to the future of FreeBSD, progress, without at least a token struggle. 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 02:25:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26325 for current-outgoing; Tue, 10 Feb 1998 02:25:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26268 for ; Tue, 10 Feb 1998 02:25:22 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id NAA23044; Tue, 10 Feb 1998 13:15:27 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id NAA03007; Tue, 10 Feb 1998 13:21:16 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802101021.NAA03007@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Jordan K. Hubbard" cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Mon, 09 Feb 1998 23:25:52 PST." <1760.887095552@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 1998 13:21:16 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Great! You'll test this in -current and give one of the committers > something to commit once you're comfortable with the testing, Are you the volunteered commiter? I run my patches under -current several months, and almost comfortable with testing. I should clean up some things, though. I probably could send you patches until end of week. > or what > precisely? > What else you can propose? Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 02:27:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26535 for current-outgoing; Tue, 10 Feb 1998 02:27:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26486 for ; Tue, 10 Feb 1998 02:26:39 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id NAA23042; Tue, 10 Feb 1998 13:15:26 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id NAA02985; Tue, 10 Feb 1998 13:20:58 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802101020.NAA02985@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Mon, 09 Feb 1998 16:54:51 PST." <199802100054.QAA05622@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 1998 13:20:58 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > I should also point out that there is another diff, msdosfs-vfat.diff, in > > incoming. This diff is for 2.2. It is original and independent work of > > Luoqi Chen. It is not supposed to support FAT32. May be, now Luoqi did some > > further development of his work. > > I think that this is where things hit a logjam last time; there are two > sets of incompatible patches to achieve two desirable things. *Two* desirable things? That is, VFAT for 2.2 and VFAT for -current? Or what do you mean? > Until > the two sets of patches are _merged_, there is unlikely to be anything > committed. I don't underastand this idea at all. If you like Luoqi's patches more than mine, please go ahead and commit them. At least, I will not need to constantly sync my patches with -current. I made my patches mostly because I "really" need long file name support (I do some multi-platfom development...). So, if a working long file name support will be added to -current, I will be happy. Of course, I prefer to see my patches committed. I should clean up some things until (and if) they will be committed. If you want to commit my patches, tell me and I will do it. Also, I will appreciate review of my patches. Merging my and Luoqi's patches is somewhat difficult, since they are incompatible, and pointless, at least as a prerequistic. Such merge would not create something much better than each of these 2 patches, and there is far more important things, in msdosfs, in FreeBSD in general, and in my life. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 02:28:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27123 for current-outgoing; Tue, 10 Feb 1998 02:28:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA27044 for ; Tue, 10 Feb 1998 02:28:08 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id NAA23043; Tue, 10 Feb 1998 13:15:27 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id NAA03023; Tue, 10 Feb 1998 13:22:00 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802101022.NAA03023@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 09:13:07 GMT." <199802100913.CAA23783@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 1998 13:21:59 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > There's no one who currently "owns" MSDOSFS, that's why, and no one to > > > do the work of integrating changes from NetBSD or any other OS. Any > > > volunteers? > > > > Me. > > Please apply my nami/nameifree patches before attempting this. Where can I gen them? > If you > do not, the resulting created long file names will not be usable from > Windows95. Specifically, 4DOS get a short name list, and then goes back > and requests the long names given the short names. Well, I don't use 4DOS, and believed that created long file names are ok. Scandisk doesn't report any problems also. How 4DOS can have problems? Doesn't it use standard DOS or Windows syscalls? > [problems with locales] This is indeed a big headache for me. I have several files with Russian filenames, and msdosfs doesn't do something minimally correct with them at all. So I am interested to look at your code. But I believe that in the meantime something working in real life is already useful. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 02:42:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29500 for current-outgoing; Tue, 10 Feb 1998 02:42:56 -0800 (PST) (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 CAA29495 for ; Tue, 10 Feb 1998 02:42:54 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id DAA04214; Tue, 10 Feb 1998 03:42:53 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd004209; Tue Feb 10 03:42:44 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id DAA25601; Tue, 10 Feb 1998 03:42:40 -0700 (MST) From: Terry Lambert Message-Id: <199802101042.DAA25601@usr05.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: dima@tejblum.dnttm.rssi.ru (Dmitrij Tejblum) Date: Tue, 10 Feb 1998 10:42:40 +0000 (GMT) Cc: tlambert@primenet.com, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199802101022.NAA03023@tejblum.dnttm.rssi.ru> from "Dmitrij Tejblum" at Feb 10, 98 01:21:59 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 > > Please apply my nami/nameifree patches before attempting this. > > Where can I gen them? >From the -current list archives, or in ~terry on freefall.freebsd.org. > > If you > > do not, the resulting created long file names will not be usable from > > Windows95. Specifically, 4DOS get a short name list, and then goes back > > and requests the long names given the short names. > > Well, I don't use 4DOS, and believed that created long file names are ok. > Scandisk doesn't report any problems also. How 4DOS can have problems? > Doesn't it use standard DOS or Windows syscalls? It uses DOs calls to get the directory, then goes back and uses Win95 calls to get the long name from the short name. The problem is that the same algorithm *must* be used for this to work reliably. This is documented in the IFS.DOC in the DDK of the MSDN Level II developer CDROM, along with the collision algortihm. I published the algorithm (from observation of behaviour, later verified by the MS document) both on the SAMBA mailing list, and in the -current and -hacker's archives (in reply to Rober Nordier, who was precviously working on VFAT support in FreeBSD -- you may wish to contact him). > > [problems with locales] > > This is indeed a big headache for me. I have several files with Russian > filenames, and msdosfs doesn't do something minimally correct with them > at all. So I am interested to look at your code. But I believe that in the > meantime something working in real life is already useful. If the path buffer is opaque, you can send both Unicode and 8.3 data down, based on what the FS that's decoding the component wants. There is a UNICODE flag in namei.h for this. The problem is that you can't guarantee not to sleep when traversing the directory looking for the numeric tail for the short name. This means that it's not safe to reeenter the VOP_LOOKUP with the CREATE/RENAME flags set on a given dir. The only way you can guarantee this in the face of the parent -> child traversal race condition is to do the name binding in the CREATE/RENAME commit while holding a lock on the directory. You also need to flag if the name going down is a valid 8.3 name, or if it is a long name. This is only for the terminal path component (Win95 must do it for each path component, so this is one difference). The reason for this problem is that in VFAT a directory entry *is* an inode. I did effectively this when I converted FFS/UFS for Windows 95 IFS, and added a Unicode name space and 8.3 names for FFS/UFS directory entries; the problems I faced are exactly the inverse of the problems you face. 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 03:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA02544 for current-outgoing; Tue, 10 Feb 1998 03:04:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA02539 for ; Tue, 10 Feb 1998 03:04:28 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id DAA15316; Tue, 10 Feb 1998 03:04:11 -0800 (PST) To: Terry Lambert cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 10:22:06 GMT." <199802101022.DAA25240@usr05.primenet.com> Date: Tue, 10 Feb 1998 03:04:10 -0800 Message-ID: <15304.887108650@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I think Poul has honestly done a lot of work in this area, and > I've done most of the rest of the work, if only people would take the > code without insisting on understanding how it works, so long as it It's not "people" who need to take this code, however. What's needed is "a person" (possibly more than one, but that's neither here nor there) who's also wearing a committer hat and is willing to front this for you in -current. Find yourself that person to stand behind and understand that no matter what you might personally be willing to promise, it's still HE who's going to be held most principally responsible for it since his fingerprints will be the ones directly on the repository and so should thus have at least some *hope* of understanding your code, at least. Any random committer won't do or I might be even willing to do it myself, if only to see what your next move was. :-) However, I'm not a FS dude and never pretended to be so it's gotta be one of those other 107 committers who play in /sys more often than I do. Find one, work the change through him, do it just like all the other "complete strangers" out there have done it and it will be done. :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 03:31:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06367 for current-outgoing; Tue, 10 Feb 1998 03:31:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA06354 for ; Tue, 10 Feb 1998 03:31:31 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 1717 invoked by uid 100); 10 Feb 1998 11:33:04 -0000 Message-ID: <19980210033259.62112@top.worldcontrol.com> Date: Tue, 10 Feb 1998 03:32:59 -0800 To: Chris Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: rxvt: can't load color "darkslateblue" ; 16 bit depth Mail-Followup-To: Chris Dillon , freebsd-current@freebsd.org References: <19980209002408.02309@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.90.1i In-Reply-To: ; from Chris Dillon on Mon, Feb 09, 1998 at 07:44:04AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 09-Feb-98 brian@worldcontrol.com wrote: > >I'm running -current. After working on my laptop for some time, I > >find that I can't create any more rxvt windows. > > > >Specifically I get: > > > >brian@top>rxvt > >rxvt: can't load color "darkslateblue" > >rxvt: can't load color "White" > >rxvt: aborting > > > >I found in /var/log/messages that apparently some other process has > >had similar complaints: > > > >Warning: Color name "black" is not defined > >Warning: Color name "Black" is not defined > > > >If I reboot the systems, the problem is gone, and then comes back later. > > > >What is happening? On %M %N, Chris Dillon wrote: > Nothing is wrong, really. If you are using an 8-bit color depth (256 colors) > not all applications can get the colors they want, and must share amongst what > is available. Use a 16-bit or 24-bit color depth and those messages will > disappear (not to mention everything will just generally look better). Thanks for the pointer, sadly, I'm running 16-bit depth: xwininfo: Window id: 0x26 (the root window) (has no name) Absolute upper-left X: 0 Absolute upper-left Y: 0 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 1024 Height: 768 Depth: 16 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x23 (installed) Bit Gravity State: ForgetGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +0+0 -0+0 -0-0 +0-0 -geometry 1024x768+0+0 Any other ideas? -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 03:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA07712 for current-outgoing; Tue, 10 Feb 1998 03:43:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA07692 for ; Tue, 10 Feb 1998 03:43:27 -0800 (PST) (envelope-from bsdcur@shadows.aeon.net) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.8/8.8.3) id NAA15114 for current@freebsd.org; Tue, 10 Feb 1998 13:43:46 +0200 (EET) From: mika ruohotie Message-Id: <199802101143.NAA15114@shadows.aeon.net> Subject: scsi performance in current... To: current@FreeBSD.ORG Date: Tue, 10 Feb 1998 13:43:46 +0200 (EET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG where is my scsi performance going? i installed the machine from the latest snap cdrom i had, october, remade the kernel, couldnt use AHC options (kernel compilation failed) so i made on without them, and bonnie gives me: -------Sequential Output-------- ---Sequential Input--- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU sd0s1e 384 10018 69.4 9812 17.5 3363 8.9 12761 91.9 12824 20.8 124.6 2.1 that is a filesystem right after the root partition 64M root partition and 448M swap partition. and i am MOST impressed about the performance, this is by far the fastest result i've ever seen. the drive is 9GB western digital ultra wide, connected into 2940UW, machine is pII 262,5MHz (75MHzx3.5) with 128M SDRAM, the board is Soyo (i wanted asus but couldnt wait for few days until the suppliers would've gotten those) dual pII, with one cpu. (i include dmesg and kernel config to the end of this mail for those interested in reading that). for the record, the END of the drive still performs: sd0s3f 384 7080 49.0 6971 12.3 2579 5.5 8181 58.4 8179 9.4 115.4 1.6 (that is about as end as i can get, the last filesystem is 468745 1K-blocks, and the performance is still quite outstanding, outperforming some 4 disk! ccd-setups i've gotten in the past) and "bad" test with 8M file: sd0s1e 8 14007 93.2 49940 82.9 35081 67.2 11700 78.5 139066 99.5 1193.5 9.0 BUT!!! without changing ANYTHING else but cvsupping into the february 4th CURRENT tree, and adding those three AHC kernel options, the machine is only able to give me this: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU sd0s1e 384 3384 23.6 2969 5.4 2200 6.1 11449 89.0 12176 20.9 147.8 2.2 sd0s1e 8 14216 97.5 53072 90.2 38811 99.9 6099 42.2 88255 99.8 3191.6 35.3 same filesystem, STILL EMPTY! where did the disk i/o go? AARGH! (for the record part2, i installed another drive, sd1, ibm ultra scsi 4GB, and it gives me now: sd1s1e 384 6532 45.8 5788 10.7 2206 7.1 7441 57.6 7457 16.0 94.3 1.6 and to me that looks about "right" for such a drive...) dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Thu Feb 5 20:54:55 GMT 1998 root@tuuba:/usr/src/sys/compile/TUUBA CPU: Pentium Pro (262.52-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80fbff real memory = 134217728 (131072K bytes) avail memory = 128057344 (125056K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x01 int d irq 11 on pci0.7.2 chip4: rev 0x01 on pci0.7.3 ahc0: rev 0x01 int a irq 10 on pci0.16.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs scbus0 at ahc0 bus 0 ahc0: target 0 Tagged Queuing Device sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 8683MB (17783204 512 byte sectors) ahc0:A:6: refuses WIDE negotiation. Using 8bit transfers ahc0: target 6 Tagged Queuing Device sd1 at scbus0 target 6 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 4134MB (8467200 512 byte sectors) fxp0: rev 0x02 int a irq 10 on pci0.12 .0 fxp0: Ethernet address 00:a0:c9:45:6e:23 vga0: rev 0x01 int a irq 9 on pci0.18.0 Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A wdc0 at 0x1f0-0x1f7 irq 14 flags 0x20ff20ff on isa wdc0: unit 0 (atapi): , removable, dma, iordy atapi0.0: unknown phase npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, unlimited logging changing root device to sd0a kernel config: (should i change anything there? remove/add) machine "i386" cpu "I686_CPU" ident TUUBA maxusers 128 options MATH_EMULATE options INET options FFS options NFS options "CD9660" options PROCFS options KERNFS options QUOTA options FAT_CURSOR options "COMPAT_43" options BOUNCE_BUFFERS options UCONSOLE options FAILSAFE options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" options CLK_CALIBRATION_LOOP options "CLK_USE_I8254_CALIBRATION" options "CLK_USE_I586_CALIBRATION" options PQ_LARGECACHE options CPU_UPGRADE_HW_CACHE options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO options USERCONFIG options VISUAL_USERCONFIG options INCLUDE_CONFIG_FILE options IPFIREWALL options IPFIREWALL_VERBOSE options IPDIVERT options PERFMON options COMPAT_LINUX options ATAPI options ATAPI_STATIC config kernel root on sd0 swap on sd0 and sd1 dumps on sd0 controller isa0 controller pci0 controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x20ff20ff vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 device wcd0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" flags 0x0 irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr controller scbus0 controller ahc0 device sd0 device de0 device fxp0 pseudo-device loop pseudo-device ether pseudo-device pty 128 pseudo-device snp 4 pseudo-device gzip pseudo-device bpfilter 4 mickey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 03:53:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09202 for current-outgoing; Tue, 10 Feb 1998 03:53:53 -0800 (PST) (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 DAA09032; Tue, 10 Feb 1998 03:53:10 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with ESMTP id GAA29760; Tue, 10 Feb 1998 06:53:23 -0500 (EST) Date: Tue, 10 Feb 1998 06:53:22 -0500 (EST) From: The Hermit Hacker To: Søren Schmidt cc: freebsd-current@FreeBSD.ORG Subject: Re: ACER CD910E/JAS IDE CDrom... In-Reply-To: <199802100717.IAA01018@sos.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Feb 1998, Søren Schmidt wrote: > In reply to The Hermit Hacker who wrote: > > The problem is the '#' in front of all the lines in the section > "I had", you have effectively disabled any ata/atapi support :) > Or is this not an _exact_ copy of your config... Sorry, when I did config the system, the commented lines were what was uncommented, and the "And now have" didn't exist...if I had those lines commented out, my system wouldn't have booted, as its an IDE system :) > The CMD640 might very well be the help you needed... Okay, I'll try that out tonight then...see if taking it out re-breaks it... > > > Actually, not really the answer, but I did get it to work. I > > ended up downloading the boot.flp from the latest snapshot, then when that > > worked, building a GENERIC kernel...and when that worked, copied in > > anything that appeared pertinent...and now it works. > > > > I had: > > > > #controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ffa004 > > vector wdintr > > #disk wd0 at wdc0 drive 0 > > #disk wd1 at wdc0 drive 1 > > #options ATAPI #Enable ATAPI support for IDE bus > > #options ATAPI_STATIC #Don't do it as an LKM > > #device wcd0 #IDE CD-ROM > > > > And now have: > > > > options "CMD640" # work around CMD640 chip deficiency > > controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr > > disk wd0 at wdc0 drive 0 > > disk wd1 at wdc0 drive 1 > > > > #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr > > #disk wd2 at wdc1 drive 0 > > #disk wd3 at wdc1 drive 1 > > > > options ATAPI #Enable ATAPI support for IDE bus > > options ATAPI_STATIC #Don't do it as an LKM > > device wcd0 #IDE CD-ROM > > > > I haven't investigated further, yet, about whether the problem is > > the missing CMD640 or the flags setting on wdc0...before I go through > > that, does anyone know if either should affect it? If its something > > known, no reason to go and test it...:) > > > > Marc G. Fournier > > Systems Administrator @ hub.org > > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 current" in the body of the message From owner-freebsd-current Tue Feb 10 03:55:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09524 for current-outgoing; Tue, 10 Feb 1998 03:55:33 -0800 (PST) (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 DAA09363; Tue, 10 Feb 1998 03:54:58 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id GAA29790; Tue, 10 Feb 1998 06:54:20 -0500 (EST) Date: Tue, 10 Feb 1998 06:54:19 -0500 (EST) From: The Hermit Hacker To: Wolfgang Helbig cc: sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: ACER CD910E/JAS IDE CDrom... In-Reply-To: <199802100853.JAA00421@rvc1.informatik.ba-stuttgart.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Feb 1998, Wolfgang Helbig wrote: > > In reply to The Hermit Hacker who wrote: > > > > The problem is the '#' in front of all the lines in the section > > "I had", you have effectively disabled any ata/atapi support :) > > Or is this not an _exact_ copy of your config... > > > > The CMD640 might very well be the help you needed... > > In fact, it shouldn't, since only one IDE controller is defined. > In that case the code shouldn't be changed by the CMD640 option. > > Wolfgang > > > > Actually, not really the answer, but I did get it to work. I > > > ended up downloading the boot.flp from the latest snapshot, then when that > > > worked, building a GENERIC kernel...and when that worked, copied in > > > anything that appeared pertinent...and now it works. > > > > > > I had: > > > > > > #controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x00ffa004 > > You need to define an IDE controller to use an ATAPI CDROM. > > > > vector wdintr > > > #disk wd0 at wdc0 drive 0 > > > #disk wd1 at wdc0 drive 1 > > > #options ATAPI #Enable ATAPI support for IDE bus > > > #options ATAPI_STATIC #Don't do it as an LKM > > And you need to define ATAPI options. Actually, I did, in both cases...I cut and paste from my current config, where I had the above enabled, and blow disabled... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 04:44:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20119 for current-outgoing; Tue, 10 Feb 1998 04:44:08 -0800 (PST) (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 EAA20064 for ; Tue, 10 Feb 1998 04:44:02 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id MAA01640; Tue, 10 Feb 1998 12:43:45 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id NAA15263; Tue, 10 Feb 1998 13:43:43 +0100 (MET) Message-ID: <19980210134334.60912@follo.net> Date: Tue, 10 Feb 1998 13:43:34 +0100 From: Eivind Eklund To: "Jordan K. Hubbard" Cc: Terry Lambert , freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs References: <199802101022.DAA25240@usr05.primenet.com> <15304.887108650@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <15304.887108650@time.cdrom.com>; from Jordan K. Hubbard on Tue, Feb 10, 1998 at 03:04:10AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 10, 1998 at 03:04:10AM -0800, Jordan K. Hubbard wrote: > > Well, I think Poul has honestly done a lot of work in this area, and > > I've done most of the rest of the work, if only people would take the > > code without insisting on understanding how it works, so long as it > > It's not "people" who need to take this code, however. What's needed > is "a person" (possibly more than one, but that's neither here nor > there) who's also wearing a committer hat and is willing to front this > for you in -current. Find yourself that person to stand behind and > understand that no matter what you might personally be willing to > promise, it's still HE who's going to be held most principally > responsible for it since his fingerprints will be the ones directly on > the repository and so should thus have at least some *hope* of > understanding your code, at least. I'm willing to try. I've been toying with just running some of Terrys patches here and see if they're stable, attempting to test the areas they touch, and then just commit them and take the blame (if any). I'm just not quite certain how hard that blame is going to be, and I would dislike loosing my commit privileges :-( I don't think I have time to really understand all of the issues with all of the changes; the best I'd be able to do is understand the overall goals, and see 'this looks good', and test that it works. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 04:52:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21165 for current-outgoing; Tue, 10 Feb 1998 04:52:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21160 for ; Tue, 10 Feb 1998 04:52:27 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id EAA12823; Tue, 10 Feb 1998 04:51:59 -0800 (PST) To: Eivind Eklund cc: Terry Lambert , freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 13:43:34 +0100." <19980210134334.60912@follo.net> Date: Tue, 10 Feb 1998 04:51:59 -0800 Message-ID: <12818.887115119@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm willing to try. I've been toying with just running some of Terrys > patches here and see if they're stable, attempting to test the areas they > touch, and then just commit them and take the blame (if any). I'm just not > quite certain how hard that blame is going to be, and I would dislike > loosing my commit privileges :-( In -current, you and your commit privileges are reasonably safe as long as you're at least willing to deal with any potential "this sucks because ..." arguments that may come up and, should those arguments prove convincing enough, be willing to back the changes out again. It's only the folks that get sticky over such issues that ever get the Big Stick waved at them. :-) Needless to say, you're also expected to make every reasonable effort to stress test the code on a local machine before committing it. "Well, it compiled!" is not anyone's idea of a proper acceptance test. ;) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 06:11:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01609 for current-outgoing; Tue, 10 Feb 1998 06:11:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01586 for ; Tue, 10 Feb 1998 06:11:31 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id PAA29471; Tue, 10 Feb 1998 15:12:59 +0100 (CET) Message-ID: <19980210151257.23319@cons.org> Date: Tue, 10 Feb 1998 15:12:57 +0100 From: Martin Cracauer To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG, cracauer@cons.org Subject: Re: cvs commit: src/bin/sh jobs.c References: <199802071645.DAA14279@godzilla.zeta.org.au> <19980207195952.24691@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <19980207195952.24691@cons.org>; from Martin Cracauer on Sat, Feb 07, 1998 at 07:59:52PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patch below makes sh pass all my tests. In addition to the last one, it also behaves right on: #!./testshell echo 'Test 2: You should not be able to exit cat with SIGINT.' echo ' But SIGQUIT should abort cat with coredump while' echo ' the shell should continue and call cat again.' echo ' SIGTERM should exit the whole script.' set -x trap '' 2 while : ; do cat ; echo -n $? ; done # End of script *** sh/jobs.c Tue Feb 10 10:42:47 1998 --- sh.cra/jobs.c Tue Feb 10 14:54:50 1998 *************** *** 86,89 **** --- 86,92 ---- int curjob; /* current job */ #endif + sig_t oldsigint; + sig_t oldsigquit; + int oldsigs_valid = 0; #if JOBS *************** *** 575,580 **** --- 578,593 ---- mode)); INTOFF; + if (mode == FORK_FG) { + oldsigquit = signal(SIGQUIT, SIG_IGN); + oldsigint = signal(SIGINT, SIG_IGN); + oldsigs_valid = 1; + } pid = fork(); if (pid == -1) { + if (oldsigs_valid) { + signal(SIGQUIT, oldsigquit); + signal(SIGINT, oldsigint); + oldsigs_valid = 0; + } TRACE(("Fork failed, errno=%d\n", errno)); INTON; *************** *** 587,590 **** --- 600,607 ---- TRACE(("Child shell %d\n", getpid())); + if (oldsigquit != SIG_IGN) + signal(SIGQUIT,SIG_DFL); + if (oldsigint != SIG_IGN) + signal(SIGINT,SIG_DFL); wasroot = rootshell; rootshell = 0; *************** *** 701,704 **** --- 718,727 ---- dowait(1, jp); } + if (oldsigs_valid) { + signal(SIGQUIT, oldsigquit); + signal(SIGINT, oldsigint); + oldsigs_valid = 0; + } + #if JOBS if (jp->jobctl) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 06:18:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03209 for current-outgoing; Tue, 10 Feb 1998 06:18:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03101 for ; Tue, 10 Feb 1998 06:17:37 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id PAA21167; Tue, 10 Feb 1998 15:13:42 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199802101413.PAA21167@ocean.campus.luth.se> Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <26929.887078004@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 9, 98 06:33:24 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 10 Feb 1998 15:13:42 +0100 (CET) Cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > > i have also noticed a lack of response on any questions to this group > > dealing with this issue. i have previously asked about such support > > and received absolutely no answers in the [recent] past. > > There's no one who currently "owns" MSDOSFS, that's why, and no one to > do the work of integrating changes from NetBSD or any other OS. Any > volunteers? I'm a little confused by all this. Wasn't someone working on a complete rewrite of the msdosfs? One that would be safe to use without making double backups of your system first, and support VFAT? Did that work go in (under my nose), and that's what you want to fix? Or are we trying to add more potential problems to a should-be-killed-off piece of code? :-) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 07:23:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10824 for current-outgoing; Tue, 10 Feb 1998 07:23:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10817 for ; Tue, 10 Feb 1998 07:23:35 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id HAA03519; Tue, 10 Feb 1998 07:23:00 -0800 (PST) To: Mikael Karpberg cc: jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 15:13:42 +0100." <199802101413.PAA21167@ocean.campus.luth.se> Date: Tue, 10 Feb 1998 07:23:00 -0800 Message-ID: <3512.887124180@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm a little confused by all this. Wasn't someone working on a complete > rewrite of the msdosfs? One that would be safe to use without making Robert Nordier. He was called away. :-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 08:40:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24319 for current-outgoing; Tue, 10 Feb 1998 08:40:25 -0800 (PST) (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 IAA24311 for ; Tue, 10 Feb 1998 08:40:19 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA06888 for ; Tue, 10 Feb 1998 16:40:17 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id RAA17357; Tue, 10 Feb 1998 17:40:16 +0100 (MET) Message-ID: <19980210174001.25447@follo.net> Date: Tue, 10 Feb 1998 17:40:01 +0100 From: Eivind Eklund To: current@FreeBSD.ORG Subject: Minor test from somebody with SMP needed Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can somebody test if their system seem to work reliably with the below patch and options SIMPLELOCK_DEBUG in their kernel config file? Alternatively, can somebody that understand the issues say if the change is correct? SIMPLELOCK_DEBUG doesn't work at all with a multiprocessor-system as it is; the kernel won't even link, and this breaks LINT. Index: kern/kern_lock.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_lock.c,v retrieving revision 1.16 diff -u -r1.16 kern_lock.c --- kern_lock.c 1998/02/06 12:13:23 1.16 +++ kern_lock.c 1998/02/10 16:35:20 @@ -462,7 +462,7 @@ printf(" with %d pending", lkp->lk_waitcount); } -#if defined(SIMPLELOCK_DEBUG) && NCPUS == 1 +#if defined(SIMPLELOCK_DEBUG) #include #include Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 08:54:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27329 for current-outgoing; Tue, 10 Feb 1998 08:54:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA27317 for ; Tue, 10 Feb 1998 08:54:36 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0y2Ix1-0002hK-00; Tue, 10 Feb 1998 09:54:27 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id JAA14179; Tue, 10 Feb 1998 09:54:41 -0700 (MST) Message-Id: <199802101654.JAA14179@harmony.village.org> To: Eivind Eklund Subject: Re: merging win95 and nt filesystem changes into msdosfs Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 10 Feb 1998 13:43:34 +0100." <19980210134334.60912@follo.net> References: <19980210134334.60912@follo.net> <199802101022.DAA25240@usr05.primenet.com> <15304.887108650@time.cdrom.com> Date: Tue, 10 Feb 1998 09:54:41 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980210134334.60912@follo.net> Eivind Eklund writes: : I'm willing to try. I've been toying with just running some of Terrys : patches here and see if they're stable, attempting to test the areas they : touch, and then just commit them and take the blame (if any). I'm just not : quite certain how hard that blame is going to be, and I would dislike : loosing my commit privileges :-( Commiting bogus changes won't get your commit privs yanked if you are willing and able to fix the problems that come up, or at least back them out if they break the world and you don't know how to unbreak the world. At least that's what I've seen to date. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 09:12:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00941 for current-outgoing; Tue, 10 Feb 1998 09:12:13 -0800 (PST) (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 JAA00927 for ; Tue, 10 Feb 1998 09:12:02 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id KAA23233; Tue, 10 Feb 1998 10:11:51 -0700 (MST) Message-Id: <199802101711.KAA23233@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Eivind Eklund cc: current@FreeBSD.ORG Subject: Re: Minor test from somebody with SMP needed In-reply-to: Your message of "Tue, 10 Feb 1998 17:40:01 +0100." <19980210174001.25447@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 1998 10:11:51 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Can somebody test if their system seem to work reliably with the below > patch and > > options SIMPLELOCK_DEBUG > > in their kernel config file? Alternatively, can somebody that > understand the issues say if the change is correct? > > SIMPLELOCK_DEBUG doesn't work at all with a multiprocessor-system as > it is; the kernel won't even link, and this breaks LINT. These routines can't work with SMP as they substitute for real locks and an SMP machine would soon go down in flames if it depended on them. They are a debug mechanism for a single CPU system, and predate the FreeBSD developmnent effort. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 09:21:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03314 for current-outgoing; Tue, 10 Feb 1998 09:21:34 -0800 (PST) (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 JAA03260 for ; Tue, 10 Feb 1998 09:21:31 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id RAA07786; Tue, 10 Feb 1998 17:21:25 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id SAA18433; Tue, 10 Feb 1998 18:21:24 +0100 (MET) Message-ID: <19980210182124.35246@follo.net> Date: Tue, 10 Feb 1998 18:21:24 +0100 From: Eivind Eklund To: Steve Passe Cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: Minor test from somebody with SMP needed References: <19980210174001.25447@follo.net> <199802101711.KAA23233@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199802101711.KAA23233@Ilsa.StevesCafe.com>; from Steve Passe on Tue, Feb 10, 1998 at 10:11:51AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 10, 1998 at 10:11:51AM -0700, Steve Passe wrote: > Hi, > > > Can somebody test if their system seem to work reliably with the below > > patch and > > > > options SIMPLELOCK_DEBUG > > > > in their kernel config file? Alternatively, can somebody that > > understand the issues say if the change is correct? > > > > SIMPLELOCK_DEBUG doesn't work at all with a multiprocessor-system as > > it is; the kernel won't even link, and this breaks LINT. > > These routines can't work with SMP as they substitute for real locks > and an SMP machine would soon go down in flames if it depended on them. > They are a debug mechanism for a single CPU system, and predate the > FreeBSD developmnent effort. OK, what is the right fix, then? I can see three obvious 'fixes' for the time being: 1. Make SIMPLELOCK_DEBUG a no-op if NCPUS > 1 2. Rip out the SIMPLELOCK_DEBUG code (if it is no longer usable, and not likely to become usable) 3. Do the below change (basically an error if compiling anything other than LINT with SIMPLELOCK_DEBUG and SMP) Index: kern_lock.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_lock.c,v retrieving revision 1.16 diff -u -r1.16 kern_lock.c --- kern_lock.c 1998/02/06 12:13:23 1.16 +++ kern_lock.c 1998/02/10 17:20:08 @@ -462,7 +462,7 @@ printf(" with %d pending", lkp->lk_waitcount); } -#if defined(SIMPLELOCK_DEBUG) && NCPUS == 1 +#if defined(SIMPLELOCK_DEBUG) && (NCPUS == 1 || defined(COMPILING_LINT)) #include #include @@ -555,4 +555,6 @@ if (curproc) curproc->p_simple_locks--; } +#elif defined(SIMPLELOCK_DEBUG) +#error "SIMPLELOCK_DEBUG is not compatible with SMP!" #endif /* SIMPLELOCK_DEBUG && NCPUS == 1 */ Just help me determine what is right, and I'll do the work. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 09:45:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08943 for current-outgoing; Tue, 10 Feb 1998 09:45:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08934 for ; Tue, 10 Feb 1998 09:45:20 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA16027; Wed, 11 Feb 1998 04:42:20 +1100 Date: Wed, 11 Feb 1998 04:42:20 +1100 From: Bruce Evans Message-Id: <199802101742.EAA16027@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: cvs commit: src/bin/sh jobs.c Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The patch below makes sh pass all my tests. In addition to the last >... >*************** >*** 575,580 **** >--- 578,593 ---- > mode)); > INTOFF; >+ if (mode == FORK_FG) { Add ` || mode == FORK_NOJOB' >*************** >*** 587,590 **** >--- 600,607 ---- > > TRACE(("Child shell %d\n", getpid())); >+ if (oldsigquit != SIG_IGN) >+ signal(SIGQUIT,SIG_DFL); >+ if (oldsigint != SIG_IGN) >+ signal(SIGINT,SIG_DFL); Add `if (oldsigs_valid) ... I checked an old draft of POSIX.2. The main points about signal handling seem to be: 1. For async commands, SIGINT and SIGQUIT from the keyboard shall be prevented from interrupting the command. Otherwise, signal handling shall be inherited from the shell's parent. Notes. This seems to require SIGINT and SIGQUIT not from the keyboard to not be handled specially. (How can the shell tell whether stdin is connected to _the_ keyboard? ;-). This doesn't specify handling of signals by the shell itself. 2. If the shell is waiting for a forground command, and a signal with a trap handler is received, then "the trap shall not be executed until after the foreground command has been completed". Notes. Presumably, trapped signals are supposed to be received and not just ignored while waiting for a command. Your change breaks this in most cases, since the shell ignores SIGINT and SIGQUIT while waiting. The SIGINT case still works, accidentally, when the foreground command is killed by a SIGINT. Then the shell forwards the signal to itself after it restores its signal catcher. This can probably be fixed by replacing the signal(..., SIG_IGN)'s by a sigprocmask(SIG_BLOCK, ...), etc. Signals will be delayed until they are unblocked after the command completes, but this is precisely what is wanted. Traps are also handled strangely in interactive shells when the shell is not waiting for a command. They are not executed until the next command completes. 3. If the shell is waiting (via the wait command) for a background command, then the wait command shall exit immediately on receipt of a signal, and then the trap shall be executed. Notes. This is very broken in all versions of sh. Both the command and the wait builtin seem to ignore all keyboard signals. It works in bash. 4. For subshells, traps caught by the shell shall be set to the default values and traps ignored by the shell shall be ignored by the command. Notes. "the default values" doesn't seem to be specified. It presumably means that the corresponding signals are set to SIG_DFL. The initial state of trap handlers doesn't seem to be specified anywhere. I think this means that sh's handling of signals is already correct, but bash's. handling of subshells is incorrect. If you want to set the signal handling portably, then you must use `trap'. This makes sense, since changing from from SIG_DFL to SIG_IGN is easy, while changing from SIG_IGN to SIG_DFL is impossible (the best you can do is attempt to kill the shell from the trap handler) and wrong if anything except the shell set SIG_IGN. Examples (where catchint exits normally when killed by SIGINT): (a) while :; do catchint; done # interactive The shell may be killed by a SIGINT. To ensure the usual handling, you must use "trap '' SIGINT". It is not an error for the shell to ignore SIGINT. (?) (b) #!/bin/sh while :; do catchint; done Same as (a). "the default values" in for the trap handlers are not specified to be different for interactive shells. (?) (c) #!/bin/sh (while :; do catchint; done) Now there is a subshell. It must be killed by SIGINT. (?) (PR1206) /bin/sh -c "trap '' SIGINT; emacs" The command must be written something like this to ensure ignoring of SIGINT. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 09:47:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09176 for current-outgoing; Tue, 10 Feb 1998 09:47:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09166 for ; Tue, 10 Feb 1998 09:47:04 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id PAA12461; Tue, 10 Feb 1998 15:45:02 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199802101745.PAA12461@gaia.coppe.ufrj.br> Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <199802101042.DAA25601@usr05.primenet.com> from Terry Lambert at "Feb 10, 98 10:42:40 am" To: tlambert@primenet.com (Terry Lambert) Date: Tue, 10 Feb 1998 15:45:02 -0200 (EDT) Cc: dima@tejblum.dnttm.rssi.ru, tlambert@primenet.com, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Terry Lambert) // > Well, I don't use 4DOS, and believed that created long file names are ok. // > Scandisk doesn't report any problems also. How 4DOS can have problems? // > Doesn't it use standard DOS or Windows syscalls? // // It uses DOs calls to get the directory, then goes back and uses Win95 // calls to get the long name from the short name. // // The problem is that the same algorithm *must* be used for this to work // reliably. I suppose that by algorithm you mean how the filenames are archived, and not how the names are converted between formats. If it the second option, let me remember you that Win95 registry can be programmed to change the algorithm. I hate those ~'s in file names. :) // I did effectively this when I converted FFS/UFS for Windows 95 IFS, and // added a Unicode name space and 8.3 names for FFS/UFS directory entries; // the problems I faced are exactly the inverse of the problems you face. You mean you have a FFS driver for Win95 ? Is it available ? :) Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 09:52:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10547 for current-outgoing; Tue, 10 Feb 1998 09:52:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10542 for ; Tue, 10 Feb 1998 09:52:25 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA23953; Tue, 10 Feb 1998 10:52:16 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA25116; Tue, 10 Feb 1998 10:52:14 -0700 Date: Tue, 10 Feb 1998 10:52:14 -0700 Message-Id: <199802101752.KAA25116@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Terry Lambert , jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <15304.887108650@time.cdrom.com> References: <199802101022.DAA25240@usr05.primenet.com> <15304.887108650@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Well, I think Poul has honestly done a lot of work in this area, and > > I've done most of the rest of the work, if only people would take the > > code without insisting on understanding how it works, so long as it > > It's not "people" who need to take this code, however. What's needed > is "a person" (possibly more than one, but that's neither here nor > there) who's also wearing a committer hat and is willing to front this > for you in -current. Find yourself that person to stand behind and > understand that no matter what you might personally be willing to > promise, it's still HE who's going to be held most principally > responsible for it since his fingerprints will be the ones directly on > the repository and so should thus have at least some *hope* of > understanding your code, at least. I was/am willing to do this, but at a price that Terry is intimately familiar with, yet he has refused to pay. IMHO, until he is willing to educate me to a certain amount, then I'm unwilling to commit his code. He claimed to be willing, but when things started hitting the fan (rubber meets the road, push came to shove) nothing of any consequence happened. This was almost 5 months ago. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 11:33:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27747 for current-outgoing; Tue, 10 Feb 1998 11:33:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eac.iafrica.com (196-31-98-138.iafrica.com [196.31.98.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27503 for ; Tue, 10 Feb 1998 11:32:44 -0800 (PST) (envelope-from rnordier@iafrica.com) Received: (from rnordier@localhost) by eac.iafrica.com (8.8.7/8.6.12) id VAA19576; Tue, 10 Feb 1998 21:29:07 +0200 (SAT) From: Robert Nordier Message-Id: <199802101929.VAA19576@eac.iafrica.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <3512.887124180@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 10, 98 07:23:00 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 10 Feb 1998 21:29:00 +0200 (SAT) Cc: karpen@ocean.campus.luth.se, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > I'm a little confused by all this. Wasn't someone working on a complete > > rewrite of the msdosfs? One that would be safe to use without making > > Robert Nordier. He was called away. :-) Actually, I'm back. :-) (Having just come off two projects that together have taken most of the days/nights for the last eighteen months.) Adding Windows support to the existing msdosfs is a reasonable move that I've always been in favor of someone doing. And if/when I get my own code finished, there's probably no reason why there shouldn't be more than one dosfs available (as with pppd and iijppp). My own immediate plans, though, in the next couple of weeks, are to release a dosfs-checking tool `ckfatfs', which will probably be useful, given the work on msdosfs. The checking by ckfatfs is comprehensive and extremely rigorous. Conceptually, it's more like an FS lint, and less like the fsck-style "fixing" programs (which actually do fairly limited overall checking). This should probably serve as a useful confidence/diagnostic tool in conjunction with revisions to the msdosfs. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 11:36:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28834 for current-outgoing; Tue, 10 Feb 1998 11:36:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28815 for ; Tue, 10 Feb 1998 11:36:36 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id UAA00178; Tue, 10 Feb 1998 20:38:08 +0100 (CET) Message-ID: <19980210203807.25569@cons.org> Date: Tue, 10 Feb 1998 20:38:07 +0100 From: Martin Cracauer To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/bin/sh jobs.c References: <199802101742.EAA16027@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199802101742.EAA16027@godzilla.zeta.org.au>; from Bruce Evans on Wed, Feb 11, 1998 at 04:42:20AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199802101742.EAA16027@godzilla.zeta.org.au>, Bruce Evans wrote: [edited my patch as you requested] > I checked an old draft of POSIX.2. The main points about signal handling > seem to be: > > 1. For async commands, SIGINT and SIGQUIT from the keyboard shall be > prevented from interrupting the command. Otherwise, signal handling > shall be inherited from the shell's parent. > > Notes. This seems to require SIGINT and SIGQUIT not from the keyboard > to not be handled specially. (How can the shell tell whether stdin is > connected to _the_ keyboard? ;-). This doesn't specify handling of > signals by the shell itself. I'll try to get ahold of a newer POSIX document, maybe they became more specific. > 2. If the shell is waiting for a forground command, and a signal with a > trap handler is received, then "the trap shall not be executed until > after the foreground command has been completed". > > Notes. Presumably, trapped signals are supposed to be received and not > just ignored while waiting for a command. Your change breaks this in > most cases, since the shell ignores SIGINT and SIGQUIT while waiting. I agree that this is probably intended, but I'm not sure this is the right thing to do. Suppose I have $EDITOR set to a script like this: #!/bin/sh emacs -nw "$@" somecleanup or an application calls system("emacs -nw ; somecleanup-in-shell") The cleanup will not be run when the user uses SIGINT/SIGQUIT in emacs, but it will be run when the user exits emacs without using these signals. In my opinion, if the user uses an application that uses SIGINT and SIGQUIT for its own purposes (that means, using these signals is part of normal program usage like any other keystroke is), then the surrounding shell should not take any action based on the signals. No matter if it is done synchonously or after the childs exits. The script above should run the cleanup in any case. Also, I would like to avoid waking up the shell everytime a signal arrives. /bin/csh behaves as you describe, BTW. I added a test for this to my suite. > The SIGINT case still works, accidentally, when the foreground command > is killed by a SIGINT. Then the shell forwards the signal to itself > after it restores its signal catcher. This can probably be fixed > by replacing the signal(..., SIG_IGN)'s by a sigprocmask(SIG_BLOCK, > ...), etc. Signals will be delayed until they are unblocked after the > command completes, but this is precisely what is wanted. Hm, unless I'm convinced otherwise, this isn't what I want. It's fine in the case that the child is killed by (did not catch) the signal, though. As you said, my version accidentally does exactly what I want for both bases. I'll answer the other points later, got to drive home now. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer cracauer@wavehh.hanse.de (batched, preferred for large mails) Tel.: (daytime) +4940 41478712 Fax.: (daytime) +4940 41478715 Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 11:55:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02467 for current-outgoing; Tue, 10 Feb 1998 11:55:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02462 for ; Tue, 10 Feb 1998 11:55:44 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id MAA12145; Tue, 10 Feb 1998 12:55:43 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd012121; Tue Feb 10 12:55:41 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id MAA01977; Tue, 10 Feb 1998 12:55:38 -0700 (MST) From: Terry Lambert Message-Id: <199802101955.MAA01977@usr04.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 10 Feb 1998 19:55:38 +0000 (GMT) Cc: tlambert@primenet.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <15304.887108650@time.cdrom.com> from "Jordan K. Hubbard" at Feb 10, 98 03:04:10 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > least. Any random committer won't do or I > might be even willing to do it myself, if only to see what your next > move was. :-) However, I'm not a FS dude and never pretended to be so > it's gotta be one of those other 107 committers who play in /sys more > often than I do. Find one, work the change through him, do it just > like all the other "complete strangers" out there have done it and it > will be done. :-) Are there any "FS dudes" with commit priviledges out there? (Hey! Why haven't you been fixing these same problems? 8-)). I think this is the problem Jordan. FreeBSD doesn't have any FS dudes (being defined as people who *live* FS code, like McKusick, Heidimann, or, in fact, me [No, I'm not comparing myself to them]). Any "FS dabblers" out there who whould be willing to type a one line CVS command to revert the archive if I step on any feet? 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 12:03:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03994 for current-outgoing; Tue, 10 Feb 1998 12:03:21 -0800 (PST) (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 MAA03985 for ; Tue, 10 Feb 1998 12:03:18 -0800 (PST) (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 MAA02411; Tue, 10 Feb 1998 12:01:27 -0800 (PST) Message-Id: <199802102001.MAA02411@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Dmitrij Tejblum cc: Mike Smith , jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 13:20:58 +0300." <199802101020.NAA02985@tejblum.dnttm.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Feb 1998 12:01:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > > > I should also point out that there is another diff, msdosfs-vfat.diff, in > > > incoming. This diff is for 2.2. It is original and independent work of > > > Luoqi Chen. It is not supposed to support FAT32. May be, now Luoqi did some > > > further development of his work. > > > > I think that this is where things hit a logjam last time; there are two > > sets of incompatible patches to achieve two desirable things. > > *Two* desirable things? That is, VFAT for 2.2 and VFAT for -current? Or what > do you mean? My understanding was that one set of patches provided long filename support, and the other gave fat32 support. What we want is *both* of these. If I am misremembering things, please accept my apologies. Under no circumstances did I mean to imply that your work was unwanted. -- \\ 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 12:10:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05556 for current-outgoing; Tue, 10 Feb 1998 12:10:53 -0800 (PST) (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 MAA05545 for ; Tue, 10 Feb 1998 12:10:48 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.7/8.8.7) id HAA05415; Wed, 11 Feb 1998 07:16:10 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199802102016.HAA05415@cimlogic.com.au> Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <199802101955.MAA01977@usr04.primenet.com> from Terry Lambert at "Feb 10, 98 07:55:38 pm" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 11 Feb 1998 07:16:10 +1100 (EST) Cc: jkh@time.cdrom.com, tlambert@primenet.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > Are there any "FS dudes" with commit priviledges out there? (Hey! > Why haven't you been fixing these same problems? 8-)). > > I think this is the problem Jordan. FreeBSD doesn't have any FS dudes > (being defined as people who *live* FS code, like McKusick, Heidimann, > or, in fact, me [No, I'm not comparing myself to them]). What is the problem with you having commit priviledges? -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 12:50:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11368 for current-outgoing; Tue, 10 Feb 1998 12:50:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11362 for ; Tue, 10 Feb 1998 12:50:55 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id HAA21731; Wed, 11 Feb 1998 07:46:22 +1100 Date: Wed, 11 Feb 1998 07:46:22 +1100 From: Bruce Evans Message-Id: <199802102046.HAA21731@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: cvs commit: src/bin/sh jobs.c Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In my opinion, if the user uses an application that uses SIGINT and >SIGQUIT for its own purposes (that means, using these signals is part >of normal program usage like any other keystroke is), then the >surrounding shell should not take any action based on the signals. No >matter if it is done synchonously or after the childs exits. The >script above should run the cleanup in any case. Apparently, this is supposed to be programmed into the surrounding shell script. >Also, I would like to avoid waking up the shell everytime a signal >arrives. This would be a pessimization according to sh's philosophy. I first objected to your version because I remembered that it goes to some trouble to get woken up at inconvenient time because this is considered better than fiddling with signals. Here is a comment about this. /* * These macros allow the user to suspend the handling of interrupt signals * over a period of time. This is similar to SIGHOLD to or sigblock, but * much more efficient and portable. (But hacking the kernel is so much * more fun than worrying about efficiency and portability. :-)) */ >/bin/csh behaves as you describe, BTW. I added a test for this to my suite. > >> The SIGINT case still works, accidentally, when the foreground command >> is killed by a SIGINT. Then the shell forwards the signal to itself >> after it restores its signal catcher. This can probably be fixed >> by replacing the signal(..., SIG_IGN)'s by a sigprocmask(SIG_BLOCK, >> ...), etc. Signals will be delayed until they are unblocked after the >> command completes, but this is precisely what is wanted. > >Hm, unless I'm convinced otherwise, this isn't what I want. It's fine >in the case that the child is killed by (did not catch) the signal, >though. It's also fine (and required) when the shell is trapping the signal - the trap handler will be reinstalled before the signal is delivered. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 12:56:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12408 for current-outgoing; Tue, 10 Feb 1998 12:56:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nike.ins.cwru.edu (chet@nike.INS.CWRU.Edu [129.22.8.219]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12134 for ; Tue, 10 Feb 1998 12:55:28 -0800 (PST) (envelope-from chet@nike.ins.cwru.edu) Received: (chet@localhost) by nike.ins.cwru.edu (8.8.7/CWRU-2.5-bsdi) id PAA17032; Tue, 10 Feb 1998 15:54:25 -0500 (EST) (from chet) Date: Tue, 10 Feb 1998 15:51:30 -0500 From: Chet Ramey To: bde@zeta.org.au Subject: Re: cvs commit: src/bin/sh jobs.c Cc: cracauer@cons.org, freebsd-current@FreeBSD.ORG, chet@po.cwru.edu Reply-To: chet@po.cwru.edu In-Reply-To: Message from bde@zeta.org.au of Wed, 11 Feb 1998 04:42:20 +1100 (id <199802101742.EAA16027@godzilla.zeta.org.au>) Message-ID: <980210205130.AA17028.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 4. For subshells, traps caught by the shell shall be set to the default > values and traps ignored by the shell shall be ignored by the command. > > Notes. "the default values" doesn't seem to be specified. It presumably > means that the corresponding signals are set to SIG_DFL. The initial > state of trap handlers doesn't seem to be specified anywhere. I disagree. I believe that it means the values of signal handlers inherited from the shells' parent. That is the `initial state of trap handlers'. If a user starts a shell with some signal ignored, he has every right to expect that all processes begun from that shell will have that signal ignored. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 13:33:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18640 for current-outgoing; Tue, 10 Feb 1998 13:33:05 -0800 (PST) (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 NAA18623 for ; Tue, 10 Feb 1998 13:32:59 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA09318; Tue, 10 Feb 1998 13:32:38 -0800 (PST) Message-Id: <199802102132.NAA09318@implode.root.com> To: John Birrell cc: tlambert@primenet.com (Terry Lambert), jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Wed, 11 Feb 1998 07:16:10 +1100." <199802102016.HAA05415@cimlogic.com.au> From: David Greenman Reply-To: dg@root.com Date: Tue, 10 Feb 1998 13:32:38 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Terry Lambert wrote: >> Are there any "FS dudes" with commit priviledges out there? (Hey! >> Why haven't you been fixing these same problems? 8-)). >> >> I think this is the problem Jordan. FreeBSD doesn't have any FS dudes >> (being defined as people who *live* FS code, like McKusick, Heidimann, >> or, in fact, me [No, I'm not comparing myself to them]). > >What is the problem with you having commit priviledges? In many cases, Terry's solutions to the problems that he is trying to solve aren't the ones we want to adopt. There are far more instances where Kirk McKusick and other people in-the-know have objected to the direction that Terry wants to take us than there are in favor. Terry's unwillingness to carefully explain/justify the changes that he proposes in a manor that reasonable kernel developers can understand has further resulted in a serious lack of trust. For these reasons it's the unanimous opinion of the core team that Terry not be given commit privileges. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 14:00:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23758 for current-outgoing; Tue, 10 Feb 1998 14:00:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23737 for ; Tue, 10 Feb 1998 14:00:08 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id XAA00479; Tue, 10 Feb 1998 23:01:29 +0100 (CET) Message-ID: <19980210230129.52530@cons.org> Date: Tue, 10 Feb 1998 23:01:29 +0100 From: Martin Cracauer To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/bin/sh jobs.c References: <199802101742.EAA16027@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199802101742.EAA16027@godzilla.zeta.org.au>; from Bruce Evans on Wed, Feb 11, 1998 at 04:42:20AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [continuing my last mail] > 3. If the shell is waiting (via the wait command) for a background > command, then the wait command shall exit immediately on receipt of > a signal, and then the trap shall be executed. > > Notes. This is very broken in all versions of sh. Both the command > and the wait builtin seem to ignore all keyboard signals. It works > in bash. They ignore the signals only when handlers are installed. I added this to the tests and see if I can fix this. This is one reason more why I wouldn't like a solution that forces a user to trap a signal in a script where he uses a signal-catching program like emacs. i.e.: #!/bin/sh trap '' 2 trap '' 3 emacs -nw cleanup where he can't be sure to get his cleanup done without the traps. I don't want this anyway, but if the wait comman dis broken in this case, it is even worse. > 4. For subshells, traps caught by the shell shall be set to the default > values and traps ignored by the shell shall be ignored by the command. > > Notes. "the default values" doesn't seem to be specified. It presumably > means that the corresponding signals are set to SIG_DFL. The initial > state of trap handlers doesn't seem to be specified anywhere. I think > this means that sh's handling of signals is already correct, but bash's. > handling of subshells is incorrect. If you want to set the signal > handling portably, then you must use `trap'. This makes sense, since > changing from from SIG_DFL to SIG_IGN is easy, while changing from SIG_IGN > to SIG_DFL is impossible (the best you can do is attempt to kill the shell > from the trap handler) and wrong if anything except the shell set SIG_IGN. > Examples (where catchint exits normally when killed by SIGINT): > > (a) while :; do catchint; done # interactive > > The shell may be killed by a SIGINT. To ensure the usual handling, you > must use "trap '' SIGINT". It is not an error for the shell to ignore > SIGINT. (?) Sorry, you lost me. Did you mean "The LOOP my be killed by a SIGINT". The interactive shell shouldn't exit, no? If you do do trap '' 2 while :; do catchint; done You'll get completely runaway behaviour, you can't get rid of this loop any way. Even SIGSTOP won't work since it will usually be caught by the catchint process. > (b) #!/bin/sh > while :; do catchint; done > > Same as (a). "the default values" in for the trap handlers are not > specified to be different for interactive shells. (?) > > (c) #!/bin/sh > (while :; do catchint; done) > > Now there is a subshell. It must be killed by SIGINT. (?) For me (our sh and bash), the whole script (outer shell, inner shell, catchint) is terminated on SIGINT. It's the way it should be, IMHO. > (PR1206) /bin/sh -c "trap '' SIGINT; emacs" > > The command must be written something like this to ensure ignoring of > SIGINT. Is this your conclusion from this? > 4. For subshells, traps caught by the shell shall be set to the default > values and traps ignored by the shell shall be ignored by the command. What exactly do they mean by "command"? Does sh -c count as subshell? I think I'll have to sleep over it. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer cracauer@wavehh.hanse.de (batched, preferred for large mails) Tel.: (daytime) +4940 41478712 Fax.: (daytime) +4940 41478715 Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 14:09:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26086 for current-outgoing; Tue, 10 Feb 1998 14:09:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26081 for ; Tue, 10 Feb 1998 14:09:49 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id XAA00559; Tue, 10 Feb 1998 23:11:18 +0100 (CET) Message-ID: <19980210231117.55326@cons.org> Date: Tue, 10 Feb 1998 23:11:17 +0100 From: Martin Cracauer To: chet@po.cwru.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/bin/sh jobs.c References: <19980210203807.25569@cons.org> <980210205735.AA17101.SM@nike.ins.cwru.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <980210205735.AA17101.SM@nike.ins.cwru.edu>; from Chet Ramey on Tue, Feb 10, 1998 at 03:57:35PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <980210205735.AA17101.SM@nike.ins.cwru.edu>, Chet Ramey wrote: > > /bin/csh behaves as you describe, BTW. I added a test for this to my suite. > > Is your test suite available? On Freefall ~cracauer/public_html/testsuite/ Or http://www.freebsd.org/~cracauer/testsuite/ Start reading DOC. Essentially link the shell to test to ./testshell, then start ./test1.sh ... ./test10.sh bde's and my diffs for FreeBSD's /bin/sh are one dir above. Please note that the behaviour I indicated as expected is IMHO! Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer cracauer@wavehh.hanse.de (batched, preferred for large mails) Tel.: (daytime) +4940 41478712 Fax.: (daytime) +4940 41478715 Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 15:36:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11121 for current-outgoing; Tue, 10 Feb 1998 15:36:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11116 for ; Tue, 10 Feb 1998 15:36:47 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA29236; Wed, 11 Feb 1998 10:34:49 +1100 Date: Wed, 11 Feb 1998 10:34:49 +1100 From: Bruce Evans Message-Id: <199802102334.KAA29236@godzilla.zeta.org.au> To: bde@zeta.org.au, chet@nike.ins.cwru.edu Subject: Re: cvs commit: src/bin/sh jobs.c Cc: chet@po.cwru.edu, cracauer@cons.org, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 4. For subshells, traps caught by the shell shall be set to the default >> values and traps ignored by the shell shall be ignored by the command. >> >> Notes. "the default values" doesn't seem to be specified. It presumably >> means that the corresponding signals are set to SIG_DFL. The initial >> state of trap handlers doesn't seem to be specified anywhere. > >I disagree. I believe that it means the values of signal handlers >inherited from the shells' parent. That is the `initial state of >trap handlers'. > >If a user starts a shell with some signal ignored, he has every right >to expect that all processes begun from that shell will have that >signal ignored. I agree. I was only guessing about the "traps caught by the shell" case. Signals ignored when the shell starts can't be caught (as traps). This is specified clearly enough. sh gets this slightly wrong by putting traps for ignored signals in the trap table and letting you see this with the `trap' command. It correctly never executes such traps. bash gets this slightly wrong by catching "ignored" SIGINTs in interactive mode and handling them as usual. I thought that the bug was in readline (it's in the versions of bash-1, bash-2 and gnuplot in the FreeBSD-2.2.5 packages), but at least the current libreadline handles ignored SIGINTs correctly. bash uses a private version of readline but the gnuplot port uses libreadline.so. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 17:11:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23371 for current-outgoing; Tue, 10 Feb 1998 17:11:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23362 for ; Tue, 10 Feb 1998 17:11:31 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA00738; Wed, 11 Feb 1998 12:06:49 +1100 Date: Wed, 11 Feb 1998 12:06:49 +1100 From: Bruce Evans Message-Id: <199802110106.MAA00738@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: cvs commit: src/bin/sh jobs.c Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 3. If the shell is waiting (via the wait command) for a background >> command, then the wait command shall exit immediately on receipt of >> a signal, and then the trap shall be executed. >> >> Notes. This is very broken in all versions of sh. Both the command >> and the wait builtin seem to ignore all keyboard signals. It works >> in bash. >... >This is one reason more why I wouldn't like a solution that forces a >user to trap a signal in a script where he uses a signal-catching >program like emacs. > >i.e.: >#!/bin/sh >trap '' 2 >trap '' 3 >emacs -nw >cleanup > >where he can't be sure to get his cleanup done without the traps. I forgot about this when I removed 'echo -n' from my example for PR1206. Just do nothing in the trap handler instead of ignoring the signal: #!/bin/sh trap 'echo -n' 2 ... emacs -nw cleanup >> 4. For subshells, traps caught by the shell shall be set to the default >> values and traps ignored by the shell shall be ignored by the command. >>/// >> Examples (where catchint exits normally when killed by SIGINT): >> >> (a) while :; do catchint; done # interactive >> >> The shell may be killed by a SIGINT. To ensure the usual handling, you >> must use "trap '' SIGINT". It is not an error for the shell to ignore >> SIGINT. (?) > >Sorry, you lost me. Did you mean "The LOOP my be killed by a >SIGINT". The interactive shell shouldn't exit, no? Apparently, it _may_ be killed. The only relevant point in the spec seems to be: "An interactive shell may reset or catch signals ignored on entry". Non-interactive shells cannot trap or reset such signals. >If you do do > > trap '' 2 > while :; do catchint; done > >You'll get completely runaway behaviour, you can't get rid of this >loop any way. Even SIGSTOP won't work since it will usually be caught >by the catchint process. catchint is only supposed to catch SIGINT. Other signals _may_ kill either the shell or catchint. >> (c) #!/bin/sh >> (while :; do catchint; done) >> >> Now there is a subshell. It must be killed by SIGINT. (?) > >For me (our sh and bash), the whole script (outer shell, inner shell, >catchint) is terminated on SIGINT. It's the way it should be, IMHO. Actually, it doesn't for your version of sh, or bash. At least for your version of sh, the subshell waits for catchint, and then doesn't exit because catchint exits with a normal status. Exit on SIGQUIT is broken (if it is correct :-) even when the the command run by the subshell gets killed, because the subshell waits for the command and completely ignores SIGQUIT. For the original sh, the shells get killed immediately by SIGINT and catchint exits normally; SIGQUIT kills everything immediately. >> (PR1206) /bin/sh -c "trap '' SIGINT; emacs" >> >> The command must be written something like this to ensure ignoring of >> SIGINT. > >Is this your conclusion from this? >> 4. For subshells, traps caught by the shell shall be set to the default >> values and traps ignored by the shell shall be ignored by the command. > >What exactly do they mean by "command"? Does sh -c count as subshell? I abbreviated too much. The above is part of the specification of a "shell execution environment". Subshells give the most important example of such an environment. The spec says "utility" instead of "command" and distinguishes between builtins, shell scripts and other utilities [being executed in the environment]. The above does not apply to buitlins. I think only sourced scripts count here - there is no way to pass shell traps across exec, even if the exec'ed process is /bin/sh or what is normally called a "shell script" (an executable file beginning with #!/bin/sh). A nearby part of the spec says that traps must be mapped to signals in the obvious way (ignore -> SIG_IGN, other -> SIG_DFL) for executing utilities that aren't builtins or scripts. A subshell is a shell created by `()'. sh -c is certainly not a subshell. The main point of the above is that traps are not passed to subshells unless they are ignored. This is all consistent with signal handling across exec (SIG_IGN -> SIG_IGN, other -> SIG_DFL). Traps could be passed to subshells, but presumably aren't because this would make subshells too different from sh -c. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 17:46:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27676 for current-outgoing; Tue, 10 Feb 1998 17:46:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-22.acadiau.ca [131.162.2.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27657; Tue, 10 Feb 1998 17:45:55 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id VAA00742; Tue, 10 Feb 1998 21:45:18 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 10 Feb 1998 21:45:12 -0400 (AST) From: The Hermit Hacker To: freebsd-multimedia@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Soundblaster 16 4.16 configuration 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 Evening... A friend and I just spent the past several hours going through the mailing lists at www.freebsd.org, newsgroups and whatever README files we could find, and can't seem to get this thing to work...so now I ask here. I just picked up a Soundblaster card for my machine, and altho I think its configured correctly, and FreeBSD appears to recognize it, I can't appear to do anything with it. dmesg shows: Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 vga0: rev 0x00 on pci0.12.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A lpt0 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, dma, iordy wcd0: 687Kb/sec, 240Kb cache, audio play, 2 volume levels, ejectable tray wcd0: 120mm data disc loaded, unlocked npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 10 drq 1 on isa snd0: sbxvi0 at ? drq 6 on isa snd0: opl0 at 0x388 on isa snd0: Intel Pentium F00F detected, installing workaround But, if I try to use something like 'splay' to play an mp3 file, I get: Sound: DMA (output) timed out - IRQ/DRQ config error? My first "concern" is that the sbxvi0 line above shows "at ? ..", which I don't know if its important or not... My kernel config looks like: machine "i386" cpu "I586_CPU" ident thelab maxusers 32 options USER_LDT options SYSVSHM options SYSVSEM options SYSVMSG options "CD9660" #ISO 9660 Filesystem options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #InterNETworking options FFS #Berkeley Fast Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options KTRACE options "AUTO_EOI_1" config kernel root on wd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr # Controls all sound devices controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device awe0 at isa? port 0x620 device opl0 at isa? port 0x388 device mpu0 at isa? port 0x330 irq 6 drq 0 pseudo-device loop pseudo-device ether pseudo-device tun 1 pseudo-device pty 16 pseudo-device bpfilter 1 #Berkeley packet filter And, I sent through the 'kernel -c' interface to change sb0 to irq 10 instead of 5, because of the conflict with sio2 ... Is there something really simple I'm missing here? The kernel source is from ~Jan20, 1998... My friend, having more experience with Linux, asked if we had a pnpprobe utility...something that would list all the irq's and such being used...do we have something like that? Thanks for any help... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 19:06:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14121 for current-outgoing; Tue, 10 Feb 1998 19:06:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-38.acadiau.ca [131.162.2.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14033; Tue, 10 Feb 1998 19:06:00 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id XAA01936; Tue, 10 Feb 1998 23:05:45 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 10 Feb 1998 23:05:45 -0400 (AST) From: The Hermit Hacker To: freebsd-multimedia@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Re: Soundblaster 16 4.16 configuration 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 Found it. After further investigations (and finding pnpinfo), we determined that altho the kernel was configured for sb0 on IRQ 10, the card itself was "stuck" on IRQ 5, so it was conflicting with my modem... moved the modem to IRQ7, and now it works... Sorry for bothering... :( On Tue, 10 Feb 1998, The Hermit Hacker wrote: > > Evening... > > A friend and I just spent the past several hours going through the > mailing lists at www.freebsd.org, newsgroups and whatever README files we > could find, and can't seem to get this thing to work...so now I ask here. > > I just picked up a Soundblaster card for my machine, and altho I > think its configured correctly, and FreeBSD appears to recognize it, I > can't appear to do anything with it. > > dmesg shows: > > Probing for devices on PCI bus 0: > chip0: rev 0x03 on pci0.0.0 > chip1: rev 0x01 on pci0.7.0 > ide_pci0: rev 0x00 on pci0.7.1 > vga0: rev 0x00 on pci0.12.0 > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: VGA color <16 virtual consoles, flags=0x0> > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > sio2 at 0x3e8-0x3ef irq 5 on isa > sio2: type 16550A > lpt0 not found > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: unit 1 (atapi): , removable, dma, iordy > wcd0: 687Kb/sec, 240Kb cache, audio play, 2 volume levels, ejectable tray > wcd0: 120mm data disc loaded, unlocked > npx0 on motherboard > npx0: INT 16 interface > sb0 at 0x220 irq 10 drq 1 on isa > snd0: > sbxvi0 at ? drq 6 on isa > snd0: > opl0 at 0x388 on isa > snd0: > Intel Pentium F00F detected, installing workaround > > But, if I try to use something like 'splay' to play an mp3 file, I get: > > Sound: DMA (output) timed out - IRQ/DRQ config error? > > My first "concern" is that the sbxvi0 line above shows "at ? ..", which I > don't know if its important or not... > > My kernel config looks like: > > machine "i386" > cpu "I586_CPU" > ident thelab > maxusers 32 > > options USER_LDT > options SYSVSHM > options SYSVSEM > options SYSVMSG > options "CD9660" #ISO 9660 Filesystem > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options PROCFS #Process filesystem > options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] > options KTRACE > options "AUTO_EOI_1" > > config kernel root on wd0 > > controller isa0 > controller pci0 > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr > disk fd0 at fdc0 drive 0 > > options "CMD640" # work around CMD640 chip deficiency > controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr > disk wd0 at wdc0 drive 0 > disk wd1 at wdc0 drive 1 > > options ATAPI #Enable ATAPI support for IDE bus > options ATAPI_STATIC #Don't do it as an LKM > device wcd0 #IDE CD-ROM > > device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr > > device npx0 at isa? port "IO_NPX" irq 13 vector npxintr > > device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4 vector siointr > device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr > device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr > > device lpt0 at isa? port? tty irq 7 vector lptintr > > # Controls all sound devices > controller snd0 > device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr > device sbxvi0 at isa? drq 5 > device sbmidi0 at isa? port 0x330 > device awe0 at isa? port 0x620 > device opl0 at isa? port 0x388 > device mpu0 at isa? port 0x330 irq 6 drq 0 > > pseudo-device loop > pseudo-device ether > pseudo-device tun 1 > pseudo-device pty 16 > pseudo-device bpfilter 1 #Berkeley packet filter > > > And, I sent through the 'kernel -c' interface to change sb0 to irq 10 > instead of 5, because of the conflict with sio2 ... > > Is there something really simple I'm missing here? The kernel source is > from ~Jan20, 1998... > > My friend, having more experience with Linux, asked if we had a pnpprobe > utility...something that would list all the irq's and such being used...do > we have something like that? > > Thanks for any help... > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe current" in the body of the message > 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 19:15:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16838 for current-outgoing; Tue, 10 Feb 1998 19:15:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16805 for ; Tue, 10 Feb 1998 19:15:30 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id UAA04192; Tue, 10 Feb 1998 20:15:27 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd004148; Tue Feb 10 20:15:21 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA00548; Tue, 10 Feb 1998 20:15:16 -0700 (MST) From: Terry Lambert Message-Id: <199802110315.UAA00548@usr04.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: dg@root.com Date: Wed, 11 Feb 1998 03:15:15 +0000 (GMT) Cc: jb@cimlogic.com.au, tlambert@primenet.com, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199802102132.NAA09318@implode.root.com> from "David Greenman" at Feb 10, 98 01:32:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In many cases, Terry's solutions to the problems that he is trying to > solve aren't the ones we want to adopt. The standard reasoning against this was: 1) Don't want divergence from NetBSD 2) Don't want divergence from 4.4-Lite because of 4.4-Lite2 3) Don't want to integrate 4.4-Lite2 yet (code languished 1.5 years after Lite2 release before FreeBSD integration) 4) Existing committers must understand everything that non-committers want committed. > There are far more instances where Kirk McKusick and other people > in-the-know have objected to the direction that Terry wants to take > us than there are in favor. I've talked to Kirk about many of the changes since I've been in the Bay Area, and you are misquoting him here. He has agreed that a number of the layering issues I have been harping on since day one are, in fact, legitimate problems. I've also talked to John Heidemann, who architected the FS stacking code in the first place, and he agrees that there are problems with the 4.4 integration of his source code, which he donated from the Ficus project. > Terry's unwillingness to carefully explain/justify the changes that > he proposes in a manor that reasonable kernel developers can > understand has further resulted in a serious lack of trust. For > these reasons it's the unanimous opinion of the core team that > Terry not be given commit privileges. Not to mention that I've never asked for them, and when I was initially offered them badk in 1994, I declined on the basis that, as a USL employee at the time, I would potentially be a legal liability to the project that USL could use to claim contamination by way of FreeBSD use of USL intellectual property. I'll be happy to explain anything you have questions about. As far as justification goes, well, "reasonable kernel hackers" aren't terribly interested in FS code, except when someone else goes to do something to it, then they get incredibly interested. Otherwise there would be more "resonable kernel hackers" actually writing FS code. It's also a bit hard to justify "commit this so I can better do research on what I think should be done next so I can answer your questions about 'what should be done next?'". 8-). It's strange that commits that seem to be diddles to other people are not allowed: if they have no effect they can perceive, then they certainly have no harm, either. Harm requires effect to occur. The only rationale against these has been "we fear change, specifically in the form of divergence". Now that that's blown out, so long as it's possible to revert such changes if they are seen to have a detrimental effect, I don't see why there's a problem. 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 19:43:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26502 for current-outgoing; Tue, 10 Feb 1998 19:43:01 -0800 (PST) (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 TAA26482 for ; Tue, 10 Feb 1998 19:42:50 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id UAA03699; Tue, 10 Feb 1998 20:42:47 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd003660; Tue Feb 10 20:42:37 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA01926; Tue, 10 Feb 1998 20:42:31 -0700 (MST) From: Terry Lambert Message-Id: <199802110342.UAA01926@usr04.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Wed, 11 Feb 1998 03:42:31 +0000 (GMT) Cc: jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199802101413.PAA21167@ocean.campus.luth.se> from "Mikael Karpberg" at Feb 10, 98 03:13:42 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 > > There's no one who currently "owns" MSDOSFS, that's why, and no one to > > do the work of integrating changes from NetBSD or any other OS. Any > > volunteers? > > I'm a little confused by all this. Wasn't someone working on a complete > rewrite of the msdosfs? One that would be safe to use without making > double backups of your system first, and support VFAT? Did that work > go in (under my nose), and that's what you want to fix? Or are we trying > to add more potential problems to a should-be-killed-off piece of code? :-) Robert Nordier. 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 19:45:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27435 for current-outgoing; Tue, 10 Feb 1998 19:45:49 -0800 (PST) (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 TAA27429 for ; Tue, 10 Feb 1998 19:45:45 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id UAA26430; Tue, 10 Feb 1998 20:45:39 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp02.primenet.com, id smtpd026412; Tue Feb 10 20:45:34 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA02149; Tue, 10 Feb 1998 20:45:31 -0700 (MST) From: Terry Lambert Message-Id: <199802110345.UAA02149@usr04.primenet.com> Subject: Re: Minor test from somebody with SMP needed To: eivind@yes.no (Eivind Eklund) Date: Wed, 11 Feb 1998 03:45:31 +0000 (GMT) Cc: smp@csn.net, eivind@yes.no, current@FreeBSD.ORG In-Reply-To: <19980210182124.35246@follo.net> from "Eivind Eklund" at Feb 10, 98 06:21:24 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 > > These routines can't work with SMP as they substitute for real locks > > and an SMP machine would soon go down in flames if it depended on them. > > They are a debug mechanism for a single CPU system, and predate the > > FreeBSD developmnent effort. > > OK, what is the right fix, then? I can see three obvious 'fixes' for > the time being: > > 1. Make SIMPLELOCK_DEBUG a no-op if NCPUS > 1 > > 2. Rip out the SIMPLELOCK_DEBUG code (if it is no longer usable, and > not likely to become usable) > > 3. Do the below change (basically an error if compiling anything other > than LINT with SIMPLELOCK_DEBUG and SMP) They need to be real locks. The reason they need to be real locks is that if kernel preemption is to be allowed in kernel threading, then there may be a case they need to lock against. Topologically, kernel preemption on a single CPU is equivalent to the problem of multiple CPU's being in the kernel. You should probably get with John Dyson on this; he's the most vocal advocate of kernel threads. 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 20:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15844 for current-outgoing; Tue, 10 Feb 1998 20:46:53 -0800 (PST) (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 UAA15839; Tue, 10 Feb 1998 20:46:49 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id XAA03625; Wed, 11 Feb 1998 23:43:59 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 12 Feb 1998 00:43:56 -0400 (EDT) From: "Alok K. Dhir" To: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: Compiling LKMs 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 Hey all - I'm running 3.0-current. After a "make world", I noticed that I could no longer load the linux emulation. Modload reported several "Undefined Symbol" errors. Similarly, the ibcs2 emulation loading reported an error as well (although at least it loaded). After messing around for a while, I realized that if I back out to the previous (before make world) version of the linux_mod.o, and the ibcs2 .o modules, everything works again. So the question is, what am I doing wrong? Why can't I compile the lkm's as part of the make world and have them continue to work? Thanks for any help... -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 20:55:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17340 for current-outgoing; Tue, 10 Feb 1998 20:55:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from master.inter-linc.net ([12.10.101.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17332 for ; Tue, 10 Feb 1998 20:55:54 -0800 (PST) (envelope-from cdillon@inter-linc.net) Received: from cheetah.inter-linc.net (12.10.101.15) by master.inter-linc.net (Worldmail 1.3.167); 10 Feb 1998 22:54:06 -0600 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980210033259.62112@top.worldcontrol.com> Date: Tue, 10 Feb 1998 22:49:49 -0600 (CST) From: Chris Dillon To: brian@worldcontrol.com Subject: Re: rxvt: can't load color "darkslateblue" ; 16 bit depth Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Feb-98 brian@worldcontrol.com wrote: >Any other ideas? > >-- >Brian Litzinger I may not have been paying close enough attention to the problem you stated. I'm not an expert on this, but I have experienced similar problems, and that is the only reason I am even offering help. :-) In /usr/X11R6/lib/X11 on my system (and yours too, most likely) is a file called rgb.txt. This is where color names are mapped to RGB values. Make sure this file is not corrupt and is world readable, and all of the "missing" color names appear in it. I'm not sure why it would work OK and then later have problems, though. A 16-bit color depth is still a "palleted" mode, so give 24-bit a try and see if the problems disappear for good. If not, there is some other underlying problem which I would have no clue about. --- Chris Dillon --- cdillon@inter-linc.net --- Powered by FreeBSD, the best operating system on the planet for Intel x86 based computers (and soon Sparcs). ---- (http://www.freebsd.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 21:08:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20159 for current-outgoing; Tue, 10 Feb 1998 21:08:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20068; Tue, 10 Feb 1998 21:07:58 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id XAA09593; Tue, 10 Feb 1998 23:07:48 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id XAA12032; Tue, 10 Feb 1998 23:07:17 -0600 Message-ID: <19980210230717.57903@right.PCS> Date: Tue, 10 Feb 1998 23:07:17 -0600 From: Jonathan Lemon To: "Alok K. Dhir" Cc: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Compiling LKMs References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Alok K. Dhir on Feb 02, 1998 at 12:43:56AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Feb 02, 1998 at 12:43:56AM -0400, Alok K. Dhir wrote: > > Hey all - I'm running 3.0-current. After a "make world", I noticed that I > could no longer load the linux emulation. Modload reported several > "Undefined Symbol" errors. Similarly, the ibcs2 emulation loading > reported an error as well (although at least it loaded). Temporary breakage. Re-cvsup again, I believe I saw a commit message go by, fixing this. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 21:19:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22217 for current-outgoing; Tue, 10 Feb 1998 21:19:04 -0800 (PST) (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 VAA22169; Tue, 10 Feb 1998 21:18:11 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id FAA15439; Wed, 11 Feb 1998 05:18:04 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id GAA02642; Wed, 11 Feb 1998 06:18:03 +0100 (MET) Message-ID: <19980211061803.50235@follo.net> Date: Wed, 11 Feb 1998 06:18:03 +0100 From: Eivind Eklund To: "Alok K. Dhir" Cc: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Compiling LKMs References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Alok K. Dhir on Thu, Feb 12, 1998 at 12:43:56AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 12, 1998 at 12:43:56AM -0400, Alok K. Dhir wrote: > > Hey all - I'm running 3.0-current. After a "make world", I noticed that I > could no longer load the linux emulation. Modload reported several > "Undefined Symbol" errors. Similarly, the ibcs2 emulation loading > reported an error as well (although at least it loaded). > > After messing around for a while, I realized that if I back out to the > previous (before make world) version of the linux_mod.o, and the ibcs2 > .o modules, everything works again. > > So the question is, what am I doing wrong? Why can't I compile the lkm's > as part of the make world and have them continue to work? Recompile your kernel, too. After recompiling the kernel and the LKMs, it should work. If not, then please yell at me - it is most likely my changes that are causing this. I committed fixes for this earlier tonight, so AFAIK everything is OK in the source tree as of right now. It wasn't OK 6 hours ago. Eivind, the major repeat offender for LKM-breaking :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 22:11:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29437 for current-outgoing; Tue, 10 Feb 1998 22:11:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from unix.tfs.net (as1-p167.tfs.net [139.146.210.167]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29282 for ; Tue, 10 Feb 1998 22:09:56 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id AAA08487 for freebsd-current@freebsd.org; Wed, 11 Feb 1998 00:09:48 -0600 (CST) From: Jim Bryant Message-Id: <199802110609.AAA08487@unix.tfs.net> Subject: st/mt To: freebsd-current@FreeBSD.ORG Date: Wed, 11 Feb 1998 00:09:47 -0600 (CST) Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Thu Jan 1 19:03:58 CST 1998 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG when was the last time st/mt was updated? mt comp 1 does not work.. density 0x24 == dds-2, and i have hacked mt.c to show this, but what about all in between 0x17 and 0x24? i'll provide diffs for mt.c with my changes... also, i have added a field for bp->mt_comp to the status display. who is the committer for these? jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 22:35:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02532 for current-outgoing; Tue, 10 Feb 1998 22:35:34 -0800 (PST) (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 WAA02511 for ; Tue, 10 Feb 1998 22:35:18 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id XAA05427; Tue, 10 Feb 1998 23:35:14 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd005402; Tue Feb 10 23:35:06 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id VAA02729; Tue, 10 Feb 1998 21:01:33 -0700 (MST) From: Terry Lambert Message-Id: <199802110401.VAA02729@usr04.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: jonny@coppe.ufrj.br (Joao Carlos Mendes Luis) Date: Wed, 11 Feb 1998 04:01:32 +0000 (GMT) Cc: tlambert@primenet.com, dima@tejblum.dnttm.rssi.ru, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199802101745.PAA12461@gaia.coppe.ufrj.br> from "Joao Carlos Mendes Luis" at Feb 10, 98 03:45:02 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > // The problem is that the same algorithm *must* be used for this to work > // reliably. > > I suppose that by algorithm you mean how the filenames are archived, > and not how the names are converted between formats. If it the second > option, let me remember you that Win95 registry can be programmed to > change the algorithm. I hate those ~'s in file names. :) Files created before the change will have the old value; files created after will have the new. The algorithm treats the "numeric tail" (MS terminology) identically in either case, as far as coming up with the next number. The problem with the algortihm that had been suggested is that it (effectively) went randomly into the number space. > // I did effectively this when I converted FFS/UFS for Windows 95 IFS, and > // added a Unicode name space and 8.3 names for FFS/UFS directory entries; > // the problems I faced are exactly the inverse of the problems you face. > > You mean you have a FFS driver for Win95 ? Is it available ? :) It belongs to Artisoft, and it was also licensed as part of a severance package to the other two engineers who worked on it (they left before I left). It's actually a port of the entire Heidemann framework to Windows 95, only you can start with zero FS's, add as many FS's vfsops tables as you want, etc. Windows 95 treats it as a local media FS (it is, I believe, still the only local media FS ever written for Windows 95 outside of Microsoft). In this framework, we put a FFS/UFS with Unicode support, second name space support, and soft updates. The namespace changes made the on dosk format incompatible with FreeBSD's FFS/UFS, mostly because of the FreeBSD namei() code. The other two engineers are currently working on FS code and server code for NetWork appliance. One of them is the person primarily responsible for NetWare's NDS working. 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 current" in the body of the message From owner-freebsd-current Tue Feb 10 22:42:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03681 for current-outgoing; Tue, 10 Feb 1998 22:42:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from unix.tfs.net (as1-p167.tfs.net [139.146.210.167]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03673 for ; Tue, 10 Feb 1998 22:42:41 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.8.8/8.8.5) id AAA10013 for freebsd-current@freebsd.org; Wed, 11 Feb 1998 00:42:35 -0600 (CST) From: Jim Bryant Message-Id: <199802110642.AAA10013@unix.tfs.net> Subject: st/mt To: freebsd-current@FreeBSD.ORG Date: Wed, 11 Feb 1998 00:42:34 -0600 (CST) Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Thu Jan 1 19:03:58 CST 1998 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG here is the diff i mentioned... not much right now, just perusing the code mainly... *** mt.c.orig Thu Aug 21 00:49:29 1997 --- mt.c Wed Feb 11 00:36:27 1998 *************** *** 368,371 **** --- 368,378 ---- { 0x16, "X3.193-1990" }, { 0x17, "X3B5/91-174" }, + { 0x18, "0x18 ???"}, /* ??? */ + { 0x19, "0x19 ???"}, /* ??? */ + { 0x20, "0x20 ???"}, /* ??? */ + { 0x21, "0x21 ???"}, /* ??? */ + { 0x22, "0x22 ???"}, /* ??? */ + { 0x23, "0x23 ???"}, /* ??? */ + { 0x24, "ECMA DDS-2"}, /* As returned by HP C1533A with 120M tape inserted [jdb] */ { 0, 0 } }; *************** *** 416,430 **** st_status(struct mtget *bp) { ! printf("Present Mode: Density = %-12s Blocksize %s\n", ! denstostring(bp->mt_density), getblksiz(bp->mt_blksiz)); printf("---------available modes---------\n"); ! printf("Mode 0: Density = %-12s Blocksize %s\n", ! denstostring(bp->mt_density0), getblksiz(bp->mt_blksiz0)); ! printf("Mode 1: Density = %-12s Blocksize %s\n", ! denstostring(bp->mt_density1), getblksiz(bp->mt_blksiz1)); ! printf("Mode 2: Density = %-12s Blocksize %s\n", ! denstostring(bp->mt_density2), getblksiz(bp->mt_blksiz2)); ! printf("Mode 3: Density = %-12s Blocksize %s\n", ! denstostring(bp->mt_density3), getblksiz(bp->mt_blksiz3)); } --- 423,437 ---- st_status(struct mtget *bp) { ! printf("Present Mode: Density = %-12s Compression: %d Blocksize %s\n", ! denstostring(bp->mt_density), bp->mt_comp, getblksiz(bp->mt_blksiz)); printf("---------available modes---------\n"); ! printf("Mode 0: Density = %-12s Compression: %d Blocksize %s\n", ! denstostring(bp->mt_density0), bp->mt_comp, getblksiz(bp->mt_blksiz0)); ! printf("Mode 1: Density = %-12s Compression: %d Blocksize %s\n", ! denstostring(bp->mt_density1), bp->mt_comp, getblksiz(bp->mt_blksiz1)); ! printf("Mode 2: Density = %-12s Compression: %d Blocksize %s\n", ! denstostring(bp->mt_density2), bp->mt_comp, getblksiz(bp->mt_blksiz2)); ! printf("Mode 3: Density = %-12s Compression: %d Blocksize %s\n", ! denstostring(bp->mt_density3), bp->mt_comp, getblksiz(bp->mt_blksiz3)); } jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Tue Feb 10 23:58:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11431 for current-outgoing; Tue, 10 Feb 1998 23:58:48 -0800 (PST) (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 XAA11396 for ; Tue, 10 Feb 1998 23:58:43 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id XAA15322; Tue, 10 Feb 1998 23:58:21 -0800 (PST) Message-Id: <199802110758.XAA15322@implode.root.com> To: Terry Lambert cc: jb@cimlogic.com.au, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Wed, 11 Feb 1998 03:15:15 GMT." <199802110315.UAA00548@usr04.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 10 Feb 1998 23:58:21 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In many cases, Terry's solutions to the problems that he is trying to >> solve aren't the ones we want to adopt. >> There are far more instances where Kirk McKusick and other people >> in-the-know have objected to the direction that Terry wants to take >> us than there are in favor. > >I've talked to Kirk about many of the changes since I've been in the >Bay Area, and you are misquoting him here. I have neither quoted nor paraphrased Kirk or anyone else in my last message. > He has agreed that >a number of the layering issues I have been harping on since day one >are, in fact, legitimate problems. Yes, and I agree as well about some issues. For instance, there is agreement that VOP_UNLOCK should be handled entirely by the VOP_LOCK'er, and not haphazardly by the lower levels depending on the phase of the moon and other factors. Those of us who have looked at making this change realize that this is riddled with potential problems, however, especially when code such as ufs_rename has to be rewritten. I don't even trust Kirk (the author) to do this, so why would I trust you? On the other hand, there is general disagreement on changing the symantics of advisory locking. >> Terry's unwillingness to carefully explain/justify the changes that >> he proposes in a manor that reasonable kernel developers can >> understand has further resulted in a serious lack of trust. For ... >I'll be happy to explain anything you have questions about. This is inconsistent with what you have said in the past which was escentially that you had neither the time nor the willingness to explain the changes you were proposing and that we should just take it on faith that what you want to do is good. >occur. The only rationale against these has been "we fear change, >specifically in the form of divergence". Now that that's blown >out, so long as it's possible to revert such changes if they are seen >to have a detrimental effect, I don't see why there's a problem. Backing out changes after some amount of time has gone by (and thus the code has been modified by other people for other reasons) is not a trivial undertaking. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 00:12:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13038 for current-outgoing; Wed, 11 Feb 1998 00:12:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12894; Wed, 11 Feb 1998 00:10:52 -0800 (PST) (envelope-from abial@korin.warman.org.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id JAA18206; Wed, 11 Feb 1998 09:13:16 +0100 (CET) Date: Wed, 11 Feb 1998 09:13:15 +0100 (CET) From: Andrzej Bialecki To: freebsd-current@FreeBSD.ORG cc: dyson@FreeBSD.ORG Subject: Crash in -current VM Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-960935415-887184795=:12470" 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-960935415-887184795=:12470 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi! Bad news, at least for me. The system is current as of yesterday (1998.02.10, ca. 2100 GMT). `dmesg` is attached, as well as kernel config file. The situation was as follows: I put only 8MB RAM into machine to perform some tests. I caused extremely heavy paging (started X, Netscape, make world etc...). I have 65MB of swap, and it wasn't full at the end, but the system wasn't doing almost anything useful except swapping :-). I didn't use NFS. I mount a DOS partition (and of course several FFS ones). The problem is very repeatable: after some time (from 1-20min) the system locks up (I have only local access to this machine, so if it was in X I was locked out, and had to push Reset - keyboard reset wouldn't work), and drops me into ddb. I was once in gdb and tried to debug previous crash dump when the machine locked - after pressing ^T gdb said it was sitting in [vmwait]. Next time I managed to get some info from the crash dump. Here it is: # gdb -k kernel.5 vmcore.5 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 221000 current pcb at 1d2dcc panicstr: vm_object_deallocate: object deallocated too many times: %d panic messages: --- panic: vm_object_deallocate: object deallocated too many times: 1 panic: from debugger dumping to dev 30001, offset 114688 dump 7 6 5 4 3 2 1 --- #0 0xf01204ab in boot () (kgdb) where #0 0xf01204ab in boot () #1 0xf0120797 in panic () #2 0xf01013e5 in db_panic () #3 0xf01012d5 in db_command () #4 0xf0101452 in db_command_loop () #5 0xf0103b13 in db_trap () #6 0xf018e401 in kdb_trap () #7 0xf0198ff8 in trap () #8 0xf018e62d in Debugger () #9 0xf012078e in panic () #10 0xf0181fa3 in vm_object_deallocate () #11 0xf017f86b in vm_map_entry_delete () #12 0xf017f9e5 in vm_map_delete () #13 0xf017fa69 in vm_map_remove () #14 0xf01195d8 in exit1 () #15 0xf0121a4a in sigexit () #16 0xf0121847 in postsig () #17 0xf0199094 in trap () #18 0x85e4 in ?? () Cannot access memory at address 0xefbfdc8c. (kgdb) quit As I said, the problem is very repeatable - if you need more details, I can provide them (if you tell me what to do with gdb/config/etc... ;-), though I would want to make a fresh backup first - last time it crashed I had to run fsck several times, and I'm still not sure it recovered all the pieces... Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- --0-960935415-887184795=:12470 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=tune Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Iw0KIyBHRU5FUklDIC0tIEdlbmVyaWMgbWFjaGluZSB3aXRoIFdEL0FIeC9O Q1IvQlR4IGZhbWlseSBkaXNrcw0KIw0KIyBGb3IgbW9yZSBpbmZvcm1hdGlv biByZWFkIHRoZSBoYW5kYm9vayBwYXJ0IFN5c3RlbSBBZG1pbmlzdHJhdGlv biAtPiANCiMgQ29uZmlndXJpbmcgdGhlIEZyZWVCU0QgS2VybmVsIC0+IFRo ZSBDb25maWd1cmF0aW9uIEZpbGUuIA0KIyBUaGUgaGFuZGJvb2sgaXMgYXZh aWxhYmxlIGluIC91c3Ivc2hhcmUvZG9jL2hhbmRib29rIG9yIG9ubGluZSBh cw0KIyBsYXRlc3QgdmVyc2lvbiBmcm9tIHRoZSBGcmVlQlNEIFdvcmxkIFdp ZGUgV2ViIHNlcnZlciANCiMgPFVSTDpodHRwOi8vd3d3LkZyZWVCU0QuT1JH Lz4NCiMNCiMgQW4gZXhoYXVzdGl2ZSBsaXN0IG9mIG9wdGlvbnMgYW5kIG1v cmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZSANCiMgZGV2aWNlIGxp bmVzIGlzIHByZXNlbnQgaW4gdGhlIC4vTElOVCBjb25maWd1cmF0aW9uIGZp bGUuIElmIHlvdSBhcmUgDQojIGluIGRvdWJ0IGFzIHRvIHRoZSBwdXJwb3Nl IG9yIG5lY2Vzc2l0eSBvZiBhIGxpbmUsIGNoZWNrIGZpcnN0IGluIExJTlQu DQojDQojCSRJZDogR0VORVJJQyx2IDEuODggMTk5Ny8wMy8xMyAxOTowMzo1 OCBiZGUgRXhwICQNCg0KbWFjaGluZQkJImkzODYiDQpjcHUJCSJJNDg2X0NQ VSINCmNwdQkJIkk1ODZfQ1BVIg0KaWRlbnQJCVRVTkUNCm1heHVzZXJzCTMw DQoNCm9wdGlvbnMJCUlORVQJCQkjSW50ZXJORVR3b3JraW5nDQpvcHRpb25z CQlGRlMJCQkjQmVya2VsZXkgRmFzdCBGaWxlc3lzdGVtDQpvcHRpb25zCQlN U0RPU0ZTCQkJI01TRE9TIEZpbGVzeXN0ZW0NCm9wdGlvbnMJCSJDRDk2NjAi CQkjSVNPIDk2NjAgRmlsZXN5c3RlbQ0Kb3B0aW9ucwkJUFJPQ0ZTCQkJI1By b2Nlc3MgZmlsZXN5c3RlbQ0Kb3B0aW9ucwkJS0VSTkZTCQkJI1Byb2Nlc3Mg ZmlsZXN5c3RlbQ0KI29wdGlvbnMJCURFVkZTDQpvcHRpb25zCQkiQ09NUEFU XzQzIgkJI0NvbXBhdGlibGUgd2l0aCBCU0QgNC4zIFtLRUVQIFRISVMhXQ0K b3B0aW9ucwkJVUNPTlNPTEUJCSNBbGxvdyB1c2VycyB0byBncmFiIHRoZSBj b25zb2xlDQpvcHRpb25zCQlVU0VSQ09ORklHCQkjYm9vdCAtYyBlZGl0b3IN Cm9wdGlvbnMJCVZJU1VBTF9VU0VSQ09ORklHCSN2aXN1YWwgYm9vdCAtYyBl ZGl0b3INCm9wdGlvbnMJCVVTRVJfTERUDQpvcHRpb25zCQlTWVNWU0hNDQpv cHRpb25zCQlTWVNWU0VNDQpvcHRpb25zCQlTWVNWTVNHDQpvcHRpb25zCQlL VFJBQ0UNCm9wdGlvbnMJCUREQg0Kb3B0aW9ucwkJIkFVVE9fRU9JXzEiDQpv cHRpb25zCQkiQVVUT19FT0lfMiINCiNvcHRpb25zCQlDT01QQVRfTElOVVgN Cm9wdGlvbnMJCSJFWFQyRlMiDQojb3B0aW9ucwkJIklCQ1MyIg0Kb3B0aW9u cwkJIlZNODYiDQoNCmNvbmZpZwkJa2VybmVsCXJvb3Qgb24gd2QwIHN3YXAg b24gZ2VuZXJpYw0KDQpjb250cm9sbGVyCWlzYTANCmNvbnRyb2xsZXIJcGNp MA0KDQpjb250cm9sbGVyCWZkYzAJYXQgaXNhPyBwb3J0ICJJT19GRDEiIGJp byBpcnEgNiBkcnEgMiB2ZWN0b3IgZmRpbnRyDQpkaXNrCQlmZDAJYXQgZmRj MCBkcml2ZSAwDQoNCmNvbnRyb2xsZXIJd2RjMAlhdCBpc2E/IHBvcnQgIklP X1dEMSIgYmlvIGlycSAxNCBmbGFncyAweGEwZmZhMGZmIHZlY3RvciB3ZGlu dHINCmRpc2sJCXdkMAlhdCB3ZGMwIGRyaXZlIDANCmRpc2sJCXdkMQlhdCB3 ZGMwIGRyaXZlIDENCg0KY29udHJvbGxlcgl3ZGMxCWF0IGlzYT8gcG9ydCAi SU9fV0QyIiBiaW8gaXJxIDE1IGZsYWdzIDB4YTBmZmEwZmYgdmVjdG9yIHdk aW50cg0KZGlzawkJd2QyCWF0IHdkYzEgZHJpdmUgMA0KZGlzawkJd2QzCWF0 IHdkYzEgZHJpdmUgMQ0KDQpvcHRpb25zCQlBVEFQSQkJI0VuYWJsZSBBVEFQ SSBzdXBwb3J0IGZvciBJREUgYnVzDQpvcHRpb25zCQlBVEFQSV9TVEFUSUMJ I0Rvbid0IGRvIGl0IGFzIGFuIExLTQ0KZGV2aWNlCQl3Y2QwCSNJREUgQ0Qt Uk9NDQoNCg0KIyBzeXNjb25zIGlzIHRoZSBkZWZhdWx0IGNvbnNvbGUgZHJp dmVyLCByZXNlbWJsaW5nIGFuIFNDTyBjb25zb2xlDQpkZXZpY2UJCXNjMAlh dCBpc2E/IHBvcnQgIklPX0tCRCIgdHR5IGlycSAxIHZlY3RvciBzY2ludHIN Cg0KZGV2aWNlCQlucHgwCWF0IGlzYT8gcG9ydCAiSU9fTlBYIiBpcnEgMTMg dmVjdG9yIG5weGludHINCg0KZGV2aWNlCQlzaW8wCWF0IGlzYT8gcG9ydCAi SU9fQ09NMSIgdHR5IGlycSA0IHZlY3RvciBzaW9pbnRyDQpkZXZpY2UJCXNp bzEJYXQgaXNhPyBwb3J0ICJJT19DT00yIiB0dHkgaXJxIDMgdmVjdG9yIHNp b2ludHINCg0KZGV2aWNlCQlscHQwCWF0IGlzYT8gcG9ydD8gdHR5IGlycSA3 IHZlY3RvciBscHRpbnRyDQoNCmNvbnRyb2xsZXIgcG5wMA0KI2NvbnRyb2xs ZXIgc25kMA0KI2RldmljZSBndXMwIGF0IGlzYT8gdmVjdG9yIGd1c2ludHIN CiNkZXZpY2UgcGNtMCBhdCBpc2E/IHBvcnQgPyB0dHkgaXJxIDEwIGRycSAx IGZsYWdzIDB4MCB2ZWN0b3IgcGNtaW50cg0KDQojY29udHJvbGxlciBwcGJ1 czANCiNkZXZpY2UgbmxwdDAgYXQgcHBidXM/DQoNCiNjb250cm9sbGVyIHBw YzAgYXQgaXNhPyBkaXNhYmxlIHBvcnQgPyBpcnEgNyB2ZWN0b3IgcHBjaW50 cg0KDQpkZXZpY2UgZWQwIGF0IGlzYT8gcG9ydCAweDI4MCBpcnEgMTAgdmVj dG9yIGVkaW50cg0KDQpwc2V1ZG8tZGV2aWNlCWxvb3ANCnBzZXVkby1kZXZp Y2UJZXRoZXINCiNwc2V1ZG8tZGV2aWNlCXNsCTENCnBzZXVkby1kZXZpY2UJ YnBmaWx0ZXIJNA0KI3BzZXVkby1kZXZpY2UJZGlzYw0KcHNldWRvLWRldmlj ZQlzcGVha2VyDQpwc2V1ZG8tZGV2aWNlCXZuDQpwc2V1ZG8tZGV2aWNlCXNu cAkyDQojIGlqcHBwIHVzZXMgdHVuIGluc3RlYWQgb2YgcHBwIGRldmljZQ0K I3BzZXVkby1kZXZpY2UJcHBwCTENCnBzZXVkby1kZXZpY2UJdHVuCTENCnBz ZXVkby1kZXZpY2UJcHR5CTE2DQpwc2V1ZG8tZGV2aWNlCWd6aXAJCSMgRXhl YyBnemlwcGVkIGEub3V0J3MNCg== --0-960935415-887184795=:12470 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Q29weXJpZ2h0IChjKSAxOTkyLTE5OTggRnJlZUJTRCBJbmMuDQpDb3B5cmln aHQgKGMpIDE5ODIsIDE5ODYsIDE5ODksIDE5OTEsIDE5OTMNCglUaGUgUmVn ZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLg0KRnJlZUJTRCAzLjAtQ1VSUkVOVCAjMDogVHVlIEZl YiAxMCAyMDoyNjo1MSBNRVQgMTk5OA0KICAgIHJvb3RAYWJpYWwud2FybWFu LmNvbS5wbDovdXNyL3NyYy9zeXMvY29tcGlsZS9UVU5FDQpDYWxpYnJhdGlu ZyBjbG9jayhzKSAuLi4gVFNDIGNsb2NrOiAxMDAyMzY5MzAgSHosIGk4MjU0 IGNsb2NrOiAxMTkzMjk4IEh6DQpDTEtfVVNFX0k4MjU0X0NBTElCUkFUSU9O IG5vdCBzcGVjaWZpZWQgLSB1c2luZyBkZWZhdWx0IGZyZXF1ZW5jeQ0KQ0xL X1VTRV9UU0NfQ0FMSUJSQVRJT04gbm90IHNwZWNpZmllZCAtIHVzaW5nIG9s ZCBjYWxpYnJhdGlvbiBtZXRob2QNCkNQVTogQU1ELUs1KHRtKSBQcm9jZXNz b3IgKDEwMC4yMy1NSHogNTg2LWNsYXNzIENQVSkNCiAgT3JpZ2luID0gIkF1 dGhlbnRpY0FNRCIgIElkID0gMHg1MTEgIFN0ZXBwaW5nPTENCiAgRmVhdHVy ZXM9MHgyMWJmPEZQVSxWTUUsREUsUFNFLFRTQyxNU1IsTUNFLENYOCxQR0U+ DQpEYXRhIFRMQjogMTI4IGVudHJpZXMsIDQtd2F5IGFzc29jaWF0aXZlDQpJ bnN0cnVjdGlvbiBUTEI6IDAgZW50cmllcywgMC13YXkgYXNzb2NpYXRpdmUN CkwxIGRhdGEgY2FjaGU6IDgga2J5dGVzLCAzMiBieXRlcy9saW5lLCAxIGxp bmVzL3RhZywgNC13YXkgYXNzb2NpYXRpdmUNCkwxIGluc3RydWN0aW9uIGNh Y2hlOiAxNiBrYnl0ZXMsIDMyIGJ5dGVzL2xpbmUsIDEgbGluZXMvdGFnLCA0 LXdheSBhc3NvY2lhdGl2ZQ0KcmVhbCBtZW1vcnkgID0gODM4ODYwOCAoODE5 MksgYnl0ZXMpDQpQaHlzaWNhbCBtZW1vcnkgY2h1bmsocyk6DQoweDAwMDAx MDAwIC0gMHgwMDA5ZmZmZiwgNjUxMjY0IGJ5dGVzICgxNTkgcGFnZXMpDQow eDAwMjI0MDAwIC0gMHgwMDdmZGZmZiwgNjEzNTgwOCBieXRlcyAoMTQ5OCBw YWdlcykNCmF2YWlsIG1lbW9yeSA9IDY0MTQzMzYgKDYyNjRLIGJ5dGVzKQ0K Rm91bmQgQklPUzMyIFNlcnZpY2UgRGlyZWN0b3J5IGhlYWRlciBhdCAweGYw MGZiMTMwDQpFbnRyeSA9IDB4ZmI1YTAgKDB4ZjAwZmI1YTApICBSZXYgPSAw ICBMZW4gPSAxDQpQQ0kgQklPUyBlbnRyeSBhdCAweGI1ZDANCk90aGVyIEJJ T1Mgc2lnbmF0dXJlcyBmb3VuZDoNCkFDUEk6IDAwMDAwMDAwDQokUG5QOiAw MDBmYzJjMA0KcGNpX29wZW4oMSk6CW1vZGUgMSBhZGRyIHBvcnQgKDB4MGNm OCkgaXMgMHg4MDAwMDA1Yw0KcGNpX29wZW4oMWEpOgltb2RlMXJlcz0weDgw MDAwMDAwICgweDgwMDAwMDAwKQ0KcGNpX2NmZ2NoZWNrOglkZXZpY2UgMCBb Y2xhc3M9MDYwMDAwXSBbaGRyPTAwXSBpcyB0aGVyZSAoaWQ9MTI1MDgwODYp DQpQcm9iaW5nIGZvciBkZXZpY2VzIG9uIFBDSSBidXMgMDoNCmZvdW5kLT4J dmVuZG9yPTB4ODA4NiwgZGV2PTB4MTI1MCwgcmV2aWQ9MHgwMw0KCWNsYXNz PTA2LTAwLTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTANCmNoaXAwOiA8SW50 ZWwgODI0Mzk+IHJldiAweDAzIG9uIHBjaTAuMC4wDQpmb3VuZC0+CXZlbmRv cj0weDgwODYsIGRldj0weDcwMDAsIHJldmlkPTB4MDENCgljbGFzcz0wNi0w MS0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0xDQpjaGlwMTogPEludGVsIDgy MzcxU0IgUENJIHRvIElTQSBicmlkZ2U+IHJldiAweDAxIG9uIHBjaTAuNy4w DQoJSS9PIFJlY292ZXJ5IFRpbWluZzogOC1iaXQgMSBjbG9ja3MsIDE2LWJp dCAxIGNsb2Nrcw0KCUV4dGVuZGVkIEJJT1M6IGVuYWJsZWQNCglMb3dlciBC SU9TOiBkaXNhYmxlZA0KCUNvcHJvY2Vzc29yIElSUTEzOiBlbmFibGVkDQoJ TW91c2UgSVJRMTI6IGRpc2FibGVkDQoJSW50ZXJydXB0IFJvdXRpbmc6IEE6 IGRpc2FibGVkLCBCOiBkaXNhYmxlZCwgQzogSVJRMTAsIEQ6IGRpc2FibGVk DQoJCU1CMDogZGlzYWJsZWQsIE1CMTogDQpmb3VuZC0+CXZlbmRvcj0weDgw ODYsIGRldj0weDcwMTAsIHJldmlkPTB4MDANCgljbGFzcz0wMS0wMS04MCwg aGRydHlwZT0weDAwLCBtZmRldj0wDQppZGVfcGNpMDogPEludGVsIFBJSVgz IEJ1cy1tYXN0ZXIgSURFIGNvbnRyb2xsZXI+IHJldiAweDAwIG9uIHBjaTAu Ny4xDQppbnRlbF9waWl4X3N0YXR1czogcHJpbWFyeSBtYXN0ZXIgc2FtcGxl ID0gMywgbWFzdGVyIHJlY292ZXJ5ID0gMQ0KaW50ZWxfcGlpeF9zdGF0dXM6 IHByaW1hcnkgbWFzdGVyIGZhc3RETUFvbmx5IGRpc2FibGVkLCBwcmUvcG9z dCBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBJT1JEWSBzYW1wbGlu ZyBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBmYXN0IFBJTyBlbmFi bGVkDQppbnRlbF9waWl4X3N0YXR1czogcHJpbWFyeSBzbGF2ZSBzYW1wbGUg PSAzLCBzbGF2ZSByZWNvdmVyeSA9IDENCmludGVsX3BpaXhfc3RhdHVzOiBw cmltYXJ5IHNsYXZlIGZhc3RETUFvbmx5IGRpc2FibGVkLCBwcmUvcG9zdCBl bmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBJT1JEWSBzYW1wbGluZyBl bmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBmYXN0IFBJTyBlbmFibGVk DQppZGVfcGNpOiBidXNtYXN0ZXIgMCBzdGF0dXM6IDA0IGZyb20gcG9ydDog MDAwMDkwMDINCmludGVsX3BpaXhfc3RhdHVzOiBzZWNvbmRhcnkgbWFzdGVy IHNhbXBsZSA9IDQsIG1hc3RlciByZWNvdmVyeSA9IDQNCmludGVsX3BpaXhf c3RhdHVzOiBzZWNvbmRhcnkgbWFzdGVyIGZhc3RETUFvbmx5IGRpc2FibGVk LCBwcmUvcG9zdCBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBJT1JE WSBzYW1wbGluZyBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBmYXN0 IFBJTyBlbmFibGVkDQppbnRlbF9waWl4X3N0YXR1czogc2Vjb25kYXJ5IHNs YXZlIHNhbXBsZSA9IDUsIHNsYXZlIHJlY292ZXJ5ID0gNA0KaW50ZWxfcGlp eF9zdGF0dXM6IHNlY29uZGFyeSBzbGF2ZSBmYXN0RE1Bb25seSBkaXNhYmxl ZCwgcHJlL3Bvc3QgZGlzYWJsZWQsDQppbnRlbF9waWl4X3N0YXR1czogIElP UkRZIHNhbXBsaW5nIGRpc2FibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBm YXN0IFBJTyBkaXNhYmxlZA0KaWRlX3BjaTogYnVzbWFzdGVyIDEgc3RhdHVz OiAwNCBmcm9tIHBvcnQ6IDAwMDA5MDBhDQpmb3VuZC0+CXZlbmRvcj0weDUz MzMsIGRldj0weDU2MzEsIHJldmlkPTB4MDYNCgljbGFzcz0wMy0wMC0wMCwg aGRydHlwZT0weDAwLCBtZmRldj0wDQoJaW50cGluPWEsIGlycT0xMA0KCW1h cFswXTogdHlwZSAxLCByYW5nZSAzMiwgYmFzZSBlMDAwMDAwMCwgc2l6ZSAy Ng0KdmdhMDogPFMzIFZpUkdFIGdyYXBoaWNzIGFjY2VsZXJhdG9yPiByZXYg MHgwNiBpbnQgYSBpcnEgMTAgb24gcGNpMC4xOC4wDQpJbml0aWFsaXppbmcg UG5QIG92ZXJyaWRlIHRhYmxlDQpQcm9iaW5nIGZvciBQblAgZGV2aWNlczoN ClRyeWluZyBSZWFkX1BvcnQgYXQgMjAzDQpDU04gMSBWZW5kb3IgSUQ6IEdS VjAwMDEgWzB4MDEwMDU2MWVdIFNlcmlhbCAweGZmZmZmZmZmDQpDYWxsZWQg bnVsbHBucF9wcm9iZSB3aXRoIHRhZyAweDAwMDAwMDAxLCB0eXBlIDB4MDEw MDU2MWUNClByb2JpbmcgZm9yIGRldmljZXMgb24gdGhlIElTQSBidXM6DQpz YzA6IHRoZSBjdXJyZW50IGtleWJvYXJkIGNvbnRyb2xsZXIgY29tbWFuZCBi eXRlIDAwNjUNCmtiZGlvOiBESUFHTk9TRSBzdGF0dXM6MDA1NQ0Ka2JkaW86 IFRFU1RfS0JEX1BPUlQgc3RhdHVzOjAwMDANCmtiZGlvOiBSRVNFVF9LQkQg cmV0dXJuIGNvZGU6MDBmYQ0Ka2JkaW86IFJFU0VUX0tCRCBzdGF0dXM6MDBh YQ0Kc2MwIGF0IDB4NjAtMHg2ZiBpcnEgMSBvbiBtb3RoZXJib2FyZA0Kc2Mw OiBCSU9TIHZpZGVvIG1vZGU6Mw0Kc2MwOiBWR0EgcmVnaXN0ZXJzIHVwb24g cG93ZXItdXANCjUwIDE4IDEwIDAwIDEwIDAwIDAzIDAwIDAyIDY3IDVmIDRm IDUwIDgyIDU1IDgxIA0KYmYgMWYgMDAgNGYgMGUgMGYgMDAgMDAgMDcgODAg OWMgOGUgOGYgMjggMWYgOTYgDQpiOSBhMyBmZiAwMCAwMSAwMiAwMyAwNCAw NSAxNCAwNyAzOCAzOSAzYSAzYiAzYyANCjNkIDNlIDNmIDBjIDAwIDBmIDA4 IDAwIDAwIDAwIDAwIDAwIDEwIDBlIDAwIGZmIA0Kc2MwOiB2aWRlbyBtb2Rl OjI0DQpzYzA6IFZHQSByZWdpc3RlcnMgaW4gQklPUyBmb3IgbW9kZToyNA0K NTAgMTggMTAgMDAgMTAgMDAgMDMgMDAgMDIgNjcgNWYgNGYgNTAgODIgNTUg ODEgDQpiZiAxZiAwMCA0ZiAwZCAwZSAwMCAwMCAwMCAwMCA5YyA4ZSA4ZiAy OCAxZiA5NiANCmI5IGEzIGZmIDAwIDAxIDAyIDAzIDA0IDA1IDE0IDA3IDM4 IDM5IDNhIDNiIDNjIA0KM2QgM2UgM2YgMGMgMDAgMGYgMDggMDAgMDAgMDAg MDAgMDAgMTAgMGUgMDAgZmYgDQpzYzA6IFZHQSByZWdpc3RlcnMgdG8gYmUg dXNlZCBmb3IgbW9kZToyNA0KNTAgMTggMTAgMDAgMTAgMDAgMDMgMDAgMDIg NjcgNWYgNGYgNTAgODIgNTUgODEgDQpiZiAxZiAwMCA0ZiAwZCAwZSAwMCAw MCAwMCAwMCA5YyA4ZSA4ZiAyOCAxZiA5NiANCmI5IGEzIGZmIDAwIDAxIDAy IDAzIDA0IDA1IDE0IDA3IDM4IDM5IDNhIDNiIDNjIA0KM2QgM2UgM2YgMGMg MDAgMGYgMDggMDAgMDAgMDAgMDAgMDAgMTAgMGUgMDAgZmYgDQpzYzA6IHJv d3Nfb2Zmc2V0OjENCnNjMDogVkdBIGNvbG9yIDwxNiB2aXJ0dWFsIGNvbnNv bGVzLCBmbGFncz0weDA+DQplZDAgbm90IGZvdW5kIGF0IDB4MjgwDQpzaW8w IGF0IDB4M2Y4LTB4M2ZmIGlycSA0IG9uIGlzYQ0Kc2lvMDogdHlwZSAxNjU1 MEENCnNpbzEgYXQgMHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhDQpzaW8xOiB0 eXBlIDE2NTUwQQ0KbHB0MCBhdCAweDM3OC0weDM3ZiBpcnEgNyBvbiBpc2EN CmxwdDA6IEludGVycnVwdC1kcml2ZW4gcG9ydA0KbHAwOiBUQ1AvSVAgY2Fw YWJsZSBpbnRlcmZhY2UNCmJwZjogbHAwIGF0dGFjaGVkDQpmZGMwIGF0IDB4 M2YwLTB4M2Y3IGlycSA2IGRycSAyIG9uIGlzYQ0KZmRjMDogRklGTyBlbmFi bGVkLCA4IGJ5dGVzIHRocmVzaG9sZA0KZmQwOiAxLjQ0TUIgMy41aW4NCndk YzAgYXQgMHgxZjAtMHgxZjcgaXJxIDE0IGZsYWdzIDB4YTBmZmEwZmYgb24g aXNhDQppbnRlbF9waWl4X2RtYWluaXQ6IHNldHRpbmcgbXVsdGl3b3JkIERN QSBtb2RlIDINCndkMDogd2RzZXRtb2RlKCkgc2V0dGluZyB0cmFuc2ZlciBt b2RlIHRvIDIyDQppbnRlbF9waWl4X3N0YXR1czogcHJpbWFyeSBzbGF2ZSBz YW1wbGUgPSAzLCBzbGF2ZSByZWNvdmVyeSA9IDENCmludGVsX3BpaXhfc3Rh dHVzOiBwcmltYXJ5IHNsYXZlIGZhc3RETUFvbmx5IGRpc2FibGVkLCBwcmUv cG9zdCBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBJT1JEWSBzYW1w bGluZyBlbmFibGVkLA0KaW50ZWxfcGlpeF9zdGF0dXM6ICBmYXN0IFBJTyBl bmFibGVkDQp3ZGMwOiB1bml0IDAgKHdkMCk6IDxXREMgQUMyMjUwMEw+LCBE TUEsIDMyLWJpdCwgbXVsdGktYmxvY2stMTYNCndkMDogMjQ0MU1CICg0OTk5 NjgwIHNlY3RvcnMpLCA0OTYwIGN5bHMsIDE2IGhlYWRzLCA2MyBTL1QsIDUx MiBCL1MNCndkMDogQVRBIElOUVVJUkUgdmFsaWQgPSAwMDAzLCBkbWFtd29y ZCA9IDA0MDcsIGFwaW8gPSAwMDAzLCB1ZG1hID0gMDAwMA0KaW50ZWxfcGlp eF9kbWFpbml0OiBzZXR0aW5nIG11bHRpd29yZCBETUEgbW9kZSAyDQp3ZDE6 IHdkc2V0bW9kZSgpIHNldHRpbmcgdHJhbnNmZXIgbW9kZSB0byAyMg0KaW50 ZWxfcGlpeF9zdGF0dXM6IHByaW1hcnkgc2xhdmUgc2FtcGxlID0gMywgc2xh dmUgcmVjb3ZlcnkgPSAxDQppbnRlbF9waWl4X3N0YXR1czogcHJpbWFyeSBz bGF2ZSBmYXN0RE1Bb25seSBkaXNhYmxlZCwgcHJlL3Bvc3QgZW5hYmxlZCwN CmludGVsX3BpaXhfc3RhdHVzOiAgSU9SRFkgc2FtcGxpbmcgZW5hYmxlZCwN CmludGVsX3BpaXhfc3RhdHVzOiAgZmFzdCBQSU8gZW5hYmxlZA0Kd2RjMDog dW5pdCAxICh3ZDEpOiA8Q29ubmVyIFBlcmlwaGVyYWxzIDg1ME1CIC0gQ0ZT ODUwQT4sIERNQSwgMzItYml0LCBtdWx0aS1ibG9jay0xNg0Kd2QxOiA4MTJN QiAoMTY2NDIwOCBzZWN0b3JzKSwgMTY1MSBjeWxzLCAxNiBoZWFkcywgNjMg Uy9ULCA1MTIgQi9TDQp3ZDE6IEFUQSBJTlFVSVJFIHZhbGlkID0gMDAwMywg ZG1hbXdvcmQgPSAwMzA3LCBhcGlvID0gMDAwMywgdWRtYSA9IDAwMDANCndk YzEgYXQgMHgxNzAtMHgxNzcgaXJxIDE1IGZsYWdzIDB4YTBmZmEwZmYgb24g aXNhDQp3ZGMxOiB1bml0IDAgKGF0YXBpKTogPGlQbm9lZSByRENSLU1PQSBB VElQb01lZCBsUkRVLTFBNDIgWDIwMDAvMkUwLkEwPiwgcmVtb3ZhYmxlLCBk bWEsIGlvcmRpcw0Kd2NkMDogNjg5S2Ivc2VjLCAxMjhLYiBjYWNoZSwgYXVk aW8gcGxheSwgMjU2IHZvbHVtZSBsZXZlbHMsIGVqZWN0YWJsZSB0cmF5DQp3 Y2QwOiAxMjBtbSBhdWRpbyBkaXNjIGxvYWRlZCwgdW5sb2NrZWQNCm5weDAg b24gbW90aGVyYm9hcmQNCm5weDA6IElOVCAxNiBpbnRlcmZhY2UNCmltYXNr czogYmlvIGMwMDhjMDQwLCB0dHkgYzAwMzAwOWEsIG5ldCBjMDA2MDAwMA0K QklPUyBHZW9tZXRyaWVzOg0KIDA6MDI2YTdmM2YgMC4uNjE4PTYxOSBjeWxp bmRlcnMsIDAuLjEyNz0xMjggaGVhZHMsIDEuLjYzPTYzIHNlY3RvcnMNCiAx OjAzMzcxZjNmIDAuLjgyMz04MjQgY3lsaW5kZXJzLCAwLi4zMT0zMiBoZWFk cywgMS4uNjM9NjMgc2VjdG9ycw0KIDAgYWNjb3VudGVkIGZvcg0KRGV2aWNl IGNvbmZpZ3VyYXRpb24gZmluaXNoZWQuDQpicGY6IHR1bjAgYXR0YWNoZWQN CmJwZjogbG8wIGF0dGFjaGVkDQpDb25zaWRlcmluZyBGRlMgcm9vdCBmL3Mu DQpjaGFuZ2luZyByb290IGRldmljZSB0byB3ZDBhDQp3ZDBzMTogdHlwZSAw eDYsIHN0YXJ0IDYzLCBlbmQgPSAxMDI0MTI3LCBzaXplIDEwMjQwNjUgOiBP Sw0Kd2QwczI6IHR5cGUgMHhhNSwgc3RhcnQgMTAyNDEyOCwgZW5kID0gMzA2 NDMxOSwgc2l6ZSAyMDQwMTkyIDogT0sNCndkMHMzOiB0eXBlIDB4NjMsIHN0 YXJ0IDMwNjQzMjAsIGVuZCA9IDQwODAzODMsIHNpemUgMTAxNjA2NCA6IE9L DQp3ZDBzNDogdHlwZSAweDUsIHN0YXJ0IDQwODAzODQsIGVuZCA9IDQ5OTE2 MTUsIHNpemUgOTExMjMyIDogT0sNCndkMHM1OiB0eXBlIDB4Niwgc3RhcnQg NDA4MDQ0NywgZW5kID0gNDk5MTYxNSwgc2l6ZSA5MTExNjkgOiBPSw0Kd2Qx czE6IHR5cGUgMHg4MSwgc3RhcnQgNjMsIGVuZCA9IDEzMzA1NSwgc2l6ZSAx MzI5OTMgOiBPSw0Kd2QxczI6IHR5cGUgMHhhNSwgc3RhcnQgMTMzMDU2LCBl bmQgPSAxNjYzMTk5LCBzaXplIDE1MzAxNDQgOiBPSw0Kd2QxczE6IHR5cGUg MHg4MSwgc3RhcnQgNjMsIGVuZCA9IDEzMzA1NSwgc2l6ZSAxMzI5OTMgOiBP Sw0Kd2QxczI6IHR5cGUgMHhhNSwgc3RhcnQgMTMzMDU2LCBlbmQgPSAxNjYz MTk5LCBzaXplIDE1MzAxNDQgOiBPSw0K --0-960935415-887184795=:12470-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 00:44:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16905 for current-outgoing; Wed, 11 Feb 1998 00:44:27 -0800 (PST) (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 AAA16896 for ; Wed, 11 Feb 1998 00:44:24 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id BAA20464; Wed, 11 Feb 1998 01:44:10 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd020422; Wed Feb 11 01:44:01 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id BAA21978; Wed, 11 Feb 1998 01:43:56 -0700 (MST) From: Terry Lambert Message-Id: <199802110843.BAA21978@usr09.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: dg@root.com Date: Wed, 11 Feb 1998 08:43:56 +0000 (GMT) Cc: tlambert@primenet.com, jb@cimlogic.com.au, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199802110758.XAA15322@implode.root.com> from "David Greenman" at Feb 10, 98 11:58:21 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> There are far more instances where Kirk McKusick and other people > >> in-the-know have objected to the direction that Terry wants to take > >> us than there are in favor. > > > >I've talked to Kirk about many of the changes since I've been in the > >Bay Area, and you are misquoting him here. > > I have neither quoted nor paraphrased Kirk or anyone else in my last > message. What is your semantic definition for "Kirk McKusick and other people in-the-know have objected to the direction that Terry wants to take us"? I'll be happy to use that definition istead to describe what you said. > Those of us who have looked at making this change > realize that this is riddled with potential problems, however, especially > when code such as ufs_rename has to be rewritten. I don't even trust > Kirk (the author) to do this, so why would I trust you? Who do you trust to do it? Are they working on it? > On the other hand, there is general disagreement on changing the > symantics of advisory locking. Well, I've stated my reasons for it. So long as it keeps working, there's really no good reason not to, and a lot of good reasons to. I've explained one of them in great gory detail in my recent posting about the unionfs changes that have been proposed. > >I'll be happy to explain anything you have questions about. > > This is inconsistent with what you have said in the past which was > escentially that you had neither the time nor the willingness to explain > the changes you were proposing and that we should just take it on > faith that what you want to do is good. This is false. This seems to be is a paraphrase of one of Jordans previous complaints. In effect, you are complaining that because I can't persuade you, in a sufficiently small amount of words that you are willing to read them, that something is good, then it must not be good. I admit that I have fallen down on providing architecture documents to Nate; however, I have provided him with some information, and the main complaint was that it was too low level and assumed too much knowledge. I have to assume *some* knowledge. > >occur. The only rationale against these has been "we fear change, > >specifically in the form of divergence". Now that that's blown > >out, so long as it's possible to revert such changes if they are seen > >to have a detrimental effect, I don't see why there's a problem. > > Backing out changes after some amount of time has gone by (and thus the > code has been modified by other people for other reasons) is not a trivial > undertaking. If you are right, and my changes are bad, it will be immediately apparent (in that they will fail to operate). If they operate, you are no worse off than before, and you have someone actively working on an area of the system that has languished. 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 current" in the body of the message From owner-freebsd-current Wed Feb 11 00:48:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17420 for current-outgoing; Wed, 11 Feb 1998 00:48:10 -0800 (PST) (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 AAA17395; Wed, 11 Feb 1998 00:48:06 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id BAA19394; Wed, 11 Feb 1998 01:48:06 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd019380; Wed Feb 11 01:48:00 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id BAA22120; Wed, 11 Feb 1998 01:47:58 -0700 (MST) From: Terry Lambert Message-Id: <199802110847.BAA22120@usr09.primenet.com> Subject: PATCH.D: Kernel changes for NFS client and server locking To: fs@FreeBSD.ORG, current@FreeBSD.ORG Date: Wed, 11 Feb 1998 08:47:58 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the decription of two patches, to follow immeditely. These two patches are being submitted for review by a wider audioence to determine of they damage advisory locking semantics or other system functionality. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. ============================================================================== Description: The following two patches implement the majority of the necessary kernel code for supporting NFS client and server locking. I recommend that other *BSD's apply this against a -current FreeBSD tree, and then use that information to apply them against their own. FreeBSD has diverged greatly in the files these patches touch, despite claims to the contrary. Purpose: 1) Resubmit patches first submitted ~3 years ago. These patches are virtually unchanged, but have not been committed because they previously included bug fixes to other portions of the kernel that people (apparently) didn't want fixed. 2) Provide a small enough subset of patches at one time; the purpose of this is five-fold: a) It allows someone who has not spent their career (as I have) working on FS code to understand the nature of the changes, without me having to spend an equal amount of time as I have spent educating myself to educate them (this code is already ~3 years old; my research has progressed significantly beyond this point already). b) It increases the likelihood that they will be committed. c) It allows me to not have to merge ~1500 of my over 30,000 lines of diffs each time I update my kernel. d) It puts a damper on any forward progress I could make if all of my patches were committed, while I seperate this stuff out from my othe changes. e) It stretches out the time it's going to take to get them all committed, and generally slows down my research, since it increases the overall commit latency I must put up with. Admittedly, these last two are of questionable benefit to anyone but a wart on the tail of progress. 8-|. 3) Get feedback on whether or not this actually breaks anything for someone other than myself. It doesn't break things for me; I would be interested in the ruslts of anyone else's attempts at running the POSIX validation suite before and after these patches. 4) Provide a base from which Andrew and Doug can actually finish the implementation of rpc.lockd and the NFS client locking code, which will hopefully result in the first free and working NFS locking implementation. Jordan was going to finish this code for Kirk's class, but never did. 5) Various people at BSDI have been pestering me for these, off and on, for some time. 6) It might be nice if, for once, FreeBSD actually had something before Linux, for a change. Specific changes are: 1) Add preliminary NFS server locking support; the following fcntl() commands are added: F_RGETLK F_RSETLK F_RSETLKW F_CNVT F_UNLKSYS These are identical to the same commands in SunOS 4.1.3 2) Move VOP_ADVLOCK to a veto basis This is necessary for NFS client locking support. NFS client locking proxies local requests on the caller's behalf. 3) Add preliminary NFS client locking support. This consists of changing nfs_advlock to operate a veto basis. The ufs_advlock function is also changed so it will continue to function. 4) Add preliminary advisory locking to all filesystems. Before this patch, advisory locking was not supported on any FS other than a UFS derived FS and on NFS. 5) Seperate lock assertion from lock coelescence (see previous discussion over the past several days on the -current list). 6) Move the advisory lock list to hang off the in core vnode instead of the in core inode. This is consistent with the VOP_FINALVP discussion, and was necessary to support the veto-based VOP_ADVLOCK interface. 7) Modify vn_advlock() parameters and add vn_unlksys() support. The first is for seperation of lock commits for NFS client locking support, the second is for NFS server locking support. 8) Addition of lf_commit(). This allows a provisional lock to be committed (coelesced) or aborted (deasserted prior to coelesce). 10) Revision of lock debug dumps for use in kernel debugger. 11) Addition of a comment to union_vnops.c to note what is really taking place (necessary information for agregation support at a later date). 12) Removal of n_lockf from nfsnode. This is no longer necessary; lock lists are off the vnode now. 13) Removal of i_lockf from inode. This is no longer necessary; lock lists are off the vnode now. 14) Binary backward compatability is assured through the use of an oflock structure. Binary forward compatability is assured with an l_pad reservation of 4 longwords. 15) Copious comments 16) The fcntl.2 man page is updated to reflect these changes. ============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 00:51:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18234 for current-outgoing; Wed, 11 Feb 1998 00:51:32 -0800 (PST) (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 AAA18228 for ; Wed, 11 Feb 1998 00:51:29 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id BAA26267 for ; Wed, 11 Feb 1998 01:51:02 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd026257; Wed Feb 11 01:50:53 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id BAA22210 for current@freebsd.org; Wed, 11 Feb 1998 01:50:53 -0700 (MST) From: Terry Lambert Message-Id: <199802110850.BAA22210@usr09.primenet.com> Subject: PATCH.M To: current@FreeBSD.ORG Date: Wed, 11 Feb 1998 08:50:52 +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 These are the patches to the fcntl() man page to describe the NFS server side proxy locking interface. This manual page should be read and understood before applying the related code patches, which implement not only the server side locking semantics, but the advisory locking veto semantics necessary to enable support for NFS client locking. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. ============================================================================== Index: fcntl.2 =================================================================== RCS file: /b/cvstree/ncvs/src/lib/libc/sys/fcntl.2,v retrieving revision 1.11 diff -c -r1.11 fcntl.2 *** 1.11 1997/01/31 01:06:39 --- fcntl.2 1997/05/09 00:22:15 *************** *** 158,165 **** --- 158,171 ---- pid_t l_pid; /* lock owner */ short l_type; /* lock type: read/write, etc. */ short l_whence; /* type of l_start */ + long l_rsys; /* remote system id, or 0 for local*/ + long l_pad[4]; /* reserved */ }; .Ed + Note: the l_rsys fields and l_pad fields are not used for the local + versions of the locking commands for binary compatability with + previous versions of these commands. + .Pp The commands available for advisory record locking are as follows: .Bl -tag -width F_SETLKWX .It Dv F_GETLK *************** *** 190,197 **** .Dv (F_RDLCK) or exclusive (or write) locks, .Dv (F_WRLCK) , ! as well as remove either type of lock ! .Dv (F_UNLCK) . If a shared or exclusive lock cannot be set, .Fn fcntl returns immediately with --- 196,206 ---- .Dv (F_RDLCK) or exclusive (or write) locks, .Dv (F_WRLCK) , ! or remove either type of lock, ! .Dv (F_UNLCK) , ! as well as removing all locks for a given remote system id specified by ! .Fa l_rsys , ! .Dv (F_UNLKSYS) . If a shared or exclusive lock cannot be set, .Fn fcntl returns immediately with *************** *** 209,214 **** --- 218,262 ---- .Dv SA_RESTART (see .Xr sigaction 2 ) . + .It Dv F_RGETLK + Identical in operation to + .Dv F_GETLK + above, but is used to test locks on behalf of a remote system. The + value of + .Fa l_rsys + and + .Fa l_rpid + are also used in determining the uniqueness of the lock. This allows + a process to proxy lock services for a remote host or hosted server + environment. + .It Dv F_RSETLK + Identical in operation to + .Dv F_SETLK + above, but is used to assert locks on behalf of a remote system. The + value of + .Fa l_rsys + and + .Fa l_pid + are also used in determining the uniqueness of the lock. This allows + a process to proxy lock services for a remote host or hosted server + environment. + .It Dv F_RSETLKW + Identical in operation to + .Dv F_SETLKW + above, but is used to assert locks on behalf of a remote system. The + value of + .Fa l_rsys + and + .Fa l_pid + are also used in determining the uniqueness of the lock. This allows + a process to proxy lock services for a remote host or hosted server + environment. + .It Dv F_CNVT + Convert an NFS file handle into an open fd; this is used by the NFS + proxy locking process to get a local file handle on which proxy + requests can be made. This call is + .Xr rpc.lockd 8 + specific, and is not useful otherwise. .El .Pp When a shared lock has been set on a segment of a file, *************** *** 243,249 **** is negative, the result is undefined. The .Fa l_pid ! field is only used with .Dv F_GETLK to return the process ID of the process holding a blocking lock. After a successful --- 291,298 ---- is negative, the result is undefined. The .Fa l_pid ! field is used by the remote calls to pass the remote process identifier ! in, and with .Dv F_GETLK to return the process ID of the process holding a blocking lock. After a successful ============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 04:45:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02937 for current-outgoing; Wed, 11 Feb 1998 04:45:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA02918 for ; Wed, 11 Feb 1998 04:45:18 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id PAA12497; Wed, 11 Feb 1998 15:30:44 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id PAA03257; Wed, 11 Feb 1998 15:37:28 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802111237.PAA03257@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Tue, 10 Feb 1998 10:42:40 GMT." <199802101042.DAA25601@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Feb 1998 15:37:28 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > Please apply my nami/nameifree patches before attempting this. > > > > Where can I gen them? > > From the -current list archives, or in ~terry on freefall.freebsd.org. I didn't found the patches in list archives yet, I found only your announcement that you put the patches to ~terry on freefall. And I have no account on freefall. I believe you could create directory ~terry/public_html there, and move your patches to it. So people will able to easy get them from http://www.freebsd.org/~terry/. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 05:08:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05140 for current-outgoing; Wed, 11 Feb 1998 05:08:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05135 for ; Wed, 11 Feb 1998 05:08:18 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id FAA02308; Wed, 11 Feb 1998 05:08:15 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802111308.FAA02308@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: current@FreeBSD.ORG Subject: Hollywood (Re: PATCH.M ) In-reply-to: Your message of "Wed, 11 Feb 1998 08:50:52 GMT." <199802110850.BAA22210@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Feb 1998 05:08:15 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Terry, Where is code ? If you want me to test or check out the patches just let me know. Off Topic: Battlefield Hollywood: NT Vs Linux E. Kevin Hall wrote: > Hi Daryll. Some misinformation for you: This digital link claims > your recent cinematic masterpiece was rendered on NT. I thought I > might mention it; I hate misinformation like this. To save Daryll having to repeat himself too much, someone has put his canonical response to this whole thing on a web page - http://www.wibble.net/~sky/ ---- Daryll is a also the linux hacker responsible the Voodoo Chipset support on linux. ---- I sure hope that if someone decides to use FreeBSD in a major project such as the making of the Titanic that NFS works 8) Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 07:02:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17422 for current-outgoing; Wed, 11 Feb 1998 07:02:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mamba-e.gsfc.nasa.gov (mamba-f.gsfc.nasa.gov [128.183.245.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17414 for ; Wed, 11 Feb 1998 07:02:38 -0800 (PST) (envelope-from uhl@mamba-e.gsfc.nasa.gov) Received: (from uhl@localhost) by mamba-e.gsfc.nasa.gov (8.8.5/8.8.4) id KAA17171 for freebsd-current@FreeBSD.ORG; Wed, 11 Feb 1998 10:02:21 -0500 (EST) Date: Wed, 11 Feb 1998 10:02:21 -0500 (EST) From: George Uhl Message-Id: <199802111502.KAA17171@mamba-e.gsfc.nasa.gov> To: freebsd-current@FreeBSD.ORG Subject: boot.flp bug? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-MD5: bLvemd5r4ffzK1DFoX/EmQ== Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to install the latest 3.0-SNAP (2/10) from a diskette. I downloaded the boot.flp image and dd'ed it to the diskette. During the probing sequence while booting I get the following: | | V npx0 on motherboard npx0: INT 16 interface changing root device to fd0c rootfs is 1440 kbyte compiled in MFS vm_page_free: pindex(12), busy(0), PG_BUSY(0), hdd(0) panic: vm_page_free: freeing free page Causing my host to reboot. What gives? BTW, I tried the previous day's (2/9) for grins. Same effect. George Uhl Sending from the Land of the Free ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 07:40:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22111 for current-outgoing; Wed, 11 Feb 1998 07:40:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from obiwan.creative.net.au (obiwan.creative.net.au [203.56.168.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22093 for ; Wed, 11 Feb 1998 07:40:05 -0800 (PST) (envelope-from adrian@obiwan.creative.net.au) Received: from localhost (adrian@localhost) by obiwan.creative.net.au (8.8.8/8.8.5) with SMTP id XAA01791; Wed, 11 Feb 1998 23:39:18 +0800 (WST) Date: Wed, 11 Feb 1998 23:39:17 +0800 (WST) From: Adrian Chadd To: Amancio Hasty cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: Hollywood (Re: PATCH.M ) In-Reply-To: <199802111308.FAA02308@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Feb 1998, Amancio Hasty wrote: > I sure hope that if someone decides to use FreeBSD in a major project > such as the making of the Titanic that NFS works 8) I just read the nt/win95 thread and I'm trying to figure out where it says -current has to be stable. Linux isn't stable all the time. I mean hey, I can give you so many examples where someone changed something in the kernel source, the kernel goes out, and then things break. And then Linus announces a new kernel 12 hours later with the 'fix'. But its tried. If she no work, then they back the change out. Its worked for them.. you try the ideas out. If it doesn't work in -current, you back it out. Or fix it until it does. Then you bring it into -release. Or have I like missed something totally about how its meant to work? -- Adrian Chadd | "I used to be thin, handsome and smart. | Then I discovered UNIX." | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 07:44:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22611 for current-outgoing; Wed, 11 Feb 1998 07:44:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA22577 for ; Wed, 11 Feb 1998 07:43:56 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA07387; Thu, 12 Feb 1998 00:43:37 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id AAA28888; Thu, 12 Feb 1998 00:51:25 +0900 (JST) Message-Id: <199802111551.AAA28888@zodiac.mech.utsunomiya-u.ac.jp> To: current@FreeBSD.ORG Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: recent syscons update Date: Thu, 12 Feb 1998 00:51:24 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have committed quite a few fixes/improvements to syscons.c in a separate batches: v1.248: miscellaneous fixes v1.249: screen update related fixes v1.250: font loading fixes v1.251: mouse cursor related fixes If you find any problems with syscons, please report which version of syscons.c you are using, and try to locate the offending modification by backing out the above changes one by one. Thank you for your cooperation. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 07:54:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24882 for current-outgoing; Wed, 11 Feb 1998 07:54:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24762 for ; Wed, 11 Feb 1998 07:53:52 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id QAA02364; Wed, 11 Feb 1998 16:50:19 +0100 (CET) Message-ID: <19980211165018.48435@cons.org> Date: Wed, 11 Feb 1998 16:50:18 +0100 From: Martin Cracauer To: Bruce Evans Cc: cracauer@cons.org, freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/bin/sh jobs.c References: <199802110106.MAA00738@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199802110106.MAA00738@godzilla.zeta.org.au>; from Bruce Evans on Wed, Feb 11, 1998 at 12:06:49PM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199802110106.MAA00738@godzilla.zeta.org.au>, Bruce Evans wrote: > >> (c) #!/bin/sh > >> (while :; do catchint; done) > >> > >> Now there is a subshell. It must be killed by SIGINT. (?) > > > >For me (our sh and bash), the whole script (outer shell, inner shell, > >catchint) is terminated on SIGINT. It's the way it should be, IMHO. > > Actually, it doesn't for your version of sh, or bash. At least for > your version of sh, the subshell waits for catchint, and then doesn't > exit because catchint exits with a normal status. There must be some misunderstanding here. If catchint is a program with SIGINT => SIGN_DFL, all versions of sh (original, your, mine, bash) exit this script (test10.sh from testsuite) immedeatly: #!./testshell echo 'You should be able to end the script with one SIGINT' (while :; do wc /kernel > /dev/null ; done) The first SIGINT kills wc, the inner shell and the outer shell. If you mean catchint to be a program that directs SIGINT to its own routine and not exit on it, then you're right, this loop isn't breakable by SIGINT if the shell behaves the way I think is right. If an application catches SIGINT for its own purposes (i.e. emacs), then - in my opinion - the surrounding shellscript should not behave different when a) the catchint program ends without using SIGINT and b) the catchint program ends and has used SIGINT while it was running. For an emacs user, SIGINT/SIGQUIT are just normal keystrokes that shouldn't have any effect on other programs than emacs. This is the only way to ensure that an application we can assure that system(2) does what the application writer expects if he/she calls it with $EDITOR. And it's the way the SunOS /bin/sh works, not without a reason, I think. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer cracauer@wavehh.hanse.de (batched, preferred for large mails) Tel.: (daytime) +4940 41478712 Fax.: (daytime) +4940 41478715 Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 Paper: (private) Waldstrasse 200, 22846 Norderstedt, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 08:41:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00680 for current-outgoing; Wed, 11 Feb 1998 08:41:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00663 for ; Wed, 11 Feb 1998 08:41:32 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id KAA10646; Wed, 11 Feb 1998 10:18:58 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id KAA03867; Wed, 11 Feb 1998 10:18:26 -0600 Message-ID: <19980211101825.53750@right.PCS> Date: Wed, 11 Feb 1998 10:18:26 -0600 From: Jonathan Lemon To: Adrian Chadd Cc: Amancio Hasty , Terry Lambert , current@FreeBSD.ORG Subject: Re: Hollywood (Re: PATCH.M ) References: <199802111308.FAA02308@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Adrian Chadd on Feb 02, 1998 at 11:39:17PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Feb 02, 1998 at 11:39:17PM +0800, Adrian Chadd wrote: > But its tried. If she no work, then they back the change out. Its worked > for them.. you try the ideas out. If it doesn't work in -current, you back > it out. Or fix it until it does. Then you bring it into -release. Or have > I like missed something totally about how its meant to work? I think so. From my understanding, -current isn't intended to be a dumping ground for new features, it's more like a final shakedown where the bugs can get ironed out. If you have a new feature, (like the CAM work, timing wheel changes, or SMP ability) then these should be hammered out in the developer's own release branch until they are stable. Then, after others have had a chance to test them out as well, they are brought into -current. Of course, at this point, several things may break, since the developer may not have been able to test all the various kernel permutations on their machine. But usually, the fundamental code is fairly stable, and it it just a matter of squashing some last bugs, not making major changes to the code. > Error: end tag detected with no corresponding opening tag. :-) -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 08:55:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02415 for current-outgoing; Wed, 11 Feb 1998 08:55:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from obiwan.creative.net.au (obiwan.creative.net.au [203.56.168.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02397 for ; Wed, 11 Feb 1998 08:55:43 -0800 (PST) (envelope-from adrian@obiwan.creative.net.au) Received: from localhost (adrian@localhost) by obiwan.creative.net.au (8.8.8/8.8.5) with SMTP id AAA02001; Thu, 12 Feb 1998 00:55:15 +0800 (WST) Date: Thu, 12 Feb 1998 00:55:15 +0800 (WST) From: Adrian Chadd To: Jonathan Lemon cc: current@FreeBSD.ORG Subject: Re: Hollywood (Re: PATCH.M ) In-Reply-To: <19980211101825.53750@right.PCS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Feb 1998, Jonathan Lemon wrote: > On Feb 02, 1998 at 11:39:17PM +0800, Adrian Chadd wrote: > > But its tried. If she no work, then they back the change out. Its worked > > for them.. you try the ideas out. If it doesn't work in -current, you back > > it out. Or fix it until it does. Then you bring it into -release. Or have > > I like missed something totally about how its meant to work? > > I think so. From my understanding, -current isn't intended to be a dumping > ground for new features, it's more like a final shakedown where the bugs > can get ironed out. If you have a new feature, (like the CAM work, timing > wheel changes, or SMP ability) then these should be hammered out in the > developer's own release branch until they are stable. Then, after others > have had a chance to test them out as well, they are brought into -current. I assume Terry wouldn't be putting forward patches that didn't work. And hadn't been throughly tested. > > Of course, at this point, several things may break, since the developer may > not have been able to test all the various kernel permutations on their > machine. But usually, the fundamental code is fairly stable, and it it just > a matter of squashing some last bugs, not making major changes to the code. If I mention VM code would someone kill me? :-) (Not taking a personal attack at anyone here, so please don't read it as such.. :) Its not like stuff has been changed in -current before that hasn't horrendously broken things in a big way and take ages to fix. > > > > Error: end tag detected with no corresponding opening tag. :-) Damn. And I deleted the top while editing the email. Thanks for reminding me. :) Now, I wonder whats going to happen in the 8 hours I'll be sleeping.. :) Adrian -- Adrian Chadd | "I used to be thin, handsome and smart. | Then I discovered UNIX." | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 09:10:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04294 for current-outgoing; Wed, 11 Feb 1998 09:10:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04280 for ; Wed, 11 Feb 1998 09:10:16 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA04905; Thu, 12 Feb 1998 04:05:41 +1100 Date: Thu, 12 Feb 1998 04:05:41 +1100 From: Bruce Evans Message-Id: <199802111705.EAA04905@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: cvs commit: src/bin/sh jobs.c Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> (c) #!/bin/sh >> >> (while :; do catchint; done) >> >> >> >> Now there is a subshell. It must be killed by SIGINT. (?) >> > >> >For me (our sh and bash), the whole script (outer shell, inner shell, >> >catchint) is terminated on SIGINT. It's the way it should be, IMHO. >> >> Actually, it doesn't for your version of sh, or bash. At least for >> your version of sh, the subshell waits for catchint, and then doesn't >> exit because catchint exits with a normal status. > >There must be some misunderstanding here. > >If catchint is a program with SIGINT => SIGN_DFL, all versions of sh >(original, your, mine, bash) exit this script (test10.sh from >testsuite) immedeatly: It's not. It's a program that catches SIGINT and exits normally (i.e., with a non-signal status) in its SIGINT handler. >#!./testshell >echo 'You should be able to end the script with one SIGINT' >(while :; do wc /kernel > /dev/null ; done) wc doesn't catch SIGINT. >The first SIGINT kills wc, the inner shell and the outer shell. Not quite. The first SIGINT kills wc, but is ignored by both shells (probably incorrectly by at least the inner shell). Then the inner shell notices that wc was killed with a SIGINT and relays this SIGINT to itself by killing itself with a SIGINT. This kills it completely because it is no longer ignoring SIGINT. Then the outer shell notices that the inner shell was killed by a SIGINT and relays the SIGINT to itself, etc. Relaying is not done for signals other than SIGINT, so test10.sh can't be killed by SIGQUIT with your version of sh. >If you mean catchint to be a program that directs SIGINT to its own >routine and not exit on it, then you're right, this loop isn't >breakable by SIGINT if the shell behaves the way I think is right. Yes, if the shell behaves the way I think is wrong. >If an application catches SIGINT for its own purposes (i.e. emacs), >then - in my opinion - the surrounding shellscript should not behave >different when a) the catchint program ends without using SIGINT and >b) the catchint program ends and has used SIGINT while it was running. If a program wants to use SIGINT, then it should avoid sending it to the entire process group. This prevents it from using SIGINTs generated by the tty. >This is the only way to ensure that an application we can assure that >system(2) does what the application writer expects if he/she calls it >with $EDITOR. Hmm. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 09:28:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06945 for current-outgoing; Wed, 11 Feb 1998 09:28:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA06937 for ; Wed, 11 Feb 1998 09:28:29 -0800 (PST) (envelope-from handy@sag.space.lockheed.com) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA08897; Wed, 11 Feb 1998 09:16:49 -0800 Date: Wed, 11 Feb 1998 09:16:49 -0800 (PST) From: Brian Handy To: Adrian Chadd Cc: Jonathan Lemon , current@FreeBSD.ORG Subject: Re: Hollywood (Re: PATCH.M ) In-Reply-To: Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> [A vigorous discussion of the purpose of the -current branch] >> >> Of course, at this point, several things may break, since the developer may >> not have been able to test all the various kernel permutations on their >> machine. But usually, the fundamental code is fairly stable, and it it just >> a matter of squashing some last bugs, not making major changes to the code. > >If I mention VM code would someone kill me? :-) (Not taking a personal >attack at anyone here, so please don't read it as such.. :) [Brian swiftly jumps in to feed the fire] Hmm, I remember to Jordan referring to the lite2 merge as "Black Sunday"... :-) Over the ages, I've seen probably whole *months* where -current was totally unreliable dumping ground, and although it's a noble idea to think everything that goes into -current is well tested and just needs a few bugs ironed out, that's not necessarily always the case, and IMHO it shouldn't be. As one of my Physics profs once said, during a particularly brutal homework set: "I relate your experience here to growing plants. They grow most when they're under a great deal of stress." I identify with that, and if you want to see FreeBSD move forward in something other than tinny incremental steps, I think once in a while it's time to kick the tires really hard and see what happens. Lite2 did that, I think SMP did it to a lesser extent, ELF is going to brutalize the -current branch. I imagine Terry's patches would fall somewhere between the extremes. Now, I also agree with Nate, in that it would sure be nice if people had at least a *vague* idea what his stuff did, but it's couched in such extreme lingo that nobody can, and Terry has a hard time boiling it down to something reasonable. Things have progressed significantly, though, in that people are talking about his work now. I claim this is new. If Terry can spend a bit more time with a committer and give them a warm feeling about what the patches *might* do, I suspect they might be worth getting into the system, if the product is as good as the hype. There has been noise about how "but this isn't how we wanted to do this change", but to Terry's advantage he's actually *done* the work. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 09:36:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08018 for current-outgoing; Wed, 11 Feb 1998 09:36:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA08010 for ; Wed, 11 Feb 1998 09:36:15 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0y2g4k-0003Ni-00; Wed, 11 Feb 1998 10:35:58 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id KAA22807; Wed, 11 Feb 1998 10:36:07 -0700 (MST) Message-Id: <199802111736.KAA22807@harmony.village.org> To: Adrian Chadd Subject: Re: Hollywood (Re: PATCH.M ) Cc: Jonathan Lemon , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 12 Feb 1998 00:55:15 +0800." References: Date: Wed, 11 Feb 1998 10:36:07 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Adrian Chadd writes: : I assume Terry wouldn't be putting forward patches that didn't work. And : hadn't been throughly tested. For some parts of the kernel there are additional requirements to amke sure that we're all haded in the right direction. Terry's patches are very interesting, but they are in an area that is hard to explain, as well as hard to understand. This presenets a barrier to having the patches included. I don't know the specifics of this, so I'll not speculate further on the interactions at work here. : If I mention VM code would someone kill me? :-) (Not taking a personal : attack at anyone here, so please don't read it as such.. :) : : Its not like stuff has been changed in -current before that hasn't : horrendously broken things in a big way and take ages to fix. My view of current is that things that should be in a future release of FreeBSD go there. If there are nit, bugs, crashses in the work that is committed, so be it. So long as those folks are comitted to fixing it or backing it out in a timely basis, I don't care if things are busted for a day or two here or there. The VM code I think is a special case. It is so complicated that it has to have lots of testers as soon as possible to shake out the problems. Also, the person making the changes has a stellar reputation for taking responsibility for making things work and has done some very impressive things in the FreeBSD world for a long time. If I were to start making such extensive changes to the VM tromorrow, I'd likely have multiple people ask me to prove myself (or at least my code) before it went in (and stayed in). However, no one seems to blink much when I commit buffer overflow fixes (even in large numbers of files) because I've done that many times. Sometimes I have the pointy hat thrust upon me for a commit that I've made, but in those cases I've always backed out the changes until I could fix the issue at hand. -current is for experimental things, but not too radically experimental. -current is the place for new ideas and code to mature, but isn't a dumping ground for all new code. There is a balance that needs to be maintained. This balance isn't always 100% technical. Sometimes there are polical reasons for doing things. lpr/lpd and sendmail come mind as programs that are known to be dangerous, but are still the best solution to the problems available given all considerations. Anyway, I'm not a core team member. These are just my views from interacting with the CVS tree for a long time and some private release engineerig philosophy that I've evolved in the jobs I've had over the years. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 09:54:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10469 for current-outgoing; Wed, 11 Feb 1998 09:54:34 -0800 (PST) (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 JAA10462 for ; Wed, 11 Feb 1998 09:54:25 -0800 (PST) (envelope-from dyson@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA09484; Wed, 11 Feb 1998 12:53:47 -0500 (EST) (envelope-from dyson) Message-Id: <199802111753.MAA09484@dyson.iquest.net> Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <199802102132.NAA09318@implode.root.com> from David Greenman at "Feb 10, 98 01:32:38 pm" To: dg@root.com Date: Wed, 11 Feb 1998 12:53:47 -0500 (EST) Cc: jb@cimlogic.com.au, tlambert@primenet.com, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My opinion is slightly different than DG, but with pretty much the same results. We need someone to referee Terry's work. Some of his changes are structurally significant, and I simply do not have the energy or wherewithall to work his stuff in. Seldom are such changes bug-free or problem-free, and I am already 100% committed. Perhaps there are some disagreements on specific changes architecturally, but the eventual direction that Terry is suggesting is correct. If someone who is unbiased and not in an advocacy position who is willing to understand the stuff, and to be appropriately critical, I would be all for what Terry is generally trying to do. At least Terry is trying (and probably doing a pretty good job), but we do need that review process for radical changes. David Greenman said: > >Terry Lambert wrote: > >> Are there any "FS dudes" with commit priviledges out there? (Hey! > >> Why haven't you been fixing these same problems? 8-)). > >> > >> I think this is the problem Jordan. FreeBSD doesn't have any FS dudes > >> (being defined as people who *live* FS code, like McKusick, Heidimann, > >> or, in fact, me [No, I'm not comparing myself to them]). > > > >What is the problem with you having commit priviledges? > > In many cases, Terry's solutions to the problems that he is trying to > solve aren't the ones we want to adopt. There are far more instances where > Kirk McKusick and other people in-the-know have objected to the direction > that Terry wants to take us than there are in favor. Terry's unwillingness > to carefully explain/justify the changes that he proposes in a manor that > reasonable kernel developers can understand has further resulted in a > serious lack of trust. For these reasons it's the unanimous opinion of > the core team that Terry not be given commit privileges. > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project > -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 10:02:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11725 for current-outgoing; Wed, 11 Feb 1998 10:02:42 -0800 (PST) (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 KAA11719 for ; Wed, 11 Feb 1998 10:02:39 -0800 (PST) (envelope-from dyson@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id NAA09523; Wed, 11 Feb 1998 13:01:52 -0500 (EST) (envelope-from dyson) Message-Id: <199802111801.NAA09523@dyson.iquest.net> Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <199802110758.XAA15322@implode.root.com> from David Greenman at "Feb 10, 98 11:58:21 pm" To: dg@root.com Date: Wed, 11 Feb 1998 13:01:52 -0500 (EST) Cc: tlambert@primenet.com, jb@cimlogic.com.au, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman said: > > This is inconsistent with what you have said in the past which was > escentially that you had neither the time nor the willingness to explain > the changes you were proposing and that we should just take it on > faith that what you want to do is good. > > >occur. The only rationale against these has been "we fear change, > >specifically in the form of divergence". Now that that's blown > >out, so long as it's possible to revert such changes if they are seen > >to have a detrimental effect, I don't see why there's a problem. > > Backing out changes after some amount of time has gone by (and thus the > code has been modified by other people for other reasons) is not a trivial > undertaking. > To address DG's concerns, and the bona-fide problems that Terry is trying to solve, we need someone who has the time, energy and ability to field the problems that *WILL* occur. It is not a simple undertaking to make the kind of changes that an advocate like Terry has, where there is no review process. Terry is bright, and probably brighter than me (so he is brighter than dim :-)). That doesn't mean that DG, PHK, BDE or me can accept his changes without review by at least a trusted third-party. My bread and butter is based upon FreeBSD existing, and I just don't have the time to do Terry's stuff justice. Perhaps we need an organized effort (even including Kirk in on this) to make sure that Terry's changes are indeed fixing the problems, and not just trading one set for another. I do know about the kind of subtile breakage that can occur when working on a critical subsystem (e.g. VM or even parts of the VFS system), and we need to move forward, but oh so carefully... -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 10:14:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14258 for current-outgoing; Wed, 11 Feb 1998 10:14:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14253 for ; Wed, 11 Feb 1998 10:14:34 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA02976; Wed, 11 Feb 1998 10:49:23 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA29341; Wed, 11 Feb 1998 10:49:15 -0700 Date: Wed, 11 Feb 1998 10:49:15 -0700 Message-Id: <199802111749.KAA29341@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: dg@root.com, jb@cimlogic.com.au, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <199802110843.BAA21978@usr09.primenet.com> References: <199802110758.XAA15322@implode.root.com> <199802110843.BAA21978@usr09.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I admit that I have fallen down on providing architecture documents > to Nate; however, I have provided him with some information, and the > main complaint was that it was too low level and assumed too much > knowledge. I have to assume *some* knowledge. What you provided to me was a political document riddled with 'this is why I did this', and what I asked for was a technical document that explained *what* you were doing, not why. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 11:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27811 for current-outgoing; Wed, 11 Feb 1998 11:22:29 -0800 (PST) (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 LAA27800 for ; Wed, 11 Feb 1998 11:22:25 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id LAA21018; Wed, 11 Feb 1998 11:22:13 -0800 (PST) Message-Id: <199802111922.LAA21018@implode.root.com> To: Eivind Eklund cc: tlambert@primenet.com, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-reply-to: Your message of "Wed, 11 Feb 1998 20:14:15 +0100." <19980211201414.31767@follo.net> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Feb 1998 11:22:13 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Have anybody checked how much it would cost to pay McKusick >consultancy fees to review and commit (if viable) Terrys changes? > >Would this be a solution you'd allow if monetary feasible, David? Yes. I trust Kirk's judgement completely. ...but I doubt that Kirk is for hire. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 11:25:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28404 for current-outgoing; Wed, 11 Feb 1998 11:25:24 -0800 (PST) (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 LAA28399 for ; Wed, 11 Feb 1998 11:25:20 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id LAA21044; Wed, 11 Feb 1998 11:24:51 -0800 (PST) Message-Id: <199802111924.LAA21044@implode.root.com> To: Adrian Chadd cc: Jonathan Lemon , current@FreeBSD.ORG Subject: Re: Hollywood (Re: PATCH.M ) In-reply-to: Your message of "Thu, 12 Feb 1998 00:55:15 +0800." From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Feb 1998 11:24:51 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I assume Terry wouldn't be putting forward patches that didn't work. And >hadn't been throughly tested. In fact, I can't recall a time when it was the case that Terry's patches both compiled cleanly and worked without problems. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 11:27:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28854 for current-outgoing; Wed, 11 Feb 1998 11:27:29 -0800 (PST) (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 LAA28803; Wed, 11 Feb 1998 11:27:13 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id TAA28714; Wed, 11 Feb 1998 19:14:25 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id UAA20015; Wed, 11 Feb 1998 20:14:15 +0100 (MET) Message-ID: <19980211201414.31767@follo.net> Date: Wed, 11 Feb 1998 20:14:15 +0100 From: Eivind Eklund To: dyson@FreeBSD.ORG Cc: dg@root.com, tlambert@primenet.com, jb@cimlogic.com.au, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs References: <199802110758.XAA15322@implode.root.com> <199802111801.NAA09523@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199802111801.NAA09523@dyson.iquest.net>; from John S. Dyson on Wed, Feb 11, 1998 at 01:01:52PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 11, 1998 at 01:01:52PM -0500, John S. Dyson wrote: > Terry is bright, and probably brighter than me (so he is brighter than > dim :-)). That doesn't mean that DG, PHK, BDE or me can accept his > changes without review by at least a trusted third-party. My bread > and butter is based upon FreeBSD existing, and I just don't have the > time to do Terry's stuff justice. > > Perhaps we need an organized effort (even including Kirk in on this) > to make sure that Terry's changes are indeed fixing the problems, > and not just trading one set for another. I do know about the kind > of subtile breakage that can occur when working on a critical subsystem > (e.g. VM or even parts of the VFS system), and we need to move forward, > but oh so carefully... Have anybody checked how much it would cost to pay McKusick consultancy fees to review and commit (if viable) Terrys changes? Would this be a solution you'd allow if monetary feasible, David? Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 11:33:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00627 for current-outgoing; Wed, 11 Feb 1998 11:33:40 -0800 (PST) (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 LAA00621 for ; Wed, 11 Feb 1998 11:33:34 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA04739; Wed, 11 Feb 1998 12:33:25 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp01.primenet.com, id smtpd004703; Wed Feb 11 12:33:22 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id MAA08353; Wed, 11 Feb 1998 12:33:14 -0700 (MST) From: Terry Lambert Message-Id: <199802111933.MAA08353@usr07.primenet.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs To: nate@mt.sri.com (Nate Williams) Date: Wed, 11 Feb 1998 19:33:14 +0000 (GMT) Cc: tlambert@primenet.com, dg@root.com, jb@cimlogic.com.au, jkh@time.cdrom.com, jbryant@unix.tfs.net, freebsd-current@FreeBSD.ORG In-Reply-To: <199802111749.KAA29341@mt.sri.com> from "Nate Williams" at Feb 11, 98 10:49:15 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 admit that I have fallen down on providing architecture documents > > to Nate; however, I have provided him with some information, and the > > main complaint was that it was too low level and assumed too much > > knowledge. I have to assume *some* knowledge. > > What you provided to me was a political document riddled with 'this is > why I did this', and what I asked for was a technical document that > explained *what* you were doing, not why. I provided you with a technical document, and you had me cut it down until it was a fluff piece. You either want an architecture document, or you don't. You were asking me to defend my design decisions in such a way as to give so little information that they would appear to be bad decisions. 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 current" in the body of the message From owner-freebsd-current Wed Feb 11 11:37:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01520 for current-outgoing; Wed, 11 Feb 1998 11:37:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01503 for ; Wed, 11 Feb 1998 11:37:23 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (markham.southpeak.com [192.58.185.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id OAA15624 for ; Wed, 11 Feb 1998 14:37:09 -0500 (EST) Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA23551; Wed, 11 Feb 1998 14:37:09 -0500 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA20502; Wed, 11 Feb 1998 14:37:09 -0500 Message-Id: <199802111937.AA20502@iluvatar.unx.sas.com> Subject: Possible BUG in vfs_bio.c/brelse() line 643 To: freebsd-current@FreeBSD.ORG Date: Wed, 11 Feb 1998 14:37:08 -0500 (EST) 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 believe the following is a bug in vfs_bio.c/brelse() version 1.147 and the following change should be committed. 643c643 < if (bp->b_flags && (B_INVAL | B_RELBUF)) --- > if (bp->b_flags & (B_INVAL | B_RELBUF)) I always did like those if (1) conditions. Comments? Critiques? thanks, John -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 11:42:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02979 for current-outgoing; Wed, 11 Feb 1998 11:42:51 -0800 (PST) (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 LAA02965 for ; Wed, 11 Feb 1998 11:42:48 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id MAA01251; Wed, 11 Feb 1998 12:42:47 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd001230; Wed Feb 11 12:42:45 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id MAA08969; Wed, 11 Feb 1998 12:42:41 -0700 (MST) From: Terry Lambert Message-Id: <199802111942.MAA08969@usr07.primenet.com> Subject: Re: Hollywood (Re: PATCH.M ) To: dg@root.com Date: Wed, 11 Feb 1998 19:42:41 +0000 (GMT) Cc: adrian@obiwan.creative.net.au, jlemon@americantv.com, current@FreeBSD.ORG In-Reply-To: <199802111924.LAA21044@implode.root.com> from "David Greenman" at Feb 11, 98 11:24:51 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I assume Terry wouldn't be putting forward patches that didn't work. And > >hadn't been throughly tested. > > In fact, I can't recall a time when it was the case that Terry's patches > both compiled cleanly and worked without problems. You don't remember the 100+ patches in the patchkit? When FreeBSD boots, it uses my init_main.c. SYSINIT was *my* baby, as is the kernel process starting code used by updated (now syncd), etc.. You are using my reference counting changes to mount.c. You are using my LKM code; if you had problems, it's because you waited so long, and then acquired it from NetBSD instead of me. But you are right; I don't have the luxury that committers have, in being able to cvs update directly from Freefall, commit the changes, and turn the process around in a short enough time that nobody notices the breakage. People actually notice my mistakes, but it's the fault of the process *you've* imposed, not because my code is different than anyone elses (well, I tend to touch more things at once; that's what happens when you look at big pictures -- that's the same problem everyone else who looks at big pictures has). PS: Did someone specifically kill the mailing of my PATCH.C that contained the actual patches? 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 current" in the body of the message From owner-freebsd-current Wed Feb 11 11:44:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03381 for current-outgoing; Wed, 11 Feb 1998 11:44:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03374 for ; Wed, 11 Feb 1998 11:44:54 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA03758; Wed, 11 Feb 1998 12:43:34 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA29812; Wed, 11 Feb 1998 12:43:32 -0700 Date: Wed, 11 Feb 1998 12:43:32 -0700 Message-Id: <199802111943.MAA29812@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), freebsd-current@FreeBSD.ORG Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <199802111933.MAA08353@usr07.primenet.com> References: <199802111749.KAA29341@mt.sri.com> <199802111933.MAA08353@usr07.primenet.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert writes: > > > I admit that I have fallen down on providing architecture documents > > > to Nate; however, I have provided him with some information, and the > > > main complaint was that it was too low level and assumed too much > > > knowledge. I have to assume *some* knowledge. > > > > What you provided to me was a political document riddled with 'this is > > why I did this', and what I asked for was a technical document that > > explained *what* you were doing, not why. > > I provided you with a technical document, and you had me cut it > down until it was a fluff piece. No, I had you explain everything to bring it down to an audience that hadn't been doing 'FS design and implementation for over 10 years.' > You either want an architecture document, or you don't. I wanted you to explain the issues behind the FS, so that *I* (and others) could understand the current design, and then understand why it was lacking. > You were > asking me to defend my design decisions in such a way as to give > so little information that they would appear to be bad decisions. No I wasn't. The implication all along was 'FS 101', so that I and a number of other folks could be brought up to speed on FS design, and *AFTER* we understood the basic terminology and such we could be shown the current system and then *AFTER* what was wrong with it and then *AFTER* we could see how your patches fixed it. >From the *beginning* it was called FS 101, not 'Why Terry's patches should go into FreeBSD'. I've heard alot of reason why your patches should go into FreeBSD from a political point of view, and even architectural at times when I took the time to wade through the rhetoric, but not *ONCE* have you explained the basics. Other may understand the basics, but I and many others don't, If you aren't willing to do that, then don't say you are. If you want, I can't dig up the public email you sent saying you were willing to 'teach' people about FS. Teaching != Preaching, and the document you sent me was a sermon, not a technical document. I've got megabytes of FS sermons from you on-line in my mail archives, so I don't need any more. What I am willing to do is 'learn', so that you and I both get something out of this. You get your patches integrated *AND* an advocate. What I get is knowledge on what I consider to be an extremely interesting topic (which I had planned to do my Master's on until my current job stole me away.;) Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 11:50:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04344 for current-outgoing; Wed, 11 Feb 1998 11:50:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04227 for ; Wed, 11 Feb 1998 11:49:56 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.8/8.8.7) id VAA22493; Wed, 11 Feb 1998 21:49:36 +0200 (SAT) From: John Hay Message-Id: <199802111949.VAA22493@zibbi.mikom.csir.co.za> Subject: Re: Hollywood (Re: PATCH.M ) In-Reply-To: <199802111942.MAA08969@usr07.primenet.com> from Terry Lambert at "Feb 11, 98 07:42:41 pm" To: tlambert@primenet.com (Terry Lambert) Date: Wed, 11 Feb 1998 21:49:36 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > PS: Did someone specifically kill the mailing of my PATCH.C that > contained the actual patches? > > > Terry Lambert > terry@lambert.org Probably majordomo himself ... if it was more than 40k. Well that was what it did with mine a while back. :-) John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 11:51:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04486 for current-outgoing; Wed, 11 Feb 1998 11:51:14 -0800 (PST) (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 LAA04472 for ; Wed, 11 Feb 1998 11:51:03 -0800 (PST) (envelope-from dyson@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id OAA10458; Wed, 11 Feb 1998 14:50:51 -0500 (EST) (envelope-from dyson) Message-Id: <199802111950.OAA10458@dyson.iquest.net> Subject: Re: Possible BUG in vfs_bio.c/brelse() line 643 In-Reply-To: <199802111937.AA20502@iluvatar.unx.sas.com> from "John W. DeBoskey" at "Feb 11, 98 02:37:08 pm" To: jwd@unx.sas.com (John W. DeBoskey) Date: Wed, 11 Feb 1998 14:50:51 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John W. DeBoskey said: > Hi, > > I believe the following is a bug in vfs_bio.c/brelse() version 1.147 > and the following change should be committed. > > 643c643 > < if (bp->b_flags && (B_INVAL | B_RELBUF)) > --- > > if (bp->b_flags & (B_INVAL | B_RELBUF)) > > I always did like those if (1) conditions. > > Comments? Critiques? > && in this case is very bad. I cannot make the change, but whomever has commit privs, and can do it right now, should change the && to &. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 12:01:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07217 for current-outgoing; Wed, 11 Feb 1998 12:01:04 -0800 (PST) (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 MAA07209 for ; Wed, 11 Feb 1998 12:01:00 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id MAA21439; Wed, 11 Feb 1998 12:00:38 -0800 (PST) Message-Id: <199802112000.MAA21439@implode.root.com> To: Terry Lambert cc: adrian@obiwan.creative.net.au, jlemon@americantv.com, current@FreeBSD.ORG Subject: Re: Hollywood (Re: PATCH.M ) In-reply-to: Your message of "Wed, 11 Feb 1998 19:42:41 GMT." <199802111942.MAA08969@usr07.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Feb 1998 12:00:38 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >I assume Terry wouldn't be putting forward patches that didn't work. And >> >hadn't been throughly tested. >> >> In fact, I can't recall a time when it was the case that Terry's patches >> both compiled cleanly and worked without problems. > >You don't remember the 100+ patches in the patchkit? Oh, yes, I remember *those*. Case in point. :-) >When FreeBSD boots, it uses my init_main.c. SYSINIT was *my* baby, >as is the kernel process starting code used by updated (now syncd), >etc.. Yes, and I recall that SYSINIT was broken and took some frobbing by Julian to get it to work. I might also mention that some people, myself included, aren't entirely satisfied with the direction that SYSINIT has taken us. For one thing, it's made it much more difficult to debug the system during startup and has made it near impossible to see the pathologic interaction between various random users of it spread out over dozens of kernel source files. It reminds me of DEC's 'sysman' utility replacing the standard system startup script, or the SysV model - you could never figure out exactly what has happend or predict what will happen. >You are using my LKM code; if you had problems, it's because you >waited so long, and then acquired it from NetBSD instead of me. Unfortunately, you're right. I'm sure even you will agree that it is not much more than a proof of concept and falls way short of the needs of any sort of production LKM system. Look, I'm not interested in putting you down in public. This sort of pissing match benefits neither of us. >PS: Did someone specifically kill the mailing of my PATCH.C that > contained the actual patches? No, but I didn't get a copy of it, either. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 12:06:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08411 for current-outgoing; Wed, 11 Feb 1998 12:06:13 -0800 (PST) (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 MAA08394 for ; Wed, 11 Feb 1998 12:06:10 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id NAA07251; Wed, 11 Feb 1998 13:06:06 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd007228; Wed Feb 11 13:06:00 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id NAA10426; Wed, 11 Feb 1998 13:05:57 -0700 (MST) From: Terry Lambert Message-Id: <199802112005.NAA10426@usr07.primenet.com> Subject: Re: Hollywood (Re: PATCH.M ) To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 11 Feb 1998 20:05:57 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199802111308.FAA02308@rah.star-gate.com> from "Amancio Hasty" at Feb 11, 98 05:08:15 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 > Hi Terry, > > Where is code ? If you want me to test or check out the patches just > let me know. It was posted to -current under the subject "PATCH.C". BTW: Doug Rabson has reviewed these patches in my last monolithic attempt containing the locking patches, the EXCLUDE flag patches, the nameifree patches, and a number of other namei cleanups. The patches I sent him applied cleanly -- most likely because he did not wait for weeks of kernel changes before applying them, unlike some people. His single complaint, which I was unable to resolve to his satisfaction, was that there was a pathname buffer memory leak in the NFS server rename code. The NFS server code must allocate and free pathname buffers, just as the system call code must allocate and free pathname buffers: the patch enforced a more orthogonal VFS interface, and both are VFS consumers. In order to attempt to resolve his problem, I sent him a kernel memory leak test framework. In it, you can snapshot any set of named VM variables (anything you can get back from vmstat), and exervice any combination of VOP code paths. My sample code included with this framework tests only the namei() freeing VOP's. It localized the problem, but he was unable to put any time into fixing it. These new patches do not include the monolithic changes that caused him problems: only the things he was prepared to commit inre: NFS locking. 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 current" in the body of the message From owner-freebsd-current Wed Feb 11 12:07:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08775 for current-outgoing; Wed, 11 Feb 1998 12:07:23 -0800 (PST) (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 MAA08763; Wed, 11 Feb 1998 12:07:14 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id MAA21506; Wed, 11 Feb 1998 12:07:12 -0800 (PST) Message-Id: <199802112007.MAA21506@implode.root.com> To: dyson@FreeBSD.ORG cc: jwd@unx.sas.com (John W. DeBoskey), freebsd-current@FreeBSD.ORG Subject: Re: Possible BUG in vfs_bio.c/brelse() line 643 In-reply-to: Your message of "Wed, 11 Feb 1998 14:50:51 EST." <199802111950.OAA10458@dyson.iquest.net> From: David Greenman Reply-To: dg@root.com Date: Wed, 11 Feb 1998 12:07:12 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >John W. DeBoskey said: >> Hi, >> >> I believe the following is a bug in vfs_bio.c/brelse() version 1.147 >> and the following change should be committed. >> >> 643c643 >> < if (bp->b_flags && (B_INVAL | B_RELBUF)) >> --- >> > if (bp->b_flags & (B_INVAL | B_RELBUF)) >> >> I always did like those if (1) conditions. >> >> Comments? Critiques? >> >&& in this case is very bad. I cannot make the change, but whomever >has commit privs, and can do it right now, should change the && to &. Fixed. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 13:50:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28573 for current-outgoing; Wed, 11 Feb 1998 13:50:20 -0800 (PST) (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 NAA28552 for ; Wed, 11 Feb 1998 13:50:15 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA25636 for ; Wed, 11 Feb 1998 13:49:36 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd025631; Wed Feb 11 13:49:28 1998 Message-ID: <34E21C06.794BDF32@whistle.com> Date: Wed, 11 Feb 1998 13:45:42 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: ip_input.c not compiling Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looking for a variable called ip_forwarding I saw a relelated commit, I guess that broke it.. (forget who did it) (from sources cvsupp'ed about 10 minutes ago) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 14:20:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02502 for current-outgoing; Wed, 11 Feb 1998 14:20:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02497 for ; Wed, 11 Feb 1998 14:20:49 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (markham.southpeak.com [192.58.185.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id RAA20368 for ; Wed, 11 Feb 1998 17:20:19 -0500 (EST) Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA01189; Wed, 11 Feb 1998 17:20:19 -0500 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA20790; Wed, 11 Feb 1998 17:20:19 -0500 Message-Id: <199802112220.AA20790@iluvatar.unx.sas.com> Subject: NFS V3 page caching & vm_page_is_valid() To: freebsd-current@FreeBSD.ORG Date: Wed, 11 Feb 1998 17:20:18 -0500 (EST) Cc: jwd@unx.sas.com (John W. DeBoskey) 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, For this test, I am cat'ing a 16385 byte file from an NFS V3 fileserver. ie: 2 8k blocks and a 1byte frag. The completely full pages are cached correctly. The last partial page is not. As I trace nfs_bioread() into brelse() and then into vm_page_is_valid(), I find that m->valid is 0. (kgdb) p m->valid $12 = 0 '\000' (kgdb) p bits $13 = 1 Thus, the following statement: if (m->valid && ((m->valid & bits) == bits)) return 1; else return 0 is false, and we are returning 0. Unfortunately, there is 1 single solitary valid byte in this buffer. Due to the above, the buffer is tossed causing an nfs readrpc to the server to read the tail of the file everytime. Yuck. I am continuing to trace this problem, but any hints about where to look for how the decision to set m->valid is made would be much appreciated. Thanks, John ps: Thanks for pushing the logical vs bitwise and fix. -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 15:52:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16976 for current-outgoing; Wed, 11 Feb 1998 15:52:23 -0800 (PST) (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 PAA16964 for ; Wed, 11 Feb 1998 15:52:17 -0800 (PST) (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 KAA24289; Thu, 12 Feb 1998 10:22:02 +1030 (CST) Message-Id: <199802112352.KAA24289@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Adrian Chadd cc: current@FreeBSD.ORG Subject: Re: Hollywood (Re: PATCH.M ) In-reply-to: Your message of "Wed, 11 Feb 1998 23:39:17 +0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Feb 1998 10:22:02 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But its tried. If she no work, then they back the change out. Its worked > for them.. you try the ideas out. If it doesn't work in -current, you back > it out. Or fix it until it does. Then you bring it into -release. Or have > I like missed something totally about how its meant to work? Well, IMHO if you want to run current you have to be prepared for a machine that doesn't work properly.. (read the handbook :) Anyway, if it doesn't work you can always cvsup back to an known working version... (Of course assuming you have a machine that you can _use_ to run cvsup =) --------------------------------------------------------------------- |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 current" in the body of the message From owner-freebsd-current Wed Feb 11 17:49:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06050 for current-outgoing; Wed, 11 Feb 1998 17:49:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06045 for ; Wed, 11 Feb 1998 17:49:48 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA27828; Wed, 11 Feb 1998 18:49:38 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpd025399; Wed Feb 11 18:39:30 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id SAA28932; Wed, 11 Feb 1998 18:39:19 -0700 (MST) From: Terry Lambert Message-Id: <199802120139.SAA28932@usr07.primenet.com> Subject: Re: Hollywood (Re: PATCH.M ) To: dg@root.com Date: Thu, 12 Feb 1998 01:39:19 +0000 (GMT) Cc: tlambert@primenet.com, adrian@obiwan.creative.net.au, jlemon@americantv.com, current@FreeBSD.ORG In-Reply-To: <199802112000.MAA21439@implode.root.com> from "David Greenman" at Feb 11, 98 12:00:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >When FreeBSD boots, it uses my init_main.c. SYSINIT was *my* baby, > >as is the kernel process starting code used by updated (now syncd), > >etc.. > > Yes, and I recall that SYSINIT was broken and took some frobbing by > Julian to get it to work. I might also mention that some people, myself > included, aren't entirely satisfied with the direction that SYSINIT has > taken us. FWIW, neither am I. The intent was to make it so that you could decide to include a kernel component by linking it or not linking it. Unfortunately, people have continued futzing around with the config program and puting opt_this.h and opt_that.h everywhere, instead of getting rid of conditional compilation in favor of conditional linking, and from there to conditional agregation of seperate object sections (using ELF). In my ideal world, there is no "config". One thing that would encourage this greatly is cutting over to John Polstra's dual ELF/a.out bootblocks, despite the fact that they leave only 34 bytes free, and switching 3.0 over to ELF. As the architect, this is more your department to make a call on. > For one thing, it's made it much more difficult to debug the > system during startup and has made it near impossible to see the > pathologic interaction between various random users of it spread > out over dozens of kernel source files. I'm *very* open to any suggestion on how to deal with pathologic users. If you can come up with a design with the same capabilities that enforces your desired usage model, more power to you. I'd personally be happy with a better level of abstraction in all of the DDI/DKI interfaces, and the kernel inter-subsystem interfaces so that it's finally at least possible to document *preferred* usage. At the very least, preferred usage should be documented by style, but it can't be until there are interfaces that allow it. I think, however, it more a case of "here is a hammer" resulting in people treating everything as a nail. This is endemic to a *lack* of tools interfaces, not their proliferation. > >You are using my LKM code; if you had problems, it's because you > >waited so long, and then acquired it from NetBSD instead of me. > > Unfortunately, you're right. I'm sure even you will agree that it is > not much more than a proof of concept and falls way short of the needs of > any sort of production LKM system. Certainly. I rushed its release for the benefit of "the grand unified console project", delaying the release of my BSD style shared library code, and the next week Novell bought USL, and USL came in, held a meeting, and said work on free UNIX clones was now in violation of Novell employee's non-competition agreements. I stopped contribution then and there because of the lawsuit. In fact, when Chris integrated the LKM code in NetBSD, and it was alpha code (in fact, it had the SunOS manual pages I was using as interface docuementation for the module management programs in the module management source code, in comments -- Copyrighted material; the intent was to distribute *solely* to users who had licenses to the SunOS code for them to comment on how well the interface resembed the SunOS code -- something they couldn't do without the SunOS in hand as a reference). I'm well aware that BSD languished without a good shared library implementation for about a year; I personally sorely missed it, and I'm sure Jeffrey Hsu, who originated the GCC PIC patches and rushed their release for me to use in my shared library effort, was sorely disappointed as well. I'm sure the OSF people, who donated the SunOS shared library source code to be used in the FreeBSD implementation felt a bit betrayed, as well. Unfortunately, I was not in a position to be able to maintain the code I donated. Fortunately, this is no longer the case, and has not been since I left Novell. It's the major reason I left Novell, in fact: inability to do outside research unrelated to my job responsibilities. Research is my method for relieving stress and for keeping engineering fun. You could say I'm in this solely for the fun of it, if you wanted to oversimplify. I'll even go you one further: the SYSINIT/init_main.c code was alpha code, and probably shouldn't have been integrated into FreeBSD as quickly as it was, even given the problems it solved that needed solving. I *still* get email giving me shit over my use of "goto" in about three places in that code, mostly from people who don't understand that compilers kick out JMP instructions. Anyone who has looked at my attempts to get patches into vfs_syscalls.c *knows* that, if *anything*, I will reorganize to use negative logic. I'm a big fan of single-entry/single-exit on function calls, because I understand the kernel preeemption issues FreeBSD will face if it want to support a hard realtime implementation (something I'm also in favor of), or kernel preemption for other reasons, like kernel threads, or the moral equivalen, fine grain SMP. > Look, I'm not interested in putting you down in public. This sort of > pissing match benefits neither of us. I agree; my intent was not to get into a pissing match. Only to refute the implied claims of me being incompetent. There are good reasons why some of my code that people have seen looks bad, either political (USL), or process (update/submit/patch cycle time, use of alpha code simply because it exists, etc.), and so on. Part of it is that the code has been characterized as bad, and now people who haven't seen my production code are making judgments based on other peoples public opinions rather than looking at the code, like they should. > >PS: Did someone specifically kill the mailing of my PATCH.C that > > contained the actual patches? > > No, but I didn't get a copy of it, either. It apparently exceeded filter limits; I will cvs update and repost when I get home tonight. 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 current" in the body of the message From owner-freebsd-current Wed Feb 11 18:07:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09569 for current-outgoing; Wed, 11 Feb 1998 18:07:57 -0800 (PST) (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 SAA09519 for ; Wed, 11 Feb 1998 18:07:50 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id CAA03056; Thu, 12 Feb 1998 02:07:39 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id DAA21958; Thu, 12 Feb 1998 03:07:38 +0100 (MET) Message-ID: <19980212030737.36421@follo.net> Date: Thu, 12 Feb 1998 03:07:37 +0100 From: Eivind Eklund To: Terry Lambert Cc: dg@root.com, current@FreeBSD.ORG Subject: Re: Hollywood (Re: PATCH.M ) References: <199802112000.MAA21439@implode.root.com> <199802120139.SAA28932@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199802120139.SAA28932@usr07.primenet.com>; from Terry Lambert on Thu, Feb 12, 1998 at 01:39:19AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 12, 1998 at 01:39:19AM +0000, Terry Lambert wrote: > > >When FreeBSD boots, it uses my init_main.c. SYSINIT was *my* baby, > > >as is the kernel process starting code used by updated (now syncd), > > >etc.. > > > > Yes, and I recall that SYSINIT was broken and took some frobbing by > > Julian to get it to work. I might also mention that some people, myself > > included, aren't entirely satisfied with the direction that SYSINIT has > > taken us. > > FWIW, neither am I. The intent was to make it so that you could > decide to include a kernel component by linking it or not linking > it. Unfortunately, people have continued futzing around with the > config program and puting opt_this.h and opt_that.h everywhere, > instead of getting rid of conditional compilation in favor of > conditional linking, and from there to conditional agregation > of seperate object sections (using ELF). In my ideal world, > there is no "config". I'm planning to do a option-walk-through and change the options that can easily be changed to sysctl's. This will at least get rid of some of them. If you want to get rid of config, mailing me patches that remove one and one option is a good way to get closer to that goal ;-) I promise to commit any such patch within 48h unless I'm absent or have a deadline just that day. Restriction: The patch must be correct as far as I can verify, and must not look like an option that could easily just be removed instead, and the SYSCTL fields must include a filled-out description. And as stated above: Each patch should remove _one_ option. Eivind, who realize that this is drudge work, but it still needs doing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 19:44:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22535 for current-outgoing; Wed, 11 Feb 1998 19:44:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22527 for ; Wed, 11 Feb 1998 19:44:48 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA23038; Wed, 11 Feb 1998 19:44:16 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma023032; Wed Feb 11 19:43:49 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id TAA25634; Wed, 11 Feb 1998 19:43:49 -0800 (PST) From: Archie Cobbs Message-Id: <199802120343.TAA25634@bubba.whistle.com> Subject: Re: merging win95 and nt filesystem changes into msdosfs In-Reply-To: <199802111922.LAA21018@implode.root.com> from David Greenman at "Feb 11, 98 11:22:13 am" To: dg@root.com Date: Wed, 11 Feb 1998 19:43:49 -0800 (PST) Cc: eivind@yes.no, tlambert@primenet.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman writes: > >Have anybody checked how much it would cost to pay McKusick > >consultancy fees to review and commit (if viable) Terrys changes? > > > >Would this be a solution you'd allow if monetary feasible, David? > > Yes. I trust Kirk's judgement completely. ...but I doubt that Kirk > is for hire. Well, we hired him to help integrate the soft-update code. But he ain't cheap :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 21:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02999 for current-outgoing; Wed, 11 Feb 1998 21:11:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02972 for ; Wed, 11 Feb 1998 21:11:09 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA03695; Thu, 12 Feb 1998 16:05:47 +1100 Date: Thu, 12 Feb 1998 16:05:47 +1100 From: Bruce Evans Message-Id: <199802120505.QAA03695@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: cvs commit: src/bin/sh jobs.c Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This version works bug-for-bug compatibly with bash-2 on tests 01-05. It handles SIGINT "right". It ignores SIGQUIT unless SIGQUIT is trapped. SIGQUIT handling is currently not critical for emacs, due to a bug in the tty driver. Emacs sets both the intr and the quit character to ^G. I think the tty driver should generate both a SIGINT and a SIGQUIT when ^G is hit, but it only generates a SIGINT. Another test: #!./testshell while :; cat; done Sending a SIGINT to `cat' alone doesn't terminate bash. The change in jobs.c is to make it not terminate sh. Bruce diff -c2 error.c~ error.c *** error.c~ Tue Apr 29 04:24:04 1997 --- error.c Thu Feb 12 11:22:06 1998 *************** *** 90,97 **** * that SIGINT is to be trapped or ignored using the trap builtin, then * this routine is not called.) Suppressint is nonzero when interrupts ! * are held using the INTOFF macro. The call to _exit is necessary because ! * there is a short period after a fork before the signal handlers are ! * set to the appropriate value for the child. (The test for iflag is ! * just defensive programming.) */ --- 90,97 ---- * that SIGINT is to be trapped or ignored using the trap builtin, then * this routine is not called.) Suppressint is nonzero when interrupts ! * are held using the INTOFF macro. If SIGINTs are not suppressed and ! * the shell is not a root shell, then we want to be terminated if we ! * get here, as if we were terminated directly by a SIGINT. Arrange for ! * this here. */ *************** *** 107,115 **** sigemptyset(&sigset); sigprocmask(SIG_SETMASK, &sigset, NULL); ! out2str("\n"); ! if (rootshell && iflag) exraise(EXINT); ! else ! _exit(128 + SIGINT); } --- 107,117 ---- sigemptyset(&sigset); sigprocmask(SIG_SETMASK, &sigset, NULL); ! write(STDERR_FILENO, "\n", 1); ! if (rootshell /* && iflag ?? */) exraise(EXINT); ! else { ! signal(SIGINT, SIG_DFL); ! kill(getpid(), SIGINT); ! } } diff -c2 jobs.c~ jobs.c *** jobs.c~ Sun Feb 8 20:50:06 1998 --- jobs.c Thu Feb 12 11:19:43 1998 *************** *** 726,732 **** if (! JOBS || jp->state == JOBDONE) freejob(jp); ! CLEAR_PENDING_INT; ! if (WIFSIGNALED(status) && WTERMSIG(status) == SIGINT) ! kill(getpid(), SIGINT); INTON; return st; --- 726,735 ---- if (! JOBS || jp->state == JOBDONE) freejob(jp); ! if (int_pending()) { ! if (WIFSIGNALED(status) && WTERMSIG(status) == SIGINT) ! kill(getpid(), SIGINT); ! else ! CLEAR_PENDING_INT; ! } INTON; return st; diff -c2 trap.c~ trap.c *** trap.c~ Tue Nov 11 18:15:35 1997 --- trap.c Thu Feb 12 14:45:23 1998 *************** *** 220,228 **** else action = S_IGN; ! if (rootshell && action == S_DFL) { switch (signo) { case SIGINT: ! if (iflag) ! action = S_CATCH; break; case SIGQUIT: --- 220,227 ---- else action = S_IGN; ! if (action == S_DFL) { switch (signo) { case SIGINT: ! action = S_CATCH; break; case SIGQUIT: *************** *** 235,241 **** } #endif ! /* FALLTHROUGH */ case SIGTERM: ! if (iflag) action = S_IGN; break; --- 234,241 ---- } #endif ! action = S_IGN; ! break; case SIGTERM: ! if (rootshell && iflag) action = S_IGN; break; *************** *** 243,247 **** case SIGTSTP: case SIGTTOU: ! if (mflag) action = S_IGN; break; --- 243,247 ---- case SIGTSTP: case SIGTTOU: ! if (rootshell && mflag) action = S_IGN; break; *************** *** 402,406 **** int on; { ! static int is_interactive = 0; if (on == is_interactive) --- 402,406 ---- int on; { ! static int is_interactive = -1; if (on == is_interactive) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 21:51:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07643 for current-outgoing; Wed, 11 Feb 1998 21:51:14 -0800 (PST) (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 VAA07636 for ; Wed, 11 Feb 1998 21:51:12 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id WAA27436 for ; Wed, 11 Feb 1998 22:50:54 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd027430; Wed Feb 11 22:50:51 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id WAA02802 for current@freebsd.org; Wed, 11 Feb 1998 22:50:51 -0700 (MST) From: Terry Lambert Message-Id: <199802120550.WAA02802@usr02.primenet.com> Subject: PATCH.C: NFS client and server locking kernel patches To: current@FreeBSD.ORG Date: Thu, 12 Feb 1998 05:50:51 +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 Here is my second try at this (majordomo stomped the first). I have gzipped and uuencoded these to save space. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. ============================================================================= begin 600 DIFF.LOCKS.gz M'XL("/F,XC0``T1)1D8N3$]#2U,`S#QK4]O(LI_)KQCGUG)L$.`7-H9-JD@P M6\HEK!&H(DM>23;A;G)_^^W'S&@DRSP"23:5!*R9Z>GNZ?>T M?!1Y\M.N^"B3:`O_&WDR'2?!='/\[,7C_SP[?7TF_""4NV+K8FL\3[-$RJT( M?ME*D_%6>I-N5>SLS)\E,DL".0^B2Y'`CS2((]':W&X^\P+?%QMCL9'@1U%" M>6UMC::MM`:#G:UF>ZO9$ZWV;JNSVVX_V]C8*,TWTUHMT>SM-F%:$V'8?PAF M>Z?C=-H#00^$6%E9J?M31YP?G;P^>_?F])TCZF/7\Y)1UEB=N=.-EVYRZ8AI MH[$'LW'!V$VE.!R=#<_?_OIAET#XX:7X_`(>?M@_.M^C1UMKXM`-0Q%$6:QG MB[6M"A@,(O`%X+'QTA]E-U,I:B_$P?F_W@U'[X]/#H8-1A0X.4LB41^^VC\X M;/`^\ZEX(>IP&+-Q)N91[$FQUF!`GINY>\\V&)G7\?0&D!'9E11A//XH>,DL MD8@53I))$B<`;`PS@ZANN)`S(6>,'SHB#?Y7QHAUB+S94#00E`9]-/CRL[V< MSG`S'%U?R6@LQ8L7XFPX_'7T^O=3126-IIF;9&+]A6!28M]/9<80TNL@&U\I M*,BLAOA+L57S]?3@[6O%5]I0<=8/W4NQ*@Y/A_L'#=RYJ;:LY.P*K)GR&CC; M=Z/]@_=O3U[_NO>L9M/V_L2,U.=3BT?PNSI@1Q"_0$B04;4"IA].;\7TP^G1 M^?"'H5IDZN_'A.H#0-(*!LG+5@Y'[T[.COZP@'O2=V=AMEN2\*/C]_MO%75? MBDKSYCLH3>T^2E-[M-*(HM*(.Y5&DZE$7*RNBM)S$BAX3B:2;%VO*^#WC:>P M=>OFR>D3FK\R5'J"$/9?'8D+=_SQVDT\X/!D"F=S$81!=B.NX#&`6R?FU`4A M/YYXJ"D:C/C\N?+Y![07N-`^X4A>YX>K`#_T<'D1&"@Z8RU>/@H.A]XWVCPL(L'5-P%L#W-.S?YV-0'?WWRKL%#^-0*Y7">2Z+9`$J6:# M*LHD\1WLP*\P;O&=?XHUB`A"B6>/LH)XIL('DK.K(!73)![+5#^09DDZE>/` M#Z0'BR=Q)@6@D,G)GO`]`4R93624"5@?7$9Q(KU-O7"K2`[H_6@6A1]A=5T8 M6I3TY]Q0N,*^!S)T;X2,`)^QI$U`D:,XVC`$BE1.W"@+QJF8P8]0KW3]3!(- M+`R6%4$T(^%&GKB6XF,47\,L-]/KB`U!&OTC@RDY'S?5^-:WM8&/]];K0HU/ M`]!`04X*?OT[NG$0!M>;X^G<[AJ5'UL1`IVDL94_Q)\_$N>[?/NMX!==.X)7 M[KVXQ7T]O.4&P@<$JY_A"<6SK%X,)"L.S(XMC?H5M&^!`1@D=GH]IS/H6$'B]^!3T;K< MSB9G>BNCGEYI@=UW:^U]SN2KU18QN%-OOQZ#HN)^*(Y8!=X.)TD@Z#CISSRBB.]R@(V#N-4IIMJ9*M` M[_#X!(/3^RE,E:'9&32=G4$_-S2A;Q0!'/U>_BP$OA2?<)"L'>H#/%5]'@=> MHVQNEGCIT'>T;V9M)FN,^KBQP8#',42LXJ4.2S3=364C!MVN,]BV;,0C2%S7 M`TNR$!JKBA@?PI=[!2\66\#$/)@Q5;(P:+:=07/P]Y(%OX+J0YQ6HEF9[&G* MM&I34U\S`_`C'I$R-:B2,-7RL;WC#'J];RX?3R4&2SG")#V>*96RT=T&)>H: MV2`BM3=E9PI1^YX9*K)O@7N(')GY*T@;5P5B#Q1Q%G6+1-D)R0OQ?X>_[)_E MN<6==;WEHE1B6QFSX1^-"KPH@&,1:C5!=5K-5FYD'L.?=7&;C5EF8KXE2[]* M%!_#U$H1)#W=SLU31:9D48-%/4/,$AR.7S4>(CHZ+RV)#D#X>@"?N?+(W%+5 M8@A36*I:?9"JME4#?7J2;S_:"H35T5I$/QB$HMD(24[V4?D:$*'Z/^`24.V[ M]`JPM5.X`FSMB`*Z?`'8VE$W>ZVM3DLT^[OMSFZKE5\`JMFEZ[]N?[?;J]2` M;LO9;K/\(PS\:&0#_OY7$(W#&;B4GY&6J9NXD\VKEPL#6'*D@?72`/(&X\ZJ M18AJU7,L=%8]GT40`GM5(^3UJ@8F;AA6`_/'418NPY@75"+LJ[$J7O::3J^? M\[+7=OHMS?FU^U%21;@"@DGAMW!C2&?V/="<.+D! M%1K'D.::U&O(%T(4)O*Q( M^QJB2\]GHS]GK@<;(NK(D+_P:CF1EZ`:,A'%S?P0SI$27]I5+$Y4\/$'C<>^ MC[`QD'`$B`R;?,"4PCR=$M()8$;Y.HX@`JM!Y;W&]*7Y0[-2&@+QC)?UW;967AMY(II,VC7VF&1P-7>:9 MH!X&-(!"9<94B54]]QH)+[G:[3ZG;NJ"E_4>=>HW/?1XDE#HSCR00B'^(QC\1.R9#=,B/'I2O=A=83=>%I5W1@R3B4;I(O4H6);?#? M.WVC`C]>(H+2P[F2A/ET[ZZ37[>&56V$A_%#<9CK(SRJ"R3WEAJEL%\G*X^5 MDEOD(W=1AY"YYHU=8*58#EB`]D0,0\EU`.M!)N92KX)0C5(L%W#8$U,W3?$1 M7CVAE0.GAVZ<[!]XNOPB(G1O)%Y,T66'W%SP=G5+"(MR:^ZF#D^'PWI!K/2U M*Q%@L3R_TM$Q$JHQ(;76X-"GZK[G:_2CTH+VP67T!XLUIN)&QL\B+CX4`LKJNJ@Z[2;S<5:SRU;5_+U85M7=I@!62GT&PY(J+FTQN)&YTR1*)33YBC?X3'Z2``#H7UHR5`:)=KJ6X MW#M%5V:;`J;S,B\&QYH9J1-NQAU%63"1>_PK.M]@`AG(F'2)FJUX,I[H6\P.<858,XC*_$1(ZOW"A()YLF?\%*46MR:=XTD7-'K.%M8HC9\5J83:8*(.$-]##QL/#?_P&0SVGI-"#\A&QY%W5=25'70[>8`%&''V`<5KUQ?87Y0KU\HA8D[R$X6NN7K)\:RJ#E;5G\6EAEL,1&XA]M_L'QU; MO4R$(YUF!TZS:Y3^,;0^&5'W0+WRV+I(BMU.8R5.^.$:LV\K8*2/:XUK-V#* M5/RBIR.R:LG"&FNZ.89;G(1-S\%P_^#MKV:`25+)3+O7<]JZ1%E)XP[0.+"2 M:R/5)K;1;7L<"?B+8VRBQ;Y3;$*]#L)0Q5Q>?!U=)BZ$EN#_9U/^U8UN MA+*;4\SD""@Y$[5*M^VZ(0B'!Y.O(YW7<;M1<]OI-NV,\EOQ^.F9MN!QP1.3 ML8607_>KJ+"NI(;4'O_N].3]'H8/%IR]@H_V2HM5-,WU4.H.HB?@N<>S),%V M&QS9W-SD=;;EW^-N(AC#3B8:"/B@:)@6P-\*8UZK-N8J$,7,(`$G47^>N_5= M<1EG1J2>\Y&H\%3/1_[8:PJS,%SEDCV6H"UD%#?MW+TFOC#JE`_#?U1;FTPP M-%?E2$X,A#C7$=,$$B3N))>?`(]<<%UP&7``#`6.!1O*O2V/&LL][N(VE8P` M@ZM7DQK:-1S"D*$$)O;3!``#+B30B?-<45C"F&N:5/B8PTG3 MF?04CF`FTAA/+0[G@&&.G0<"2[!HNMZ=@>AZDLLT>+,$=YZ`ZW0F$T%Z,C?3XSL!\,7:F#46(()EO5;**)>5D?)$CD933*'I`.JE0'ZM`HO24*2V5K>(:Z0(I!ISF1 M;D09<4!=@?'4A;-7[(OCCX'4;W,`I6$H$YO6HT@-Z,.=RRQVK,DBO8IGV!,) M''_N!>G83;SG#`&-!'*$KRQ8^^KYW82:W##W!X7+`[QA4#/P\U]5=Q)A?G%0 M41.KN(JX/19?OL.%2=#OE[.4(O8\"]$-G,:;G2:9#Q#'R62`V=2 MCE)RJ=;3$F7(+`#@8/('N9D@V!=L+!4`]3H+VZTHO!'3$-47I`4T!.:J[;U- MRXV"N-3%'CM`K/?2+JNK^0-=]1#F[H:KQHT\FN#[`1!JL/LSJ?F"S<`+]66: M.85<=DRNB@5I%^O3Z0R4V?(NSQLY@VV^E;B$7$#.3MSD(]E6BZ^+/MO@?'M- M;3&\H+:C/+Z@>GITR0ZEL)U!.%4W-+2[44H5AC!FRT2W*%76H2)]IMI`>EP/ MY*[29!&/*69A+31%_KI13A5?Y!D/7FW2BV&:KZG`9`*-6!R5A51%@7F/<421 M-$V;P/$D-PX_A0"`*4_B&<`J%>.L&U5=XWILC*2%2-$I\]C[CD")%SXH3EI> M)80`+<:N<@.F<(I6&S8S&F]M=,CS_?*#JIRLTVXYG;952.NV!TZWNVT5TM1K M3*U=9(K:'+6:=%'EQO9+A^#B)NZ-P>#*1>_*(0QK+(N7F5\6LSV,OE+P36-Z MPR:C/GY"#_45Q6G+#`V``2X`.:+>8%3*&J/?",'^K@= M+AZFQ.0+:::Z%R&%#.Z8NODQ;-!CU3743J?O=`JWK2BJ5Q(M+#;U\^TB79[@ MWA0-D;7%MC))Z1'>>J36-B;AM(G7;ZH:INK7$?G=B5OJ#BH>4,#V4/X0,S8( MH&W3&3K!,+XV>Q=J)ER6Z&[WG&[??@'GAY"I#.^#-,0LN)^*F.E+=43/4&^[ M/$!+>/Z]U$1-+>E)`^.?R\N'CI:=2:?H]I[/3MNMT>5"8 MM]ZK]X[4#(HN'7+SP`?[?4[1]%V/XL&NLRCW[7#?DMTC"XO,K@%\L97`'' MSV;1R=D>IO`$Q$W3V01?U1,I&-Q0JGH#04OFP9A;LZE0HTM2XC*8`_/YVQ4< M!0;/5N61JIZ45ZVP&!5QFU=&OAYGH^E(\Z]W8#`ZWV#8F#+2SKIHA^5-RO0A M)\3;27JQ$,MQ*16;&(9"`_R-ZB]3P,I(9'&>GF'M,X!34HT#ZX(/`F\IU]&" MF^^#T%\%P0T1T>7*BNF/L%L-L=-PG2.TA29&U0@NUGQOJM\S\;V]97-AWK0X MB%X^L+?DID%LBUPO-EH*ZK,DH5%A[D*Z3S[;SYFS^#T;O(R"4TJZ`S*^\.-G M`11LO/2]440KX=GZNHY+\Z_'P%*5/^5:*)S;W`VQ6Q1%`-2:GB;2IUJ5^5H, MQC[_.@O];2YU'SFF=XUIUW^+X#]TAW7\^]NWXO-G7H3W)_ M/Z;FY:\SKR`GJ)I.FO'JY%`A2U-"&>430-J&Q6'$;"7O1<-)W`=G3^*&R!7K M+2>H=-J]CM/M65>9%`)T*`0@?%!FW"!*#48Z_EH>>-!PZ/^0&*K7;3J] MKO7VY?>@YSL&6=NM#L2(.]:;)@,@>-"W@D;3IH:Z7;I-KMO7SXU&X9WB/*BT M(6RT])?7Z-8X>)A#,;Z@L"@?U]#-J_U"W-*96AW&;[>;SG;;M,.4XK,/;OBQ M8-C571+K$7>&XBOWI#M*C;D'.T'S;%_6+/3L%.O.BM\#I]\T)9<'(3-_2F0J M.=6%&'"[\PA.@4LBW%0=?*%^)>H0P8%=:=C&[/CD?+C+'I1I2KFHC7L='IV> MG2^`X0O)1!)+^^V>T^^T'\'2[XUU)>][;6?;?@>LWVTY_6ZNF:5+#)WJ/E.= M38NO5:SS?4;J3JC_*)YK$Z+74KN,>343+915OJ_$L0_68Z=IK+UNNC7JFG?? M>@BA&]=.-BMZ/4ZJ?4J>.^W,+"Z"ACJ;MV:!0^[62!RJ:G(Q2P[ M.?]E>'I66OBBN-!T[FB3O:JF6N:ZP"+ZKSPCM\MT6-L=I]_O68?UE)S)"_G& MS^,;&^I^5UT9X#ECJ2C(_F$]R*_!.5!4L0*-%>(=$>!%\K[)0`)JQ6B*P*RE M:WG('5S,?:Z#T,,:O*C/4LG7'OFWTQ4O`FBO%TA:]8'@MPYQ]ZUO-5-;4^B! MGE2W?0-U8N&W$ZJETQ+P*1XW>UE4``N+O*4+KWK,U]]H6H]\:A<@;QJ3344* MXUF"178V(2I6*MWNZ>L][HC;.9OB('3B_LH%?31ESU7;*/VH"_3\,U MYV/,OT;39*'J\I#2![I6OI94B-0K(9["RV_IZ1#"O:W!>D%%:TCBG?I(?,#9 M2,F3*V&5N>HU6TZOV:_H0Y0TR`7.((Z M7L/@QS)$;!)>XECY"^OT>S1?S0PR08.^L].JZ@9[0FIU9;NB3FTZ@.B+TA*/ M\F[C>1VS+HU51D%SU56>@F`J\_P]CR#(^3)B'U?L(>M#$P6P;]2FA=O@?"^4 M=E45YYD:-5T<"5+[9EV;V(05T[30@%>?S,(LF(*%MIQZCIO,J(O'9@E:VA)> MJFYCD%.A@3$2W!(R=;76K=PN9*1(/T+:JG2MWX$@;#NOWE)C]%KF7M[GY6$T M!4BHELJ?TEUF1O/33^$GLHC/P0RZEW;=L-#K:)ES^FHFHD*#H^3E)P]`+.0S M5>D,@S?IC(8"K@70^:3*DGK1GHTWBA?$P;`7YNT>,/?GGSP'/KZ$_]+_[^Y: MG]JVEOAG]Z]0Z=S6!D$D8?"#N9TI`;:-).DO$XM@1JC$0MVX0/_=_O MOLY+EAQH$GK3?,A@^[S/[IX]>W9_ZPL-XU>X93@B-H#J]E`;W?PQ'63SRW?Q ME'^]'/Z>3YO+9:#YEI2`[^I+>'8/!DF6@0`?>FL%[%0\7O/Z=249&A!*QA]& MDWF1+N(5A>DRAH79,H,E&?4J]'L6?/(=R<,U%GKK2)>C^10_[$FX'EMVJB*' M:PGK7\42:?&"5M(5J@D/U[PF_;'67UN[!1G*(?=)A$AV/%<7L+YW.;:6+_]VKJD4LH@+TNE8 M]Z\Z:5K+4HF/CG'OJQCC6#])(U=4[T`?U`1>6SY?-DDF@&J[H6F'/D5OR;U'"O,8M5,%MB6,UFQY54J:Y) M*XF29&YGQ^]9+WJ?0BV?4P`OTQE+X,\J;TIRIO\FJQ`UWMHJ"O\,8L90[[J9 M"/E4WIULS6D%VR+'5.5=MN*06D7BZB+V*43.9U2R^H2J/:*2T@'E>"C<)]=4 MRMQNZ'=ZQN;%>PI,87:NY$*SYXF`Y;NPQV7A?RF,EL#9'['><&>:;[(W,]EU MN;Z[0@N:,6M.XU@AMY;W5+[G._J2;;].`[&$6,5^6/7VW,FLWI&&JOA12;8, M:/AU[()J]K/M`_&9^KV>T>HXS:ZIFG2\@>Y[:4AKQ/,7B\R>;:Z7A#VVV%_>YOHV"U?D6#W0@,7(TD? M%$L].WGVB-JW4SY0!Z5\.:@\@#ZM,"\#?HA7AV`-N/PJF$CR[=2\;.!P*8J) M*AO02_6W4DV$9Q)ZLD[,9][V91?C]I"9V`=B MR-_?:I1%!*B!5W^#?)!N:X5#N^<(AW;/LP?+DJ'=6\[`9TD&*7QKL=!N^RJ( MG'R?V_Y.<%?,2(UEN?2#8%F6,2[I9E")/CD;SNX"R7F)KQ?X0]74=J+0/-F3 M=V(4^;O;%AR)"=8Y_FGP]-G9X0N-,_NG)V]IBEV@Q(O#LQ>_M<385$["M.PH M^#*>Y9OOAH5$G7H4&YB@8=;S]B>3_)K>9M#*>Z41/]``C.&'HTD:9^(KR%;M M6>Z-+!_TR82)1MY:SG-^LV'';K(&7Z?3F)Z(Q#^/+-(I@7OIZO(LA,5M6=8R M8Z789@SW&TLSN7$!Y%?J4Y4!:J0"/4T4;`'K!\.%&5%/A2"AJ%<1X79.K'T"4](2O<5L00K$#+FA2ONZSSY,9XD7(331WG#1.&JRM' MCK^/KV9>$5/3,52BI\JR!;YE`\+0*P`%59EU0[,X3*YFCX&(YV'20 M\8P(1"8$@1)B,X(.+56>>1P5ZEF/S9R9#ETNM*N>]MA\`FL.$J"(9_B:](!B M]*Q0=3(PLDLGOP9M;5D^FP[TU49%BCW+55,%E--V"*DN.6%^V^3)3CX*`?H] MC)1P&*L2O)W.1_@R#WQV&NNH=8?J!)!4UU!,?3W,R"D@9TJOBZ.RQUK6CW"P M6A70([8&JD?J#E7@!*1+X<`M75)Z;KBAQJ"HZ#`I)\V?T\D1\-Z:8LBP0DI0T81X2COGC+*BLX<#=8I5^7`9H9L7G_QT@K##Q(U% MESPMY4PSRJ?3>"28M,MNU:NY1+R!J[BDDIWWC1!!,`G>KS)SWE:$H-:L?8]7 MD/1_JL09TM7AAQ&0H=P*/H]9%X]@IT$+]4^?%3(#3X M621Y!9V#VJ:&Q/RHW.LM'BW7_FMKKE>[(8JEJ)Q-I"9;X73"4N#N/KPJYA." M%[$"*%I[A)3X#L[2X6A6:.$-2KA'"C7*'*W@D3LB!4$T&88DY;BW#*BP0D_X MI"@-2?Y9%>Q1G4?A$L1T0F#\><;_W_-MKGX`]=2F*) M>NU=/[+S(6FPUS-'?K^'Z_)F$MV/K@9[&K[#@ANUL M"]\W,Z`=24X"U,"?*/M"18X:LQ+*4/"5K`0'H1,*$E]&9U5KXY4C3%V.X)P= M]\L/W&YC@8`@?N!%4]H'X M.+P32Z@0*%I#>6D3^K(LA?=$75:/M;2UZY#6KJ=&R'2URV0%1`,G9M#KMW=` MRM($I5R%G36J/HNW>W[8;ELG,7YAD/R_&\=)FL4-T:D;C0X1#J*9E3*#I)CQ M_)(M2;1=INHI5^U2U>+N55\U>E15/NX1O@]>SAA@>,R*WW=IDF%$-[]/#DY/ M?GGQ^!"_UXUQ&M=&&'`,9ES,;*V9&S&%>=1AJ$=-"4+CX=3H_Q75,`-JHQ%& M5$LAI,%=$5DMN6`V0[&<>$2-U*)?MSM^N*LQ?JVEP.?4AK3'3ZH>H:X/QQ9SPV&UC_REL;O`A$!)ZA73(AZ>Z M8)]/AQ2$7NJ=DK%1U2AH$+;6+X7D=VE&+2LOK6S3TO")J*F!MM4`9[>MK>UL M[S=N8A_:["(^)XNYXD2,;*9W,&^3B]NLB:HP`AWD*JKFW0W:+*??F&`\*P#= M!&XU5!85VDSE!<\IGT6RJW*3...32=YOQ>#!2XR/\-;Y@9Y7Z9BJX:,M5\.> M\^L,%'TYRRY`VVE(6@-3!#_VB9P>T.[[7CP;;97J\)LSC9J6!./KY+&9"OXI M,6>2_F''#WO!LMS\&TGY-C)1PIH:;1TEOF`T-<>>@'1EA8YKPOJ'L(J](.A= M1I6[//`S!87K,0B"A9-WWQRVH3@L5RRV<4L6V_AK++:QFL6:0B/H/I$FOV MVSWK.6IN\EUWE)V1!%6[8\$[:]*.J''5"826A+N5MK MRSM=W\J**T2DXE_)X0T6\-$-K/QW&FZ&=DH^&&EE*F.,;*.ZKA"@P;_8#/]] M>'(D^I=^S20/-M/&4UT)\9+GTU'L7>23L0V@YEST&N(0O:ZP.]58$,ZW!!VL M4,RE(88S5UEUN#6.E5]7ONRK6DO5%7)I+"H<2\WIN5N1D$Z9]S(Q.50W1<-3 M_I-[U-2QA,J;`%*Y1*BFK`5BD+?#9V]T" M.7=T,?FILMA\W22C[.<*VT)5=Z4-+(&YB#B'2"*"4ZI9T=A-OIF07H1MM;X@ M@2XT@2X^1J"+?SB!5LFXW:[?T58F:./GX8?T_IU`^7IV:YD`Q&7L&X$.D-_!SF M!LY\QM6W](W%O=I^K1[KK7,E\]RNMW#LOKN[.AMYU/:"J!^$_6W.1KZHM/J& M03^H,="%H1^&EK<@?[$$G;*X'.3O?DD%R\&&''+-96B;#WV MT;V+ZQ&--Z`SPG'C&D"3"W1)HV(XWJ20TL=/3\\&3P[W#YJ^EPTOX]%P=!&W MH#OZ8P!D0VKS8_P$QR^2BT`CSHM:.-!>U]\)MBW_UEX/OC";BJ<*,@G(&=]C M]!N^OV`H`LB?>9H/X&:)M\MD%?5SH9JQY%@WG);*DMX*F/+&9O:&K[.V,T% MQ"5A19=WD5-4)2ED(Q&I9'ZU=/+PUW+P#$LUF9/0!1QI9_6*2=>X0>5_=7MU M/2SXZ+<$8BF)_3T)Q5*O]4]B@?LD%GBI^R`6:,&X'8`HZV^W4?`A"Z35SV'D M15[%0YU=W\`7*_--.HBCI.`[R&"^A1\L">6-_YCG0+;I@/YX#2?O?W\Y.=L_ M?4N@R@?TJTY;4JB;N$XNGPXN\S',EAC^A9HU2RCQ)\8TH$6\Y;R+-=2YIJ)Z MH?83T5.K9)SJ5S_OGJ9`2W&2`*T5XB8J65K&*7IRL1\1TJE^6"7E!59H11:S M[J[?,_C/8[Y=`&T/6-+0)$_8:()6$,R20/@=Z&&J^U5CA167VO`757U*',`A MT]0`'!WCY8IS/&VV(UI=^(D,,OB$)QG!2[5(P'+=;_GY$+N$84WCUSMO5;2N MP!%-;NC4H5_9X1NT^:.#IK(@GB;.>W1V_9W+T??T+ MMOLE%ZPDKN;W[M-2T?,=_%KF*_U:>J2SA?VPS6Y0*P-[[EV 8IO+8VB:OCYR;A9S;[:'\#XG-JL":I``` ` end ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 22:08:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09551 for current-outgoing; Wed, 11 Feb 1998 22:08:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09543 for ; Wed, 11 Feb 1998 22:08:31 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA00954; Wed, 11 Feb 1998 22:08:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802120608.WAA00954@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: PATCH.C: NFS client and server locking kernel patches In-reply-to: Your message of "Thu, 12 Feb 1998 05:50:51 GMT." <199802120550.WAA02802@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Feb 1998 22:08:24 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, this mailing list not really suitable for carrying out this kind of stuff. Yes, I know that you like to post and thats okay . Try to setup a web page or an ftp site where you can place the patches and the documentation as well as any update notices. At least two group of people have done something similar to what I described above and they are busy hammering out the code. Last but not least tnks for the patches!! Best Regards, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 22:23:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11840 for current-outgoing; Wed, 11 Feb 1998 22:23:47 -0800 (PST) (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 WAA11818 for ; Wed, 11 Feb 1998 22:23:44 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0y2s3e-0003fY-00; Wed, 11 Feb 1998 22:23:38 -0800 Date: Wed, 11 Feb 1998 22:23:35 -0800 (PST) From: Tom To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: PATCH.C: NFS client and server locking kernel patches In-Reply-To: <199802120550.WAA02802@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Feb 1998, Terry Lambert wrote: > Here is my second try at this (majordomo stomped the first). I have > gzipped and uuencoded these to save space. It seems very wasteful sending patches out to a mailing list, considering the number of the people on the list, and the size of intended audience. A http or ftp site would be much better. > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Wed Feb 11 23:50:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22373 for current-outgoing; Wed, 11 Feb 1998 23:50:42 -0800 (PST) (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 XAA22355; Wed, 11 Feb 1998 23:50:39 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id LAA13207; Wed, 11 Feb 1998 11:37:55 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Wed, 11 Feb 1998 11:37:52 -0500 (EST) From: "Alok K. Dhir" To: smp@FreeBSD.ORG, current@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Sound trouble 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 Hey all - I'm running FreeBSD 3.0-current with an SMP kernel on a Dell Workstation 400 with two 300Mhz P-II processors and 256megs ram. :-) The Workstation 400 has a Crystal CSS4236B sound chip on the motherboard. The only driver I've been able to get sound working with on this machine/kernel is "Luigi's" plug and play pcm driver. I couldn't get the "standard" Voxware drivers to work at all, and the OSS drivers (which I bought) don't work with SMP kernels (annoyingly enough). Luigi's sound driver works OK, but I'd like to see a more robust, complete sound solution for this machine. When I try to run "timidity" (the software wavetable midi player which used the GUS patch set), it starts out sounding nice for about half a second. Then it starts mixing in an incredible amount of noise until its completely unbearable to listen to. Similarly, some games (like xgal) make horrible noises... I wonder if this could have something to do with SMP? Other things, such as xanim, mpg123, and a few others render sound without any trouble. Does anyone have any suggestions? -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ R7-003, ITSMC 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 current" in the body of the message From owner-freebsd-current Thu Feb 12 00:01:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23629 for current-outgoing; Thu, 12 Feb 1998 00:01:09 -0800 (PST) (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 AAA23621 for ; Thu, 12 Feb 1998 00:01:07 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id BAA09919; Thu, 12 Feb 1998 01:01:06 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd009895; Thu Feb 12 01:00:57 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id BAA16756; Thu, 12 Feb 1998 01:00:54 -0700 (MST) From: Terry Lambert Message-Id: <199802120800.BAA16756@usr09.primenet.com> Subject: Re: PATCH.C: NFS client and server locking kernel patches To: hasty@rah.star-gate.com (Amancio Hasty) Date: Thu, 12 Feb 1998 08:00:54 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199802120608.WAA00954@rah.star-gate.com> from "Amancio Hasty" at Feb 11, 98 10:08:24 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 > Okay, this mailing list not really suitable for carrying out this > kind of stuff. Yes, I know that you like to post and thats okay . > > Try to setup a web page or an ftp site where you can place the patches > and the documentation as well as any update notices. > > At least two group of people have done something similar to what I > described above and they are busy hammering out the code. > > Last but not least tnks for the patches!! Due to popular demand, I have created a www page on freebsd.org. The URL is: http://www.freebsd.org/~terry/ Here is what's there now: NFS client and server locking NFS lease code left out of the kernel (patches for real bugs) Line discipline changes A validation suite for testing for kernel memory leaks [*] Here's what will be there as soon as I can clean it up (running for 6 months to 2.5 years on my personal machines): The nameifree changes The namei EXCLUDE flag: eliminating redundant code FSFRAME: a framework for user space FS developement PFS: a proxy FS for use in FSFRAME UNIONFS: patches to make it work UMAPFS: patches to make it work Here's newly developed stuff: RAIDFrame: a software RAID on FreeBSD DEVFS Slice code: how one fdisk can handle all partitioning Here's stuff I need to clear with Whistle: LDAP on FreeBSD (patches; assumes you have the fixed pthreads) [*] If you are running the soft updates patches, you should download this now! In addition, I will be putting up about 20,000 more lines of changes as soon as I can classify them and clean them up into little pieces that can't be applied simultaneously, like the committers want. Just like the good old dsays of 386BSD before I wrote the patchkit... All of this code assumes you patch against -current. Making the patches work together is left as an exercise for the committers (I could do this, but only if you were willing to commit everything at once). 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 current" in the body of the message From owner-freebsd-current Thu Feb 12 00:03:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA24076 for current-outgoing; Thu, 12 Feb 1998 00:03:47 -0800 (PST) (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 AAA24071 for ; Thu, 12 Feb 1998 00:03:45 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id BAA22785; Thu, 12 Feb 1998 01:03:44 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd022771; Thu Feb 12 01:03:41 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id BAA16816; Thu, 12 Feb 1998 01:03:40 -0700 (MST) From: Terry Lambert Message-Id: <199802120803.BAA16816@usr09.primenet.com> Subject: ONE STOP SHOPPING: ALL OF TERRY'S PATCHES To: tlambert@primenet.com (Terry Lambert) Date: Thu, 12 Feb 1998 08:03:40 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199802120800.BAA16756@usr09.primenet.com> from "Terry Lambert" at Feb 12, 98 08:00:54 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Due to popular demand, I have created a www page on freebsd.org. > > > The URL is: http://www.freebsd.org/~terry/ I forgot; also coming soon: Patches to add -F option to "newsyslog" Patches to add -d option to "w" (just like SunOS 4.x and Ultrix) 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 current" in the body of the message From owner-freebsd-current Thu Feb 12 00:19:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26621 for current-outgoing; Thu, 12 Feb 1998 00:19:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26616 for ; Thu, 12 Feb 1998 00:19:00 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id AAA01607; Thu, 12 Feb 1998 00:18:57 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802120818.AAA01607@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: PATCH.C: NFS client and server locking kernel patches In-reply-to: Your message of "Thu, 12 Feb 1998 08:00:54 GMT." <199802120800.BAA16756@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Feb 1998 00:18:57 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You have a pretty good idea of what I am doing over here I will get to your stuff this weekend . Tnks Terry ! Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 02:52:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11007 for current-outgoing; Thu, 12 Feb 1998 02:52:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10997 for ; Thu, 12 Feb 1998 02:52:26 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.7/8.8.7) id MAA23164 for freebsd-current@freefall.cdrom.com; Thu, 12 Feb 1998 12:03:09 GMT (envelope-from kuku) Date: Thu, 12 Feb 1998 12:03:09 GMT From: Christoph Kukulies Message-Id: <199802121203.MAA23164@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.FreeBSD.org Subject: rc.network - ipfw l 65535 | grep deny ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could someone explain to me what the line 84 means? I believe this is bogus. if ipfw l 65535 | grep deny; then # $Id: rc.network,v 1.16 1998/02/07 04:56:56 alex Exp $ -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 05:38:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28281 for current-outgoing; Thu, 12 Feb 1998 05:38:52 -0800 (PST) (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 FAA28260 for ; Thu, 12 Feb 1998 05:38:48 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id NAA11467; Thu, 12 Feb 1998 13:38:46 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id OAA20426; Thu, 12 Feb 1998 14:38:45 +0100 (MET) Message-ID: <19980212143844.44164@follo.net> Date: Thu, 12 Feb 1998 14:38:44 +0100 From: Eivind Eklund To: Terry Lambert , Eivind Eklund Cc: current@FreeBSD.ORG Subject: Re: Heads up: static -ification References: <19980210030906.20113@follo.net> <199802100857.BAA22938@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199802100857.BAA22938@usr05.primenet.com>; from Terry Lambert on Tue, Feb 10, 1998 at 08:57:11AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 10, 1998 at 08:57:11AM +0000, Terry Lambert wrote: > > > Remember that functions and variables are exported interfaces in > > > many cases. This includes user space uses for "ps", "w", "netstat", > > > and so on, as well as kernel space uses. > > > > I know. I hope I didn't break any of them; the suspicion that I might > > have was the reason for sending the heads-up in the first place. > > > > I though fixing this (the extreme spread of kernel symbols) was worth > > the potential trouble. > > > > BTW: Speaking of symbol spread - you once gave a reference to the ld > > manpage and implied that it was possible to create new object files > > included a specific subset of the symbols from the original object > > files. I tried to find out how to do this, as I wanted it both for > > the kernel and for libalias, but I've spent quite some time without > > finding out how to do it. Would you mind giving detailed > > instructions? (Re-creating object files is easy, the problem is > > controlling which symbols to include on a fine-grained basis). > > You should look at the man page again. Keep in hand a copy of the nm > man page with reference to the "-g" option, and a copy of the modload > source code. The implied pointer to the LKMs made me discover the solution - just as I had discovered it by myself :-) symorder can be used to restrict symbols, too. I can't see anything else that does this job. And a simple reference to 'symorder' would have been all I needed. [... On what my staticization might have broken ...] > If I don't miss my guess, this was either in the console code (World21 > uses this to replace the console with an internalized console capable > of displaying 21 different locales -- one at a time) or it's in the > NFS lease function pointer management. Those are the two examples that > spring to mind. It was some MIDI-stuff in VoxWare. And I don't think it was intended as an LKM hook. > You may wish to explicitly contact binary driver vendors (like Dennis > at ETINC), who may depend on unknown symbols. He hasn't complained yet... :-) > I definitely agree that the interfaces should be pruned, for what it's > worth. I'm not quite to the point that I agree with the Linux/AIX or > Microsoft link ".DEF" file approach to defining external interfaces to > objects, but a directive to decide which symbol table in an ELF file, for > instance, would probably be acceptable to everyone, especially if it > were a macro wrapped storage class specifier or a #pragma of some kind > (we will need these for marking things pageable and "non-load" for the > kernel loader at some point, anyway). The problem is that we have subsystems that share symbols internally, but shouldn't expose those symbols to the rest of the world. I'd like a hierarchical model where we the kernel is the top node of a tree, and each node in the tree have a defined exported interface, and all symbols not in that interface will be removed. Each node will be implemented as an object file, but might be constructed by re-linking subnodes through ld -r and a pass through symorder -c to zap non-wanted symbols. This has two good effects: (1) Limiting exposure of symbols as much as possible, so incestous relationships don't develop so easily. (2) Minimizing re-link time, as only the parts of the kernel that really has changed will be re-linked. OTOH, I think this might be too large a change for people to swallow. > Once this is done, along with your other changes, then we will be a long > way down the road of having a documentable DDI/DKI that we can stick with > to get vendors to start writing binary drivers for their hardware for > FreeBSD (I'm sure the aforementioned Dennis would be happy with this). I'd like it, at least. I'm hacking drivers, too, though not usually sending it out as LKMs. > A lot of problems like this come from subsystem exposure. Veto interfaces > will definitely reduce the kernel symbol "footprint" of subsystems (my > favorite hobby horse here is the VOP_ADVLOCK code in the FS's). Most > of these are violations of the "downcalls only, no upcalls" rule that > any beginning professional interface designer must know. I actually dislike the use of calls between layers at all (or at least in almost all cases). Layers should communicate through asynchronous messages; that way, you avoid a lot of stupid implict ordering assumptions. > In any case, keep up the good work; I only meant to caution you about the > amount of exposure that was dependended upon; I in no way advocate it, > nor do I hold it up as an example of "good engineering practice". ;-). I actually think I've zapped all the variables that can turn static. The next stage would be to go for the module-variables, but that need a re-design of the kernel link process as outlined above. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 07:09:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07213 for current-outgoing; Thu, 12 Feb 1998 07:09:46 -0800 (PST) (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 HAA07207 for ; Thu, 12 Feb 1998 07:09:42 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id KAA21386; Thu, 12 Feb 1998 10:09:30 -0500 (EST) (envelope-from wollman) Date: Thu, 12 Feb 1998 10:09:30 -0500 (EST) From: Garrett Wollman Message-Id: <199802121509.KAA21386@khavrinen.lcs.mit.edu> To: Eivind Eklund Cc: current@FreeBSD.ORG Subject: Re: Heads up: static -ification In-Reply-To: <19980212143844.44164@follo.net> References: <19980210030906.20113@follo.net> <199802100857.BAA22938@usr05.primenet.com> <19980212143844.44164@follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I actually dislike the use of calls between layers at all (or at > least in almost all cases). Layers should communicate through > asynchronous messages; that way, you avoid a lot of stupid implict > ordering assumptions. ``Layering is a great model for designing protocols, but an incredibly lousy way of implementing them.'' - D. D. Clark -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 current" in the body of the message From owner-freebsd-current Thu Feb 12 07:18:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08645 for current-outgoing; Thu, 12 Feb 1998 07:18:26 -0800 (PST) (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 HAA08637 for ; Thu, 12 Feb 1998 07:18:18 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id PAA15581; Thu, 12 Feb 1998 15:18:15 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id QAA22660; Thu, 12 Feb 1998 16:18:14 +0100 (MET) Message-ID: <19980212161814.38690@follo.net> Date: Thu, 12 Feb 1998 16:18:14 +0100 From: Eivind Eklund To: Garrett Wollman , Eivind Eklund Cc: current@FreeBSD.ORG Subject: Re: Heads up: static -ification References: <19980210030906.20113@follo.net> <199802100857.BAA22938@usr05.primenet.com> <19980212143844.44164@follo.net> <199802121509.KAA21386@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199802121509.KAA21386@khavrinen.lcs.mit.edu>; from Garrett Wollman on Thu, Feb 12, 1998 at 10:09:30AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 12, 1998 at 10:09:30AM -0500, Garrett Wollman wrote: > < said: > > > I actually dislike the use of calls between layers at all (or at > > least in almost all cases). Layers should communicate through > > asynchronous messages; that way, you avoid a lot of stupid implict > > ordering assumptions. > > ``Layering is a great model for designing protocols, but an incredibly > lousy way of implementing them.'' > - D. D. Clark That quote is often true for protocols, yes. OTOH, I haven't yet found a way of implementing advanced protocols that isn't lousy. And one of the problems with most layered protocol implementations is that they don't take the layering far enough - they throw in a lot of indirect calls and non-visible state as their 'layers', instead of abstracting enough and consider each layer a process. At least for operating systems, message-passing systems tend to be beautifully simple. The main problem is that if you do them in a memory-protected environment your performance tend to suck. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 09:15:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25436 for current-outgoing; Thu, 12 Feb 1998 09:15:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25426 for ; Thu, 12 Feb 1998 09:15:32 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA30328; Fri, 13 Feb 1998 04:13:51 +1100 Date: Fri, 13 Feb 1998 04:13:51 +1100 From: Bruce Evans Message-Id: <199802121713.EAA30328@godzilla.zeta.org.au> To: bde@zeta.org.au, cracauer@cons.org Subject: Re: cvs commit: src/bin/sh jobs.c Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen some problems with my version of the fix. The serious ones (2-3) probably affect all versions. 1) When `make' of a kernel is killed by ^C, the newline to clean up the output is printed after the shell prompt appears, so it messes up the output. This problem doesn't occur if /bin/sh is bash-1. 2) Shell scripts with `make' commands in them are hard to kill. This problem still occurs if /bin/sh is bash-1. It seems to be a bug in `make'. According to a draft of POSIX.2, `make' shall catch SIGINT, SIGQUIT, SIGTERM and SIGHUP in order to clean up, but it shall resend SIGINT, SIGTERM and SIGHUP (but not necessarily SIGQUIT) to itself in order to exit with a signal status. `make' doesn't do this (at least in -current). Gnu make does it. 3) Recursive makes (e.g., of /usr/src) are very hard to kill. This seems to be caused by the same bug in `make'. The bug in `make' is very old. I first saw it several years ago when I tried applying a patch by Chet Ramey for sh's signal handling. At the time I thought it was caused bugs in the patch. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 10:05:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02827 for current-outgoing; Thu, 12 Feb 1998 10:05:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from prefetch.san.rr.com (ns1.san.rr.com [204.210.0.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02822 for ; Thu, 12 Feb 1998 10:05:24 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (dt050ndd.san.rr.com [204.210.31.221]) by prefetch.san.rr.com (8.8.7/8.8.8) with ESMTP id KAA20051; Thu, 12 Feb 1998 10:04:05 -0800 (PST) Message-ID: <34E3398E.DAF4EAC@dal.net> Date: Thu, 12 Feb 1998 10:03:58 -0800 From: Studded Organization: Triborough Bridge and Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE-0211 i386) MIME-Version: 1.0 To: Christoph Kukulies CC: freebsd-current@freefall.FreeBSD.org Subject: Re: rc.network - ipfw l 65535 | grep deny ? References: <199802121203.MAA23164@gilberto.physik.RWTH-Aachen.DE> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christoph Kukulies wrote: > > Could someone explain to me what the line 84 means? > I believe this is bogus. > > if ipfw l 65535 | grep deny; then > > # $Id: rc.network,v 1.16 1998/02/07 04:56:56 alex Exp $ That line is checking to determine whether the default rule is "deny" or "accept." an important distinction if you're going to warn people that IP services are disabled. :) Hope this helps, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 10:17:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04534 for current-outgoing; Thu, 12 Feb 1998 10:17:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04520 for ; Thu, 12 Feb 1998 10:16:57 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.7/8.8.7) id SAA24249; Thu, 12 Feb 1998 18:16:42 GMT (envelope-from kuku) Message-ID: <19980212181642.44127@gil.physik.rwth-aachen.de> Date: Thu, 12 Feb 1998 18:16:42 +0000 From: Christoph Kukulies To: Studded Cc: Christoph Kukulies , freebsd-current@freefall.FreeBSD.org Subject: Re: rc.network - ipfw l 65535 | grep deny ? References: <199802121203.MAA23164@gilberto.physik.RWTH-Aachen.DE> <34E3398E.DAF4EAC@dal.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <34E3398E.DAF4EAC@dal.net>; from Studded on Thu, Feb 12, 1998 at 10:03:58AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 12, 1998 at 10:03:58AM -0800, Studded wrote: > Christoph Kukulies wrote: > > > > Could someone explain to me what the line 84 means? > > I believe this is bogus. > > > > if ipfw l 65535 | grep deny; then > > > > # $Id: rc.network,v 1.16 1998/02/07 04:56:56 alex Exp $ > > That line is checking to determine whether the default rule is "deny" > or "accept." an important distinction if you're going to warn people > that IP services are disabled. :) yeah, but when I type ipfw l 65535 in the command line (sh prompt) I'm getting an error about bad arguments and a 'usage' message. Am I using the wrong ipfw or what's wrong here? > > Hope this helps, > > Doug > > -- > *** Chief Operations Officer, DALnet IRC network *** > *** Proud operator, designer and maintainer of the world's largest > *** Internet Relay Chat server. 5,328 clients and still growing. > *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 10:27:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06305 for current-outgoing; Thu, 12 Feb 1998 10:27:25 -0800 (PST) (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 KAA06294 for ; Thu, 12 Feb 1998 10:27:24 -0800 (PST) (envelope-from nash@Jupiter.Mcs.Net) Received: from Jupiter.Mcs.Net (nash@Jupiter.mcs.net [192.160.127.88]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id MAA16364; Thu, 12 Feb 1998 12:27:15 -0600 (CST) Received: from localhost (nash@localhost) by Jupiter.Mcs.Net (8.8.7/8.8.2) with SMTP id MAA05056; Thu, 12 Feb 1998 12:27:14 -0600 (CST) Date: Thu, 12 Feb 1998 12:27:14 -0600 (CST) From: Alex Nash To: Christoph Kukulies cc: Studded , freebsd-current@freefall.FreeBSD.org Subject: Re: rc.network - ipfw l 65535 | grep deny ? In-Reply-To: <19980212181642.44127@gil.physik.rwth-aachen.de> 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, 12 Feb 1998, Christoph Kukulies wrote: > > That line is checking to determine whether the default rule is "deny" > > or "accept." an important distinction if you're going to warn people > > that IP services are disabled. :) > > yeah, but when I type > > ipfw l 65535 > > in the command line (sh prompt) I'm getting an error > about bad arguments and a 'usage' message. > Am I using the wrong ipfw or what's wrong here? Yes you're using the wrong ipfw. Try using an ipfw of the same vintage as the rc.network you're looking at: etc/rc.network revision 1.16 date: 1998/02/07 04:56:56; author: alex; state: Exp; lines: +6 -3 Don't assume that IP services are disabled just because firewall_enable is not set to YES in rc.conf. sbin/ipfw/ipfw.c revision 1.51 date: 1998/01/07 02:23:04; author: alex; state: Exp; lines: +72 -29 Support listing/showing specific rules supplied on the command line. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 11:11:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12941 for current-outgoing; Thu, 12 Feb 1998 11:11:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxyb1.san.rr.com (proxyb1-atm.san.rr.com [204.210.0.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12928 for ; Thu, 12 Feb 1998 11:11:38 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (dt050ndd.san.rr.com [204.210.31.221]) by proxyb1.san.rr.com (8.8.7/8.8.8) with ESMTP id LAA10976; Thu, 12 Feb 1998 11:09:47 -0800 (PST) Message-ID: <34E348F5.70410E1B@dal.net> Date: Thu, 12 Feb 1998 11:09:41 -0800 From: Studded Organization: Triborough Bridge and Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE-0211 i386) MIME-Version: 1.0 To: Alex Nash CC: Christoph Kukulies , freebsd-current@freefall.FreeBSD.org Subject: Re: rc.network - ipfw l 65535 | grep deny ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Nash wrote: > Yes you're using the wrong ipfw. Ah, that's very different. :) Just ignore my last letter then. Doug (who figured it was probably something like this) -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 12:56:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29605 for current-outgoing; Thu, 12 Feb 1998 12:56:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29597 for ; Thu, 12 Feb 1998 12:56:26 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.7) with SMTP id OAA06827 for ; Thu, 12 Feb 1998 14:56:21 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <000601bd37f8$9ff39600$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: Subject: Re: boot.flp bug? Date: Thu, 12 Feb 1998 14:56:00 -0600 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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: George Uhl > >I'm trying to install the latest 3.0-SNAP (2/10) >from a diskette. I downloaded the boot.flp image >and dd'ed it to the diskette. During the probing >sequence while booting I get the following: > > | > | > V >npx0 on motherboard >npx0: INT 16 interface >changing root device to fd0c >rootfs is 1440 kbyte compiled in MFS >vm_page_free: pindex(12), busy(0), PG_BUSY(0), hdd(0) >panic: vm_page_free: freeing free page > >Causing my host to reboot. What gives? > >BTW, I tried the previous day's (2/9) for grins. >Same effect. Same bug with 2/12 boot.flp, any one know what is causing this? My System: GA-586DX 2 Intel Pentium 200Mhz CPU's 128MB RAM 1 Seagate FireBall ST 3.2 GB 3 Quantum Barracuda 4.5 GB Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 13:13:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03105 for current-outgoing; Thu, 12 Feb 1998 13:13:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02966; Thu, 12 Feb 1998 13:13:24 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199802122113.NAA02966@hub.freebsd.org> Subject: Re: Hollywood (Re: PATCH.M ) In-Reply-To: <199802111942.MAA08969@usr07.primenet.com> from Terry Lambert at "Feb 11, 98 07:42:41 pm" To: tlambert@primenet.com (Terry Lambert) Date: Thu, 12 Feb 1998 13:13:24 -0800 (PST) Cc: dg@root.com, adrian@obiwan.creative.net.au, jlemon@americantv.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > PS: Did someone specifically kill the mailing of my PATCH.C that > contained the actual patches? no one killed it. it was over the max message size of 40,000 bytes. i have raised the max message size to 100,000 bytes. didnt anyone ever wonder why we dont get large spams (gifs) in the mailing lists? ;) one, question.....what is the PATCH naming convention? .C .M ....???? jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 14:44:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17805 for current-outgoing; Thu, 12 Feb 1998 14:44:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17799 for ; Thu, 12 Feb 1998 14:44:46 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.7) with SMTP id QAA07004 for ; Thu, 12 Feb 1998 16:44:45 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <000a01bd3807$c447ac80$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: Subject: Re: boot.flp bug? Date: Thu, 12 Feb 1998 16:44:24 -0600 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.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Scot W. Hetzel To: freebsd-current@FreeBSD.ORG Date: Thursday, February 12, 1998 2:58 PM Subject: Re: boot.flp bug? > >-----Original Message----- >From: George Uhl > >> >>I'm trying to install the latest 3.0-SNAP (2/10) : >> >>BTW, I tried the previous day's (2/9) for grins. >>Same effect. > >Same bug with 2/12 boot.flp, any one know what is causing this? > Just to follow up. The last good boot.flp is the one created on Feb 4th. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 14:50:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19706 for current-outgoing; Thu, 12 Feb 1998 14:50:42 -0800 (PST) (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 OAA19701 for ; Thu, 12 Feb 1998 14:50:41 -0800 (PST) (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 OAA04510; Thu, 12 Feb 1998 14:49:55 -0800 (PST) Message-Id: <199802122249.OAA04510@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Scot W. Hetzel" cc: freebsd-current@FreeBSD.ORG Subject: Re: boot.flp bug? In-reply-to: Your message of "Thu, 12 Feb 1998 16:44:24 CST." <000a01bd3807$c447ac80$c3e0d9cf@admin.westbend.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Feb 1998 14:49:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>BTW, I tried the previous day's (2/9) for grins. > >>Same effect. > > > >Same bug with 2/12 boot.flp, any one know what is causing this? > > > Just to follow up. The last good boot.flp is the one created on Feb 4th. Bruce just fixed a bug which sounds very much like it was the cause of this problem. Wait for the next -SNAP after today (the 12th) for one that should work again. -- \\ 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 current" in the body of the message From owner-freebsd-current Thu Feb 12 15:08:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24925 for current-outgoing; Thu, 12 Feb 1998 15:08:52 -0800 (PST) (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 PAA24899; Thu, 12 Feb 1998 15:08:48 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA17321; Thu, 12 Feb 1998 16:08:47 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd017297; Thu Feb 12 16:08:45 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA04168; Thu, 12 Feb 1998 16:08:40 -0700 (MST) From: Terry Lambert Message-Id: <199802122308.QAA04168@usr02.primenet.com> Subject: Re: Hollywood (Re: PATCH.M ) To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Thu, 12 Feb 1998 23:08:40 +0000 (GMT) Cc: tlambert@primenet.com, dg@root.com, adrian@obiwan.creative.net.au, jlemon@americantv.com, current@FreeBSD.ORG In-Reply-To: <199802122113.NAA02966@hub.freebsd.org> from "Jonathan M. Bresler" at Feb 12, 98 01:13:24 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 > > PS: Did someone specifically kill the mailing of my PATCH.C that > > contained the actual patches? > > no one killed it. > it was over the max message size of 40,000 bytes. > i have raised the max message size to 100,000 bytes. > > didnt anyone ever wonder why we dont get large spams > (gifs) in the mailing lists? ;) I did the http page thing on freebsd.org; everyone should now be happy. > one, question.....what is the PATCH naming convention? > .C .M ....???? .D: description .M: man pages .C: 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 current" in the body of the message From owner-freebsd-current Thu Feb 12 15:11:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25243 for current-outgoing; Thu, 12 Feb 1998 15:11:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axp5-fddi.physik.fu-berlin.de (axp5-fddi.physik.fu-berlin.de [160.45.34.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25232 for ; Thu, 12 Feb 1998 15:11:32 -0800 (PST) (envelope-from thimm@oberon.physik.fu-berlin.de) Received: from oberon.physik.fu-berlin.de (oberon.physik.fu-berlin.de [160.45.33.83]) by axp5-fddi.physik.fu-berlin.de (8.8.5/8.8.5) with ESMTP id AAA24424; Fri, 13 Feb 1998 00:10:46 +0100 (MET) Received: (from thimm@localhost) by oberon.physik.fu-berlin.de (8.8.5/8.7.1) id AAA12094; Fri, 13 Feb 1998 00:10:45 +0100 (MET) From: Axel Thimm Message-Id: <199802122310.AAA12094@oberon.physik.fu-berlin.de> Subject: getcwd, fork & vfork To: current@FreeBSD.ORG Date: Fri, 13 Feb 1998 00:10:44 +0100 (MET) Cc: Axel.Thimm@physik.fu-berlin.de (Axel Thimm) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, trying to configure the latest (prerelease) tetex as a normal user under my account, I get a sudden reboot unfortunately leaving no traces behind. It doesn't matter, if X is running, and I updated /etc and /dev accordingly. Checking the configure output by eye I see that it stops at the following line "checking if getcwd uses fork or vfork", so it could be that the problem lies somewhere there. I can provide more information, if neccessary. (Just tell me what you would like to know.) Regards, Axel. System: FreeBSD 3.0-CURRENT #0: Thu Feb 12 19:42:53 CET 1998 egcs 1.0.1 as a port, and detected by configure Pentium, 64MB dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Thu Feb 12 19:42:53 CET 1998 root@rige.physik.fu-berlin.de:/usr/src/sys/compile/RIGE CPU: Pentium (166.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 62857216 (61384K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 vga0: rev 0x01 int a irq 10 on pci0.10.0 vx0: <3COM 3C900 Etherlink XL PCI> rev 0x00 int a irq 11 on pci0.11.0 utp/aui/bnc[*bnc*] address 00:60:08:8f:e0:9d Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface pca0 on motherboard pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2503MB (5126688 sectors), 5086 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 1219MB (2496816 sectors), 2477 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround -- Axel Thimm Axel.Thimm@physik.fu-berlin.de Axel.Thimm@ifh.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 15:11:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25294 for current-outgoing; Thu, 12 Feb 1998 15:11:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25265 for ; Thu, 12 Feb 1998 15:11:50 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA14022; Thu, 12 Feb 1998 16:11:48 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp04.primenet.com, id smtpd013997; Thu Feb 12 16:11:48 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA04342; Thu, 12 Feb 1998 16:11:45 -0700 (MST) From: Terry Lambert Message-Id: <199802122311.QAA04342@usr02.primenet.com> Subject: Re: Heads up: static -ification To: eivind@yes.no (Eivind Eklund) Date: Thu, 12 Feb 1998 23:11:45 +0000 (GMT) Cc: tlambert@primenet.com, eivind@yes.no, current@FreeBSD.ORG In-Reply-To: <19980212143844.44164@follo.net> from "Eivind Eklund" at Feb 12, 98 02:38:44 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem is that we have subsystems that share symbols internally, but > shouldn't expose those symbols to the rest of the world. I'd like a > hierarchical model where we the kernel is the top node of a tree, and each > node in the tree have a defined exported interface, and all symbols not in > that interface will be removed. Each node will be implemented as an object > file, but might be constructed by re-linking subnodes through ld -r and a > pass through symorder -c to zap non-wanted symbols. > > This has two good effects: > (1) Limiting exposure of symbols as much as possible, so incestous > relationships don't develop so easily. > (2) Minimizing re-link time, as only the parts of the kernel that really has > changed will be re-linked. > > OTOH, I think this might be too large a change for people to swallow. It wants the kernel build tree reorganized on module boundries. As an aside, so does multiple architecture support. As another aside, filesystems want to be in /sys/fs instead of spread all over the source tree at random locations. So a source tree reorganization is due. Maybe we could have CSRG assert a trademark on their source tree organization... ;-). 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 current" in the body of the message From owner-freebsd-current Thu Feb 12 15:13:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25805 for current-outgoing; Thu, 12 Feb 1998 15:13:29 -0800 (PST) (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 PAA25794 for ; Thu, 12 Feb 1998 15:13:26 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id QAA14288; Thu, 12 Feb 1998 16:13:22 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd014273; Thu Feb 12 16:13:19 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA04436; Thu, 12 Feb 1998 16:13:18 -0700 (MST) From: Terry Lambert Message-Id: <199802122313.QAA04436@usr02.primenet.com> Subject: Re: ONE STOP SHOPPING: ALL OF TERRY'S PATCHES To: tlambert@primenet.com (Terry Lambert) Date: Thu, 12 Feb 1998 23:13:18 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199802120803.BAA16816@usr09.primenet.com> from "Terry Lambert" at Feb 12, 98 08:03:40 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 > Patches to add -d option to "w" (just like SunOS 4.x and Ultrix) Oops. I have been told that my patch to add "-d" to the "w" command was committed a while ago. Nice to have other SunOS addicts... 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 current" in the body of the message From owner-freebsd-current Thu Feb 12 15:23:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27676 for current-outgoing; Thu, 12 Feb 1998 15:23:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp160.103.mmtl.videotron.net [207.253.103.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27671 for ; Thu, 12 Feb 1998 15:23:44 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost.videotron.ca [127.0.0.1]) by azimov.videotron.ca (8.8.8/8.8.8) with ESMTP id SAA00280 for ; Thu, 12 Feb 1998 18:24:43 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34E384BA.8D863AA2@videotron.ca> Date: Thu, 12 Feb 1998 18:24:43 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <19980210091252Z1182-22297+718@hphalle0.informatik.tu-muenchen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan Schmidt wrote: > Later I've tried newer kernel version, or just updated the lpt driver, but > no change. I suspect that lpt.c must be buggy. (indeed, when trying to > tcpdump on lp0, packets are not shown correctly due to some bugs in lpt.c > (using wrong offsets). dunno if this is related to the crashes.) > > stefan Do you have more information on what's wrong in the lp driver? I can't really switch to ethernet right now so maybe it's better if I try to find out what is really happening. Any starting pointers on what could be wrong would be appreciated as it will be my first attempt at working on a FreeBSD (or network for that matter) driver. Regards -- Stephane E. Potvin sepotvin@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 15:24:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27971 for current-outgoing; Thu, 12 Feb 1998 15:24:33 -0800 (PST) (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 PAA27962 for ; Thu, 12 Feb 1998 15:24:29 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA16659; Thu, 12 Feb 1998 16:06:28 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp01.primenet.com, id smtpd016630; Thu Feb 12 16:06:23 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id QAA04054; Thu, 12 Feb 1998 16:06:22 -0700 (MST) From: Terry Lambert Message-Id: <199802122306.QAA04054@usr02.primenet.com> Subject: Re: Heads up: static -ification To: eivind@yes.no (Eivind Eklund) Date: Thu, 12 Feb 1998 23:06:22 +0000 (GMT) Cc: wollman@khavrinen.lcs.mit.edu, eivind@yes.no, current@FreeBSD.ORG In-Reply-To: <19980212161814.38690@follo.net> from "Eivind Eklund" at Feb 12, 98 04:18:14 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 > > ``Layering is a great model for designing protocols, but an incredibly > > lousy way of implementing them.'' > > - D. D. Clark > > That quote is often true for protocols, yes. OTOH, I haven't yet > found a way of implementing advanced protocols that isn't lousy. Have you ever heard of a "monostack"? In a traditional streams implementation, given when streams runs, a protocol stack will not run to completion pushing message either up or down (or if they are badly arranged, both directions). A "monostack" overcomes this problem by creating a monolithic protocol, per traditional designs, and then exporting discrete protocol components. For instance, I might have a monostack that implements IP, ICMP, UDP, and TCP, and exports each of these interfaces as if they were segregable, when in fact they were not. Because of this, an inbound or outbound TCP packet can run to completion through the stack without incurring a streams scheduling overhead from the processing order not matching the stacking order. > At least for operating systems, message-passing systems tend to be > beautifully simple. The main problem is that if you do them in a > memory-protected environment your performance tend to suck. And you can't get orangebook certification using statistical memory protections. ;-). 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 current" in the body of the message From owner-freebsd-current Thu Feb 12 15:39:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29958 for current-outgoing; Thu, 12 Feb 1998 15:39:50 -0800 (PST) (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 PAA29951 for ; Thu, 12 Feb 1998 15:39:47 -0800 (PST) (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 PAA04815; Thu, 12 Feb 1998 15:38:55 -0800 (PST) Message-Id: <199802122338.PAA04815@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sepotvin@videotron.ca cc: current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 In-reply-to: Your message of "Thu, 12 Feb 1998 18:24:43 EST." <34E384BA.8D863AA2@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Feb 1998 15:38:54 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Do you have more information on what's wrong in the lp driver? I can't really > switch to ethernet right now so maybe it's better if I try to find out what is > really happening. Any starting pointers on what could be wrong would be > appreciated as it will be my first attempt at working on a FreeBSD (or network > for that matter) driver. If you are serious about working on the PLIP code, may I suggest that you try to separate it out and integrate with the ppbus code in -current (/sys/dev/ppbus). This is where development on the parallel port is going. -- \\ 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 current" in the body of the message From owner-freebsd-current Thu Feb 12 15:44:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00702 for current-outgoing; Thu, 12 Feb 1998 15:44:15 -0800 (PST) (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 PAA00695 for ; Thu, 12 Feb 1998 15:44:10 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id XAA22141; Thu, 12 Feb 1998 23:44:03 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id AAA29113; Fri, 13 Feb 1998 00:44:02 +0100 (MET) Message-ID: <19980213004401.13104@follo.net> Date: Fri, 13 Feb 1998 00:44:02 +0100 From: Eivind Eklund To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: Heads up: static -ification References: <19980212143844.44164@follo.net> <199802122311.QAA04342@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199802122311.QAA04342@usr02.primenet.com>; from Terry Lambert on Thu, Feb 12, 1998 at 11:11:45PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 12, 1998 at 11:11:45PM +0000, Terry Lambert wrote: > > The problem is that we have subsystems that share symbols internally, but > > shouldn't expose those symbols to the rest of the world. I'd like a > > hierarchical model where we the kernel is the top node of a tree, and each > > node in the tree have a defined exported interface, and all symbols not in > > that interface will be removed. Each node will be implemented as an object > > file, but might be constructed by re-linking subnodes through ld -r and a > > pass through symorder -c to zap non-wanted symbols. > > > > This has two good effects: > > (1) Limiting exposure of symbols as much as possible, so incestous > > relationships don't develop so easily. > > (2) Minimizing re-link time, as only the parts of the kernel that > > really has changed will be re-linked. > > > > OTOH, I think this might be too large a change for people to swallow. > > It wants the kernel build tree reorganized on module boundries. This isn't a necessity, though it would be nice. See below for details. > As an aside, so does multiple architecture support. > > As another aside, filesystems want to be in /sys/fs instead of spread > all over the source tree at random locations. > > So a source tree reorganization is due. As a first step on this, could you help me try to define which files ought to belong in which module? You can see the start of one of my attempts in the patch at http://freefall.freebsd.org/~eivind/module-link.patch which goes against a config'ed LINT from today's current; as you can see, it tend to show a lot of exposure, and possibly not match the module boundaries too well :-( If the basic idea here seems feasible, I was thinking along the lines of an extra file for config(8) with a syntax somewhat like makefiles, but with allowed symbols replacing the shell commands of a regular makefile. Could I ask you another favour, too? Can you look over the proposal I sent to -hackers about a week ago under the subject "Proposal for IPFW interface change, w/potentially larger application"? It is basically a system for building binary objects in kernel space from userland by starting with a default and modifying it; it should allow the IPFW interface to be upgraded without breaking binary compatibility. I wasn't able to solicit _any_ feedback on this :-( I have three potential levels for it: (1) IPFW interface only, with the above benefits (2) Generalized kernel interface for building and retrieving objects this way; would allow us to kill most of kmem dragons fairly easily. (3) Generalized object and capability buildning system. Would allow us to view ipfw as a routing capability, and would allow a lot of other capability manipulation (including port access limitations and file system access limitations for child processes). and I desperately need feedback on what (if any) of this people think would be useful, and in what direction to target my implementation (which I need for work purposes). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 15:54:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02041 for current-outgoing; Thu, 12 Feb 1998 15:54:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp160.103.mmtl.videotron.net [207.253.103.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02017 for ; Thu, 12 Feb 1998 15:54:02 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost.videotron.ca [127.0.0.1]) by azimov.videotron.ca (8.8.8/8.8.8) with ESMTP id SAA10557; Thu, 12 Feb 1998 18:54:34 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34E38BB5.E10D67B3@videotron.ca> Date: Thu, 12 Feb 1998 18:54:30 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith CC: current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <199802122338.PAA04815@dingo.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 Mike Smith wrote: > > > > Do you have more information on what's wrong in the lp driver? I can't really > > switch to ethernet right now so maybe it's better if I try to find out what is > > really happening. Any starting pointers on what could be wrong would be > > appreciated as it will be my first attempt at working on a FreeBSD (or network > > for that matter) driver. > > If you are serious about working on the PLIP code, may I suggest that > you try to separate it out and integrate with the ppbus code in > -current (/sys/dev/ppbus). This is where development on the parallel > port is going. If nobody else is currently working on that I'm willing to give it a try. -- Stephane E. Potvin sepotvin@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 16:04:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04343 for current-outgoing; Thu, 12 Feb 1998 16:04:25 -0800 (PST) (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 QAA04333 for ; Thu, 12 Feb 1998 16:04:24 -0800 (PST) (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 QAA04968; Thu, 12 Feb 1998 16:03:38 -0800 (PST) Message-Id: <199802130003.QAA04968@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sepotvin@videotron.ca cc: current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 In-reply-to: Your message of "Thu, 12 Feb 1998 18:54:30 EST." <34E38BB5.E10D67B3@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Feb 1998 16:03:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If you are serious about working on the PLIP code, may I suggest that > > you try to separate it out and integrate with the ppbus code in > > -current (/sys/dev/ppbus). This is where development on the parallel > > port is going. > > If nobody else is currently working on that I'm willing to give it a try. There's no active work going on, as far as I am aware. I would suggest having a look at the 'nlpt' driver to see how access to the bus is arbitrated, and then start building the 'lp' driver as a separate animal. Please feel free to post questions about the process on -hackers or direct to me. I ought to get the ppbus mailing list back together again, as there are a number of people very interested in this. You might also want to check out the latest ppbus code, as there are some changes in there that may be of use to you. -- \\ 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 current" in the body of the message From owner-freebsd-current Thu Feb 12 16:11:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05956 for current-outgoing; Thu, 12 Feb 1998 16:11:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05943; Thu, 12 Feb 1998 16:10:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA14327; Fri, 13 Feb 1998 11:07:30 +1100 Date: Fri, 13 Feb 1998 11:07:30 +1100 From: Bruce Evans Message-Id: <199802130007.LAA14327@godzilla.zeta.org.au> To: current@FreeBSD.ORG Subject: panic in vm_pager_has_page() Cc: dyson@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This seems to fix the panic in vm_pager_has_page() when nfs file systems are forcibly unmounted by `umount -Af -t nfs'. (pagertab[OBJT_DEAD] is invalid.) Bruce diff -c2 src/sys/vm/vm_fault.c~ src/sys/vm/vm_fault.c *** src/sys/vm/vm_fault.c~ Tue Feb 10 05:17:46 1998 --- src/sys/vm/vm_fault.c Tue Feb 10 05:17:47 1998 *************** *** 290,294 **** while (TRUE) { ! if (object->flags & OBJ_DEAD) { UNLOCK_AND_DEALLOCATE; return (KERN_PROTECTION_FAILURE); --- 290,294 ---- while (TRUE) { ! if (object->flags & OBJ_DEAD || object->type == OBJT_DEAD) { UNLOCK_AND_DEALLOCATE; return (KERN_PROTECTION_FAILURE); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Thu Feb 12 17:29:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18952 for freebsd-current-outgoing; Thu, 12 Feb 1998 17:29:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18914; Thu, 12 Feb 1998 17:28:52 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199802130128.RAA18914@hub.freebsd.org> Subject: Re: Heads up: static -ification In-Reply-To: <19980212161814.38690@follo.net> from Eivind Eklund at "Feb 12, 98 04:18:14 pm" To: eivind@yes.no (Eivind Eklund) Date: Thu, 12 Feb 1998 17:28:52 -0800 (PST) Cc: wollman@khavrinen.lcs.mit.edu, eivind@yes.no, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > > That quote is often true for protocols, yes. OTOH, I haven't yet > found a way of implementing advanced protocols that isn't lousy. And > one of the problems with most layered protocol implementations is that > they don't take the layering far enough - they throw in a lot of > indirect calls and non-visible state as their 'layers', instead of > abstracting enough and consider each layer a process. > > At least for operating systems, message-passing systems tend to be > beautifully simple. The main problem is that if you do them in a > memory-protected environment your performance tend to suck. compare nit (netowrk interface tap) and bpf (berkeley packet filter) load due to bpf increases as the number of packets accepted by the filter increases. load due to nit increases as the number of packets on the wire increases. there was a usenix paper about this. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 12 17:31:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19821 for freebsd-current-outgoing; Thu, 12 Feb 1998 17:31:51 -0800 (PST) (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 RAA19743; Thu, 12 Feb 1998 17:31:32 -0800 (PST) (envelope-from dyson@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA14633; Thu, 12 Feb 1998 20:31:21 -0500 (EST) (envelope-from dyson) Message-Id: <199802130131.UAA14633@dyson.iquest.net> Subject: Re: panic in vm_pager_has_page() In-Reply-To: <199802130007.LAA14327@godzilla.zeta.org.au> from Bruce Evans at "Feb 13, 98 11:07:30 am" To: bde@zeta.org.au (Bruce Evans) Date: Thu, 12 Feb 1998 20:31:20 -0500 (EST) Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans said: > This seems to fix the panic in vm_pager_has_page() when nfs file systems > are forcibly unmounted by `umount -Af -t nfs'. (pagertab[OBJT_DEAD] is > invalid.) > That is a good 1st order fix, but I should also create a dead entry. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you 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 Thu Feb 12 17:57:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25287 for freebsd-current-outgoing; Thu, 12 Feb 1998 17:57:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.31.78.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25281 for ; Thu, 12 Feb 1998 17:57:32 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id UAA17632; Thu, 12 Feb 1998 20:56:47 -0500 (EST) Date: Thu, 12 Feb 1998 20:56:46 -0500 (EST) From: "Matthew N. Dodd" To: Terry Lambert cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: Heads up: static -ification In-Reply-To: <199802122311.QAA04342@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 12 Feb 1998, Terry Lambert wrote: > As another aside, filesystems want to be in /sys/fs instead of spread > all over the source tree at random locations. Maybe a /sys/net too? /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 12 18:11:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27066 for freebsd-current-outgoing; Thu, 12 Feb 1998 18:11:51 -0800 (PST) (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 SAA27051 for ; Thu, 12 Feb 1998 18:11:44 -0800 (PST) (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 MAA10745 for ; Fri, 13 Feb 1998 12:41:38 +1030 (CST) Message-Id: <199802130211.MAA10745@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.ORG Subject: Linux GGI Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Feb 1998 12:41:38 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have come across the GGI project, which aims to allow access to graphics devices easily, and without having SUID binaries around - also allows multiple monitors and keyboards etc.. I am thinking of porting it to FreeBSD, because it actually looks descent - well, their goals are good anyway :) They have kernel bits which have to be added which are going to be the hard stuff, but I am working on the userland stuff at the moment. Anyone else interested? The URL for the GGI Homepage is http://synergy.caltech.edu/~ggi/ --------------------------------------------------------------------- |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 Thu Feb 12 18:14:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27531 for freebsd-current-outgoing; Thu, 12 Feb 1998 18:14:38 -0800 (PST) (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 SAA27509 for ; Thu, 12 Feb 1998 18:14:36 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id TAA01853; Thu, 12 Feb 1998 19:14:34 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd001834; Thu Feb 12 19:14:29 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id TAA09562; Thu, 12 Feb 1998 19:14:25 -0700 (MST) From: Terry Lambert Message-Id: <199802130214.TAA09562@usr07.primenet.com> Subject: Re: Heads up: static -ification To: winter@jurai.net (Matthew N. Dodd) Date: Fri, 13 Feb 1998 02:14:25 +0000 (GMT) Cc: tlambert@primenet.com, eivind@yes.no, current@FreeBSD.ORG In-Reply-To: from "Matthew N. Dodd" at Feb 12, 98 08:56:46 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 > On Thu, 12 Feb 1998, Terry Lambert wrote: > > As another aside, filesystems want to be in /sys/fs instead of spread > > all over the source tree at random locations. > > Maybe a /sys/net too? This is why I think it needs a discussion... A wholesale rewrite of history means that if you check out a historical version, it should still build after the rewrite. There's already need for a rewrite because of the trademark issues that people keep bending over for... at least there needs to be a standard direction to bend. 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 Feb 12 18:46:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02268 for freebsd-current-outgoing; Thu, 12 Feb 1998 18:46:43 -0800 (PST) (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 SAA02263 for ; Thu, 12 Feb 1998 18:46:40 -0800 (PST) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA29547; Thu, 12 Feb 1998 19:46:38 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd029513; Thu Feb 12 19:46:32 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id TAA11073; Thu, 12 Feb 1998 19:46:30 -0700 (MST) From: Terry Lambert Message-Id: <199802130246.TAA11073@usr07.primenet.com> Subject: Re: Linux GGI To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Fri, 13 Feb 1998 02:46:29 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199802130211.MAA10745@cain.gsoft.com.au> from "Daniel O'Connor" at Feb 13, 98 12:41:38 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have come across the GGI project, which aims to allow access to graphics > devices easily, and without having SUID binaries around - also allows multiple > monitors and keyboards etc.. > I am thinking of porting it to FreeBSD, because it actually looks descent - > well, their goals are good anyway :) > > They have kernel bits which have to be added which are going to be the hard > stuff, but I am working on the userland stuff at the moment. > > Anyone else interested? > The URL for the GGI Homepage is http://synergy.caltech.edu/~ggi/ FWIW: This is the Linux project "DDX in the Kernel" that I was referring to the other week, and couldn't remember the name of the thing. This project, from what I can tell, comes as close as anything ever has to the original fall 1993 "Grand Unified Console Design" that never got built. 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 Feb 12 18:50:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02891 for freebsd-current-outgoing; Thu, 12 Feb 1998 18:50:13 -0800 (PST) (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 SAA02859; Thu, 12 Feb 1998 18:50:04 -0800 (PST) (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 SAA28900; Thu, 12 Feb 1998 18:50:02 -0800 (PST) (envelope-from jdp) Message-Id: <199802130250.SAA28900@austin.polstra.com> To: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: WARNING: Parallel CVSup sessions are frowned upon! Date: Thu, 12 Feb 1998 18:50:02 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of the CVSup mirror site maintainers has complained to me that a person has been making 5 simultaneous connections to his server, thereby shutting out other innocent users from the system. This is not only incredibly anti-social, it is also kind of dumb. Normally, 5 simultaneous updates won't run significantly faster than 5 sequential ones. So people, don't do this! You know who you are. Whether you manage a single machine or a group of them, please run only one update at a time from the FreeBSD mirrors. If you need to update multiple machines, do them at different times. Or better yet, install the cvsup-mirror port and update just one "master" machine from a FreeBSD mirror. Then update your other machines from the master. Every connection is logged. We have all the information we need to blacklist the offenders if necessary, thereby denying them access to the servers. Please don't force us to take that step. Be sensible and be considerate. Thank you. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 12 18:52:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03584 for freebsd-current-outgoing; Thu, 12 Feb 1998 18:52:22 -0800 (PST) (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 SAA03578 for ; Thu, 12 Feb 1998 18:52:19 -0800 (PST) (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 NAA11449; Fri, 13 Feb 1998 13:22:05 +1030 (CST) Message-Id: <199802130252.NAA11449@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: Linux GGI In-reply-to: Your message of "Fri, 13 Feb 1998 02:46:29 -0000." <199802130246.TAA11073@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Feb 1998 13:22:04 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This project, from what I can tell, comes as close as anything ever > has to the original fall 1993 "Grand Unified Console Design" that > never got built. Hmm.. well IMHO its a good idea.. I'm a little dubious about their kernel mods tho, but I am going to look at them in depth soon, which should prove interesting. I can't say I'm looking forward to porting them though =) --------------------------------------------------------------------- |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 Thu Feb 12 19:54:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11586 for freebsd-current-outgoing; Thu, 12 Feb 1998 19:54:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11576; Thu, 12 Feb 1998 19:54:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA05201; Thu, 12 Feb 1998 19:54:17 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802130354.TAA05201@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "Jonathan M. Bresler" cc: tlambert@primenet.com (Terry Lambert), dg@root.com, adrian@obiwan.creative.net.au, jlemon@americantv.com, current@FreeBSD.ORG Subject: Re: Hollywood (Re: PATCH.M ) In-reply-to: Your message of "Thu, 12 Feb 1998 13:13:24 PST." <199802122113.NAA02966@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Feb 1998 19:54:17 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Terry Lambert wrote: > > > > PS: Did someone specifically kill the mailing of my PATCH.C that > > contained the actual patches? > > no one killed it. > it was over the max message size of 40,000 bytes. You can bring down again to 40k thats more than enough for a general purpose mailing list beyond that I think is a better idea to provide an ftp or http pointer. Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 12 20:59:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21004 for freebsd-current-outgoing; Thu, 12 Feb 1998 20:59:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20978 for ; Thu, 12 Feb 1998 20:58:54 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA05232; Thu, 12 Feb 1998 19:56:08 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802130356.TAA05232@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: doconnor@gsoft.com.au (Daniel O'Connor), current@FreeBSD.ORG Subject: Re: Linux GGI In-reply-to: Your message of "Fri, 13 Feb 1998 02:46:29 GMT." <199802130246.TAA11073@usr07.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Feb 1998 19:56:08 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I have known about them for a little while . Doing low level graphics chipset support is not an easy job and requires highly skilled and dedicated personnel. Regards, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 12 23:39:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12846 for freebsd-current-outgoing; Thu, 12 Feb 1998 23:39:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA12829 for ; Thu, 12 Feb 1998 23:39:40 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 11623 invoked by uid 1001); 13 Feb 1998 07:38:52 +0000 (GMT) To: jmb@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Heads up: static -ification In-Reply-To: Your message of "Thu, 12 Feb 1998 17:28:52 -0800 (PST)" References: <199802130128.RAA18914@hub.freebsd.org> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 13 Feb 1998 08:38:52 +0100 Message-ID: <11621.887355532@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > load due to bpf increases as the number of packets accepted > by the filter increases. > > load due to nit increases as the number of packets on the wire > increases. > > there was a usenix paper about this. McCanne, S., and Jacobson, V.: The BSD Packet Filter: A New Architecture for User-level Packet Capture. Proceedings of the 1993 Winter USENIX Technical Conference (San Diego, CA, Jan. 1993), USENIX. Available from ftp://ftp.ee.lbl.gov/papers/bpf-usenix93.ps.Z. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 00:28:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21046 for freebsd-current-outgoing; Fri, 13 Feb 1998 00:28:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21041 for ; Fri, 13 Feb 1998 00:28:47 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id IAA01718; Fri, 13 Feb 1998 08:51:36 +0100 (MET) (envelope-from sos) Message-Id: <199802130751.IAA01718@sos.freebsd.dk> Subject: Re: Linux GGI In-Reply-To: <199802130211.MAA10745@cain.gsoft.com.au> from Daniel O'Connor at "Feb 13, 98 12:41:38 pm" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Fri, 13 Feb 1998 08:51:35 +0100 (MET) Cc: current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Daniel O'Connor who wrote: > Hi, > I have come across the GGI project, which aims to allow access to graphics > devices easily, and without having SUID binaries around - also allows multiple > monitors and keyboards etc.. > I am thinking of porting it to FreeBSD, because it actually looks descent - > well, their goals are good anyway :) Hmm, you have plenty of spare time I guess :) > They have kernel bits which have to be added which are going to be the hard > stuff, but I am working on the userland stuff at the moment. > > Anyone else interested? > The URL for the GGI Homepage is http://synergy.caltech.edu/~ggi/ I've looked at this long ago, and it sounds real nice... However, I dont see it having much success with the rate new Video Chipsets occur currently. There is no chance in hell for holding up on this... Its worth looking after though, if they manage to get enough momentum behind them, it might challenge the Xfree guys, and competition newer hurts :) Let me know if you need help with the kernel/video parts, I know my way around there ;) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Feb 13 05:04:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22606 for freebsd-current-outgoing; Fri, 13 Feb 1998 05:04:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22589 for ; Fri, 13 Feb 1998 05:04:35 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id PAA00955; Fri, 13 Feb 1998 15:03:20 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 13 Feb 1998 15:03:20 +0200 (EET) From: Penisoara Adrian Reply-To: Penisoara Adrian To: "Stephane E. Potvin" cc: freebsd-current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 In-Reply-To: <34DF6E3C.4A6C11B5@videotron.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Mon, 9 Feb 1998, Stephane E. Potvin wrote: > Terry Lambert wrote: > > > Are you running IP firewall? > > I've tried a kernel (3.0-CURRENT #0: Mon Feb 9 14:25:19 EST 1998) with > IPFIREWALL disabled and got the same trap 12. > > I doubt that it is hardware related as I have 2 computers experiencing the > same problem. Is there anyone else able to reproduce it? If not then I'll > begin to check my hardware for a defective part. I might be one case; This is 3.0-971117-SNAP here, but it might very well be the same problem as current of the day; if not, all my apologises... Situation: -> sio0 + sio1 used for PPP over leased lines (which tend to be pretty noisy some times) ; I believe this might be the source of the problems, as someone else did have problems with lp0... -> 2 PCI ethernet cards -> IP Firewalling activated, "open" type Thing is that I saw one time a "65535 1 60 deny ip from any to any" in my "security check output" but it can't be this, I experienced panics like this even before activating IPFW ====[ Hand rewritten panic that I experienced this morning ]==== Fatak trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0xc0004 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01b81ae stack pointer = 0x10:0xf49b3b48 frame pointer = 0x10:0xf4933b60 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 = 12879 (sendmail) interrupt mask = net bio cam <- SMP:XXX trap number = 12 panic: page fault mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 boot() called on cpu#0 syncing disks ============================================================ nm /kernel | sort | more : --------------------------- f01b7028 T _pmap_protect f01b7248 T _pmap_enter f01b74ac t _pmap_enter_quick f01b7584 T _pmap_object_init_pt f01b7898 T _pmap_prefault f01b7a60 T _pmap_change_wiring f01b7b08 T _pmap_copy f01b7cc4 T _pmap_kernel f01b7cf0 T _pmap_zero_page f01b7d90 T _pmap_copy_page f01b7e3c T _pmap_pageable f01b7e44 T _pmap_page_exists f01b7f0c T _pmap_remove_pages f01b8048 t _pmap_testbit ** f01b8110 t _pmap_changebit ** f01b8228 T _pmap_page_protect ** f01b8250 T _pmap_phys_address f01b825c T _pmap_ts_referenced f01b8324 T _pmap_is_modified f01b8334 T _pmap_clear_modify f01b8348 T _pmap_clear_reference f01b835c t _i386_protection_init f01b83e0 T _pmap_mapdev f01b8460 T _pmap_mincore f01b855c T _pmap_activate f01b85b8 T _pmap_addr_hint And related to this, David Greenman suggested that my problem might be a bug in execve() from kern_exec.c ; I has been a month since I patched the kernel and I got again 2 panics of this kind. So execve() is out of discussion for me. (What about PR#5313 though ?) > > -- > Stephane E. Potvin > sepotvin@videotron.ca > Hoping this helps somehow... Ady (@warpnet.ro) Warp Net Technologies To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 08:04:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12748 for freebsd-current-outgoing; Fri, 13 Feb 1998 08:04:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ache.relcom.ru (ache@ache.relcom.ru [193.125.20.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12615; Fri, 13 Feb 1998 08:03:48 -0800 (PST) (envelope-from ache@ache.relcom.ru) Received: (from ache@localhost) by ache.relcom.ru (8.8.8/8.8.8) id TAA00278; Fri, 13 Feb 1998 19:00:59 +0300 (MSK) (envelope-from ache) Message-ID: <19980213190058.19651@nagual.pp.ru> Date: Fri, 13 Feb 1998 19:00:58 +0300 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: phk@FreeBSD.ORG, current@FreeBSD.ORG, yokota@FreeBSD.ORG, sos@FreeBSD.ORG Subject: syscons becomes worse somwhere in v1.252-1.255 Mail-Followup-To: phk@freebsd.org, current@freebsd.org, yokota@freebsd.org, sos@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now I got sc0: WARNING: video mode switching is only partially supported I never got before, moreover 8bit characters used for cursor displays some junk while they stay as normal characters with v1.251 version. I.e. v1.251 works ideally for me. I not look yet which particular commit from v1.252 to v1.255 broke it exactly, but I plan to look ASAP. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 08:53:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18239 for freebsd-current-outgoing; Fri, 13 Feb 1998 08:53:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ache.relcom.ru (ache@ache.relcom.ru [193.125.20.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17624; Fri, 13 Feb 1998 08:48:59 -0800 (PST) (envelope-from ache@ache.relcom.ru) Received: (from ache@localhost) by ache.relcom.ru (8.8.8/8.8.8) id TAA00301; Fri, 13 Feb 1998 19:39:40 +0300 (MSK) (envelope-from ache) Message-ID: <19980213193928.28090@nagual.pp.ru> Date: Fri, 13 Feb 1998 19:39:28 +0300 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: phk@FreeBSD.ORG, current@FreeBSD.ORG, yokota@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: syscons becomes worse somwhere in v1.252-1.255 Mail-Followup-To: phk@FreeBSD.ORG, current@FreeBSD.ORG, yokota@FreeBSD.ORG, sos@FreeBSD.ORG References: <19980213190058.19651@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.89.1i In-Reply-To: <19980213190058.19651@nagual.pp.ru>; from ache@nagual.pp.ru on Fri, Feb 13, 1998 at 07:00:58PM +0300 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 13, 1998 at 07:00:58PM +0300, áÎÄÒÅÊ þÅÒÎÏ× wrote: > Now I got > sc0: WARNING: video mode switching is only partially supported > I never got before, moreover 8bit characters used for cursor > displays some junk while they stay as normal characters with v1.251 > version. Exact details: 1) sc0: WARNING: video mode switching is only partially supported introduced in v1.254 2) Junk in 8bit character introduced in v1.252 with removing #define SC_MOUSE_CHAR (0x03) For 1) - phk, please fix. For 2) - I think we need to make 0x03 ad _default_ mouse character code instead of 0xd0 as was before. 0xd0 very depends on code table used and points to valid used character in many tables while 0x03 don't confuse anybody since lower controls not used in termcap entries and for national character too. Any objections? -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 09:12:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20696 for freebsd-current-outgoing; Fri, 13 Feb 1998 09:12:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20581; Fri, 13 Feb 1998 09:10:43 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id SAA11827; Fri, 13 Feb 1998 18:11:11 +0100 (MET) (envelope-from sos) Message-Id: <199802131711.SAA11827@sos.freebsd.dk> Subject: Re: syscons becomes worse somwhere in v1.252-1.255 In-Reply-To: <19980213193928.28090@nagual.pp.ru> from "[______ ______]" at "Feb 13, 98 07:39:28 pm" To: ache@nagual.pp.ru (=?koi8-r?B?4c7E0sXKIP7F0s7P1w==?=) Date: Fri, 13 Feb 1998 18:11:10 +0100 (MET) Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG, yokota@FreeBSD.ORG, sos@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to [______ ______] who wrote: [Charset koi8-r unsupported, filtering to ASCII...] > > For 2) - I think we need to make 0x03 ad _default_ mouse character code > instead of 0xd0 as was before. 0xd0 very depends on code table used and > points to valid used character in many tables while 0x03 don't confuse > anybody since lower controls not used in termcap entries and for national > character too. Any objections? YES! it makes the mouse cursor look really bad if the chars is not in the interval 0xc0-0xdf. In that interval you can pick and chose... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 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 Feb 13 09:41:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25654 for freebsd-current-outgoing; Fri, 13 Feb 1998 09:41:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lsd.relcom.eu.net (ache@lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25544; Fri, 13 Feb 1998 09:41:28 -0800 (PST) (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.8/8.8.8) id UAA05585; Fri, 13 Feb 1998 20:41:12 +0300 (MSK) (envelope-from ache) Message-ID: <19980213204110.51597@nagual.pp.ru> Date: Fri, 13 Feb 1998 20:41:10 +0300 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: sos@FreeBSD.ORG Cc: current@FreeBSD.ORG, yokota@FreeBSD.ORG Subject: mouse chars default (was Re: syscons becomes worse somwhere in v1.252-1.255) Mail-Followup-To: sos@FreeBSD.ORG, current@freebsd.org, yokota@freebsd.org References: <19980213193928.28090@nagual.pp.ru> <199802131711.SAA11827@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.89.1i In-Reply-To: <199802131711.SAA11827@sos.freebsd.dk>; from sos@FreeBSD.ORG on Fri, Feb 13, 1998 at 06:11:10PM +0100 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 13, 1998 at 06:11:10PM +0100, Søren Schmidt wrote: > In reply to [______ ______] who wrote: > [Charset koi8-r unsupported, filtering to ASCII...] > > > > For 2) - I think we need to make 0x03 ad _default_ mouse character code > > instead of 0xd0 as was before. 0xd0 very depends on code table used and > > points to valid used character in many tables while 0x03 don't confuse > > anybody since lower controls not used in termcap entries and for national > > character too. Any objections? > > YES! it makes the mouse cursor look really bad if the chars is not in > the interval 0xc0-0xdf. In that interval you can pick and chose... You mean thin vertical black lines in mouse cursor? I even didn't notice them until you point on it, so "really bad" is too strong phrase :-) Well, I agree. The question remains what is worse for _default_: national characters overlap (i.e. Russian termcap entry already is in conflict with 0xd0 and with any 0xc0-0xdf characters) or thin vertical lines in mouse cursor... -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 09:50:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27584 for freebsd-current-outgoing; Fri, 13 Feb 1998 09:50:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27432; Fri, 13 Feb 1998 09:49:01 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id SAA00373; Fri, 13 Feb 1998 18:44:13 +0100 (CET) To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= cc: sos@FreeBSD.ORG, current@FreeBSD.ORG, yokota@FreeBSD.ORG Subject: Re: mouse chars default (was Re: syscons becomes worse somwhere in v1.252-1.255) In-reply-to: Your message of "Fri, 13 Feb 1998 20:41:10 +0300." <19980213204110.51597@nagual.pp.ru> Date: Fri, 13 Feb 1998 18:44:13 +0100 Message-ID: <371.887391853@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980213204110.51597@nagual.pp.ru>, =?koi8-r?B?4c7E0sXKIP7F0s7P1w== ?= writes: >On Fri, Feb 13, 1998 at 06:11:10PM +0100, Søren Schmidt wrote: >> In reply to [______ ______] who wrote: >> [Charset koi8-r unsupported, filtering to ASCII...] >> > >> > For 2) - I think we need to make 0x03 ad _default_ mouse character code >> > instead of 0xd0 as was before. 0xd0 very depends on code table used and >> > points to valid used character in many tables while 0x03 don't confuse >> > anybody since lower controls not used in termcap entries and for national >> > character too. Any objections? >> >> YES! it makes the mouse cursor look really bad if the chars is not in >> the interval 0xc0-0xdf. In that interval you can pick and chose... > >You mean thin vertical black lines in mouse cursor? I even didn't notice >them until you point on it, so "really bad" is too strong phrase :-) >Well, I agree. The question remains what is worse for _default_: national >characters overlap (i.e. Russian termcap entry already is in conflict with >0xd0 and with any 0xc0-0xdf characters) or thin vertical lines in mouse >cursor... But the russian font doesn't need that special double-pixel, right ? so just remap the russian chars to another range when displaying... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 10:17:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01761 for freebsd-current-outgoing; Fri, 13 Feb 1998 10:17:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lsd.relcom.eu.net (root@lsd.relcom.eu.net [193.124.23.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01727; Fri, 13 Feb 1998 10:17:32 -0800 (PST) (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.8/8.8.8) id VAA05787; Fri, 13 Feb 1998 21:02:07 +0300 (MSK) (envelope-from ache) Message-ID: <19980213210206.11762@nagual.pp.ru> Date: Fri, 13 Feb 1998 21:02:06 +0300 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG, yokota@FreeBSD.ORG Subject: Re: mouse chars default (was Re: syscons becomes worse somwhere in v1.252-1.255) Mail-Followup-To: Poul-Henning Kamp , current@freebsd.org, sos@freebsd.org, yokota@freebsd.org References: <19980213204110.51597@nagual.pp.ru> <371.887391853@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <371.887391853@critter.freebsd.dk>; from phk@critter.freebsd.dk on Fri, Feb 13, 1998 at 06:44:13PM +0100 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 13, 1998 at 06:44:13PM +0100, Poul-Henning Kamp wrote: > In message <19980213204110.51597@nagual.pp.ru>, =?koi8-r?B?4c7E0sXKIP7F0s7P1w== > But the russian font doesn't need that special double-pixel, right ? > so just remap the russian chars to another range when displaying... No, Russian font needs double-pixel for pseudographics and remapping already used to match VGA hardware font special range. BTW, I find "right" mouse cursor (without thin black vertical lines) somehow ugly because when it is placed over f.e. ASCII letter, 9 pixels line flips on the fly, i.e. 8-9 pixel expansion happens for normal ASCII character, it never happens with "broken" mouse cursor started from 0x03. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 11:30:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16325 for freebsd-current-outgoing; Fri, 13 Feb 1998 11:30:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16309; Fri, 13 Feb 1998 11:30:04 -0800 (PST) (envelope-from gozer@ludd.luth.se) Received: from sister.ludd.luth.se (gozer@sister.ludd.luth.se [130.240.16.77]) by zed.ludd.luth.se (8.8.5/8.8.5) with SMTP id UAA29015; Fri, 13 Feb 1998 20:29:45 +0100 Date: Fri, 13 Feb 1998 20:29:44 +0100 (MET) From: Johan Larsson To: Dmitrij Tejblum cc: FreeBSD Current , FreeBSD Hackers Subject: Re: Fat32 In-Reply-To: <199802111228.PAA03112@tejblum.dnttm.rssi.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 11 Feb 1998, Dmitrij Tejblum wrote: > Johan Larsson wrote: > > What happened to this? Is there any development going on? Or did it just > > die? It would be very nice to see it in current. I am running this just > > now, and it seems to work fine. How much testing would it require before > > it gets commited. > > I hope you seen the discussion in the other thread on -current, so you > know answers to the questions. But please tell me: do you have FAT32 or > VFAT? If FAT32, you are the first man in the world, who mounted a FAT32 > partition on FreeBSD :-) Well, now i have mounted a fat32 partition under freebsd, and it seems to work just fine!! :-) I must say that if not the msdosfs-netbsd.diff don't get in to -current i will be extremely disappointed :) Johan -- * mailto:gozer@ludd.luth.se * http://www.ludd.luth.se/users/gozer/ * * Powered by FreeBSD. http://www.se.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 Feb 13 11:30:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16723 for freebsd-current-outgoing; Fri, 13 Feb 1998 11:30:59 -0800 (PST) (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 LAA16713 for ; Fri, 13 Feb 1998 11:30:56 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA18677; Fri, 13 Feb 1998 12:30:54 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd018649; Fri Feb 13 12:30:50 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id MAA03251; Fri, 13 Feb 1998 12:30:46 -0700 (MST) From: Terry Lambert Message-Id: <199802131930.MAA03251@usr01.primenet.com> Subject: Re: Linux GGI To: hasty@rah.star-gate.com (Amancio Hasty) Date: Fri, 13 Feb 1998 19:30:46 +0000 (GMT) Cc: tlambert@primenet.com, doconnor@gsoft.com.au, current@FreeBSD.ORG In-Reply-To: <199802130356.TAA05232@rah.star-gate.com> from "Amancio Hasty" at Feb 12, 98 07:56:08 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, I have known about them for a little while . Doing low level > graphics chipset support is not an easy job and requires highly skilled > and dedicated personnel. Or you could just grab the code from XFree86, which already has highly skilled and dedicated personnel, and make it into an LKM, *after* you have the hooks defined for it to latch itself in. 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 Feb 13 11:56:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24178 for freebsd-current-outgoing; Fri, 13 Feb 1998 11:56:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24142 for ; Fri, 13 Feb 1998 11:56:51 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id LAA04693; Fri, 13 Feb 1998 11:56:30 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802131956.LAA04693@rah.star-gate.com> To: Terry Lambert cc: hasty@rah.star-gate.com (Amancio Hasty), doconnor@gsoft.com.au, current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Linux GGI In-reply-to: Your message of "Fri, 13 Feb 1998 19:30:46 GMT." <199802131930.MAA03251@usr01.primenet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4690.887399790.1@rah> Date: Fri, 13 Feb 1998 11:56:30 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Terry, Yes, I have taken a look at that section of the code also I used literally live inside the ddx section when I was hacking on XS3. This is really a job for the XFree86 folks to split it up and the reason for that is so that we can all then enjoy their support. 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 Fri Feb 13 12:24:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29458 for freebsd-current-outgoing; Fri, 13 Feb 1998 12:24:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29442 for ; Fri, 13 Feb 1998 12:24:44 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id WAA00653; Fri, 13 Feb 1998 22:24:08 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Fri, 13 Feb 1998 22:24:08 +0200 (EET) From: Penisoara Adrian To: "Stephane E. Potvin" cc: current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 In-Reply-To: <34E4A0C8.B474DD6A@videotron.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 13 Feb 1998, Stephane E. Potvin wrote: [ ...bunch o' HTML junked by Pine deleted... ] >  Do you have bpfilter enabled? I just found out this morning > that disabling it seems to make the problem go away. I have no bpf's installed (though I'm going to some time in the future)... BTW, the problem is manifesting pretty rarely and it's hard to catch... The system could go OK for days, but when it goes down it's really nasty -- I mean you can't blame anything, the logs look very clean. I'd say give it time and you'll it's going to byte (the dust ?) again... > 
-- 
> Stephane E. Potvin
> sepotvin@videotron.ca
>   > PS: please try to disable HTML in your mails, we're on a Unix list... Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 13:33:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12725 for freebsd-current-outgoing; Fri, 13 Feb 1998 13:33:03 -0800 (PST) (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 NAA12648 for ; Fri, 13 Feb 1998 13:32:42 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id VAA10148; Fri, 13 Feb 1998 21:32:36 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id WAA05867; Fri, 13 Feb 1998 22:32:36 +0100 (MET) Message-ID: <19980213223236.56066@follo.net> Date: Fri, 13 Feb 1998 22:32:36 +0100 From: Eivind Eklund To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: Linux GGI References: <199802130246.TAA11073@usr07.primenet.com> <199802130356.TAA05232@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199802130356.TAA05232@rah.star-gate.com>; from Amancio Hasty on Thu, Feb 12, 1998 at 07:56:08PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 12, 1998 at 07:56:08PM -0800, Amancio Hasty wrote: > > Yes, I have known about them for a little while . Doing low level > graphics chipset support is not an easy job and requires highly skilled > and dedicated personnel. Eh? Unless some magic has happened during the last year or so (which was when I stopped doing this), it isn't really a hard problem, just a lot of work. There are other areas (protocol implementations come to mind) where there are _much_ larger dragons. But there are a lot of chipsets these days - even if each one isn't a really hard problem, tackling all of them require either a lot of dedication or a lot of personell, or preferably both. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 13:39:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14152 for freebsd-current-outgoing; Fri, 13 Feb 1998 13:39:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14120 for ; Fri, 13 Feb 1998 13:39:23 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: (from hasty@localhost) by rah.star-gate.com (8.8.8/8.8.8) id NAA05267; Fri, 13 Feb 1998 13:39:15 -0800 (PST) (envelope-from hasty) Date: Fri, 13 Feb 1998 13:39:15 -0800 (PST) From: Amancio Hasty Message-Id: <199802132139.NAA05267@rah.star-gate.com> To: eivind@yes.no, hasty@rah.star-gate.com Subject: Re: Linux GGI Cc: current@FreeBSD.ORG In-Reply-To: <19980213223236.56066@follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Eh? Unless some magic has happened during the last year or so (which Just talking from experience and yes supporting different chipsets is a big undertaking as for the protocol aspects althought difficult we can probably tackle them given that we will have access to the sources --- it is a bit different to circumvent bugs in planted in silicon. At any rate, all this discussion is nice and fun -- I am going back to hacking 8) 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 Fri Feb 13 14:49:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24516 for freebsd-current-outgoing; Fri, 13 Feb 1998 14:49:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ady.warpnet.ro (ady.warpnet.ro [193.230.201.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24499 for ; Fri, 13 Feb 1998 14:48:55 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.8.8/8.8.8) with SMTP id AAA00385; Sat, 14 Feb 1998 00:48:30 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Sat, 14 Feb 1998 00:48:29 +0200 (EET) From: Penisoara Adrian To: "Stephane E. Potvin" cc: current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, On Fri, 13 Feb 1998, Penisoara Adrian wrote: > BTW, the problem is manifesting pretty rarely and it's hard to catch... > The system could go OK for days, but when it goes down it's really nasty > -- I mean you can't blame anything, the logs look very clean. > > I'd say give it time and you'll it's going to byte (the dust ?) again... > Well, today I hammered the server with FTP downloads (2 concurent wget's, half Gb worth of data) -- and after some time it has fallen on its knees. Please notice that I took care to eliminate everything it could have upset the beast: PPP daemons, squid daemon, nntpcache daemon; kernel still did have IPFW, but, as I told you, problems were showing even before adding IPFW. One thing I observed is that the panic is manifestig mostly when network traffic is in progress and another process is started in the mean time, but this is just a presumption somehow. It's getting harder and harder for me to nail this one down... Ady (@warpnet.ro), hoping I'll get my hands on a stable SNAP real soon... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 15:20:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00408 for freebsd-current-outgoing; Fri, 13 Feb 1998 15:20:24 -0800 (PST) (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 PAA00382 for ; Fri, 13 Feb 1998 15:20:15 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA02923 for ; Fri, 13 Feb 1998 15:11:46 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd002917; Fri Feb 13 15:11:41 1998 Date: Fri, 13 Feb 1998 15:07:52 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Subject: Working (apparently) soft-update code available. 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 look in: ftp://ftp.freebsd.org/pub/FreeBSD/incoming/softupdates4.tgz first extract the README and read it before extracting everything. this should patch cleanly against last night's -current. try a make world before and after.. particularly, make /var/tmp and/or /usr/obj use softupdates. for a real laugh, try timing deletion of a large directory hierarchy.. enjoy.. courtesy of: Kirk Mckusick John Dyson, Whistle Communications. (Julian Terry and Archie) this at least should put an end to the "ext2fs is faster" arguments, even if they are based on apple/oranges comparisons. :-) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 16:00:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09535 for freebsd-current-outgoing; Fri, 13 Feb 1998 16:00:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09366 for ; Fri, 13 Feb 1998 15:59:43 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id CAA29463; Sat, 14 Feb 1998 02:58:09 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id DAA02201; Sat, 14 Feb 1998 03:05:09 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802140005.DAA02201@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Johan Larsson cc: FreeBSD Current Subject: Re: Fat32 In-reply-to: Your message of "Fri, 13 Feb 1998 20:29:44 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 03:05:09 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan Larsson wrote: > Well, now i have mounted a fat32 partition under freebsd, and it seems to > work just fine!! :-) I must say that if not the msdosfs-netbsd.diff don't > get in to -current i will be extremely disappointed :) Thanks! Now, could somebody please test this patch on PC98? MSDOSFS has some PC98 ifdefs, and I could occasionaly break the PC98 support. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 17:28:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27765 for freebsd-current-outgoing; Fri, 13 Feb 1998 17:28:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27743 for ; Fri, 13 Feb 1998 17:28:50 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id UAA25313; Fri, 13 Feb 1998 20:27:59 -0500 (EST) Date: Fri, 13 Feb 1998 20:27:59 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: Working (apparently) soft-update code available. 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, 13 Feb 1998, Julian Elischer wrote: > > look in: > ftp://ftp.freebsd.org/pub/FreeBSD/incoming/softupdates4.tgz > > first extract the README and read it before extracting everything. > this should patch cleanly against last night's -current. Julian, is this safe for an SMP system? > > try a make world before and after.. > particularly, > make /var/tmp and/or /usr/obj use softupdates. > > for a real laugh, try timing deletion of a large directory hierarchy.. > > enjoy.. > > courtesy of: > Kirk Mckusick > John Dyson, > Whistle Communications. (Julian Terry and Archie) > > this at least should put an end to the > "ext2fs is faster" arguments, even if they are based on apple/oranges > comparisons. :-) > > > julian > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 17:40:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29594 for freebsd-current-outgoing; Fri, 13 Feb 1998 17:40:25 -0800 (PST) (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 RAA29588 for ; Fri, 13 Feb 1998 17:40:23 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA07233; Fri, 13 Feb 1998 17:35:24 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd007228; Fri Feb 13 17:35:20 1998 Date: Fri, 13 Feb 1998 17:31:32 -0800 (PST) From: Julian Elischer To: Chuck Robey cc: current@FreeBSD.ORG Subject: Re: Working (apparently) soft-update code available. 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 John Dyson has tested on one but I think you should be careful (use it on an expendable partition.) On Fri, 13 Feb 1998, Chuck Robey wrote: > On Fri, 13 Feb 1998, Julian Elischer wrote: > > > > > look in: > > ftp://ftp.freebsd.org/pub/FreeBSD/incoming/softupdates4.tgz > > > > first extract the README and read it before extracting everything. > > this should patch cleanly against last night's -current. > > Julian, is this safe for an SMP system? > > > > > try a make world before and after.. > > particularly, > > make /var/tmp and/or /usr/obj use softupdates. > > > > for a real laugh, try timing deletion of a large directory hierarchy.. > > > > enjoy.. > > > > courtesy of: > > Kirk Mckusick > > John Dyson, > > Whistle Communications. (Julian Terry and Archie) > > > > this at least should put an end to the > > "ext2fs is faster" arguments, even if they are based on apple/oranges > > comparisons. :-) > > > > > > julian > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 18:39:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08048 for freebsd-current-outgoing; Fri, 13 Feb 1998 18:39:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA07827; Fri, 13 Feb 1998 18:38:37 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA14549; Sat, 14 Feb 1998 11:38:10 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA19177; Sat, 14 Feb 1998 11:45:45 +0900 (JST) Message-Id: <199802140245.LAA19177@zodiac.mech.utsunomiya-u.ac.jp> To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG, yokota@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: syscons becomes worse somwhere in v1.252-1.255 In-Reply-To: Your message of "Fri, 13 Feb 1998 19:39:28 +0300." <19980213193928.28090@nagual.pp.ru> References: <19980213190058.19651@nagual.pp.ru> <19980213193928.28090@nagual.pp.ru> Date: Sat, 14 Feb 1998 11:45:44 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >2) Junk in 8bit character introduced in v1.252 with removing >#define SC_MOUSE_CHAR (0x03) This #define was accidentally introduced in v.1.251 and removed in v1.252. The behavior of syscons WITHOUT the define is the same as versions up to v.1.250. >For 2) - I think we need to make 0x03 ad _default_ mouse character code >instead of 0xd0 as was before. 0xd0 very depends on code table used and >points to valid used character in many tables while 0x03 don't confuse >anybody since lower controls not used in termcap entries and for national >character too. Any objections? This issue has been brought up several times before, and I myself discussed it with sos recently. The thing is we are in loose-loose situation. We can't have both: good-looking mouse cursor and national character support. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 18:40:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08144 for freebsd-current-outgoing; Fri, 13 Feb 1998 18:40:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08058 for ; Fri, 13 Feb 1998 18:39:42 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.5) with ESMTP id UAA02339; Fri, 13 Feb 1998 20:39:24 -0600 (CST) Message-Id: <199802140239.UAA02339@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: Working (apparently) soft-update code available. In-reply-to: Your message of "Fri, 13 Feb 1998 15:07:52 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Feb 1998 20:39:24 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it seems that my machine must just hate me, because I can't seem to get them to work for more than a few minutes. Been having lots of bad luck lately though.. oh well. :( Anyways, I do have a few comments.. I have gotten the following panic many times. It seems to occur even when I do not have soft updates turned on for any of my file systems. :/ panic: softdep_disk_io_initiation: read >From looking at the code, this seems to indicate that dependancies are being formed for read operations as well. This seems somewhat disturbing.. any ideas? >look in: >ftp://ftp.freebsd.org/pub/FreeBSD/incoming/softupdates4.tgz > >first extract the README and read it before extracting everything. >this should patch cleanly against last night's -current. In the readme, you might want to mention running 'make includes' or something before building the userland programs. If you don't, some of the defines are not defined. :) >try a make world before and after.. >particularly, >make /var/tmp and/or /usr/obj use softupdates. > >for a real laugh, try timing deletion of a large directory hierarchy.. I was curious about this.. when i rm'd my /usr/obj, it took about 30 seconds or so. This seems like a while to me.. I guess maybe I am impatient though. ;) Although it seemed faster in OpenBSD, i can't accurately compare due to possible caching effects. (in FreeBSD, the tree was completely untouched beforhand--not recently untarred) Either way, I was curious about the sync/async stats given in mount. It seems that some operations are still being done sync?! Also, perhaps the stats should be an option to mount rather than given by default.. >enjoy.. > >courtesy of: >Kirk Mckusick >John Dyson, >Whistle Communications. (Julian Terry and Archie) Thanks much to all involved. :) I have been looking forward to seeing this work done and integrated for while now. >this at least should put an end to the >"ext2fs is faster" arguments, even if they are based on apple/oranges >comparisons. :-) I can't wait. :) It's rediculous, but still annoying to keep hearing this one. Chris > >julian > > >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 Feb 13 18:42:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09013 for freebsd-current-outgoing; Fri, 13 Feb 1998 18:42:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08981 for ; Fri, 13 Feb 1998 18:42:22 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.5) with ESMTP id UAA02339; Fri, 13 Feb 1998 20:39:24 -0600 (CST) Message-Id: <199802140239.UAA02339@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: Working (apparently) soft-update code available. In-reply-to: Your message of "Fri, 13 Feb 1998 15:07:52 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Feb 1998 20:39:24 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it seems that my machine must just hate me, because I can't seem to get them to work for more than a few minutes. Been having lots of bad luck lately though.. oh well. :( Anyways, I do have a few comments.. I have gotten the following panic many times. It seems to occur even when I do not have soft updates turned on for any of my file systems. :/ panic: softdep_disk_io_initiation: read >From looking at the code, this seems to indicate that dependancies are being formed for read operations as well. This seems somewhat disturbing.. any ideas? >look in: >ftp://ftp.freebsd.org/pub/FreeBSD/incoming/softupdates4.tgz > >first extract the README and read it before extracting everything. >this should patch cleanly against last night's -current. In the readme, you might want to mention running 'make includes' or something before building the userland programs. If you don't, some of the defines are not defined. :) >try a make world before and after.. >particularly, >make /var/tmp and/or /usr/obj use softupdates. > >for a real laugh, try timing deletion of a large directory hierarchy.. I was curious about this.. when i rm'd my /usr/obj, it took about 30 seconds or so. This seems like a while to me.. I guess maybe I am impatient though. ;) Although it seemed faster in OpenBSD, i can't accurately compare due to possible caching effects. (in FreeBSD, the tree was completely untouched beforhand--not recently untarred) Either way, I was curious about the sync/async stats given in mount. It seems that some operations are still being done sync?! Also, perhaps the stats should be an option to mount rather than given by default.. >enjoy.. > >courtesy of: >Kirk Mckusick >John Dyson, >Whistle Communications. (Julian Terry and Archie) Thanks much to all involved. :) I have been looking forward to seeing this work done and integrated for while now. >this at least should put an end to the >"ext2fs is faster" arguments, even if they are based on apple/oranges >comparisons. :-) I can't wait. :) It's rediculous, but still annoying to keep hearing this one. Chris > >julian > > >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 Feb 13 18:46:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10318 for freebsd-current-outgoing; Fri, 13 Feb 1998 18:46:12 -0800 (PST) (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 SAA10260 for ; Fri, 13 Feb 1998 18:46:05 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id TAA07513; Fri, 13 Feb 1998 19:46:00 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd007482; Fri Feb 13 19:45:59 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id TAA12922; Fri, 13 Feb 1998 19:45:57 -0700 (MST) From: Terry Lambert Message-Id: <199802140245.TAA12922@usr06.primenet.com> Subject: Re: Working (apparently) soft-update code available. To: chuckr@glue.umd.edu (Chuck Robey) Date: Sat, 14 Feb 1998 02:45:57 +0000 (GMT) Cc: julian@whistle.com, current@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Feb 13, 98 08:27:59 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 > > look in: > > ftp://ftp.freebsd.org/pub/FreeBSD/incoming/softupdates4.tgz > > > > first extract the README and read it before extracting everything. > > this should patch cleanly against last night's -current. > > Julian, is this safe for an SMP system? As long as you are using the Big Giant Lock, it should be safe. The syncer process that replaces updated runs as a kernel process; this means that it's a process in the kernel address space and with a seperate stack. In theory, this will prevent you from coming in an doing something while it's doing something. But this theory depends on the Big Giant Lock in the scheduler. A pushdown below the system call trap layer could make this dangerous, unless done exactly right. Heed Julian's warning and run it on an expendable partition. I would be very interested in seeing a three-process thrash on a two processor machine (or an N+1 process thrash on an N processor machine) to see if you can kick it in the groin through the scheduler (SMP FreeBSD does not have CPU affinity in the form of seperate scheduler queues with a roll count for the idle process to determine the right time to do load migration). "We didn't make the Big Giant Lock, we only made it Big and Giant!" -- FreeBSD/SMP 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 Feb 13 19:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15273 for freebsd-current-outgoing; Fri, 13 Feb 1998 19:10:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA15235; Fri, 13 Feb 1998 19:10:18 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA14650; Sat, 14 Feb 1998 12:09:48 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id MAA19828; Sat, 14 Feb 1998 12:17:38 +0900 (JST) Message-Id: <199802140317.MAA19828@zodiac.mech.utsunomiya-u.ac.jp> To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG, sos@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons becomes worse somwhere in v1.252-1.255 In-Reply-To: Your message of "Sat, 14 Feb 1998 11:45:44 JST." <199802140245.LAA19177@zodiac.mech.utsunomiya-u.ac.jp> References: <19980213190058.19651@nagual.pp.ru> <19980213193928.28090@nagual.pp.ru> <199802140245.LAA19177@zodiac.mech.utsunomiya-u.ac.jp> Date: Sat, 14 Feb 1998 12:17:37 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>For 2) - I think we need to make 0x03 ad _default_ mouse character code >>instead of 0xd0 as was before. 0xd0 very depends on code table used and >>points to valid used character in many tables while 0x03 don't confuse >>anybody since lower controls not used in termcap entries and for national >>character too. Any objections? > >This issue has been brought up several times before, and I myself >discussed it with sos recently. The thing is we are in loose-loose >situation. We can't have both: good-looking mouse cursor and national >character support. > >Kazu Don't take the above statement to mean I am against the idea. I personally think the use of control code for the mouse cursor quite acceptable (that's why I tested the code with "#define SC_MOUSE_CHAR 0x03"). But, the consensus has been in favor of 0xd0. Anyway, those who can accept less-good-looking mouse cursor can have the option option "SC_MOUSE_CHAR=0x??" in the kernel configuration file. That's the whole point, I think. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 19:17:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16538 for freebsd-current-outgoing; Fri, 13 Feb 1998 19:17:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16530 for ; Fri, 13 Feb 1998 19:16:56 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id UAA21379; Fri, 13 Feb 1998 20:16:54 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd021355; Fri Feb 13 20:16:50 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id UAA15274; Fri, 13 Feb 1998 20:16:48 -0700 (MST) From: Terry Lambert Message-Id: <199802140316.UAA15274@usr06.primenet.com> Subject: Re: Working (apparently) soft-update code available. To: ccsanady@friley585.res.iastate.edu (Chris Csanady) Date: Sat, 14 Feb 1998 03:16:48 +0000 (GMT) Cc: julian@whistle.com, current@FreeBSD.ORG In-Reply-To: <199802140239.UAA02339@friley585.res.iastate.edu> from "Chris Csanady" at Feb 13, 98 08:39:24 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have gotten the following panic many times. It seems to occur even > when I do not have soft updates turned on for any of my file systems. :/ > > panic: softdep_disk_io_initiation: read > > From looking at the code, this seems to indicate that dependancies are > being formed for read operations as well. This seems somewhat > disturbing.. any ideas? Not about the panic. But the read dependencies are real. Consider the case where I'm making a change to a directory, and I delete one file then create another. Both go in the same page, but not in the same directory block. Pages are read-before-write for sub-page sized changes. You really need to give more information than you are giving before it's possible to actually intelligently track down the bug; like what exactly were you doing to get the panic? I can make a guess, though: In practice, the stub routines will not get called unless the soft updates are on; are you using the stubbed version of the calls and turning the updates on on the stubs? This won't work. > Either way, I was curious about the sync/async stats given in mount. > It seems that some operations are still being done sync?! Also, > perhaps the stats should be an option to mount rather than given > by default.. This is a case of ungathered writes. There's a pool of time slots, and things are placed in slots "some time in the future". The effect if the syncd is to actually "gather" writes to objects scheduled to be written, but not yet written. If you cause vnode recycling (of vnodes with dirty buffers), or your dependency tree depth exceeds the number of slots, then you will get dependency-forced writes before the time limit expires. There are actually two ways you could tune up something to avoid this; one of them is a global (I can't rememebr the name without the code in front of me, sorry), and you should up the number. The other is to push the scheduler window into the future, so events get thrown in in the same order, but the events you process are delayed afterwards (It's a bit of work, but I'll probably play with it at some time). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 19:21:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17540 for freebsd-current-outgoing; Fri, 13 Feb 1998 19:21:33 -0800 (PST) (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 TAA17535 for ; Fri, 13 Feb 1998 19:21:31 -0800 (PST) (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 TAA22163; Fri, 13 Feb 1998 19:21:28 -0800 (PST) (envelope-from jdp) Message-Id: <199802140321.TAA22163@austin.polstra.com> To: julian@whistle.com Subject: Re: Working (apparently) soft-update code available. In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Fri, 13 Feb 1998 19:21:28 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Julian Elischer wrote: > > look in: > ftp://ftp.freebsd.org/pub/FreeBSD/incoming/softupdates4.tgz Great! But ... what is this doing in there?? > Index: sys/pci/if_de.c > =================================================================== > RCS file: /cvs/freebsd/src/sys/pci/if_de.c,v > retrieving revision 1.79 > diff -c -r1.79 if_de.c > *** if_de.c 1998/02/06 12:14:08 1.79 > --- if_de.c 1998/02/13 22:39:06 > *************** > *** 1,3 **** > --- 1,5 ---- > + #undef __FreeBSD__ > + #define __FreeBSD__ 3 > /* $NetBSD: if_de.c,v 1.56 1997/10/20 14:32:46 matt Exp $ */ > /* $Id: if_de.c,v 1.79 1998/02/06 12:14:08 eivind Exp $ */ > John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 19:30:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18294 for freebsd-current-outgoing; Fri, 13 Feb 1998 19:30:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from plugcom.ru (uucp@radiance.plugcom.ru [195.2.73.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18284 for ; Fri, 13 Feb 1998 19:30:04 -0800 (PST) (envelope-from tarkhil@minas-tirith.pol.ru) Received: from minas-tirith.pol.ru (uucp@localhost) by plugcom.ru (8.8.7/8.8.6) with UUCP id GAA01171 for FreeBSD.ORG!freebsd-current; Sat, 14 Feb 1998 06:30:01 +0300 (MSK) Received: from minas-tirith.pol.ru (tarkhil@tarkhil.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.7/8.8.7) with ESMTP id BAA19020 for ; Sat, 14 Feb 1998 01:01:47 +0300 (MSK) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199802132201.BAA19020@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.1 12/23/97 To: FreeBSD.ORG!freebsd-current@minas-tirith.pol.ru Subject: Problems building -stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 01:01:44 +0300 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I understand that there's little chance to make something good on Thriday, 13, full moon, but... I've CVSup'ed latest 2_2_RELENG and tried to make release. I've got the following errors: cc -O2 -pipe -DLIBC_RCS -DSYSLIBC_RCS -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I /usr/src/lib/libc/../libc/locale -DYP -c /usr/src/lib/libc/../libc/gen/getvfsen t .c -o getvfsent.o /usr/src/lib/libc/../libc/gen/getvfsent.c:58: conflicting types for `getvfsent' /usr/include/sys/mount.h:472: previous declaration of `getvfsent' /usr/src/lib/libc/../libc/gen/getvfsent.c:80: conflicting types for `new_getvfsb yname' ... and so on. I think I should use some specific date to fetch out buildable release, can anyone point me to it? Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 19:46:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20036 for freebsd-current-outgoing; Fri, 13 Feb 1998 19:46:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20028 for ; Fri, 13 Feb 1998 19:46:17 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.5) with ESMTP id VAA00664; Fri, 13 Feb 1998 21:46:13 -0600 (CST) Message-Id: <199802140346.VAA00664@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: Terry Lambert cc: julian@whistle.com, current@FreeBSD.ORG Subject: Re: Working (apparently) soft-update code available. In-reply-to: Your message of "Sat, 14 Feb 1998 03:16:48 GMT." <199802140316.UAA15274@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Feb 1998 21:46:12 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >You really need to give more information than you are giving before >it's possible to actually intelligently track down the bug; like >what exactly were you doing to get the panic? Well, when the system comes up sometimes, it panics during the fsck's. It also panics after untarring a file for a little while on a partition with soft updates enabled. I will look into it a bit more. I also have some ccd's, but that shouldn't be a problem I don't think.. Anyone else have any experiences with the code? >I can make a guess, though: > >In practice, the stub routines will not get called unless the soft >updates are on; are you using the stubbed version of the calls >and turning the updates on on the stubs? This won't work. I believe that I was using the real file. It is distributed with the real file in place. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 19:46:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20114 for freebsd-current-outgoing; Fri, 13 Feb 1998 19:46:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20077 for ; Fri, 13 Feb 1998 19:46:23 -0800 (PST) (envelope-from kato@migmatite.eps.nagoya-u.ac.jp) Received: from localhost (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.8/3.6Wbeta7) with ESMTP id LAA06572; Sat, 14 Feb 1998 11:53:15 +0900 (JST) To: dima@tejblum.dnttm.rssi.ru Cc: freebsd-current@FreeBSD.ORG Subject: Re: Fat32 From: KATO Takenori In-Reply-To: Your message of "Sat, 14 Feb 1998 03:05:09 +0300" <199802140005.DAA02201@tejblum.dnttm.rssi.ru> References: <199802140005.DAA02201@tejblum.dnttm.rssi.ru> X-Mailer: Mew version 1.92.4 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980214115315K.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 14 Feb 1998 11:53:15 +0900 X-Dispatcher: imput version 971024 Lines: 17 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitrij Tejblum wrote: > Now, could somebody please test this patch on PC98? MSDOSFS has some PC98 > ifdefs, and I could occasionaly break the PC98 support. Very dirty PC98 code in msdosfs is used for 1024 bytes/sector floppy disk, and it does not work in -current. It used 386BSD's B_XXX2 flag but FreeBSD does not have such flag. IMO, breakage of PC98 code in msdosfs has no problem, and 1024 bytes/sector floppy support should be revised. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) ------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 21:29:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29620 for freebsd-current-outgoing; Fri, 13 Feb 1998 21:29:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29612 for ; Fri, 13 Feb 1998 21:29:09 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.5) with ESMTP id XAA00351; Fri, 13 Feb 1998 23:29:05 -0600 (CST) Message-Id: <199802140529.XAA00351@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: Working (apparently) soft-update code available. In-reply-to: Your message of "Fri, 13 Feb 1998 20:39:24 CST." <199802140239.UAA02339@friley585.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Feb 1998 23:29:05 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have gotten the following panic many times. It seems to occur even >when I do not have soft updates turned on for any of my file systems. :/ > >panic: softdep_disk_io_initiation: read Ok, I have found the problem. You can not use the soft updates patches with CCD's. Even if you do not have them turned on for anything, the panic still occurs. This should be fairly reproducable, so I hope that someone with a little more clue than myself can track down the problem. I booted my system single-user with no CCD's, and played with an FS with soft updates for quite a while. It seems perfectly stable, and it is damn fast. :) Thanks again for the great work.. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 13 21:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01970 for freebsd-current-outgoing; Fri, 13 Feb 1998 21:45:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01964 for ; Fri, 13 Feb 1998 21:45:01 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id WAA20962 for ; Fri, 13 Feb 1998 22:34:17 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp04.primenet.com, id smtpd020955; Fri Feb 13 22:34:10 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id WAA25250 for current@freebsd.org; Fri, 13 Feb 1998 22:34:10 -0700 (MST) From: Terry Lambert Message-Id: <199802140534.WAA25250@usr01.primenet.com> Subject: NFS locking patches -- status update To: current@FreeBSD.ORG Date: Sat, 14 Feb 1998 05:34:10 +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 Well, I've received one bug report on the NFS locking patches. If anyone else is playing with them, here's how you should send me debug information: 1) Do a truss/ktrace on the offending program; I need to know if it's a flock, lockf, or fcntl based lock causing the problem for you. 2) Consider building a debug kernel. Since the option changes, I don't know if you can set "option LOCKF_DEBUG" in the kernel config or not, or under what conditions the debug sysctl's will show up. Best bet is to: a) build the kernel DEBUG to be sure to get the sysctl's b) At the top of /sys/kern/lockf.c, add "#define LOCKF_DEBUG"; if you are adventurous, you can try it as a kernel option; if it doesn't work, then the lockf_debug value won't show up in the sysctl output c) Get to the point where the bug *almost* is going to happen. d) sysctl lockf_debug to 1 (for entry logging), 2 (for overlap management), or 3 (for both). You will get a *lot* of debug output; if you have a small dmesg buffer, do them seperately 3) Send me the logs. I should be able to fix the problem very quickly. Thanks, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 01:36:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25452 for freebsd-current-outgoing; Sat, 14 Feb 1998 01:36:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bsdx.dyn.ml.org (root@pm335-40.dialip.mich.net [35.9.11.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25420 for ; Sat, 14 Feb 1998 01:36:08 -0800 (PST) (envelope-from mcdougall@ameritech.net) Received: from ameritech.net (user1@localhost.dyn.ml.org [127.0.0.1]) by bsdx.dyn.ml.org (8.8.8/8.8.7) with ESMTP id EAA25311 for ; Sat, 14 Feb 1998 04:36:01 -0500 (EST) (envelope-from mcdougall@ameritech.net) Message-ID: <34E56580.BAC4A1E5@ameritech.net> Date: Sat, 14 Feb 1998 04:36:00 -0500 From: Adam McDougall Reply-To: mcdougall@ameritech.net X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: SparQ drive support on -current? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wondering if anyone can confirm that the syquest Sparq works in -current (with wfd?) before I think about getting one. Its EIDE, its 1 gig removable media, its $199, and the carts are only $33. Sounds like a good deal to me, if it will work. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 01:59:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28800 for freebsd-current-outgoing; Sat, 14 Feb 1998 01:59:31 -0800 (PST) (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 BAA28789 for ; Sat, 14 Feb 1998 01:59:26 -0800 (PST) (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 BAA18953; Sat, 14 Feb 1998 01:59:01 -0800 (PST) Message-Id: <199802140959.BAA18953@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: mcdougall@ameritech.net cc: current@FreeBSD.ORG Subject: Re: SparQ drive support on -current? In-reply-to: Your message of "Sat, 14 Feb 1998 04:36:00 EST." <34E56580.BAC4A1E5@ameritech.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 01:59:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just wondering if anyone can confirm that the syquest Sparq works in > -current (with wfd?) before I think about getting one. Its EIDE, its 1 > gig removable media, its $199, and the carts are only $33. Sounds like > a good deal to me, if it will work. Thanks. Quite possibly not. It'll be an ATAPI removable, not an ATAPI floppy. This isn't the first ask we've had on this one; I'll try getting one in the next few days. -- \\ 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 Feb 14 07:52:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04738 for freebsd-current-outgoing; Sat, 14 Feb 1998 07:52:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04701 for ; Sat, 14 Feb 1998 07:52:11 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id SAA14491; Sat, 14 Feb 1998 18:45:41 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id SAA01922; Sat, 14 Feb 1998 18:52:06 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802141552.SAA01922@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: KATO Takenori cc: freebsd-current@FreeBSD.ORG Subject: Re: Fat32 In-reply-to: Your message of "Sat, 14 Feb 1998 11:53:15 +0900." <19980214115315K.kato@gneiss.eps.nagoya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 18:52:06 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG KATO Takenori wrote: > Dmitrij Tejblum wrote: > > > Now, could somebody please test this patch on PC98? MSDOSFS has some PC98 > > ifdefs, and I could occasionaly break the PC98 support. > > Very dirty PC98 code in msdosfs is used for 1024 bytes/sector floppy > disk, and it does not work in -current. It used 386BSD's B_XXX2 flag > but FreeBSD does not have such flag. It wasn't obvious for me. FreeBSD does not have B_XXX2 in , but it has the flag in, for example, vfs_bio.c and pc98/pc98/fd.c. B_XXX2 == B_ORDERED, though. > > IMO, breakage of PC98 code in msdosfs has no problem, and 1024 > bytes/sector floppy support should be revised. I think, idea of a machide-dependent filesystem also should be revised. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 08:34:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10879 for freebsd-current-outgoing; Sat, 14 Feb 1998 08:34:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10869 for ; Sat, 14 Feb 1998 08:34:40 -0800 (PST) (envelope-from kato@migmatite.eps.nagoya-u.ac.jp) Received: from localhost (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.8/3.6Wbeta7) with ESMTP id BAA03913; Sun, 15 Feb 1998 01:33:40 +0900 (JST) To: dima@tejblum.dnttm.rssi.ru Cc: freebsd-current@FreeBSD.ORG, FreeBSD98-hackers@jp.freebsd.org Subject: Re: Fat32 From: KATO Takenori In-Reply-To: Your message of "Sat, 14 Feb 1998 18:52:06 +0300" <199802141552.SAA01922@tejblum.dnttm.rssi.ru> References: <199802141552.SAA01922@tejblum.dnttm.rssi.ru> X-Mailer: Mew version 1.92.4 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980215013340A.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sun, 15 Feb 1998 01:33:40 +0900 X-Dispatcher: imput version 971024 Lines: 37 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (FreeBSD98-hackers@jp.freebsd.org is FreeBSD(98) developper's mailing list.) Dmitrij Tejblum wrote: > It wasn't obvious for me. FreeBSD does not have B_XXX2 in , but it > has the flag in, for example, vfs_bio.c and pc98/pc98/fd.c. > B_XXX2 == B_ORDERED, though. Sorry, I wrote wrong explanation about B_XXX2. Unused bit was assinged to B_XXX2 in old version. It didn't break any existing-code in FreeBSD. But, in today's FreeBSD, all bits in b_flags are defined and there is no space in b_flags to be assigned to B_XXX2. This is why PC-98 code is broken in current msdosfs. The breakage affects only 1024 byts/sector floppy disk (1024 byte/sector HDD are not supported in PC-98 port of FreeBSD), and 512 byts/sector disks can be used without problem. Does FreeBSD support 1024 bytes/sector block device? If so, PC-98 code could be implemented by another way which does not use b_flags. > > IMO, breakage of PC98 code in msdosfs has no problem, and 1024 > > bytes/sector floppy support should be revised. > > I think, idea of a machide-dependent filesystem also should be revised. I think 1024 bytes/sector support is independent of machin-arch. If fd driver supports it, IBM-PC users also can read/write such floppy disk. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) ------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 09:30:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15858 for freebsd-current-outgoing; Sat, 14 Feb 1998 09:30:38 -0800 (PST) (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 JAA15850 for ; Sat, 14 Feb 1998 09:30:33 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA06166 for current@freebsd.org; Sat, 14 Feb 1998 12:30:31 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802141730.MAA06166@dyson.iquest.net> Subject: Warning about -current bugs To: current@FreeBSD.ORG Date: Sat, 14 Feb 1998 12:30:31 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am sending this to lower expectations for another week. -current VM and VFS bugs will have to handled by others. There are certain areas where I might be the best person to work on the problems, but I have to be focused on product bugs for another week (using another, less stable OS.) Those who actually embark to fix any of my bugs, will get as much support from me as I can. However, it is likely that others can do as well as me -- but just wanted to say that if it is something that I should be doing, it might not get done!!! Sorry!!! -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you 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 Sat Feb 14 14:43:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00964 for freebsd-current-outgoing; Sat, 14 Feb 1998 14:43:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00952 for ; Sat, 14 Feb 1998 14:43:10 -0800 (PST) (envelope-from guest@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id OAA09495 for ; Sat, 14 Feb 1998 14:43:05 -0800 (PST) (envelope-from guest@mantar.slip.netcom.com) Date: Sat, 14 Feb 1998 14:43:04 -0800 (PST) From: Guest User To: current@FreeBSD.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 subscribe freebsd-current guest@mantar.slip.netcom.com subscribe freebsd-ports guest@mantar.slip.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 14:59:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02866 for freebsd-current-outgoing; Sat, 14 Feb 1998 14:59:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02861 for ; Sat, 14 Feb 1998 14:59:40 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (wether.sas.com [192.35.83.7]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id OAA00244 for ; Sat, 14 Feb 1998 14:49:59 -0500 (EST) Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA18968; Sat, 14 Feb 1998 14:49:59 -0500 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA25321; Sat, 14 Feb 1998 14:49:58 -0500 Message-Id: <199802141949.AA25321@iluvatar.unx.sas.com> Subject: Terry's DIFF.LEASE(Ok) & NFS V3 caching problem To: freebsd-current@FreeBSD.ORG Date: Sat, 14 Feb 1998 14:49:58 -0500 (EST) Cc: jwd@unx.sas.com (John W. DeBoskey) 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 Hello, I have applied DIFF.LEASE from Terry's FreeBSD Page. It was applied against the 3.0-980212-SNAP. The patched files: /usr/src/sys/kern: -rw-r--r-- 1 root wheel 12494 Dec 5 14:55 kern_ktrace.c.orig -rw-r--r-- 1 root wheel 11171 Nov 20 15:07 link_aout.c.orig -rw-r--r-- 1 root wheel 5593 Jan 23 21:54 tty_tty.c.orig -rw-r--r-- 1 root wheel 12670 Feb 6 07:13 vfs_vnops.c.orig with versions: * $Id: kern_ktrace.c,v 1.22 1997/12/05 19:55:38 bde Exp $ * $Id: link_aout.c,v 1.5 1997/11/20 20:07:50 bde Exp $ * $Id: tty_tty.c,v 1.22 1998/01/24 02:54:35 eivind Exp $ * $Id: vfs_vnops.c,v 1.49 1998/02/06 12:13:33 eivind Exp $ In and of themselves, the patches applied cleanly. Heavy NFS V3 usage to a network appliance F540 showed no problems. Thus, I give this patch a thumbs up with regards to my testing. The reason I applied these diffs was an attempt to see if they had any effect on the following problem. I have a file which is 16385 bytes on the NFS server. When the file is cat'd there is a series of additional rpc reads done due to incorrect EOF detection and partial block caching. The following sniffer output of the 1st cat execution shows this. Consecutive cat's always go to the server to read the final byte of the file. SUMMARY Delta T Dest Source Summary 46 [.11] [.213] NFS C LOOKUP 16385.bytes in FH=B056 47 0.00025 [.213] [.11] NFS R LOOKUP OK FH=B517 48 0.00014 [.11] [.213] NFS C ACCESS FH=B517 (Read) 49 0.00018 [.213] [.11] NFS R ACCESS OK (Read) 50 0.00027 [.11] [.213] NFS C FSINFO FH=B517 51 0.00018 [.213] [.11] NFS R FSINFO OK 52 0.00019 [.11] [.213] NFS C READ FH=B517 at 0 for 8192 53 0.00003 [.11] [.213] NFS C READ FH=B517 at 8192 for 8192 54 0.00058 [.213] [.11] NFS R READ OK 8192 bytes 58 0.00085 [.213] [.11] NFS R READ OK 8192 bytes 63 0.00050 [.11] [.213] NFS C READ FH=B517 at 16384 for 8192 66 0.00020 [.213] [.11] NFS R READ OK 1 byte (EOF) 67 0.00035 [.11] [.213] Read/write overlap NFS C READ FH=B517 at 16384 for 512 68 0.00024 [.213] [.11] NFS R READ OK 1 byte (EOF) 69 0.00016 [.11] [.213] File retransmission NFS C READ FH=B517 at 16384 for 512 70 0.00023 [.213] [.11] NFS R READ OK 1 byte (EOF) The following patch to nfs_bio.c removes the additional readrpc calls. It does not address the lack of caching of the last partial block of the file (a possible bug in the brelse() & vm_page_is_valid() fuctions or related code. ie: m->valid is 0). * @(#)nfs_bio.c 8.9 (Berkeley) 3/30/95 * $Id: nfs_bio.c,v 1.47 1998/01/25 06:24:09 dyson Exp $ # diff nfs_bio.c~ nfs_bio.c 242a243,246 > if (uio->uio_offset >= np->n_size) { /* Req past EOF? */ > n = 0; bp = 0; > break; > } 452a457,458 > if (uio->uio_offset >= np->n_size) > n=0; Unless there is a better way of fixing this problem, would someone please test & commit this small patch? Comments? Critiques? Thanks, John -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 15:12:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04841 for freebsd-current-outgoing; Sat, 14 Feb 1998 15:12:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04797 for ; Sat, 14 Feb 1998 15:12:03 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id AAA27520 for freebsd-current@FreeBSD.ORG; Sun, 15 Feb 1998 00:11:58 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id AAA00321; Sun, 15 Feb 1998 00:05:52 +0100 (CET) (envelope-from roberto) Message-ID: <19980215000552.55511@keltia.freenix.fr> Date: Sun, 15 Feb 1998 00:05:52 +0100 From: Ollivier Robert To: "FreeBSD Current Users' list" Subject: Panic within softupdates code Mail-Followup-To: FreeBSD Current Users' list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i X-Operating-System: FreeBSD 3.0-CURRENT ctm#4066 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got the following panic (following some complete locks of the system), running with softupdates4.tgz code. It generally happen during uuxqt runs when it unbatches news and feed them to INN. The stack trace (I was not under X this time) is panic: vm_fault on nofault entry, addr: f36b2000 _panic _vm_fault _trap_pfault _trap calltrap() --- trap 0xc, eip=0xf019dac2 _generic_bcopy _softdep_setup_allocindir_page _ffs_balloc _ffs_write _vn_write _writev _syscall _Xsyscall Kernel sources from cvs-cur 4066, a few hours ago. /dev/sd0a on / (local, writes: sync 9 async 133) /dev/sd0s2e on /usr (local, writes: sync 2 async 92) /dev/sd2s4a on /var (local, writes: sync 288 async 798) /dev/sd0s2f on /usr/local (local, writes: sync 2 async 71) /dev/sd0s2g on /users (local, writes: sync 18 async 53) /dev/sd2s4e on /news (local, noatime, nosuid, soft-updates, writes: sync 666 async 1025) /dev/sd0s2h on /src (local, noatime, soft-updates, writes: sync 2 async 0) /dev/sd2s4d on /spare (asynchronous, local, noatime, writes: sync 2 async 0) /dev/sd0s2d on /work (local, noatime, soft-updates, writes: sync 2 async 64) /dev/sd12a on /x (local, noatime, nosuid, soft-updates, writes: sync 2 async 0) /dev/sd2s4f on /y (local, noatime, soft-updates, writes: sync 2 async 0) /dev/sd1s1e on /z (local, noatime, soft-updates, writes: sync 2 async 1454) procfs on /proc (local, writes: sync 0 async 0) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #0: Sat Feb 14 15:42:16 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 16:13:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16742 for freebsd-current-outgoing; Sat, 14 Feb 1998 16:13:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16706 for ; Sat, 14 Feb 1998 16:13:29 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id VAA19778 for current@FreeBSD.ORG; Sat, 14 Feb 1998 21:13:15 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id VAA19488; Sat, 14 Feb 1998 21:06:46 +0100 (CET) (envelope-from roberto) Message-ID: <19980214210646.46577@keltia.freenix.fr> Date: Sat, 14 Feb 1998 21:06:46 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Working (apparently) soft-update code available. Mail-Followup-To: current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Julian Elischer on Fri, Feb 13, 1998 at 03:07:52PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4049 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Julian Elischer: > for a real laugh, try timing deletion of a large directory hierarchy.. > > enjoy.. I've tried the patches and I must say I'm impressed. Softupdates are faster than async for some things and much faster for others. "cp -pr" was just a little bit faster but bootstrapping egcs-980205 using "async,noatime" was about between 38 and 45 minutes. Using "soft-updates,noatime" gave me: 1478.805u 118.119s 27:39.27 96.2% 1627+2376k 7767+2440io 1019pf+0w I can't wait for a "make world" gain (waiting for the big CTM delta to arrive)... Before egcs bootstrap: -=-=-=-=- 233 [20:04] root@keltia:~# mount ... /dev/sd1s1e on /z (local, noatime, soft-updates, writes: sync 23 async 7324) -=-=-=-=- After completion of egcs compilation: -=-=-=-=- 234 [20:21] root@keltia:~# mount ... /dev/sd1s1e on /z (local, noatime, soft-updates, writes: sync 46 async 11749) -=-=-=-=- Thanks to Kirk, John, Julian and Whistle ! -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #56: Fri Feb 6 21:36:56 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 16:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23506 for freebsd-current-outgoing; Sat, 14 Feb 1998 16:57:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23496 for ; Sat, 14 Feb 1998 16:57:15 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id QAA13127 for ; Sat, 14 Feb 1998 16:57:09 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802150057.QAA13127@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: current@FreeBSD.ORG Subject: current is panicky with... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 16:57:09 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG During "heavy" i/o I am getting this panic , anyone has a clue as to why. This started happening as of yesterday, prior to that I didn't have any problems with compiling a kernel with -g. Tnks, Amancio Fatal trap 12: page fault while in kernel mode fault virtual address = 0xa4 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01fa8f0 stack pointer = 0x10:0xf47a9d6c frame pointer = 0x10:0xf47a9d78 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 = 2 (pagedaemon) interrupt mask = bio panic: from debugger panic: from debugger (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xf01178c7 in panic (fmt=0xf01013e8 "from debugger") at ../../kern/kern_shutdown.c:425 #2 0xf0101405 in db_panic (addr=-266360592, have_addr=0, count=1, modif=0xf47a9bec "") at ../../ddb/db_command.c:432 #3 0xf01012e5 in db_command (last_cmdp=0xf0201aa4, cmd_table=0xf0201904, aux_cmd_tablep=0xf020e344) at ../../ddb/db_command.c:332 #4 0xf0101472 in db_command_loop () at ../../ddb/db_command.c:454 #5 0xf0103b33 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #6 0xf01c2b81 in kdb_trap (type=12, code=0, regs=0xf47a9d30) at ../../i386/i386/db_interface.c:157 #7 0xf01d08bf in trap_fatal (frame=0xf47a9d30) at ../../i386/i386/trap.c:837 #8 0xf01d0368 in trap_pfault (frame=0xf47a9d30, usermode=0) at ../../i386/i386/trap.c:735 #9 0xf01cff97 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -266247204, tf_esi = 0, tf_ebp = -193290888, tf_isp = -193290920, tf_ebx = -261470208, tf_edx = -261470208, tf_ecx = -193290680, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -266360592, tf_cs = 8, tf_eflags = 66054, tf_esp = 1, tf_ss = -261470208}) at ../../i386/i386/trap.c:363 #10 0xf01fa8f0 in wfdstrategy (bp=0xf06a4800) at ../../i386/isa/wfd.c:429 #11 0xf0141c7e in spec_strategy (ap=0xf47a9e48) at ../../miscfs/specfs/spec_vnops.c:557 #12 0xf01af52a in swap_pager_putpages (object=0xf021ba50, m=0xf47a9f00, count=1, sync=0, rtvals=0xf47a9eb4) at vnode_if.h:1064 #13 0xf01ad492 in default_pager_putpages (object=0xf021ba50, m=0xf47a9f00, c=1, sync=0, rtvals=0xf47a9eb4) at ../../vm/default_pager.c:129 #14 0xf01bb06a in vm_pager_put_pages (object=0xf021ba50, m=0xf47a9f00, count=1, sync=0, rtvals=0xf47a9eb4) at ../../vm/vm_pager.c:193 #15 0xf01b9cde in vm_pageout_flush (mc=0xf47a9f00, count=1, sync=0) at ../../vm/vm_pageout.c:376 #16 0xf01b9c81 in vm_pageout_clean (m=0xf047c870, sync=0) at ../../vm/vm_pageout.c:359 #17 0xf01ba500 in vm_pageout_scan () at ../../vm/vm_pageout.c:842 #18 0xf01bad32 in vm_pageout () at ../../vm/vm_pageout.c:1259 #19 0xf010b21e in kproc_start (udata=0xf02087b0) at ../../kern/init_main.c:263 #20 0xf01c3e43 in fork_trampoline () Cannot access memory at address 0x1fff000. (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 16:59:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23879 for freebsd-current-outgoing; Sat, 14 Feb 1998 16:59:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23847 for ; Sat, 14 Feb 1998 16:59:13 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id QAA13152 for ; Sat, 14 Feb 1998 16:59:05 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802150059.QAA13152@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: current@FreeBSD.ORG Subject: about my last panic Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 16:59:05 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forgot to include this: 419 void wfdstrategy (struct buf *bp) 420 { 421 int lun = UNIT(bp->b_dev); 422 struct wfd *t = wfdtab[lun]; 423 int x; 424 (kgdb) 425 /* If it's a null transfer, return immediatly. */ 426 if (bp->b_bcount == 0) { 427 bp->b_resid = 0; 428 biodone (bp); 429 return; 430 } (kgdb) print *bp $4 = {b_hash = {le_next = 0x0, le_prev = 0x0}, b_vnbufs = { le_next = 0x87654321, le_prev = 0x0}, b_freelist = {tqe_next = 0x0, tqe_prev = 0x0}, b_act = {tqe_next = 0x0, tqe_prev = 0x0}, b_proc = 0xf022b7bc, b_flags = 67108944, b_qindex = 0, b_usecount = 0 '\000', b_error = 0, b_bufsize = 4096, b_bcount = 4096, b_resid = 0, b_dev = 256, b_data = 0xf39cf000 "", b_kvabase = 0x0, b_kvasize = 0, b_lblkno = 0, b_blkno = 544, b_iodone = 0xf01af970 , b_iodone_chain = 0x0, b_vp = 0xf479c560, b_dirtyoff = 0, b_dirtyend = 4096, b_generation = 0, b_rcred = 0xf068ac00, b_wcred = 0xf068ac00, b_validoff = 0, b_validend = 0, b_pblkno = 0, b_saveaddr = 0x0, b_savekva = 0x0, b_driver1 = 0x0, b_driver2 = 0x0, b_spc = 0xf02163dc, b_cluster = {cluster_head = { tqh_first = 0x0, tqh_last = 0x0}, cluster_entry = {tqe_next = 0x0, tqe_prev = 0x0}}, b_pages = {0x0 }, b_npages = 0} Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 17:39:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29150 for freebsd-current-outgoing; Sat, 14 Feb 1998 17:39:13 -0800 (PST) (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 RAA29128 for ; Sat, 14 Feb 1998 17:39:05 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA16244; Sat, 14 Feb 1998 18:27:28 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd014413; Sat Feb 14 18:17:18 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id SAA27759; Sat, 14 Feb 1998 18:17:14 -0700 (MST) From: Terry Lambert Message-Id: <199802150117.SAA27759@usr09.primenet.com> Subject: NFS CLIENT/SERVER LOCKING PATCHES NOW WORKING To: tech-kern@netbsd.org, kern@openbsd.org, current@FreeBSD.ORG Date: Sun, 15 Feb 1998 01:17:13 +0000 (GMT) Cc: terry@lambert.org 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 warning on the NFS kernel patches for NFS client and server locking has been removed, thanks to some dilligent tracing on the part of Chris Csanady. With these patches, modifications to the rpc.lockd, addition of an F_NONPOSIX fcntl to get rid of the clear-on-close behavior, and use of F_CNVT patches appropriate for whatever the wire format is to interface to VOP_FHTOVP, NFS server locking should be completely functional. NFS client locking requires that the non-veto nfs_advlock() function attempt to proxy the lock via RPC to the remote system, and if it fails, should veto the request. Note: I have not done anything to deal with blocking NFS lock requests; IMO, that code belongs in the rpc.lockd. The F_RSETLKW is specifically for support of a threaded implementation for proxied blocking locks. 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 Feb 14 17:53:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02136 for freebsd-current-outgoing; Sat, 14 Feb 1998 17:53:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (dyna2-169.acadiau.ca [131.162.2.169]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02130 for ; Sat, 14 Feb 1998 17:53:37 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id VAA24588 for ; Sat, 14 Feb 1998 21:53:30 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sat, 14 Feb 1998 21:53:29 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: Win95 long filenames on CDs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi... I have a cd of mp3's written on a Win95 system that, if viewed on the Win95 system, show up as long file names... Is there any way of seeing these under FreeBSD, or work being done towards this? I can view them as 8.3, but that losses most of the information... 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 Sat Feb 14 18:58:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08938 for freebsd-current-outgoing; Sat, 14 Feb 1998 18:58:28 -0800 (PST) (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 SAA08933 for ; Sat, 14 Feb 1998 18:58:26 -0800 (PST) (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 SAA00648; Sat, 14 Feb 1998 18:57:38 -0800 (PST) Message-Id: <199802150257.SAA00648@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: about my last panic In-reply-to: Your message of "Sat, 14 Feb 1998 16:59:05 PST." <199802150059.QAA13152@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 18:57:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What sort of "heavy" I/O are you talking about here? Are you swapping on this sucker? Is it actually getting a null transfer? > Forgot to include this: > > 419 void wfdstrategy (struct buf *bp) > 420 { > 421 int lun = UNIT(bp->b_dev); > 422 struct wfd *t = wfdtab[lun]; > 423 int x; > 424 > (kgdb) > 425 /* If it's a null transfer, return immediatly. */ > 426 if (bp->b_bcount == 0) { > 427 bp->b_resid = 0; > 428 biodone (bp); > 429 return; > 430 } > (kgdb) print *bp > $4 = {b_hash = {le_next = 0x0, le_prev = 0x0}, b_vnbufs = { > le_next = 0x87654321, le_prev = 0x0}, b_freelist = {tqe_next = 0x0, > tqe_prev = 0x0}, b_act = {tqe_next = 0x0, tqe_prev = 0x0}, > b_proc = 0xf022b7bc, b_flags = 67108944, b_qindex = 0, > b_usecount = 0 '\000', b_error = 0, b_bufsize = 4096, b_bcount = 4096, > b_resid = 0, b_dev = 256, b_data = 0xf39cf000 "", b_kvabase = 0x0, > b_kvasize = 0, b_lblkno = 0, b_blkno = 544, > b_iodone = 0xf01af970 , b_iodone_chain = 0x0, > b_vp = 0xf479c560, b_dirtyoff = 0, b_dirtyend = 4096, b_generation = 0, > b_rcred = 0xf068ac00, b_wcred = 0xf068ac00, b_validoff = 0, b_validend = 0, > b_pblkno = 0, b_saveaddr = 0x0, b_savekva = 0x0, b_driver1 = 0x0, > b_driver2 = 0x0, b_spc = 0xf02163dc, b_cluster = {cluster_head = { > tqh_first = 0x0, tqh_last = 0x0}, cluster_entry = {tqe_next = 0x0, > tqe_prev = 0x0}}, b_pages = {0x0 }, b_npages = 0} > > Tnks, > Amancio > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ 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 Feb 14 19:24:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11428 for freebsd-current-outgoing; Sat, 14 Feb 1998 19:24:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11422 for ; Sat, 14 Feb 1998 19:24:33 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id NAA24501; Sun, 15 Feb 1998 13:54:13 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id NAA28259; Sun, 15 Feb 1998 13:54:12 +1030 (CST) (envelope-from grog) Message-ID: <19980215135411.54721@freebie.lemis.com> Date: Sun, 15 Feb 1998 13:54:11 +1030 From: Greg Lehey To: Julian Elischer , current@FreeBSD.ORG Subject: Re: Working (apparently) soft-update code available. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Julian Elischer on Fri, Feb 13, 1998 at 03:07:52PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 13 February 1998 at 15:07:52 -0800, Julian Elischer wrote: > > look in: > ftp://ftp.freebsd.org/pub/FreeBSD/incoming/softupdates4.tgz > > first extract the README and read it before extracting everything. > this should patch cleanly against last night's -current. > > try a make world before and after.. > particularly, > make /var/tmp and/or /usr/obj use softupdates. I tried this with a "make world". The figures are only approximate, since I didn't time the same make world under identical conditions, but they give a rough idea. I have my sources mounted on drive /src, and the objects are written to an old Conner 4 GB drive, /S. With both of these drives mounted async, a make world took 177 minutes. With soft updates, it took 156. Note that I'm still installing on /usr, which is an IDE drive with neither async nor soft updates. Here's the mount output after the build. I started the build effectively immediately after booting, so you can assume that most of these values were 0 when the make world started. I was, however, doing some other things on the system. In addition, I had /var/tmp on /home, which wasn't mounted /dev/wd0a on / (NFS exported, local, writes: sync 837 async 2326) /dev/wd0s1e on /usr (NFS exported, local, writes: sync 23567 async 10110) /dev/sd1h on /home (NFS exported, local, writes: sync 137441 async 8059) /dev/sd2e on /S (NFS exported, local, soft-updates, writes: sync 1305 async 66484) /dev/sd0e on /src (NFS exported, local, soft-updates, writes: sync 6 async 19466) > for a real laugh, try timing deletion of a large directory hierarchy.. === root@freebie (/dev/ttyp0) /usr 43 -> time rm -fr /usr/obj 2>/dev/null real 0m0.179s user 0m0.001s sys 0m0.012s Is that what I should have seen? I'm going to do some more comparisons, including another 'make world' with /var/tmp on /S, and again with neither async nor soft updates. It'll take a while :-) Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 19:30:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12046 for freebsd-current-outgoing; Sat, 14 Feb 1998 19:30:12 -0800 (PST) (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 TAA12035 for ; Sat, 14 Feb 1998 19:30:06 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA04018; Sat, 14 Feb 1998 22:29:57 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802150329.WAA04018@dyson.iquest.net> Subject: Re: current is panicky with... In-Reply-To: <199802150057.QAA13127@rah.star-gate.com> from Amancio Hasty at "Feb 14, 98 04:57:09 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sat, 14 Feb 1998 22:29:56 -0500 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty said: > > During "heavy" i/o I am getting this panic , anyone has a clue as to > why. This started happening as of yesterday, prior to that I didn't > have any problems with compiling a kernel with -g. > Just a guess, try the following patch (vm/vm_pager.c): Index: vm_pager.c =================================================================== RCS file: /local/home/ncvs/src/sys/vm/vm_pager.c,v retrieving revision 1.34 diff -C2 -r1.34 vm_pager.c *** vm_pager.c 1998/02/06 12:14:29 1.34 --- vm_pager.c 1998/02/15 03:28:28 *************** *** 264,267 **** --- 264,268 ---- bp->b_kvasize = MAXPHYS; bp->b_vnbufs.le_next = NOLIST; + bp->b_dep = NULL; } John dyson@freebsd.org jdyson@nc.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 19:40:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13310 for freebsd-current-outgoing; Sat, 14 Feb 1998 19:40:38 -0800 (PST) (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 TAA13305 for ; Sat, 14 Feb 1998 19:40:35 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA00207; Sat, 14 Feb 1998 22:40:05 -0500 (EST) (envelope-from toor) Message-Id: <199802150340.WAA00207@dyson.iquest.net> Subject: Re: about my last panic In-Reply-To: <199802150257.SAA00648@dingo.cdrom.com> from Mike Smith at "Feb 14, 98 06:57:37 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 14 Feb 1998 22:40:05 -0500 (EST) Cc: hasty@rah.star-gate.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith said: > > What sort of "heavy" I/O are you talking about here? Are you swapping > on this sucker? Is it actually getting a null transfer? > My previous patch was in error, try this: Index: vm_pager.c =================================================================== RCS file: /local/home/ncvs/src/sys/vm/vm_pager.c,v retrieving revision 1.34 diff -C2 -r1.34 vm_pager.c *** vm_pager.c 1998/02/06 12:14:29 1.34 --- vm_pager.c 1998/02/15 03:32:58 *************** *** 264,267 **** --- 264,268 ---- bp->b_kvasize = MAXPHYS; bp->b_vnbufs.le_next = NOLIST; + LIST_FIRST(&bp->b_dep) = NULL; } -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you 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 Sat Feb 14 20:07:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16108 for freebsd-current-outgoing; Sat, 14 Feb 1998 20:07:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA16092 for ; Sat, 14 Feb 1998 20:07:38 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA13783; Sat, 14 Feb 1998 20:06:16 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802150406.UAA13783@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "John S. Dyson" cc: current@FreeBSD.ORG Subject: Re: current is panicky with... In-reply-to: Your message of "Sat, 14 Feb 1998 22:29:56 EST." <199802150329.WAA04018@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 20:06:15 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hm... I don't have a structure member b_dep... Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 20:12:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16678 for freebsd-current-outgoing; Sat, 14 Feb 1998 20:12:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA16662 for ; Sat, 14 Feb 1998 20:12:45 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA13818; Sat, 14 Feb 1998 20:12:25 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802150412.UAA13818@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: about my last panic In-reply-to: Your message of "Sat, 14 Feb 1998 18:57:37 PST." <199802150257.SAA00648@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 20:12:25 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Like writing the final stage of a kernel compiled -g ls -ald kernel.debub -rwxr-xr-x 1 root wheel 9116287 Feb 14 16:06 kernel.debug At any rate, the panic looks like is due to something in the vm system . Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 20:26:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19060 for freebsd-current-outgoing; Sat, 14 Feb 1998 20:26:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19037 for ; Sat, 14 Feb 1998 20:25:57 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.5) with ESMTP id WAA00407 for ; Sat, 14 Feb 1998 22:25:54 -0600 (CST) Message-Id: <199802150425.WAA00407@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-current@FreeBSD.ORG Subject: Soft Updates/CCD's don't work together--larger problems perhaps Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 22:25:53 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I have mentioned before, using Soft Updates and CCD's together cause a panic in softdep_disk_io_initiation(). The problems seem to be related to the ordering of the bioops.io_start() calls in kern/vfs_cluster.c--it is possible to call this function with B_READ, which will immediately causes the panic. A couple thoughts.. Would it be ok to move around the flag assignment as follows? Also, does there really need to be a call to bioops.io_start() from cluster_rbuild? I noticed that OpenBSD has rearranged things so that the flags are set before the call to bioops.io_start(), to avoid just this problem. Also, they do not call it from cluster_rbuild either.. Could someone who knows more about the VFS code have a look at how the Soft Updates code is integrated here? Thanks, Chris *** vfs_cluster.c.old Sat Feb 14 22:16:20 1998 --- vfs_cluster.c Sat Feb 14 21:36:45 1998 *************** *** 722,727 **** --- 722,729 ---- tbp->b_flags &= ~B_DONE; splx(s); } + tbp->b_flags &= ~(B_READ | B_DONE | B_ERROR | B_DELWRI); + tbp->b_flags |= B_ASYNC; /* check for latent dependencies to be handled */ if ((LIST_FIRST(&tbp->b_dep)) != NULL && bioops.io_start) *************** *** 752,759 **** bp->b_bufsize += size; --numdirtybuffers; - tbp->b_flags &= ~(B_READ | B_DONE | B_ERROR | B_DELWRI); - tbp->b_flags |= B_ASYNC; s = splbio(); reassignbuf(tbp, tbp->b_vp); /* put on clean list */ ++tbp->b_vp->v_numoutput; --- 754,759 ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 20:30:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19865 for freebsd-current-outgoing; Sat, 14 Feb 1998 20:30:50 -0800 (PST) (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 UAA19839 for ; Sat, 14 Feb 1998 20:30:47 -0800 (PST) (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 UAA00902; Sat, 14 Feb 1998 20:29:12 -0800 (PST) Message-Id: <199802150429.UAA00902@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Mike Smith , current@FreeBSD.ORG Subject: Re: about my last panic In-reply-to: Your message of "Sat, 14 Feb 1998 20:12:25 PST." <199802150412.UAA13818@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 20:29:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Like writing the final stage of a kernel compiled -g > ls -ald kernel.debub > -rwxr-xr-x 1 root wheel 9116287 Feb 14 16:06 kernel.debug > > At any rate, the panic looks like is due to something in the vm system . Just a little odd to me that it was coming out of the wfd driver. There are some drivers that don't check for 0-length transactions in their strategy routines, so it was a bit odd. -- \\ 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 Feb 14 20:31:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20095 for freebsd-current-outgoing; Sat, 14 Feb 1998 20:31:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20068 for ; Sat, 14 Feb 1998 20:31:19 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.5) with ESMTP id WAA00428 for ; Sat, 14 Feb 1998 22:31:08 -0600 (CST) Message-Id: <199802150431.WAA00428@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-current@FreeBSD.ORG Subject: CCD missing spl() call.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 22:31:08 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is also a off by one error in the handling of the partitions. Credit goes to OpenBSD for these. There are numerous other changes that would be worth integrating as well.. Chris *** ccd.c.old Sat Feb 14 22:27:17 1998 --- ccd.c Sat Feb 14 20:27:12 1998 *************** *** 631,637 **** ccdgetdisklabel(dev); /* Check that the partition exists. */ ! if (part != RAW_PART && ((part > lp->d_npartitions) || (lp->d_partitions[part].p_fstype == FS_UNUSED))) { error = ENXIO; goto done; --- 631,637 ---- ccdgetdisklabel(dev); /* Check that the partition exists. */ ! if (part != RAW_PART && ((part >= lp->d_npartitions) || (lp->d_partitions[part].p_fstype == FS_UNUSED))) { error = ENXIO; goto done; *************** *** 973,978 **** --- 973,979 ---- register int unit = cbp->cb_unit; int count, s; + s = splbio(); #ifdef DEBUG if (ccddebug & CCDB_FOLLOW) printf("ccdiodone(%x)\n", cbp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 20:41:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22316 for freebsd-current-outgoing; Sat, 14 Feb 1998 20:41:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22281 for ; Sat, 14 Feb 1998 20:41:41 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA14147; Sat, 14 Feb 1998 20:41:17 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802150441.UAA14147@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: about my last panic In-reply-to: Your message of "Sat, 14 Feb 1998 20:29:11 PST." <199802150429.UAA00902@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 20:41:17 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I took out that device out of my system configureation since I don't have a wfd drive so lets see if the system panics or not. Cheers, Amancio > > > > Like writing the final stage of a kernel compiled -g > > ls -ald kernel.debub > > -rwxr-xr-x 1 root wheel 9116287 Feb 14 16:06 kernel.debug > > > > At any rate, the panic looks like is due to something in the vm system . > > Just a little odd to me that it was coming out of the wfd driver. > There are some drivers that don't check for 0-length transactions in > their strategy routines, so it was a bit odd. > -- > \\ 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 Feb 14 21:04:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26574 for freebsd-current-outgoing; Sat, 14 Feb 1998 21:04:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26542; Sat, 14 Feb 1998 21:04:22 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id NAA00730; Sun, 15 Feb 1998 13:04:14 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199802150504.NAA00730@spinner.netplex.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Gary Palmer" cc: Donn Miller , current@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: netscape/swap_pager causing problems with syscons In-reply-to: Your message of "Mon, 02 Feb 1998 20:28:06 EST." <16424.886469286@gjp.erols.com> Date: Sun, 15 Feb 1998 13:04:14 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Gary Palmer" wrote: > Donn Miller wrote in message ID > : > > Jordan hinted to this as a problem with syscons in one posting I saw. I > > would have to agree. In general, running out of swap space with netscape > > and X running wrecks havoc on syscons. I was wondering if anyone has > > experience with this problem and a possible solution as to how to get > > syscons responding again. I can't login by way of serial console so I > > guess the only choice is to just ctrl+alt+delete > > The problem is that the X server reprograms the chipset on the video > card to do what *it* wants. Syscons has no idea of the original > settings, and therefore can't restore them if X exits abnormally > (i.e. running out of swap and the kernel killing the server) > > The only possible solution is telling the console code how to reprogram > the video chipset, and making X indirect through the console code > for paramater changes. Perhaps it's not quite necessary to go that far, but it would be nice if syscons could be programmed (by the X server) with a sequence of instructions for resetting the video card back to sane settings. Then, when the xserver was killed, ot the machine paniced or whatever, then syscons could step through a list of instructions to reset the video card back to sanity. Presumably it'd have to be a mini instruction list.. ie: outb this value to this port, write to such-and-such a memory location, pause for a given amount, and so on.. kinda like BPF's programming. But then again, there's always the 'load the DDX component as a kernel module' option as Terry has pointed out. > Gary Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 21:14:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27385 for freebsd-current-outgoing; Sat, 14 Feb 1998 21:14:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27370 for ; Sat, 14 Feb 1998 21:14:18 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id PAA24600; Sun, 15 Feb 1998 15:43:52 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id PAA18516; Sun, 15 Feb 1998 15:43:52 +1030 (CST) (envelope-from grog) Message-ID: <19980215154350.44866@freebie.lemis.com> Date: Sun, 15 Feb 1998 15:43:50 +1030 From: Greg Lehey To: Chris Csanady , freebsd-current@FreeBSD.ORG Subject: Re: CCD missing spl() call.. References: <199802150431.WAA00428@friley585.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802150431.WAA00428@friley585.res.iastate.edu>; from Chris Csanady on Sat, Feb 14, 1998 at 10:31:08PM -0600 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 February 1998 at 22:31:08 -0600, Chris Csanady wrote: > > There is also a off by one error in the handling of the > partitions. Credit goes to OpenBSD for these. There are > numerous other changes that would be worth integrating > as well.. OK. The first one (off by 1) makes sense, but the second one (splbio) was there from the start. What sources are you comparing with? Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 21:15:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27483 for freebsd-current-outgoing; Sat, 14 Feb 1998 21:15:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27476 for ; Sat, 14 Feb 1998 21:15:06 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id VAA14338; Sat, 14 Feb 1998 21:14:45 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802150514.VAA14338@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: about my last panic In-reply-to: Your message of "Sat, 14 Feb 1998 20:29:11 PST." <199802150429.UAA00902@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 21:14:45 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cool, I just took out wfd out of my kernel configuration , rebuilt kernel, rebooted now all is well 8) Got no clue what was triggering the call to wfd strategy. Tnks, Amancio > > > > Like writing the final stage of a kernel compiled -g > > ls -ald kernel.debub > > -rwxr-xr-x 1 root wheel 9116287 Feb 14 16:06 kernel.debug > > > > At any rate, the panic looks like is due to something in the vm system . > > Just a little odd to me that it was coming out of the wfd driver. > There are some drivers that don't check for 0-length transactions in > their strategy routines, so it was a bit odd. > -- > \\ 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 Feb 14 21:44:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01586 for freebsd-current-outgoing; Sat, 14 Feb 1998 21:44:11 -0800 (PST) (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 VAA01579 for ; Sat, 14 Feb 1998 21:44:09 -0800 (PST) (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 VAA01088; Sat, 14 Feb 1998 21:42:33 -0800 (PST) Message-Id: <199802150542.VAA01088@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Mike Smith , current@FreeBSD.ORG Subject: Re: about my last panic In-reply-to: Your message of "Sat, 14 Feb 1998 20:41:17 PST." <199802150441.UAA14147@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 21:42:33 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I took out that device out of my system configureation since I don't have > a wfd drive so lets see if the system panics or not. ???!!! How could you be in wfdstrategy() if you don't have a wfd drive? -- \\ 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 Feb 14 22:59:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09867 for freebsd-current-outgoing; Sat, 14 Feb 1998 22:59:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09840 for ; Sat, 14 Feb 1998 22:59:40 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.5) with ESMTP id AAA00370; Sun, 15 Feb 1998 00:59:28 -0600 (CST) Message-Id: <199802150659.AAA00370@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: Greg Lehey cc: freebsd-current@FreeBSD.ORG Subject: Re: CCD missing spl() call.. In-reply-to: Your message of "Sun, 15 Feb 1998 15:43:50 +1030." <19980215154350.44866@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Feb 1998 00:59:28 -0600 From: Chris Csanady Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >OK. The first one (off by 1) makes sense, but the second one (splbio) >was there from the start. What sources are you comparing with? My mistake, not sure where that came from. :\ Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 23:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10565 for freebsd-current-outgoing; Sat, 14 Feb 1998 23:03:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10545 for ; Sat, 14 Feb 1998 23:03:47 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id SAA00658; Sun, 15 Feb 1998 18:03:02 +1100 (EST) Message-ID: <19980215180301.36777@rf900.physics.usyd.edu.au> Date: Sun, 15 Feb 1998 18:03:01 +1100 From: David Dawes To: current@FreeBSD.ORG Subject: Re: netscape/swap_pager causing problems with syscons References: <16424.886469286@gjp.erols.com> <199802150504.NAA00730@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199802150504.NAA00730@spinner.netplex.com.au>; from Peter Wemm on Sun, Feb 15, 1998 at 01:04:14PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Feb 15, 1998 at 01:04:14PM +0800, Peter Wemm wrote: >"Gary Palmer" wrote: >> Donn Miller wrote in message ID >> : >> > Jordan hinted to this as a problem with syscons in one posting I saw. I >> > would have to agree. In general, running out of swap space with netscape >> > and X running wrecks havoc on syscons. I was wondering if anyone has >> > experience with this problem and a possible solution as to how to get >> > syscons responding again. I can't login by way of serial console so I >> > guess the only choice is to just ctrl+alt+delete >> >> The problem is that the X server reprograms the chipset on the video >> card to do what *it* wants. Syscons has no idea of the original >> settings, and therefore can't restore them if X exits abnormally >> (i.e. running out of swap and the kernel killing the server) >> >> The only possible solution is telling the console code how to reprogram >> the video chipset, and making X indirect through the console code >> for paramater changes. > >Perhaps it's not quite necessary to go that far, but it would be nice if >syscons could be programmed (by the X server) with a sequence of >instructions for resetting the video card back to sane settings. Then, >when the xserver was killed, ot the machine paniced or whatever, then >syscons could step through a list of instructions to reset the video card >back to sanity. Presumably it'd have to be a mini instruction list.. ie: >outb this value to this port, write to such-and-such a memory location, >pause for a given amount, and so on.. kinda like BPF's programming. That sounds a bit like VESA's SVPMI standard (or a subset thereof). The standard is dated 1991, and it seems to me that it never caught on. [SVPMI = Super VGA Protected Mode Interface. An example of an implementation of this can be found in the xc/programs/Xserver/hw/svga directory of X11R6.0 (it was dropped in R6.1), and in any XFree86 3.x source. It was contributed to the then X Consortium by a predecessor of Xi Graphics.] David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 14 23:11:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12480 for freebsd-current-outgoing; Sat, 14 Feb 1998 23:11:34 -0800 (PST) (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 XAA12455 for ; Sat, 14 Feb 1998 23:11:31 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id AAA01719; Sun, 15 Feb 1998 00:11:28 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd001649; Sun Feb 15 00:11:19 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id AAA02976; Sun, 15 Feb 1998 00:11:15 -0700 (MST) From: Terry Lambert Message-Id: <199802150711.AAA02976@usr02.primenet.com> Subject: Re: about my last panic To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 15 Feb 1998 07:11:15 +0000 (GMT) Cc: mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: <199802150514.VAA14338@rah.star-gate.com> from "Amancio Hasty" at Feb 14, 98 09:14:45 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just took out wfd out of my kernel configuration , rebuilt kernel, rebooted > now all is well 8) > > Got no clue what was triggering the call to wfd strategy. Ata a guess, what does your "dump on" in your config look like? It's probably just trying to dump the kernel image after the panic. 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 Feb 14 23:22:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14110 for freebsd-current-outgoing; Sat, 14 Feb 1998 23:22:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14105 for ; Sat, 14 Feb 1998 23:22:04 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id XAA14962; Sat, 14 Feb 1998 23:21:46 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802150721.XAA14962@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: about my last panic In-reply-to: Your message of "Sun, 15 Feb 1998 07:11:15 GMT." <199802150711.AAA02976@usr02.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Feb 1998 23:21:45 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is my little bit on my config: config kernel root on wd0 in /etc/rc.conf dumpdev="/dev/wd0s1b" # Device name to crashdump to (if enabled). Cheers Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message