From owner-freebsd-current Sun Dec 13 00:03:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28739 for freebsd-current-outgoing; Sun, 13 Dec 1998 00:03:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.eecis.udel.edu (louie.udel.edu [128.175.2.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA28734 for ; Sun, 13 Dec 1998 00:03:01 -0800 (PST) (envelope-from alexandr@mail.eecis.udel.edu) Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa18157; 13 Dec 1998 03:02 EST To: current@FreeBSD.ORG Subject: Memory Problems Organization: Mos Eisley Candy Store Reply-To: alexandr@mail.eecis.udel.edu Date: Sun, 13 Dec 1998 03:02:29 -0500 From: Jerry Alexandratos Message-ID: <199812130302.aa18157@mail.eecis.udel.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running -current on a ThinkPad 600E. If I put more then 64M of memory in this machine it randomly hangs on me. I've tried ever memory combo that I can for anything above 64M (80, 96 116 and 128), and they all produce the same results. Has anyone ever seen a problem like this? If so, does anyone know of a solution? Thanks in advance. --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 00:30:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01726 for freebsd-current-outgoing; Sun, 13 Dec 1998 00:30:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01721 for ; Sun, 13 Dec 1998 00:30:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id AAA34780; Sun, 13 Dec 1998 00:29:35 -0800 (PST) To: NAKAGAWA Yoshihisa cc: Mike Smith , Kenjiro Cho , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sun, 13 Dec 1998 02:57:27 +0900." <199812121757.CAA08603@chandra.eatell.msr.prug.or.jp> Date: Sun, 13 Dec 1998 00:29:34 -0800 Message-ID: <34776.913537774@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I want to change this situation, so I am using many power for > communication. It is very hard for me. :-( And we appreciate that, believe me. I think Mike may have been a little too harsh in his original message and I think that everyone in core, at least, does appreciate the language problem and the fact that you guys are often "out of the loop" on a lot of things going on around here. It would help greatly, of course, if Tatsumi-san would come back and take up the commit privs we gave him for the purpose of creating closer cooperation. Has anyone even seen Mr. Hosokawa lately? Is he still alive? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 01:28:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05090 for freebsd-current-outgoing; Sun, 13 Dec 1998 01:28:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp (ykh28DS39.kng.mesh.ad.jp [133.205.214.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05085 for ; Sun, 13 Dec 1998 01:28:24 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id MAA09045; Sun, 13 Dec 1998 12:15:51 +0900 (JST) Message-Id: <199812130315.MAA09045@chandra.eatell.msr.prug.or.jp> To: Garrett Wollman cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sat, 12 Dec 1998 14:26:11 EST." <199812121926.OAA05241@khavrinen.lcs.mit.edu> Date: Sun, 13 Dec 1998 12:15:51 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > CardBus support, we are planning on newconfig Project in near > > future. Bus independ code is necessary. So, we use NetBSD(4.4BSD) > > style bus and device configuration code. > > Please don't waste your time. This code will never be in FreeBSD. Garrett, What do you want to say? Do you want to battle? -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 01:28:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05116 for freebsd-current-outgoing; Sun, 13 Dec 1998 01:28:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp (ykh28DS39.kng.mesh.ad.jp [133.205.214.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05107 for ; Sun, 13 Dec 1998 01:28:54 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id MAA09027; Sun, 13 Dec 1998 12:03:32 +0900 (JST) Message-Id: <199812130303.MAA09027@chandra.eatell.msr.prug.or.jp> To: Garrett Wollman cc: Nate Williams , Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sat, 12 Dec 1998 14:25:30 EST." <199812121925.OAA05227@khavrinen.lcs.mit.edu> Date: Sun, 13 Dec 1998 12:03:31 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not at all. Please join new-bus-arch. OK, I will join new-bus ML. But I disagree "now -current style bus code". -current bus code is very different other BSDs, it is large demerit. And, I NEED "new" config for staticaly configuration. In now, -current bus code lack of many feature, NetBSD-current bus code has it. So, we use NetBSD style bus and device configuration code. We already re-write PCI and part of ISA code, it works fine. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 02:24:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09693 for freebsd-current-outgoing; Sun, 13 Dec 1998 02:24:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09687 for ; Sun, 13 Dec 1998 02:24:14 -0800 (PST) (envelope-from furuta@sra.co.jp) Received: from sramhc.sra.co.jp (sramhc [133.137.20.31]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id TAA08935; Sun, 13 Dec 1998 19:22:55 +0859 (JST) Received: from sramhc.sra.co.jp (furuta@localhost [127.0.0.1]) by sramhc.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id TAA05525; Sun, 13 Dec 1998 19:23:09 +0900 (JST) Message-Id: <199812131023.TAA05525@sramhc.sra.co.jp> To: dfr@nlsystems.com Cc: mike@smith.net.au, y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: Your message of "Fri, 11 Dec 1998 23:12:45 +0000 (GMT)" References: X-Mailer: Mew version 1.70 on Emacs 19.28.7 / Mule 2.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 13 Dec 1998 19:23:08 +0900 From: Atsushi Furuta Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In article , Doug Rabson writes: > The softc issue is addressed by the new device framework. The pci support > code has not yet been updated to the new interface but when it is, it will > get this for free. The flags field can also be easily added. I wonder how a user specifies flags to pci bus. I seems that there is no generic way to specify flags in current subr_bus.c, and it is up to each bus codes how to provide ivers and flags. -- furuta@sra.co.jp (Atsushi Furuta) Advanced Technology Group. Software Research Associates, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 02:51:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11843 for freebsd-current-outgoing; Sun, 13 Dec 1998 02:51:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11835; Sun, 13 Dec 1998 02:51:31 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id KAA17784; Sun, 13 Dec 1998 10:47:27 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id KAA17485; Sun, 13 Dec 1998 10:48:39 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812131048.KAA17485@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: Brian Somers , "Enoch Ceshkovsky" , "Gary Palmer" , current@FreeBSD.ORG, Eivind Eklund Subject: Re: NATD/Libalias leaks In-reply-to: Your message of "Sat, 12 Dec 1998 18:06:42 PST." <199812130206.SAA14397@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 10:48:38 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can't set up a scenario with bad NetBIOS packets, but I've got a hub here and should be able to route from one machine to another via something running natd. I should also be able to set up a dialup scenario using ppp/libalias. I think this sort of thing can only really be proven to still work - it's impractical to try to fake bad network traffic (well, as you say, it's at least too stressful!). > :It looks like Matt's going to have a crack at alias_nbt according to > :his followup to bin/8962. > > Well, I tried... but after staring at my old windows box (which I haven't > turned on in a month) for a few minutes, I decided that actually > trying to test the damn thing would be too stressful on my delicate > constitution :-) > > We're going to need someone with a cable modem (like the original bug > poster) who regularly gets malformed netbios packets to test it. I'm > considering just comitting it (I don't think it will get adequate testing, > else). > > :Brian > > Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet > Communications & God knows what else. > (Please include original email in any response) -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 03:16:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15601 for freebsd-current-outgoing; Sun, 13 Dec 1998 03:16:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15560 for ; Sun, 13 Dec 1998 03:15:52 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id MAA00577; Sun, 13 Dec 1998 12:03:20 +0100 (CET) Message-Id: <199812131103.MAA00577@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com cc: Greg Lehey , FreeBSD current users Subject: Re: Can't access tapes with scsi_sa.c r1.7 Reply-To: Gary Jennejohn In-reply-to: Your message of "Sat, 12 Dec 1998 18:18:26 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 12:03:19 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > >Yes, that'd be my change. Whups! It worked for me! Could you build a >CAMDEBUG kernel, use camcontrol to turn on debugging for that device and >do whatever it is you did and send me the output, or send me what it is >you tried first? I'll be in my shop tomorrow morning to work on this! >Sorry! > just another data point. My SDT-9000 also doesn't work anymore with the latest scsi_sa.c. Although the kernel finds it I always get I/O errors when I try to access it. Highly inconvenient because I lost 2 file systems in a crash last night and wanted to restore them today. I'll do what you requested. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 04:08:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23944 for freebsd-current-outgoing; Sun, 13 Dec 1998 04:08:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23934 for ; Sun, 13 Dec 1998 04:08:09 -0800 (PST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id NAA12050; Sun, 13 Dec 1998 13:07:54 +0100 (MET) Received: from cicely.cicely.de (cicely.cicely.de [10.1.3.3]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id NAA11253; Sun, 13 Dec 1998 13:07:56 +0100 (CET) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.5.7]) by cicely.cicely.de (8.8.8/8.8.8) with ESMTP id NAA04934; Sun, 13 Dec 1998 13:07:54 +0100 (CET) Received: (from ticso@localhost) by cicely5.cicely.de (8.9.0/8.9.0) id NAA02388; Sun, 13 Dec 1998 13:07:47 +0100 (CET) Message-ID: <19981213130746.07809@cicely.de> Date: Sun, 13 Dec 1998 13:07:46 +0100 From: Bernd Walter To: Greg Pavelcak , freebsd-current@FreeBSD.ORG Subject: Re: Build Fails with Signal 4 References: <19981211105035.A230@oit.umass.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19981211105035.A230@oit.umass.edu>; from Greg Pavelcak on Fri, Dec 11, 1998 at 10:50:35AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 11, 1998 at 10:50:35AM -0500, Greg Pavelcak wrote: > With sources supped last night, > > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/com5.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/com6.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/com7.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/init.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/cypher.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/getcom.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/parse.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/room.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/save.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/fly.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/misc.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/globals.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/dayfile.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/nightfile.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/dayobjs.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/nightobjs.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/words.c > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -o battlestar battlestar.o com1.o com2.o com3.o com4.o com5.o com6.o com7.o init.o cypher.o getcom.o parse.o room.o save.o fly.o misc.o globals.o dayfile.o nightfile.o dayobjs.o nightobjs.o words.o -lcurses -ltermcap -lcompat > gzip -cn /usr/src/games/battlestar/battlestar.6 > battlestar.6.gz > ===> games/bcd > cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/bcd/bcd.c > cc: Internal compiler error: program cc1 got fatal signal 4 > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > However, this may not be a -current problem, since I got these on > my last several build attempts in different places. I'm hoping > someone can shed some light though. > I had similar problems with the SNAP from 3.11. I first compiled a new kernel with a recent src-tree and rebootet. With the new kernel I was able to buildworld without any problems. But I'm not shure if it was the kernel, because I exchanged all RAM before compiling. RAM was 128M ECC before and 256M ECC after. No Memory errors were reported. The system was running a 2.2.2-RELEASE over 1 year without problems. I asume it was the kernel. > Thanks. > > Greg > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 05:20:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28690 for freebsd-current-outgoing; Sun, 13 Dec 1998 05:20:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28683; Sun, 13 Dec 1998 05:20:54 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id OAA12375; Sun, 13 Dec 1998 14:20:51 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA29891; Sun, 13 Dec 1998 14:20:45 +0100 (MET) Message-ID: <19981213142045.H5444@follo.net> Date: Sun, 13 Dec 1998 14:20:45 +0100 From: Eivind Eklund To: Brian Somers , Enoch Ceshkovsky Cc: Gary Palmer , current@FreeBSD.ORG Subject: Re: NATD/Libalias leaks References: <000e01be2605$9f11fa00$0201a8c0@shadey.oow.com> <199812130008.AAA16396@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812130008.AAA16396@keep.lan.Awfulhak.org>; from Brian Somers on Sun, Dec 13, 1998 at 12:08:39AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 13, 1998 at 12:08:39AM +0000, Brian Somers wrote: > > Version 2.5: December, 1997 (ee) > > - Added PKT_ALIAS_PUNCH_FW mode for firewall > > bypass of FTP/IRC DCC data connections. Also added > > improved TCP connection monitoring. > > > > Version 2.6: May, 1998 (amurai) > > - Added supporting routine for NetBios over TCP/IP. > > I added alias_cuseeme.c > > It looks like Matt's going to have a crack at alias_nbt according to > his followup to bin/8962. > > Can you try building the -current version of libalias with > -DNO_FW_PUNCH and see if that makes a difference ? If it does, we > can point the finger at Eivind (cc'd, hi;) I'd be surprised - I'm running those changes in active production at _many_ boxes (I can't say any exact numbers, so lets leave it at being significantly more than 100). Also, the firewall changes do _nothing_ unless PKT_ALIAS_PUNCH_FW is set. There might be an issue with the improvements to the connection monitoring. I'm pretty certain it is NOT buggy, but it may cause something that looks like a leak if the boxes being aliased are doing TCP incorrectly. This will reach a steady state, however, as there is a timeout of 24 hours. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 07:30:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08778 for freebsd-current-outgoing; Sun, 13 Dec 1998 07:30:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from easeway.com (ns1.easeway.com [209.69.71.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08767 for ; Sun, 13 Dec 1998 07:30:11 -0800 (PST) (envelope-from mwlucas@easeway.com) Received: (from mwlucas@localhost) by easeway.com (8.8.8/8.8.5) id KAA29974 for freebsd-current@freebsd.org; Sun, 13 Dec 1998 10:12:15 -0500 (EST) Message-Id: <199812131512.KAA29974@easeway.com> Subject: good new 3x laptop? To: freebsd-current@FreeBSD.ORG Date: Sun, 13 Dec 1998 10:12:15 -0500 (EST) From: mwlucas@exceptionet.com 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 Folks, I'm about to purchase a laptop to run FreeBSD on. With all this discussion about PAO and -current differences, I figured I'd better ask first. ;) Can anyone recommend a decent new laptop for FreeBSD? I want to run 3.x. I'm looking in the sub-$2000 range. Thanks, Michael -- Michael Lucas | Exceptionet, Inc. | www.exceptionet.com "Exceptional Networking" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 07:49:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10209 for freebsd-current-outgoing; Sun, 13 Dec 1998 07:49:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10201 for ; Sun, 13 Dec 1998 07:49:46 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t1o29p112.telia.com [194.236.214.112]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id QAA00465; Sun, 13 Dec 1998 16:49:37 +0100 Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.1/8.9.1) with ESMTP id QAA02281; Sun, 13 Dec 1998 16:47:39 +0100 (CET) (envelope-from johan@granlund.nu) Date: Sun, 13 Dec 1998 16:47:39 +0100 (CET) From: Johan Granlund To: Matthew Jacob cc: Greg Lehey , FreeBSD current users Subject: Re: Can't access tapes with scsi_sa.c r1.7 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 Dec 1998, Matthew Jacob wrote: > > Yes, that'd be my change. Whups! It worked for me! Could you build a And it also works for me. Exabyte EXB-8200 and Adaptec 2940UW. Both dump and restore of selected files. This is with variable blocksize. Matthew: Did you test making a fulltape dump (until EOT) that caused a kernel panic (kernel from Nov 7) for me? I can't test this easily now beqause my large datadisk finally failed. I should get a replacement sometime next week. Then we will see if a full multitape restore works:) /Johan > CAMDEBUG kernel, use camcontrol to turn on debugging for that device and > do whatever it is you did and send me the output, or send me what it is > you tried first? I'll be in my shop tomorrow morning to work on this! > Sorry! > > > > > > > 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 Sun Dec 13 08:02:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11355 for freebsd-current-outgoing; Sun, 13 Dec 1998 08:02:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11348 for ; Sun, 13 Dec 1998 08:02:17 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from heidi.plazza.it (mobile18.jrc.it [139.191.250.18]) by mrelay.jrc.it (LMC5692) with SMTP id RAA00560; Sun, 13 Dec 1998 17:02:45 +0100 (MET) Date: Sun, 13 Dec 1998 17:03:43 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Matthew Dillon cc: freebsd-current@FreeBSD.ORG Subject: Re: bin/5572 (critial, high priority cron bug never fixed) In-Reply-To: <199812130611.WAA00663@apollo.backplane.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 Here is a man who enjoys his privileges. And right he is. Cheers, you're doing a great job. Everybody who wants to fix a PR has to be quick, otherwise Matt will have done it already. Nick On Sat, 12 Dec 1998, Matthew Dillon wrote: > ... that I submitted all the way back on Jan 26th. It even included > a patch. > > And nobody read it. Nobody fixed it. It's still sitting there > in the critical list, untouched. > > Well, now that I have commit privs I'm damn well going to fix this > one! > > -Matt > > Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet > Communications & God knows what else. > (Please include original email in any response) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > -- e-Mail: n_hibma@etla.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 08:14:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12519 for freebsd-current-outgoing; Sun, 13 Dec 1998 08:14:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12265; Sun, 13 Dec 1998 08:14:14 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from heidi.plazza.it (mobile18.jrc.it [139.191.250.18]) by mrelay.jrc.it (LMC5692) with SMTP id RAA00644; Sun, 13 Dec 1998 17:14:45 +0100 (MET) Date: Sun, 13 Dec 1998 17:15:43 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Matt Dillon cc: current@FreeBSD.ORG, CVS Committers FreeBSD Subject: Re: cvs commit: src/etc/mtree BSD.include.dist In-Reply-To: <199812130431.UAA10549@freefall.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 The changes to include the usbd and usbdevs programs will be submitted tomorrow when I get a chance to do a make world and check whether everything is working properly. Sorry about the confusion. Nick On Sat, 12 Dec 1998, Matt Dillon wrote: > dillon 1998/12/12 20:31:15 PST > > Modified files: > etc/mtree BSD.include.dist > Log: > This needs to be commited now to fix usbd for make world > > Revision Changes Path > 1.23 +3 -1 src/etc/mtree/BSD.include.dist > -- e-Mail: n_hibma@etla.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 08:18:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12926 for freebsd-current-outgoing; Sun, 13 Dec 1998 08:18:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12919 for ; Sun, 13 Dec 1998 08:18:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id IAA35754; Sun, 13 Dec 1998 08:18:04 -0800 (PST) To: NAKAGAWA Yoshihisa cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sun, 13 Dec 1998 12:15:51 +0900." <199812130315.MAA09045@chandra.eatell.msr.prug.or.jp> Date: Sun, 13 Dec 1998 08:18:03 -0800 Message-ID: <35750.913565883@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Please don't waste your time. This code will never be in FreeBSD. > > Garrett, What do you want to say? Do you want to battle? Ummm. I do not think that this conversation is going in productive directions, and there are certainly many users who would much rather see anything at all related to cardbus be productive. No one person in core is really empowered to say that something will "never" be in FreeBSD unless that something defies all common sense, like moving the X server into the kernel. :) Like most things in FreeBSD, I suspect that "success" in this area will come to whichever approach manages to provide reasonable functionality and win user acclamation. Sometimes that's a function of raw technical merit and sometimes it's the fact that it Just Works where none of the more technically meritorious solutions are doing the job. I'm interested to see what both groups produce and even more interested to see how the users judge their work. That, far more than any core team member's possibly hasty pronouncement, is going to determine the final outcome here. Better that everyone involved spend more time worrying about their code than on "battling" in email. :) - Jordan outcome of all this. So > > -- > NAKAGAWA, Yoshihisa > y-nakaga@nwsl.mesh.ad.jp > nakagawa@jp.FreeBSD.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 09:25:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18412 for freebsd-current-outgoing; Sun, 13 Dec 1998 09:25:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18407 for ; Sun, 13 Dec 1998 09:25:30 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id MAA19040 for ; Sun, 13 Dec 1998 12:25:27 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA01645; Sun, 13 Dec 1998 12:25:27 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id MAA12313 for freebsd-current@freebsd.org; Sun, 13 Dec 1998 12:25:27 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812131725.MAA12313@bb01f39.unx.sas.com> Subject: make release busted creating README.html for net/gtkicq To: freebsd-current@FreeBSD.ORG Date: Sun, 13 Dec 1998 12:25:26 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The subject says it all... ===> net/gopher ===> Creating README.html for gopher-2.3 ===> net/gicq ===> Creating README.html for gicq-0.22 ===> net/gtkicq "Makefile", line 13: Unassociated shell command "ftp://ftp.rnd.runnet.ru/pub/uni x/GUI_Toolkits/gtk/" make: fatal errors encountered -- cannot continue *** Error code 1 Stop. In "/usr/ports/net/gtkicq/Makefile": Would someone please delete the tab character at the end of line 12 of the Makefile? It's breaks the continuation. Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 10:06:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22184 for freebsd-current-outgoing; Sun, 13 Dec 1998 10:06:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22179 for ; Sun, 13 Dec 1998 10:06:47 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id KAA11150; Sun, 13 Dec 1998 10:06:21 -0800 Date: Sun, 13 Dec 1998 10:06:21 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Johan Granlund cc: Greg Lehey , FreeBSD current users Subject: Re: Can't access tapes with scsi_sa.c r1.7 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did writes to EOT, but not with dump. > On Sat, 12 Dec 1998, Matthew Jacob wrote: > > > > > Yes, that'd be my change. Whups! It worked for me! Could you build a > > And it also works for me. Exabyte EXB-8200 and Adaptec 2940UW. Both dump > and restore of selected files. This is with variable blocksize. > > Matthew: Did you test making a fulltape dump (until EOT) that caused a > kernel panic (kernel from Nov 7) for me? I can't test this easily now > beqause my large datadisk finally failed. I should get a replacement > sometime next week. Then we will see if a full multitape restore works:) > > /Johan > > > CAMDEBUG kernel, use camcontrol to turn on debugging for that device and > > do whatever it is you did and send me the output, or send me what it is > > you tried first? I'll be in my shop tomorrow morning to work on this! > > Sorry! > > > > > > > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 10:34:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24859 for freebsd-current-outgoing; Sun, 13 Dec 1998 10:34:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d2.dialup.hilink.com.au [203.2.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24854 for ; Sun, 13 Dec 1998 10:34:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA00419; Sun, 13 Dec 1998 10:32:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812131832.KAA00419@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mwlucas@exceptionet.com cc: freebsd-current@FreeBSD.ORG Subject: Re: good new 3x laptop? In-reply-to: Your message of "Sun, 13 Dec 1998 10:12:15 EST." <199812131512.KAA29974@easeway.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 10:32:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Folks, > > I'm about to purchase a laptop to run FreeBSD on. With all this > discussion about PAO and -current differences, I figured I'd better ask > first. ;) > > Can anyone recommend a decent new laptop for FreeBSD? I want to run 3.x. > I'm looking in the sub-$2000 range. Any of the Toshiba Satellite units in that range will give you good service. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 11:09:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27704 for freebsd-current-outgoing; Sun, 13 Dec 1998 11:09:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from poynting.physics.purdue.edu (poynting.physics.purdue.edu [128.210.146.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27694 for ; Sun, 13 Dec 1998 11:09:35 -0800 (PST) (envelope-from ajk@poynting.physics.purdue.edu) Received: from poynting.physics.purdue.edu (localhost [127.0.0.1]) by poynting.physics.purdue.edu (8.9.1/8.9.1) with ESMTP id OAA11246 for ; Sun, 13 Dec 1998 14:09:36 -0500 (EST) (envelope-from ajk@poynting.physics.purdue.edu) Message-Id: <199812131909.OAA11246@poynting.physics.purdue.edu> To: freebsd-current@FreeBSD.ORG Subject: biff b From: "Andrew J. Korty" MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0" Content-ID: <11234.913576157.0@poynting.physics.purdue.edu> Date: Sun, 13 Dec 1998 14:09:35 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11234.913576157.1@poynting.physics.purdue.edu> The stock versions of biff(1) and comsat(8) cause the header and first few lines of an arriving mail message to be displayed. My (trivial) modifications to these programs add the "biff b" feature found in some other UNIX variants. In this mode, only a couple of BEL characters are sent to the user's terminal, signifying new mail without disturbing the display. I can't commit this feature because I don't have the privs, but my diffs are attached ... Andrew J. Korty, Director http://www.physics.purdue.edu/~ajk/ Physics Computer Network 85 73 1F 04 63 D9 9D 65 Purdue University 65 2E 7A A8 81 8C 45 75 ------- =_aaaaaaaaaa0 Content-Type: application/x-patch Content-ID: <11234.913576157.2@poynting.physics.purdue.edu> Content-Description: biff b Content-Transfer-Encoding: base64 SW5kZXg6IHNyYy91c3IuYmluL2JpZmYvYmlmZi4xCj09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC91c3Iv Y3ZzL2ZyZWVic2Qvc3JjL3Vzci5iaW4vYmlmZi9iaWZmLjEsdgpyZXRyaWV2aW5nIHJldmlzaW9u IDEuMS4xLjEKcmV0cmlldmluZyByZXZpc2lvbiAxLjIKZGlmZiAtYyAtcjEuMS4xLjEgLXIxLjIK KioqIGJpZmYuMQkxOTk4LzEyLzAzIDE1OjQxOjQwCTEuMS4xLjEKLS0tIGJpZmYuMQkxOTk4LzEy LzA3IDE0OjUyOjM5CTEuMgoqKioqKioqKioqKioqKioKKioqIDQwLDQ2ICoqKioKICAuTmQgImJl IG5vdGlmaWVkIGlmIG1haWwgYXJyaXZlcyBhbmQgd2hvIGl0IGlzIGZyb20iCiAgLlNoIFNZTk9Q U0lTCiAgLk5tIGJpZmYKISAuT3AgQ20gbiB8IHkKICAuU2ggREVTQ1JJUFRJT04KICAuTm0gQmlm ZgogIGluZm9ybXMgdGhlIHN5c3RlbSB3aGV0aGVyIHlvdSB3YW50IHRvIGJlIG5vdGlmaWVkIHdo ZW4gbWFpbCBhcnJpdmVzCi0tLSA0MCw0NiAtLS0tCiAgLk5kICJiZSBub3RpZmllZCBpZiBtYWls IGFycml2ZXMgYW5kIHdobyBpdCBpcyBmcm9tIgogIC5TaCBTWU5PUFNJUwogIC5ObSBiaWZmCiEg Lk9wIENtIG4gfCB5IHwgYgogIC5TaCBERVNDUklQVElPTgogIC5ObSBCaWZmCiAgaW5mb3JtcyB0 aGUgc3lzdGVtIHdoZXRoZXIgeW91IHdhbnQgdG8gYmUgbm90aWZpZWQgd2hlbiBtYWlsIGFycml2 ZXMKKioqKioqKioqKioqKioqCioqKiA1Myw1OCAqKioqCi0tLSA1Myw2MCAtLS0tCiAgRGlzYWJs ZXMgbm90aWZpY2F0aW9uLgogIC5JdCBDbSB5CiAgRW5hYmxlcyBub3RpZmljYXRpb24uCisgLkl0 IENtIGIKKyBCZWVwcyB0d2ljZS4gIChQcmludHMgbm8gaGVhZGVyIGluZm9ybWF0aW9uLikKICAu RWwKICAuUHAKICBXaGVuIG1haWwgbm90aWZpY2F0aW9uIGlzIGVuYWJsZWQsIHRoZSBoZWFkZXIg YW5kIGZpcnN0IGZldyBsaW5lcyBvZgpJbmRleDogc3JjL3Vzci5iaW4vYmlmZi9iaWZmLmMKPT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PQpSQ1MgZmlsZTogL3Vzci9jdnMvZnJlZWJzZC9zcmMvdXNyLmJpbi9iaWZmL2JpZmYu Yyx2CnJldHJpZXZpbmcgcmV2aXNpb24gMS4xLjEuMQpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMgpk aWZmIC1jIC1yMS4xLjEuMSAtcjEuMgoqKiogYmlmZi5jCTE5OTgvMTIvMDMgMTU6NDE6NDAJMS4x LjEuMQotLS0gYmlmZi5jCTE5OTgvMTIvMDcgMTQ6NTI6MzkJMS4yCioqKioqKioqKioqKioqKgoq KiogODAsMTA3ICoqKioKICAJCWVycigyLCAic3RhdCIpOwogIAogIAlpZiAoKmFyZ3YgPT0gTlVM TCkgewohIAkJKHZvaWQpcHJpbnRmKCJpcyAlc1xuIiwgc2Iuc3RfbW9kZSYwMTAwID8gInkiIDog Im4iKTsKICAJCXJldHVybihzYi5zdF9tb2RlICYgMDEwMCA/IDAgOiAxKTsKICAJfQogIAogIAlz d2l0Y2goYXJndlswXVswXSkgewogIAljYXNlICduJzoKISAJCWlmIChjaG1vZChuYW1lLCBzYi5z dF9tb2RlICYgfjAxMDApIDwgMCkKICAJCQllcnIoMiwgbmFtZSk7CiAgCQlicmVhazsKICAJY2Fz ZSAneSc6CiEgCQlpZiAoY2htb2QobmFtZSwgc2Iuc3RfbW9kZSB8IDAxMDApIDwgMCkKICAJCQll cnIoMiwgbmFtZSk7CiAgCQlicmVhazsKICAJZGVmYXVsdDoKICAJCXVzYWdlKCk7CiAgCX0KISAJ cmV0dXJuKHNiLnN0X21vZGUgJiAwMTAwID8gMCA6IDEpOwogIH0KICAKICBzdGF0aWMgdm9pZAog IHVzYWdlKCkKICB7CiEgCSh2b2lkKWZwcmludGYoc3RkZXJyLCAidXNhZ2U6IGJpZmYgW3kgfCBu XVxuIik7CiAgCWV4aXQoMik7CiAgfQotLS0gODAsMTIxIC0tLS0KICAJCWVycigyLCAic3RhdCIp OwogIAogIAlpZiAoKmFyZ3YgPT0gTlVMTCkgewohIAkJc3dpdGNoIChzYi5zdF9tb2RlICYgKFNf SVhVU1IgfCBTX0lYR1JQKSkgewohIAkJY2FzZSBTX0lYVVNSOgohIAkJCSh2b2lkKXByaW50Zigi aXMgeVxuIik7CiEgCQkJYnJlYWs7CiEgCQljYXNlIFNfSVhHUlA6CiEgCQkJKHZvaWQpcHJpbnRm KCJpcyBiXG4iKTsKISAJCQlicmVhazsKISAJCWRlZmF1bHQ6CiEgCQkJKHZvaWQpcHJpbnRmKCJp cyBuXG4iKTsKISAJCQlicmVhazsKISAJCX0KICAJCXJldHVybihzYi5zdF9tb2RlICYgMDEwMCA/ IDAgOiAxKTsKICAJfQogIAogIAlzd2l0Y2goYXJndlswXVswXSkgewogIAljYXNlICduJzoKISAJ CWlmIChjaG1vZChuYW1lLCBzYi5zdF9tb2RlICYgfihTX0lYVVNSIHwgU19JWEdSUCkpIDwgMCkK ICAJCQllcnIoMiwgbmFtZSk7CiAgCQlicmVhazsKICAJY2FzZSAneSc6CiEgCQlpZiAoY2htb2Qo bmFtZSwgc2Iuc3RfbW9kZSAmIH5TX0lYR1JQIHwgU19JWFVTUikgPCAwKQohIAkJCWVycigyLCBu YW1lKTsKISAJCWJyZWFrOwohIAljYXNlICdiJzoKISAJCWlmIChjaG1vZChuYW1lLCBzYi5zdF9t b2RlICYgflNfSVhVU1IgfCBTX0lYR1JQKSA8IDApCiAgCQkJZXJyKDIsIG5hbWUpOwogIAkJYnJl YWs7CiAgCWRlZmF1bHQ6CiAgCQl1c2FnZSgpOwogIAl9CiEgCXJldHVybihzYi5zdF9tb2RlICYg KFNfSVhVU1IgfCBTX0lYR1JQKSA/IDAgOiAxKTsKICB9CiAgCiAgc3RhdGljIHZvaWQKICB1c2Fn ZSgpCiAgewohIAkodm9pZClmcHJpbnRmKHN0ZGVyciwgInVzYWdlOiBiaWZmIFt5IHwgbiB8IGJd XG4iKTsKICAJZXhpdCgyKTsKICB9CkluZGV4OiBzcmMvbGliZXhlYy9jb21zYXQvY29tc2F0LmMK PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PQpSQ1MgZmlsZTogL3Vzci9jdnMvZnJlZWJzZC9zcmMvbGliZXhlYy9jb21zYXQv Y29tc2F0LmMsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMS4xLjEKcmV0cmlldmluZyByZXZpc2lv biAxLjIKZGlmZiAtYyAtcjEuMS4xLjEgLXIxLjIKKioqIGNvbXNhdC5jCTE5OTgvMTIvMDMgMTU6 Mzg6MTAJMS4xLjEuMQotLS0gY29tc2F0LmMJMTk5OC8xMi8wNyAxNDo1NDoxNwkxLjIKKioqKioq KioqKioqKioqCioqKiAyMjAsMjI2ICoqKioKICAJCXN5c2xvZyhMT0dfQVVUSCB8IExPR19OT1RJ Q0UsICInLycgaW4gXCIlc1wiIiwgdHR5KTsKICAJCXJldHVybjsKICAJfQohIAlpZiAoc3RhdCh0 dHksICZzdGIpIHx8ICEoc3RiLnN0X21vZGUgJiBTX0lFWEVDKSkgewogIAkJZHN5c2xvZyhMT0df REVCVUcsICIlczogd3JvbmcgbW9kZSBvbiAlcyIsIHV0cC0+dXRfbmFtZSwgdHR5KTsKICAJCXJl dHVybjsKICAJfQotLS0gMjIwLDIyNiAtLS0tCiAgCQlzeXNsb2coTE9HX0FVVEggfCBMT0dfTk9U SUNFLCAiJy8nIGluIFwiJXNcIiIsIHR0eSk7CiAgCQlyZXR1cm47CiAgCX0KISAJaWYgKHN0YXQo dHR5LCAmc3RiKSB8fCAhKHN0Yi5zdF9tb2RlICYgKFNfSVhVU1IgfCBTX0lYR1JQKSkpIHsKICAJ CWRzeXNsb2coTE9HX0RFQlVHLCAiJXM6IHdyb25nIG1vZGUgb24gJXMiLCB1dHAtPnV0X25hbWUs IHR0eSk7CiAgCQlyZXR1cm47CiAgCX0KKioqKioqKioqKioqKioqCioqKiAyMzcsMjQ3ICoqKioK ICAJY3IgPSAoKHRpby5jX29mbGFnICYgKE9QT1NUfE9OTENSKSkgPT0gKE9QT1NUfE9OTENSKSkg PyAgIlxuIiA6ICJcblxyIjsKICAJKHZvaWQpc3RybmNweShuYW1lLCB1dHAtPnV0X25hbWUsIHNp emVvZih1dHAtPnV0X25hbWUpKTsKICAJbmFtZVtzaXplb2YobmFtZSkgLSAxXSA9ICdcMCc7CiEg CSh2b2lkKWZwcmludGYodHAsICIlc1wwMDdOZXcgbWFpbCBmb3IgJXNAJS4qc1wwMDcgaGFzIGFy cml2ZWQlcyVzJXM6JXMtLS0tJXMiLAohIAkgICAgY3IsIG5hbWUsIChpbnQpc2l6ZW9mKGhvc3Ru YW1lKSwgaG9zdG5hbWUsCiEgCSAgICBmb2xkZXIgPyBjciA6ICIiLCBmb2xkZXIgPyAidG8gIiA6 ICIiLCBmb2xkZXIgPyBmaWxlIDogIiIsCiEgCSAgICBjciwgY3IpOwohIAlqa2ZwcmludGYodHAs IG5hbWUsIGZpbGUsIG9mZnNldCk7CiAgCSh2b2lkKWZjbG9zZSh0cCk7CiAgCV9leGl0KDApOwog IH0KLS0tIDIzNywyNTcgLS0tLQogIAljciA9ICgodGlvLmNfb2ZsYWcgJiAoT1BPU1R8T05MQ1Ip KSA9PSAoT1BPU1R8T05MQ1IpKSA/ICAiXG4iIDogIlxuXHIiOwogIAkodm9pZClzdHJuY3B5KG5h bWUsIHV0cC0+dXRfbmFtZSwgc2l6ZW9mKHV0cC0+dXRfbmFtZSkpOwogIAluYW1lW3NpemVvZihu YW1lKSAtIDFdID0gJ1wwJzsKISAJc3dpdGNoIChzdGIuc3RfbW9kZSAmIChTX0lYVVNSIHwgU19J WEdSUCkpIHsKISAJY2FzZSBTX0lYVVNSOgohIAkJKHZvaWQpZnByaW50Zih0cCwgIiVzXDAwN05l dyBtYWlsIGZvciAlc0AlLipzXDAwNyBoYXMgYXJyaXZlZCVzJXMlczolcy0tLS0lcyIsCiEgCQkg ICAgY3IsIG5hbWUsIChpbnQpc2l6ZW9mKGhvc3RuYW1lKSwgaG9zdG5hbWUsCiEgCQkgICAgZm9s ZGVyID8gY3IgOiAiIiwgZm9sZGVyID8gInRvICIgOiAiIiwgZm9sZGVyID8gZmlsZSA6ICIiLAoh IAkJICAgIGNyLCBjcik7CiEgCQlqa2ZwcmludGYodHAsIG5hbWUsIGZpbGUsIG9mZnNldCk7CiEg CQlicmVhazsKISAJY2FzZSBTX0lYR1JQOgohIAkJKHZvaWQpIGZwcmludGYodHAsICJcMDA3Iik7 CiEgCQkodm9pZCkgZmZsdXNoKHRwKTsJCiEgCQkodm9pZCkgc2xlZXAoMSk7CiEgCQkodm9pZCkg ZnByaW50Zih0cCwgIlwwMDciKTsKISAJCWJyZWFrOwohIAl9CiAgCSh2b2lkKWZjbG9zZSh0cCk7 CiAgCV9leGl0KDApOwogIH0K ------- =_aaaaaaaaaa0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 11:25:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29179 for freebsd-current-outgoing; Sun, 13 Dec 1998 11:25:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29174 for ; Sun, 13 Dec 1998 11:25:03 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.1a/8.9.0) with SMTP id NAA24175; Sun, 13 Dec 1998 13:24:58 -0600 (CST) Date: Sun, 13 Dec 1998 13:24:58 -0600 (CST) From: Steve Price To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: make release busted creating README.html for net/gtkicq In-Reply-To: <199812131725.MAA12313@bb01f39.unx.sas.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 Jordan fixed this in revision 1.4 of the Makefile for this port. -steve On Sun, 13 Dec 1998, John W. DeBoskey wrote: # Hi, # # The subject says it all... # # ===> net/gopher # ===> Creating README.html for gopher-2.3 # ===> net/gicq # ===> Creating README.html for gicq-0.22 # ===> net/gtkicq # "Makefile", line 13: Unassociated shell command "ftp://ftp.rnd.runnet.ru/pub/uni # x/GUI_Toolkits/gtk/" # make: fatal errors encountered -- cannot continue # *** Error code 1 # # Stop. # # In "/usr/ports/net/gtkicq/Makefile": # # Would someone please delete the tab character at the end of line 12 # of the Makefile? It's breaks the continuation. # # Thanks, # John # # To Unsubscribe: send mail to majordomo@FreeBSD.org # with "unsubscribe freebsd-current" in the body of the message # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 12:48:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07742 for freebsd-current-outgoing; Sun, 13 Dec 1998 12:48:09 -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 MAA07732 for ; Sun, 13 Dec 1998 12:48:07 -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 NAA09089; Sun, 13 Dec 1998 13:48:04 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA06177; Sun, 13 Dec 1998 13:48:04 -0700 Date: Sun, 13 Dec 1998 13:48:04 -0700 Message-Id: <199812132048.NAA06177@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: minor vipw/pwd_mkdb changes commited In-Reply-To: <199812130203.SAA14359@apollo.backplane.com> References: <199812130203.SAA14359@apollo.backplane.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've made a few minor fixes to vipw and pwd_mkdb to handle a > master.passwd race condition (note: there are no security issues > with the race). I *think* I fixed this is Auguest already, didn't I? nate 1998/07/16 10:18:30 PDT Modified files: usr.sbin/pw edgroup.c fileupd.c pw.c Log: Fix race condition in pw caused by multiple instances of pwd_mkdb being run at the same time. Notes: The fileupdate function is still somewhat broken. Instead of returning a failure code if it can't modify the original file it renames the .new file and continues as though nothing is wrong. This will cause the lock on the original file to be lost and could lead to a similar race condition. I left that portion of the code alone since I feel that the maintainer of the code would have a better concept of how he wants to handle errors in that function than I do. PR: bin/6787 Submitted by: Craig Spannring If not, will these changes conflict with the above changes? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 12:55:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08708 for freebsd-current-outgoing; Sun, 13 Dec 1998 12:55:15 -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 MAA08703 for ; Sun, 13 Dec 1998 12:55:13 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id OAA14463; Sun, 13 Dec 1998 14:00:59 -0700 (MST) Message-Id: <199812132100.OAA14463@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: Mike Smith cc: mwlucas@exceptionet.com, freebsd-current@FreeBSD.ORG Subject: Re: good new 3x laptop? In-reply-to: Your message of "Sun, 13 Dec 1998 10:32:34 PST." <199812131832.KAA00419@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 14:00:59 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > I'm about to purchase a laptop to run FreeBSD on. With all this > > discussion about PAO and -current differences, I figured I'd better ask > > first. ;) > > > > Can anyone recommend a decent new laptop for FreeBSD? I want to run 3.x. > > I'm looking in the sub-$2000 range. > > Any of the Toshiba Satellite units in that range will give you good > service. How about a high end PII/14" display machine. I need to have 3.0-current development system for field compiles. A good docking station would be a plus. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 13:21:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11531 for freebsd-current-outgoing; Sun, 13 Dec 1998 13:21:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11526 for ; Sun, 13 Dec 1998 13:21:28 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t1o29p106.telia.com [194.236.214.106]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id WAA00539; Sun, 13 Dec 1998 22:21:20 +0100 Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.1/8.9.1) with ESMTP id WAA02579; Sun, 13 Dec 1998 22:11:49 +0100 (CET) (envelope-from johan@granlund.nu) Date: Sun, 13 Dec 1998 22:11:49 +0100 (CET) From: Johan Granlund To: Matthew Jacob cc: Greg Lehey , FreeBSD current users Subject: Re: Can't access tapes with scsi_sa.c r1.7 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 Sun, 13 Dec 1998, Matthew Jacob wrote: > > I did writes to EOT, but not with dump. Then it's probally fixed as it was a kernel panic and not dump that cored. /Johan > > > On Sat, 12 Dec 1998, Matthew Jacob wrote: > > > > > > > > Yes, that'd be my change. Whups! It worked for me! Could you build a > > > > And it also works for me. Exabyte EXB-8200 and Adaptec 2940UW. Both dump > > and restore of selected files. This is with variable blocksize. > > > > Matthew: Did you test making a fulltape dump (until EOT) that caused a > > kernel panic (kernel from Nov 7) for me? I can't test this easily now > > beqause my large datadisk finally failed. I should get a replacement > > sometime next week. Then we will see if a full multitape restore works:) > > > > /Johan > > > > > CAMDEBUG kernel, use camcontrol to turn on debugging for that device and > > > do whatever it is you did and send me the output, or send me what it is > > > you tried first? I'll be in my shop tomorrow morning to work on this! > > > Sorry! > > > > > > > > > > > > > > > > > > > > > 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 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 14:04:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14851 for freebsd-current-outgoing; Sun, 13 Dec 1998 14:04: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 OAA14846 for ; Sun, 13 Dec 1998 14:04:09 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id PAA29916; Sun, 13 Dec 1998 15:04:01 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp02.primenet.com, id smtpd029876; Sun Dec 13 15:03:52 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA09407; Sun, 13 Dec 1998 15:03:49 -0700 (MST) From: Terry Lambert Message-Id: <199812132203.PAA09407@usr09.primenet.com> Subject: Re: PAO Integration? To: imp@village.org (Warner Losh) Date: Sun, 13 Dec 1998 22:03:48 +0000 (GMT) Cc: mike@smith.net.au, y-nakaga@nwsl.mesh.ad.jp, mark@grondar.za, current@FreeBSD.ORG In-Reply-To: <199812110109.SAA65255@harmony.village.org> from "Warner Losh" at Dec 10, 98 06:09:50 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : > > shutdown -h. What is wrong with this? > : > > : > It is wrong. > > Why? Traditionally Unix hasn't run on hardware that has software > power off. Who can say what traditional unix is when the hardware has > a new feature? The AT&T 3B2 I uses to use had soft power-off... to get UNIX hardware old than that, you'd need to use a VAX. The VAX at the Univeristy of Utah at the time I was there could switch off its UPS; it didn't normally do this, of course, but the possibility was there. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 14:26:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16358 for freebsd-current-outgoing; Sun, 13 Dec 1998 14:26:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16353 for ; Sun, 13 Dec 1998 14:26:32 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id OAA11909; Sun, 13 Dec 1998 14:25:39 -0800 Date: Sun, 13 Dec 1998 14:25:39 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Gary Jennejohn cc: Greg Lehey , FreeBSD current users Subject: (Re: Can't access tapes with scsi_sa.c r1.7) (LONG) In-Reply-To: <199812131103.MAA00577@peedub.muc.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 Well, I've been looking over this, and a preliminary check seems to indicate to me that the driver is, in fact, doing what it is supposed to do. Now, wait, don't start throwing things yet.. :-) The simple fix for all of you is to explicitly set variable mode (mt blocksize 0) on your tape device *if you want it to be in variable record length mode*, but see. If you're in fixed block mode (the default now that a lot of these drives show up as, but see below), and you issue a read that doesn't match the blocksize for that device, you get an ILI (incorrect length indicator) error- no data was actually transferred. I went back to the 1.6 version, added some debugging, and ran on a 8505 the same sorts of tests that Greg had done. The test here is you have a header record, say, of 512 bytes, followed by a filemark, and you read it with a 1k read from user space. Here's what had occurred: scsi_sa, 1.6: a) The device is in fixed block mode, but the tape driver is ignorant of this. This is because the old test at samount time was to see whether the maximum block size supported equaled the minimum blocksize, not what the actual current blocksize is. b) Thus, a read of 1k bytes gets shipped out as a variable mode read- not as a fixed length read. c) This gets returned, like a variable length read should, as having read 512 bytes of 1024 requested. This gets propagated back to the user application as a short read. All is good, if frightening because reality and driver state aren't coordinated, but.... !!!!!!!!The results of what occurs when you *write* such a device are not entirely predictable. Some tape devices, like the Exabyte 85XX and probably the Archive DAT drives, really don't care what 'mode' they're in but simply key off of each WRITE command as to what the actual record size being requested is. Other tape devices, e.g. the Exabyte 8200, get really bothered and just cannot cope. The main point of the 1.6 to 1.7 change was to address this. scsi_sa, 1.7: a) The device is in fixed block mode, and the tape driver is now cognizant of this because it keys off of what the actual current blocksize for the device is. b) A read of 1k bytes gets turned into a fixed length read of 1 record (1024 bytes) and shipped down to the drive- but the drive bounces the read because the only record available is the 512 byte record- and no data is actually then transferred and an error is returned to the user application. This is, in fact, the desired behaviour for fixed length record operations. Well, you *could* argue that SILI should be set (which supresses this error), but I would assert that you should just be operating in variable record mode when you want read variably sized records. If you use SILI, people will forget that they're in fixed block mode and when they write tapes with what *they* think are variable sized records, they won't be, which will be a zoo for media interchange.... In any case, the take home lesson of the change between scsi_sa 1.6 and 1.7 is that a 'fix' to actually make the driver operate as it is supposed to violated the principle of least surprise and nailed some folks- Sorry! scsi_sa, 1.8: (NOT YET INTEGRATED) What was *planned* was that in response to several requests, the *real* default behaviour should very likely be to to put all tape devices (with the exception of some QIC devices) into variable block mode at samount time unless someone has explicitly set fixed record mode. Opinions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 14:35:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17342 for freebsd-current-outgoing; Sun, 13 Dec 1998 14:35:49 -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 OAA17335 for ; Sun, 13 Dec 1998 14:35:47 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA21481; Sun, 13 Dec 1998 15:35:45 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd021470; Sun Dec 13 15:35:43 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA10207; Sun, 13 Dec 1998 15:35:42 -0700 (MST) From: Terry Lambert Message-Id: <199812132235.PAA10207@usr09.primenet.com> Subject: Re: HEADS UP : laptop power-down change To: imp@village.org (Warner Losh) Date: Sun, 13 Dec 1998 22:35:42 +0000 (GMT) Cc: mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: <199812110422.VAA65796@harmony.village.org> from "Warner Losh" at Dec 10, 98 09:22:15 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : No. RB_POWEROFF and RB_HALT have very different meanings. The PC > : doesn't have a useful means for getting back to the resident firmware, > : but many other systems do. That's what RB_HALT is meant to do, while > : RB_POWEROFF is meant to power the system down. The two are mutually > : exclusive. > > I know... halt should turn the machine off. Halt should trigger the halt trap, which on an Alpha means putting you into the boot monitor. For the PC, it means putting you in a state where you can hit "DEL" to get the setup, or "CTRL-A" to get into the Adaptec BIOS configuration, etc.. It's not FreeBSD's fault that (most) PC hardware is too stupid to have a boot-ROM that lets you configure things before triggering the boot loader, unless you overrice the default behaviour with keystrokes while it's pounding away at things. Also, I think the correct flag is "-x", not "-p", from a historical (Sony NeWS, NeXTStep, and A/UX, et. al.). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 14:44:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18164 for freebsd-current-outgoing; Sun, 13 Dec 1998 14:44:50 -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 OAA18159 for ; Sun, 13 Dec 1998 14:44:49 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA28907; Sun, 13 Dec 1998 15:44:40 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd028850; Sun Dec 13 15:44:34 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA10383; Sun, 13 Dec 1998 15:44:29 -0700 (MST) From: Terry Lambert Message-Id: <199812132244.PAA10383@usr09.primenet.com> Subject: Re: inetd: realloc/free bug To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 13 Dec 1998 22:44:29 +0000 (GMT) Cc: archie@whistle.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199812110659.WAA35073@apollo.backplane.com> from "Matthew Dillon" at Dec 10, 98 10:59:07 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 > :> If you put a time limit on select(), it doesn't matter if there is a > :> race condition there. How does select() cause a signal to be missed ? > : > :Well, sure.. :-) but then you don't service signals in real time > :and spend extra cycles timing out all the time. > > You do serve signals in real time... the signals are *unmasked* during > the select() :-) ... the race condition is that the unmasked signal may > cause the descriptor set to be changed just prior to the select() call, > causing select() to wait forever. The timeout on the select() handles > the race condition without effecting the realtime delivery of signals. You should just use siginterrupt(3) to make sure select restarts, and be done with it. If you need to interrupt the select after setting system call restart behaviour, then use a longjmp from the signal handler after setting a volatile flag so that the flag can be tested in the "else" case of the setjmp() call. If the call is restarted, you don't have to worry about the timer, it will do the right thing, and you won't get an EINTR that you con't know how to handle the masks around. If you don't like siginterrupt(3), and want to use the non-Berkeley signal mechanisms for setting call restart behaviour, then be my guest and write 30 or 40 lines of POSIX expecting code instead. The siginterrupt(2) system call first appeared in BSD 4.1c; the current code uses POSIX sigaction(2); someone might want to correct the siginterrupt(3) man page... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 14:54:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18896 for freebsd-current-outgoing; Sun, 13 Dec 1998 14:54:11 -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 OAA18890 for ; Sun, 13 Dec 1998 14:54:10 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA01500; Sun, 13 Dec 1998 15:54:05 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd001476; Sun Dec 13 15:54:04 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA10799; Sun, 13 Dec 1998 15:53:54 -0700 (MST) From: Terry Lambert Message-Id: <199812132253.PAA10799@usr09.primenet.com> Subject: Re: inetd: realloc/free bug To: archie@whistle.com (Archie Cobbs) Date: Sun, 13 Dec 1998 22:53:54 +0000 (GMT) Cc: peter.edwards@isocor.ie, dillon@apollo.backplane.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199812111940.LAA27652@bubba.whistle.com> from "Archie Cobbs" at Dec 11, 98 11:40:58 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 guess I was thinking in terms of the event library model; that is, > you don't handle the signal event in the signal handler (because in > general the event handler could call malloc(), etc), but rather you > simply set a flag (call it "signalFlag"). > > The race condition is getting a signal between the first and second > lines below: > > sigprocmask(SIG_UNBLOCK ..) /* unblock signals */ > r = select(...) /* wait for event */ > sigprocmask(SIG_BLOCK ..) /* block signals */ > > if (signalFlag || r > 0) { > ... /* handle event(s) */ > } > > But there are probably smarter ways to do it than this. Yes. Don't block signals, use a setjmp for the select, and choose system call restart behaviour. The race you are concerned with is a signal occurring before the select starts, and the resulting EINTR. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 14:56:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19312 for freebsd-current-outgoing; Sun, 13 Dec 1998 14:56:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19306; Sun, 13 Dec 1998 14:56:32 -0800 (PST) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (Postfix) with ESMTP id C6979182; Sun, 13 Dec 1998 23:56:21 +0100 (MET) Received: by ariel.xaa.iae.nl (Postfix, from userid 1008) id 8FC283E15; Sun, 13 Dec 1998 23:56:15 +0100 (CET) Date: Sun, 13 Dec 1998 23:56:15 +0100 From: Mark Huizer To: questions@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: ^@^@^@^@^@^@^@ (empty pages) in NFS served file. Message-ID: <19981213235615.A12800@ariel.xaa.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! quite often I run into problems with NFS served files, containing a page of ^@^@^@^@^@^@^@'s instead of actual data (mostly noticed in textfiles). After checking on the server, it seems the data is valid there. Touch'ing it helps sometimes. Environment is 2x FreeBSD current, running nfsv3 over udp, on machines with softupdates enabled. Anyone having the same trouble?? Mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 15:13:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22412 for freebsd-current-outgoing; Sun, 13 Dec 1998 15:13:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22407 for ; Sun, 13 Dec 1998 15:13:43 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id SAA20113 for ; Sun, 13 Dec 1998 18:13:38 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA15439; Sun, 13 Dec 1998 18:13:38 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id SAA13630 for freebsd-current@freebsd.org; Sun, 13 Dec 1998 18:13:37 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812132313.SAA13630@bb01f39.unx.sas.com> Subject: Re: cvs commit: src/etc Makefile To: freebsd-current@FreeBSD.ORG Date: Sun, 13 Dec 1998 18:13:37 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Eivind Eklund Subject: Re: cvs commit: src/etc Makefile Eivind said: > On Sun, Dec 13, 1998 at 02:44:23PM +0200, Mark Murray wrote: > > Dag-Erling Smorgrav wrote: > > > Better, but not sufficient; it assumes that the user checks 'ls > > > /etc/*sample' after make world. For such a feature to have any effect, > > > you have to somehow warn the user about missing files, e.g. by mailing > > > a list to root. > > > > I can see annoyed users turning this off and _still_ complaining. Current > > is turning into too much of a commodity with not enough emphasis of "thou > > shalt RTFM and RTSL". > > I've been thinking of how to say this with a suitable amount of force. > One way of doing this could be to stop cvsup access for -current. > > Yup - if you want to track -current, you track the cvs repository. If > you don't need the cvs repository, you're not developing code, and > thus shouldn't be in -current. > > I'm not sure if this is too drastic, but we really should be shooting > off those people... > > Eivind. Well, a dose of reality. Every one of you used to be in the position of some of these "people". You didn't know everything. And sometimes, RTFM just doesn't do the trick, especially when TFM is out-of-date because you the "developers" changed the code, but not the doc's. Now, with that said... My stupid question: How does one track -current without cvsup? I can't access the repository via nfs, and I don't have an account for either pserver or rsh mode... Now some praise for the the committers who have been working through the bug database. Thanks! And my pet peaves :-) 'make release' still seems to be installing a kerberos system. telnetd has a bug somewhere in it's handling of the default banner: / (cvs.unx.sas.com) (ttyp1) which should read: FreeBSD/i386 (cvs.unx.sas.com) (ttyp1) This is ONLY exhibitted under the krb version of telnetd, the the default version. Comments, Critiques, and helpful hints are ALWAYS welcome! Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 16:22:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03188 for freebsd-current-outgoing; Sun, 13 Dec 1998 16:22:20 -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 QAA03164; Sun, 13 Dec 1998 16:22:12 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA17891; Mon, 14 Dec 1998 10:51:24 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812112008.MAA28016@bubba.whistle.com> Date: Mon, 14 Dec 1998 10:51:15 +1030 (CST) From: "Daniel O'Connor" To: Archie Cobbs Subject: Re: mformat in free(): warning: junk pointer, too high to make s Cc: dg@FreeBSD.ORG, current@FreeBSD.ORG, vallo@matti.ee, eivind@yes.no, jkh@zippy.cdrom.com, sthaug@nethelp.no Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Dec-98 Archie Cobbs wrote: > Looks like the same idea but much more complete (and probably faster, > better tested, etc..) I'd love to break this out into it's own library > in src/lib. I think lots of people would find it useful. What kind of > backlash could I expect? :-) Probably a large one of the variety 'why did it take so long?' :) Sounds like an EXCELLENT idea! > The other libraries look interesting too: "heap", "tree", "logging", etc. Yes, indeedy :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 17:00:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05856 for freebsd-current-outgoing; Sun, 13 Dec 1998 17:00:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05843 for ; Sun, 13 Dec 1998 17:00:51 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id UAA00551 for ; Sun, 13 Dec 1998 20:00:46 -0500 (EST) Date: Sun, 13 Dec 1998 20:00:45 -0500 (EST) From: jack To: freebsd-current@FreeBSD.ORG Subject: make install broken in /usr/sys/etc 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 Someone needs to tell /usr/src/etc/Makefile that rc.local went away, it still trys to install it. :( -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 18:01:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12427 for freebsd-current-outgoing; Sun, 13 Dec 1998 18:01:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12422 for ; Sun, 13 Dec 1998 18:01:35 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA07770; Sun, 13 Dec 1998 18:01:22 -0800 (PST) (envelope-from dillon) Date: Sun, 13 Dec 1998 18:01:22 -0800 (PST) From: Matthew Dillon Message-Id: <199812140201.SAA07770@apollo.backplane.com> To: jack Cc: freebsd-current@FreeBSD.ORG Subject: Re: make install broken in /usr/sys/etc References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fixed! -Matt : :Someone needs to tell /usr/src/etc/Makefile that rc.local went :away, it still trys to install it. :( : :-------------------------------------------------------------------------- :Jack O'Neill Systems Administrator / Systems Analyst :jack@germanium.xtalwind.net Crystal Wind Communications, Inc. : Finger jack@germanium.xtalwind.net for my PGP key. : PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD : enriched, vcard, HTML messages > /dev/null :-------------------------------------------------------------------------- : : : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 18:08:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12934 for freebsd-current-outgoing; Sun, 13 Dec 1998 18:08:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12929 for ; Sun, 13 Dec 1998 18:08:35 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA07846; Sun, 13 Dec 1998 18:08:31 -0800 (PST) (envelope-from dillon) Date: Sun, 13 Dec 1998 18:08:31 -0800 (PST) From: Matthew Dillon Message-Id: <199812140208.SAA07846@apollo.backplane.com> To: Terry Lambert Cc: archie@whistle.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812132244.PAA10383@usr09.primenet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think there's some confusion here: The reason there is a timeout on the select has nothing to do with signals interrupting system calls. We don't care about that case - it's irrelevant. The only reason there is a timeout on the select is to handle the case where a signal occurs just *BEFORE* select() is entered where the signal function adds a file descriptor to the mask set. If this case occurs, the select() will wind up waiting on a mask set that does not contain the new descriptor thus possibly resulting in an infinite wait. That is the *SOLE REASON* why there is a timeout on the select. As I have said repeatedly: If someone does a read of the code and can guarentee that none of the signal functions *add* a descriptor to the mask set, we can remove the timeout entirely. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) :> :> If you put a time limit on select(), it doesn't matter if there is a :> :> race condition there. How does select() cause a signal to be missed ? :> : :> :Well, sure.. :-) but then you don't service signals in real time :> :and spend extra cycles timing out all the time. :> :> You do serve signals in real time... the signals are *unmasked* during :> the select() :-) ... the race condition is that the unmasked signal may :> cause the descriptor set to be changed just prior to the select() call, :> causing select() to wait forever. The timeout on the select() handles :> the race condition without effecting the realtime delivery of signals. : :You should just use siginterrupt(3) to make sure select restarts, and be :done with it. : :If you need to interrupt the select after setting system call restart :behaviour, then use a longjmp from the signal handler after setting a :volatile flag so that the flag can be tested in the "else" case of :the setjmp() call. : :If the call is restarted, you don't have to worry about the timer, it :will do the right thing, and you won't get an EINTR that you con't know :how to handle the masks around. : :If you don't like siginterrupt(3), and want to use the non-Berkeley :signal mechanisms for setting call restart behaviour, then be my :guest and write 30 or 40 lines of POSIX expecting code instead. : :The siginterrupt(2) system call first appeared in BSD 4.1c; the :current code uses POSIX sigaction(2); someone might want to correct :the siginterrupt(3) man page... : : : 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 : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 18:22:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14149 for freebsd-current-outgoing; Sun, 13 Dec 1998 18:22:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pippin.jblhome.ping.dk (pm28-32.image.dk [194.234.59.224]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14136 for ; Sun, 13 Dec 1998 18:22:36 -0800 (PST) (envelope-from jacob@e-postboks.dk) Received: (from jablo@localhost) by pippin.jblhome.ping.dk (8.9.1/8.9.1) id CAA11210; Mon, 14 Dec 1998 02:24:52 +0100 (CET) (envelope-from jacob) X-Authentication-Warning: pippin.jblhome.ping.dk: jablo set sender to jacob using -f To: Chris Timmons Cc: Brett Taylor , freebsd-current@FreeBSD.ORG Subject: Re: make aout-to-world-build problem References: From: Jacob Bohn Lorensen Date: 14 Dec 1998 02:24:31 +0100 In-Reply-To: Chris Timmons's message of Tue, 8 Dec 1998 15:02:16 -0800 (PST) Message-ID: <87g1ajikhc.fsf@pippin.jblhome.ping.dk> Lines: 32 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Timmons writes: > make aout-to-elf-build > make aout-to-elf-install > I just successfully did it from a 2.2.7 system. Make sure you start with > a real -current /usr/src and have plenty of room 300+MB for /usr/obj. I did the same thing about a week ago. I had two problems, one of which I am sure was a pilot error (I did it with at umask of 007 so only root was able to run aout programs after the upgrade as all the lib/aout directories were created with only user and group read/execute permissions). The other (non pilot-error) was that I had to do a find / -name '*.a' -o -name '*.so.*' | xargs chflags noschg before makeing aout-to-elf-install otherwise the upgrade process wasnt able to move the aout libraries. > On Tue, 8 Dec 1998, Brett Taylor wrote: > > Hi, > > I've been trying to do a make aout-to-world-build w/ -current sources from > > that I cvsup'ed on the 6th of Dec. I am attempting to upgrade from 2.2.8 > > to -current. -- Jacob Lorensen; Mosebuen 33, 1.; DK-2820 Gentofte, Denmark; +45 39560401 PGPid: 0x752EB4DE Fingerprint: F609A0BAFF393EA904F7-F344680F8EED752EB4DE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 18:47:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16043 for freebsd-current-outgoing; Sun, 13 Dec 1998 18:47:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16038 for ; Sun, 13 Dec 1998 18:46:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA18566; Sun, 13 Dec 1998 18:46:54 -0800 (PST) (envelope-from dillon) Date: Sun, 13 Dec 1998 18:46:54 -0800 (PST) From: Matthew Dillon Message-Id: <199812140246.SAA18566@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: 'make clean' in /usr/src does not cleanup .o's or shared libs ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to do a buildworld with /usr/src mounted read-only (via NFS). The buildworld has died several times trying to remove .o files, binaries, and libraries (*.so.*) from /usr/src that happened to be hanging around. Ok, I say... cd /usr/src on the physical machine and 'make clean'. Only problem is it doesn't work... it does not recursive through the entire source hierarchy. For example, make clean in /usr/src does not bother recursing through /usr/src/bin, /usr/src/sbin, /usr/src/gnu, etc... It is *very* annoying. Is there any particular reason why make clean in /usr/src does not clean the entire source hierarchy? Also, having to restart the buildworld from scratch every time it blows up and exits is also quite annoying. It would be nice to have a 'rebuildworld' target that uses dot files similar to the way bsd.port.mk uses them to pick up where it left off. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 19:14:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18431 for freebsd-current-outgoing; Sun, 13 Dec 1998 19:14:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18426 for ; Sun, 13 Dec 1998 19:14:41 -0800 (PST) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id UAA13285 for ; Sun, 13 Dec 1998 20:14:21 -0700 (MST) (envelope-from brett@peloton.physics.montana.edu) Date: Sun, 13 Dec 1998 20:14:21 -0700 (MST) From: Brett Taylor To: freebsd-current@FreeBSD.ORG Subject: Navigator problem in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I moved to -CURRENT on Dec 10th. I pkg_deleted all my old -STABLE ports and reinstalled from scratch so everything would be ELF. Problem - I can't get Netscape Navigator to run. I saw this mentioned before in -current so I scanned through the archive and the recommended fix was to copy an aout version of libXt.so.6.0 into /usr/X11R6/lib/aout and then do an ldconfig -aout -m /usr/X11R6/lib/aout When I copy this over from my -STABLE machine and try this I get: monkey: {5} ldconfig -aout -m /usr/X11R6/lib/aout ldconfig: /var/run/ld.so.hints: No such file or directory Do I need to do something else in addition to this? Brett ****************************************************************** Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ On the eve of his 21st birthday, he set out on his own He was 30 years and runnin' when he found his way back home Ridin' a storm across the mountains and an achin' in his heart Said he came to turn the pages and to make a brand new start To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 19:23:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19102 for freebsd-current-outgoing; Sun, 13 Dec 1998 19:23:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19096 for ; Sun, 13 Dec 1998 19:23:01 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id WAA15115 for ; Sun, 13 Dec 1998 22:22:58 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA01633; Sun, 13 Dec 1998 22:22:57 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id WAA14885 for freebsd-current@freebsd.org; Sun, 13 Dec 1998 22:22:57 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812140322.WAA14885@bb01f39.unx.sas.com> Subject: /etc/rc busted for legacy aout ldconfig setup To: freebsd-current@FreeBSD.ORG Date: Sun, 13 Dec 1998 22:22:57 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The following commit broke legacy ldconfig aout support: 1.161 Thu Dec 10 8:06:59 1998 UTC by jb Diffs to 1.160 Add a test for hw.machine == i386 before trying to run ldconfig for legacy aout support. The following conditional is wrong: if [ X"`sysctl hw.machine`" = X"i386" ]; then and needs to read: if [ X"`sysctl hw.machine | cut -d' ' -f2`" = X"i386" ]; then assuming the bruce filter doesn't mind a pipe in an 'if' statement. Anyone running a -current machine doing a 'make world' every day and still using any aout libraries will be affected by this. Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 19:28:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19776 for freebsd-current-outgoing; Sun, 13 Dec 1998 19:28:21 -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 TAA19770 for ; Sun, 13 Dec 1998 19:28:18 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id OAA01662; Mon, 14 Dec 1998 14:40:13 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812140340.OAA01662@cimlogic.com.au> Subject: Re: /etc/rc busted for legacy aout ldconfig setup In-Reply-To: <199812140322.WAA14885@bb01f39.unx.sas.com> from "John W. DeBoskey" at "Dec 13, 98 10:22:57 pm" To: jwd@unx.sas.com (John W. DeBoskey) Date: Mon, 14 Dec 1998 14:40:13 +1100 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John W. DeBoskey wrote: > 1.161 Thu Dec 10 8:06:59 1998 UTC by jb > Diffs to 1.160 > > Add a test for hw.machine == i386 before trying to run ldconfig for > legacy aout support. > > > The following conditional is wrong: > > if [ X"`sysctl hw.machine`" = X"i386" ]; then There's a -n in rev 1.162. Please check the _current_ sources before reporting this sort of thing. 1.162 is dated 1998/12/11 08:25:12. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 20:08:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21786 for freebsd-current-outgoing; Sun, 13 Dec 1998 20:08:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21781 for ; Sun, 13 Dec 1998 20:08:18 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40406>; Mon, 14 Dec 1998 15:07:29 +1100 Date: Mon, 14 Dec 1998 15:07:58 +1100 From: Peter Jeremy Subject: Re: panic: getnewbuf inconsistent EMPTY queue in 3.0-RELEASE To: freebsd-current@FreeBSD.ORG Message-Id: <98Dec14.150729est.40406@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri Dec 4 07:47:27 1998, I wrote: >I've just upgraded a Dell OptiPlex GXi from 32MB to 96MB. When I >increase MAXUSERS from 20 to 40 and SEMMNU from 350 to 1000, the >system panics `getnewbuf: inconsistent EMPTY queue, qindex=0' >immediately after the message `changing root device to wd0s1a'. I've managed to track this down to a bug in the handling of SysV semaphore undo structures when non-default SEMxxx values are used. Look up kern/9068 for details. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 20:41:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24440 for freebsd-current-outgoing; Sun, 13 Dec 1998 20:41:21 -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 UAA24435 for ; Sun, 13 Dec 1998 20:41:17 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA12411; Sun, 13 Dec 1998 20:31:29 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdK12406; Mon Dec 14 04:31:23 1998 Date: Sun, 13 Dec 1998 20:31:20 -0800 (PST) From: Julian Elischer To: Terry Lambert cc: Warner Losh , mike@smith.net.au, y-nakaga@nwsl.mesh.ad.jp, mark@grondar.za, current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812132203.PAA09407@usr09.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 Archie and I added dthe RB_POWEROFF flag to allow our Interjets to turn off the power when requested. In other situations we do not want to remove power, but rather halt so that control is then handed to the H/W watchdog, which will do a full reset of everything. I was also thinking of laptops whan I added this. (see the commit message) We'd be really thrilled if someone changed the semantics out from under us...... RB_POWEROFF does exactly that. RB_HALT does NOT do that. The processor either executes a HALT instrauction, or enters a type loop. Alternatively it might go to a firmware monitor, but we don't have that. what the 'shutdown' instruction does is arguable, but my personal feel is that it should require an argument to make it power off. Just like it requires an argument to make it reboot. On Sun, 13 Dec 1998, Terry Lambert wrote: > > : > > shutdown -h. What is wrong with this? > > : > > > : > It is wrong. > > > > Why? Traditionally Unix hasn't run on hardware that has software > > power off. Who can say what traditional unix is when the hardware has > > a new feature? > > The AT&T 3B2 I uses to use had soft power-off... to get UNIX hardware > old than that, you'd need to use a VAX. The VAX at the Univeristy > of Utah at the time I was there could switch off its UPS; it didn't > normally do this, of course, but the possibility was there. > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 20:48:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24790 for freebsd-current-outgoing; Sun, 13 Dec 1998 20:48:32 -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 UAA24774; Sun, 13 Dec 1998 20:48:25 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA12553; Sun, 13 Dec 1998 20:39:51 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdO12550; Mon Dec 14 04:39:41 1998 Date: Sun, 13 Dec 1998 20:39:38 -0800 (PST) From: Julian Elischer To: Poul-Henning Kamp cc: current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! In-Reply-To: <8711.913504842@critter.freebsd.dk> 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 how about porting the whole shebang to whistle's 'streams' replacement.. we could probably supply the frame relay and ppp packetizer nodes along with the framework and tools... s On Sun, 13 Dec 1998, Poul-Henning Kamp wrote: > > I think I have finally found out what the problem is with the state > machine in the if_sppp implementation. Whoever wrote the implementation > didn't carefully consider the inter-layer calls tls and tlf. > > If one applies a lot of patches like this one: > > case STATE_OPENED: > - (cp->tld)(sp); > sp->rst_counter[cp->protoidx] = 0; > sppp_cp_change_state(cp, sp, STATE_STOPPING); > + (cp->tld)(sp); > goto sta; > break; > > Then things actually start to make sense... > > The problem is that the tld and tlf functions often just call the > pp_up and pp_down routines directly, and therefore most if not all > of the expected up and down events happen in the previous state > as opposed to the next state. > > Flipping it around like I have done above, on the other hand, may > not be a good idea either, since it means we can nest another layer > on the stack and get somewhat confused on the way down. > > It is quite obvious that this will need some more work to sort out, > anybody interested in participating ? > > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 21:29:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28956 for freebsd-current-outgoing; Sun, 13 Dec 1998 21:29:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28951 for ; Sun, 13 Dec 1998 21:29:34 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA26641; Sun, 13 Dec 1998 21:29:30 -0800 (PST) (envelope-from dillon) Date: Sun, 13 Dec 1998 21:29:30 -0800 (PST) From: Matthew Dillon Message-Id: <199812140529.VAA26641@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: Totally illegal declaration/check in i386/i386/busdma_machdep.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG GCC warning expected? I'm sorry, but this is *illegal*. Totally illegal. nextpaddr can be legally destroyed on each loop by the compiler. I know what the author was trying to do, but he's wrong. I'm fixing this. (from i386/i386/busdma_machdep.c) do { bus_size_t size; vm_offset_t nextpaddr; /* GCC warning expected */ paddr = pmap_kextract(vaddr); size = PAGE_SIZE - (paddr & PAGE_MASK); if (size > buflen) size = buflen; ... } else if (paddr == nextpaddr) { sg->ds_len += size; ... nextpaddr = paddr + size; buflen -= size; } while (buflen > 0); Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 21:47:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00468 for freebsd-current-outgoing; Sun, 13 Dec 1998 21:47:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00462 for ; Sun, 13 Dec 1998 21:47:50 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id QAA11172; Mon, 14 Dec 1998 16:47:42 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma011166; Mon, 14 Dec 98 16:47:40 +1100 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id QAA05843 for ; Mon, 14 Dec 1998 16:47:31 +1100 From: "John Saunders" To: "FreeBSD current" Subject: RE: inetd: realloc/free bug Date: Mon, 14 Dec 1998 16:47:31 +1100 Message-ID: <002f01be2725$3dab6af0$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199812110722.AAA00650@harmony.village.org> X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Linux implemented the timeval stomping version of select. It was the > first OS to do this. At the time they claimed that BSD 4.4 would be > doing this and that they were going to be compatible with that, plus > it was listed as a bug. BSD 4.4 came out, and it didn't change this > part of the interface. There were boatloads of programs that were > inexpertly ported to Linux that exhibited cpu eating problems. Turns > out that they weren't robust enough to deal with the timeval stomping > interface. In time they created a bsd_select, which was what all user > progams used. I think it is possible to get the "new" linux behavior, > but I don't know how. Actually the Linux version of select checks a bit in the personality flag called "STICKY_TIMEOUTS". If this flag is set then the timeout value is not overwritten. Currently only the Sun SPARC port of Linux sets this bit, at least in Linux 2.0.36 that is. There is a version of select in libbsd.a which basically copies the timeout to a local variable and calls the Linux native select. So only the local copy gets altered leaving the original passed in version intact. You need to link against libbsd.a to get this behaviour. Speaking of this, I wonder what FreeBSD when running Linux binaries under emulation? Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 21:59:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01625 for freebsd-current-outgoing; Sun, 13 Dec 1998 21:59:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (76-sweet.camalott.com [208.239.153.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01618 for ; Sun, 13 Dec 1998 21:59:24 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id XAA18140; Sun, 13 Dec 1998 23:59:13 -0600 (CST) (envelope-from joelh) To: Mark Huizer Cc: current@FreeBSD.ORG Subject: Re: ^@^@^@^@^@^@^@ (empty pages) in NFS served file. References: <19981213235615.A12800@ariel.xaa.iae.nl> From: Joel Ray Holveck Date: 13 Dec 1998 23:59:11 -0600 In-Reply-To: Mark Huizer's message of "Sun, 13 Dec 1998 23:56:15 +0100" Message-ID: <864sqzmfgw.fsf@detlev.UUCP> Lines: 26 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to -current] > Hi! quite often I run into problems with NFS served files, containing a > page of ^@^@^@^@^@^@^@'s instead of actual data (mostly noticed in > textfiles). > After checking on the server, it seems the data is valid there. Touch'ing > it helps sometimes. > Environment is 2x FreeBSD current, running nfsv3 over udp, on machines > with softupdates enabled. > Anyone having the same trouble?? Yes, on a small shared mail directory. I assumed that it was equally corrupt on both client and server, but haven't verified that. All file access to the file I'm monitoring has been from the same client, with locking implements (not flock) to prevent simultanious writes. Same setup as you describe, although I'm about to move the server to -stable instead. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:09:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02647 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:09:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02642; Sun, 13 Dec 1998 22:09:46 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id RAA13463; Mon, 14 Dec 1998 17:09:42 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma013443; Mon, 14 Dec 98 17:09:15 +1100 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id RAA06013; Mon, 14 Dec 1998 17:09:15 +1100 From: "John Saunders" To: "FreeBSD current" Cc: Subject: RE: HEADS UP : laptop power-down change Date: Mon, 14 Dec 1998 17:09:15 +1100 Message-ID: <003001be2728$46d0d9a0$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199812112115.OAA04520@harmony.village.org> X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Now in the subcase that you're running FreeBSD on i386 with no monitor > : ROM, then I don't what's wrong with making '-h' and '-p' degenerate, > : ie, they both do the same thing: halt the system and cause a power off. > > Also agreed. > > For a power managed i386 system, I see no benefit from not mapping the > two to the same thing. As long as you provide a way for halting without powering down then I don't really care. I have a power managed machine and I _do_not_ want it to power down when I halt it. At least the "-p == power down" and "-h == halt" argument provides me with both the options I need. Your option removes the very option that I want, with no replacement mechanism. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:09:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02913 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:09:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02851 for ; Sun, 13 Dec 1998 22:09:57 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id WAA37519; Sun, 13 Dec 1998 22:09:35 -0800 (PST) To: Matthew Dillon cc: freebsd-current@FreeBSD.ORG Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? In-reply-to: Your message of "Sun, 13 Dec 1998 18:46:54 PST." <199812140246.SAA18566@apollo.backplane.com> Date: Sun, 13 Dec 1998 22:09:34 -0800 Message-ID: <37515.913615774@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is *very* annoying. Is there any particular reason why make clean > in /usr/src does not clean the entire source hierarchy? Probably because someone broke it and nobody noticed. It should indeed be possible to build with a r/o /usr/src just as it should be possible to get back to a /usr/obj containing little more than .depend files and directories if you do a make clean. How true that is at any given time depends on how thorough people have been in their Makefile hacking. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:21:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04326 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:21:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04310 for ; Sun, 13 Dec 1998 22:20:59 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:GTi2I6wiOOcWwPRCJKPSJZjyrhOPcecQ@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA28196; Mon, 14 Dec 1998 08:20:53 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:a9tf5ti29OxQUSn9GsNso7NN7Iz/ooNM@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id IAA61231; Mon, 14 Dec 1998 08:20:51 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812140620.IAA61231@greenpeace.grondar.za> To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Pet peeves (WAS: Re: cvs commit: src/etc Makefile) In-Reply-To: Your message of " Sun, 13 Dec 1998 18:13:37 EST." <199812132313.SAA13630@bb01f39.unx.sas.com> References: <199812132313.SAA13630@bb01f39.unx.sas.com> Date: Mon, 14 Dec 1998 08:20:50 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John W. DeBoskey" wrote: > And my pet peaves :-) > > 'make release' still seems to be installing a kerberos system. Fix coming with PAM completion. > telnetd has a bug somewhere in it's handling of the default banner: : > This is ONLY exhibitted under the krb version of telnetd, the the default > version. Evaluating fix... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:26:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05415 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:26:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05163 for ; Sun, 13 Dec 1998 22:25:49 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA07739 for ; Mon, 14 Dec 1998 07:25:44 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA18301 for ; Mon, 14 Dec 1998 07:25:43 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA06750 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:56 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:56 +0100 (CET) From: List User Message-Id: <199812140553.GAA06750@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Mark Huizer Subject: ^@^@^@^@^@^@^@ (empty pages) in NFS served file. Content-Type: text/plain; charset=us-ascii Received: by ariel.xaa.iae.nl (Postfix, from userid 1008) id 8FC283E15; Sun, 13 Dec 1998 23:56:15 +0100 (CET) To: questions Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <19981213235615.A12800@ariel.xaa.iae.nl> X-Mailer: Mutt 0.95i Delivered-To: vmailer-current@freebsd.org X-Uidl: c27d7a35533025cd46fb39c02ad333dd X-Loop: FreeBSD.ORG Mime-Version: 1.0 Cc: current Date: Sun, 13 Dec 1998 22:56:15 GMT Hi! quite often I run into problems with NFS served files, containing a page of ^@^@^@^@^@^@^@'s instead of actual data (mostly noticed in textfiles). After checking on the server, it seems the data is valid there. Touch'ing it helps sometimes. Environment is 2x FreeBSD current, running nfsv3 over udp, on machines with softupdates enabled. Anyone having the same trouble?? Mark -- Nice testing in little China... 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 Sun Dec 13 22:27:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05749 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:27:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05421 for ; Sun, 13 Dec 1998 22:26:18 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA07977 for ; Mon, 14 Dec 1998 07:26:08 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA18376 for ; Mon, 14 Dec 1998 07:26:07 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA08010 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:54:57 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:54:57 +0100 (CET) From: List User Message-Id: <199812140554.GAA08010@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: jack Subject: make install broken in /usr/sys/etc Content-Type: TEXT/PLAIN; charset=US-ASCII Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id UAA00551 for ; Sun, 13 Dec 1998 20:00:46 -0500 (EST) To: freebsd-current Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: Delivered-To: vmailer-current@freebsd.org X-Uidl: ef8303636079ca176e2d97366fba5638 X-Loop: FreeBSD.ORG Mime-Version: 1.0 Date: Mon, 14 Dec 1998 01:00:45 GMT Someone needs to tell /usr/src/etc/Makefile that rc.local went away, it still trys to install it. :( -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- 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 Sun Dec 13 22:27:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05945 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:27:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05544 for ; Sun, 13 Dec 1998 22:26:31 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08172 for ; Mon, 14 Dec 1998 07:26:24 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA18795 for ; Mon, 14 Dec 1998 07:26:22 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA05550 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:05 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:05 +0100 (CET) From: List User Message-Id: <199812140553.GAA05550@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Steve Passe Subject: Re: good new 3x laptop? Content-Type: text/plain; charset=us-ascii Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id OAA14463; Sun, 13 Dec 1998 14:00:59 -0700 (MST) To: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <199812132100.OAA14463@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 Delivered-To: vmailer-current@freebsd.org X-Uidl: 74deca19e02767b896a59285bdabefba X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: Your message of "Sun, 13 Dec 1998 10:32:34 PST." <199812131832.KAA00419@dingo.cdrom.com> Cc: mwlucas, freebsd-current Date: Sun, 13 Dec 1998 21:00:59 GMT Hi, > > I'm about to purchase a laptop to run FreeBSD on. With all this > > discussion about PAO and -current differences, I figured I'd better ask > > first. ;) > > > > Can anyone recommend a decent new laptop for FreeBSD? I want to run 3.x. > > I'm looking in the sub-$2000 range. > > Any of the Toshiba Satellite units in that range will give you good > service. How about a high end PII/14" display machine. I need to have 3.0-current development system for field compiles. A good docking station would be a plus. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:27:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05803 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:27:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05451 for ; Sun, 13 Dec 1998 22:26:20 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08044 for ; Mon, 14 Dec 1998 07:26:14 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA18396 for ; Mon, 14 Dec 1998 07:26:13 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA08910 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:36 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:36 +0100 (CET) From: List User Message-Id: <199812140555.GAA08910@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: "John W. DeBoskey" Subject: /etc/rc busted for legacy aout ldconfig setup Content-Type: text/plain; charset=US-ASCII Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id WAA14885 for freebsd-current@freebsd.org; Sun, 13 Dec 1998 22:22:57 -0500 (EST) (envelope-from jwd) To: freebsd-current Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812140322.WAA14885@bb01f39.unx.sas.com> X-Mailer: ELM [version 2.4ME+ PL38 (25)] Delivered-To: vmailer-current@freebsd.org X-Uidl: 4c0ea638a5255233c61c0359728e81be X-Loop: FreeBSD.ORG Mime-Version: 1.0 Date: Mon, 14 Dec 1998 03:22:57 GMT Hi, The following commit broke legacy ldconfig aout support: 1.161 Thu Dec 10 8:06:59 1998 UTC by jb Diffs to 1.160 Add a test for hw.machine == i386 before trying to run ldconfig for legacy aout support. The following conditional is wrong: if [ X"`sysctl hw.machine`" = X"i386" ]; then and needs to read: if [ X"`sysctl hw.machine | cut -d' ' -f2`" = X"i386" ]; then assuming the bruce filter doesn't mind a pipe in an 'if' statement. Anyone running a -current machine doing a 'make world' every day and still using any aout libraries will be affected by this. Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:27:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05908 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:27:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05538 for ; Sun, 13 Dec 1998 22:26:31 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08157 for ; Mon, 14 Dec 1998 07:26:22 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA18664 for ; Mon, 14 Dec 1998 07:26:21 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA06265 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:36 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:36 +0100 (CET) From: List User Message-Id: <199812140553.GAA06265@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Terry Lambert Subject: Re: PAO Integration? Content-Type: text/plain; charset=US-ASCII Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA09407; Sun, 13 Dec 1998 15:03:49 -0700 (MST) To: imp (Warner Losh) Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812132203.PAA09407@usr09.primenet.com> X-Mailer: ELM [version 2.4 PL25] Delivered-To: vmailer-current@freebsd.org X-Uidl: 6a5fa3f140d06074a49b83126e445f28 X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: <199812110109.SAA65255@harmony.village.org> from "Warner Losh" at Dec 10, 98 06:09:50 pm Cc: mike, y-nakaga, mark, current Date: Sun, 13 Dec 1998 22:03:48 GMT > : > > shutdown -h. What is wrong with this? > : > > : > It is wrong. > > Why? Traditionally Unix hasn't run on hardware that has software > power off. Who can say what traditional unix is when the hardware has > a new feature? The AT&T 3B2 I uses to use had soft power-off... to get UNIX hardware old than that, you'd need to use a VAX. The VAX at the Univeristy of Utah at the time I was there could switch off its UPS; it didn't normally do this, of course, but the possibility was there. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:26:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05629 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:26:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05324 for ; Sun, 13 Dec 1998 22:26:08 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA07913 for ; Mon, 14 Dec 1998 07:26:01 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA18355 for ; Mon, 14 Dec 1998 07:26:00 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA08973 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:39 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:39 +0100 (CET) From: List User Message-Id: <199812140555.GAA08973@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Peter Jeremy Subject: Re: panic: getnewbuf inconsistent EMPTY queue in 3.0-RELEASE Received: by border.alcanet.com.au id <40406>; Mon, 14 Dec 1998 15:07:29 +1100 To: freebsd-current Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <98Dec14.150729est.40406@border.alcanet.com.au> Delivered-To: vmailer-current@freebsd.org X-Uidl: 46d110033e32e564767593b49f09054a X-Loop: FreeBSD.ORG Date: Mon, 14 Dec 1998 04:07:58 GMT On Fri Dec 4 07:47:27 1998, I wrote: >I've just upgraded a Dell OptiPlex GXi from 32MB to 96MB. When I >increase MAXUSERS from 20 to 40 and SEMMNU from 350 to 1000, the >system panics `getnewbuf: inconsistent EMPTY queue, qindex=0' >immediately after the message `changing root device to wd0s1a'. I've managed to track this down to a bug in the handling of SysV semaphore undo structures when non-default SEMxxx values are used. Look up kern/9068 for details. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 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 Sun Dec 13 22:31:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07180 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:31:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07036 for ; Sun, 13 Dec 1998 22:31:24 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08979 for ; Mon, 14 Dec 1998 07:27:39 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19389 for ; Mon, 14 Dec 1998 07:27:38 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA08425 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:16 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:16 +0100 (CET) From: List User Message-Id: <199812140555.GAA08425@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Matthew Dillon Subject: Re: inetd: realloc/free bug Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA07846; Sun, 13 Dec 1998 18:08:31 -0800 (PST) (envelope-from dillon) To: Terry Lambert Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <199812140208.SAA07846@apollo.backplane.com> References: <199812132244.PAA10383@usr09.primenet.com> Delivered-To: vmailer-current@freebsd.org X-Uidl: 286bceb955549236b6e1d1cad241ea38 X-Loop: FreeBSD.ORG Cc: archie, jwd, freebsd-current Date: Mon, 14 Dec 1998 02:08:31 GMT I think there's some confusion here: The reason there is a timeout on the select has nothing to do with signals interrupting system calls. We don't care about that case - it's irrelevant. The only reason there is a timeout on the select is to handle the case where a signal occurs just *BEFORE* select() is entered where the signal function adds a file descriptor to the mask set. If this case occurs, the select() will wind up waiting on a mask set that does not contain the new descriptor thus possibly resulting in an infinite wait. That is the *SOLE REASON* why there is a timeout on the select. As I have said repeatedly: If someone does a read of the code and can guarentee that none of the signal functions *add* a descriptor to the mask set, we can remove the timeout entirely. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) :> :> If you put a time limit on select(), it doesn't matter if there is a :> :> race condition there. How does select() cause a signal to be missed ? :> : :> :Well, sure.. :-) but then you don't service signals in real time :> :and spend extra cycles timing out all the time. :> :> You do serve signals in real time... the signals are *unmasked* during :> the select() :-) ... the race condition is that the unmasked signal may :> cause the descriptor set to be changed just prior to the select() call, :> causing select() to wait forever. The timeout on the select() handles :> the race condition without effecting the realtime delivery of signals. : :You should just use siginterrupt(3) to make sure select restarts, and be :done with it. : :If you need to interrupt the select after setting system call restart :behaviour, then use a longjmp from the signal handler after setting a :volatile flag so that the flag can be tested in the "else" case of :the setjmp() call. : :If the call is restarted, you don't have to worry about the timer, it :will do the right thing, and you won't get an EINTR that you con't know :how to handle the masks around. : :If you don't like siginterrupt(3), and want to use the non-Berkeley :signal mechanisms for setting call restart behaviour, then be my :guest and write 30 or 40 lines of POSIX expecting code instead. : :The siginterrupt(2) system call first appeared in BSD 4.1c; the :current code uses POSIX sigaction(2); someone might want to correct :the siginterrupt(3) man page... : : : 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 : 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 Sun Dec 13 22:31:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07287 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:31:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07123 for ; Sun, 13 Dec 1998 22:31:33 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA09039 for ; Mon, 14 Dec 1998 07:27:43 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19401 for ; Mon, 14 Dec 1998 07:27:41 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA06492 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:44 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:44 +0100 (CET) From: List User Message-Id: <199812140553.GAA06492@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Matthew Jacob Subject: (Re: Can't access tapes with scsi_sa.c r1.7) (LONG) Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: mjacob@feral.com Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id OAA11909; Sun, 13 Dec 1998 14:25:39 -0800 To: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: Delivered-To: vmailer-current@freebsd.org X-Uidl: 47416de1548c713ab7084a9940b58d4a X-Loop: FreeBSD.ORG Mime-Version: 1.0 X-Sender: mjacob@feral-gw In-Reply-To: <199812131103.MAA00577@peedub.muc.de> Cc: Greg Lehey , FreeBSD current users Date: Sun, 13 Dec 1998 22:25:39 GMT Well, I've been looking over this, and a preliminary check seems to indicate to me that the driver is, in fact, doing what it is supposed to do. Now, wait, don't start throwing things yet.. :-) The simple fix for all of you is to explicitly set variable mode (mt blocksize 0) on your tape device *if you want it to be in variable record length mode*, but see. If you're in fixed block mode (the default now that a lot of these drives show up as, but see below), and you issue a read that doesn't match the blocksize for that device, you get an ILI (incorrect length indicator) error- no data was actually transferred. I went back to the 1.6 version, added some debugging, and ran on a 8505 the same sorts of tests that Greg had done. The test here is you have a header record, say, of 512 bytes, followed by a filemark, and you read it with a 1k read from user space. Here's what had occurred: scsi_sa, 1.6: a) The device is in fixed block mode, but the tape driver is ignorant of this. This is because the old test at samount time was to see whether the maximum block size supported equaled the minimum blocksize, not what the actual current blocksize is. b) Thus, a read of 1k bytes gets shipped out as a variable mode read- not as a fixed length read. c) This gets returned, like a variable length read should, as having read 512 bytes of 1024 requested. This gets propagated back to the user application as a short read. All is good, if frightening because reality and driver state aren't coordinated, but.... !!!!!!!!The results of what occurs when you *write* such a device are not entirely predictable. Some tape devices, like the Exabyte 85XX and probably the Archive DAT drives, really don't care what 'mode' they're in but simply key off of each WRITE command as to what the actual record size being requested is. Other tape devices, e.g. the Exabyte 8200, get really bothered and just cannot cope. The main point of the 1.6 to 1.7 change was to address this. scsi_sa, 1.7: a) The device is in fixed block mode, and the tape driver is now cognizant of this because it keys off of what the actual current blocksize for the device is. b) A read of 1k bytes gets turned into a fixed length read of 1 record (1024 bytes) and shipped down to the drive- but the drive bounces the read because the only record available is the 512 byte record- and no data is actually then transferred and an error is returned to the user application. This is, in fact, the desired behaviour for fixed length record operations. Well, you *could* argue that SILI should be set (which supresses this error), but I would assert that you should just be operating in variable record mode when you want read variably sized records. If you use SILI, people will forget that they're in fixed block mode and when they write tapes with what *they* think are variable sized records, they won't be, which will be a zoo for media interchange.... In any case, the take home lesson of the change between scsi_sa 1.6 and 1.7 is that a 'fix' to actually make the driver operate as it is supposed to violated the principle of least surprise and nailed some folks- Sorry! scsi_sa, 1.8: (NOT YET INTEGRATED) What was *planned* was that in response to several requests, the *real* default behaviour should very likely be to to put all tape devices (with the exception of some QIC devices) into variable block mode at samount time unless someone has explicitly set fixed record mode. Opinions? 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 Sun Dec 13 22:53:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06032 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:27:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05510 for ; Sun, 13 Dec 1998 22:26:27 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08097 for ; Mon, 14 Dec 1998 07:26:18 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA18409 for ; Mon, 14 Dec 1998 07:26:17 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA08924 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:36 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:36 +0100 (CET) From: List User Message-Id: <199812140555.GAA08924@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: John Birrell Subject: Re: /etc/rc busted for legacy aout ldconfig setup Content-Type: text/plain; charset=US-ASCII Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id OAA01662; Mon, 14 Dec 1998 14:40:13 +1100 (EST) (envelope-from jb) To: jwd (John W. DeBoskey) Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812140340.OAA01662@cimlogic.com.au> X-Mailer: ELM [version 2.4ME+ PL40 (25)] Delivered-To: vmailer-current@freebsd.org X-Uidl: 81509ea83f05d4ab18e74758e5b12d02 X-Loop: FreeBSD.ORG Mime-Version: 1.0 Cc: freebsd-current In-Reply-To: <199812140322.WAA14885@bb01f39.unx.sas.com> from "John W. DeBoskey" at "Dec 13, 98 10:22:57 pm" Date: Mon, 14 Dec 1998 03:40:13 GMT John W. DeBoskey wrote: > 1.161 Thu Dec 10 8:06:59 1998 UTC by jb > Diffs to 1.160 > > Add a test for hw.machine == i386 before trying to run ldconfig for > legacy aout support. > > > The following conditional is wrong: > > if [ X"`sysctl hw.machine`" = X"i386" ]; then There's a -n in rev 1.162. Please check the _current_ sources before reporting this sort of thing. 1.162 is dated 1998/12/11 08:25:12. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:54:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06061 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:27:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05678 for ; Sun, 13 Dec 1998 22:26:49 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08369 for ; Mon, 14 Dec 1998 07:26:38 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19178 for ; Mon, 14 Dec 1998 07:26:37 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA09281 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:52 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:52 +0100 (CET) From: List User Message-Id: <199812140555.GAA09281@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Matthew Dillon Subject: Totally illegal declaration/check in i386/i386/busdma_machdep.c Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA26641; Sun, 13 Dec 1998 21:29:30 -0800 (PST) (envelope-from dillon) To: freebsd-current Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <199812140529.VAA26641@apollo.backplane.com> Delivered-To: vmailer-current@freebsd.org X-Uidl: ee3c7bdc33b6650e037137b89ee4214f X-Loop: FreeBSD.ORG Date: Mon, 14 Dec 1998 05:29:30 GMT GCC warning expected? I'm sorry, but this is *illegal*. Totally illegal. nextpaddr can be legally destroyed on each loop by the compiler. I know what the author was trying to do, but he's wrong. I'm fixing this. (from i386/i386/busdma_machdep.c) do { bus_size_t size; vm_offset_t nextpaddr; /* GCC warning expected */ paddr = pmap_kextract(vaddr); size = PAGE_SIZE - (paddr & PAGE_MASK); if (size > buflen) size = buflen; ... } else if (paddr == nextpaddr) { sg->ds_len += size; ... nextpaddr = paddr + size; buflen -= size; } while (buflen > 0); Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-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 Sun Dec 13 22:54:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06182 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05699 for ; Sun, 13 Dec 1998 22:26:52 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08413 for ; Mon, 14 Dec 1998 07:26:42 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19188 for ; Mon, 14 Dec 1998 07:26:40 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA07758 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:54:45 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:54:45 +0100 (CET) From: List User Message-Id: <199812140554.GAA07758@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: "Daniel O'Connor" Subject: Re: mformat in free(): warning: junk pointer, too high to make s Content-Type: text/plain; charset=us-ascii Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA17891; Mon, 14 Dec 1998 10:51:24 +1030 (CST) (envelope-from doconnor@gsoft.com.au) To: Archie Cobbs Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 8bit Organization: Private News Host Precedence: bulk Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD Delivered-To: vmailer-current@freebsd.org X-Uidl: 353c14eeae0ccfb23460799b86435c20 X-Loop: FreeBSD.ORG Mime-Version: 1.0 X-Priority: 3 (Normal) Cc: dg, current, vallo, eivind, jkh, sthaug In-Reply-To: <199812112008.MAA28016@bubba.whistle.com> Date: Mon, 14 Dec 1998 00:21:15 GMT On 11-Dec-98 Archie Cobbs wrote: > Looks like the same idea but much more complete (and probably faster, > better tested, etc..) I'd love to break this out into it's own library > in src/lib. I think lots of people would find it useful. What kind of > backlash could I expect? :-) Probably a large one of the variety 'why did it take so long?' :) Sounds like an EXCELLENT idea! > The other libraries look interesting too: "heap", "tree", "logging", etc. Yes, indeedy :) --- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:54:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06125 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:27:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05714 for ; Sun, 13 Dec 1998 22:26:55 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08442 for ; Mon, 14 Dec 1998 07:26:44 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19199 for ; Mon, 14 Dec 1998 07:26:43 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA08368 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:12 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:12 +0100 (CET) From: List User Message-Id: <199812140555.GAA08368@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Matthew Dillon Subject: Re: make install broken in /usr/sys/etc Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA07770; Sun, 13 Dec 1998 18:01:22 -0800 (PST) (envelope-from dillon) To: jack Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <199812140201.SAA07770@apollo.backplane.com> References: Delivered-To: vmailer-current@freebsd.org X-Uidl: 1e5871092f28d88f7d074fd24d56281f X-Loop: FreeBSD.ORG Cc: freebsd-current Date: Mon, 14 Dec 1998 02:01:22 GMT Fixed! -Matt : :Someone needs to tell /usr/src/etc/Makefile that rc.local went :away, it still trys to install it. :( : :-------------------------------------------------------------------------- :Jack O'Neill Systems Administrator / Systems Analyst :jack@germanium.xtalwind.net Crystal Wind Communications, Inc. : Finger jack@germanium.xtalwind.net for my PGP key. : PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD : enriched, vcard, HTML messages > /dev/null :-------------------------------------------------------------------------- : : : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-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 Sun Dec 13 22:54:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06204 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05781 for ; Sun, 13 Dec 1998 22:27:00 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08498 for ; Mon, 14 Dec 1998 07:26:49 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19215 for ; Mon, 14 Dec 1998 07:26:47 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA08688 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:27 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:27 +0100 (CET) From: List User Message-Id: <199812140555.GAA08688@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Matthew Dillon Subject: 'make clean' in /usr/src does not cleanup .o's or shared libs ? Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA18566; Sun, 13 Dec 1998 18:46:54 -0800 (PST) (envelope-from dillon) To: freebsd-current Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <199812140246.SAA18566@apollo.backplane.com> Delivered-To: vmailer-current@freebsd.org X-Uidl: b11a4e27a0d368545552a49dcef31635 X-Loop: FreeBSD.ORG Date: Mon, 14 Dec 1998 02:46:54 GMT I'm trying to do a buildworld with /usr/src mounted read-only (via NFS). The buildworld has died several times trying to remove .o files, binaries, and libraries (*.so.*) from /usr/src that happened to be hanging around. Ok, I say... cd /usr/src on the physical machine and 'make clean'. Only problem is it doesn't work... it does not recursive through the entire source hierarchy. For example, make clean in /usr/src does not bother recursing through /usr/src/bin, /usr/src/sbin, /usr/src/gnu, etc... It is *very* annoying. Is there any particular reason why make clean in /usr/src does not clean the entire source hierarchy? Also, having to restart the buildworld from scratch every time it blows up and exits is also quite annoying. It would be nice to have a 'rebuildworld' target that uses dot files similar to the way bsd.port.mk uses them to pick up where it left off. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-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 Sun Dec 13 22:54:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06250 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05782 for ; Sun, 13 Dec 1998 22:27:00 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08522 for ; Mon, 14 Dec 1998 07:26:51 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19219 for ; Mon, 14 Dec 1998 07:26:49 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA06687 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:53 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:53 +0100 (CET) From: List User Message-Id: <199812140553.GAA06687@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Terry Lambert Subject: Re: inetd: realloc/free bug Content-Type: text/plain; charset=US-ASCII Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA10799; Sun, 13 Dec 1998 15:53:54 -0700 (MST) To: archie (Archie Cobbs) Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812132253.PAA10799@usr09.primenet.com> X-Mailer: ELM [version 2.4 PL25] Delivered-To: vmailer-current@freebsd.org X-Uidl: c91810ec79230b03092ce6e89e303611 X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: <199812111940.LAA27652@bubba.whistle.com> from "Archie Cobbs" at Dec 11, 98 11:40:58 am Cc: peter.edwards, dillon, jwd, freebsd-current Date: Sun, 13 Dec 1998 22:53:54 GMT > I guess I was thinking in terms of the event library model; that is, > you don't handle the signal event in the signal handler (because in > general the event handler could call malloc(), etc), but rather you > simply set a flag (call it "signalFlag"). > > The race condition is getting a signal between the first and second > lines below: > > sigprocmask(SIG_UNBLOCK ..) /* unblock signals */ > r = select(...) /* wait for event */ > sigprocmask(SIG_BLOCK ..) /* block signals */ > > if (signalFlag || r > 0) { > ... /* handle event(s) */ > } > > But there are probably smarter ways to do it than this. Yes. Don't block signals, use a setjmp for the select, and choose system call restart behaviour. The race you are concerned with is a signal occurring before the select starts, and the resulting EINTR. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:54:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06278 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05791 for ; Sun, 13 Dec 1998 22:27:01 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08586 for ; Mon, 14 Dec 1998 07:26:54 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19250 for ; Mon, 14 Dec 1998 07:26:52 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA08834 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:33 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:33 +0100 (CET) From: List User Message-Id: <199812140555.GAA08834@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Brett Taylor Subject: Navigator problem in -current Content-Type: TEXT/PLAIN; charset=US-ASCII Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id UAA13285 for ; Sun, 13 Dec 1998 20:14:21 -0700 (MST) (envelope-from brett@peloton.physics.montana.edu) To: freebsd-current Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: Delivered-To: vmailer-current@freebsd.org X-Uidl: 7cbe23c1d1aca1526f702eefa144b99a X-Loop: FreeBSD.ORG Mime-Version: 1.0 Date: Mon, 14 Dec 1998 03:14:21 GMT Hi, I moved to -CURRENT on Dec 10th. I pkg_deleted all my old -STABLE ports and reinstalled from scratch so everything would be ELF. Problem - I can't get Netscape Navigator to run. I saw this mentioned before in -current so I scanned through the archive and the recommended fix was to copy an aout version of libXt.so.6.0 into /usr/X11R6/lib/aout and then do an ldconfig -aout -m /usr/X11R6/lib/aout When I copy this over from my -STABLE machine and try this I get: monkey: {5} ldconfig -aout -m /usr/X11R6/lib/aout ldconfig: /var/run/ld.so.hints: No such file or directory Do I need to do something else in addition to this? Brett ****************************************************************** Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ On the eve of his 21st birthday, he set out on his own He was 30 years and runnin' when he found his way back home Ridin' a storm across the mountains and an achin' in his heart Said he came to turn the pages and to make a brand new start 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 Sun Dec 13 22:54:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06193 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05817 for ; Sun, 13 Dec 1998 22:27:04 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08606 for ; Mon, 14 Dec 1998 07:26:56 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19259 for ; Mon, 14 Dec 1998 07:26:54 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA05438 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:00 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:00 +0100 (CET) From: List User Message-Id: <199812140553.GAA05438@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Nate Williams Subject: Re: minor vipw/pwd_mkdb changes commited Content-Type: text/plain; charset=us-ascii Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA06177; Sun, 13 Dec 1998 13:48:04 -0700 To: Matthew Dillon Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812132048.NAA06177@mt.sri.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid References: <199812130203.SAA14359@apollo.backplane.com> Delivered-To: vmailer-current@freebsd.org X-Uidl: 00a9774843d396711f353f1597ddbc0a X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: <199812130203.SAA14359@apollo.backplane.com> Cc: freebsd-current Date: Sun, 13 Dec 1998 20:48:04 GMT > I've made a few minor fixes to vipw and pwd_mkdb to handle a > master.passwd race condition (note: there are no security issues > with the race). I *think* I fixed this is Auguest already, didn't I? nate 1998/07/16 10:18:30 PDT Modified files: usr.sbin/pw edgroup.c fileupd.c pw.c Log: Fix race condition in pw caused by multiple instances of pwd_mkdb being run at the same time. Notes: The fileupdate function is still somewhat broken. Instead of returning a failure code if it can't modify the original file it renames the .new file and continues as though nothing is wrong. This will cause the lock on the original file to be lost and could lead to a similar race condition. I left that portion of the code alone since I feel that the maintainer of the code would have a better concept of how he wants to handle errors in that function than I do. PR: bin/6787 Submitted by: Craig Spannring If not, will these changes conflict with the above changes? Nate 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 Sun Dec 13 22:54:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06234 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05836 for ; Sun, 13 Dec 1998 22:27:06 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08626 for ; Mon, 14 Dec 1998 07:26:57 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19263 for ; Mon, 14 Dec 1998 07:26:56 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA06522 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:46 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:46 +0100 (CET) From: List User Message-Id: <199812140553.GAA06522@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Terry Lambert Subject: Re: HEADS UP : laptop power-down change Content-Type: text/plain; charset=US-ASCII Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA10207; Sun, 13 Dec 1998 15:35:42 -0700 (MST) To: imp (Warner Losh) Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812132235.PAA10207@usr09.primenet.com> X-Mailer: ELM [version 2.4 PL25] Delivered-To: vmailer-current@freebsd.org X-Uidl: 97cda81a83e4da1c5aedeaec8c9de282 X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: <199812110422.VAA65796@harmony.village.org> from "Warner Losh" at Dec 10, 98 09:22:15 pm Cc: mike, current Date: Sun, 13 Dec 1998 22:35:42 GMT > : No. RB_POWEROFF and RB_HALT have very different meanings. The PC > : doesn't have a useful means for getting back to the resident firmware, > : but many other systems do. That's what RB_HALT is meant to do, while > : RB_POWEROFF is meant to power the system down. The two are mutually > : exclusive. > > I know... halt should turn the machine off. Halt should trigger the halt trap, which on an Alpha means putting you into the boot monitor. For the PC, it means putting you in a state where you can hit "DEL" to get the setup, or "CTRL-A" to get into the Adaptec BIOS configuration, etc.. It's not FreeBSD's fault that (most) PC hardware is too stupid to have a boot-ROM that lets you configure things before triggering the boot loader, unless you overrice the default behaviour with keystrokes while it's pounding away at things. Also, I think the correct flag is "-x", not "-p", from a historical (Sony NeWS, NeXTStep, and A/UX, et. al.). 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:54:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06323 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05971 for ; Sun, 13 Dec 1998 22:27:24 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08782 for ; Mon, 14 Dec 1998 07:27:11 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19296 for ; Mon, 14 Dec 1998 07:27:09 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA08586 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:21 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:21 +0100 (CET) From: List User Message-Id: <199812140555.GAA08586@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Jacob Bohn Lorensen Subject: Re: make aout-to-world-build problem Received: (from jablo@localhost) by pippin.jblhome.ping.dk (8.9.1/8.9.1) id CAA11210; Mon, 14 Dec 1998 02:24:52 +0100 (CET) (envelope-from jacob) To: Chris Timmons Sender: owner-freebsd-current@FreeBSD.ORG X-Authentication-Warning: pippin.jblhome.ping.dk: jablo set sender to jacob using -f Organization: Private News Host Precedence: bulk Lines: 32 Message-ID: <87g1ajikhc.fsf@pippin.jblhome.ping.dk> X-Mailer: Gnus v5.5/Emacs 20.2 References: Delivered-To: vmailer-current@freebsd.org X-Uidl: 02112e04ed22f4057d641549dea91deb X-Loop: FreeBSD.ORG In-Reply-To: Chris Timmons's message of Tue, 8 Dec 1998 15:02:16 -0800 (PST) Cc: Brett Taylor , freebsd-current Date: Mon, 14 Dec 1998 01:24:31 GMT Chris Timmons writes: > make aout-to-elf-build > make aout-to-elf-install > I just successfully did it from a 2.2.7 system. Make sure you start with > a real -current /usr/src and have plenty of room 300+MB for /usr/obj. I did the same thing about a week ago. I had two problems, one of which I am sure was a pilot error (I did it with at umask of 007 so only root was able to run aout programs after the upgrade as all the lib/aout directories were created with only user and group read/execute permissions). The other (non pilot-error) was that I had to do a find / -name '*.a' -o -name '*.so.*' | xargs chflags noschg before makeing aout-to-elf-install otherwise the upgrade process wasnt able to move the aout libraries. > On Tue, 8 Dec 1998, Brett Taylor wrote: > > Hi, > > I've been trying to do a make aout-to-world-build w/ -current sources from > > that I cvsup'ed on the 6th of Dec. I am attempting to upgrade from 2.2.8 > > to -current. -- Jacob Lorensen; Mosebuen 33, 1.; DK-2820 Gentofte, Denmark; +45 39560401 PGPid: 0x752EB4DE Fingerprint: F609A0BAFF393EA904F7-F344680F8EED752EB4DE 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 Sun Dec 13 22:54:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06298 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05975 for ; Sun, 13 Dec 1998 22:27:23 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08805 for ; Mon, 14 Dec 1998 07:27:14 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19306 for ; Mon, 14 Dec 1998 07:27:12 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA05794 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:15 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:15 +0100 (CET) From: List User Message-Id: <199812140553.GAA05794@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Johan Granlund Subject: Re: Can't access tapes with scsi_sa.c r1.7 Content-Type: TEXT/PLAIN; charset=US-ASCII Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.1/8.9.1) with ESMTP id WAA02579; Sun, 13 Dec 1998 22:11:49 +0100 (CET) (envelope-from johan@granlund.nu) To: Matthew Jacob Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: Delivered-To: vmailer-current@freebsd.org X-Uidl: fc9d0e6583f27ad6f7e301803f28a3af X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: Cc: Greg Lehey , FreeBSD current users Date: Sun, 13 Dec 1998 21:11:49 GMT On Sun, 13 Dec 1998, Matthew Jacob wrote: > > I did writes to EOT, but not with dump. Then it's probally fixed as it was a kernel panic and not dump that cored. /Johan > > > On Sat, 12 Dec 1998, Matthew Jacob wrote: > > > > > > > > Yes, that'd be my change. Whups! It worked for me! Could you build a > > > > And it also works for me. Exabyte EXB-8200 and Adaptec 2940UW. Both dump > > and restore of selected files. This is with variable blocksize. > > > > Matthew: Did you test making a fulltape dump (until EOT) that caused a > > kernel panic (kernel from Nov 7) for me? I can't test this easily now > > beqause my large datadisk finally failed. I should get a replacement > > sometime next week. Then we will see if a full multitape restore works:) > > > > /Johan > > > > > CAMDEBUG kernel, use camcontrol to turn on debugging for that device and > > > do whatever it is you did and send me the output, or send me what it is > > > you tried first? I'll be in my shop tomorrow morning to work on this! > > > Sorry! > > > > > > > > > > > > > > > > > > > > > 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 > > > > > 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 Sun Dec 13 22:54:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06360 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06040 for ; Sun, 13 Dec 1998 22:27:31 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08844 for ; Mon, 14 Dec 1998 07:27:21 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19324 for ; Mon, 14 Dec 1998 07:27:19 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA09113 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:46 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:46 +0100 (CET) From: List User Message-Id: <199812140555.GAA09113@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Julian Elischer Subject: Re: PAO Integration? Content-Type: TEXT/PLAIN; charset=US-ASCII Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdK12406; Mon Dec 14 04:31:23 1998 To: Terry Lambert Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: Delivered-To: vmailer-current@freebsd.org X-Uidl: f9822ba8ee310d24d35035685d495697 X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: <199812132203.PAA09407@usr09.primenet.com> Cc: Warner Losh , mike, y-nakaga, mark, current Date: Mon, 14 Dec 1998 04:31:20 GMT Archie and I added dthe RB_POWEROFF flag to allow our Interjets to turn off the power when requested. In other situations we do not want to remove power, but rather halt so that control is then handed to the H/W watchdog, which will do a full reset of everything. I was also thinking of laptops whan I added this. (see the commit message) We'd be really thrilled if someone changed the semantics out from under us...... RB_POWEROFF does exactly that. RB_HALT does NOT do that. The processor either executes a HALT instrauction, or enters a type loop. Alternatively it might go to a firmware monitor, but we don't have that. what the 'shutdown' instruction does is arguable, but my personal feel is that it should require an argument to make it power off. Just like it requires an argument to make it reboot. On Sun, 13 Dec 1998, Terry Lambert wrote: > > : > > shutdown -h. What is wrong with this? > > : > > > : > It is wrong. > > > > Why? Traditionally Unix hasn't run on hardware that has software > > power off. Who can say what traditional unix is when the hardware has > > a new feature? > > The AT&T 3B2 I uses to use had soft power-off... to get UNIX hardware > old than that, you'd need to use a VAX. The VAX at the Univeristy > of Utah at the time I was there could switch off its UPS; it didn't > normally do this, of course, but the possibility was there. > > > 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 > 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 Sun Dec 13 22:55:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06354 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06078 for ; Sun, 13 Dec 1998 22:27:39 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08885 for ; Mon, 14 Dec 1998 07:27:26 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19347 for ; Mon, 14 Dec 1998 07:27:24 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA09116 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:46 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:46 +0100 (CET) From: List User Message-Id: <199812140555.GAA09116@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Julian Elischer Subject: Re: if_sppp is BROKEN!!! Content-Type: TEXT/PLAIN; charset=US-ASCII Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdO12550; Mon Dec 14 04:39:41 1998 To: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: Delivered-To: vmailer-current@freebsd.org X-Uidl: 1b358c9d32d6f0710962374315794de3 X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: <8711.913504842@critter.freebsd.dk> Cc: current, isdn Date: Mon, 14 Dec 1998 04:39:38 GMT how about porting the whole shebang to whistle's 'streams' replacement.. we could probably supply the frame relay and ppp packetizer nodes along with the framework and tools... s On Sun, 13 Dec 1998, Poul-Henning Kamp wrote: > > I think I have finally found out what the problem is with the state > machine in the if_sppp implementation. Whoever wrote the implementation > didn't carefully consider the inter-layer calls tls and tlf. > > If one applies a lot of patches like this one: > > case STATE_OPENED: > - (cp->tld)(sp); > sp->rst_counter[cp->protoidx] = 0; > sppp_cp_change_state(cp, sp, STATE_STOPPING); > + (cp->tld)(sp); > goto sta; > break; > > Then things actually start to make sense... > > The problem is that the tld and tlf functions often just call the > pp_up and pp_down routines directly, and therefore most if not all > of the expected up and down events happen in the previous state > as opposed to the next state. > > Flipping it around like I have done above, on the other hand, may > not be a good idea either, since it means we can nest another layer > on the stack and get somewhat confused on the way down. > > It is quite obvious that this will need some more work to sort out, > anybody interested in participating ? > > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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 Sun Dec 13 22:55:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06290 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06093 for ; Sun, 13 Dec 1998 22:27:38 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08899 for ; Mon, 14 Dec 1998 07:27:29 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19363 for ; Mon, 14 Dec 1998 07:27:27 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA06551 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:48 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:48 +0100 (CET) From: List User Message-Id: <199812140553.GAA06551@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Terry Lambert Subject: Re: inetd: realloc/free bug Content-Type: text/plain; charset=US-ASCII Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA10383; Sun, 13 Dec 1998 15:44:29 -0700 (MST) To: dillon (Matthew Dillon) Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812132244.PAA10383@usr09.primenet.com> X-Mailer: ELM [version 2.4 PL25] Delivered-To: vmailer-current@freebsd.org X-Uidl: 5544d48168888e07a011e920f4adf1ba X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: <199812110659.WAA35073@apollo.backplane.com> from "Matthew Dillon" at Dec 10, 98 10:59:07 pm Cc: archie, jwd, freebsd-current Date: Sun, 13 Dec 1998 22:44:29 GMT > :> If you put a time limit on select(), it doesn't matter if there is a > :> race condition there. How does select() cause a signal to be missed ? > : > :Well, sure.. :-) but then you don't service signals in real time > :and spend extra cycles timing out all the time. > > You do serve signals in real time... the signals are *unmasked* during > the select() :-) ... the race condition is that the unmasked signal may > cause the descriptor set to be changed just prior to the select() call, > causing select() to wait forever. The timeout on the select() handles > the race condition without effecting the realtime delivery of signals. You should just use siginterrupt(3) to make sure select restarts, and be done with it. If you need to interrupt the select after setting system call restart behaviour, then use a longjmp from the signal handler after setting a volatile flag so that the flag can be tested in the "else" case of the setjmp() call. If the call is restarted, you don't have to worry about the timer, it will do the right thing, and you won't get an EINTR that you con't know how to handle the masks around. If you don't like siginterrupt(3), and want to use the non-Berkeley signal mechanisms for setting call restart behaviour, then be my guest and write 30 or 40 lines of POSIX expecting code instead. The siginterrupt(2) system call first appeared in BSD 4.1c; the current code uses POSIX sigaction(2); someone might want to correct the siginterrupt(3) man page... 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:55:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06390 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:29:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06111 for ; Sun, 13 Dec 1998 22:27:41 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08892 for ; Mon, 14 Dec 1998 07:27:27 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19358 for ; Mon, 14 Dec 1998 07:27:26 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA06605 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:50 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:50 +0100 (CET) From: List User Message-Id: <199812140553.GAA06605@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Terry Lambert Subject: Re: inetd: realloc/free bug Content-Type: text/plain; charset=US-ASCII Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA10383; Sun, 13 Dec 1998 15:44:29 -0700 (MST) To: dillon (Matthew Dillon) Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812132244.PAA10383@usr09.primenet.com> X-Mailer: ELM [version 2.4 PL25] Delivered-To: vmailer-current@freebsd.org X-Uidl: 99aca69af5a54152a8fb7035187d2c37 X-Loop: FreeBSD.ORG Mime-Version: 1.0 In-Reply-To: <199812110659.WAA35073@apollo.backplane.com> from "Matthew Dillon" at Dec 10, 98 10:59:07 pm Cc: archie, jwd, freebsd-current Date: Sun, 13 Dec 1998 22:44:29 GMT > :> If you put a time limit on select(), it doesn't matter if there is a > :> race condition there. How does select() cause a signal to be missed ? > : > :Well, sure.. :-) but then you don't service signals in real time > :and spend extra cycles timing out all the time. > > You do serve signals in real time... the signals are *unmasked* during > the select() :-) ... the race condition is that the unmasked signal may > cause the descriptor set to be changed just prior to the select() call, > causing select() to wait forever. The timeout on the select() handles > the race condition without effecting the realtime delivery of signals. You should just use siginterrupt(3) to make sure select restarts, and be done with it. If you need to interrupt the select after setting system call restart behaviour, then use a longjmp from the signal handler after setting a volatile flag so that the flag can be tested in the "else" case of the setjmp() call. If the call is restarted, you don't have to worry about the timer, it will do the right thing, and you won't get an EINTR that you con't know how to handle the masks around. If you don't like siginterrupt(3), and want to use the non-Berkeley signal mechanisms for setting call restart behaviour, then be my guest and write 30 or 40 lines of POSIX expecting code instead. The siginterrupt(2) system call first appeared in BSD 4.1c; the current code uses POSIX sigaction(2); someone might want to correct the siginterrupt(3) man page... 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:55:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06333 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:28:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06134 for ; Sun, 13 Dec 1998 22:27:43 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08919 for ; Mon, 14 Dec 1998 07:27:32 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19371 for ; Mon, 14 Dec 1998 07:27:31 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA09287 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:55:54 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:54 +0100 (CET) From: List User Message-Id: <199812140555.GAA09287@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: "John Saunders" Subject: RE: inetd: realloc/free bug Content-Type: text/plain; charset="iso-8859-1" X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id QAA05843 for ; Mon, 14 Dec 1998 16:47:31 +1100 To: "FreeBSD current" Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Importance: Normal Message-ID: <002f01be2725$3dab6af0$6cb611cb@saruman.scitec.com.au> X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Delivered-To: vmailer-current@freebsd.org X-Uidl: a388a55e70e8f5b4a7f5072b4b704fd8 X-Loop: FreeBSD.ORG X-Priority: 3 (Normal) Mime-Version: 1.0 In-Reply-To: <199812110722.AAA00650@harmony.village.org> Date: Mon, 14 Dec 1998 05:47:31 GMT > Linux implemented the timeval stomping version of select. It was the > first OS to do this. At the time they claimed that BSD 4.4 would be > doing this and that they were going to be compatible with that, plus > it was listed as a bug. BSD 4.4 came out, and it didn't change this > part of the interface. There were boatloads of programs that were > inexpertly ported to Linux that exhibited cpu eating problems. Turns > out that they weren't robust enough to deal with the timeval stomping > interface. In time they created a bsd_select, which was what all user > progams used. I think it is possible to get the "new" linux behavior, > but I don't know how. Actually the Linux version of select checks a bit in the personality flag called "STICKY_TIMEOUTS". If this flag is set then the timeout value is not overwritten. Currently only the Sun SPARC port of Linux sets this bit, at least in Linux 2.0.36 that is. There is a version of select in libbsd.a which basically copies the timeout to a local variable and calls the Linux native select. So only the local copy gets altered leaving the original passed in version intact. You need to link against libbsd.a to get this behaviour. Speaking of this, I wonder what FreeBSD when running Linux binaries under emulation? Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ 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 Sun Dec 13 22:55:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06381 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:29:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06138 for ; Sun, 13 Dec 1998 22:27:46 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08932 for ; Mon, 14 Dec 1998 07:27:34 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19375 for ; Mon, 14 Dec 1998 07:27:32 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA06820 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 06:53:58 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:58 +0100 (CET) From: List User Message-Id: <199812140553.GAA06820@doorway.home.lan> To: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: "John W. DeBoskey" Subject: Re: cvs commit: src/etc Makefile Content-Type: text/plain; charset=US-ASCII Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id SAA13630 for freebsd-current@freebsd.org; Sun, 13 Dec 1998 18:13:37 -0500 (EST) (envelope-from jwd) To: freebsd-current Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812132313.SAA13630@bb01f39.unx.sas.com> X-Mailer: ELM [version 2.4ME+ PL38 (25)] Delivered-To: vmailer-current@freebsd.org X-Uidl: 9a32f5ee0df05d0c5a7bc68ed44354b0 X-Loop: FreeBSD.ORG Mime-Version: 1.0 Date: Sun, 13 Dec 1998 23:13:37 GMT From: Eivind Eklund Subject: Re: cvs commit: src/etc Makefile Eivind said: > On Sun, Dec 13, 1998 at 02:44:23PM +0200, Mark Murray wrote: > > Dag-Erling Smorgrav wrote: > > > Better, but not sufficient; it assumes that the user checks 'ls > > > /etc/*sample' after make world. For such a feature to have any effect, > > > you have to somehow warn the user about missing files, e.g. by mailing > > > a list to root. > > > > I can see annoyed users turning this off and _still_ complaining. Current > > is turning into too much of a commodity with not enough emphasis of "thou > > shalt RTFM and RTSL". > > I've been thinking of how to say this with a suitable amount of force. > One way of doing this could be to stop cvsup access for -current. > > Yup - if you want to track -current, you track the cvs repository. If > you don't need the cvs repository, you're not developing code, and > thus shouldn't be in -current. > > I'm not sure if this is too drastic, but we really should be shooting > off those people... > > Eivind. Well, a dose of reality. Every one of you used to be in the position of some of these "people". You didn't know everything. And sometimes, RTFM just doesn't do the trick, especially when TFM is out-of-date because you the "developers" changed the code, but not the doc's. Now, with that said... My stupid question: How does one track -current without cvsup? I can't access the repository via nfs, and I don't have an account for either pserver or rsh mode... Now some praise for the the committers who have been working through the bug database. Thanks! And my pet peaves :-) 'make release' still seems to be installing a kerberos system. telnetd has a bug somewhere in it's handling of the default banner: / (cvs.unx.sas.com) (ttyp1) which should read: FreeBSD/i386 (cvs.unx.sas.com) (ttyp1) This is ONLY exhibitted under the krb version of telnetd, the the default version. Comments, Critiques, and helpful hints are ALWAYS welcome! Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 22:57:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12668 for freebsd-current-outgoing; Sun, 13 Dec 1998 22:57:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12659 for ; Sun, 13 Dec 1998 22:57:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA35639; Sun, 13 Dec 1998 22:57:16 -0800 (PST) (envelope-from dillon) Date: Sun, 13 Dec 1998 22:57:16 -0800 (PST) From: Matthew Dillon Message-Id: <199812140657.WAA35639@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: dev/usb/umodem.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ( while trying to build LINT ) cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitializ ed -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../inc lude -DKERNEL -include opt_global.h -aout ../../dev/usb/umodem.c ../../dev/usb/umodem.c: In function `umodem_match': ../../dev/usb/umodem.c:143: `UCLASS_CDC' undeclared (first use this function) ../../dev/usb/umodem.c:143: (Each undeclared identifier is reported only once ../../dev/usb/umodem.c:143: for each function it appears in.) ../../dev/usb/umodem.c:144: `USUBCLASS_MODEM' undeclared (first use this functio n) *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 13 23:46:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17898 for freebsd-current-outgoing; Sun, 13 Dec 1998 23:46:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA17870 for ; Sun, 13 Dec 1998 23:45:59 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id CAA24218; Mon, 14 Dec 1998 02:45:46 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA08111; Mon, 14 Dec 1998 02:45:45 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id CAA15890; Mon, 14 Dec 1998 02:45:44 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812140745.CAA15890@bb01f39.unx.sas.com> Subject: Re: /etc/rc busted for legacy aout ldconfig setup In-Reply-To: <199812140340.OAA01662@cimlogic.com.au> from John Birrell at "Dec 14, 98 02:40:13 pm" To: jb@cimlogic.com.au (John Birrell) Date: Mon, 14 Dec 1998 02:45:44 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, My system is usually up-to-date within the hour. Unfortunately, the change to rc busted ldconfig and my system wasn't running cvsup correctly. It took me about 36 hours before I figured out what the problem was.... I'm probably one of the only people who does a: cd /usr/src && make world && cd release && make release and updates all files in /etc/rc, builds a new kernel, and reboots every other day. All automatically. The last few days of commits have played havoc with my system. I sometimes wonder if the code that is pushed is actually tested. That isn't a flame, but I wonder if some of the committers might not be 'over' committed. There have been alot of 'opps' lately. I'm not a committer, so take what I say with a grain of salt.... and I really do appreciate all the work everyone is doing. Yea, I should probably rebuild m3socks to be elf, not aout (I run cvsup through a firewall). Just my 0.02 cents... Thanks! John > John W. DeBoskey wrote: > > 1.161 Thu Dec 10 8:06:59 1998 UTC by jb > > Diffs to 1.160 > > > > Add a test for hw.machine == i386 before trying to run ldconfig for > > legacy aout support. > > > > > > The following conditional is wrong: > > > > if [ X"`sysctl hw.machine`" = X"i386" ]; then > > There's a -n in rev 1.162. Please check the _current_ sources before reporting > this sort of thing. 1.162 is dated 1998/12/11 08:25:12. > > -- > John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ > CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 00:25:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22928 for freebsd-current-outgoing; Mon, 14 Dec 1998 00:25:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22915 for ; Mon, 14 Dec 1998 00:25:29 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id JAA12901 for ; Mon, 14 Dec 1998 09:25:25 +0100 (CET) Received: from doorway.home.lan (t2o1p60.telia.com [195.67.240.120]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id JAA22355 for ; Mon, 14 Dec 1998 09:25:24 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id HAA09696 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 07:28:48 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 07:28:48 +0100 (CET) From: List User Message-Id: <199812140628.HAA09696@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Joel Ray Holveck Subject: Re: ^@^@^@^@^@^@^@ (empty pages) in NFS served file. Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id XAA18140; Sun, 13 Dec 1998 23:59:13 -0600 (CST) (envelope-from joelh) To: Mark Huizer Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Lines: 26 Message-ID: <864sqzmfgw.fsf@detlev.UUCP> X-Mailer: Gnus v5.5/Emacs 20.3 References: <19981213235615.A12800@ariel.xaa.iae.nl> Delivered-To: vmailer-current@freebsd.org X-Uidl: 97b9fca3cdb47626afe7c38495381f7c X-Loop: FreeBSD.ORG In-Reply-To: Mark Huizer's message of "Sun, 13 Dec 1998 23:56:15 +0100" Cc: current Date: Mon, 14 Dec 1998 05:59:11 GMT [moved to -current] > Hi! quite often I run into problems with NFS served files, containing a > page of ^@^@^@^@^@^@^@'s instead of actual data (mostly noticed in > textfiles). > After checking on the server, it seems the data is valid there. Touch'ing > it helps sometimes. > Environment is 2x FreeBSD current, running nfsv3 over udp, on machines > with softupdates enabled. > Anyone having the same trouble?? Yes, on a small shared mail directory. I assumed that it was equally corrupt on both client and server, but haven't verified that. All file access to the file I'm monitoring has been from the same client, with locking implements (not flock) to prevent simultanious writes. Same setup as you describe, although I'm about to move the server to -stable instead. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 00:25:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22938 for freebsd-current-outgoing; Mon, 14 Dec 1998 00:25:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22921 for ; Mon, 14 Dec 1998 00:25:32 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id JAA12880 for ; Mon, 14 Dec 1998 09:25:24 +0100 (CET) Received: from doorway.home.lan (t2o1p60.telia.com [195.67.240.120]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id JAA22348 for ; Mon, 14 Dec 1998 09:25:22 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id HAA09747 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 07:28:50 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 07:28:50 +0100 (CET) From: List User Message-Id: <199812140628.HAA09747@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: "Jordan K. Hubbard" Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id WAA37519; Sun, 13 Dec 1998 22:09:35 -0800 (PST) To: Matthew Dillon Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <37515.913615774@zippy.cdrom.com> Delivered-To: vmailer-current@freebsd.org X-Uidl: 52843e3dbdbb36c3360471271c586cc6 X-Loop: FreeBSD.ORG In-Reply-To: Your message of "Sun, 13 Dec 1998 18:46:54 PST." <199812140246.SAA18566@apollo.backplane.com> Cc: freebsd-current Date: Mon, 14 Dec 1998 06:09:34 GMT > It is *very* annoying. Is there any particular reason why make clean > in /usr/src does not clean the entire source hierarchy? Probably because someone broke it and nobody noticed. It should indeed be possible to build with a r/o /usr/src just as it should be possible to get back to a /usr/obj containing little more than .depend files and directories if you do a make clean. How true that is at any given time depends on how thorough people have been in their Makefile hacking. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 00:25:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22963 for freebsd-current-outgoing; Mon, 14 Dec 1998 00:25:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22923 for ; Mon, 14 Dec 1998 00:25:33 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id JAA12932 for ; Mon, 14 Dec 1998 09:25:29 +0100 (CET) Received: from doorway.home.lan (t2o1p60.telia.com [195.67.240.120]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id JAA22373 for ; Mon, 14 Dec 1998 09:25:27 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id HAA09686 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 07:28:46 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 07:28:46 +0100 (CET) From: List User Message-Id: <199812140628.HAA09686@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: "John Saunders" Subject: RE: HEADS UP : laptop power-down change Content-Type: text/plain; charset="iso-8859-1" X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id RAA06013; Mon, 14 Dec 1998 17:09:15 +1100 To: "FreeBSD current" Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Importance: Normal Message-ID: <003001be2728$46d0d9a0$6cb611cb@saruman.scitec.com.au> X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Delivered-To: vmailer-current@freebsd.org X-Uidl: 4c0d57959799ddbbcf06ad7376640d7c X-Loop: FreeBSD.ORG X-Priority: 3 (Normal) Mime-Version: 1.0 In-Reply-To: <199812112115.OAA04520@harmony.village.org> Cc: Date: Mon, 14 Dec 1998 06:09:15 GMT > : Now in the subcase that you're running FreeBSD on i386 with no monitor > : ROM, then I don't what's wrong with making '-h' and '-p' degenerate, > : ie, they both do the same thing: halt the system and cause a power off. > > Also agreed. > > For a power managed i386 system, I see no benefit from not mapping the > two to the same thing. As long as you provide a way for halting without powering down then I don't really care. I have a power managed machine and I _do_not_ want it to power down when I halt it. At least the "-p == power down" and "-h == halt" argument provides me with both the options I need. Your option removes the very option that I want, with no replacement mechanism. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 00:25:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22982 for freebsd-current-outgoing; Mon, 14 Dec 1998 00:25:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22917 for ; Mon, 14 Dec 1998 00:25:31 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id JAA12851 for ; Mon, 14 Dec 1998 09:25:22 +0100 (CET) Received: from doorway.home.lan (t2o1p60.telia.com [195.67.240.120]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id JAA22337 for ; Mon, 14 Dec 1998 09:25:18 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id HAA09701 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 07:28:48 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 07:28:48 +0100 (CET) From: List User Message-Id: <199812140628.HAA09701@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Mark Murray Subject: Pet peeves (WAS: Re: cvs commit: src/etc Makefile) Received: from grondar.za (IDENT:a9tf5ti29OxQUSn9GsNso7NN7Iz/ooNM@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id IAA61231; Mon, 14 Dec 1998 08:20:51 +0200 (SAST) (envelope-from mark@grondar.za) To: "John W. DeBoskey" Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <199812140620.IAA61231@greenpeace.grondar.za> References: <199812132313.SAA13630@bb01f39.unx.sas.com> Delivered-To: vmailer-current@freebsd.org X-Uidl: 3472a58a845ff7527b2cf3b45d43215a X-Loop: FreeBSD.ORG In-Reply-To: Your message of " Sun, 13 Dec 1998 18:13:37 EST." <199812132313.SAA13630@bb01f39.unx.sas.com> Cc: freebsd-current Date: Mon, 14 Dec 1998 06:20:50 GMT "John W. DeBoskey" wrote: > And my pet peaves :-) > > 'make release' still seems to be installing a kerberos system. Fix coming with PAM completion. > telnetd has a bug somewhere in it's handling of the default banner: : > This is ONLY exhibitted under the krb version of telnetd, the the default > version. Evaluating fix... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 01:08:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29082 for freebsd-current-outgoing; Mon, 14 Dec 1998 01:08:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29063; Mon, 14 Dec 1998 01:08:30 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id KAA03043; Mon, 14 Dec 1998 10:07:37 +0100 (CET) To: Julian Elischer cc: current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! In-reply-to: Your message of "Sun, 13 Dec 1998 20:39:38 PST." Date: Mon, 14 Dec 1998 10:07:33 +0100 Message-ID: <3041.913626453@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still waiting for the src, docs and the license for that stuff, you promised to send it to me long time ago :-) Poul-Henning In message , Julian Elischer writes: >how about porting the whole shebang to whistle's 'streams' >replacement.. >we could probably supply the frame relay and ppp packetizer nodes along >with the framework and tools... >s > > >On Sun, 13 Dec 1998, Poul-Henning Kamp wrote: > >> >> I think I have finally found out what the problem is with the state >> machine in the if_sppp implementation. Whoever wrote the implementation >> didn't carefully consider the inter-layer calls tls and tlf. >> >> If one applies a lot of patches like this one: >> >> case STATE_OPENED: >> - (cp->tld)(sp); >> sp->rst_counter[cp->protoidx] = 0; >> sppp_cp_change_state(cp, sp, STATE_STOPPING); >> + (cp->tld)(sp); >> goto sta; >> break; >> >> Then things actually start to make sense... >> >> The problem is that the tld and tlf functions often just call the >> pp_up and pp_down routines directly, and therefore most if not all >> of the expected up and down events happen in the previous state >> as opposed to the next state. >> >> Flipping it around like I have done above, on the other hand, may >> not be a good idea either, since it means we can nest another layer >> on the stack and get somewhat confused on the way down. >> >> It is quite obvious that this will need some more work to sort out, >> anybody interested in participating ? >> >> >> -- >> Poul-Henning Kamp FreeBSD coreteam member >> phk@FreeBSD.ORG "Real hackers run -current on their laptop." >> "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-current" in the body of the message >> > > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 01:25:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01232 for freebsd-current-outgoing; Mon, 14 Dec 1998 01:25:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01171 for ; Mon, 14 Dec 1998 01:25:47 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id KAA24713 for ; Mon, 14 Dec 1998 10:25:40 +0100 (CET) Received: from doorway.home.lan (t6o1p48.telia.com [195.67.241.108]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id KAA10836 for ; Mon, 14 Dec 1998 10:25:38 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id JAA12155 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 09:29:53 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 09:29:53 +0100 (CET) From: List User Message-Id: <199812140829.JAA12155@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: "John W. DeBoskey" Subject: Re: /etc/rc busted for legacy aout ldconfig setup Content-Type: text/plain; charset=US-ASCII Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id CAA15890; Mon, 14 Dec 1998 02:45:44 -0500 (EST) (envelope-from jwd) To: jb (John Birrell) Sender: owner-freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812140745.CAA15890@bb01f39.unx.sas.com> X-Mailer: ELM [version 2.4ME+ PL38 (25)] Delivered-To: vmailer-current@freebsd.org X-Uidl: 9d579967b9e83b314d45c0c617e554d1 X-Loop: FreeBSD.ORG Mime-Version: 1.0 Cc: freebsd-current In-Reply-To: <199812140340.OAA01662@cimlogic.com.au> from John Birrell at "Dec 14, 98 02:40:13 pm" Date: Mon, 14 Dec 1998 07:45:44 GMT Hi, My system is usually up-to-date within the hour. Unfortunately, the change to rc busted ldconfig and my system wasn't running cvsup correctly. It took me about 36 hours before I figured out what the problem was.... I'm probably one of the only people who does a: cd /usr/src && make world && cd release && make release and updates all files in /etc/rc, builds a new kernel, and reboots every other day. All automatically. The last few days of commits have played havoc with my system. I sometimes wonder if the code that is pushed is actually tested. That isn't a flame, but I wonder if some of the committers might not be 'over' committed. There have been alot of 'opps' lately. I'm not a committer, so take what I say with a grain of salt.... and I really do appreciate all the work everyone is doing. Yea, I should probably rebuild m3socks to be elf, not aout (I run cvsup through a firewall). Just my 0.02 cents... Thanks! John > John W. DeBoskey wrote: > > 1.161 Thu Dec 10 8:06:59 1998 UTC by jb > > Diffs to 1.160 > > > > Add a test for hw.machine == i386 before trying to run ldconfig for > > legacy aout support. > > > > > > The following conditional is wrong: > > > > if [ X"`sysctl hw.machine`" = X"i386" ]; then > > There's a -n in rev 1.162. Please check the _current_ sources before reporting > this sort of thing. 1.162 is dated 1998/12/11 08:25:12. > > -- > John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ > CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 01:26:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01269 for freebsd-current-outgoing; Mon, 14 Dec 1998 01:26:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01172 for ; Mon, 14 Dec 1998 01:25:49 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id KAA24442 for ; Mon, 14 Dec 1998 10:25:22 +0100 (CET) Received: from doorway.home.lan (t6o1p48.telia.com [195.67.241.108]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id KAA10756 for ; Mon, 14 Dec 1998 10:25:20 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id JAA10957 for freebsd-current@FreeBSD.org; Mon, 14 Dec 1998 09:28:41 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 09:28:41 +0100 (CET) From: List User Message-Id: <199812140828.JAA10957@doorway.home.lan> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.current Path: root From: Matthew Dillon Subject: dev/usb/umodem.c Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA35639; Sun, 13 Dec 1998 22:57:16 -0800 (PST) (envelope-from dillon) To: freebsd-current Sender: owner-freebsd-current@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <199812140657.WAA35639@apollo.backplane.com> Delivered-To: vmailer-current@freebsd.org X-Uidl: 984d040d358b3e37b62da215b23efb2d X-Loop: FreeBSD.ORG Date: Mon, 14 Dec 1998 06:57:16 GMT ( while trying to build LINT ) cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitializ ed -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../inc lude -DKERNEL -include opt_global.h -aout ../../dev/usb/umodem.c ../../dev/usb/umodem.c: In function `umodem_match': ../../dev/usb/umodem.c:143: `UCLASS_CDC' undeclared (first use this function) ../../dev/usb/umodem.c:143: (Each undeclared identifier is reported only once ../../dev/usb/umodem.c:143: for each function it appears in.) ../../dev/usb/umodem.c:144: `USUBCLASS_MODEM' undeclared (first use this functio n) *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 01:43:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03205 for freebsd-current-outgoing; Mon, 14 Dec 1998 01:43:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03199 for ; Mon, 14 Dec 1998 01:43:16 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA49992; Mon, 14 Dec 1998 09:42:22 GMT Date: Mon, 14 Dec 1998 09:42:22 +0000 (GMT) From: Doug Rabson To: Atsushi Furuta cc: mike@smith.net.au, y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812131023.TAA05525@sramhc.sra.co.jp> 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, 13 Dec 1998, Atsushi Furuta wrote: > >> In article , > Doug Rabson writes: > > > The softc issue is addressed by the new device framework. The pci support > > code has not yet been updated to the new interface but when it is, it will > > get this for free. The flags field can also be easily added. > > I wonder how a user specifies flags to pci bus. I seems that there > is no generic way to specify flags in current subr_bus.c, and it is up > to each bus codes how to provide ivers and flags. It is true that there is no flags field hardcoded into the device. As you have noted, it is easy for any bus for which it is relavent to implement one using ivars. It is also easy for a bus implementation to pick up flags and device wiring preferences from config(8). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 01:44:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03332 for freebsd-current-outgoing; Mon, 14 Dec 1998 01:44:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hsw.generalresources.com ([203.79.17.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03254 for ; Mon, 14 Dec 1998 01:43:47 -0800 (PST) (envelope-from hsw@email.generalresources.com) Received: from hsw.generalresources.com (localhost [127.0.0.1]) by hsw.generalresources.com (8.9.1/8.9.1) with ESMTP id RAA04244 for ; Mon, 14 Dec 1998 17:42:48 +0800 (CST) (envelope-from hsw@hsw.generalresources.com) Message-Id: <199812140942.RAA04244@hsw.generalresources.com> To: freebsd-current@FreeBSD.ORG From: Christopher Hall Reply-to: Christopher Hall Subject: ppp tunnelling X-Operating-System: FreeBSD 3.0 X-Mailer: exmh 2.0 Date: Mon, 14 Dec 1998 17:42:48 +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a fairly recent make world (cvsup about 12 hours ago) I rebuilt the kernel with two tunnel devices to try to use the ppp.conf "loopback". (from ppp.conf.sample file version 1.33) I tried the following: When I run the client ppp, the server ppp seems to hang, and kill is needed to stop the server. Telnet to server ppp also hangs, there is no output from the server. Running ppp -direct loop-in prints 5 blocks of binary data. Replacing the server with a simple C program to output a couple of lines of text and running the client interactive mode; the text shows up when the "term" command is used. Here is the run: [hsw:/etc/ppp]# ppp -background loop Working in background mode Using interface: tun0 Child failed (errdead). [hsw:/etc/ppp]# >From ps -ax: 698 ?? Is 0:00.04 ppp -direct loop-in It looks to me like the server ppp is not doing any I/O once it has been started by inetd. Just added the Async log flag and I can see the data is only received by the server ppp _after_ it receives the signal 15 from the kill. Might this suggest that it has not set the socket to non-blocking? --- Christopher Hall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 02:28:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07657 for freebsd-current-outgoing; Mon, 14 Dec 1998 02:28:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07651 for ; Mon, 14 Dec 1998 02:28:42 -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 VAA27034; Mon, 14 Dec 1998 21:28:27 +1100 Date: Mon, 14 Dec 1998 21:28:27 +1100 From: Bruce Evans Message-Id: <199812141028.VAA27034@godzilla.zeta.org.au> To: dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to do a buildworld with /usr/src mounted read-only (via NFS). > > The buildworld has died several times trying to remove .o files, binaries, > and libraries (*.so.*) from /usr/src that happened to be hanging around. > > Ok, I say... cd /usr/src on the physical machine and 'make clean'. > > Only problem is it doesn't work... it does not recursive through the entire > source hierarchy. For example, make clean in /usr/src does not bother > recursing through /usr/src/bin, /usr/src/sbin, /usr/src/gnu, etc... It does recurse. This used to be fairly easy to see by typing `make -n clean', but now you have to untangle 3 layers of nested Makefiles to see what will happen, e.g., make -n clean | sed 's/make/make -n/' | sh | sed 's/make/make -n/' | sh `make clean' is the wrong command for cleaning the source tree. It cleans the object tree and should not touch the source tree unless the (separate) obj tree is nonexistent or damaged. To clean the source tree, first use `make cleandir' or `rm -rf' or `mv' to clean or move the obj tree. Then the (non-separate) obj tree will be the source tree and it can be cleaned using `make clean' or `make cleandir' (modulo obj subdirectories which may require another cleandir pass to remove). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 05:20:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21811 for freebsd-current-outgoing; Mon, 14 Dec 1998 05:20:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21803 for ; Mon, 14 Dec 1998 05:20:40 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id OAA18783; Mon, 14 Dec 1998 14:21:11 +0100 (MET) Date: Mon, 14 Dec 1998 14:20:31 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD current mailing list cc: Lennart Augustsson , USB BSD list Subject: double CVS repositories 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 Anyone working on a project in which 2 entirely different repositories are being kept up to date simultaneously? The problem we have is that we (Lennart, NetBSD and myself, FreeBSD) would like to have a CVS repository to which we commit changes to the USB source, but at the same time would like to commit things to the repository of the OS as well. Now this would be possible by writing a number of scripts that get executed when committing to a local repository. But that does not sound very sexy. Anyone any better solutions to this problem? Anyone any working examples we could copy? Cheers, Nick Hibma FreeBSD USB project -- The above are strictly my own opinions and not my employer's. e-mail: n_hibma@freebsd.org home page: http://www.etla.net/~n_hibma/usb/usb.pl mailing list: usb-bsd@egroups.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 07:04:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00563 for freebsd-current-outgoing; Mon, 14 Dec 1998 07:04:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00557 for ; Mon, 14 Dec 1998 07:04:26 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id QAA29236 for ; Mon, 14 Dec 1998 16:04:13 +0100 (CET) Received: from wurzelausix (quadratix.cs.uni-sb.de [134.96.222.2]) by cs.uni-sb.de (8.9.1a/1998121400) with ESMTP id QAA05023 for ; Mon, 14 Dec 1998 16:04:12 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:U1MJtFewysVkGycNUTsbQEiFL577RLd0@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id QAA19327 for ; Mon, 14 Dec 1998 16:04:09 +0100 (CET) Message-Id: <199812141504.QAA19327@wurzelausix> Date: Mon, 14 Dec 1998 16:04:05 +0100 (CET) From: Alexander Leidinger Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? To: current@FreeBSD.ORG In-Reply-To: <37515.913615774@zippy.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 13 Dec, Jordan K. Hubbard wrote: > Probably because someone broke it and nobody noticed. It should > indeed be possible to build with a r/o /usr/src just as it should be I tried that (r/o nfs) some weeks ago, but it failed because of freebsd.cf, which gets created in /usr/src/... I try it again (on request). Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 07:07:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01075 for freebsd-current-outgoing; Mon, 14 Dec 1998 07:07:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01070 for ; Mon, 14 Dec 1998 07:07:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id HAA39162; Mon, 14 Dec 1998 07:06:46 -0800 (PST) To: Alexander Leidinger cc: current@FreeBSD.ORG Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? In-reply-to: Your message of "Mon, 14 Dec 1998 16:04:05 +0100." <199812141504.QAA19327@wurzelausix> Date: Mon, 14 Dec 1998 07:06:46 -0800 Message-ID: <39158.913648006@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, I believe you. Getting it to stop doing that is the ticket now. :) > On 13 Dec, Jordan K. Hubbard wrote: > > Probably because someone broke it and nobody noticed. It should > > indeed be possible to build with a r/o /usr/src just as it should be > > I tried that (r/o nfs) some weeks ago, but it failed because of > freebsd.cf, which gets created in /usr/src/... > > I try it again (on request). > > Bye, > Alexander. > > -- > http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 07:47:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05191 for freebsd-current-outgoing; Mon, 14 Dec 1998 07:47:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from afs.ntc.mita.keio.ac.jp (afs.ntc.mita.keio.ac.jp [131.113.212.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05183 for ; Mon, 14 Dec 1998 07:46:59 -0800 (PST) (envelope-from hosokawa@ntc.keio.ac.jp) Received: (from hosokawa@localhost) by afs.ntc.mita.keio.ac.jp (8.8.8+2.7Wbeta7/3.6Wbeta6-ntc_mailserver1.03) id AAA25255; Tue, 15 Dec 1998 00:46:31 +0900 (JST) Date: Tue, 15 Dec 1998 00:46:31 +0900 (JST) Message-Id: <199812141546.AAA25255@afs.ntc.mita.keio.ac.jp> To: jkh@zippy.cdrom.com Cc: y-nakaga@nwsl.mesh.ad.jp, mike@smith.net.au, kjc@csl.sony.co.jp, nathan@rtfm.net, current@FreeBSD.ORG, hosokawa@ntc.keio.ac.jp Subject: Re: PAO Integration? In-Reply-To: Your message of "Sun, 13 Dec 1998 17:29:34 JST". <34776.913537774@zippy.cdrom.com> From: hosokawa@ntc.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <34776.913537774@zippy.cdrom.com> jkh@zippy.cdrom.com writes: >> And we appreciate that, believe me. I think Mike may have been a >> little too harsh in his original message and I think that everyone in >> core, at least, does appreciate the language problem and the fact that >> you guys are often "out of the loop" on a lot of things going on >> around here. It would help greatly, of course, if Tatsumi-san would >> come back and take up the commit privs we gave him for the purpose of >> creating closer cooperation. Has anyone even seen Mr. Hosokawa >> lately? Is he still alive? :-) I'm alive, but I haven't recieved any current@freebsd.org mails these days. I heard about this thread in other mailing list and I searched my mailbox, but I found that no current@freebsd.org mails in it. I unsubscribed current once, and subscribed it again, but no mails have come from current@freebsd.org... Hmm... (I'm writing this mail via mail-netnews gateway) BTW, I think that PAO for 2.2.8 and 3.0 are provided for convenience of users and should be integrated in smart way. For example, I think that pcic_probe/attach, resource allocation code, multiple windows support, and some very dirty hacks in PAO should be totally rewritten before integration, but TI support, regex in pccard.conf, function ID in pccard.conf, noirq in pccard.conf, broken CIS hack, etc. should be integrated in -current. But I can't spend time for these works because I'm very busy today. I think PAO for 3.0 is better startline for these works than PAO for 2.2.1, 2.2.2, 2.2.5,.... I hope many people works on the smart integration of PAO and I think I can help them. *I personally* don't think that newconfig is needed for *PAO*, but I think that better device driver implementation is needed for *FreeBSD*. If many people think newconfig is better implementation and FreeBSD uses it, I think that the experiences in PAO experimental code should be rewritten in newconfig way, and if everyone says new-bus is the best, PAO should be rewritten in new-bus way. I don't think that all PAO code should be in -current, but I think we've got many pracical knowledge of PC-card system from PAO, and I believe that these experiences are useful for future FreeBSD. -- HOSOKAWA, Tatsumi Network Technology Center Keio University hosokawa@ntc.keio.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 07:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05596 for freebsd-current-outgoing; Mon, 14 Dec 1998 07:48:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org ([142.177.186.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05588 for ; Mon, 14 Dec 1998 07:48:38 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id LAA27396 for ; Mon, 14 Dec 1998 11:48:34 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 14 Dec 1998 11:48:33 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: System "crashed", serial console giving garbage... 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 Morning... About 15min oago or so, my system stop'd working :( If I connect through the serial console, I see the following, after hitting return: pagecorp> attach s0 Trying 209.47.145.10 ... Connected - Escape character is '^]'. $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef Now, I could understand it crashing and just freezing, but issuign garbage? I have nothing else to debug with at this point, and have to wait for someone to head downtown to reboot the machine, but figured I'd try to start *somewhere* :( 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 Mon Dec 14 07:59:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06479 for freebsd-current-outgoing; Mon, 14 Dec 1998 07:59:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06473; Mon, 14 Dec 1998 07:59:17 -0800 (PST) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (haldjas.folklore.ee [172.17.2.1] (may be forged)) by haldjas.folklore.ee (8.8.8/8.8.4) with SMTP id RAA06489; Mon, 14 Dec 1998 17:59:03 +0200 (EET) Date: Mon, 14 Dec 1998 17:59:02 +0200 (EET) From: Narvi To: postmaster@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: List user In-Reply-To: <199812140829.JAA12155@doorway.home.lan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There's an adress to be unsubed... Aparently their mail<->news gateway is broken. Sander There is no love, no good, no happiness and no future - all these are just illusions. On Mon, 14 Dec 1998, List User wrote: > Newsgroups: freebsd.current > Path: root > From: "John W. DeBoskey" > Subject: Re: /etc/rc busted for legacy aout ldconfig setup > Content-Type: text/plain; charset=US-ASCII > Received: (from jwd@localhost) > by bb01f39.unx.sas.com (8.9.1/8.9.1) id CAA15890; > Mon, 14 Dec 1998 02:45:44 -0500 (EST) > (envelope-from jwd) > To: jb (John Birrell) > Sender: owner-freebsd-current@FreeBSD.ORG > Content-Transfer-Encoding: 7bit > Organization: Private News Host > Precedence: bulk > Message-ID: <199812140745.CAA15890@bb01f39.unx.sas.com> > X-Mailer: ELM [version 2.4ME+ PL38 (25)] > Delivered-To: vmailer-current@freebsd.org > X-Uidl: 9d579967b9e83b314d45c0c617e554d1 > X-Loop: FreeBSD.ORG > Mime-Version: 1.0 > Cc: freebsd-current > In-Reply-To: <199812140340.OAA01662@cimlogic.com.au> from John Birrell at "Dec 14, 98 02:40:13 pm" > Date: Mon, 14 Dec 1998 07:45:44 GMT > > Hi, > > My system is usually up-to-date within the hour. Unfortunately, > the change to rc busted ldconfig and my system wasn't running > cvsup correctly. It took me about 36 hours before I figured out > what the problem was.... > > I'm probably one of the only people who does a: > > cd /usr/src && make world && cd release && make release > > and updates all files in /etc/rc, builds a new kernel, and > reboots every other day. All automatically. The last few days > of commits have played havoc with my system. > > > I sometimes wonder if the code that is pushed is actually > tested. That isn't a flame, but I wonder if some of the > committers might not be 'over' committed. There have been > alot of 'opps' lately. I'm not a committer, so take what I > say with a grain of salt.... and I really do appreciate all > the work everyone is doing. > > Yea, I should probably rebuild m3socks to be elf, not aout (I run > cvsup through a firewall). > > Just my 0.02 cents... > > Thanks! > John > > > > John W. DeBoskey wrote: > > > 1.161 Thu Dec 10 8:06:59 1998 UTC by jb > > > Diffs to 1.160 > > > > > > Add a test for hw.machine == i386 before trying to run ldconfig for > > > legacy aout support. > > > > > > > > > The following conditional is wrong: > > > > > > if [ X"`sysctl hw.machine`" = X"i386" ]; then > > > > There's a -n in rev 1.162. Please check the _current_ sources before reporting > > this sort of thing. 1.162 is dated 1998/12/11 08:25:12. > > > > -- > > John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ > > CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 08:02:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06720 for freebsd-current-outgoing; Mon, 14 Dec 1998 08:02:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06709 for ; Mon, 14 Dec 1998 08:02:14 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id QAA06496; Mon, 14 Dec 1998 16:00:35 GMT Message-ID: <36753622.3B46F4E2@tdx.co.uk> Date: Mon, 14 Dec 1998 16:00:34 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: The Hermit Hacker CC: freebsd-current@FreeBSD.ORG Subject: Re: System "crashed", serial console giving garbage... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > > Morning... > > About 15min oago or so, my system stop'd working :( If I connect > through the serial console, I see the following, after hitting return: > > pagecorp> attach s0 > Trying 209.47.145.10 ... > Connected - Escape character is '^]'. > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > > Now, I could understand it crashing and just freezing, but issuign > garbage? > > I have nothing else to debug with at this point, and have to wait for > someone to head downtown to reboot the machine, but figured I'd try to > start *somewhere* :( I've seen similar to this before... Make sure your not trying to run remote GDB across the serial console? (without it's counterpart on the other end)... I can't understand your connect statement above? - If you connecting to the serial port how come you get "Trying xx.xx.xxx ..."? - I thought that was only from telnet? -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 08:38:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09569 for freebsd-current-outgoing; Mon, 14 Dec 1998 08:38:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09562 for ; Mon, 14 Dec 1998 08:38:18 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from atelier.acadiau.ca (atelier.acadiau.ca [131.162.138.103]) by garlic.acadiau.ca (8.8.5/8.8.5) with ESMTP id MAA25185; Mon, 14 Dec 1998 12:38:02 -0400 (AST) Date: Mon, 14 Dec 1998 12:37:43 -0400 (AST) From: "Marc G. Fournier" To: Karl Pielorz cc: freebsd-current@FreeBSD.ORG Subject: Re: System "crashed", serial console giving garbage... In-Reply-To: <36753622.3B46F4E2@tdx.co.uk> 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, 14 Dec 1998, Karl Pielorz wrote: > > > The Hermit Hacker wrote: > > > > Morning... > > > > About 15min oago or so, my system stop'd working :( If I connect > > through the serial console, I see the following, after hitting return: > > > > pagecorp> attach s0 > > Trying 209.47.145.10 ... > > Connected - Escape character is '^]'. > > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > > > > Now, I could understand it crashing and just freezing, but issuign > > garbage? > > > > I have nothing else to debug with at this point, and have to wait for > > someone to head downtown to reboot the machine, but figured I'd try to > > start *somewhere* :( > > I've seen similar to this before... Make sure your not trying to run remote > GDB across the serial console? (without it's counterpart on the other end)... Altho I think this would be highly unlikely, given the method of connecting the serial console I'm using...how would I check this, just in case? > I can't understand your connect statement above? - If you connecting to the > serial port how come you get "Trying xx.xx.xxx ..."? - I thought that was only > from telnet? I've got the serial port connected to a port on a portmaster, so when I 'attach', it initiates a telnet to the port itself... Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 08:52:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11423 for freebsd-current-outgoing; Mon, 14 Dec 1998 08:52:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11413 for ; Mon, 14 Dec 1998 08:52:42 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from atelier.acadiau.ca (atelier.acadiau.ca [131.162.138.103]) by garlic.acadiau.ca (8.8.5/8.8.5) with ESMTP id MAA26293; Mon, 14 Dec 1998 12:52:31 -0400 (AST) Date: Mon, 14 Dec 1998 12:52:12 -0400 (AST) From: "Marc G. Fournier" To: "Marc G. Fournier" cc: Karl Pielorz , freebsd-current@FreeBSD.ORG Subject: Re: System "crashed", serial console giving garbage... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 14 Dec 1998, Marc G. Fournier wrote: > I've got the serial port connected to a port on a portmaster, so when I > 'attach', it initiates a telnet to the port itself... Just a quick followup, I just took a drive up home to check what was on the serial console before this happened, and...nothing. Last 'error' had to do with httpd some 4 hours previous... I feared that I might see some scrolling list of errors or something :( Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 09:13:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13305 for freebsd-current-outgoing; Mon, 14 Dec 1998 09:13:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13266 for ; Mon, 14 Dec 1998 09:13:13 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id JAA02678 for ; Mon, 14 Dec 1998 09:13:06 -0800 Date: Mon, 14 Dec 1998 09:13:06 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-current@FreeBSD.ORG Subject: Tape Driver Changes Proposed: Tape Early Warning Behaviour Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (This may not be the correct forum for this discussion- but I wanted to include *users* as well as *developers* of FreeBSD) I'll throw this out for opinions- I'd like to make change (close to what I did for NetBSD) to the default behaviour for how early warnings on writes are handled. The section below is from the man pages in NetBSD- I'd like to actually make EARLY WARNING default behaviour. Opinions, please... I have the hood open on the tape driver busily fixing(breaking) things so I'd like to get a sense of what people would like before marching much further. This is one of several changes under consideration. The others for immediate implementation are: + forcing variable mode for tape devices unless quirked otherwise (I have a test prototype of this already working) + correct implementation of 2 FM@EOD (only needed for tapes that do *not* have a space to end of recorded media function (basically only 1/2" Reel drives) + Hardware/SCSI/Logical Block reporting && positioning + SCSI error reporting via the MTIOCSTATUS command, possibly an auxillary MTIO command to get full (all of) previous SCSI Sense Data. Down the road a little bit would be: ++ untangling the minor device as behaviour selector so that ioctl's would not have to be used to select compression. ++ Persistent vs. per-mount device properties and reservation. ++ Proper handling of deferred errors Anyway- here's the Early warning man page clip- please let me know what y'all think: EOM HANDLING Attempts to write past EOM and how EOM is reported are handled slightly differently based upon whether EARLY WARNING recognition is enabled in the driver. If EARLY WARNING recognitions is not enabled, then detection of EOM (as reported in SCSI Sense Data with an EOM indicator) causes the write oper- ation to be flagged with I/O error (EIO). This has the effect for the user application of not knowing actually how many bytes were written (since the return of the read(2) system call is set to -1). If EARLY WARNING recognition is enabled, then detection of EOM has no im- mediate effect except that the driver notes that EOM has been detected. If the write completing didn't transfer all data that was requested, then the residual count is returned to the user application. In any event, the next attempt to write (if that is the next action the user application takes) is immediately completed with no data transferred, and a residual returned to the user application indicating that no data was transferred. This is the traditional UNIX EOF indication. The state that EOM had been seen is then cleared. In either mode of operation, the driver does not prohibit the user appli- cation from writing more data, if chooses to do so. This will continue up until the physical end of media, which is usually signalled internally to the driver as a CHECK CONDITION with the Sense Key set to VOLUME OVER- FLOW. When this or any otherwise unhandled error occurs, an error return of EIO will be transmitted to the user application. This does indeed mean that if EARLY WARNING is enables and the device continues to set EOM indicators prior to hitting physical end of media, that an indeterminate number of 'short write returns' as described in the previous paragraph will occur. However, the expected user application behaviour (in common with other systems) is to close the tape and rewind and request another tape upon the receipt of the first EOM indicator. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 09:23:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13912 for freebsd-current-outgoing; Mon, 14 Dec 1998 09:23:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13905 for ; Mon, 14 Dec 1998 09:23:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id JAA45920; Mon, 14 Dec 1998 09:23:02 -0800 (PST) (envelope-from dillon) Date: Mon, 14 Dec 1998 09:23:02 -0800 (PST) From: Matthew Dillon Message-Id: <199812141723.JAA45920@apollo.backplane.com> To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? References: <199812141504.QAA19327@wurzelausix> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On 13 Dec, Jordan K. Hubbard wrote: :> Probably because someone broke it and nobody noticed. It should :> indeed be possible to build with a r/o /usr/src just as it should be : :I tried that (r/o nfs) some weeks ago, but it failed because of :freebsd.cf, which gets created in /usr/src/... : :I try it again (on request). : :Bye, :Alexander. It seemed to do the right thing for me, once I finally got the object modules and other junk cleaned out of /usr/src from all my partial makes (i.e. when you do something like 'cd /usr/src/usr.bin/ls; make; make install' and for to 'make clean'). It took about 30 minutes of messing around to get it all, though. -Matt :-- :http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 09:48:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17392 for freebsd-current-outgoing; Mon, 14 Dec 1998 09:48:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17385 for ; Mon, 14 Dec 1998 09:48:28 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id JAA02794 for ; Mon, 14 Dec 1998 09:48:11 -0800 Date: Mon, 14 Dec 1998 09:48:11 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-current@FreeBSD.ORG Subject: building aout-to-elf? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did this once, I know, at Ames- but was finally doing feral's system, and this occurred: ===> strip cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip -I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/strip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/binutils -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/binutils/objcopy.c cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip -I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/strip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/binutils -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/binutils/is-strip.c cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src/gnu/usr.bin/binutils/strip -I/usr/src/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/include -I/usr/src/gnu/usr.bin/binutils/strip/../libbinutils -I/usr/src/gnu/usr.bin/binutils/strip/../../../../contrib/binutils/binutils -I/usr/obj/aout/usr/src/tmp/usr/include -static -o strip objcopy.o is-strip.o -L../libbinutils -lbinutils -L../libbfd -lbfd -L../libiberty -liberty cp strip maybe_stripped strip maybe_stripped strip: maybe_stripped: File format not recognized *** Error code 1 Any clues? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 09:57:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18223 for freebsd-current-outgoing; Mon, 14 Dec 1998 09:57:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18217 for ; Mon, 14 Dec 1998 09:57:07 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id MAA09454 for freebsd-current@freebsd.org; Mon, 14 Dec 1998 12:52:58 -0500 (EST) (envelope-from larry) Date: Mon, 14 Dec 1998 12:52:57 -0500 From: "Larry S. Marso" To: freebsd-current@FreeBSD.ORG Subject: recommended cvsup date? Message-ID: <19981214125257.D8998@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone provide a recommended cvsup "as of" date for the 3.0 branch? Anything subsequent to 3.0-R considered more stable? Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 10:01:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18734 for freebsd-current-outgoing; Mon, 14 Dec 1998 10:01:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18695; Mon, 14 Dec 1998 10:01:11 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t3o29p81.telia.com [194.236.215.81]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id TAA00886; Mon, 14 Dec 1998 19:00:57 +0100 Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.1/8.9.1) with ESMTP id SAA10291; Mon, 14 Dec 1998 18:58:57 +0100 (CET) (envelope-from johan@granlund.nu) Date: Mon, 14 Dec 1998 18:58:57 +0100 (CET) From: Johan Granlund To: Julian Elischer cc: Poul-Henning Kamp , current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! 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 Is this a implementation of SYSV Streams? /Johan On Sun, 13 Dec 1998, Julian Elischer wrote: > how about porting the whole shebang to whistle's 'streams' > replacement.. > we could probably supply the frame relay and ppp packetizer nodes along > with the framework and tools... > s > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 10:02:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19162 for freebsd-current-outgoing; Mon, 14 Dec 1998 10:02:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19151 for ; Mon, 14 Dec 1998 10:02:11 -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 FAA09572; Tue, 15 Dec 1998 05:02:05 +1100 Date: Tue, 15 Dec 1998 05:02:05 +1100 From: Bruce Evans Message-Id: <199812141802.FAA09572@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, mjacob@feral.com Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Down the road a little bit would be: > > ++ untangling the minor device as behaviour selector so that > ioctl's would not have to be used to select compression. This should be controversial :-). Compression is another type of behaviour. >EOM HANDLING > Attempts to write past EOM and how EOM is reported are handled slightly > differently based upon whether EARLY WARNING recognition is enabled in > the driver. > > If EARLY WARNING recognitions is not enabled, then detection of EOM (as > reported in SCSI Sense Data with an EOM indicator) causes the write oper- > ation to be flagged with I/O error (EIO). This has the effect for the > user application of not knowing actually how many bytes were written > (since the return of the read(2) system call is set to -1). I think it is a bug for write() to return -1 after sucessfully writing a short count. physio() does everything right in this area, but write(), writev(), read() and readv() do everything wrong. diff -c2 sys_generic.c~ sys_generic.c *** sys_generic.c~ Fri Dec 11 20:52:00 1998 --- sys_generic.c Fri Dec 11 20:52:03 1998 *************** *** 120,123 **** --- 120,124 ---- cnt = uap->nbyte; if ((error = (*fp->f_ops->fo_read)(fp, &auio, fp->f_cred))) + /* XXX short read botch. */ if (auio.uio_resid != cnt && (error == ERESTART || error == EINTR || error == EWOULDBLOCK)) *************** *** 202,205 **** --- 203,207 ---- cnt = auio.uio_resid; if ((error = (*fp->f_ops->fo_read)(fp, &auio, fp->f_cred))) + /* XXX short read botch. */ if (auio.uio_resid != cnt && (error == ERESTART || error == EINTR || error == EWOULDBLOCK)) *************** *** 269,272 **** --- 271,275 ---- cnt = uap->nbyte; if ((error = (*fp->f_ops->fo_write)(fp, &auio, fp->f_cred))) { + /* XXX short write botch. */ if (auio.uio_resid != cnt && (error == ERESTART || error == EINTR || error == EWOULDBLOCK)) *************** *** 355,358 **** --- 358,362 ---- cnt = auio.uio_resid; if ((error = (*fp->f_ops->fo_write)(fp, &auio, fp->f_cred))) { + /* XXX short write botch. */ if (auio.uio_resid != cnt && (error == ERESTART || error == EINTR || error == EWOULDBLOCK)) Here `auio.uio_resid != cnt' is true if some i/o was done, and in that case I think we should return the amount done and discard the error code (for EIO the next i/o will presumably hit the error immediately and return EIO), but we only do this for a few types of errors (ones that don't occur for disks or tapes). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 10:08:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19775 for freebsd-current-outgoing; Mon, 14 Dec 1998 10:08:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19770 for ; Mon, 14 Dec 1998 10:08:37 -0800 (PST) (envelope-from richard@cogsci.ed.ac.uk) Received: (from richard@localhost) by cogsci.ed.ac.uk (8.8.7/8.8.7) id SAA17001; Mon, 14 Dec 1998 18:07:57 GMT Date: Mon, 14 Dec 1998 18:07:57 GMT Message-Id: <199812141807.SAA17001@cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour To: mjacob@feral.com, freebsd-current@FreeBSD.ORG In-Reply-To: Matthew Jacob's message of Mon, 14 Dec 1998 09:13:06 -0800 (PST) Organization: just say no Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a nit about terminology: > If the write completing didn't transfer all data that was requested, then > the residual count is returned to the user application. Surely the "residual count" is the number of bytes *not* written, whereas what is returned to the user is the number successfully written. -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 10:15:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20748 for freebsd-current-outgoing; Mon, 14 Dec 1998 10:15:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20742 for ; Mon, 14 Dec 1998 10:15:28 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id KAA02910; Mon, 14 Dec 1998 10:14:55 -0800 Date: Mon, 14 Dec 1998 10:14:55 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Richard Tobin cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour In-Reply-To: <199812141807.SAA17001@cogsci.ed.ac.uk> 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 Oh *nooooooo*- I went through a very long discussion in NetBSD over this.. I guess I should rewrite that paragraph to make it clearer..... Yes- the count returned to the user application is the number of bytes successfully written. On Mon, 14 Dec 1998, Richard Tobin wrote: > Just a nit about terminology: > > > If the write completing didn't transfer all data that was requested, then > > the residual count is returned to the user application. > > Surely the "residual count" is the number of bytes *not* written, whereas > what is returned to the user is the number successfully written. > > -- Richard > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 10:23:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21573 for freebsd-current-outgoing; Mon, 14 Dec 1998 10:23:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21568 for ; Mon, 14 Dec 1998 10:23:44 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id KAA02933; Mon, 14 Dec 1998 10:23:27 -0800 Date: Mon, 14 Dec 1998 10:23:27 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Bruce Evans cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour In-Reply-To: <199812141802.FAA09572@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think it is a bug for write() to return -1 after sucessfully writing a > short count. physio() does everything right in this area, but write(), > writev(), read() and readv() do everything wrong. >... > > Here `auio.uio_resid != cnt' is true if some i/o was done, and in that > case I think we should return the amount done and discard the error code > (for EIO the next i/o will presumably hit the error immediately and > return EIO), but we only do this for a few types of errors (ones that > don't occur for disks or tapes). > Yes, it could be fixed in this way, I suppose, but I don't believe that an error condition should be signalled- a signification condition that early warning has been reached isn't an error- at least for tape drives. What is it for other character devices? > > >Down the road a little bit would be: > > > > ++ untangling the minor device as behaviour selector so that > > ioctl's would not have to be used to select compression. > > This should be controversial :-). Compression is another type of behaviour. Yes, but we'll leave that one for another day... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 10:39:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23733 for freebsd-current-outgoing; Mon, 14 Dec 1998 10:39:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23717 for ; Mon, 14 Dec 1998 10:39:08 -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 FAA11479; Tue, 15 Dec 1998 05:39:01 +1100 Date: Tue, 15 Dec 1998 05:39:01 +1100 From: Bruce Evans Message-Id: <199812141839.FAA11479@godzilla.zeta.org.au> To: bde@zeta.org.au, mjacob@feral.com Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I think it is a bug for write() to return -1 after sucessfully writing a >> short count. physio() does everything right in this area, but write(), >> writev(), read() and readv() do everything wrong. >>... >> >> Here `auio.uio_resid != cnt' is true if some i/o was done, and in that >> case I think we should return the amount done and discard the error code >> (for EIO the next i/o will presumably hit the error immediately and >> return EIO), but we only do this for a few types of errors (ones that >> don't occur for disks or tapes). >> > >Yes, it could be fixed in this way, I suppose, but I don't believe that an >error condition should be signalled- a signification condition that early >warning has been reached isn't an error- at least for tape drives. What is >it for other character devices? Returning an error (or EOF for the read case) from the strategy routine is the only legitimate way to stop physio(). Ttys return EIO after certain errors and than read/readv/write/writev return the wrong value (-1/EIO) if the EIO occurred after successfully completing some i/o. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 10:49:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24975 for freebsd-current-outgoing; Mon, 14 Dec 1998 10:49:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA24947; Mon, 14 Dec 1998 10:48:53 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA05342; Mon, 14 Dec 1998 17:38:35 +0100 From: Luigi Rizzo Message-Id: <199812141638.RAA05342@labinfo.iet.unipi.it> Subject: dummynet almost in -current To: current@FreeBSD.ORG, net@FreeBSD.ORG Date: Mon, 14 Dec 1998 17:38:35 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG excuse the crosspost, but as the subject says, i think i have committed all the relevant pieces to have dummynet in -current. While i look for the manpages (I could swear i had committed them to -stable, but i cannot find them!) can people have a try ? It should work by simply putting options DUMMYNET options BRIDGE in your kernel config file. Remember you need IPFIREWALL. More info at the usual place http://www.iet.unipi.it/~luigi/ip_dummynet/ dummynet should also work on alpha architecture (I cannot test it) whereas bridging will not because some macros are missing in bridge.h i think. if there is some obvious mistake (my 3.0 disk is a bit outdated) feel free to fix things. Also, if someone wants to compile a LINT kernel with both options that would make me feel safer in adding those options uncommented in LINT. thanks luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 10:57:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25910 for freebsd-current-outgoing; Mon, 14 Dec 1998 10:57:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25905 for ; Mon, 14 Dec 1998 10:57:16 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id KAA03514; Mon, 14 Dec 1998 10:56:58 -0800 (PST) Date: Mon, 14 Dec 1998 10:56:57 -0800 (PST) From: Chris Timmons To: Joel Ray Holveck cc: Mark Huizer , current@FreeBSD.ORG Subject: Re: ^@^@^@^@^@^@^@ (empty pages) in NFS served file. In-Reply-To: <864sqzmfgw.fsf@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see something similar to this when mounting a filesystem on -current from a mid-july -stable using nfsv3. As soon as you fall back to nfsv2 things start working again. For example, mount a /usr/ports homed on a 2.2-stable system to a 3.0-current system and try building something big (eg. XFree86) on the -current system in the mounted filesystem. I'll have to try with -current vs. -current. Some of the -current NFS fixes may have been merged into 2.2 prior to 2.2.8 but I'm not sure and I doubt it. -Chris On 13 Dec 1998, Joel Ray Holveck wrote: > [moved to -current] > > > Hi! quite often I run into problems with NFS served files, containing a > > page of ^@^@^@^@^@^@^@'s instead of actual data (mostly noticed in > > textfiles). > > After checking on the server, it seems the data is valid there. Touch'ing > > it helps sometimes. > > Environment is 2x FreeBSD current, running nfsv3 over udp, on machines > > with softupdates enabled. > > Anyone having the same trouble?? > > Yes, on a small shared mail directory. I assumed that it was equally > corrupt on both client and server, but haven't verified that. All > file access to the file I'm monitoring has been from the same client, > with locking implements (not flock) to prevent simultanious writes. > Same setup as you describe, although I'm about to move the server to > -stable instead. > > Happy hacking, > joelh > > -- > Joel Ray Holveck - joelh@gnu.org > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 10:58:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26093 for freebsd-current-outgoing; Mon, 14 Dec 1998 10:58:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26082 for ; Mon, 14 Dec 1998 10:58:11 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id KAA03076; Mon, 14 Dec 1998 10:57:58 -0800 Date: Mon, 14 Dec 1998 10:57:58 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Bruce Evans cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour In-Reply-To: <199812141839.FAA11479@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > >Yes, it could be fixed in this way, I suppose, but I don't believe that an > >error condition should be signalled- a signification condition that early > >warning has been reached isn't an error- at least for tape drives. What is > >it for other character devices? > > Returning an error (or EOF for the read case) from the strategy routine > is the only legitimate way to stop physio(). No EOF for the write case? > > Ttys return EIO after certain errors and than read/readv/write/writev > return the wrong value (-1/EIO) if the EIO occurred after successfully > completing some i/o. > All I want to see is that the actual number of bytes written gets succesfully propagated back to the application and that the user application can get some kind of warning the physical EOT is near. If you think that fixing the read/readv/write/writev is the way to go, like, solid, man.... It makes state management in the tape driver easier! But here's the kicker- nearly all the time that tapes report early warning, they actually have written all the data. Under the model you're proposing, then no signification will make it back to the user application since the tape driver will complete such commands as having an error (EIO) but all data was 'successfully' (this seems wierd to me) written (and you'll have tossed the EIO). Without the signification, then you'll always write up until physical EOT where you'll get VOLUME OVERFLOW. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 11:24:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29204 for freebsd-current-outgoing; Mon, 14 Dec 1998 11:24:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29143; Mon, 14 Dec 1998 11:24:10 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA21292; Mon, 14 Dec 1998 19:23:59 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id TAA04535; Mon, 14 Dec 1998 19:09:05 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812141909.TAA04535@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Dmitry Valdov cc: Brian Somers , Brian Somers , current@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd) In-reply-to: Your message of "Thu, 12 Nov 1998 11:28:45 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 19:09:05 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The attached message got lost in my intray :-/ Sorry. You say that with debug enabled, ppp thinks everything's ok. Does this mean that ppp is reporting the modem carrier status as being ``online'' ? If this is the case, then I suspect a hardware failure - it's unlikely that the sio driver would report carrier if there isn't any.... all it's doing is an inb() when it's given an ioctl(,TIOCMGET,). > On Thu, 12 Nov 1998, Brian Somers wrote: > > > Date: Thu, 12 Nov 1998 01:12:37 +0000 > > From: Brian Somers > > To: Dmitry Valdov > > Cc: Brian Somers , current@freebsd.org > > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd) > > > > In the log, does it mention something like: > > > > deflink: /dev/cuaa0 doesn't support CD > > No. I've aready said that the problem exists periodicaly (~ in 5-10% cases). > Once again - I'm really sure that modem is configured properly, port/modem > correctly handles CD signal and it connected when script finished.. Just > believe me because I've experience with modems since 1990 :) > > > > > ? This will happen if your modem doesn't show a CD signal at all > > when LCP is started. If this is the case, your modem is > > misconfigured, or isn't connected when your dial/login scripts have > > finished. > > > > > Hi! > > > > > > Just have this problem again. With debug set on. ppp thinks that > > > everything is ok, but modem already hanged up. When I kill it with -1 it > > > says that > > > it normally terminated the connection then exit. > > > I think the workaround is to send ate0 to modem because it sends something > > > to modem and receiving it :) But default config has ATE1 in it. > > > I'm *really* sure that my modem is configured properly and it's not a user > > > error :) > > > > > > What can I do to help you to resolve the problem? I'm using dial-on-demand > > > (pmdemand section) and running ppp with a command ppp -auto pmdemand. > > > > > > > > > On Wed, 11 Nov 1998, Dmitry Valdov wrote: > > > > > > > > > > > > > > > ---------- Forwarded message ---------- > > > > Date: Tue, 10 Nov 1998 21:32:53 +0000 > > > > From: Brian Somers > > > > To: Kris Kennaway > > > > Cc: Dmitry Valdov , Brian Somers , > > > > current@freebsd.org > > > > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c > > > > > > > > > On Tue, 10 Nov 1998, Dmitry Valdov wrote: > > > > > > > > > > > Also there is one more bug - sometimes ppp don't detect carrier lost and > > > > > > stays in open state for a long time. :( > > > > > > > > > > Sorry for the "implicit bug report", Brian, but I've been meaning to track > > > > > this down for a long time and make sure it's not user error. I often see this > > > > > as well - it's noticeable for me because I have ipfw installed and when the > > > > > modem drops carrier I see packets being 'reflected' by the modem's local echo > > > > > (I assume), and bouncing off the ipfw 'incoming address of myself' filter. > > > > > > > > Try ``set log +debug''. You should see the online/offline status of > > > > the link at frequent intervals. If this doesn't agree with your > > > > modem, then you modem may be misconfigured. > > > > > > > > > Kris -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 11:40:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00977 for freebsd-current-outgoing; Mon, 14 Dec 1998 11:40:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00969 for ; Mon, 14 Dec 1998 11:40:20 -0800 (PST) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id MAA17541; Mon, 14 Dec 1998 12:39:56 -0700 (MST) (envelope-from brett@peloton.physics.montana.edu) Date: Mon, 14 Dec 1998 12:39:56 -0700 (MST) From: Brett Taylor To: Matthew Jacob cc: freebsd-current@FreeBSD.ORG Subject: Re: building aout-to-elf? 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, > I did this once, I know, at Ames- but was finally doing feral's system, > and this occurred: > [strip error deleted] Ha - I can answer this one! You have "." in your path somewhere. Remove it or move it to the very end of your path and then the build will go through. BTW, this also used to cause huge havoc while building Window Maker. :-) Brett ****************************************************************** Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ On the eve of his 21st birthday, he set out on his own He was 30 years and runnin' when he found his way back home Ridin' a storm across the mountains and an achin' in his heart Said he came to turn the pages and to make a brand new start To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 11:49:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01904 for freebsd-current-outgoing; Mon, 14 Dec 1998 11:49:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01897 for ; Mon, 14 Dec 1998 11:49:43 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id LAA03278; Mon, 14 Dec 1998 11:49:35 -0800 Date: Mon, 14 Dec 1998 11:49:35 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Brett Taylor cc: freebsd-current@FreeBSD.ORG Subject: Re: building aout-to-elf? 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 D'oh! Okay- thanks! On Mon, 14 Dec 1998, Brett Taylor wrote: > Hi, > > > I did this once, I know, at Ames- but was finally doing feral's system, > > and this occurred: > > > [strip error deleted] > > Ha - I can answer this one! You have "." in your path somewhere. Remove > it or move it to the very end of your path and then the build will go > through. > > BTW, this also used to cause huge havoc while building Window Maker. > :-) > > Brett > ****************************************************************** > Brett Taylor brett@peloton.physics.montana.edu > http://peloton.physics.montana.edu/brett/ > > On the eve of his 21st birthday, he set out on his own > He was 30 years and runnin' when he found his way back home > Ridin' a storm across the mountains and an achin' in his heart > Said he came to turn the pages and to make a brand new start > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 12:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04184 for freebsd-current-outgoing; Mon, 14 Dec 1998 12:03:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lepton.nuc.net (lepton.nuc.net [204.49.61.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04176 for ; Mon, 14 Dec 1998 12:03:36 -0800 (PST) (envelope-from wheelman@nuc.net) Received: from electron (dhcp1.nuc.net [204.49.61.49]) by lepton.nuc.net (8.8.8/8.8.8) with SMTP id OAA01136; Mon, 14 Dec 1998 14:03:03 -0600 (CST) (envelope-from wheelman@nuc.net) From: "Jaime Bozza" To: "Brian Somers" , "Dmitry Valdov" Cc: Subject: RE: cvs commit: src/usr.sbin/ppp ip.c (fwd) Date: Mon, 14 Dec 1998 14:01:17 -0600 Message-ID: <000001be279c$82ba9540$313d31cc@electron.nuc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2232.26 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 In-Reply-To: <199812141909.TAA04535@keep.lan.Awfulhak.org> Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You say that with debug enabled, ppp thinks everything's ok. Does > this mean that ppp is reporting the modem carrier status as being > ``online'' ? > > If this is the case, then I suspect a hardware failure - it's > unlikely that the sio driver would report carrier if there isn't > any.... all it's doing is an inb() when it's given an > ioctl(,TIOCMGET,). While I haven't done much debugging in this area, (haven't had a lot of time recently), I have two systems that started having the same problem once I upgraded from 2.2.7-stable to 2.2.8-stable. (I know these aren't -current, but the merge of the ppp code was brought over for 2.2.8) The first system I upgraded is using an Adtran ISDN "modem" connected through a serial port. The system was working perfectly for about 15 months (since installation) until I upgraded the box to 2.2.8-stable. Now, when the line is dropped, ppp doesn't "see" the carrier lost and just sits there. For a quick fix, I just wrote a script that resets ppp if it can't ping a known server on our end. At first I thought it could be hardware failure until I updated another 2.2.7-stable box to 2.2.8-stable. (This one is using a USR Courier V.90 modem and has been working fine for about a year.) When the same thing happened (modem dropped carrier, ppp didn't pick it up) I started to think it wasn't a hardware failure. It's unlikely that both of these systems started failing at the same time, especially when the problem happened immediately after upgrading to 2.2.8-stable. Regardless, I'd be happy to run specific debug logs and send them to you if you want. Jaime Bozza Nucleus Communications, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 12:11:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05151 for freebsd-current-outgoing; Mon, 14 Dec 1998 12:11:41 -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 MAA05110; Mon, 14 Dec 1998 12:11:32 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA03531; Mon, 14 Dec 1998 12:00:00 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdVV3523; Mon Dec 14 19:59:50 1998 Message-ID: <36756E2E.2781E494@whistle.com> Date: Mon, 14 Dec 1998 11:59:42 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Johan Granlund CC: Poul-Henning Kamp , current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan Granlund wrote: > > Is this a implementation of SYSV Streams? > > /Johan > > On Sun, 13 Dec 1998, Julian Elischer wrote: > > > how about porting the whole shebang to whistle's 'streams' > > replacement.. > > we could probably supply the frame relay and ppp packetizer nodes along > > with the framework and tools... > > s > > No it's something that lives in the same ecological niche, but is different. it's not based on a 'stack' but instead allows an arbitrary network of processing elements to be created. I released it about 12 months ago but it needs some cleaning.. :-) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 12:29:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07583 for freebsd-current-outgoing; Mon, 14 Dec 1998 12:29:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07563; Mon, 14 Dec 1998 12:29:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id VAA06202; Mon, 14 Dec 1998 21:29:03 +0100 (CET) Date: Mon, 14 Dec 1998 21:29:03 +0100 Message-ID: <6200.913667343.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: testers wanted: E1 / Nx64 interface card for FreeBSD. MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: undisclosed-recipients:; ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message Subject: testers wanted: E1 / Nx64 interface card for FreeBSD. From: Poul-Henning Kamp Date: Mon, 14 Dec 1998 21:29:03 +0100 Message-ID: <6200.913667343@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Bcc: Blind Distribution List: ; I am working on a driver for a E1/Nx64 interface card for FreeBSD. The card is PCI bus-mastering, can do 31 HDLC channels, and has a balanced E1 interface (G.703 120 Ohm). A T1 version is possible if there is sufficient interest (send me email!). The driver exists and performs well, but the framework in the FreeBSD kernel needs much more work before support for this kind of stuff can be called "serious". To further this cause, I am offering the card and driver (binary) for USD1100 (or DKR7000) to any interested and qualified testers. The majority of the profit from this sale will go into improving the FreeBSD kernels support for serial line routing use, a minor part of the profit will go into making sure my family don't starve in the meantime. The card is currently NOT approved for connection to any networks anywhere, so use it only where you are allowed to (by applicable rules and/or morals). If there is sufficient interest, I will also be interested in finding a company who can produce and possibly market these cards for me. I don't really want to be in the hardware business if I can avoid it. Send me email if you are interested in any of this. Poul-Henning -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 12:39:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08849 for freebsd-current-outgoing; Mon, 14 Dec 1998 12:39:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.whistle.com (gatekeeper.whistle.com [207.76.204.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08837 for ; Mon, 14 Dec 1998 12:39:25 -0800 (PST) (envelope-from julian@whistle.com) Received: (from smap@localhost) by gatekeeper.whistle.com (8.8.8/8.8.7) id MAA04384 for ; Mon, 14 Dec 1998 12:39:16 -0800 (PST) (envelope-from julian@whistle.com) Received: from alpo.whistle.com(unknown 207.76.204.38) by gatekeeper.whistle.com via smap (V2.0) id xma004377; Mon, 14 Dec 98 12:38:50 -0800 Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA04528; Mon, 14 Dec 1998 12:24:05 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdno4519; Mon Dec 14 20:24:03 1998 Message-ID: <367573DF.3F54BC7E@whistle.com> Date: Mon, 14 Dec 1998 12:23:59 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: The Hermit Hacker CC: freebsd-current@FreeBSD.ORG Subject: Re: System "crashed", serial console giving garbage... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > > Morning... > > About 15min oago or so, my system stop'd working :( If I connect > through the serial console, I see the following, after hitting return: > > pagecorp> attach s0 > Trying 209.47.145.10 ... > Connected - Escape character is '^]'. > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > > Now, I could understand it crashing and just freezing, but issuign > garbage? It's dropped into the debugger and this is the GDB robot trying to talk to it's controller. > > I have nothing else to debug with at this point, and have to wait for > someone to head downtown to reboot the machine, but figured I'd try to > start *somewhere* :( > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 12:50:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09927 for freebsd-current-outgoing; Mon, 14 Dec 1998 12:50:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from linteuto.teuto.de (linteuto.teuto.de [194.77.23.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09847; Mon, 14 Dec 1998 12:49:54 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (root@rumolt.teuto.de [212.8.203.81]) by linteuto.teuto.de (8.8.7/8.8.7) with ESMTP id VAA11819; Mon, 14 Dec 1998 21:49:48 +0100 Received: (from martin@localhost) by rumolt.teuto.de (8.8.8/8.8.7) id VAA15362; Mon, 14 Dec 1998 21:48:34 +0100 (MET) From: Martin Husemann Message-Id: <199812142048.VAA15362@rumolt.teuto.de> Subject: Re: if_sppp is BROKEN!!! To: johan@granlund.nu (Johan Granlund) Date: Mon, 14 Dec 1998 21:48:34 +0100 (MET) Cc: julian@whistle.com, phk@FreeBSD.ORG, current@FreeBSD.ORG, isdn@FreeBSD.ORG In-Reply-To: from "Johan Granlund" at Dec 14, 98 06:58:57 pm Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4 PL24] 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 > Is this a implementation of SYSV Streams? > > /Johan STREAMS (the SYSV heavy weight implementation) or streams (the concept)? Is it real? Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 12:58:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11084 for freebsd-current-outgoing; Mon, 14 Dec 1998 12:58:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11075 for ; Mon, 14 Dec 1998 12:58:50 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id VAA04247; Mon, 14 Dec 1998 21:43:49 +0100 (CET) Message-Id: <199812142043.VAA04247@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com cc: Greg Lehey , FreeBSD current users Subject: Re: (Re: Can't access tapes with scsi_sa.c r1.7) (LONG) Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 13 Dec 1998 23:25:39 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 21:43:48 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > > >Well, I've been looking over this, and a preliminary check seems to >indicate to me that the driver is, in fact, doing what it is supposed to >do. Now, wait, don't start throwing things yet.. :-) > >The simple fix for all of you is to explicitly set variable mode (mt >blocksize 0) on your tape device *if you want it to be in variable record >length mode*, but see. > YES !!! that makes it work. Thanks for the suggestion. If you can make it work by default that would be even better. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 13:16:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13520 for freebsd-current-outgoing; Mon, 14 Dec 1998 13:16:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13498 for ; Mon, 14 Dec 1998 13:16:53 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40374>; Tue, 15 Dec 1998 08:15:50 +1100 Date: Tue, 15 Dec 1998 08:16:29 +1100 From: Peter Jeremy Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour To: freebsd-current@FreeBSD.ORG Cc: mjacob@feral.com Message-Id: <98Dec15.081550est.40374@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > If EARLY WARNING recognitions is not enabled, then detection of EOM (as > reported in SCSI Sense Data with an EOM indicator) causes the write oper- > ation to be flagged with I/O error (EIO). This has the effect for the > user application of not knowing actually how many bytes were written > (since the return of the read(2) system call is set to -1). ^^^^^^^ presumably write(2) I also consider this behaviour to be a bug. Unfortunately, the Unix system call semantics don't provide any mechanism to report why a read or write terminated early. > the next attempt to write (if that is the next action the user application > takes) Does this mean that the EOM indication will be lost under some circumstances? Obviously is the tape is back-spaced, rewound or closed, the EOM should be cleared. Otherwise, I think the EOM should be kept. > is immediately completed with no data transferred, and a residual > returned to the user application indicating that no data was transferred. > This is the traditional UNIX EOF indication. It is for read(2). write(2) does not mention returning 0 to mean EOF. Do all applications obey this convention? > In either mode of operation, the driver does not prohibit the user appli- > cation from writing more data, if chooses to do so. If I've understood this correctly, the behaviour will be as follows (ignoring tape blocksize and blocking factor issues), assuming we are 512 bytes before logical EOM and 2048 bytes before physical EOM: a) EARLY WARNING not enabled: write(fd, buf, 1024) returns -1, errno = EIO [512 bytes actually written] [tape now at logical EOM] write(fd, buf, 1024) returns 1024 write(fd, buf, 1024) returns -1, errno = EIO [512 bytes actually written] [tape now at physical EOM] b) EARLY WARNING enabled: write(fd, buf, 1024) returns 512 [tape now at logical EOM] write(fd, buf, 1024) returns 0 [indicating logical EOM] write(fd, buf, 1024) returns 1024 write(fd, buf, 1024) returns -1, errno = EIO [512 bytes actually written] [tape now at physical EOM] In both cases, I would prefer to see the following behaviour where the write returns -1 but actually writes something: write(fd, buf, 1024) returns 512 [tape now at logical/physical EOM] write(fd, buf, 1024) returns -1, errno = EIO or ENOSPC The early warning behaviour is definitely preferable. The issue of filemarks has not been addressed. Presumably, the system will try to write FM's, but may fail if the tape is beyond EOM. Will this be reported at all? Does it matter? Presumably the behaviour of read(2) is unaffected by logical EOM: read(2) will return normally until EOF - indicated by a filemark or physical EOT. > However, the expected user application behaviour (in common > with other systems) is to close the tape and rewind and request another > tape upon the receipt of the first EOM indicator. If the application's logical blocksize is larger than the tape blocksize, the application will probably need to continue writing until it has completed a logical block. It may also need to write an application-dependent 'continued on next volume' block. One final point: How do you enable/disable early warning? Is there any point in not always enabling early warning? Should the system default to early warning off and tape-aware applications can enable it (presumably via an ioctl)? Will it be user-selectable via a bit in the minor device number? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 13:17:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13708 for freebsd-current-outgoing; Mon, 14 Dec 1998 13:17:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13669; Mon, 14 Dec 1998 13:17:39 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t3o29p14.telia.com [194.236.215.14]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id WAA00940; Mon, 14 Dec 1998 22:12:40 +0100 Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.1/8.9.1) with ESMTP id WAA10547; Mon, 14 Dec 1998 22:12:29 +0100 (CET) (envelope-from johan@granlund.nu) Date: Mon, 14 Dec 1998 22:12:29 +0100 (CET) From: Johan Granlund To: Julian Elischer cc: Poul-Henning Kamp , =?ISO-8859-1?Q?Lars_=C5kerling?= , current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! In-Reply-To: <36756E2E.2781E494@whistle.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, 14 Dec 1998, Julian Elischer wrote: > Johan Granlund wrote: > > > > Is this a implementation of SYSV Streams? > > > > /Johan > > > > On Sun, 13 Dec 1998, Julian Elischer wrote: > > > > > how about porting the whole shebang to whistle's 'streams' > > > replacement.. > > > we could probably supply the frame relay and ppp packetizer nodes along > > > with the framework and tools... > > > s > > > > > No it's something that lives in the same ecological niche, but is > different. > > it's not based on a 'stack' but instead allows an arbitrary network of > processing elements to be created. > > I released it about 12 months ago but it needs some cleaning.. > :-) > > julian This is really interesting! One of the concepts i liked in SYSV (ducking for cover) was streams and its ability to chain together modules to process a datastream. If it's coupled with kld to dynamically load/unload modules i think you have something _very_ good. That network thing. Can a module route a package thru different modules based on contents and state? /Johan > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 13:23:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14494 for freebsd-current-outgoing; Mon, 14 Dec 1998 13:23:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org ([142.177.186.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14484 for ; Mon, 14 Dec 1998 13:23:00 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id RAA29810; Mon, 14 Dec 1998 17:22:51 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 14 Dec 1998 17:22:51 -0400 (AST) From: The Hermit Hacker To: Julian Elischer cc: freebsd-current@FreeBSD.ORG Subject: Re: System "crashed", serial console giving garbage... In-Reply-To: <367573DF.3F54BC7E@whistle.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, 14 Dec 1998, Julian Elischer wrote: > The Hermit Hacker wrote: > > > > Morning... > > > > About 15min oago or so, my system stop'd working :( If I connect > > through the serial console, I see the following, after hitting return: > > > > pagecorp> attach s0 > > Trying 209.47.145.10 ... > > Connected - Escape character is '^]'. > > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > > $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef > > > > Now, I could understand it crashing and just freezing, but issuign > > garbage? > > It's dropped into the debugger and this is the GDB robot > trying to talk to it's controller. Okay..why did it do that? I don't have GDB_REMOTE_CHAT enabled in my kernel :( Is there any way of breaking out of that when it starts? Any way of disabling it using sysctl or some such? 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 Mon Dec 14 13:44:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16197 for freebsd-current-outgoing; Mon, 14 Dec 1998 13:41:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16192 for ; Mon, 14 Dec 1998 13:41:27 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id NAA03666; Mon, 14 Dec 1998 13:38:16 -0800 Date: Mon, 14 Dec 1998 13:38:16 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Gary Jennejohn cc: FreeBSD current users Subject: Re: (Re: Can't access tapes with scsi_sa.c r1.7) (LONG) In-Reply-To: <199812142043.VAA04247@peedub.muc.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 Mon, 14 Dec 1998, Gary Jennejohn wrote: > Matthew Jacob writes: > > > > > >Well, I've been looking over this, and a preliminary check seems to > >indicate to me that the driver is, in fact, doing what it is supposed to > >do. Now, wait, don't start throwing things yet.. :-) > > > >The simple fix for all of you is to explicitly set variable mode (mt > >blocksize 0) on your tape device *if you want it to be in variable record > >length mode*, but see. > > > > YES !!! that makes it work. Thanks for the suggestion. Good! > > If you can make it work by default that would be even better. > Yes, I have prototype code not checked in that forces variable mode except for some specific devices (reintroduces also the SA_QUIRK_FIXED and SA_QUIRK_VARIABLE for scsi_sa) -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 14:29:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23008 for freebsd-current-outgoing; Mon, 14 Dec 1998 14:29:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22997 for ; Mon, 14 Dec 1998 14:28:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id OAA03807; Mon, 14 Dec 1998 14:28:31 -0800 Date: Mon, 14 Dec 1998 14:28:31 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Peter Jeremy cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour In-Reply-To: <98Dec15.081550est.40374@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Matthew Jacob wrote: > > If EARLY WARNING recognitions is not enabled, then detection of EOM (as > > reported in SCSI Sense Data with an EOM indicator) causes the write oper- > > ation to be flagged with I/O error (EIO). This has the effect for the > > user application of not knowing actually how many bytes were written > > (since the return of the read(2) system call is set to -1). > ^^^^^^^ presumably write(2) D'oh! Yes... > I also consider this behaviour to be a bug. Unfortunately, the Unix > system call semantics don't provide any mechanism to report why a read > or write terminated early. That's why I want to use the 'short write' to be the signifcator. > > > the next attempt to write (if that is the next action the user application > > takes) > Does this mean that the EOM indication will be lost under some circumstances? > Obviously is the tape is back-spaced, rewound or closed, the EOM should > be cleared. Otherwise, I think the EOM should be kept. If the user application does anything *but* a write following the latching of state, that state should clear. I should note that even if logical EOM does not continue to be reported (which as far as I can remeber it does continue to be reported for all the drives I've tried this on) you still have hard EOT to stop you from running off the end of the tape (*except* for those few drives which don't do this- 1/2" Reels are the only ones that come to mind). > > > is immediately completed with no data transferred, and a residual > > returned to the user application indicating that no data was transferred. > > This is the traditional UNIX EOF indication. > It is for read(2). write(2) does not mention returning 0 to mean EOF. Do > all applications obey this convention? Apparently not. My recollections over a long period of time have made me believe that this behaviour is symmetric, but other's do not atree. > > > In either mode of operation, the driver does not prohibit the user appli- > > cation from writing more data, if chooses to do so. > > If I've understood this correctly, the behaviour will be as follows > (ignoring tape blocksize and blocking factor issues), assuming we are > 512 bytes before logical EOM and 2048 bytes before physical EOM: > > a) EARLY WARNING not enabled: > write(fd, buf, 1024) returns -1, errno = EIO [512 bytes actually written] > [tape now at logical EOM] > write(fd, buf, 1024) returns 1024 > write(fd, buf, 1024) returns -1, errno = EIO [512 bytes actually written] > [tape now at physical EOM] > > b) EARLY WARNING enabled: > write(fd, buf, 1024) returns 512 > [tape now at logical EOM] > write(fd, buf, 1024) returns 0 [indicating logical EOM] > write(fd, buf, 1024) returns 1024 > write(fd, buf, 1024) returns -1, errno = EIO [512 bytes actually written] > [tape now at physical EOM] The actual behaviour is more likely to be (assuming the app doesn't stop) a) EW not enabled (current behaviour) i) write(fd, buf, 1024) returns -1, errno = EIO [1024 bytes written] ii) write(fd, buf, 1024) returns -1, errno = EIO [1024 bytes written] iii) write(fd, buf, 1024) returns -1, errno = EIO [0 bytes written] This is because typically all the bytes transfer, but there is a CHECK CONDITION associated with the operation which notes that EOM has been reached (usually with the NO ADDITIONAL SENSE sense key). It isn't until VOLUME OVERFLOW (3rd write) that bytes moved stops. I should note that the pre-CAM driver actually stopped after #i, and that if sastart in the top half of the current CAM driver paid attention to the SA_FLAG_TAPE_MOUNTED flag it would also stop (but it doesn't). There's a slight difference also if FIXED mode is set- if FIXED mode is set, an EIO is deferred to the next I/O operation. b) I am proposing that behaviour be + write(fd, buf, 1024) returns N, where N is the amount actually written + If, and only if N was 1024 (all bytes written) (and EOM had been seen), the next write(fd, buf, 1024) returns 0 (0 bytes written). So, assuming the usual tape drive behaviour, the scenario as above would be: i) write(fd, buf, 1024) returns 1024 (1024 bytes written) [ EOM flagged ] ii) write(fd, buf, 1024) returns 0 (zero bytes moved) [ EOM cleared ] iii) write(fd, buf, 1024) returns 1024 (1024 bytes written) iv) write(fd, buf, 1024) will return -1 (ENOSPC or EIO - I don't care). It really doesn't matter what the app does at #iv- you've hit hard eot and can't do anything but rewind or space backwards. It is expected that when #ii occurs the application could (in fact) write a trailer record or two, but is expected to close the device or otherwise cause a terminating filemark to be written and then rewind or do something else. Alternatively, if the drive reports EOM *and* reports that it didn't write all that was requested, then step #ii is ommitted entirely (as the goal of signification has been met). Further, let's say we have a broken or stupid drive, and it doesn't even report EOM (just that it didn't write all that was requested)- this acts (or should act) as a significator to the user application (there's absolutely no reason for a tape device, or for that matter (sez Bob Snively of the ANSI SCSI committee) for any device, to not write all that was requested *unless* some limiting condition (like physical impossibility) occurs). > > In both cases, I would prefer to see the following behaviour where the > write returns -1 but actually writes something: > write(fd, buf, 1024) returns 512 > [tape now at logical/physical EOM] > write(fd, buf, 1024) returns -1, errno = EIO or ENOSPC > > The early warning behaviour is definitely preferable. I still am bothered about reporting errors which aren't 'errors'. If I write 1024 bytes to a tape and I get back two pieces of information- an EIO and a notification that I wrote some data, which do you think I'll believe? > The issue of filemarks has not been addressed. Presumably, the system > will try to write FM's, but may fail if the tape is beyond EOM. Will > this be reported at all? Does it matter? If you're before physical EOT you should be able to write filemarks (this is why you need to signify to the application that physical EOT is approaching). > Presumably the behaviour of read(2) is unaffected by logical EOM: read(2) > will return normally until EOF - indicated by a filemark or physical EOT. End of recorded media (and/or filemark), yes. > > > However, the expected user application behaviour (in common > > with other systems) is to close the tape and rewind and request another > > tape upon the receipt of the first EOM indicator. > > If the application's logical blocksize is larger than the tape > blocksize, the application will probably need to continue writing > until it has completed a logical block. It may also need to write an > application-dependent 'continued on next volume' block. Yes. > > One final point: How do you enable/disable early warning? Is there > any point in not always enabling early warning? Should the system > default to early warning off and tape-aware applications can enable it > (presumably via an ioctl)? Will it be user-selectable via a bit in > the minor device number? > For NetBSD this was left as a config option (which I thought was stupid). I'd like to make this behaviour the default. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 14:33:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23533 for freebsd-current-outgoing; Mon, 14 Dec 1998 14:33:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.amis.net (server.amis.net [195.10.52.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23526 for ; Mon, 14 Dec 1998 14:33:17 -0800 (PST) (envelope-from blaz@gold.amis.net) Received: (from uucp@localhost) by server.amis.net (8.8.8/8.8.8) with UUCP id XAA18854; Mon, 14 Dec 1998 23:32:48 +0100 (CET) Received: from localhost (blaz@localhost) by gold.amis.net (8.9.1/8.8.8) with ESMTP id XAA03421; Mon, 14 Dec 1998 23:30:58 +0100 (CET) Date: Mon, 14 Dec 1998 23:30:58 +0100 (CET) From: Blaz Zupan To: Brett Taylor cc: Matthew Jacob , freebsd-current@FreeBSD.ORG Subject: Re: building aout-to-elf? 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 > Ha - I can answer this one! You have "." in your path somewhere. Remove > it or move it to the very end of your path and then the build will go > through. I can't find any mention of this on the "make world" tutorial at www.nothing-going-on.demon.co.uk. Of course, I could be blind. Nik? Blaz Zupan, blaz@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 15:04:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27198 for freebsd-current-outgoing; Mon, 14 Dec 1998 15:04:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27193 for ; Mon, 14 Dec 1998 15:04:09 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id MAA18507; Tue, 15 Dec 1998 12:03:58 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id MAA17703; Tue, 15 Dec 1998 12:03:57 +1300 (NZDT) Message-ID: <19981215120357.B11837@clear.co.nz> Date: Tue, 15 Dec 1998 12:03:57 +1300 From: Joe Abley To: freebsd-current@FreeBSD.ORG Cc: jabley@clear.co.nz Subject: modification to exec in the kernel? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We want to allow people to upload scripts to provide cgi hosting for our web hosting product. However, we are nervous about allowing people to upload arbitrary binaries, even though they will be run chrooted. We would also like to provide telnet access - but again, we don't want people to hang around running their own binaries. A controlled set of binaries will be installed for users to play with instead. Telnet and ftp access is provided within a chrooted filesystem, and the web server will exec scripts with uid set to the user's uid. How about a kernel option which, when enabled, restricts the use of exec for users in a particular group? With this option set, "execve will always fail for a user in the restricted group if the binary to be run is owned by the user who is running it." This means that we don't have to worry about users uploading their own binaries any more - they won't be able to run them anyway. In fact, we bill them for the disk space they use, so the more statically-linked exploits they try to upload the better :) Here is a patch to sys/kern/kern_exec.c which, if the macro RESTRICT_EXEC_GROUP exists, restricts execve in the manner mentioned for the restricted gid RESTRICT_EXEC_GROUP. Whaddaya think? Joe [$Id: kern_exec.c,v 1.88 1998/10/28 13:36:58 dg Exp $] 256,257c256,257 < if ((attr.va_mode & VSUID && p->p_ucred->cr_uid != attr.va_uid || < attr.va_mode & VSGID && p->p_ucred->cr_gid != attr.va_gid) && --- > if ((attr.va_mode & VSUID && p->p_cred->cr_uid != attr.va_uid || > attr.va_mode & VSGID && p->p_cred->cr_gid != attr.va_gid) && 686a687,698 > > #ifdef RESTRICT_EXEC_GROUP > /* > * If the invoking user has gid RESTRICT_EXEC_GROUP, check ownership > * of the file and deny execution if owned by the invoker. > */ > if ((p->p_ucred->p_rgid == (gid_t) RESTRICT_EXEC_GROUP || \ > p->p_ucred->p_svgid == (gid_t) RESTRICT_EXEC_GROUP) && \ > (p->p_ucred->p_ruid == attr->va_uid || \ > p->p_ucred->p_psvuid == attr->va_uid)) \ > return(ENOEXEC); > #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 15:10:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27614 for freebsd-current-outgoing; Mon, 14 Dec 1998 15:10:11 -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 PAA27505; Mon, 14 Dec 1998 15:09:54 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA11184; Mon, 14 Dec 1998 15:03:18 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdY11180; Mon Dec 14 23:03:08 1998 Message-ID: <36759929.ABD322C@whistle.com> Date: Mon, 14 Dec 1998 15:03:05 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Johan Granlund CC: Poul-Henning Kamp , Lars ?kerling , current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan Granlund wrote: > > On Mon, 14 Dec 1998, Julian Elischer wrote: > > > Johan Granlund wrote: > > > > > > Is this a implementation of SYSV Streams? > > > > > > /Johan > > > > > > On Sun, 13 Dec 1998, Julian Elischer wrote: > > > > > > > how about porting the whole shebang to whistle's 'streams' > > > > replacement.. > > > > we could probably supply the frame relay and ppp packetizer nodes along > > > > with the framework and tools... > > > > s > > > > > > > > No it's something that lives in the same ecological niche, but is > > different. > > > > it's not based on a 'stack' but instead allows an arbitrary network of > > processing elements to be created. > > > > I released it about 12 months ago but it needs some cleaning.. > > :-) > > > > julian > > This is really interesting! > One of the concepts i liked in SYSV (ducking for cover) was streams and > its ability to chain together modules to process a datastream. > If it's coupled with kld to dynamically load/unload modules i think > you have something _very_ good. > > That network thing. Can a module route a package thru different modules > based on contents and state? you set up a 'web' of nodes to your own specification.. each node decides which connected node a packet will be routed out to.. you could (if you id it wrong, get an infinite loop with a packet looping around and around, but it's assumed that people setting this up wouldn't do that :-) we've had this code in heavy production for 2 years now. julian > > /Johan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 15:16:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28576 for freebsd-current-outgoing; Mon, 14 Dec 1998 15:16:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27390; Mon, 14 Dec 1998 15:07:41 -0800 (PST) (envelope-from jmb) Date: Mon, 14 Dec 1998 15:07:41 -0800 (PST) Message-Id: <199812142307.PAA27390@hub.freebsd.org> From: "Jonathan M. Bresler" To: johan@granlund.nu CC: julian@whistle.com, phk@FreeBSD.ORG, lars@akerlings.t.se, current@FreeBSD.ORG, isdn@FreeBSD.ORG In-reply-to: (message from Johan Granlund on Mon, 14 Dec 1998 22:12:29 +0100 (CET)) Subject: Re: if_sppp is BROKEN!!! References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Mon, 14 Dec 1998 22:12:29 +0100 (CET) > From: Johan Granlund > > This is really interesting! > One of the concepts i liked in SYSV (ducking for cover) was streams and > its ability to chain together modules to process a datastream. > If it's coupled with kld to dynamically load/unload modules i think > you have something _very_ good. > > That network thing. Can a module route a package thru different modules > based on contents and state? the idea of streams is wonderful, the realization is costly. each layer added (or module pushed) slows down processing and hurts throughput. ritchie developed streams for serial, if i remember correctly. streams was then applied to networks. there is an RFC about layering being bad for networking and the relative performance of NIT vs BPF prove the case. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 15:30:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29884 for freebsd-current-outgoing; Mon, 14 Dec 1998 15:30:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29860; Mon, 14 Dec 1998 15:30:15 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id AAA06843; Tue, 15 Dec 1998 00:23:01 +0100 (CET) To: "Jonathan M. Bresler" cc: johan@granlund.nu, julian@whistle.com, lars@akerlings.t.se, current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! In-reply-to: Your message of "Mon, 14 Dec 1998 15:07:41 PST." <199812142307.PAA27390@hub.freebsd.org> Date: Tue, 15 Dec 1998 00:23:00 +0100 Message-ID: <6841.913677780@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812142307.PAA27390@hub.freebsd.org>, "Jonathan M. Bresler" write s: >> Date: Mon, 14 Dec 1998 22:12:29 +0100 (CET) >> From: Johan Granlund >> >> This is really interesting! >> One of the concepts i liked in SYSV (ducking for cover) was streams and >> its ability to chain together modules to process a datastream. >> If it's coupled with kld to dynamically load/unload modules i think >> you have something _very_ good. >> >> That network thing. Can a module route a package thru different modules >> based on contents and state? > > the idea of streams is wonderful, the realization is costly. each > layer added (or module pushed) slows down processing and hurts > throughput. ritchie developed streams for serial, if i remember > correctly. streams was then applied to networks. there is an RFC > about layering being bad for networking and the relative performance > of NIT vs BPF prove the case. But with that said, there is still something to be said for modular and well defined interfaces. But streams ? No. They were great for async protocols, but they fail badly for packet stuff. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 15:31:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00267 for freebsd-current-outgoing; Mon, 14 Dec 1998 15:31:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00252 for ; Mon, 14 Dec 1998 15:31:55 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id RAA17203; Mon, 14 Dec 1998 17:31:43 -0600 (CST) From: Kevin Day Message-Id: <199812142331.RAA17203@home.dragondata.com> Subject: Re: modification to exec in the kernel? In-Reply-To: <19981215120357.B11837@clear.co.nz> from Joe Abley at "Dec 15, 1998 12: 3:57 pm" To: jabley@clear.co.nz (Joe Abley) Date: Mon, 14 Dec 1998 17:31:43 -0600 (CST) Cc: freebsd-current@FreeBSD.ORG, jabley@clear.co.nz X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > We want to allow people to upload scripts to provide cgi hosting for our > web hosting product. However, we are nervous about allowing people to > upload arbitrary binaries, even though they will be run chrooted. > > We would also like to provide telnet access - but again, we don't want people > to hang around running their own binaries. A controlled set of binaries > will be installed for users to play with instead. > > Telnet and ftp access is provided within a chrooted filesystem, and the > web server will exec scripts with uid set to the user's uid. > > How about a kernel option which, when enabled, restricts the use of exec > for users in a particular group? > > With this option set, "execve will always fail for a user in the restricted > group if the binary to be run is owned by the user who is running it." > > This means that we don't have to worry about users uploading their own > binaries any more - they won't be able to run them anyway. In fact, we bill > them for the disk space they use, so the more statically-linked exploits > they try to upload the better :) > > Here is a patch to sys/kern/kern_exec.c which, if the macro > RESTRICT_EXEC_GROUP exists, restricts execve in the manner mentioned for > the restricted gid RESTRICT_EXEC_GROUP. > > Whaddaya think? > > > Joe I dunno if this fits your requirements or not, but in the past where this was necessary, i simply put these user's home directories on a volume mounted with 'noexec'. Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 15:46:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02327 for freebsd-current-outgoing; Mon, 14 Dec 1998 15:46:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02318 for ; Mon, 14 Dec 1998 15:46:19 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id XAA03022; Mon, 14 Dec 1998 23:46:11 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id XAA12050; Mon, 14 Dec 1998 23:47:24 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812142347.XAA12050@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jaime Bozza" cc: "Brian Somers" , "Dmitry Valdov" , current@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd) In-reply-to: Your message of "Mon, 14 Dec 1998 14:01:17 CST." <000001be279c$82ba9540$313d31cc@electron.nuc.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 23:47:24 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You say that with debug enabled, ppp thinks everything's ok. Does > > this mean that ppp is reporting the modem carrier status as being > > ``online'' ? > > > > If this is the case, then I suspect a hardware failure - it's > > unlikely that the sio driver would report carrier if there isn't > > any.... all it's doing is an inb() when it's given an > > ioctl(,TIOCMGET,). > > While I haven't done much debugging in this area, (haven't had a lot of > time recently), I have two systems that started having the same problem > once I upgraded from 2.2.7-stable to 2.2.8-stable. (I know these > aren't -current, but the merge of the ppp code was brought over for 2.2.8) > > The first system I upgraded is using an Adtran ISDN "modem" connected > through a serial port. The system was working perfectly for about 15 > months (since installation) until I upgraded the box to 2.2.8-stable. Now, > when the line is dropped, ppp doesn't "see" the carrier lost and just sits > there. For a quick fix, I just wrote a script that resets ppp if it can't > ping a known server on our end. > > At first I thought it could be hardware failure until I updated another > 2.2.7-stable box to 2.2.8-stable. (This one is using a USR Courier V.90 > modem and has been working fine for about a year.) When the same thing > happened (modem dropped carrier, ppp didn't pick it up) I started to think > it wasn't a hardware failure. It's unlikely that both of these systems > started failing at the same time, especially when the problem happened > immediately after upgrading to 2.2.8-stable. > > Regardless, I'd be happy to run specific debug logs and send them to you if > you want. That's what I'm asking :-) Can you enable debug logging (``set log +debug'') and tell me what happens WRT the online/offline messages and what ``show modem'' says ? Cheers. > Jaime Bozza > Nucleus Communications, Inc. > > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 15:48:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02582 for freebsd-current-outgoing; Mon, 14 Dec 1998 15:48:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02572 for ; Mon, 14 Dec 1998 15:48:31 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id MAA04930; Tue, 15 Dec 1998 12:48:19 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id MAA29605; Tue, 15 Dec 1998 12:48:19 +1300 (NZDT) Message-ID: <19981215124818.A22526@clear.co.nz> Date: Tue, 15 Dec 1998 12:48:18 +1300 From: Joe Abley To: Kevin Day Cc: freebsd-current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: modification to exec in the kernel? References: <19981215120357.B11837@clear.co.nz> <199812142331.RAA17203@home.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812142331.RAA17203@home.dragondata.com>; from Kevin Day on Mon, Dec 14, 1998 at 05:31:43PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 14, 1998 at 05:31:43PM -0600, Kevin Day wrote: > > I dunno if this fits your requirements or not, but in the past where this > was necessary, i simply put these user's home directories on a volume > mounted with 'noexec'. I looked at that; however, remember the users will have chrooted access to their directories, and within the chrooted tree will be /usr and descendants containing controlled binaries (owned by someone else, e.g. "root") like perl, awk, sh, etc. We were planning to keep them on the same filesystem, and use hard links from the chrooted trees to allow them to appear to the users. The alternative I looked at was to mount the chrooted /usr read-only once for each user into their private tree without noexec, and mount the filesystem containing the user-modifiable stuff with noexec. However, this means we have to mount the same device hundreds of times simultaneously on the same box (or else maintain separate /usr trees on separate filesystems for each user). This all looks like mount bloat. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 16:49:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11509 for freebsd-current-outgoing; Mon, 14 Dec 1998 16:49:29 -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 QAA11488 for ; Mon, 14 Dec 1998 16:49:22 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA26526; Tue, 15 Dec 1998 11:18:50 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <98Dec15.081550est.40374@border.alcanet.com.au> Date: Tue, 15 Dec 1998 11:18:40 +1030 (CST) From: "Daniel O'Connor" To: Peter Jeremy Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour Cc: mjacob@feral.com, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Dec-98 Peter Jeremy wrote: > I also consider this behaviour to be a bug. Unfortunately, the Unix > system call semantics don't provide any mechanism to report why a read > or write terminated early. Actually, general bitch time, they don't provide ANY sort of extended error information which sucks.. errno is fine until you get a function which overloads a single errno value with lots of meanings :( Hmm.. maybe 'errno_callspec' ;) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 16:58:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12219 for freebsd-current-outgoing; Mon, 14 Dec 1998 16:58:30 -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 QAA12213 for ; Mon, 14 Dec 1998 16:58:26 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA27527; Tue, 15 Dec 1998 11:27:52 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA15555; Tue, 15 Dec 1998 11:27:51 +1030 (CST) Message-ID: <19981215112751.S17075@freebie.lemis.com> Date: Tue, 15 Dec 1998 11:27:51 +1030 From: Greg Lehey To: Nick Hibma , FreeBSD current mailing list Cc: Lennart Augustsson , USB BSD list Subject: Re: double CVS repositories References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Nick Hibma on Mon, Dec 14, 1998 at 02:20:31PM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 14 December 1998 at 14:20:31 +0100, Nick Hibma wrote: > > Anyone working on a project in which 2 entirely different repositories > are being kept up to date simultaneously? Well, no--I have 3 (FreeBSD src/doc/ports, gnats, XFree86). > The problem we have is that we (Lennart, NetBSD and myself, FreeBSD) > would like to have a CVS repository to which we commit changes to the > USB source, but at the same time would like to commit things to the > repository of the OS as well. > > Now this would be possible by writing a number of scripts that get > executed when committing to a local repository. But that does not sound > very sexy. There's not very much to do. About the only thing I've done is to set CVSROOT to 'unassigned' (which says nothing to cvs, but plenty to anybody who gets a message like: # cvs update cvs [update aborted]: CVSROOT unassigned must be an absolute pathname > Anyone any better solutions to this problem? Anyone any working examples > we could copy? There's really nothing to it. You need to set CVSROOT to the appropriate repository when you check out, but not when you update (the information is in the CVS directories off each data directory). If you're using cvsup, you need to create separate cvsupfiles pointing to the repositories, and it's a good idea to get a relatively recent copy of the repository by other means (for the FreeBSD source tree, I got a tape, for the others I duplicated and extracted a .tar.gz file). I suppose I've left some of your concerns unanswered. Let me know what they are, and I'll answer them. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:02:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12616 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:02: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 RAA12607 for ; Mon, 14 Dec 1998 17:02:24 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA27558; Tue, 15 Dec 1998 11:32:13 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA15570; Tue, 15 Dec 1998 11:32:15 +1030 (CST) Message-ID: <19981215113214.T17075@freebie.lemis.com> Date: Tue, 15 Dec 1998 11:32:14 +1030 From: Greg Lehey To: "Marc G. Fournier" , Karl Pielorz Cc: freebsd-current@FreeBSD.ORG Subject: Re: System "crashed", serial console giving garbage... References: <36753622.3B46F4E2@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Marc G. Fournier on Mon, Dec 14, 1998 at 12:37:43PM -0400 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 X-Mutt-References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 14 December 1998 at 12:37:43 -0400, Marc G. Fournier wrote: > On Mon, 14 Dec 1998, Karl Pielorz wrote: >> The Hermit Hacker wrote: >>> About 15min oago or so, my system stop'd working :( If I connect >>> through the serial console, I see the following, after hitting return: >>> >>> pagecorp> attach s0 >>> Trying 209.47.145.10 ... >>> Connected - Escape character is '^]'. >>> $T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef$T0508:91e81ff0;05:c4cf3bfa;04:a0cf3bfa;#ef >>> >>> Now, I could understand it crashing and just freezing, but issuign >>> garbage? >>> >>> I have nothing else to debug with at this point, and have to wait for >>> someone to head downtown to reboot the machine, but figured I'd try to >>> start *somewhere* :( >> >> I've seen similar to this before... Make sure your not trying to run remote >> GDB across the serial console? (without it's counterpart on the other end)... > > Altho I think this would be highly unlikely, given the method of > connecting the serial console I'm using...how would I check this, just in > case? I think Karl's probably right. This looks *very* like the kernel debugger trying to talk gdb across the serial line. The obvious thing to do is to see if a gdb understands it: # gdb -k (gdb) set remotebaud 9600 (or whatever) (gdb) target remote /dev/cuaa0 (or whatever) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:06:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13036 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:06:34 -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 RAA13031 for ; Mon, 14 Dec 1998 17:06:31 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA27577; Tue, 15 Dec 1998 11:35:52 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA15585; Tue, 15 Dec 1998 11:35:41 +1030 (CST) Message-ID: <19981215113541.U17075@freebie.lemis.com> Date: Tue, 15 Dec 1998 11:35:41 +1030 From: Greg Lehey To: "Larry S. Marso" , freebsd-current@FreeBSD.ORG Subject: Re: recommended cvsup date? References: <19981214125257.D8998@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981214125257.D8998@marso.com>; from Larry S. Marso on Mon, Dec 14, 1998 at 12:52:57PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 14 December 1998 at 12:52:57 -0500, Larry S. Marso wrote: > Can anyone provide a recommended cvsup "as of" date for the 3.0 branch? > Anything subsequent to 3.0-R considered more stable? Today? I haven't seen any show-stoppers in -CURRENT for a while. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:07:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13320 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:07:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13296 for ; Mon, 14 Dec 1998 17:07:38 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id CAA21609; Tue, 15 Dec 1998 02:07:28 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id CAA44280; Tue, 15 Dec 1998 02:07:27 +0100 (MET) Message-ID: <19981215020726.V5444@follo.net> Date: Tue, 15 Dec 1998 02:07:26 +0100 From: Eivind Eklund To: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/etc Makefile References: <199812132313.SAA13630@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812132313.SAA13630@bb01f39.unx.sas.com>; from John W. DeBoskey on Sun, Dec 13, 1998 at 06:13:37PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're writing to me, then please write to me, not to some random other list then the one I originally wrote things on without Cc to me. Thanks. On Sun, Dec 13, 1998 at 06:13:37PM -0500, John W. DeBoskey wrote: > From: Eivind Eklund > Subject: Re: cvs commit: src/etc Makefile > > > Eivind said: > > On Sun, Dec 13, 1998 at 02:44:23PM +0200, Mark Murray wrote: > > > Dag-Erling Smorgrav wrote: > > > > Better, but not sufficient; it assumes that the user checks 'ls > > > > /etc/*sample' after make world. For such a feature to have any effect, > > > > you have to somehow warn the user about missing files, e.g. by mailing > > > > a list to root. > > > > > > I can see annoyed users turning this off and _still_ complaining. Current > > > is turning into too much of a commodity with not enough emphasis of "thou > > > shalt RTFM and RTSL". > > > > I've been thinking of how to say this with a suitable amount of force. > > One way of doing this could be to stop cvsup access for -current. > > > > Yup - if you want to track -current, you track the cvs repository. If > > you don't need the cvs repository, you're not developing code, and > > thus shouldn't be in -current. > > > > I'm not sure if this is too drastic, but we really should be shooting > > off those people... > > Well, a dose of reality. Every one of you used to be in the position > of some of these "people". No. Many of the developers did _not_ track -current before becoming developers. I know there are several cases of this besides myself. > You didn't know everything. And sometimes, > RTFM just doesn't do the trick, especially when TFM is out-of-date > because you the "developers" changed the code, but not the doc's. It says 'RTSL'. If you can't read the source, YOU'RE NOT SUPPOSED TO BE RUNNING -current! > Now, with that said... My stupid question: How does one track -current > without cvsup? I can't access the repository via nfs, and I don't have > an account for either pserver or rsh mode... One learn how CVS works, and cvsup the entire repository. This cost about 450MB extra diskspace, but it makes for a much better development environment - and -current is mostly meant as a development environment, and should not be used for ordinary production unless one is very, very much aware that this is something one do to do FreeBSD a service and will cost a lot of sweat, blood and tears. > Now some praise for the the committers who have been working through > the bug database. Thanks! And none for those of us who spend days peering over output of obscure verification tools? :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:11:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13538 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:11:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13528 for ; Mon, 14 Dec 1998 17:11:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA00643; Mon, 14 Dec 1998 17:08:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812150108.RAA00643@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Passe cc: Mike Smith , mwlucas@exceptionet.com, freebsd-current@FreeBSD.ORG Subject: Re: good new 3x laptop? In-reply-to: Your message of "Sun, 13 Dec 1998 14:00:59 MST." <199812132100.OAA14463@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 17:08:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > > > I'm about to purchase a laptop to run FreeBSD on. With all this > > > discussion about PAO and -current differences, I figured I'd better ask > > > first. ;) > > > > > > Can anyone recommend a decent new laptop for FreeBSD? I want to run 3.x. > > > I'm looking in the sub-$2000 range. > > > > Any of the Toshiba Satellite units in that range will give you good > > service. > > How about a high end PII/14" display machine. I need to have > 3.0-current development system for field compiles. A good docking > station would be a plus. You should be OK with the current crop of Dell systems, as long as you bear in mind that you can't (yet) do CardBus stuff. They're also very rugged... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13555 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:11:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13529 for ; Mon, 14 Dec 1998 17:11:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id DAA00620; Mon, 14 Dec 1998 03:36:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812141136.DAA00620@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kelvin Farmer" cc: freebsd-current@FreeBSD.ORG Subject: Re: Phantom hard drive detection in GENERIC? In-reply-to: Your message of "Mon, 07 Dec 1998 15:31:54 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 03:36:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please wrap your paragraphs; it's hard (and thus discouraging) to reply to a message that requires extra formatting effort. > Okay, the problem goes like this: a phantom hard drive (wd3) appears > to be detected when the hardware is probed. The actual harddrives and > cdrom are all detected properly, and if wd3 is removed (in a custom > kernel), then there are no problems. > However, in the initial installation, wd3 cannot be disabled, only > wdc1, which also has a CDROM connected to it, so a cdrom installation is > ruled out since the detection of wd3 halts the installation process like > this: > wd3: can't handle 65535 heads from partition tale (truncating to 16) > wd3 cannot handle 65535 sectors (max 255) > wd3 wdcontrol: reca failed reading fsbn0wd3: status > 7e error 4 > wd3 error reading primary partition table reading fsbn 0 (wd3 bn0;cn0 tn0 sn0) When you say "halts the installation process", does it repeat the above error message, or does it simply lock up at this point? > The GENERIC kernel detects my system like thus: > > stDMAonly disabled, pre/post enabled, > intel_piix_status: IORDY sampling enabled, > intel_piix_status: fast PIO enabled > ide_pci: busmaster 0 status: 60 from port: 0000ffa2 > ide_pci: ide0:0 has been configured for DMA by BIOS > ide_pci: ide0:1 has been configured for DMA by BIOS Can you try winding back the BIOS IDE-related settings to their most conservative values? > intel_piix_status: secondary master sample = 3, master recovery = 3 > intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, > intel_piix_status: IORDY sampling enabled, > intel_piix_status: fast PIO enabled > intel_piix_status: secondary slave sample = 5, slave recovery = 4 > intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, > intel_piix_status: IORDY sampling disabled, > intel_piix_status: fast PIO disabled > ide_pci: busmaster 1 status: 04 from port: 0000ffaa > found-> vendor=0x5333, dev=0x883d, revid=0x02 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[0]: type 1, range 32, base 80000000, size 26 > > [snip] > > 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 > wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 > wdc0: unit 1 (wd1): > wd1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S > wd1: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 1 (wd3): <\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\\M^?\M^?\M^?\M^?> > wd3: 95MB (196607 sectors), 65535 cyls, 65535 heads, 65535 S/T, 512 B/S > wd3: ATA INQUIRE valid = ffffffff, dmamword = ffffffff, apio = ffffffff, udma = ffffffff > wdc1: unit 0 (atapi): , removable, accel, dma, iordis > wcd0: 1378Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray > wcd0: 120mm photo disc loaded, unlocked Ick. This looks like the probe is getting a false echo (or something equally nasty) from the CDROM. Is your cabling all ATA-compliant? > Hardware: > 430 HX chipset. > Intel 82371 SB is the PCI Bus Master IDE controller (PIIX3) > 2 Quantum harddrive correctly identified, they are master and slave on the > primary IDE. > 1 Matshita cdrom, master on secondary IDE. The '583 is normally well-behaved - I'm fairly sure I have one (not sure which firmware) on an identical controller (PIIX3) on a 440FX board, which has been working well for > 12 months now. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:11:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13578 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:11:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13570 for ; Mon, 14 Dec 1998 17:11:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id DAA00657; Mon, 14 Dec 1998 03:42:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812141142.DAA00657@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "D. Rock" cc: current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-reply-to: Your message of "Mon, 07 Dec 1998 20:54:30 +0100." <366C3276.E337E0F@cs.uni-sb.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 03:42:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Paul van der Zwan schrieb: > > > > When I try to create a file on a FS mounted from my Sparc 5 running Solaris 7 > > I get the following error: > > [21:14:42 trantor:paulz:/mnt/var/tmp] > > $ touch a > > touch: a: Inappropriate file type or format > I can confirm this error. The solution is (again) using NFSv2 mounts. > > Is this problem currently under investigation? It happens at least with > kernels cvsup'd up to today. I don't know of anyone actively pursuing it. If you have a little time to look at the code (it's just code), that'd be really appreciated. > Below is the output of "snoop -v port 2049" on the Solaris box > (The output of snoop seems much more readable by human). One output > is the (succeding) call using v2 mounts, the other the (failing) > using v3 mounts. I have to say that most of it looks OK; the relevant bits are: the v3 create failing: > RPC: ----- SUN RPC Header ----- > RPC: > RPC: Transaction id = 1269155957 > RPC: Type = 0 (Call) > RPC: RPC version = 2 > RPC: Program = 100003 (NFS), version = 3, procedure = 8 > RPC: Credentials: Flavor = 1 (Unix), len = 48 bytes > RPC: Time = 0 > RPC: Hostname = > RPC: Uid = 0, Gid = 0 > RPC: Groups = 0 2 3 4 5 20 31 > RPC: Verifier : Flavor = 0 (None), len = 0 bytes > RPC: > NFS: ----- Sun NFS ----- > NFS: > NFS: Proc = 8 (Create file) > NFS: File handle = [B800] > NFS: 4600FC00020000000A000000CE600000CE0069250A000000CE600000CE006925 > NFS: File name = bla > NFS: Method = Unchecked > NFS: Mode = 0644 > NFS: Setuid = 0, Setgid = 0, Sticky = 0 > NFS: Owner's permissions = rw- > NFS: Group's permissions = r-- > NFS: Other's permissions = r-- > NFS: User ID = (not set) > NFS: Group ID = (not set) > NFS: Size = (not set) > NFS: Access time = -1 (set to client time) > NFS: Modification time = -1 (set to client time) ... > RPC: ----- SUN RPC Header ----- > RPC: > RPC: Transaction id = 1269155957 > RPC: Type = 1 (Reply) > RPC: This is a reply to frame 5 > RPC: Status = 0 (Accepted) > RPC: Verifier : Flavor = 0 (None), len = 0 bytes > RPC: Accept status = 0 (Success) > RPC: > NFS: ----- Sun NFS ----- > NFS: > NFS: Proc = 8 (Create file) > NFS: Status = 79 ((unknown error)) > NFS: Pre-operation attributes: > NFS: Size = 512 bytes > NFS: Modification time = 07-Dec-98 19:27:17.665634000 GMT > NFS: Attribute change time = 07-Dec-98 19:27:17.665634000 GMT > NFS: > NFS: Post-operation attributes: > NFS: File type = 2 (Directory) > NFS: Mode = 0755 > NFS: Setuid = 0, Setgid = 0, Sticky = 0 > NFS: Owner's permissions = rwx > NFS: Group's permissions = r-x > NFS: Other's permissions = r-x > NFS: Link count = 2, User ID = 0, Group ID = 1 > NFS: File size = 512, Used = 1024 > NFS: Special: Major = 0, Minor = 0 > NFS: File system id = 16515142, File id = 24782 > NFS: Last access time = 07-Dec-98 19:37:51.535634000 GMT > NFS: Modification time = 07-Dec-98 19:27:17.665634000 GMT > NFS: Attribute change time = 07-Dec-98 19:27:17.665634000 GMT The v2 create succeeding: > RPC: ----- SUN RPC Header ----- > RPC: > RPC: Transaction id = 1269155981 > RPC: Type = 0 (Call) > RPC: RPC version = 2 > RPC: Program = 100003 (NFS), version = 2, procedure = 9 > RPC: Credentials: Flavor = 1 (Unix), len = 48 bytes > RPC: Time = 0 > RPC: Hostname = > RPC: Uid = 0, Gid = 0 > RPC: Groups = 0 2 3 4 5 20 31 > RPC: Verifier : Flavor = 0 (None), len = 0 bytes > RPC: > NFS: ----- Sun NFS ----- > NFS: > NFS: Proc = 9 (Create file) > NFS: File handle = [B800] > NFS: 4600FC00020000000A000000CE600000CE0069250A000000CE600000CE006925 > NFS: File name = bla > NFS: Mode = 0100644 > NFS: Type = Regular file > NFS: Setuid = 0, Setgid = 0, Sticky = 0 > NFS: Owner's permissions = rw- > NFS: Group's permissions = r-- > NFS: Other's permissions = r-- > NFS: UID = -1 > NFS: GID = -1 > NFS: Size = 0 > NFS: Access time = -1 > NFS: Modification time = -1 ... > RPC: ----- SUN RPC Header ----- > RPC: > RPC: Transaction id = 1269155981 > RPC: Type = 1 (Reply) > RPC: This is a reply to frame 7 > RPC: Status = 0 (Accepted) > RPC: Verifier : Flavor = 0 (None), len = 0 bytes > RPC: Accept status = 0 (Success) > RPC: > NFS: ----- Sun NFS ----- > NFS: > NFS: Proc = 9 (Create file) > NFS: Status = 0 (OK) > NFS: File handle = [2E82] > NFS: 4600FC00020000000A000000D260000004FE29590A000000CE600000CE006925 > NFS: File type = 1 (Regular File) > NFS: Mode = 0100644 > NFS: Type = Regular file > NFS: Setuid = 0, Setgid = 0, Sticky = 0 > NFS: Owner's permissions = rw- > NFS: Group's permissions = r-- > NFS: Other's permissions = r-- > NFS: Link count = 1, UID = 0, GID = 0, Rdev = 0x0 > NFS: File size = 0, Block size = 8192, No. of blocks = 0 > NFS: File system id = 16515142, File id = 24786 > NFS: Access time = 07-Dec-98 19:41:14.685634 GMT > NFS: Modification time = 07-Dec-98 19:41:14.685634 GMT > NFS: Inode change time = 07-Dec-98 19:41:14.685634 GMT > NFS: The only visible differences here are the UID/GID, and it's not clear whether the '-1' in the v2 request corresponds to the (not set) in the v3 request or not. I did have someone suggest that the create would work if you supplied O_EXCL when making the open - if you want to try a small sample program and compare the traces that might be informative. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:24:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15056 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:24:34 -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 RAA14994 for ; Mon, 14 Dec 1998 17:24:30 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA27097; Tue, 15 Dec 1998 11:54:09 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812141129.DAA00571@dingo.cdrom.com> Date: Tue, 15 Dec 1998 11:53:58 +1030 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: New drivers and install floppy space Cc: Mikael Karpberg , obrien@NUXI.com, current@FreeBSD.ORG, "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Dec-98 Mike Smith wrote: > Geez, format your messages already. 8) Feh, blame my mailer :) > You forgot to put a bootblock on the image. Splat /boot/boot0 over the > first 512 bytes of the image and try again. There's a stock (no menu) > bootblock somewhere in the libdisk sources as well. Uh, OK :) > Sounds promising; indications are that this is the way that the NT > bootable CD does it. The NT CD is bootable? Goddam I wish I realised that before! =) ($!@# 3 disk install) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:36:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15943 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:36:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15928 for ; Mon, 14 Dec 1998 17:36:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id DAA00405; Mon, 14 Dec 1998 03:06:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812141106.DAA00405@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kenneth Wayne Culver cc: current@FreeBSD.ORG Subject: Re: ide_pci.c In-reply-to: Your message of "Wed, 09 Dec 1998 20:42:42 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 03:06:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just thought that someone in here should know this: I have a generic > dual PCI IDE controller. It can support up to 4 devices. I have 2 hard > drives on the first controller, and an ATAPI cdrom drive on the second. > The problem is that when it boots, it says that the controller is simplex, > and that there is no dma on the secondary channel, and then when it gets > down to the ISA configuration, it won't find anything on the second > controller. The only way I could fix it is to go to > /usr/src/sys/i386/conf/files.i386 and delete the line that specifies > ide_pci.c > > That solved the problem, and I can now use my CD-ROM drive, but I thought > that you guys should know about the problem. Thanks. I'm sorry if I missed it, but I don't recall hearing from you what the chipset on your IDE controller was; we kinda need this to fix the problem "properly". -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:36:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16020 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:36:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15982 for ; Mon, 14 Dec 1998 17:36:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id DAA00571; Mon, 14 Dec 1998 03:29:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812141129.DAA00571@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel O'Connor" cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, obrien@NUXI.com, mike@smith.net.au (Mike Smith), Mikael Karpberg Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Tue, 08 Dec 1998 19:01:32 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 03:29:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Geez, format your messages already. 8) > On 08-Dec-98 Jordan K. Hubbard wrote: > > with information on your configuration. We'll pick out 10 people who > > seem to represent a reasonably diverse collection of CD-booters and > > send them a copy of of this. If it works on all 10, that will be a > > good sign. If it does not, it won't be and we can rethink this. :-) > > Well, I'm about to sacrifice another virgin CD blank to the ravening > CD monster to test this.. The first one I did had a broken partition > table, so it would SEE it, just not boot :) > > OK, thats done.. and the BIOS says that it sees the parition and its > moved my hard drives up a letter.. It then tries to boot, but gets > 'Missing operating system' You forgot to put a bootblock on the image. Splat /boot/boot0 over the first 512 bytes of the image and try again. There's a stock (no menu) bootblock somewhere in the libdisk sources as well. > Note that this is trying to boot off a SCSI CDROM (which works for, > say the 2.2.7 CD). The board is a P6SBS Supermicro job. (which has an > Ami WinBIOS) > > On our Abit board with an Award BIOS I get the same results.. It sees > the partition, but fails to boot. Sounds promising; indications are that this is the way that the NT bootable CD does it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:36:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16078 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:36:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16009 for ; Mon, 14 Dec 1998 17:36:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id CAA00320; Mon, 14 Dec 1998 02:54:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812141054.CAA00320@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: MIHIRA Sanpei Yoshiro cc: mike@smith.net.au, current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sat, 12 Dec 1998 16:06:54 +0900." <199812120706.QAA22991@lavender.sanpei.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 02:54:58 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > mike@smith.net.au wrote: > >> > > >> > Do NE2000 Compatible PCMCIA cards work under PAO3, as it is now? > >> > If so, is the development snapshot available anywhere? > >> > >> They work fine under stock 2.2 and 3.0 (this message is being sent > >> using one). > Content-Type: Text/Plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > I have three NE2000 compatible PCMCIA cards. > I can use two cards with FreeBSD-current which added some lines to > /etc/pccard.conf, but can't use another one. > Under PAO, I can use all these cards. > > I compare these CIS via pccardc dumpcis command. > o unusable cards has memory descriptor. > o usable cards does not have it. > > Tuple #6, code = 0x1b (Configuration entry), length = 25 > 000: c1 81 78 ca 61 00 03 0f 10 03 0f 30 fc be c9 04 > 010: 00 00 40 0d 40 40 00 40 0d > Config index = 0x1(default) > Interface byte = 0x81 (I/O) wait signal supported > Card decodes 10 address lines, limited 8/16 Bit I/O > I/O address # 1: block start = 0x300 block length = 0x10 > I/O address # 2: block start = 0x310 block length = 0x10 > IRQ modes: Level > IRQs: 2 3 4 5 6 7 9 10 11 12 13 15 > Memory descriptor 1 <------------------- > blk length = 0x400 card addr = 0x000 host addr = 0xd4000 > Memory descriptor 2 <------------------- > blk length = 0x4000 card addr = 0x4000 host addr = 0xd4000 > ---------- > Review pccardd. > PAO's assign_io function in pccardd/cardd.c has related code but > it's comment is ``XXX -- dirty hack for some 'ed' cards that have > incomplete iomem CIS tupples.'' > But FreeBSD-current's assign_io function does not have it. > > I think that Mike's card does not have Memory descriptor.. Is > that right? Yes; there's a long-standing bug in the way that the stock pccardd deals with memory blocks < 4096 bytes, where it tries to allocate a zero-sized window, which fails and thus the card is rejected. The memory region in question's not actually used for the card's operation; the simplest fix would be to correct pccardd to either expand any window < 4096 to 4096 or to just not map it (bad but simpler). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:37:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16241 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:37:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16033 for ; Mon, 14 Dec 1998 17:36:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id DAA00486; Mon, 14 Dec 1998 03:18:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812141118.DAA00486@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "David E. Cross" cc: "Jordan K. Hubbard" , Mikael Karpberg , Mike Smith , obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Tue, 08 Dec 1998 10:01:30 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 03:18:44 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 8 Dec 1998, Jordan K. Hubbard wrote: > > > > > If we're going to go off the beaten track, we might as well do it > > > > properly. A 10M harddisk image is going to be a much better idea in > > > > that case. > > > > > > Probably... If all BIOSes that handle CDROM booting can handle that... > > > > Which is as good a time as any to make a *practical* suggestion and > > get us moving back in the direction of progress, I think. :-) > > > > Let's postpone this discussion for another 15 days or so, until Mike > > can return (to the US) from the Australian location he's currently > > occupying. He and I will look over his spec and see if we can't hack > > mkisofs into using a 10MB image rather than the 1.44MB image it uses > > My understanding of this has been that the BIOS treats the CDROM as a > virtual floppy drive for the purposes of booting off of it (which matches > my experience of specifying a floppy disk image as the boot file when > using mkisofs, and having that work). It treats it as a virtual BIOS disk of some sort, using a linear region on the disk to provide the raw sectors for the disk. > I think a perhaps better solution, > and more usefull to a wider variety of people would be to have a bootdisk > that would then mount its root filesystem off of the CDROM in a > conventional manor, and make that the 'bootfile' on the CDROM. So a > person with a BIOS that cannot boot off of CDROM (they still exist in > great numbers), would place the CD in the drive, have the CDboot floppy, > and still be in buisness. (This of course does not address those w/o a > CDROM). There are some gymnastic reasons why this isn't as easy as it might be, but theoretically it would be possible to suck a root filesystem image in from a temporarily-mounted, supported CDROM and then mount that image as the MFS root. Your code diffs to implement this, cleanly, would be very welcome. You might want to consider doing it in a fashion consistent with the way that we would be doing this for the bootable CDROM, ie. read the raw CDROM to find the boot image file, 'mount' the boot image file as a UFS filesystem, locate the 'mfsroot' file and read that; this would make things somewhat easier I expect. You would *definitely* want to write this code as a KLD module using a SYSINIT() that caused it to run between the device probes and the attemt to mount the root filesystem. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:37:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16282 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:37:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16083 for ; Mon, 14 Dec 1998 17:37:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00350; Sun, 13 Dec 1998 15:21:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812132321.PAA00350@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Atsushi Furuta cc: dfr@nlsystems.com, mike@smith.net.au, y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sun, 13 Dec 1998 19:23:08 +0900." <199812131023.TAA05525@sramhc.sra.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 15:21:25 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> In article , > Doug Rabson writes: > > > The softc issue is addressed by the new device framework. The pci support > > code has not yet been updated to the new interface but when it is, it will > > get this for free. The flags field can also be easily added. > > I wonder how a user specifies flags to pci bus. I seems that there > is no generic way to specify flags in current subr_bus.c, and it is up > to each bus codes how to provide ivers and flags. Flags are bad. They exist at all because it was hard to specify meaningful options to drivers via config (which couldn't know anything about the driver structure). Drivers should export a set of options that are a union of the set of options the driver supports plus a subset of the options for a device provided by the bus. This can be determined by examining the driver and bus data at probe/attach time; something that's easy with KLD/ newbus/loader, but would require a bolt-on for newconfig. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:37:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16309 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:37:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16176 for ; Mon, 14 Dec 1998 17:37:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00301; Sun, 13 Dec 1998 12:07:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812132007.MAA00301@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: alexandr@mail.eecis.udel.edu cc: current@FreeBSD.ORG Subject: Re: Memory Problems In-reply-to: Your message of "Sun, 13 Dec 1998 03:02:29 EST." <199812130302.aa18157@mail.eecis.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 12:07:58 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm running -current on a ThinkPad 600E. If I put more then 64M of > memory in this machine it randomly hangs on me. > > I've tried ever memory combo that I can for anything above 64M (80, 96 > 116 and 128), and they all produce the same results. > > Has anyone ever seen a problem like this? If so, does anyone know of a > solution? It's a known problem; the system responds badly to attempts to probe for memory in the way that we do. You should be able to build a kernel with MAXMEM explicitly specified to match your memory config (See LINT) which should disable the speculative probe. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:37:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16247 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:37:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16074 for ; Mon, 14 Dec 1998 17:36:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00332; Sun, 13 Dec 1998 15:19:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812132319.PAA00332@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa cc: Garrett Wollman , Nate Williams , Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sun, 13 Dec 1998 12:03:31 +0900." <199812130303.MAA09027@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 15:19:22 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Not at all. Please join new-bus-arch. > > OK, I will join new-bus ML. But I disagree "now -current style bus > code". -current bus code is very different other BSDs, it is large > demerit. And, I NEED "new" config for staticaly configuration. I think this illustrates the major points of difference between the "newconfig" folks and the "new bus" folks. Let me explain my reasons for supporting the "new bus" movement; these may help explain why we think it's worth the effort. - We aren't CopycatBSD; the "new bus" group is attempting to develop a new, better approach to handling the bus/bridge/device relationships. "newconfig" is better than what we have right now, but it is not good enough. - Bus architecture "incompatibility" is not actually a significant issue. We are already 100% bus architecture incompatible with the other BSDs, change simply for compatibility's sake won't give us any benefits, and it would stifle any attempt to do better. Right now the few drivers that are shared amongst the BSD's all have different bus interface code anyway; there is nothing that will get "worse" if we change the mechanics of the interface. There are also things that we are trying to do that can't be done with newconfig (at least, as it is right now - for sure it too can be modified). - Static configuration is evil. More specifically, static configuration is a special case of dynamic configuration. "newconfig" does static configuration very well, but the "newconfig" architecture is not at all suitable for dynamic configuration. > In now, -current bus code lack of many feature, NetBSD-current bus > code has it. So, we use NetBSD style bus and device configuration > code. We already re-write PCI and part of ISA code, it works fine. I don't think this is good enough. We don't want to be playing catch-up to an architecture that was well-designed for systems where configuration is largely static; we need something that will allow us to grow and adapt to the future directions that systems architecture in our target market is taking. I don't mean to say "newconfig is bad", so much as to say "new bus is better 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 freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:37:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16345 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:37:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16280 for ; Mon, 14 Dec 1998 17:37:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00365; Sun, 13 Dec 1998 12:16:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812132016.MAA00365@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kenjiro Cho cc: Mike Smith , NAKAGAWA Yoshihisa , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sat, 12 Dec 1998 22:25:33 +0900." <199812121325.WAA08728@hotaka.csl.sony.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 12:16:57 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Mike Smith said: > > > The new-bus people talk from the view of the entire architecture, but > > the focus of the PAO people is how to face the reality *NOW*. > > >> If that was all they were doing, that'd be ideal. The real problems > >> arising at the moment however stem from the PAO team laying plans for > >> long-term development without considering the directions that other > >> groups are taking. > > This is a communication problem. > I did some research on this issue in the -hackers archive. > > When itojun brought up "newconfig" back in June, you said you would > support it if it works. Jordan encouraged them to give it a try. > Then, the PAO team decided to go for "newconfig". More to the point, I said I'd support it if integration was taken to completion, which is a lot more than "works". Back in June there was also no action from Doug on his alternative design, so I had no hope for it. > Apperently, new-bus has evolved a lot since then and the situation > has changed, but the PAO folks are unaware of the directions that > other groups are taking. This could definitely do with some help. It's important that we don't become divided over what is in many ways a relatively trivial (if crucial) issue. > Then, Jordan said (08 Jun): ... > The reason I suggest ignoring them has to do with the fact that it's > exceedingly easy to point out the flaws in config(8) but obviously not > so easy to architect a complete replacement or someone would have done > so by now. Note that I'm not even talking about an implementation, > I'm talking about a reasonable attempt to even _architect_ such a > thing. It's worth pointing out that we are now quite a long way down the path to this goal; by no means all the way there, but the new bus architecture coupled with KLD modules does largely obviate the need for config(8) in the first place. I'm of the strong opinion that our current direction, taking us away from static configuration, is the right one to be taking in the context of our current and projected future target architectures. It is no longer adequate nor desirable to require the kernel to be rebuilt to adapt to a new system configuration, and we need to reflect this in our architecture. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:37:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16364 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:37:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16308 for ; Mon, 14 Dec 1998 17:37:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00387; Sun, 13 Dec 1998 12:20:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812132020.MAA00387@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa cc: Mike Smith , Kenjiro Cho , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sun, 13 Dec 1998 02:57:27 +0900." <199812121757.CAA08603@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 12:20:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If that was all they were doing, that'd be ideal. The real problems > > arising at the moment however stem from the PAO team laying plans for > > long-term development without considering the directions that other > > groups are taking. > > This point, PAO team was wrong. But many Japanese developer have > language problem, me too. We are not native speaker of > English. English is my weak point. So we have communication problem. Your English is more than good enough for me to understand everything you've said so far; I think you are too hard on yourself. I hope that you are understanding what I'm saying too. 8) > I want to change this situation, so I am using many power for > communication. It is very hard for me. :-( Thanks for all your work towards this goal; we really appreciate it. I hope that we can work together to understand our different needs and goals; I certainly don't want to see PAOBSD formed because we couldn't. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 17:58:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19590 for freebsd-current-outgoing; Mon, 14 Dec 1998 17:58:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hillbilly.hayseed.net (dnai-207-181-249-194.dsl.dnai.com [207.181.249.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19583 for ; Mon, 14 Dec 1998 17:58:38 -0800 (PST) (envelope-from enkhyl@scient.com) Received: from localhost (IDENT:root@localhost [127.0.0.1]) by hillbilly.hayseed.net (8.9.1/8.8.5) with ESMTP id RAA24058; Mon, 14 Dec 1998 17:58:03 -0800 Date: Mon, 14 Dec 1998 17:58:00 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: Christopher Nielsen To: Mike Smith cc: Steve Passe , mwlucas@exceptionet.com, freebsd-current@FreeBSD.ORG Subject: Re: good new 3x laptop? In-Reply-To: <199812150108.RAA00643@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 Mon, 14 Dec 1998, Mike Smith wrote: > > Hi, > > > > > > I'm about to purchase a laptop to run FreeBSD on. With all this > > > > discussion about PAO and -current differences, I figured I'd better ask > > > > first. ;) > > > > > > > > Can anyone recommend a decent new laptop for FreeBSD? I want to run 3.x. > > > > I'm looking in the sub-$2000 range. > > > > > > Any of the Toshiba Satellite units in that range will give you good > > > service. > > > > How about a high end PII/14" display machine. I need to have > > 3.0-current development system for field compiles. A good docking > > station would be a plus. > > You should be OK with the current crop of Dell systems, as long as you > bear in mind that you can't (yet) do CardBus stuff. They're also very > rugged... I'm going to throw my $0.02 in here because I use (as my regular machine) a Dell Latitude CPi running -current. I have had more hardware problems with this machine than I can count; we've had to replace the LCD three times in the last four months. And now the case is coming apart (I'm not particularly rough on the beast, either). OTOH, it runs -current quite well, and it's relatively fast except when doing large amounts of disk I/O (Dell can't seem to figure out how to make a fast system bus). Also, now that XFree86 supports NeoMagic chips, X works nicely, too. -- Christopher Nielsen Scient: The eBusiness Systems Innovator cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 18:02:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20217 for freebsd-current-outgoing; Mon, 14 Dec 1998 18:02:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20191 for ; Mon, 14 Dec 1998 18:02:37 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id NAA02902; Tue, 15 Dec 1998 13:01:26 +1100 (EST) Date: Tue, 15 Dec 1998 13:01:25 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: Ben Smithurst cc: npe@bfc.dk, freebsd-current@FreeBSD.ORG Subject: Re: Aout to ELF In-Reply-To: <19981211193714.A26080@scientia.demon.co.uk> 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, 11 Dec 1998, Ben Smithurst wrote: > npe@bfc.dk wrote: > > > I'm wondering if there's any documentation on how to change from aout to > > elf kernels ?? I thought that a make aout-to-elf world do the trick.. But > > it fails with a missing script... > > If you told us what script was missing someone may be able to work out > what you've done wrong. > After a successful 'make aout-to-elf-build' this happens: Script started on Mon Dec 14 12:39:58 1998 You have mail. dev# dev# pwd /usr/src dev# dev# make aout-to-elf-install -------------------------------------------------------------- You are about to move all the installed a.out libraries into an aout sub-directory of each elf library directory. You can type Ctrl-C to abort now or press return to start the moving the libraries. -------------------------------------------------------------- Directories to search: /usr/lib /usr/lib/compat /usr/local/lib /usr/X11R6/lib Return to continue or Ctrl-C to abort: /usr/src/tools/tools/upgrade/move_aout_libs.sh: Can't open /usr/src/tools/tools/upgrade/move_aout_libs.sh *** Error code 2 Stop. *** Error code 1 Stop. dev# exit Script done on Mon Dec 14 12:40:20 1998 This is NOT pilot error, and is 100% reproducable, IF you download the tarballs from ftp://ftp.freebsd.org/pub/FreeBSD/3.0-RELEASE/src and use the install.sh script to extract them. ATTN: Jordan install.sh does not extract stools.aa -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 18:45:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27218 for freebsd-current-outgoing; Mon, 14 Dec 1998 18:45:46 -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 SAA27206 for ; Mon, 14 Dec 1998 18:45:40 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA28077; Tue, 15 Dec 1998 13:15:22 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA15779; Tue, 15 Dec 1998 13:15:22 +1030 (CST) Message-ID: <19981215131522.G15633@freebie.lemis.com> Date: Tue, 15 Dec 1998 13:15:22 +1030 From: Greg Lehey To: Bruce Evans , freebsd-current@FreeBSD.ORG, mjacob@feral.com Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour References: <199812141802.FAA09572@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812141802.FAA09572@godzilla.zeta.org.au>; from Bruce Evans on Tue, Dec 15, 1998 at 05:02:05AM +1100 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 Tuesday, 15 December 1998 at 5:02:05 +1100, Bruce Evans wrote: >> Down the road a little bit would be: >> >>>> untangling the minor device as behaviour selector so that >> ioctl's would not have to be used to select compression. > > This should be controversial :-). Compression is another type of > behaviour. Is this an argument for or against the change? I'm for the change, anyway. Currently it's not possible to tell a backup utility to write in compressed or uncompressed mode. If I have different devices, I can do this. It's been this way in ever other UNIX I've used. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 18:46:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27299 for freebsd-current-outgoing; Mon, 14 Dec 1998 18:46:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27291 for ; Mon, 14 Dec 1998 18:46:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01975; Mon, 14 Dec 1998 18:44:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812150244.SAA01975@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma cc: FreeBSD current mailing list , Lennart Augustsson , USB BSD list Subject: Re: double CVS repositories In-reply-to: Your message of "Mon, 14 Dec 1998 14:20:31 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 18:44:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Anyone working on a project in which 2 entirely different repositories > are being kept up to date simultaneously? > > The problem we have is that we (Lennart, NetBSD and myself, FreeBSD) > would like to have a CVS repository to which we commit changes to the > USB source, but at the same time would like to commit things to the > repository of the OS as well. > > Now this would be possible by writing a number of scripts that get > executed when committing to a local repository. But that does not sound > very sexy. > > Anyone any better solutions to this problem? Anyone any working examples > we could copy? Not really; I would suggest rather than you use your private repository for your development work, and just export stuff in periodic 'releases' into the FreeBSD/NetBSD repos. If you lay down a tag everytime you export, you should be able to produce diffs since the last export easily... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 18:50:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27725 for freebsd-current-outgoing; Mon, 14 Dec 1998 18:50:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27718 for ; Mon, 14 Dec 1998 18:50:06 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id SAA04762; Mon, 14 Dec 1998 18:49:45 -0800 Date: Mon, 14 Dec 1998 18:49:45 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Greg Lehey cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour In-Reply-To: <19981215131522.G15633@freebie.lemis.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 > >> Down the road a little bit would be: > >> > >>>> untangling the minor device as behaviour selector so that > >> ioctl's would not have to be used to select compression. > > > > This should be controversial :-). Compression is another type of > > behaviour. > > Is this an argument for or against the change? > > I'm for the change, anyway. Currently it's not possible to tell a > backup utility to write in compressed or uncompressed mode. If I have > different devices, I can do this. It's been this way in ever other > UNIX I've used. You *can* enable/disable compression, and we could even make the change persistent across tape mounts, but the issue here is whether or not you also want to go and change the N different backup utilities to use the appropriate ioctl to select compression or not. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 18:52:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27936 for freebsd-current-outgoing; Mon, 14 Dec 1998 18:52:02 -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 SAA27891 for ; Mon, 14 Dec 1998 18:51:58 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA28124; Tue, 15 Dec 1998 13:21:48 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA15792; Tue, 15 Dec 1998 13:21:44 +1030 (CST) Message-ID: <19981215132144.H15633@freebie.lemis.com> Date: Tue, 15 Dec 1998 13:21:44 +1030 From: Greg Lehey To: mjacob@feral.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour References: <19981215131522.G15633@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew Jacob on Mon, Dec 14, 1998 at 06:49:45PM -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 Monday, 14 December 1998 at 18:49:45 -0800, Matthew Jacob wrote: >>>> Down the road a little bit would be: >>>> >>>>>> untangling the minor device as behaviour selector so that >>>> ioctl's would not have to be used to select compression. >>> >>> This should be controversial :-). Compression is another type of >>> behaviour. >> >> Is this an argument for or against the change? >> >> I'm for the change, anyway. Currently it's not possible to tell a >> backup utility to write in compressed or uncompressed mode. If I have >> different devices, I can do this. It's been this way in ever other >> UNIX I've used. > > You *can* enable/disable compression, and we could even make the change > persistent across tape mounts, but the issue here is whether or not you > also want to go and change the N different backup utilities to use the > appropriate ioctl to select compression or not. Precisely. That would also include any tape utilities you port, and any other program you may want to use to access tape. Specifying the function in the device name seems the easiest solution to me. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 18:52:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27978 for freebsd-current-outgoing; Mon, 14 Dec 1998 18:52:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27969 for ; Mon, 14 Dec 1998 18:52:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02049; Mon, 14 Dec 1998 18:50:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812150250.SAA02049@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: imp@village.org (Warner Losh), mike@smith.net.au, current@FreeBSD.ORG Subject: Re: HEADS UP : laptop power-down change In-reply-to: Your message of "Sun, 13 Dec 1998 22:35:42 GMT." <199812132235.PAA10207@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 18:49:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Also, I think the correct flag is "-x", not "-p", from a historical > (Sony NeWS, NeXTStep, and A/UX, et. al.). That's a good point; now is probably the time to change it to be consistent. Any conflicting examples? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 18:55:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28260 for freebsd-current-outgoing; Mon, 14 Dec 1998 18:55:30 -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 SAA28254 for ; Mon, 14 Dec 1998 18:55:23 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA28155; Tue, 15 Dec 1998 13:25:11 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA15811; Tue, 15 Dec 1998 13:25:13 +1030 (CST) Message-ID: <19981215132513.I15633@freebie.lemis.com> Date: Tue, 15 Dec 1998 13:25:13 +1030 From: Greg Lehey To: mjacob@feral.com, Peter Jeremy Cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour References: <98Dec15.081550est.40374@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew Jacob on Mon, Dec 14, 1998 at 02:28:31PM -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 Monday, 14 December 1998 at 14:28:31 -0800, Matthew Jacob wrote: > On Tue, 15 Dec 1998 08:16:29 +1100, Peter Jeremy wrote: >> Matthew Jacob wrote: >> b) EARLY WARNING enabled: >> write(fd, buf, 1024) returns 512 >> [tape now at logical EOM] >> write(fd, buf, 1024) returns 0 [indicating logical EOM] >> write(fd, buf, 1024) returns 1024 >> write(fd, buf, 1024) returns -1, errno = EIO [512 bytes actually written] >> [tape now at physical EOM] > > The actual behaviour is more likely to be (assuming the app doesn't stop) > ... > b) I am proposing that behaviour be > >> write(fd, buf, 1024) returns N, where N is the amount actually written >> If, and only if N was 1024 (all bytes written) (and EOM had been > seen), the next write(fd, buf, 1024) returns 0 (0 bytes written). > > So, assuming the usual tape drive behaviour, the scenario as above would > be: > > i) write(fd, buf, 1024) returns 1024 (1024 bytes written) [ EOM flagged ] > ii) write(fd, buf, 1024) returns 0 (zero bytes moved) [ EOM cleared ] > iii) write(fd, buf, 1024) returns 1024 (1024 bytes written) > iv) write(fd, buf, 1024) will return -1 (ENOSPC or EIO - I don't care). > > It really doesn't matter what the app does at #iv- you've hit hard eot and > can't do anything but rewind or space backwards. > > It is expected that when #ii occurs the application could (in fact) write > a trailer record or two, but is expected to close the device or otherwise > cause a terminating filemark to be written and then rewind or do something > else. > > Alternatively, if the drive reports EOM *and* reports that it didn't write > all that was requested, then step #ii is ommitted entirely (as the goal of > signification has been met). Further, let's say we have a broken or stupid > drive, and it doesn't even report EOM (just that it didn't write all that > was requested)- this acts (or should act) as a significator to the user > application (there's absolutely no reason for a tape device, or for that > matter (sez Bob Snively of the ANSI SCSI committee) for any device, to not > write all that was requested *unless* some limiting condition (like > physical impossibility) occurs). I've probably missed something here, but what is the intention in (ii) or clearing EOM? What's wrong with: i) write(fd, buf, 1024) returns 1024 (1024 bytes written) [ EOM flagged ] ii) write(fd, buf, 1024) returns 0 (zero bytes moved) iii) write(fd, buf, 1024) will return -1 (ENOSPC or EIO - I don't care). Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 19:15:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00114 for freebsd-current-outgoing; Mon, 14 Dec 1998 19:15:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29993 for ; Mon, 14 Dec 1998 19:15:32 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id TAA04868; Mon, 14 Dec 1998 19:15:09 -0800 Date: Mon, 14 Dec 1998 19:15:09 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Greg Lehey cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour In-Reply-To: <19981215132144.H15633@freebie.lemis.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 > > You *can* enable/disable compression, and we could even make the change > > persistent across tape mounts, but the issue here is whether or not you > > also want to go and change the N different backup utilities to use the > > appropriate ioctl to select compression or not. > > Precisely. That would also include any tape utilities you port, and > any other program you may want to use to access tape. Specifying the > function in the device name seems the easiest solution to me. > The only problem with this is that the matrix of device names gets extremely unwieldy. It's not just compression, but perhaps density. Take a look at the Solaris tape name mess: /dev/rmt/U{l|m|h|c}[b][n] U == unit; l = low, m = med, h = high, c = compression; b = BSD semantics; n = norewind and this is where you've (incorrectly, in my opinion) smooshed compression in with density selection. I don't see an easy solution that makes sense (as yet- this requires a lot of thinking). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 19:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00426 for freebsd-current-outgoing; Mon, 14 Dec 1998 19:17:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00412 for ; Mon, 14 Dec 1998 19:17:38 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id TAA04881; Mon, 14 Dec 1998 19:17:24 -0800 Date: Mon, 14 Dec 1998 19:17:24 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Greg Lehey cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour In-Reply-To: <19981215132513.I15633@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've probably missed something here, but what is the intention in (ii) > or clearing EOM? What's wrong with: > > i) write(fd, buf, 1024) returns 1024 (1024 bytes written) [ EOM flagged ] > ii) write(fd, buf, 1024) returns 0 (zero bytes moved) > iii) write(fd, buf, 1024) will return -1 (ENOSPC or EIO - I don't care). So that the tape driver knows for #iii not to just return 0 (zero bytes moved). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 19:21:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00779 for freebsd-current-outgoing; Mon, 14 Dec 1998 19:21:59 -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 TAA00773 for ; Mon, 14 Dec 1998 19:21:56 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA28300; Tue, 15 Dec 1998 13:51:46 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA15840; Tue, 15 Dec 1998 13:51:45 +1030 (CST) Message-ID: <19981215135145.A15815@freebie.lemis.com> Date: Tue, 15 Dec 1998 13:51:45 +1030 From: Greg Lehey To: mjacob@feral.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour References: <19981215132513.I15633@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew Jacob on Mon, Dec 14, 1998 at 07:17:24PM -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 Monday, 14 December 1998 at 19:17:24 -0800, Matthew Jacob wrote: >> I've probably missed something here, but what is the intention in (ii) >> or clearing EOM? What's wrong with: >> >> i) write(fd, buf, 1024) returns 1024 (1024 bytes written) [ EOM flagged ] >> ii) write(fd, buf, 1024) returns 0 (zero bytes moved) >> iii) write(fd, buf, 1024) will return -1 (ENOSPC or EIO - I don't care). > > So that the tape driver knows for #iii not to just return 0 (zero bytes > moved). Sure, it'll need another state bit. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 19:25:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01254 for freebsd-current-outgoing; Mon, 14 Dec 1998 19:25:03 -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 TAA01246 for ; Mon, 14 Dec 1998 19:24:59 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA28317; Tue, 15 Dec 1998 13:54:47 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA15850; Tue, 15 Dec 1998 13:54:48 +1030 (CST) Message-ID: <19981215135448.B15815@freebie.lemis.com> Date: Tue, 15 Dec 1998 13:54:48 +1030 From: Greg Lehey To: mjacob@feral.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour References: <19981215132144.H15633@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew Jacob on Mon, Dec 14, 1998 at 07:15:09PM -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 Monday, 14 December 1998 at 19:15:09 -0800, Matthew Jacob wrote: > >>> You *can* enable/disable compression, and we could even make the change >>> persistent across tape mounts, but the issue here is whether or not you >>> also want to go and change the N different backup utilities to use the >>> appropriate ioctl to select compression or not. >> >> Precisely. That would also include any tape utilities you port, and >> any other program you may want to use to access tape. Specifying the >> function in the device name seems the easiest solution to me. >> > > The only problem with this is that the matrix of device names gets > extremely unwieldy. It's not just compression, but perhaps density. Take a > look at the Solaris tape name mess: > > /dev/rmt/U{l|m|h|c}[b][n] > > U == unit; l = low, m = med, h = high, c = compression; b = BSD semantics; > n = norewind > > and this is where you've (incorrectly, in my opinion) smooshed compression > in with density selection. > > I don't see an easy solution that makes sense (as yet- this requires a lot > of thinking). Well, you don't have to go overboard. Combine compression and density. We have BSD semantics, I suppose, so the only other thing is no rewind, which we already cater for. So for, say, an Exabyte 8505XL, you'd have: /dev/rst0l 8202 mode, no compression /dev/rst0n 8202 mode, compression /dev/rst0h 8205 mode, no compression /dev/rst0c 8205 mode, compression /dev/nrst0l 8202 mode, no compression, no rewind /dev/nrst0n 8202 mode, compression, no rewind /dev/nrst0h 8205 mode, no compression, no rewind /dev/nrst0c 8205 mode, compression, no rewind Sure, it's more than now, but it shouldn't confuse people too much. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 19:31:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02091 for freebsd-current-outgoing; Mon, 14 Dec 1998 19:31:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02086 for ; Mon, 14 Dec 1998 19:31:31 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id TAA04941; Mon, 14 Dec 1998 19:31:15 -0800 Date: Mon, 14 Dec 1998 19:31:15 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Greg Lehey cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour In-Reply-To: <19981215135448.B15815@freebie.lemis.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 > > Well, you don't have to go overboard. Combine compression and > density. We have BSD semantics, I suppose, so the only other thing is > no rewind, which we already cater for. So for, say, an Exabyte > 8505XL, you'd have: > > /dev/rst0l 8202 mode, no compression > /dev/rst0n 8202 mode, compression > /dev/rst0h 8205 mode, no compression > /dev/rst0c 8205 mode, compression > /dev/nrst0l 8202 mode, no compression, no rewind > /dev/nrst0n 8202 mode, compression, no rewind > /dev/nrst0h 8205 mode, no compression, no rewind > /dev/nrst0c 8205 mode, compression, no rewind > > Sure, it's more than now, but it shouldn't confuse people too much. > Cool, but there are four possible densities in the current data structures. And speeds (has anyone actually ever found a drive that *uses* these?). And multiple compression algorithms to select from. I'm kind of inclined to think that the compromise of Rew/Norew X Compress/Nocompress X Low/High density is sufficient as long as you can establish that the latter two categories are a persistent (not through reboot, tho) cache of possible values that you can set via the mt(1) command. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 19:32:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02207 for freebsd-current-outgoing; Mon, 14 Dec 1998 19:32:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02202 for ; Mon, 14 Dec 1998 19:32:16 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id WAA11299; Mon, 14 Dec 1998 22:32:05 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA18379; Mon, 14 Dec 1998 22:32:05 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id WAA01942; Mon, 14 Dec 1998 22:32:04 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812150332.WAA01942@bb01f39.unx.sas.com> Subject: Re: List user In-Reply-To: From Narvi at "Dec 14, 98 05:59:02 pm" To: narvi@haldjas.folklore.ee (Narvi) Date: Mon, 14 Dec 1998 22:32:04 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm... interesting... this mail was originally returned to me as address unknown. It sent out fine the second time. There a definitely some bad addresses in the header... :-( -John > There's an adress to be unsubed... > > Aparently their mail<->news gateway is broken. > > Sander > > There is no love, no good, no happiness and no future - > all these are just illusions. > > On Mon, 14 Dec 1998, List User wrote: > > > Newsgroups: freebsd.current > > Path: root > > From: "John W. DeBoskey" > > Subject: Re: /etc/rc busted for legacy aout ldconfig setup > > Content-Type: text/plain; charset=US-ASCII > > Received: (from jwd@localhost) > > by bb01f39.unx.sas.com (8.9.1/8.9.1) id CAA15890; > > Mon, 14 Dec 1998 02:45:44 -0500 (EST) > > (envelope-from jwd) > > To: jb (John Birrell) > > Sender: owner-freebsd-current@FreeBSD.ORG > > Content-Transfer-Encoding: 7bit > > Organization: Private News Host > > Precedence: bulk > > Message-ID: <199812140745.CAA15890@bb01f39.unx.sas.com> > > X-Mailer: ELM [version 2.4ME+ PL38 (25)] > > Delivered-To: vmailer-current@freebsd.org > > X-Uidl: 9d579967b9e83b314d45c0c617e554d1 > > X-Loop: FreeBSD.ORG > > Mime-Version: 1.0 > > Cc: freebsd-current > > In-Reply-To: <199812140340.OAA01662@cimlogic.com.au> from John Birrell at "Dec 14, 98 02:40:13 pm" > > Date: Mon, 14 Dec 1998 07:45:44 GMT > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 19:32:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02281 for freebsd-current-outgoing; Mon, 14 Dec 1998 19:32:56 -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 TAA02274 for ; Mon, 14 Dec 1998 19:32:53 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id OAA29210; Tue, 15 Dec 1998 14:02:33 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812141129.DAA00571@dingo.cdrom.com> Date: Tue, 15 Dec 1998 14:02:23 +1030 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: New drivers and install floppy space Cc: Mikael Karpberg , obrien@NUXI.com, current@FreeBSD.ORG, "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Dec-98 Mike Smith wrote: > You forgot to put a bootblock on the image. Splat /boot/boot0 over the > first 512 bytes of the image and try again. There's a stock (no menu) > bootblock somewhere in the libdisk sources as well. OK.. I tried this... I got boot0 from a 3.0 system, but it doesn't work.. When it boots it finds it and then says Default : F2 And beeps when you press anything :( BTW this is a 2.2 system with a 3.0 boot0.. I couldn't make 3.0 CD cause the 3.0 system we have is packed up in the back room so we could have an A/C installed :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 19:39:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02730 for freebsd-current-outgoing; Mon, 14 Dec 1998 19:39:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ivory.trentu.ca (trentu.ca [192.75.12.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02725 for ; Mon, 14 Dec 1998 19:39:00 -0800 (PST) (envelope-from kfarmer@trentu.ca) Received: from trentu.ca ([192.75.12.156]) by trentu.ca (PMDF V5.1-10 #22248) with ESMTP id <01J5CEQKXCV00004BR@trentu.ca> for freebsd-current@FreeBSD.ORG; Mon, 14 Dec 1998 22:38:54 EST Date: Mon, 14 Dec 1998 22:39:59 -0500 From: Kelvin Subject: Re: Phantom hard drive detection in GENERIC? To: mike@smith.net.au, freebsd-current@FreeBSD.ORG Reply-to: kfarmer@trentu.ca Message-id: <3675DA0F.CE66DD69@trentu.ca> Organization: Trent University MIME-version: 1.0 X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Please wrap your paragraphs; it's hard (and thus discouraging) to reply > to a message that requires extra formatting effort. (Sorry, no-wrapping seems to be the default for mailing from Dejanews, I'll have to remember this!) >> wd3: can't handle 65535 heads from partition tale (truncating to 16) >> wd3 cannot handle 65535 sectors (max 255) >> wd3 wdcontrol: reca failed reading fsbn0wd3: status >> 7e error 4 >> wd3 error reading primary partition table reading fsbn 0 (wd3 bn0;cn0 tn0 sn0) > > When you say "halts the installation process", does it repeat the above > error message, or does it simply lock up at this point? It gives you the blue screen of death ;) labelled "Probing Devices, please wait" You need to hit Alt-F2 to see the above error messages. (They don't repeat) > Can you try winding back the BIOS IDE-related settings to their most > conservative values? Done. And interestingly, the "failsafe" settings don't cause this problem... so I went through the various options trying to track it down. It seems the problem lies with the BIOS option: "Delayed Transaction Enable" If this is enabled there is no problem. If it is disabled, then the problem occurs. The manual only says "set this option to enabled to enable the delayed transaction feature: the failsafe setting is enabled, the optimal setting is enabled, the maximum BIOS performance setting is disabled" a quick search of dejanews seems to indicate that "delayed transaction enable" should be enabled for PCI 2.1 compliance. Therefore, the problem would be my fault rather than FreeBSD. Thanks for the help. Kelvin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 19:52:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04090 for freebsd-current-outgoing; Mon, 14 Dec 1998 19:52:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04056; Mon, 14 Dec 1998 19:52:00 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id BAA09880; Tue, 15 Dec 1998 01:47:19 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199812150347.BAA09880@roma.coe.ufrj.br> Subject: Re: HEADS UP : laptop power-down change In-Reply-To: <199812112131.NAA05568@pox.remarque.org> from Rob Robertson at "Dec 11, 98 01:31:23 pm" To: rob@remarque.org (Rob Robertson) Date: Tue, 15 Dec 1998 01:47:19 -0200 (EDT) Cc: imp@village.org, phk@critter.freebsd.dk, archie@whistle.com, mike@smith.net.au, current@FreeBSD.ORG, mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG #define quoting(Rob Robertson) // having halt and halt -p map to the same thing on i386 seems // reasonable to me. // // ok, so how do you halt the processor without turning off the machine? // // create another command or option if you want to power off the // machine. Yes... What about Solaris' poweroff ? Lets let everybody happy. It could be a hard link to halt, of course. Oh, maybe shutdown(8) should be modified to pass some flags to halt(8), or at least to support poweroff mode. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 20:16:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05756 for freebsd-current-outgoing; Mon, 14 Dec 1998 20:16:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05715 for ; Mon, 14 Dec 1998 20:15:47 -0800 (PST) (envelope-from lh@aus.org) Received: from bsd.aus.org (lh@bsd.aus.org [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id WAA01723 for ; Mon, 14 Dec 1998 22:57:00 -0500 (EST) Message-Id: <199812150357.WAA01723@ayukawa.aus.org> X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812141106.DAA00405@dingo.cdrom.com> Date: Mon, 14 Dec 1998 23:15:28 -0500 (EST) Reply-To: lh@aus.org From: Luke To: current@FreeBSD.ORG Subject: Re: ide_pci.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> That solved the problem, and I can now use my CD-ROM drive, but I thought >> that you guys should know about the problem. Thanks. > > I'm sorry if I missed it, but I don't recall hearing from you what the > chipset on your IDE controller was; we kinda need this to fix the > problem "properly". > I have the same problem, with the 2nd IDE not showing up, so here :) I have an Acer Aladdin V chipset, the IDE chip is a 1543C. It also seems to have a bizarre UDMA problem (at certain clocksettings , DMA for IDE breaks ). I have a list of the PCI clocks , if that would help. --- E-Mail: Luke Sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 20:59:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10390 for freebsd-current-outgoing; Mon, 14 Dec 1998 20:59: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 UAA10382 for ; Mon, 14 Dec 1998 20:59:48 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA29986; Tue, 15 Dec 1998 15:29:26 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812141129.DAA00571@dingo.cdrom.com> Date: Tue, 15 Dec 1998 15:29:15 +1030 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: New drivers and install floppy space Cc: Mikael Karpberg , obrien@NUXI.com, current@FreeBSD.ORG, "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Dec-98 Mike Smith wrote: > You forgot to put a bootblock on the image. Splat /boot/boot0 over the > first 512 bytes of the image and try again. There's a stock (no menu) > bootblock somewhere in the libdisk sources as well. I tried the boot sector from tst01.c but no luck :( --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 21:28:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13328 for freebsd-current-outgoing; Mon, 14 Dec 1998 21:28:32 -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 VAA13323 for ; Mon, 14 Dec 1998 21:28:30 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id VAA23566; Mon, 14 Dec 1998 21:24:49 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdE23559; Tue Dec 15 05:24:42 1998 Message-ID: <3675F292.31DFF4F5@whistle.com> Date: Mon, 14 Dec 1998 21:24:34 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: lh@aus.org CC: current@FreeBSD.ORG Subject: Re: ide_pci.c References: <199812150357.WAA01723@ayukawa.aus.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luke wrote: > > I have the same problem, with the 2nd IDE not showing up, so here :) > I have an Acer Aladdin V chipset, the IDE chip is a 1543C. It also seems to > have a bizarre UDMA problem (at certain clocksettings , DMA for IDE breaks ). I > have a list of the PCI clocks , if that would help. > Can you define "breaks" ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 22:17:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18320 for freebsd-current-outgoing; Mon, 14 Dec 1998 22:17:19 -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 WAA18313 for ; Mon, 14 Dec 1998 22:17:11 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id IAA06709; Tue, 15 Dec 1998 08:15:39 +0200 (SAT) From: John Hay Message-Id: <199812150615.IAA06709@zibbi.mikom.csir.co.za> Subject: Re: PAO Integration? In-Reply-To: <199812141054.CAA00320@dingo.cdrom.com> from Mike Smith at "Dec 14, 98 02:54:58 am" To: mike@smith.net.au (Mike Smith) Date: Tue, 15 Dec 1998 08:15:39 +0200 (SAT) Cc: sanpei@sanpei.org, mike@smith.net.au, 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 > > mike@smith.net.au wrote: > > >> > > > >> > Do NE2000 Compatible PCMCIA cards work under PAO3, as it is now? > > >> > If so, is the development snapshot available anywhere? > > >> > > >> They work fine under stock 2.2 and 3.0 (this message is being sent > > >> using one). > > Content-Type: Text/Plain; charset=us-ascii > > Content-Transfer-Encoding: 7bit > > ... > > Tuple #6, code = 0x1b (Configuration entry), length = 25 > > 000: c1 81 78 ca 61 00 03 0f 10 03 0f 30 fc be c9 04 > > 010: 00 00 40 0d 40 40 00 40 0d > > Config index = 0x1(default) > > Interface byte = 0x81 (I/O) wait signal supported > > Card decodes 10 address lines, limited 8/16 Bit I/O > > I/O address # 1: block start = 0x300 block length = 0x10 > > I/O address # 2: block start = 0x310 block length = 0x10 > > IRQ modes: Level > > IRQs: 2 3 4 5 6 7 9 10 11 12 13 15 > > Memory descriptor 1 <------------------- > > blk length = 0x400 card addr = 0x000 host addr = 0xd4000 > > Memory descriptor 2 <------------------- > > blk length = 0x4000 card addr = 0x4000 host addr = 0xd4000 > > ---------- > > Review pccardd. > > PAO's assign_io function in pccardd/cardd.c has related code but > > it's comment is ``XXX -- dirty hack for some 'ed' cards that have > > incomplete iomem CIS tupples.'' > > But FreeBSD-current's assign_io function does not have it. > > > > I think that Mike's card does not have Memory descriptor.. Is > > that right? > > Yes; there's a long-standing bug in the way that the stock pccardd > deals with memory blocks < 4096 bytes, where it tries to allocate a > zero-sized window, which fails and thus the card is rejected. > > The memory region in question's not actually used for the card's > operation; the simplest fix would be to correct pccardd to either > expand any window < 4096 to 4096 or to just not map it (bad but > simpler). Why not just check if there is a next (second) region defined that consumes the first one and use that for the mapping? All the cards that I have seen and all the complaints in the mailinglists with printouts of the CIS have a second memory region that totally overlaps the first, if you look at the host addr and blk length. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 22:44:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20765 for freebsd-current-outgoing; Mon, 14 Dec 1998 22:44:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20759 for ; Mon, 14 Dec 1998 22:44:29 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:UoYOzChG2fTDziUdIP3ITQAjqt8O0/a5@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA01897; Tue, 15 Dec 1998 08:44:19 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:A18nsY5py8zffvMbwZYd6Ncj08ASJIuT@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id IAA67338; Tue, 15 Dec 1998 08:44:18 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812150644.IAA67338@greenpeace.grondar.za> To: Joe Abley cc: Kevin Day , freebsd-current@FreeBSD.ORG Subject: Re: modification to exec in the kernel? In-Reply-To: Your message of " Tue, 15 Dec 1998 12:48:18 +1300." <19981215124818.A22526@clear.co.nz> References: <19981215120357.B11837@clear.co.nz> <199812142331.RAA17203@home.dragondata.com> <19981215124818.A22526@clear.co.nz> Date: Tue, 15 Dec 1998 08:44:16 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Abley wrote: > I looked at that; however, remember the users will have chrooted access > to their directories, and within the chrooted tree will be /usr and > descendants containing controlled binaries (owned by someone else, e.g. > "root") like perl, awk, sh, etc. Your security model is flawed. A user can do anything she wants (justabout) with shellscript and perl. Picking on compiled binaries is not going to make you that much safer. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 22:51:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21530 for freebsd-current-outgoing; Mon, 14 Dec 1998 22:51:33 -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 WAA21525 for ; Mon, 14 Dec 1998 22:51:31 -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 0zpoKF-0004Hd-00; Mon, 14 Dec 1998 23:51:19 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id XAA02978; Mon, 14 Dec 1998 23:49:38 -0700 (MST) Message-Id: <199812150649.XAA02978@harmony.village.org> To: Mike Smith Subject: Re: PAO Integration? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 13 Dec 1998 15:21:25 PST." <199812132321.PAA00350@dingo.cdrom.com> References: <199812132321.PAA00350@dingo.cdrom.com> Date: Mon, 14 Dec 1998 23:49:37 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812132321.PAA00350@dingo.cdrom.com> Mike Smith writes: : Drivers should export a set of options that are a union of the set of : options the driver supports plus a subset of the options for a device : provided by the bus. This can be determined by examining the driver : and bus data at probe/attach time; something that's easy with KLD/ : newbus/loader, but would require a bolt-on for newconfig. A sysctl-like mechanism would likely be a good idea. Let me explain what I have in mind. First, let us say that there are configuration files. Let us say these files use the sysctl syntax. Let us further suppose that we extend the sysctl notation to include wild cards. We'd have something similar to the xdefaults (xrdb actually) syntax. This sparse database would be kept around. When modules are initialized (either as being part of the base system, statically linked in, or when dynamically loaded by some means), the sysctl's variables are set (if they match this sparse database). Now, this would allow drivers and other modules to be dynamically configured in a user friendly manner. The "sparse database" would allow for the user to specify things (eg the band for a radio modem, the video signalling to use (ntsc vs pal), etc). Some examples: driver.aha*tune_bus: 1 driver.bt848*video_format: ntsc When the aha driver starts, it registers the sysctl variable driver.aha.unit0.tune_bus and then finds its value. Since it matchces the above sepecification, it will have a value of 1 when the driver checks its value. This would allow a very easy way to configure and customize the modules that are loaded and unloaded. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 22:56:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21790 for freebsd-current-outgoing; Mon, 14 Dec 1998 22:56:29 -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 WAA21778 for ; Mon, 14 Dec 1998 22:56:26 -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 0zpoOz-0004I4-00; Mon, 14 Dec 1998 23:56:13 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id XAA03013; Mon, 14 Dec 1998 23:54:32 -0700 (MST) Message-Id: <199812150654.XAA03013@harmony.village.org> To: John Hay Subject: Re: PAO Integration? Cc: mike@smith.net.au (Mike Smith), sanpei@sanpei.org, current@FreeBSD.ORG In-reply-to: Your message of "Sat, 15 Dec 1998 08:15:39 +0200." <199812150615.IAA06709@zibbi.mikom.csir.co.za> References: <199812150615.IAA06709@zibbi.mikom.csir.co.za> Date: Mon, 14 Dec 1998 23:54:32 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812150615.IAA06709@zibbi.mikom.csir.co.za> John Hay writes: : Why not just check if there is a next (second) region defined that : consumes the first one and use that for the mapping? All the cards : that I have seen and all the complaints in the mailinglists with : printouts of the CIS have a second memory region that totally : overlaps the first, if you look at the host addr and blk length. I've been seeing all kinds of problems with the cards that I have in my libretto on my Libretto 50CT. Especially when suspending and resuming as well as when swapping many different cards. I have some minor changes that seem to help a little, but there are lots of things that it just doesn't cope with well. They are not ready for prime time yet... "It" here is pccardd. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 23:34:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26040 for freebsd-current-outgoing; Mon, 14 Dec 1998 23:34: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 XAA26028 for ; Mon, 14 Dec 1998 23:34:30 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA23506; Tue, 15 Dec 1998 00:34:22 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp01.primenet.com, id smtpd023403; Tue Dec 15 00:34:09 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id AAA12910; Tue, 15 Dec 1998 00:34:08 -0700 (MST) From: Terry Lambert Message-Id: <199812150734.AAA12910@usr06.primenet.com> Subject: Re: HEADS UP : laptop power-down change To: mike@smith.net.au (Mike Smith) Date: Tue, 15 Dec 1998 07:34:08 +0000 (GMT) Cc: tlambert@primenet.com, imp@village.org, mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: <199812150250.SAA02049@dingo.cdrom.com> from "Mike Smith" at Dec 14, 98 06:49: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 > > Also, I think the correct flag is "-x", not "-p", from a historical > > (Sony NeWS, NeXTStep, and A/UX, et. al.). > > That's a good point; now is probably the time to change it to be > consistent. Any conflicting examples? Apparently NeXTStep uses "-p". Time for a survey. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 14 23:58:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28059 for freebsd-current-outgoing; Mon, 14 Dec 1998 23:58:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28054 for ; Mon, 14 Dec 1998 23:58:21 -0800 (PST) (envelope-from lh@aus.org) Received: from bsd.aus.org (lh@bsd.aus.org [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id CAA04078 for ; Tue, 15 Dec 1998 02:39:45 -0500 (EST) Message-Id: <199812150739.CAA04078@ayukawa.aus.org> X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3675F292.31DFF4F5@whistle.com> Date: Tue, 15 Dec 1998 02:58:14 -0500 (EST) Reply-To: lh@aus.org From: Luke To: current@FreeBSD.ORG Subject: Re: ide_pci.c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I have the same problem, with the 2nd IDE not showing up, so here :) >> I have an Acer Aladdin V chipset, the IDE chip is a 1543C. It also seems to >> have a bizarre UDMA problem (at certain clocksettings , DMA for IDE breaks >> ). I have a list of the PCI clocks , if that would help. >> > > > Can you define "breaks" ? > At many cpu clock settings, with DMA turned on, booting is fine, but as soon as the device detection part is done, and rc I guess is being run, theres a flood of DMA errors like (not 100% on this) wd0: DMA failure DMA status 5 I actually started trying to figure out ide_pci.c but its beyond my ability. I think it is because the PCI clock is different for every cpu clock setting , I have 2 mbs with this chipset, one only works set at 66mhz , one at 75mhz. I could and would be willing to mess with this on my machine, and I have a list of clock settings per cpu settings for this board. The only reason its annoying is because I stuck 100mhz sdram in here and have to have it running at 66mhz. I dont know if having it set to 100mhz would make any difference, its just the fact that I cant do it that bugs me :) --- E-Mail: Luke Sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 00:27:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01466 for freebsd-current-outgoing; Tue, 15 Dec 1998 00:27:14 -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 AAA01248; Tue, 15 Dec 1998 00:27:08 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id BAA17431; Tue, 15 Dec 1998 01:26:58 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd017377; Tue Dec 15 01:26:57 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id BAA16811; Tue, 15 Dec 1998 01:26:39 -0700 (MST) From: Terry Lambert Message-Id: <199812150826.BAA16811@usr06.primenet.com> Subject: Re: if_sppp is BROKEN!!! To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Tue, 15 Dec 1998 08:26:39 +0000 (GMT) Cc: johan@granlund.nu, julian@whistle.com, phk@FreeBSD.ORG, lars@akerlings.t.se, current@FreeBSD.ORG, isdn@FreeBSD.ORG In-Reply-To: <199812142307.PAA27390@hub.freebsd.org> from "Jonathan M. Bresler" at Dec 14, 98 03:07:41 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 idea of streams is wonderful, the realization is costly. each > layer added (or module pushed) slows down processing and hurts > throughput. ritchie developed streams for serial, if i remember > correctly. streams was then applied to networks. there is an RFC > about layering being bad for networking and the relative performance > of NIT vs BPF prove the case. The main drawback in streams is that, even in ideal conditions, when you get two or more layers interacting (that is, when you get one stack element between the "top" and "bottom", other than "null"), you have to take a context switch to propagate the data in at least one direction, if not both. Some hacks (at Novell) ran the push up to the top of the stack at interrupt level to try to avoid this, but of course, it failed rather spectacularly if you added things like MUX modules on top of IPX on top of SPX. In general, the fact that the getmsg/putmsg had to run in a process context, and that that context was given over by any process going into or coming out of a system call, as well as ther switchpoints in the kernel contributed to the general idea that STREAMS was a pig. When UnixWare went from a monolithic driver implemetnation (like what's in FreeBSD now) to NetWare drivers running under UNIX using a shim layer, there was an additional 35% latency, overall, that was introduced into a three module stack. I think that netgraph resolves some, but not all, of these issues. Ideally, you would want an operation to propagate the full stack, up or down, as a result of one operation. A long time ago (mid 1994), I did a full SVR4-style priority banded STREAMS implementation for FreeBSD as part of an inside "skunkworks" project to port NWU (NetWare for UNIX) to FreeBSD and Linux. I resolved a number of these issues internally by creating a high priority kernel process to push things up and down the stack; sort of a soft interrupt handler, if you will. A worker process can go a long way to resolving the streams latency issues; it also didn't hurt that FreeBSD monolithic network drivers were faster than the ones in UnixWare. 8-). I bet that if these same issues were measured in netgraph, a similar tactic would be sufficient to resolve the vast majority of cases (one exception being if someone declared a network task "real time", and no one bothered to implement priority lending to stave off inversion; but that's pilot error). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 00:27:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01528 for freebsd-current-outgoing; Tue, 15 Dec 1998 00:27:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01515 for ; Tue, 15 Dec 1998 00:27:30 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id RAA02605; Tue, 15 Dec 1998 17:22:36 +0900 (JST) Message-Id: <199812150822.RAA02605@chandra.eatell.msr.prug.or.jp> To: Mike Smith cc: Garrett Wollman , Nate Williams , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sun, 13 Dec 1998 15:19:22 PST." <199812132319.PAA00332@dingo.cdrom.com> Date: Tue, 15 Dec 1998 17:22:35 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - We aren't CopycatBSD; the "new bus" group is attempting to develop > a new, better approach to handling the bus/bridge/device > relationships. "newconfig" is better than what we have right now, > but it is not good enough. Why do you make another framework ? Why not improve 4.4BSD bus and config code ? FreeBSD, it is 4.4BSD based OS. If you want to make new framework, why FreeBSD ? I think FreeBSD is one of 4.4BSD-children, and I want to use BSD like OS, not Linux. I want to integrate other BSDs, if possible. (I know, it is too hard really.) "newconfig aproach" is improvement NetBSD-current bus and config code. > - Bus architecture "incompatibility" is not actually a significant > issue. We are already 100% bus architecture incompatible with the > other BSDs, change simply for compatibility's sake won't give us any > benefits, and it would stifle any attempt to do better. Right now > the few drivers that are shared amongst the BSD's all have different > bus interface code anyway; there is nothing that will get "worse" if > we change the mechanics of the interface. There are also things > that we are trying to do that can't be done with newconfig (at > least, as it is right now - for sure it too can be modified). At least, I want to reduce driver porting cost. In "newconfig", its cost from other BSDs is quite low. > - Static configuration is evil. More specifically, static > configuration is a special case of dynamic configuration. > "newconfig" does static configuration very well, but the "newconfig" > architecture is not at all suitable for dynamic configuration. Some case, static configuration is very useful. For example, 1 floppy router like PicoBSD, and etc .... And "newconfig" is not static configuration only, also dynamic configuration can use. We are planning add UserConfig to "newconfig", it is *true* dynamic configuration. #Old NetBSD configuration problem, it is NOT already exist. On "new-bus", How to handle boot device like console, fd, wd, ... ? > I don't mean to say "newconfig is bad", so much as to say "new bus is > better again". OK, But I think "newconfig is better". Better "source code" should be win others. I think it is correct. I want to talk by "source code". "source code" is our common language. :-) -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 00:42:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03036 for freebsd-current-outgoing; Tue, 15 Dec 1998 00:42:38 -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 AAA03031 for ; Tue, 15 Dec 1998 00:42:37 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id BAA20759; Tue, 15 Dec 1998 01:42:32 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd020726; Tue Dec 15 01:42:15 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id BAA17883; Tue, 15 Dec 1998 01:42:13 -0700 (MST) From: Terry Lambert Message-Id: <199812150842.BAA17883@usr06.primenet.com> Subject: Re: PAO Integration? To: y-nakaga@nwsl.mesh.ad.jp (NAKAGAWA Yoshihisa) Date: Tue, 15 Dec 1998 08:42:13 +0000 (GMT) Cc: mike@smith.net.au, wollman@khavrinen.lcs.mit.edu, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG In-Reply-To: <199812150822.RAA02605@chandra.eatell.msr.prug.or.jp> from "NAKAGAWA Yoshihisa" at Dec 15, 98 05:22:35 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > - We aren't CopycatBSD; the "new bus" group is attempting to develop > > a new, better approach to handling the bus/bridge/device > > relationships. "newconfig" is better than what we have right now, > > but it is not good enough. > > Why do you make another framework ? Why not improve 4.4BSD bus and > config code ? FreeBSD, it is 4.4BSD based OS. If you want to make new > framework, why FreeBSD ? > > I think FreeBSD is one of 4.4BSD-children, and I want to use BSD > like OS, not Linux. I want to integrate other BSDs, if possible. > (I know, it is too hard really.) > > "newconfig aproach" is improvement NetBSD-current bus and config code. I think the main reason for this is that "config" is a crutch used by kernels that can't dynamically change driver data and/or drivers. Try to name one ting that you could do with "config" that you could not do with a sufficiently dynamic kernel loadable module framework. The current three stage boot code is capable of loading a kernel and as many kld's as you need it to, at boot time. It's also capable (with a bit of hacking) of throwing away kld's for which there are no devices to attach. > At least, I want to reduce driver porting cost. In "newconfig", > its cost from other BSDs is quite low. That's a valid point of view. But so is the idea that a BSD could give ELF format kld's to a vendor for distribution on the vendor CDROM/floppies, and have FreeBSD supported automatically. The vendor wins because the BSD people did the developement, and BSD wins because the drivers and the hardware are bundled. > Some case, static configuration is very useful. For example, 1 > floppy router like PicoBSD, and etc .... That's mere agregation, to my mind, not static configuration. If you want to define an agregate as state merely because it's a fixed instance of an image, I think you are doing a disservice to the idea. > And "newconfig" is not static configuration only, also dynamic > configuration can use. We are planning add UserConfig to > "newconfig", it is *true* dynamic configuration. UserConfig is not dynamic, it's boot time. Dynamic is when you can boot FreeBSD on hardware using VM86() INT 13 calls, load a protected mode driver, and switch over to using it without rebooting. Windows 95/98 can do this because it has to to allow TSR's to operate, but no other OS comes close, not even NT. Try to install NT on a system with an unsupported SCSI controller with only a vendor supplied driver. You can do it, but there is a secret step in the middle where you have to manually copy the driver to exactly the right location on the hard drive. > On "new-bus", How to handle boot device like console, fd, wd, ... ? Generic fallback drivers, with hardware specific implemetnations that get loaded once you've bootstrapped yourself. > > I don't mean to say "newconfig is bad", so much as to say "new bus is > > better again". > > OK, But I think "newconfig is better". Better than the status quo, but not better than something that does away with the user having to mess around with interrupts altogether. Any time you can limit the exposure of the internals to the end user is a win. You understand the idea of abstracting API's? It's the same thing -- except what you are abstracting is complexity. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 00:49:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03382 for freebsd-current-outgoing; Tue, 15 Dec 1998 00:49:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA03362; Tue, 15 Dec 1998 00:49:11 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (2128 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Tue, 15 Dec 1998 09:48:50 +0100 (MET) (Smail-3.2.0.101 1997-Dec-17 #2 built 1998-Jun-26) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m0zpqD8-0000f8C; Tue, 15 Dec 98 09:52 MET Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: if_sppp is BROKEN!!! In-Reply-To: <199812150826.BAA16811@usr06.primenet.com> from Terry Lambert at "Dec 15, 98 08:26:39 am" To: tlambert@primenet.com (Terry Lambert) Date: Tue, 15 Dec 1998 09:52:05 +0100 (MET) Cc: current@FreeBSD.ORG, isdn@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (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 >From the keyboard of Terry Lambert: (Cc: stripped) > Ideally, you would want an operation to propagate the full stack, > up or down, as a result of one operation. Can you please explain why one operation wants to propagate the full stack ? Background: In the current i4b ISDN implementation exactly this happens, i.e. a layer 1 IRQ triggers an action in layer 2 triggering an action in layer 3 which triggers an action (going down now) in layer 2 triggering an action in layer 1 again. The problem of this going up and down at IRQ time is not only the time lasting, but i.e. layer 2 being in a state transition which is not fully finished when the reply from layer 3 going down enters layer 2 again (being still in the middle of the previous up-going state transition). Until now i was under the impression that only a decoupling of the layers would make the transitions in one layer an atomic operation to avoid the above described scenario. hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 00:54:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03894 for freebsd-current-outgoing; Tue, 15 Dec 1998 00:54:44 -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 AAA03889 for ; Tue, 15 Dec 1998 00:54:42 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id JAA16330; Tue, 15 Dec 1998 09:50:17 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199812150850.JAA16330@ocean.campus.luth.se> Subject: Re: HEADS UP : laptop power-down change In-Reply-To: <199812150734.AAA12910@usr06.primenet.com> from Terry Lambert at "Dec 15, 98 07:34:08 am" To: tlambert@primenet.com (Terry Lambert) Date: Tue, 15 Dec 1998 09:50:17 +0100 (CET) Cc: mike@smith.net.au, tlambert@primenet.com, imp@village.org, 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 Terry Lambert: > > > Also, I think the correct flag is "-x", not "-p", from a historical > > > (Sony NeWS, NeXTStep, and A/UX, et. al.). > > > > That's a good point; now is probably the time to change it to be > > consistent. Any conflicting examples? > > Apparently NeXTStep uses "-p". Time for a survey. 8-(. Is it really a problem? Just make "-p" AND "-x" mean power off, and people can chose the one they like. :-) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 01:07:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04759 for freebsd-current-outgoing; Tue, 15 Dec 1998 01:07:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04754 for ; Tue, 15 Dec 1998 01:07:28 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id KAA04156; Tue, 15 Dec 1998 10:06:12 +0100 (CET) Received: from wurzelausix (quadratix.cs.uni-sb.de [134.96.222.2]) by cs.uni-sb.de (8.9.1a/1998121400) with ESMTP id KAA13372; Tue, 15 Dec 1998 10:06:13 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:r9xNI2YVBOKXQL3qriB6rsTs0FVrqFyS@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id KAA01672; Tue, 15 Dec 1998 10:06:07 +0100 (CET) Message-Id: <199812150906.KAA01672@wurzelausix> Date: Tue, 15 Dec 1998 10:06:05 +0100 (CET) From: Alexander Leidinger Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? To: dillon@apollo.backplane.com cc: current@FreeBSD.ORG In-Reply-To: <199812141723.JAA45920@apollo.backplane.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 14 Dec, Matthew Dillon wrote: > It seemed to do the right thing for me, once I finally got the > object modules and other junk cleaned out of /usr/src from all > my partial makes (i.e. when you do something like > 'cd /usr/src/usr.bin/ls; make; make install' and for to 'make clean'). freebsd.cf (/usr/src/etc/...) gets created in /usr/obj/... after you cleaned out /usr/src from partial makes? Sounds very strange. find /usr/src -name \*.o -print shows only /*.o find /usr/src -name .depend -print shows /.depend Last cvsup on this machine: Dec, 7 Do I have to check it with a more recent current? Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 01:15:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05618 for freebsd-current-outgoing; Tue, 15 Dec 1998 01:15:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05612 for ; Tue, 15 Dec 1998 01:15:37 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id BAA52668; Tue, 15 Dec 1998 01:15:17 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Dec 1998 01:15:17 -0800 (PST) From: Matthew Dillon Message-Id: <199812150915.BAA52668@apollo.backplane.com> To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? References: <199812150906.KAA01672@wurzelausix> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On 14 Dec, Matthew Dillon wrote: : :> It seemed to do the right thing for me, once I finally got the :> object modules and other junk cleaned out of /usr/src from all :> my partial makes (i.e. when you do something like :> 'cd /usr/src/usr.bin/ls; make; make install' and for to 'make clean'). : :freebsd.cf (/usr/src/etc/...) gets created in /usr/obj/... after you :cleaned out /usr/src from partial makes? :Sounds very strange. As far as I can tell. :find /usr/src -name \*.o -print :shows only /*.o : :find /usr/src -name .depend -print :shows /.depend The object files, .depend files, binaries, synthesized source files, and other junk residing in /usr/src are typically left-overs from manual builds of various subprograms. i.e. if I need to recompile/reinstall, say, inetd I usually do: cd /usr/src/usr.sbin/inetd make make install make clean <----- the piece I often forget to do (objects, binaries, etc... are created in /usr/src, not /usr/obj) So after a while, junk builds up in /usr/src. When I get all the junk removed, buildworld seems to only operate in /usr/obj and everythings goes fine. If I don't remove all the junk, buildworld attempts to remove it from /usr/src for me which, of course, fails miserably over a read-only NFS mount. :Last cvsup on this machine: Dec, 7 : :Do I have to check it with a more recent current? : :Bye, :Alexander. Can't help you there. I would definitely sync up to the latest current. I think buildworld works as of the current moment. -Matt :-- :http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 01:18:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA05802 for freebsd-current-outgoing; Tue, 15 Dec 1998 01:18:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05797 for ; Tue, 15 Dec 1998 01:18:23 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id BAA52694; Tue, 15 Dec 1998 01:17:45 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Dec 1998 01:17:45 -0800 (PST) From: Matthew Dillon Message-Id: <199812150917.BAA52694@apollo.backplane.com> To: Mark Murray Cc: Joe Abley , Kevin Day , freebsd-current@FreeBSD.ORG Subject: Re: modification to exec in the kernel? References: <19981215120357.B11837@clear.co.nz> <199812142331.RAA17203@home.dragondata.com> <19981215124818.A22526@clear.co.nz> <199812150644.IAA67338@greenpeace.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Joe Abley wrote: :> I looked at that; however, remember the users will have chrooted access :> to their directories, and within the chrooted tree will be /usr and :> descendants containing controlled binaries (owned by someone else, e.g. :> "root") like perl, awk, sh, etc. : :Your security model is flawed. A user can do anything she wants :(justabout) with shellscript and perl. Picking on compiled binaries :is not going to make you that much safer. : :M I think a chroot'd environment can be even *more* dangerous then a non-chroot'd environment because critical system configuration files will be missing and potentially creatable by the user - if the chroot'd environment is based in a user-owned directory and you've installed any suid or sgid system binaries, you have an extremely serious security hole on your hands. -Matt :-- :Mark Murray :Join the anti-SPAM movement: http://www.cauce.org : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 01:26:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06295 for freebsd-current-outgoing; Tue, 15 Dec 1998 01:26:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA06289 for ; Tue, 15 Dec 1998 01:26:27 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id KAA04334; Tue, 15 Dec 1998 10:25:47 +0100 (CET) Received: from wurzelausix (quadratix.cs.uni-sb.de [134.96.222.2]) by cs.uni-sb.de (8.9.1a/1998121400) with ESMTP id KAA13615; Tue, 15 Dec 1998 10:25:46 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:NlXyX4JIm6nadw0K6EPoh8iJcf0Im++J@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id KAA02243; Tue, 15 Dec 1998 10:25:41 +0100 (CET) Message-Id: <199812150925.KAA02243@wurzelausix> Date: Tue, 15 Dec 1998 10:25:39 +0100 (CET) From: Alexander Leidinger Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? To: dillon@apollo.backplane.com cc: current@FreeBSD.ORG In-Reply-To: <199812150915.BAA52668@apollo.backplane.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 15 Dec, Matthew Dillon wrote: > So after a while, junk builds up in /usr/src. When I get all the junk The only thing I build manualy in /usr/src is sysinstall. > fine. If I don't remove all the junk, buildworld attempts to remove it > from /usr/src for me which, of course, fails miserably over a read-only > NFS mount. Thats not my problem. > :Do I have to check it with a more recent current? > > Can't help you there. I would definitely sync up to the latest current. > I think buildworld works as of the current moment. Ok, this seems to be the request I asked for. Im going to cvsup && buildworld. Expect the result (Yes, it works/no it did not) in some hours. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 01:34:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07145 for freebsd-current-outgoing; Tue, 15 Dec 1998 01:34:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07140 for ; Tue, 15 Dec 1998 01:34:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA04087; Tue, 15 Dec 1998 01:30:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812150930.BAA04087@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Hay cc: mike@smith.net.au (Mike Smith), sanpei@sanpei.org, current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sat, 15 Dec 1998 08:15:39 +0200." <199812150615.IAA06709@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 01:30:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I think that Mike's card does not have Memory descriptor.. Is > > > that right? > > > > Yes; there's a long-standing bug in the way that the stock pccardd > > deals with memory blocks < 4096 bytes, where it tries to allocate a > > zero-sized window, which fails and thus the card is rejected. > > > > The memory region in question's not actually used for the card's > > operation; the simplest fix would be to correct pccardd to either > > expand any window < 4096 to 4096 or to just not map it (bad but > > simpler). > > Why not just check if there is a next (second) region defined that > consumes the first one and use that for the mapping? All the cards > that I have seen and all the complaints in the mailinglists with > printouts of the CIS have a second memory region that totally > overlaps the first, if you look at the host addr and blk length. Memory regions don't work that way; two regions based at 0 of length X and Y are separate regions that have to be mapped separately into the system memory space. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 02:36:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11486 for freebsd-current-outgoing; Tue, 15 Dec 1998 02:36:11 -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 CAA11479 for ; Tue, 15 Dec 1998 02:36:05 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id MAA10471; Tue, 15 Dec 1998 12:34:17 +0200 (SAT) From: John Hay Message-Id: <199812151034.MAA10471@zibbi.mikom.csir.co.za> Subject: Re: PAO Integration? In-Reply-To: <199812150930.BAA04087@dingo.cdrom.com> from Mike Smith at "Dec 15, 98 01:30:31 am" To: mike@smith.net.au (Mike Smith) Date: Tue, 15 Dec 1998 12:34:17 +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 > > > > I think that Mike's card does not have Memory descriptor.. Is > > > > that right? > > > > > > Yes; there's a long-standing bug in the way that the stock pccardd > > > deals with memory blocks < 4096 bytes, where it tries to allocate a > > > zero-sized window, which fails and thus the card is rejected. > > > > > > The memory region in question's not actually used for the card's > > > operation; the simplest fix would be to correct pccardd to either > > > expand any window < 4096 to 4096 or to just not map it (bad but > > > simpler). > > > > Why not just check if there is a next (second) region defined that > > consumes the first one and use that for the mapping? All the cards > > that I have seen and all the complaints in the mailinglists with > > printouts of the CIS have a second memory region that totally > > overlaps the first, if you look at the host addr and blk length. > > Memory regions don't work that way; two regions based at 0 of length X > and Y are separate regions that have to be mapped separately into the > system memory space. Even if like in this example, it says that both of these regions use "host addr = 0xd4000"? I would think that you only have one region through which you talk to the card and have some other way (like an io register that you set) to differentiate between the two regions on the card, but that doesn't mean you need more than one system memory space to talk to the card. Note, this doesn't mean you won't have other kinds of cards that need more than one region, but we are not talking about them at the moment, we are just talking about pccard devices with a CIS that is different from what we expect them to be. What is happenning is that they give us more detailed information about what they look like inside and that confuse pccardd. The same kind of thing should be done for the IO space. In this example it says it needs two adjacent regions and there pccardd should just be clever enough to combine it into one region. > > Config index = 0x1(default) > > Interface byte = 0x81 (I/O) wait signal supported > > Card decodes 10 address lines, limited 8/16 Bit I/O > > I/O address # 1: block start = 0x300 block length = 0x10 > > I/O address # 2: block start = 0x310 block length = 0x10 > > IRQ modes: Level > > IRQs: 2 3 4 5 6 7 9 10 11 12 13 15 > > Memory descriptor 1 <------------------- > > blk length = 0x400 card addr = 0x000 host addr = 0xd4000 > > Memory descriptor 2 <------------------- > > blk length = 0x4000 card addr = 0x4000 host addr = 0xd4000 John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 02:40:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12221 for freebsd-current-outgoing; Tue, 15 Dec 1998 02:40:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schuimpje.snt.utwente.nl (schuimpje.snt.utwente.nl [130.89.238.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11812 for ; Tue, 15 Dec 1998 02:37:47 -0800 (PST) (envelope-from gelderen@mediaport.org) Received: from wit395306.student.utwente.nl ([130.89.235.126]:7940 "HELO deskfix" ident: "NO-IDENT-SERVICE[2]") by schuimpje.snt.utwente.nl with SMTP id <8053-18880>; Tue, 15 Dec 1998 11:37:30 +0100 Message-ID: <00ab01be2816$c5a0e4c0$1400000a@deskfix.local> From: "Jeroen C. van Gelderen" To: "Terry Lambert" , "Mike Smith" Cc: , , , Subject: Re: HEADS UP : laptop power-down change Date: Tue, 15 Dec 1998 11:36:27 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Terry Lambert >> > Also, I think the correct flag is "-x", not "-p", from a historical >> > (Sony NeWS, NeXTStep, and A/UX, et. al.). >> >> That's a good point; now is probably the time to change it to be >> consistent. Any conflicting examples? > >Apparently NeXTStep uses "-p". Time for a survey. 8-(. Below is the appropriate Linux man page: ------------------------- NAME halt, reboot, poweroff - stop the system. SYNOPSIS /sbin/halt [-n] [-w] [-d] [-f] [-i] [-p] /sbin/reboot [-n] [-w] [-d] [-f] [-i] /sbin/poweroff [-n] [-w] [-d] [-f] [-i] DESCRIPTION Halt notes that the system is being brought down in the file /var/log/wtmp, and then either tells the kernel to halt, reboot or poweroff the system. If halt or reboot is called when the system is not in runlevel 0 or 6, shut­ down(8) will be invoked instead (with the flag -h or -r). OPTIONS -n Don't sync before reboot or halt. -w Don't actually reboot or halt but only write the wtmp record (in the /var/log/wtmp file). -d Don't write the wtmp record. The -n flag implies -d. -f Force halt or reboot, don't call shutdown(8). -i Shut down all network interfaces just before halt or reboot. -p When halting the system, do a poweroff. This is the default when halt is called as poweroff. ------------------------- -- Jeroen C. van Gelderen -- gelderen@mediaport.org -- &[8-D}~<= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 03:08:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14345 for freebsd-current-outgoing; Tue, 15 Dec 1998 03:08:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14340 for ; Tue, 15 Dec 1998 03:08:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id DAA04711; Tue, 15 Dec 1998 03:04:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812151104.DAA04711@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Hay cc: mike@smith.net.au (Mike Smith), current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Sat, 15 Dec 1998 12:34:17 +0200." <199812151034.MAA10471@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 03:04:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Why not just check if there is a next (second) region defined that > > > consumes the first one and use that for the mapping? All the cards > > > that I have seen and all the complaints in the mailinglists with > > > printouts of the CIS have a second memory region that totally > > > overlaps the first, if you look at the host addr and blk length. > > > > Memory regions don't work that way; two regions based at 0 of length X > > and Y are separate regions that have to be mapped separately into the > > system memory space. > > Even if like in this example, it says that both of these regions use > "host addr = 0xd4000"? Yup. Exactly what you do with the regions is up to the driver; there may be other CIS information that describes them in more detail, but we don't have all of the CIS here obviously. It's possible that the two regions are meant to be used for different purposes at different times. > I would think that you only have one region through > which you talk to the card and have some other way (like an io register > that you set) to differentiate between the two regions on the card, but > that doesn't mean you need more than one system memory space to talk to > the card. Agreed; we almost certainly should not simply be blindly mapping every region that's listed in the CIS. > The same kind of thing should be done for the IO space. In this example > it says it needs two adjacent regions and there pccardd should just be > clever enough to combine it into one region. I'm not sure in this case whether this actually indicates two separate regions or one region which can be located at two different addresses; I'm on the other side of the Pacific from the docco right now. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 03:35:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15746 for freebsd-current-outgoing; Tue, 15 Dec 1998 03:35:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15741 for ; Tue, 15 Dec 1998 03:35:43 -0800 (PST) (envelope-from rkw@nomad.dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id FAA07262; Tue, 15 Dec 1998 05:34:32 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Tue, 15 Dec 1998 05:34:32 -0600 (CST) From: Richard Wackerbarth To: Mike Smith cc: Kenjiro Cho , NAKAGAWA Yoshihisa , current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812132016.MAA00365@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 Sun, 13 Dec 1998, Mike Smith wrote: > It's worth pointing out that we are now quite a long way down the path > to this goal; by no means all the way there, but the new bus > architecture coupled with KLD modules does largely obviate the need for > config(8) in the first place. > > I'm of the strong opinion that our current direction, taking us away > from static configuration, is the right one to be taking in the context > of our current and projected future target architectures. It is no > longer adequate nor desirable to require the kernel to be rebuilt to > adapt to a new system configuration, and we need to reflect this in our > architecture. I support Mike's opinion on this matter. At the same time, I think that the PAO folks recognize that there is a need to support the rogue devices that cannot be handled in any fashion other than manual intervention ("Damn it! I know that this card uses IRQ .. and .... . Just do it that way.") Can we have a scheme whereby the "ultra-new-config" utility generates glue modules for just those devices? By adding the resulting KLDs to the load mix, the legacy hardware would be accomodated in the same framework that the rest of the dynamic system uses. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 04:07:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20653 for freebsd-current-outgoing; Tue, 15 Dec 1998 04:07:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20644 for ; Tue, 15 Dec 1998 04:07:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id EAA05066; Tue, 15 Dec 1998 04:05:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812151205.EAA05066@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Richard Wackerbarth cc: Mike Smith , Kenjiro Cho , NAKAGAWA Yoshihisa , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Tue, 15 Dec 1998 05:34:32 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 04:05:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Sun, 13 Dec 1998, Mike Smith wrote: > > > It's worth pointing out that we are now quite a long way down the path > > to this goal; by no means all the way there, but the new bus > > architecture coupled with KLD modules does largely obviate the need for > > config(8) in the first place. > > > > I'm of the strong opinion that our current direction, taking us away > > from static configuration, is the right one to be taking in the context > > of our current and projected future target architectures. It is no > > longer adequate nor desirable to require the kernel to be rebuilt to > > adapt to a new system configuration, and we need to reflect this in our > > architecture. > > I support Mike's opinion on this matter. At the same time, I think that > the PAO folks recognize that there is a need to support the rogue devices > that cannot be handled in any fashion other than manual intervention > ("Damn it! I know that this card uses IRQ .. and .... . Just do it that > way.") There's no way that we're going to obsolete "manual configuration" in the forseeable future; ISA is not going to die that easily I fear. > Can we have a scheme whereby the "ultra-new-config" utility generates > glue modules for just those devices? By adding the resulting KLDs to the > load mix, the legacy hardware would be accomodated in the same framework > that the rest of the dynamic system uses. The problem that we're seeing in this discussion is the confusion between configuration information and driver code, or the module and its metadata. There will always be a mechanism for passing metadata to an instance of a driver. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 04:16:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21351 for freebsd-current-outgoing; Tue, 15 Dec 1998 04:16:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21346 for ; Tue, 15 Dec 1998 04:16:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id EAA05117; Tue, 15 Dec 1998 04:14:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812151214.EAA05117@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: Mike Smith , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Mon, 14 Dec 1998 23:49:37 MST." <199812150649.XAA02978@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 04:14:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199812132321.PAA00350@dingo.cdrom.com> Mike Smith writes: > : Drivers should export a set of options that are a union of the set of > : options the driver supports plus a subset of the options for a device > : provided by the bus. This can be determined by examining the driver > : and bus data at probe/attach time; something that's easy with KLD/ > : newbus/loader, but would require a bolt-on for newconfig. > > A sysctl-like mechanism would likely be a good idea. Let me explain > what I have in mind. More to the point, this is configuration information, so it lives in parameter space. > First, let us say that there are configuration files. Let us say > these files use the sysctl syntax. Let us further suppose that we > extend the sysctl notation to include wild cards. We'd have something > similar to the xdefaults (xrdb actually) syntax. This sparse database > would be kept around. > > When modules are initialized (either as being part of the base system, > statically linked in, or when dynamically loaded by some means), the > sysctl's variables are set (if they match this sparse database). > > Now, this would allow drivers and other modules to be dynamically > configured in a user friendly manner. The "sparse database" would > allow for the user to specify things (eg the band for a radio modem, > the video signalling to use (ntsc vs pal), etc). Yup; this all matches more or less what I was thinking so far... > Some examples: > > driver.aha*tune_bus: 1 > driver.bt848*video_format: ntsc > > When the aha driver starts, it registers the sysctl variable > > driver.aha.unit0.tune_bus > > and then finds its value. Since it matchces the above sepecification, > it will have a value of 1 when the driver checks its value. I think you've tangled a couple of different ways of getting at the data there, but I think that's fairly close. You've only used two uniquifiers, the driver name and instance number, but I'm wondering whether we might not want to support a more general mechanism where you can specify other uniquifiers for the match. eg. driver=sio, bus_attribute=removable: powerup_on_open=yes This may also be an instance of feeping creaturism... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 04:34:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23033 for freebsd-current-outgoing; Tue, 15 Dec 1998 04:34:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23028 for ; Tue, 15 Dec 1998 04:34:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id EAA05213; Tue, 15 Dec 1998 04:31:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812151231.EAA05213@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa cc: Mike Smith , Garrett Wollman , Nate Williams , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Tue, 15 Dec 1998 17:22:35 +0900." <199812150822.RAA02605@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 04:31:37 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > - We aren't CopycatBSD; the "new bus" group is attempting to develop > > a new, better approach to handling the bus/bridge/device > > relationships. "newconfig" is better than what we have right now, > > but it is not good enough. > > Why do you make another framework ? Why not improve 4.4BSD bus and > config code ? Because it is based on some fundamentally flawed principles, and what is required is a revolutionary rather than evolutionary change. > FreeBSD, it is 4.4BSD based OS. If you want to make new > framework, why FreeBSD ? You could apply the same argument against changing the VM subsystem, or migrating to CAM, or for that matter porting from the VAX to anything else. FreeBSD isn't about preserving the 4.4BSD heritage, it's about the ongoing development of a world-class operating system taking advantage of the foundation that we currently have. As the saying goes, evolve or die. > I think FreeBSD is one of 4.4BSD-children, and I want to use BSD > like OS, not Linux. You're quite welcome to pick an OS that will always feel like a BSD - we can't however continue to feel exactly like a BSD if we want to adapt to the changing circumstances and our growing market. > I want to integrate other BSDs, if possible. > (I know, it is too hard really.) It's impossible; if nothing else, they won't let you. > > - Bus architecture "incompatibility" is not actually a significant > > issue. We are already 100% bus architecture incompatible with the > > other BSDs, change simply for compatibility's sake won't give us any > > benefits, and it would stifle any attempt to do better. Right now > > the few drivers that are shared amongst the BSD's all have different > > bus interface code anyway; there is nothing that will get "worse" if > > we change the mechanics of the interface. There are also things > > that we are trying to do that can't be done with newconfig (at > > least, as it is right now - for sure it too can be modified). > > At least, I want to reduce driver porting cost. In "newconfig", > its cost from other BSDs is quite low. It's a fatal mistake to assume that the configuration iterface represents anything other than a tiny portion of the work in driver porting. In many cases, it's better to reimplement the driver from scratch rather than try to 'port' it from another BSD - see for example the 'de' driver for a good argument for this. Changing just our bus code for the sake of slavish compatibility wouldn't actually win us much, and if you take the same argument further we should basically sit down and copy everything that the NetBSD folks do without innovating ourselves at all. That's fairly clearly not going to work, and any partial steps in that direction that don't have anything else to offer would be a bad idea. > > - Static configuration is evil. More specifically, static > > configuration is a special case of dynamic configuration. > > "newconfig" does static configuration very well, but the "newconfig" > > architecture is not at all suitable for dynamic configuration. > > Some case, static configuration is very useful. For example, 1 > floppy router like PicoBSD, and etc .... As Terry pointed out, you are mistaking aggregation for static configuration. config(8) does two things; it builds static tables of configuration data, and it arranges for code aggregation into a kernel object. There is no dispute that it is desirable to be able to manufacture an aggregate kernel object; it is trivial to do this with KLD modules already. There are also good arguments for supporting static tables of configuration information; in some cases there is no other way of obtaining the information a driver needs to operate. However it is *not* a good idea to bind this information into the kernel object, as it makes *changing* the information very difficult. > And "newconfig" is not static configuration only, also dynamic > configuration can use. It would be more accurate to say that you can do dynamic configuration despite newconfig, but you can do that with old config as well. Newconfig does not offer any facilities to make dynamic configuration easier. > We are planning add UserConfig to > "newconfig", it is *true* dynamic configuration. Userconfig is the best solution for a statically-configured kernel. It's not a good solution for a dynamic kernel. > On "new-bus", How to handle boot device like console, fd, wd, ... ? I can't make sense of this question; could you expand a little? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 05:06:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25772 for freebsd-current-outgoing; Tue, 15 Dec 1998 05:06:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shidahara1.planet.kobe-u.ac.jp (shidahara1.planet.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25767 for ; Tue, 15 Dec 1998 05:06:52 -0800 (PST) (envelope-from takawata@shidahara1.planet.kobe-u.ac.jp) Received: from shidahara1.planet.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id VAA20860 for ; Tue, 15 Dec 1998 21:58:04 +0900 (JST) Message-Id: <199812151258.VAA20860@shidahara1.planet.kobe-u.ac.jp> To: current@FreeBSD.ORG Subject: How to use smb(4) interface? Date: Tue, 15 Dec 1998 21:58:03 +0900 From: Takanori Watanabe Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I wrote SMBus controller driver for Intel PIIX4 Power Management Controller, and I don't know how to test the driver. I think smb(4) is generic "upstream" driver for SMBus, but I don't know how to recognize and how to use it.Opening /dev/smb0 (device node made) only results EINVAL. Currently I test code in PCI probe routine by issuing recieve method from smbus address 0xa0-0xa6(assigned for DIMM EEPROM ) and 0x58-0x5e(assigned for Hectra * hardware sensor) . In my side, 0xa0,0xa2,0xa4 Succeed and others Failed, this matches the machine configuration. (It holds 768MB DRAM(256M DIMMx3) and no hardware sensor.) any Ideas? My code is at http://www.planet.kobe-u.ac.jp/~takawata/intiic.c http://www.planet.kobe-u.ac.jp/~takawata/intiicreg.h and to use it, you will need changes in smbus.c conf/files.???? configuration file. and so on. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 05:39:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28816 for freebsd-current-outgoing; Tue, 15 Dec 1998 05:39:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (pm36-5.image.dk [194.234.182.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28805 for ; Tue, 15 Dec 1998 05:39:25 -0800 (PST) (envelope-from root@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id OAA15700 for ; Tue, 15 Dec 1998 14:39:09 +0100 (CET) (envelope-from root@swimsuit.internet.dk) Date: Tue, 15 Dec 1998 14:39:09 +0100 (CET) From: Leif Neland To: freebsd-current@FreeBSD.ORG Subject: CVSROOT in making a release 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 If I want to make a "release" of the current version of my system, for installing on another computer, how do I do it? More specifically, what is CVSROOT supposed to be if I have cvsupped current? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 07:14:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07994 for freebsd-current-outgoing; Tue, 15 Dec 1998 07:14:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhost.mil.ameritech.net (mpdr0.milwaukee.wi.ameritech.net [206.141.239.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07965 for ; Tue, 15 Dec 1998 07:13:59 -0800 (PST) (envelope-from randyd@ameritech.net) Received: from ameritech.net ([209.18.22.49]) by mailhost.mil.ameritech.net (InterMail v03.02.07 118 124) with ESMTP id <19981215150651.ZOM2410@ameritech.net>; Tue, 15 Dec 1998 09:06:51 -0600 Message-ID: <3674AF65.7B6BCFAB@ameritech.net> Date: Mon, 14 Dec 1998 00:25:41 -0600 From: "Randall D. DuCharme" Organization: Astrolab Developement X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.7 i86pc) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon CC: freebsd-current@FreeBSD.ORG Subject: Re: Totally illegal declaration/check in i386/i386/busdma_machdep.c References: <199812140529.VAA26641@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > GCC warning expected? I'm sorry, but this is *illegal*. Totally > illegal. nextpaddr can be legally destroyed on each loop by the > compiler. I know what the author was trying to do, but he's wrong. > > I'm fixing this. > > (from i386/i386/busdma_machdep.c) > > do { > bus_size_t size; > vm_offset_t nextpaddr; /* GCC warning expected */ > > paddr = pmap_kextract(vaddr); > size = PAGE_SIZE - (paddr & PAGE_MASK); > if (size > buflen) > size = buflen; > > ... > > } else if (paddr == nextpaddr) { > sg->ds_len += size; > ... > nextpaddr = paddr + size; > buflen -= size; > } while (buflen > 0); > > Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet > Communications & God knows what else. > (Please include original email in any response) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Randall D DuCharme Systems Engineer Novell, Microsoft, and UNIX Networking Support Computer Specialists Free Your Machine.... FreeBSD 414-253-9998 414-253-9919 (fax) The Power To Serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 07:49:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10567 for freebsd-current-outgoing; Tue, 15 Dec 1998 07:49:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10526 for ; Tue, 15 Dec 1998 07:48:43 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id JAA71968; Tue, 15 Dec 1998 09:48:22 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <367684C6.4DA197C5@webwizard.org.mx> Date: Tue, 15 Dec 1998 09:48:22 -0600 From: Edwin Culp X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" , jabc@webwizard.org.mx Subject: IBM Netfinity 3500 - Chapter 2. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I finally have the IBM Netfinity 3500 that I wrote about two weeks ago, working well, although not the way I would have wanted. The first thing I had to do was to disable the APM completely and the USB (just in case). I could not use the onboard 100/10 EtherExpress and had to physically change the jumper on the board to disable it. I wasn't able to use an EtherExpress Pro 100+ card at all. It would probe perfectly but when it came to ifconfig the machine would freeze, no panic, just death and silence. I was able to get one ne2000 card to work reasonably well but when I installed the second, it would work sometimes and then start with "device time out". I finally gave up on them. As a last resort, I tried two 3com595 100/10 cards that I had left over when I changed to the EtherExpress 100 and much to my surprise, they work perfectly. I have no idea why they work nor why the EtherExpress doesn't nor why I wasn't able to get two ne2000 clones to work together. (Tried everything, except the right thing:-) like disabling the on board sound card, serial ports, etc. etc. I'm not planing on doing anything else to the machine, "if it ain't broke, don't fix it", but I would be interested in other peoples experiences with the IBM Netfinity 3500. Mike Smith told me in a previous mail that the problem with the onboard EtherExpress was a known problem. If anyone has better solutions and I'm sure someone must have :-), please let me know what you did. Thanks ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 08:37:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16155 for freebsd-current-outgoing; Tue, 15 Dec 1998 08:37:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16150 for ; Tue, 15 Dec 1998 08:37:14 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id FAA26924; Wed, 16 Dec 1998 05:37:06 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id FAA27118; Wed, 16 Dec 1998 05:37:01 +1300 (NZDT) Message-ID: <19981216053701.B27078@clear.co.nz> Date: Wed, 16 Dec 1998 05:37:01 +1300 From: Joe Abley To: Matthew Dillon , Mark Murray Cc: Kevin Day , freebsd-current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: modification to exec in the kernel? References: <19981215120357.B11837@clear.co.nz> <199812142331.RAA17203@home.dragondata.com> <19981215124818.A22526@clear.co.nz> <199812150644.IAA67338@greenpeace.grondar.za> <199812150917.BAA52694@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812150917.BAA52694@apollo.backplane.com>; from Matthew Dillon on Tue, Dec 15, 1998 at 01:17:45AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 15, 1998 at 01:17:45AM -0800, Matthew Dillon wrote: > > :Joe Abley wrote: > :> I looked at that; however, remember the users will have chrooted access > :> to their directories, and within the chrooted tree will be /usr and > :> descendants containing controlled binaries (owned by someone else, e.g. > :> "root") like perl, awk, sh, etc. > : > :Your security model is flawed. A user can do anything she wants > :(justabout) with shellscript and perl. Picking on compiled binaries > :is not going to make you that much safer. > : > :M > > I think a chroot'd environment can be even *more* dangerous then a > non-chroot'd environment because critical system configuration files > will be missing and potentially creatable by the user - if the > chroot'd environment is based in a user-owned directory and you've > installed any suid or sgid system binaries, you have an extremely > serious security hole on your hands. It wasn't our intention to have _any_ setuid/setgid binaries available in the chrooted environment - and the /, /usr, /var, /etc directories would not be user-owned, but rather hardlinks to private copies of the appropriate directories owned by some non-user uid. So how is this more dangerous than a non-chrooted environment? Surely it is _as_ safe - but with the added control that the user sees an appropriate subset of the entire filesystem that is controlled, regardless of what the system as a whole needs to have installed in order to function? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 08:45:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17247 for freebsd-current-outgoing; Tue, 15 Dec 1998 08:45:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17242 for ; Tue, 15 Dec 1998 08:45:06 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id FAA27117; Wed, 16 Dec 1998 05:40:36 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id FAA27138; Wed, 16 Dec 1998 05:40:35 +1300 (NZDT) Message-ID: <19981216054035.C27078@clear.co.nz> Date: Wed, 16 Dec 1998 05:40:35 +1300 From: Joe Abley To: Mark Murray Cc: Kevin Day , freebsd-current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: modification to exec in the kernel? References: <19981215120357.B11837@clear.co.nz> <199812142331.RAA17203@home.dragondata.com> <19981215124818.A22526@clear.co.nz> <199812150644.IAA67338@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812150644.IAA67338@greenpeace.grondar.za>; from Mark Murray on Tue, Dec 15, 1998 at 08:44:16AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 15, 1998 at 08:44:16AM +0200, Mark Murray wrote: > Joe Abley wrote: > > I looked at that; however, remember the users will have chrooted access > > to their directories, and within the chrooted tree will be /usr and > > descendants containing controlled binaries (owned by someone else, e.g. > > "root") like perl, awk, sh, etc. > > Your security model is flawed. A user can do anything she wants > (justabout) with shellscript and perl. Picking on compiled binaries > is not going to make you that much safer. "Just about" - so there are _some_ exploits that would require a user-supplied binary? So preventing execution of user-supplied binaries does give _some_ safety benefit? I take your point, though - I was forgetting how much feature bloat there is in perl. Why people can't just make do with awk is a little beyond me :) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 08:51:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18226 for freebsd-current-outgoing; Tue, 15 Dec 1998 08:51:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18214 for ; Tue, 15 Dec 1998 08:51:02 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:GES4EJkEct1hOjS+ynQsqTaA8dBoyGzk@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id SAA02753; Tue, 15 Dec 1998 18:50:53 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:w6Drr6HBhysDqC794attde3rBE7aifp+@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id SAA68842; Tue, 15 Dec 1998 18:50:52 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812151650.SAA68842@greenpeace.grondar.za> To: Joe Abley cc: Matthew Dillon , Kevin Day , freebsd-current@FreeBSD.ORG Subject: Re: modification to exec in the kernel? In-Reply-To: Your message of " Wed, 16 Dec 1998 05:37:01 +1300." <19981216053701.B27078@clear.co.nz> References: <19981215120357.B11837@clear.co.nz> <199812142331.RAA17203@home.dragondata.com> <19981215124818.A22526@clear.co.nz> <199812150644.IAA67338@greenpeace.grondar.za> <199812150917.BAA52694@apollo.backplane.com> <19981216053701.B27078@clear.co.nz> Date: Tue, 15 Dec 1998 18:50:51 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Abley wrote: > So how is this more dangerous than a non-chrooted environment? Surely it > is _as_ safe - but with the added control that the user sees an appropriate > subset of the entire filesystem that is controlled, regardless of what the > system as a whole needs to have installed in order to function? You give the user Perl5, you may as well give them a C compiler. They'll have full access to sockets etc. Who knows what nasty attacks they can launch against you from inside your own network. By assuming it is safe, you are mainly deluding yourself. Given that the chroot'ed environment is "sanitised", it becomes easy to control (within its limits) and understand. I am not proposing security-by-obsurity here, just that you either make it "UNIX" and go with that warts-and-all (security patrols necessary), or make it tighter than a mouse's arse (and non-useful to scriptwriters). We (an ISP) have constructed a non-chroot, noexec, no C-compiler, no-questions-asked box, and we still recognise the need to patrol. It works well, as long as the human intervention is recognised. Oh - while you are building this box - make sure that suidperl is not on board. :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 08:58:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19739 for freebsd-current-outgoing; Tue, 15 Dec 1998 08:58:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19731 for ; Tue, 15 Dec 1998 08:58:40 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:tETawZTphrcpzoHKWALfy5ccmFlRY8WR@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id SAA02767; Tue, 15 Dec 1998 18:58:32 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:UrJnBkCAZeTZelhDG90rrhIUgRdgtzxN@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id SAA68881; Tue, 15 Dec 1998 18:58:31 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812151658.SAA68881@greenpeace.grondar.za> To: Joe Abley cc: Kevin Day , freebsd-current@FreeBSD.ORG Subject: Re: modification to exec in the kernel? In-Reply-To: Your message of " Wed, 16 Dec 1998 05:40:35 +1300." <19981216054035.C27078@clear.co.nz> References: <19981215120357.B11837@clear.co.nz> <199812142331.RAA17203@home.dragondata.com> <19981215124818.A22526@clear.co.nz> <199812150644.IAA67338@greenpeace.grondar.za> <19981216054035.C27078@clear.co.nz> Date: Tue, 15 Dec 1998 18:58:30 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Abley wrote: > On Tue, Dec 15, 1998 at 08:44:16AM +0200, Mark Murray wrote: > "Just about" - so there are _some_ exploits that would require a user-supplied > binary? So preventing execution of user-supplied binaries does give _some_ > safety benefit? 0.001%. If you can do it in C, you can do it in perl. Buffer exploits are much easier in C and assembler, though. A cracker with time is a dangerous beast, remember. > I take your point, though - I was forgetting how much feature bloat there > is in perl. > > Why people can't just make do with awk is a little beyond me :) Shellscript+awk+sed is a potent combination in the hands of an uberhacker. Consider the case of the virus-written-in-shellscript; when last and how often do you run tripwire? Are you _convinced_ that you have _never_ (both absolutes) run a user-written substitute (possibly trojaned) replacement for a system applet? I've hit a perl replacement for ls(1) that only gloated. Yes, I was root. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 09:13:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22187 for freebsd-current-outgoing; Tue, 15 Dec 1998 09:13:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22182 for ; Tue, 15 Dec 1998 09:13:36 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id MAA00808; Tue, 15 Dec 1998 12:17:35 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 15 Dec 1998 12:17:35 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Mark Murray cc: Joe Abley , Kevin Day , freebsd-current@FreeBSD.ORG Subject: Re: modification to exec in the kernel? In-Reply-To: <199812151658.SAA68881@greenpeace.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Dec 1998, Mark Murray wrote: > Joe Abley wrote: > > On Tue, Dec 15, 1998 at 08:44:16AM +0200, Mark Murray wrote: > > "Just about" - so there are _some_ exploits that would require a user-supplied > > binary? So preventing execution of user-supplied binaries does give _some_ > > safety benefit? > > 0.001%. If you can do it in C, you can do it in perl. Buffer exploits > are much easier in C and assembler, though. A cracker with time is > a dangerous beast, remember. > > > I take your point, though - I was forgetting how much feature bloat there > > is in perl. > > > > Why people can't just make do with awk is a little beyond me :) > > Shellscript+awk+sed is a potent combination in the hands of an > uberhacker. > > Consider the case of the virus-written-in-shellscript; when last > and how often do you run tripwire? Are you _convinced_ that you > have _never_ (both absolutes) run a user-written substitute (possibly > trojaned) replacement for a system applet? > > I've hit a perl replacement for ls(1) that only gloated. Yes, I > was root. > I think the point here is so that the next "biggie" out on rootshell doesn't give every amatuer script kiddie root on your boxen. Any 'uberhacker' on the otherhand might find an overflow in any util to get it to run his arbitrary code. (i've seen vi segfault) It's not 1980, lock the doors and hope no one with a fireaxe comes knocking. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 09:15:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22624 for freebsd-current-outgoing; Tue, 15 Dec 1998 09:15:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22619 for ; Tue, 15 Dec 1998 09:15:17 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id JAA08496 for current@FreeBSD.ORG; Tue, 15 Dec 1998 09:14:04 -0800 (PST) (envelope-from dhw) Date: Tue, 15 Dec 1998 09:14:04 -0800 (PST) From: David Wolfskill Message-Id: <199812151714.JAA08496@pau-amma.whistle.com> Subject: Re: HEADS UP : laptop power-down change Cc: current@FreeBSD.ORG In-Reply-To: <199812150734.AAA12910@usr06.primenet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Terry Lambert >Date: Tue, 15 Dec 1998 07:34:08 +0000 (GMT) >Apparently NeXTStep uses "-p". Time for a survey. 8-(. "Conformance with other implementations" isn't an attribute I've come to associate with NeXTSTEP. I wouldn't weight that particular datum especially heavily. But then, that's just me, david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 09:33:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24575 for freebsd-current-outgoing; Tue, 15 Dec 1998 09:33:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24569 for ; Tue, 15 Dec 1998 09:33:26 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA05230; Tue, 15 Dec 1998 09:33:20 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id JAA16433; Tue, 15 Dec 1998 09:33:20 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 15 Dec 1998 09:33:20 -0800 (PST) Message-Id: <199812151733.JAA16433@vashon.polstra.com> To: root@swimsuit.internet.dk Subject: Re: CVSROOT in making a release Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Leif Neland wrote: > If I want to make a "release" of the current version of my system, for > installing on another computer, how do I do it? > > More specifically, what is CVSROOT supposed to be if I have cvsupped > current? To make a release, you must have the whole CVS repository -- not just the checked-out current. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 09:36:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25236 for freebsd-current-outgoing; Tue, 15 Dec 1998 09:36:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25216 for ; Tue, 15 Dec 1998 09:36:38 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id SAA08107; Tue, 15 Dec 1998 18:35:30 +0100 (CET) Received: from wurzelausix (quadratix.cs.uni-sb.de [134.96.222.2]) by cs.uni-sb.de (8.9.1a/1998121400) with ESMTP id SAA19383; Tue, 15 Dec 1998 18:35:25 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:4dQ6ubLO4cilELSgl9C79kLvjcGxt0cH@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id SAA22946; Tue, 15 Dec 1998 18:35:17 +0100 (CET) Message-Id: <199812151735.SAA22946@wurzelausix> Date: Tue, 15 Dec 1998 18:35:14 +0100 (CET) From: Alexander Leidinger Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? To: dillon@apollo.backplane.com cc: current@FreeBSD.ORG In-Reply-To: <199812150925.KAA02243@wurzelausix> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Dec, To: dillon@apollo.backplane.com wrote: > Expect the result (Yes, it works/no it did not) in some hours. Ok, works here (testet with nfs ro and local rw, no freebsd.cf in src/etc/sendmail). Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 09:42:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25970 for freebsd-current-outgoing; Tue, 15 Dec 1998 09:42:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mamut.isi.wat.waw.pl (mamut.isi.wat.waw.pl [193.59.144.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA25952 for ; Tue, 15 Dec 1998 09:42:10 -0800 (PST) (envelope-from dwojtas@mamut.isi.wat.waw.pl) Received: (qmail 18020 invoked by uid 1030); 15 Dec 1998 17:44:36 -0000 Date: Tue, 15 Dec 1998 18:44:36 +0100 (EET) From: Darek Wojtas To: freebsd-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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 09:50:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26933 for freebsd-current-outgoing; Tue, 15 Dec 1998 09:50:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.elpost.com (DNS2.ELPOST.COM [193.15.1.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26912; Tue, 15 Dec 1998 09:50:25 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t4o29p18.telia.com [194.236.215.138]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id SAA01235; Tue, 15 Dec 1998 18:50:14 +0100 Received: from localhost (johan@localhost) by phoenix.granlund.nu (8.9.1/8.9.1) with ESMTP id SAA11956; Tue, 15 Dec 1998 18:49:13 +0100 (CET) (envelope-from johan@granlund.nu) Date: Tue, 15 Dec 1998 18:49:13 +0100 (CET) From: Johan Granlund To: Poul-Henning Kamp cc: "Jonathan M. Bresler" , julian@whistle.com, lars@akerlings.t.se, current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! In-Reply-To: <6841.913677780@critter.freebsd.dk> 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, 15 Dec 1998, Poul-Henning Kamp wrote: > In message <199812142307.PAA27390@hub.freebsd.org>, "Jonathan M. Bresler" write > s: > >> Date: Mon, 14 Dec 1998 22:12:29 +0100 (CET) > >> From: Johan Granlund > >> > >> This is really interesting! > >> One of the concepts i liked in SYSV (ducking for cover) was streams and > >> its ability to chain together modules to process a datastream. > >> If it's coupled with kld to dynamically load/unload modules i think > >> you have something _very_ good. > >> > >> That network thing. Can a module route a package thru different modules > >> based on contents and state? > > > > the idea of streams is wonderful, the realization is costly. each > > layer added (or module pushed) slows down processing and hurts > > throughput. ritchie developed streams for serial, if i remember > > correctly. streams was then applied to networks. there is an RFC > > about layering being bad for networking and the relative performance > > of NIT vs BPF prove the case. > > But with that said, there is still something to be said for modular > and well defined interfaces. But streams ? No. They were great > for async protocols, but they fail badly for packet stuff. Lets get something clear. I was not talking about migrating our networking to SYSV style streams. If someone was talking about converting our networking code to streams i would probably scream. Multiple layers cause more latency, nothing new there at all! What i was thinking about was something more like lowbandwidth / high processing protocols. If the endpoint is a serial port, network interface or the network protocol stack (for tunneling) should't be a issue if it's used right. PPP seems as a contender there and it would get streams used. If it's not used then it's rotts. /Johan > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 10:15:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00753 for freebsd-current-outgoing; Tue, 15 Dec 1998 10:15:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00515; Tue, 15 Dec 1998 10:15:15 -0800 (PST) (envelope-from jmb) Date: Tue, 15 Dec 1998 10:15:15 -0800 (PST) Message-Id: <199812151815.KAA00515@hub.freebsd.org> From: "Jonathan M. Bresler" To: johan@granlund.nu CC: phk@critter.freebsd.dk, julian@whistle.com, lars@akerlings.t.se, current@FreeBSD.ORG, isdn@FreeBSD.ORG In-reply-to: (message from Johan Granlund on Tue, 15 Dec 1998 18:49:13 +0100 (CET)) Subject: Re: if_sppp is BROKEN!!! References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Tue, 15 Dec 1998 18:49:13 +0100 (CET) > From: Johan Granlund > > Lets get something clear. I was not talking about migrating our networking > to SYSV style streams. [snip] > If the endpoint is a serial port, network interface > or the network protocol stack (for tunneling) should't be a issue if > it's used right. [snip] i agree.....with your first statement. how that mess^Hhes with the second statement, i dont know. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 10:26:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02121 for freebsd-current-outgoing; Tue, 15 Dec 1998 10:21:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02115 for ; Tue, 15 Dec 1998 10:21:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id KAA56685; Tue, 15 Dec 1998 10:21:04 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Dec 1998 10:21:04 -0800 (PST) From: Matthew Dillon Message-Id: <199812151821.KAA56685@apollo.backplane.com> To: Joe Abley Cc: Mark Murray , Kevin Day , freebsd-current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: modification to exec in the kernel? References: <19981215120357.B11837@clear.co.nz> <199812142331.RAA17203@home.dragondata.com> <19981215124818.A22526@clear.co.nz> <199812150644.IAA67338@greenpeace.grondar.za> <199812150917.BAA52694@apollo.backplane.com> <19981216053701.B27078@clear.co.nz> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> I think a chroot'd environment can be even *more* dangerous then a :> non-chroot'd environment because critical system configuration files :> will be missing and potentially creatable by the user - if the :> chroot'd environment is based in a user-owned directory and you've :> installed any suid or sgid system binaries, you have an extremely :> serious security hole on your hands. : :It wasn't our intention to have _any_ setuid/setgid binaries available in :the chrooted environment - and the /, /usr, /var, /etc directories would not :be user-owned, but rather hardlinks to private copies of the appropriate :directories owned by some non-user uid. : :So how is this more dangerous than a non-chrooted environment? Surely it :is _as_ safe - but with the added control that the user sees an appropriate :subset of the entire filesystem that is controlled, regardless of what the :system as a whole needs to have installed in order to function? : : :Joe I don't see the point. Let me put it this way: If you give the user a non-chrooted environment but do not give the user access to any suid/sgid programs, how is this different from giving the user a chroot'd environment without access to any suid/sgid programs? The only difference that I can think of is access to /tmp. I don't see how the chroot'd environment is any safer then the non-chroot'd environment. In the chroot'd environment the user still has access to the network, all system calls, and can still create and run binaries. Going through my memory and considering the known root exploits found in the last year, this user would still be able to run most of them. Once the user breaks root, the user can trivially break out of the chroot. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 10:28:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03344 for freebsd-current-outgoing; Tue, 15 Dec 1998 10:28:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03338 for ; Tue, 15 Dec 1998 10:28:46 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id KAA08964 for current@FreeBSD.ORG; Tue, 15 Dec 1998 10:27:32 -0800 (PST) (envelope-from dhw) Date: Tue, 15 Dec 1998 10:27:32 -0800 (PST) From: David Wolfskill Message-Id: <199812151827.KAA08964@pau-amma.whistle.com> To: current@FreeBSD.ORG Subject: Re: HEADS UP : laptop power-down change In-Reply-To: <199812150347.BAA09880@roma.coe.ufrj.br> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Joao Carlos Mendes Luis >Date: Tue, 15 Dec 1998 01:47:19 -0200 (EDT) >Yes... What about Solaris' poweroff ? Lets let everybody happy. >It could be a hard link to halt, of course. Oh, maybe shutdown(8) >should be modified to pass some flags to halt(8), or at least to >support poweroff mode. Actually, in Solaris 2.5: axe% ls -li `which poweroff halt` 54730 -rwxr-xr-x 1 bin bin 6652 Oct 25 1995 /usr/sbin/halt 54673 lrwxrwxrwx 1 root root 6 May 1 1996 /usr/sbin/poweroff -> ./halt david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 11:48:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15493 for freebsd-current-outgoing; Tue, 15 Dec 1998 11:48:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15488 for ; Tue, 15 Dec 1998 11:48:35 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA11894; Tue, 15 Dec 1998 19:44:54 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id KAA01588; Tue, 15 Dec 1998 10:45:30 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812151045.KAA01588@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Hall cc: freebsd-current@FreeBSD.ORG Subject: Re: ppp tunnelling In-reply-to: Your message of "Mon, 14 Dec 1998 17:42:48 +0800." <199812140942.RAA04244@hsw.generalresources.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 10:45:30 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's what you get for being so -current ;-P This is a latency problem - one that's been made just a bit worse by yesterdays timer changes.... But the good news is that I've found the problem. The fix should be committed by the time you read this mail. Thanks for the report. > On a fairly recent make world (cvsu30220p about 12 hours ago) I rebuilt the > kernel with two tunnel devices to try to use the ppp.conf "loopback". > (from ppp.conf.sample file version 1.33) > > I tried the following: > > When I run the client ppp, the server ppp seems to hang, and kill is > needed to stop the server. > > Telnet to server ppp also hangs, there is no output from the server. > > Running ppp -direct loop-in prints 5 blocks of binary data. > > Replacing the server with a simple C program to output a couple of > lines of text and running the client interactive mode; the text shows > up when the "term" command is used. > > > > Here is the run: > > [hsw:/etc/ppp]# ppp -background loop > Working in background mode > Using interface: tun0 > Child failed (errdead). > [hsw:/etc/ppp]# > > > >From ps -ax: > > 698 ?? Is 0:00.04 ppp -direct loop-in > > > It looks to me like the server ppp is not doing any I/O once it has been > started by inetd. > > Just added the Async log flag and I can see the data is only received > by the server ppp _after_ it receives the signal 15 from the kill. > Might this suggest that it has not set the socket to non-blocking? > > > --- > Christopher Hall -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 12:12:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18826 for freebsd-current-outgoing; Tue, 15 Dec 1998 12:12:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18813 for ; Tue, 15 Dec 1998 12:12:11 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id PAA61334 for ; Tue, 15 Dec 1998 15:11:20 -0500 (EST) Message-Id: <4.1.19981215150929.0098bec0@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 15 Dec 1998 15:10:28 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Default mail.local behavior Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When was the default behavior for mail.local changed to include an attempt to "biff" unless -b is specified? Shouldn't this be the other way around? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 12:41:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22092 for freebsd-current-outgoing; Tue, 15 Dec 1998 12:41:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lonegunman.xfiles.org.uk (lonegunman.xfiles.org.uk [194.200.230.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22076 for ; Tue, 15 Dec 1998 12:41:42 -0800 (PST) (envelope-from benhutch@lonegunman.xfiles.org.uk) Received: (from benhutch@localhost) by lonegunman.xfiles.org.uk (8.9.1/8.9.1) id UAA04701; Tue, 15 Dec 1998 20:41:15 GMT (envelope-from benhutch) Message-ID: <19981215204115.A4613@xfiles.org.uk> Date: Tue, 15 Dec 1998 20:41:15 +0000 From: Ben Hutchinson To: Mike Smith Cc: FreeBSD Current Subject: Re: HEADS UP : laptop power-down change References: <199812132235.PAA10207@usr09.primenet.com> <199812150250.SAA02049@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812150250.SAA02049@dingo.cdrom.com>; from Mike Smith on Mon, Dec 14, 1998 at 06:49:59PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IRIX. - Ben On Mon, Dec 14, 1998 at 06:49:59PM -0800, Mike Smith wrote: > That's a good point; now is probably the time to change it to be > consistent. Any conflicting examples? -- "Trust No One" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 13:02:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24528 for freebsd-current-outgoing; Tue, 15 Dec 1998 13:02:49 -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 NAA24508; Tue, 15 Dec 1998 13:02:45 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA17085; Tue, 15 Dec 1998 12:56:37 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma017081; Tue, 15 Dec 98 12:56:21 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA00665; Tue, 15 Dec 1998 12:56:21 -0800 (PST) From: Archie Cobbs Message-Id: <199812152056.MAA00665@bubba.whistle.com> Subject: Re: if_sppp is BROKEN!!! In-Reply-To: from Johan Granlund at "Dec 15, 98 06:49:13 pm" To: johan@granlund.nu (Johan Granlund) Date: Tue, 15 Dec 1998 12:56:21 -0800 (PST) Cc: phk@critter.freebsd.dk, jmb@FreeBSD.ORG, julian@whistle.com, lars@akerlings.t.se, current@FreeBSD.ORG, isdn@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Johan Granlund writes: > What i was thinking about was something more like lowbandwidth / high > processing protocols. If the endpoint is a serial port, network interface > or the network protocol stack (for tunneling) should't be a issue if > it's used right. Here's some examples of what we use the netgraph stuff for on the InterJet. As quick background, netgraph nodes are in the kernel and represent the atomic units of the netgraph system. Each node has 'hooks' which can be connected to other netgraph nodes via their corresponding hooks. If you're into graph theory, node == node and joined pair of hooks == edge. Data travels in mbufs from node to node via their connected hooks. There is also a synchronous command/response message capability, for configuration, misc other stuff, etc.. Nodes normally run at splnet(), but can run at different spl's if need be; we have routines to handle the required queueing. Examples of nodes we've actually written and use in production (some of these are proprietary and can't be released just yet): - Socket node This is a netgraph node which is also a socket in the family PF_NETGRAPH. Allows user mode programs to participate in the netgraph system and act just like any other node. We've also written a user level library to make communicating with netgraph sockets easy. - Async node This is a netgraph node which is also a line discipline. It does PPP async <-> sync conversion, by connecting to a serial line and having a hook for sending/receiving synchronous PPP frames (which get converted) to the serial line. - Interface node This is a netgraph node which is also a (point-to-point) interface. It has hooks for each protocol family. Packets are forwarded between the interface and the hooks. - Cisco HDLC node This node takes raw frames on one side and demultiplexes them according to the Cisco HDLC protocol into IP, AppleTalk, etc. Also handles keep-alives. Typically, you'd connect each protocol hook to the corresponding protocol hook of an interface node. - Frame relay node Receives raw frame relay frames, and has hooks for each DLCI. - Frame relay LMI Hook this to DLCI 0 and DLCI 1023 to do auto-detection of frame relay LMI type, and perform the appropriate LMI protocol. - RFC 1490 Protocol demux'ing according to RFC 1490. Used on many frame relay links. - ISDN node Is a device driver and a netgraph node. Performs the D channel signalling and has a hook for each B channel. Accepts synchronous commands for things like dialing, etc. - Synchronous card node We have a synchronous card that is also a node with a single hook for the input/output of raw HDLC frames. - Other nodes.. mostly for debugging... Echo node - echo frames back on the hook whence they came Hole node - consume and discard all frames received Tee node - dupliacate each frame that passes through it and send it out via a different hook This system has really worked out great. If we wanted to do something wacky like run frame relay over the ISDN B channel, it would be trivial to set up. If you've seen the InterJet synchronous port configuration page, you can see how we support all the different ways of configuring that port -- each configuration just represents a different netgraph setup. The more I work with it, the more I realize that a major benefit is that it provides a clean and efficient way for user level programs to communicate directly with low-level kernel drivers and stuff -- and in more interesting ways than a /dev entry allows. It's a step up from the /dev/foo* and ioctl() method of communicating. The simplicity of nodes means you can get the minimal kernel stuff done first and develop the higher layer protocols in user space, where debugging is easier. Then when it's all working, turn it into a kernel netgraph node -- none of it's neighbors will know the difference. Of course the other major benefit is modularity. Instead of having if_ppp.c, if_sppp.c, if_foo1.c, if_foo2.c, where you are reimplementing the interface behavior code over and over again, you just keep this code in a single place: ng_iface.c, the interface node. Then anybody who needs to export an interface can do so by connecting it to an interface node (example: cisco hdlc node). These little guys make great LKM/KLD modules too.. Anyway, one reason I'm hyping this a little bit is because we (Julian and me) want to clean up, and update, and unencumber the netgraph code that was released a year or so ago, and check it in so people can start playing with it more. It will take a little time though, not to mention approval from the kernel gargoyles... -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 13:57:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02077 for freebsd-current-outgoing; Tue, 15 Dec 1998 13:57:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01955; Tue, 15 Dec 1998 13:57:11 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id WAA37509; Tue, 15 Dec 1998 22:56:25 +0100 (CET) To: Archie Cobbs cc: johan@granlund.nu (Johan Granlund), jmb@FreeBSD.ORG, julian@whistle.com, lars@akerlings.t.se, current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! In-reply-to: Your message of "Tue, 15 Dec 1998 12:56:21 PST." <199812152056.MAA00665@bubba.whistle.com> Date: Tue, 15 Dec 1998 22:56:24 +0100 Message-ID: <37507.913758984@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Anyway, one reason I'm hyping this a little bit is because we >(Julian and me) want to clean up, and update, and unencumber the >netgraph code that was released a year or so ago, and check it in >so people can start playing with it more. It will take a little time >though, not to mention approval from the kernel gargoyles... Well, I think this one of those gargoyles speaking, and his position is that it sounds very very interesting, but he would hate to have it committed anywhere until he has had a decent chance to try it out. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 13:58:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02282 for freebsd-current-outgoing; Tue, 15 Dec 1998 13:58:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02254; Tue, 15 Dec 1998 13:58:03 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.1/8.6.9) with ESMTP id WAA10556; Tue, 15 Dec 1998 22:44:48 +0100 (CET) Message-Id: <199812152144.WAA10556@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! Reply-To: Gary Jennejohn In-reply-to: Your message of "Tue, 15 Dec 1998 12:56:21 PST." <199812152056.MAA00665@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 22:44:48 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs writes: >Johan Granlund writes: >> What i was thinking about was something more like lowbandwidth / high >> processing protocols. If the endpoint is a serial port, network interface >> or the network protocol stack (for tunneling) should't be a issue if >> it's used right. > >Here's some examples of what we use the netgraph stuff for on the >InterJet. > [snip] > - ISDN node > > Is a device driver and a netgraph node. Performs the D channel > signalling and has a hook for each B channel. Accepts synchronous > commands for things like dialing, etc. > [snip] does this handle the full I.430, Q.93x stuff too ? In other words, passive ISDN cards ? >Of course the other major benefit is modularity. Instead of having >if_ppp.c, if_sppp.c, if_foo1.c, if_foo2.c, where you are reimplementing >the interface behavior code over and over again, you just keep this >code in a single place: ng_iface.c, the interface node. Then anybody >who needs to export an interface can do so by connecting it to an >interface node (example: cisco hdlc node). > >These little guys make great LKM/KLD modules too.. > >Anyway, one reason I'm hyping this a little bit is because we >(Julian and me) want to clean up, and update, and unencumber the >netgraph code that was released a year or so ago, and check it in >so people can start playing with it more. It will take a little time >though, not to mention approval from the kernel gargoyles... > wow ! This sounds like it would be great for the CAPI stuff I'm trying to implement for isdn4bsd right now. If the card needs CAPI, just hang a CAPI node in the graph. Unfortunately, the effort involved in converting isdn4bsd to use the netgraph mechanism boggles the mind :-( --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 14:15:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04668 for freebsd-current-outgoing; Tue, 15 Dec 1998 14:15:08 -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 OAA04646; Tue, 15 Dec 1998 14:15:06 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id OAA18171; Tue, 15 Dec 1998 14:06:13 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma018163; Tue, 15 Dec 98 14:06:05 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id OAA03477; Tue, 15 Dec 1998 14:06:05 -0800 (PST) From: Archie Cobbs Message-Id: <199812152206.OAA03477@bubba.whistle.com> Subject: Re: if_sppp is BROKEN!!! In-Reply-To: <37507.913758984@critter.freebsd.dk> from Poul-Henning Kamp at "Dec 15, 98 10:56:24 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Tue, 15 Dec 1998 14:06:05 -0800 (PST) Cc: archie@whistle.com, johan@granlund.nu, jmb@FreeBSD.ORG, julian@whistle.com, lars@akerlings.t.se, current@FreeBSD.ORG, isdn@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > >Anyway, one reason I'm hyping this a little bit is because we > >(Julian and me) want to clean up, and update, and unencumber the > >netgraph code that was released a year or so ago, and check it in > >so people can start playing with it more. It will take a little time > >though, not to mention approval from the kernel gargoyles... > > Well, I think this one of those gargoyles speaking, and his position > is that it sounds very very interesting, but he would hate to have > it committed anywhere until he has had a decent chance to try it > out. That's certainly OK.. One nice thing is that no existing kernel source files are modified (except /sys/files/conf). It all lives in /sys/netgraph. So it's easy to play with without a lot of... patchwork. I'll send out a message when we've got something ready for review & testing (probably after Christmas holidays when I can spend some time on it). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 14:37:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07550 for freebsd-current-outgoing; Tue, 15 Dec 1998 14:37:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07545 for ; Tue, 15 Dec 1998 14:37:38 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id RAA57771 for ; Tue, 15 Dec 1998 17:36:56 -0500 (EST) Message-Id: <4.1.19981215173455.009a4b10@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 15 Dec 1998 17:35:52 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: FreeBSD Buildworld fails Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Buildworld is still failing after a make clean, and cvsups today (FreeBSD-3.0-CURRENT): cc -nostdinc -O -pipe -DBOOT_FORTH -I/usr/src/sys/boot/i386/loader/../../ficl -I/usr/src/sys/boot/i386/loader/../../common -I/usr/src/sys/boot/i386/loader/../../.. -I. -Wall -I/usr/src/sys/boot/i386/loader/.. -I/usr/src/sys/boot/i386/loader/../btx/lib -elf -DNEW_LINKER_SET -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/sys/boot/i386/loader/../../common/interp.c /usr/src/sys/boot/i386/loader/../../common/interp.c: In function `perform': /usr/src/sys/boot/i386/loader/../../common/interp.c:48: warning: unused variable `i' /usr/src/sys/boot/i386/loader/../../common/interp.c: In function `interact': /usr/src/sys/boot/i386/loader/../../common/interp.c:85: warning: implicit declaration of function `bf_init' /usr/src/sys/boot/i386/loader/../../common/interp.c:110: warning: implicit declaration of function `bf_run' /usr/src/sys/boot/i386/loader/../../common/interp.c:82: warning: unused variable `argv' /usr/src/sys/boot/i386/loader/../../common/interp.c:81: warning: unused variable `argc' 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 14:41:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07957 for freebsd-current-outgoing; Tue, 15 Dec 1998 14:41:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07952 for ; Tue, 15 Dec 1998 14:41:10 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id QAA06550 for ; Tue, 15 Dec 1998 16:41:05 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812152241.QAA06550@ns.tar.com> From: "Richard Seaman, Jr." To: "current@freebsd.org" Date: Tue, 15 Dec 98 16:41:04 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Linux Threads patches available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The linux threads patches are available at http://lt.tar.com/ These patches include modifications to patches previously posted to this list by Brian Feldman. The goals are twofold: 1) Create a port of Linux Threads that can be compiled and used as a kernel threads implementation under FreeBSD. 2) Allow native Linux applications linked against the Linux Threads pthread library (either static or shared libs) to run under FreeBSD in Linux "emulation" mode. The 5 example programs that come with the linux threads source now appear to run correctly in linux emulation mode, as well as in "native" FreeBSD mode when compiled with the linux threads port. In addition, StarOffice 5.0 for Linux appears to install and run without any apparent problems so far. If people are interested in either of the goals above, you would help greatly by installing and testing these patches. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 14:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08542 for freebsd-current-outgoing; Tue, 15 Dec 1998 14:46:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08535 for ; Tue, 15 Dec 1998 14:46:49 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id RAA57966 for ; Tue, 15 Dec 1998 17:46:08 -0500 (EST) Message-Id: <4.1.19981215174423.009b9c10@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 15 Dec 1998 17:45:04 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: IPFW screwed up? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Something's really wrong with ipfw... this is what my rules end up looking like, and no changes have ever been made: 01010 deny ip from 127.0.0.0/8 to 127.0.0.0/8 00000 deny ip from 255.255.255.255:86.4.0.0 to 255.255.255.0:2.3.0.0 00000 deny ip from any to any 00000 deny ip from any to any 58995 deny igmp from any to 0.0.0.0:0.0.64.0 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any 00000 deny ip from any to any ipopt ssrr,!lsrr,rr,ts,!ts established 00000 deny ip from any to any ipopt ssrr,!ssrr,lsrr,!lsrr,rr,!rr,ts,!ts established 00000 deny ip from any to any ipopt ssrr,!ssrr,!lsrr 06606 ipfw: impossible Nice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 14:53:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09376 for freebsd-current-outgoing; Tue, 15 Dec 1998 14:53:13 -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 OAA09369 for ; Tue, 15 Dec 1998 14:53:11 -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 PAA28761; Tue, 15 Dec 1998 15:53:04 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA19031; Tue, 15 Dec 1998 15:53:03 -0700 Date: Tue, 15 Dec 1998 15:53:03 -0700 Message-Id: <199812152253.PAA19031@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Richard Seaman, Jr." Cc: "current@freebsd.org" Subject: Re: Linux Threads patches available In-Reply-To: <199812152241.QAA06550@ns.tar.com> References: <199812152241.QAA06550@ns.tar.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > These patches include modifications to patches previously posted > to this list by Brian Feldman. > > The goals are twofold: > > 1) Create a port of Linux Threads that can be compiled and > used as a kernel threads implementation under FreeBSD. Is this code GPL, or BSD copyrighted? If the former, then it can't be a 'normal' part of the kernel. It also has alot of implications for the many vendors who use FreeBSD as an embedded system. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 14:58:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09752 for freebsd-current-outgoing; Tue, 15 Dec 1998 14:58:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09747 for ; Tue, 15 Dec 1998 14:58:47 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.8.8) with ESMTP id OAA00612; Tue, 15 Dec 1998 14:58:39 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Date: Tue, 15 Dec 1998 14:58:39 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: IPFW screwed up? In-Reply-To: <4.1.19981215174423.009b9c10@206.25.93.69> 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, 15 Dec 1998, Forrest Aldrich wrote: > Something's really wrong with ipfw... this is what my rules end up looking > like, and no changes have ever been made: Are your kernel and /sbin/ipfw in sync? It appears that some changes have been made to the ipfw userland<->kernel interface. -- Brian Buchanan brian@smarter.than.nu brian@CSUA.Berkeley.EDU "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 15:04:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10382 for freebsd-current-outgoing; Tue, 15 Dec 1998 15:04:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10373 for ; Tue, 15 Dec 1998 15:04:28 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:6vrSY2Qtma9PerLxiHz5q/8Cm3Zc9rdD@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id BAA03466; Wed, 16 Dec 1998 01:04:18 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:7FgJ3AZzIZV1Cge2MFn4TQpf6GcPkiQe@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id BAA01285; Wed, 16 Dec 1998 01:04:03 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812152304.BAA01285@greenpeace.grondar.za> To: Alfred Perlstein cc: Joe Abley , Kevin Day , freebsd-current@FreeBSD.ORG Subject: Re: modification to exec in the kernel? In-Reply-To: Your message of " Tue, 15 Dec 1998 12:17:35 EST." References: Date: Wed, 16 Dec 1998 01:04:02 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > Any 'uberhacker' on the otherhand might find an overflow in any util to > get it to run his arbitrary code. (i've seen vi segfault) > > It's not 1980, lock the doors and hope no one with a fireaxe comes > knocking. Right. Security is 50% procedure, 50% knowledge and the remaining 50% is the luck that puts you in front of the bad guys. :-) There is no "build it and leave it" formula. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 15:09:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10966 for freebsd-current-outgoing; Tue, 15 Dec 1998 15:09:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10961 for ; Tue, 15 Dec 1998 15:09:13 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id RAA20066 for ; Tue, 15 Dec 1998 17:45:09 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA14619; Tue, 15 Dec 1998 17:45:08 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id RAA21523 for freebsd-current@freebsd.org; Tue, 15 Dec 1998 17:45:08 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812152245.RAA21523@bb01f39.unx.sas.com> Subject: Inetd 1.42 now blocking all signals in child by default To: freebsd-current@FreeBSD.ORG Date: Tue, 15 Dec 1998 17:45:08 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Well, the good news is I haven't made inetd fail... The bad news is that by default the SIGCHLD, SIGHUP and, SIGALRM signals are now being blocked when the fork()/exec() calls are made. So... The child process does not receive these signals by default anymore. This is major behavior modification and definitely causes some very interesting side effects... :-) Love them Zombies! We still need to unblock the signals in the child process after the fork... The following should do the trick: --- inetd.c.orig Mon Dec 14 02:07:34 1998 +++ inetd.c Tue Dec 15 17:20:02 1998 @@ -555,6 +555,7 @@ /* sigsetmask(0L); */ if (pid == 0) { if (dofork) { + sigsetmask(0L); if (debug) warnx("+ closing from %d", maxsock); for (tmpint = maxsock; tmpint > 2; tmpint--) Hey! As always comments, critiques, and hints are most welcome... Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 15:11:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11162 for freebsd-current-outgoing; Tue, 15 Dec 1998 15:11:42 -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 PAA11151; Tue, 15 Dec 1998 15:11:38 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA19343; Tue, 15 Dec 1998 15:10:18 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma019339; Tue, 15 Dec 98 15:10:04 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA04618; Tue, 15 Dec 1998 15:10:04 -0800 (PST) From: Archie Cobbs Message-Id: <199812152310.PAA04618@bubba.whistle.com> Subject: Re: if_sppp is BROKEN!!! In-Reply-To: <199812152144.WAA10556@peedub.muc.de> from Gary Jennejohn at "Dec 15, 98 10:44:48 pm" To: garyj@muc.de Date: Tue, 15 Dec 1998 15:10:04 -0800 (PST) Cc: isdn@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary Jennejohn writes: > >Here's some examples of what we use the netgraph stuff for on the > >InterJet. > > > [snip] > > - ISDN node > > > > Is a device driver and a netgraph node. Performs the D channel > > signalling and has a hook for each B channel. Accepts synchronous > > commands for things like dialing, etc. > > > [snip] > > does this handle the full I.430, Q.93x stuff too ? In other words, > passive ISDN cards ? [ trimming recipients to -isdn after this reply ] We have a (very big) node that does this based on a 3rd party ISDN stack. Unfortunately, we can't give away their software without their permission... > wow ! This sounds like it would be great for the CAPI stuff I'm trying > to implement for isdn4bsd right now. If the card needs CAPI, just hang > a CAPI node in the graph. Yep. > Unfortunately, the effort involved in converting isdn4bsd to use the > netgraph mechanism boggles the mind :-( It's probably not that hard. I mean, the netgraph part of it is fairly minimal and can just be a wrapper around existing code. It more depends on how modular the code is to begin with. It would definitely be nice if all the different ISDN drivers could export the same type of netgraph "ISDN BRI" node. Then you could use the user-mode PPP with any of them, for example. The command/response stuff makes it kindof object oriented.. eg, netgraph node | +------- ISDN BRI node | +-------- Foo ISDN card | +-------- Bar ISDN card Each "type" has a certain API for the synchronous command/response messages. Eg, for ISDN they would be things like "dial this number", "configure SPID", etc. There are generic commands at the netgraph level too, like "reset node", etc. In the other direction, the Foo type could extend the set of commands with card-specific stuff. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 15:16:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11681 for freebsd-current-outgoing; Tue, 15 Dec 1998 15:16:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11676 for ; Tue, 15 Dec 1998 15:16:13 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.8.8) with ESMTP id OAA00603 for ; Tue, 15 Dec 1998 14:56:09 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Date: Tue, 15 Dec 1998 14:56:09 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: current@FreeBSD.ORG Subject: Terminal rows weirdness Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think some possibly broken behavior with regard to handling terminal size information may have been introduced within the past month or so. Old (kernel and userland built Nov 12): screen size set to 80x30 in /etc/rc user logs in programs treat terminal as being 80x30 New (kernel and userland built today): screen size set to 80x30 in /etc/rc user logs in programs treat terminal as being 80x25 user executes 'vidcontrol VGA_80x30' programs treat terminal as being 80x30 Do I need to change something to be consistent with the new order of things to get the correct behavior back, or is this some brokenness which has crept in? -- Brian Buchanan brian@smarter.than.nu brian@CSUA.Berkeley.EDU "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 15:28:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12628 for freebsd-current-outgoing; Tue, 15 Dec 1998 15:28:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12604 for ; Tue, 15 Dec 1998 15:28:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id PAA60898; Tue, 15 Dec 1998 15:27:52 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Dec 1998 15:27:52 -0800 (PST) From: Matthew Dillon Message-Id: <199812152327.PAA60898@apollo.backplane.com> To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Inetd 1.42 now blocking all signals in child by default References: <199812152245.RAA21523@bb01f39.unx.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : : Well, the good news is I haven't made inetd fail... The bad news :is that by default the SIGCHLD, SIGHUP and, SIGALRM signals are now :being blocked when the fork()/exec() calls are made. : : So... The child process does not receive these signals by default :anymore. This is major behavior modification and definitely causes :some very interesting side effects... :-) Love them Zombies! : : We still need to unblock the signals in the child process after :the fork... The following should do the trick: : :--- inetd.c.orig Mon Dec 14 02:07:34 1998 :+++ inetd.c Tue Dec 15 17:20:02 1998 :@@ -555,6 +555,7 @@ : /* sigsetmask(0L); */ : if (pid == 0) { : if (dofork) { :+ sigsetmask(0L); : if (debug) : warnx("+ closing from %d", maxsock); : for (tmpint = maxsock; tmpint > 2; tmpint--) : : Hey! As always comments, critiques, and hints are most welcome... : :Thanks! :John Yup. Commited... though I'm unblocking just before the exec call. I think it amounts to the same thing. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 15:32:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12992 for freebsd-current-outgoing; Tue, 15 Dec 1998 15:30:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12974 for ; Tue, 15 Dec 1998 15:30:32 -0800 (PST) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <5257-32728>; Wed, 16 Dec 1998 00:30:02 +0100 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.9.1) with UUCP id WAA27146; Tue, 15 Dec 1998 22:40:27 +0100 (MET) (envelope-from paulz@trantor.stuyts.nl) Received: from trantor.stuyts.nl (localhost [127.0.0.1]) by trantor.stuyts.nl (8.9.1/8.8.5) with ESMTP id WAA74654; Tue, 15 Dec 1998 22:04:59 +0100 (MET) Message-Id: <199812152104.WAA74654@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: current@freebsd.org Subject: Re: Weird NFS error using Solaris 7 server In-reply-to: Your message of "Mon, 14 Dec 1998 03:42:35 PST." <199812141142.DAA00657@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 22:04:58 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG I did some testing using the following test program: #include main() { int rv; rv=open("testfile1",O_CREAT|O_RDWR|O_EXCL,0666); if ( rv < 0 ) perror("testfile1"); rv=open("testfile2",O_CREAT|O_RDWR,0666); if ( rv < 0 ) perror("testfile2"); } This program results in a file called 'testfile1' being created on the server but having the creation of 'testfile2' fail with errno=79 ( which means EOVERFLOW 79 /* value too large to be stored in data type */ on Solaris ) If I do a snoop for the create requests sent I se the following request for testfile1 : RPC: ----- SUN RPC Header ----- RPC: RPC: Record Mark: last fragment, length = 156 RPC: Transaction id = 1478392196 RPC: Type = 0 (Call) RPC: RPC version = 2 RPC: Program = 100003 (NFS), version = 3, procedure = 8 RPC: Credentials: Flavor = 1 (Unix), len = 52 bytes RPC: Time = 0 RPC: Hostname = RPC: Uid = 544, Gid = 200 RPC: Groups = 200 0 5 14 68 69 70 1000 RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 8 (Create file) NFS: File handle = [008A] NFS: 0080000800000002000A000000000002694370EA000A000000000002694370EA NFS: File name = testfile1 NFS: Guard = 7F00000103000000 NFS: And the following for testfile2: RPC: ----- SUN RPC Header ----- RPC: RPC: Record Mark: last fragment, length = 192 RPC: Transaction id = 1478392200 RPC: Type = 0 (Call) RPC: RPC version = 2 RPC: Program = 100003 (NFS), version = 3, procedure = 8 RPC: Credentials: Flavor = 1 (Unix), len = 52 bytes RPC: Time = 0 RPC: Hostname = RPC: Uid = 544, Gid = 200 RPC: Groups = 200 0 5 14 68 69 70 1000 RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 8 (Create file) NFS: File handle = [008A] NFS: 0080000800000002000A000000000002694370EA000A000000000002694370EA NFS: File name = testfile2 NFS: Method = Unchecked NFS: Mode = 0644 NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rw- NFS: Group's permissions = r-- NFS: Other's permissions = r-- NFS: User ID = (not set) NFS: Group ID = (not set) NFS: Size = (not set) NFS: Access time = -1 (set to client time) NFS: Modification time = -1 (set to client time) NFS: NFS: So the open with the O_EXCL flag ( which succeeds ) shows a field decode by snoop as Guard and the failing request shows a lot of other fields. Hope someone can use this to find out what is wrong. ( If needed I can send the full snoop capture ) Paul -- Paul van der Zwan paulz @ trantor.stuyts.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 15:38:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13620 for freebsd-current-outgoing; Tue, 15 Dec 1998 15:38:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13615 for ; Tue, 15 Dec 1998 15:38:02 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id RAA06787; Tue, 15 Dec 1998 17:18:04 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812152318.RAA06787@ns.tar.com> From: "Richard Seaman, Jr." To: "Nate Williams" Cc: "current@freebsd.org" Date: Tue, 15 Dec 98 17:18:03 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Linux Threads patches available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Dec 1998 15:53:03 -0700, Nate Williams wrote: >Is this code GPL, or BSD copyrighted? If the former, then it can't be a >'normal' part of the kernel. It also has alot of implications for the >many vendors who use FreeBSD as an embedded system. The kernel patches are not GPL copyrighted. They're just patches to the existing FreeBSD kernel without any additional copyright restriction. Perhaps I should have added that I think the kernel patches included here, or something like them, will be needed with just about any "kernel threads" implementation. The patches allow kernel threads signal handling to move much closer to the posix requirements, but doesn't quite go all the way (linux doesn't either at this point). The patches also implement the linux "clone" call using rfork, and make changes to the linux_mmap and linux_wait calls in the linux emulation module. However the Linux Threads code is GPL copyrighted. The additional code provided in separate files needed to get the port working, is not GPL copyrighted. However, none of this code goes into the kernel, its all in a library. I know the GPL on the threads library is a drawback. Earlier I offered to try to implement a "one-to-one" kernel threads library by extending the current pthreads code, but almost all the comments I received were that people wanted something other than one-to-one kernel threads. This was beyond my capabilities and interest. When Brian Feldman posted his patches, which were close to working, it appeared to me that a port of linux threads could be a "quick fix" for kernel threads, while someone, eventually, does the real thing for FreeBSD. Its one-to-one kernel threads, but there's not much that needs to be changed in the threads library itself. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 15:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14943 for freebsd-current-outgoing; Tue, 15 Dec 1998 15:46:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14937 for ; Tue, 15 Dec 1998 15:46:39 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id PAA06322; Tue, 15 Dec 1998 15:45:08 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id PAA07273; Tue, 15 Dec 1998 15:45:07 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id PAA00799; Tue, 15 Dec 1998 15:45:06 -0800 (PST) From: Don Lewis Message-Id: <199812152345.PAA00799@salsa.gv.tsc.tdk.com> Date: Tue, 15 Dec 1998 15:45:06 -0800 In-Reply-To: John Polstra "Re: CVSROOT in making a release" (Dec 15, 9:33am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: John Polstra , root@swimsuit.internet.dk Subject: Re: CVSROOT in making a release Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 15, 9:33am, John Polstra wrote: } Subject: Re: CVSROOT in making a release } In article , } Leif Neland wrote: } > If I want to make a "release" of the current version of my system, for } > installing on another computer, how do I do it? } > } > More specifically, what is CVSROOT supposed to be if I have cvsupped } > current? } } To make a release, you must have the whole CVS repository -- not just } the checked-out current. ... or hack release/Makefile to make a copy of your checked-out copy of the source in the desired location rather than using cvs to check out a new copy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 15:59:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16869 for freebsd-current-outgoing; Tue, 15 Dec 1998 15:59:04 -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 PAA16858 for ; Tue, 15 Dec 1998 15:59:03 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA20203; Tue, 15 Dec 1998 15:57:49 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma020199; Tue, 15 Dec 98 15:57:36 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA11828; Tue, 15 Dec 1998 15:57:35 -0800 (PST) From: Archie Cobbs Message-Id: <199812152357.PAA11828@bubba.whistle.com> Subject: Re: Linux Threads patches available In-Reply-To: <199812152318.RAA06787@ns.tar.com> from "Richard Seaman, Jr." at "Dec 15, 98 05:18:03 pm" To: lists@tar.com Date: Tue, 15 Dec 1998 15:57:35 -0800 (PST) Cc: nate@mt.sri.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Seaman, Jr. writes: > Earlier I offered > to try to implement a "one-to-one" kernel threads library by extending > the current pthreads code, but almost all the comments I received were > that people wanted something other than one-to-one kernel threads. > This was beyond my capabilities and interest. Forgive me if I don't completely understand, but... It seems that if the one-to-one implementation were layered the right way, it would be easy to add a 'shim' layer (later on) that converts it into a many-to-many version of the same thing. In other words, can't you localize the operation 'give me a new context' to a single place in the code, which to start with always creates a kernel thread, but later can do some more intelligent thread management? Then we can start with 1:1 threads, and improve them later. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 16:11:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20950 for freebsd-current-outgoing; Tue, 15 Dec 1998 16:11:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ogurok.com (ogurok.com [208.212.72.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20941 for ; Tue, 15 Dec 1998 16:11:46 -0800 (PST) (envelope-from oleg@ogurok.com) Received: from localhost (oleg@localhost) by ogurok.com (8.9.1/8.9.1) with ESMTP id TAA21651 for ; Tue, 15 Dec 1998 19:20:17 -0500 (EST) (envelope-from oleg@ogurok.com) Date: Tue, 15 Dec 1998 19:20:17 -0500 (EST) From: Oleg Ogurok To: freebsd-current@FreeBSD.ORG Subject: /ports/mbone/speakfreely - can't compile. 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, all. I am getting following errors trying to "make" this port. I am running 3.0-CURRENT Dec15, and just cvsup'ed the CURRENT port collection. BTW, is freebsd-bugs correct maillist to put things like this? ===> speak_freely ===> Building for speak_freely-6.1c cc -O -pipe -Iadpcm -Ilpc -Iidea -I/usr/include -I/usr/local/include -DInternet_Port=2074 -DHALF_DUPLEX -DM_LITTLE_ENDIAN -c mike.c mike.c:877: warning: static declaration for `sendfile' follows non-static mike.c: In function `sendfile': mike.c:878: argument `f' doesn't match prototype /usr/include/sys/socket.h:395: prototype declaration mike.c:878: number of arguments doesn't match prototype /usr/include/sys/socket.h:395: prototype declaration mike.c: In function `main': mike.c:1948: warning: passing arg 1 of `sendfile' makes integer from pointer without a cast mike.c:1948: too few arguments to function `sendfile' mike.c:1960: too few arguments to function `sendfile' *** Error code 1 Stop. *** Error code 1 Oleg Ogurok oleg@ogurok.com http://www.ogurok.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 16:16:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21579 for freebsd-current-outgoing; Tue, 15 Dec 1998 16:16:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21556; Tue, 15 Dec 1998 16:16:45 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id QAA06688; Tue, 15 Dec 1998 16:11:32 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id QAA07792; Tue, 15 Dec 1998 16:11:30 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id QAA00971; Tue, 15 Dec 1998 16:11:29 -0800 (PST) From: Don Lewis Message-Id: <199812160011.QAA00971@salsa.gv.tsc.tdk.com> Date: Tue, 15 Dec 1998 16:11:29 -0800 In-Reply-To: Poul-Henning Kamp "Re: if_sppp is BROKEN!!!" (Dec 15, 12:23am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Poul-Henning Kamp , "Jonathan M. Bresler" Subject: Re: if_sppp is BROKEN!!! Cc: johan@granlund.nu, julian@whistle.com, lars@akerlings.t.se, current@FreeBSD.ORG, isdn@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 15, 12:23am, Poul-Henning Kamp wrote: } Subject: Re: if_sppp is BROKEN!!! } But with that said, there is still something to be said for modular } and well defined interfaces. But streams ? No. They were great } for async protocols, but they fail badly for packet stuff. This is one of my favorite quotes, from Van Jacobson in his cslip package: Note that in Sun OS 4.x, slip runs over a "streams" tty driver where much of the underlying support code was taken from AT&T's System-V Unix. This support code is incredibly bad: A Sun-3/50 will run both it's serial ports at 38,400 baud with no problems under Sun OS 3.x (which uses the Berkeley/V7 tty driver). That same 3/50 can not keep up with one serial port running at 9600 baud under Sun OS 4.0.3. The AT&T code also doesn't handle any kind of exception correctly: If it runs out of stream buffers or gets a signal or interrupt at the wrong time, the system will crash. So, run Sun OS 3 if you have any choice. If you have no choice, try this stuff but don't expect reasonable performance or robustness. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 17:00:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26145 for freebsd-current-outgoing; Tue, 15 Dec 1998 17:00:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26140 for ; Tue, 15 Dec 1998 17:00:34 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id RAA07469; Tue, 15 Dec 1998 17:00:25 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id RAA08730; Tue, 15 Dec 1998 17:00:23 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA01124; Tue, 15 Dec 1998 17:00:22 -0800 (PST) From: Don Lewis Message-Id: <199812160100.RAA01124@salsa.gv.tsc.tdk.com> Date: Tue, 15 Dec 1998 17:00:22 -0800 In-Reply-To: Archie Cobbs "Re: if_sppp is BROKEN!!!" (Dec 15, 12:56pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Archie Cobbs Subject: Re: if_sppp is BROKEN!!! Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 15, 12:56pm, Archie Cobbs wrote: } Subject: Re: if_sppp is BROKEN!!! } - Frame relay node } } Receives raw frame relay frames, and has hooks for each DLCI. } } - Frame relay LMI } } Hook this to DLCI 0 and DLCI 1023 to do auto-detection of } frame relay LMI type, and perform the appropriate LMI protocol. Drool! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 17:17:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28207 for freebsd-current-outgoing; Tue, 15 Dec 1998 17:17:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28200 for ; Tue, 15 Dec 1998 17:17:36 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id UAA05353; Tue, 15 Dec 1998 20:22:12 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 15 Dec 1998 20:22:12 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Oleg Ogurok cc: freebsd-current@FreeBSD.ORG Subject: Re: /ports/mbone/speakfreely - can't compile. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this should be posted to ports@freebsd.org, however David G recently added a syscall to 3.0, 'sendfile' the point of it is to send a file through a socket with as little overhead as possible. This is really nifty but certain newer interfaces for freebsd syscalls and freebsd specific library calls are really going to cause C namespace problems. I wish someone would take this into consideration when adding new functionality. man devstat: int getversion(void) int checkversion(void) would it kill for a devstat_* prefix? i know you need to -ldevstat for these problems to show up, but simply including socket.h causes sendfile problems. I'm just hoping to stir a discussion about this. Who hasn't at one time coded a program with 'sendfile' as an argument or function name? Maybe at least more isolation, ala sendfile.h. Anyhow, to answer your question, grep all the .c and .h files and replace 'sendfile' with 'sendfile_freely' or something. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 15 Dec 1998, Oleg Ogurok wrote: > Hi, all. > > I am getting following errors trying to "make" this port. > I am running 3.0-CURRENT Dec15, and just cvsup'ed the CURRENT port > collection. > BTW, is freebsd-bugs correct maillist to put things like this? > > ===> speak_freely > ===> Building for speak_freely-6.1c > cc -O -pipe -Iadpcm -Ilpc -Iidea -I/usr/include -I/usr/local/include > -DInternet_Port=2074 -DHALF_DUPLEX -DM_LITTLE_ENDIAN -c mike.c > mike.c:877: warning: static declaration for `sendfile' follows non-static > mike.c: In function `sendfile': > mike.c:878: argument `f' doesn't match prototype > /usr/include/sys/socket.h:395: prototype declaration > mike.c:878: number of arguments doesn't match prototype > /usr/include/sys/socket.h:395: prototype declaration > mike.c: In function `main': > mike.c:1948: warning: passing arg 1 of `sendfile' makes integer from > pointer > without a cast > mike.c:1948: too few arguments to function `sendfile' > mike.c:1960: too few arguments to function `sendfile' > *** Error code 1 > > Stop. > *** Error code 1 > > > Oleg Ogurok > oleg@ogurok.com > http://www.ogurok.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 17:25:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29700 for freebsd-current-outgoing; Tue, 15 Dec 1998 17:25:52 -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 RAA29695 for ; Tue, 15 Dec 1998 17:25:49 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA03352; Wed, 16 Dec 1998 11:55:36 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA18259; Wed, 16 Dec 1998 11:55:37 +1030 (CST) Message-ID: <19981216115536.W15815@freebie.lemis.com> Date: Wed, 16 Dec 1998 11:55:36 +1030 From: Greg Lehey To: mjacob@feral.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour References: <19981215135448.B15815@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew Jacob on Mon, Dec 14, 1998 at 07:31:15PM -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 Monday, 14 December 1998 at 19:31:15 -0800, Matthew Jacob wrote: >> >> Well, you don't have to go overboard. Combine compression and >> density. We have BSD semantics, I suppose, so the only other thing is >> no rewind, which we already cater for. So for, say, an Exabyte >> 8505XL, you'd have: >> >> /dev/rst0l 8202 mode, no compression >> /dev/rst0n 8202 mode, compression >> /dev/rst0h 8205 mode, no compression >> /dev/rst0c 8205 mode, compression >> /dev/nrst0l 8202 mode, no compression, no rewind >> /dev/nrst0n 8202 mode, compression, no rewind >> /dev/nrst0h 8205 mode, no compression, no rewind >> /dev/nrst0c 8205 mode, compression, no rewind >> >> Sure, it's more than now, but it shouldn't confuse people too much. > > Cool, but there are four possible densities in the current data > structures. And speeds (has anyone actually ever found a drive that > *uses* these?). And multiple compression algorithms to select from. > > I'm kind of inclined to think that the compromise of > > Rew/Norew X Compress/Nocompress X Low/High density > > is sufficient as long as you can establish that the latter two > categories are a persistent (not through reboot, tho) cache of possible > values that you can set via the mt(1) command. I can't see any particular reason to restrict the minor number format if it's not necessary. So we have 4 densities, n (<=4?) speeds and compression. That makes 5 bits. Then we have non-rewind, a maximum of 16 units per drive and (on a PC) probably not more than 16 controllers. A total of 14 bits of minor number out of the 24 available: in other words, there should be no problem finding a minor number format which fits. The naming is a different matter. The `convenient' format doesn't have to cover every possibility; we could think up a `complete' format at a later date, something like /dev/tape/nrc0u5d3s1c meaning no rewind, raw, controller 0, unit 5, density setting 3, speed setting 1, compression. There's no reason to think these out at this stage, since they're probably not needed; but if we create a minor number format which can't represent one or the other of them, we're bound to find a case where it's needed. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 17:34:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01191 for freebsd-current-outgoing; Tue, 15 Dec 1998 17:34:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01173 for ; Tue, 15 Dec 1998 17:33:55 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id CAA09939 for freebsd-current@FreeBSD.ORG; Wed, 16 Dec 1998 02:33:50 +0100 (CET) (envelope-from olli) Date: Wed, 16 Dec 1998 02:33:50 +0100 (CET) From: Oliver Fromme Message-Id: <199812160133.CAA09939@dorifer.heim3.tu-clausthal.de> To: freebsd-current@FreeBSD.ORG Subject: Re: modification to exec in the kernel? Newsgroups: list.freebsd-current Organization: Administration Heim 3 Reply-To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joe Abley wrote in list.freebsd-current: > On Tue, Dec 15, 1998 at 08:44:16AM +0200, Mark Murray wrote: > > Your security model is flawed. A user can do anything she wants > > (justabout) with shellscript and perl. Picking on compiled binaries > > is not going to make you that much safer. > > "Just about" - so there are _some_ exploits that would require a user-supplied > binary? So preventing execution of user-supplied binaries does give _some_ > safety benefit? > > I take your point, though - I was forgetting how much feature bloat there > is in perl. In fact, you can execute arbitrary byte code in perl5. #!/usr/local/bin/perl require DynaLoader; DynaLoader::dl_install_xsub("main::hangme", unpack("I", pack("P4", "\xF0\x0F\xC7\xC8"))); hangme(); In case you haven't recognized it, that beast is equivalent with the following C "program": unsigned char main[4] = {0xF0, 0x0F, 0xC7, 0xC8}; > Why people can't just make do with awk is a little beyond me :) Me too. :) Quite a lot of my scripts begin with #!/usr/bin/awk -f :) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 18:01:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04419 for freebsd-current-outgoing; Tue, 15 Dec 1998 18:01:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04414 for ; Tue, 15 Dec 1998 18:00:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA00944; Tue, 15 Dec 1998 17:58:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812160158.RAA00944@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Paul van der Zwan cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-reply-to: Your message of "Tue, 15 Dec 1998 22:04:58 +0100." <199812152104.WAA74654@trantor.stuyts.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 17:58:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I did some testing using the following test program: > #include > main() > { > int rv; > rv=open("testfile1",O_CREAT|O_RDWR|O_EXCL,0666); > if ( rv < 0 ) > perror("testfile1"); > rv=open("testfile2",O_CREAT|O_RDWR,0666); > if ( rv < 0 ) > perror("testfile2"); > } > > This program results in a file called 'testfile1' being created on the server > but having the creation of 'testfile2' fail with errno=79 ( which means > EOVERFLOW 79 /* value too large to be stored in data type */ > on Solaris ) > > If I do a snoop for the create requests sent I se the following request for > testfile1 : > RPC: ----- SUN RPC Header ----- > RPC: > RPC: Record Mark: last fragment, length = 156 > RPC: Transaction id = 1478392196 > RPC: Type = 0 (Call) > RPC: RPC version = 2 > RPC: Program = 100003 (NFS), version = 3, procedure = 8 > RPC: Credentials: Flavor = 1 (Unix), len = 52 bytes > RPC: Time = 0 > RPC: Hostname = > RPC: Uid = 544, Gid = 200 > RPC: Groups = 200 0 5 14 68 69 70 1000 > RPC: Verifier : Flavor = 0 (None), len = 0 bytes > RPC: > NFS: ----- Sun NFS ----- > NFS: > NFS: Proc = 8 (Create file) > NFS: File handle = [008A] > NFS: 0080000800000002000A000000000002694370EA000A000000000002694370EA > NFS: File name = testfile1 > NFS: Guard = 7F00000103000000 > NFS: > > And the following for testfile2: > RPC: ----- SUN RPC Header ----- > RPC: > RPC: Record Mark: last fragment, length = 192 > RPC: Transaction id = 1478392200 > RPC: Type = 0 (Call) > RPC: RPC version = 2 > RPC: Program = 100003 (NFS), version = 3, procedure = 8 > RPC: Credentials: Flavor = 1 (Unix), len = 52 bytes > RPC: Time = 0 > RPC: Hostname = > RPC: Uid = 544, Gid = 200 > RPC: Groups = 200 0 5 14 68 69 70 1000 > RPC: Verifier : Flavor = 0 (None), len = 0 bytes > RPC: > NFS: ----- Sun NFS ----- > NFS: > NFS: Proc = 8 (Create file) > NFS: File handle = [008A] > NFS: 0080000800000002000A000000000002694370EA000A000000000002694370EA > NFS: File name = testfile2 > NFS: Method = Unchecked > NFS: Mode = 0644 > NFS: Setuid = 0, Setgid = 0, Sticky = 0 > NFS: Owner's permissions = rw- > NFS: Group's permissions = r-- > NFS: Other's permissions = r-- > NFS: User ID = (not set) > NFS: Group ID = (not set) > NFS: Size = (not set) > NFS: Access time = -1 (set to client time) > NFS: Modification time = -1 (set to client time) > NFS: > NFS: > > So the open with the O_EXCL flag ( which succeeds ) shows a field decode by > snoop as Guard and the failing request shows a lot of other fields. This looks like snoop is failing to usefully process the packet. Can you feed the trace to Ethereal and see what it has to say about it? > Hope someone can use this to find out what is wrong. > ( If needed I can send the full snoop capture ) If you've got it in a format that can be used by other programs, please do make it available somewhere. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 18:08:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05085 for freebsd-current-outgoing; Tue, 15 Dec 1998 18:08:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05079 for ; Tue, 15 Dec 1998 18:08:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01013; Tue, 15 Dec 1998 18:06:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812160206.SAA01013@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD Buildworld fails In-reply-to: Your message of "Tue, 15 Dec 1998 17:35:52 EST." <4.1.19981215173455.009a4b10@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 18:06:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Buildworld is still failing after a make clean, and cvsups today > (FreeBSD-3.0-CURRENT): There are no errors in this transcript. I suspect that you're not properly capturing the full build output; use the 'script' command for this. > > cc -nostdinc -O -pipe -DBOOT_FORTH > -I/usr/src/sys/boot/i386/loader/../../ficl > -I/usr/src/sys/boot/i386/loader/../../common > -I/usr/src/sys/boot/i386/loader/../../.. -I. -Wall > -I/usr/src/sys/boot/i386/loader/.. > -I/usr/src/sys/boot/i386/loader/../btx/lib -elf -DNEW_LINKER_SET > -I/usr/obj/elf/usr/src/tmp/usr/include -c > /usr/src/sys/boot/i386/loader/../../common/interp.c > /usr/src/sys/boot/i386/loader/../../common/interp.c: In function `perform': > /usr/src/sys/boot/i386/loader/../../common/interp.c:48: warning: unused > variable `i' > /usr/src/sys/boot/i386/loader/../../common/interp.c: In function `interact': > /usr/src/sys/boot/i386/loader/../../common/interp.c:85: warning: implicit > declaration of function `bf_init' > /usr/src/sys/boot/i386/loader/../../common/interp.c:110: warning: implicit > declaration of function `bf_run' > /usr/src/sys/boot/i386/loader/../../common/interp.c:82: warning: unused > variable `argv' > /usr/src/sys/boot/i386/loader/../../common/interp.c:81: warning: unused > variable `argc' > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > > 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 Tue Dec 15 18:10:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05451 for freebsd-current-outgoing; Tue, 15 Dec 1998 18:10:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05445 for ; Tue, 15 Dec 1998 18:10:49 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forresta (forrie.ne.mediaone.net [24.128.73.118]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id VAA81105; Tue, 15 Dec 1998 21:09:59 -0500 (EST) Message-Id: <4.1.19981215211051.0092faa0@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 15 Dec 1998 21:11:29 -0500 To: Mike Smith From: Forrest Aldrich Subject: Re: FreeBSD Buildworld fails Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199812160206.SAA01013@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 06:06 PM 12/15/98 -0800, Mike Smith wrote: >> >> Buildworld is still failing after a make clean, and cvsups today >> (FreeBSD-3.0-CURRENT): > >There are no errors in this transcript. I suspect that you're not >properly capturing the full build output; use the 'script' command >for this. [ ... ] Here ya go... just bombed again: Date: Tue, 15 Dec 1998 21:08:17 -0500 (EST) From: Forrest Aldrich Message-Id: <199812160208.VAA81096@spook.navinet.net> To: forrie@forrie.com X-UIDL: f11ea8d774d85c1bda77ed91542b3e48 cc -nostdinc -O -pipe -DBOOT_FORTH -I/usr/src/sys/boot/i386/loader/../../ficl -I/usr/src/sys/boot/i386/loader/../../common -I/usr/src/sys/boot/i386/loader/../../.. -I. -Wall -I/usr/src/sys/boot/i386/loader/.. -I/usr/src/sys/boot/i386/loader/../btx/lib -elf -DNEW_LINKER_SET -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/sys/boot/i386/loader/../../common/commands.c Can't load module IO, dynamic loading not available in this perl. (You may need to build a new perl executable which either supports dynamic loading or has the IO module statically linked into it.) at /usr/libdata/perl/5.00502/mach/IO/Handle.pm line 248 BEGIN failed--compilation aborted at /usr/libdata/perl/5.00502/mach/IO/Seekable.pm line 50. BEGIN failed--compilation aborted at /usr/libdata/perl/5.00502/mach/IO/File.pm line 111. BEGIN failed--compilation aborted at /usr/src/sys/boot/i386/loader/../../common/merge_help.pl line 45. /usr/src/sys/boot/i386/loader/main.c: In function `main': /usr/src/sys/boot/i386/loader/main.c:103: warning: implicit declaration of function `bcache_init' /usr/src/sys/boot/i386/loader/../../common/bcache.c: In function `command_bcache': /usr/src/sys/boot/i386/loader/../../common/bcache.c:255: warning: unsigned int format, long unsigned int arg (arg 3) cc -nostdinc -O -pipe -DBOOT_FORTH -I/usr/src/sys/boot/i386/loader/../../ficl -I/usr/src/sys/boot/i386/loader/../../common -I/usr/src/sys/boot/i386/loader/../../.. -I. -Wall -I/usr/src/sys/boot/i386/loader/.. -I/usr/src/sys/boot/i386/loader/../btx/lib -elf -DNEW_LINKER_SET -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/sys/boot/i386/loader/../../common/console.c *** Error code 2 cc -nostdinc -O -pipe -DBOOT_FORTH -I/usr/src/sys/boot/i386/loader/../../ficl -I/usr/src/sys/boot/i386/loader/../../common -I/usr/src/sys/boot/i386/loader/../../.. -I. -Wall -I/usr/src/sys/boot/i386/loader/.. -I/usr/src/sys/boot/i386/loader/../btx/lib -elf -DNEW_LINKER_SET -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/sys/boot/i386/loader/../../common/devopen.c cc -c vers.c 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 18:17:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05928 for freebsd-current-outgoing; Tue, 15 Dec 1998 18:17:44 -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 SAA05923 for ; Tue, 15 Dec 1998 18:17:41 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id NAA13518; Wed, 16 Dec 1998 13:29:57 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812160229.NAA13518@cimlogic.com.au> Subject: Re: FreeBSD Buildworld fails In-Reply-To: <199812160206.SAA01013@dingo.cdrom.com> from Mike Smith at "Dec 15, 98 06:06:42 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 16 Dec 1998 13:29:57 +1100 (EST) Cc: forrie@forrie.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > > Buildworld is still failing after a make clean, and cvsups today > > (FreeBSD-3.0-CURRENT): > > There are no errors in this transcript. I suspect that you're not > properly capturing the full build output; use the 'script' command > for this. I think it's the "case of the missing elf shared loader" that only gets reported by the kernel, not into user-space. Perl is really difficult to bootstrap build. I wish we had a rule that said it is not allowed to be used as a build tool. Perhaps I'll go hide now. 8-) -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 18:23:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06487 for freebsd-current-outgoing; Tue, 15 Dec 1998 18:23:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06482 for ; Tue, 15 Dec 1998 18:22:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01095; Tue, 15 Dec 1998 18:20:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812160220.SAA01095@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Forrest Aldrich cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD Buildworld fails In-reply-to: Your message of "Tue, 15 Dec 1998 21:11:29 EST." <4.1.19981215211051.0092faa0@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 18:20:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 06:06 PM 12/15/98 -0800, Mike Smith wrote: > >> > >> Buildworld is still failing after a make clean, and cvsups today > >> (FreeBSD-3.0-CURRENT): > > > >There are no errors in this transcript. I suspect that you're not > >properly capturing the full build output; use the 'script' command > >for this. > [ ... ] > > Here ya go... just bombed again: You're using a -j something build; it's always a good idea to remove the -j and build again to get a meaningful output. In this case, the problem is actually with the buildtools verion of Perl - I'm trying to resolve this right now. > Date: Tue, 15 Dec 1998 21:08:17 -0500 (EST) > From: Forrest Aldrich > Message-Id: <199812160208.VAA81096@spook.navinet.net> > To: forrie@forrie.com > X-UIDL: f11ea8d774d85c1bda77ed91542b3e48 > > cc -nostdinc -O -pipe -DBOOT_FORTH > -I/usr/src/sys/boot/i386/loader/../../ficl > -I/usr/src/sys/boot/i386/loader/../../common > -I/usr/src/sys/boot/i386/loader/../../.. -I. -Wall > -I/usr/src/sys/boot/i386/loader/.. > -I/usr/src/sys/boot/i386/loader/../btx/lib -elf -DNEW_LINKER_SET > -I/usr/obj/elf/usr/src/tmp/usr/include -c > /usr/src/sys/boot/i386/loader/../../common/commands.c > Can't load module IO, dynamic loading not available in this perl. > (You may need to build a new perl executable which either supports > dynamic loading or has the IO module statically linked into it.) > at /usr/libdata/perl/5.00502/mach/IO/Handle.pm line 248 here... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 18:26:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07002 for freebsd-current-outgoing; Tue, 15 Dec 1998 18:26:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06997 for ; Tue, 15 Dec 1998 18:26:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01119; Tue, 15 Dec 1998 18:23:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812160223.SAA01119@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: mike@smith.net.au (Mike Smith), forrie@forrie.com, freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD Buildworld fails In-reply-to: Your message of "Wed, 16 Dec 1998 13:29:57 +1100." <199812160229.NAA13518@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 18:23:33 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > > > > > Buildworld is still failing after a make clean, and cvsups today > > > (FreeBSD-3.0-CURRENT): > > > > There are no errors in this transcript. I suspect that you're not > > properly capturing the full build output; use the 'script' command > > for this. > > I think it's the "case of the missing elf shared loader" that only gets > reported by the kernel, not into user-space. Perl is really difficult > to bootstrap build. I wish we had a rule that said it is not allowed > to be used as a build tool. Perhaps I'll go hide now. 8-) If we had Tcl in the base system, this would be trivial. I don't want to use Perl at all - one is simply told that Perl is the be-all and end-all of hackish scripting languages, but it truly appears to be too fragile for that. If anyone wants to take the offending script and rewrite it in a fashion which is friendly to the build environment, please be my guest. Perhaps the built versions of the help texts should be committed to the repository? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 18:34:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07883 for freebsd-current-outgoing; Tue, 15 Dec 1998 18:34:44 -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 SAA07873 for ; Tue, 15 Dec 1998 18:34:39 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id NAA13577; Wed, 16 Dec 1998 13:47:14 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812160247.NAA13577@cimlogic.com.au> Subject: Re: FreeBSD Buildworld fails In-Reply-To: <199812160223.SAA01119@dingo.cdrom.com> from Mike Smith at "Dec 15, 98 06:23:33 pm" To: mike@smith.net.au (Mike Smith) Date: Wed, 16 Dec 1998 13:47:13 +1100 (EST) Cc: forrie@forrie.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > If we had Tcl in the base system, this would be trivial. I don't want > to use Perl at all - one is simply told that Perl is the be-all and > end-all of hackish scripting languages, but it truly appears to be too > fragile for that. It's not perl that is fragile so much as it's build process doesn't lend itself to our build/bootstrap procedure. We expect that our bootstrap procedure knows best. Perl knows that perl knows best. Sigh. > If anyone wants to take the offending script and rewrite it in a > fashion which is friendly to the build environment, please be my guest. > Perhaps the built versions of the help texts should be committed to the > repository? That's the easy way out of the problem if it doesn't cause "but why aren't my text files updated by buildworld" type questions. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 18:44:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08811 for freebsd-current-outgoing; Tue, 15 Dec 1998 18:44:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08802 for ; Tue, 15 Dec 1998 18:44:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA00394; Tue, 15 Dec 1998 18:40:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812160240.SAA00394@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: mike@smith.net.au (Mike Smith), forrie@forrie.com, current@FreeBSD.ORG Subject: Re: FreeBSD Buildworld fails In-reply-to: Your message of "Wed, 16 Dec 1998 13:47:13 +1100." <199812160247.NAA13577@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 18:40:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If anyone wants to take the offending script and rewrite it in a > > fashion which is friendly to the build environment, please be my guest. > > Perhaps the built versions of the help texts should be committed to the > > repository? > > That's the easy way out of the problem if it doesn't cause "but why aren't > my text files updated by buildworld" type questions. Changes to the (default) text are only going to happen if you update one of the master texts. It's debatable as to whether the master texts should be intermixed with the source as they are now, or separate to make i18n work simpler. At any rate, I'm not convinced that committing the merged text is the right way to go; it's even more dubious than having the generated syscall-related files in the repo. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 18:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09701 for freebsd-current-outgoing; Tue, 15 Dec 1998 18:53:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09696 for ; Tue, 15 Dec 1998 18:52:57 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id LAA03052; Wed, 16 Dec 1998 11:50:58 +0900 (JST) Message-Id: <199812160250.LAA03052@chandra.eatell.msr.prug.or.jp> To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Tue, 15 Dec 1998 04:31:37 PST." <199812151231.EAA05213@dingo.cdrom.com> Date: Wed, 16 Dec 1998 11:50:58 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > config(8) does two things; it builds static tables of configuration > data, and it arranges for code aggregation into a kernel object. newconfig" is not only config(8), but also include bus and device configuration code. See: sys/kern/subr_autoconf.c (in "newconfig", it it much better.) Now, "newconfig" support static-linked kernel only, but it is first step. On near future, we support UserConfig, and next target is dynamic loadable module. These configuration, we support "newconfig" integrated. > > On "new-bus", How to handle boot device like console, fd, wd, ... ? > > I can't make sense of this question; could you expand a little? I think, some case needs statically-configuration. So, using boot-time divices, I think that they are statically-configurated. I want to know if new-bus using another way. Mike, new-bus is good; but "newconfig" is also good, I think. Until now, same purpose drivers stand side by side in FreeBSD. (example, Voxware and Luigi's new audio driver, BSD ATM and HARP, ...) "new-bus" and "newconfig", I think same relation. Choose by users. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 19:18:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11634 for freebsd-current-outgoing; Tue, 15 Dec 1998 19:18:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11628 for ; Tue, 15 Dec 1998 19:18:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id TAA08918 for ; Tue, 15 Dec 1998 19:17:55 -0800 Date: Tue, 15 Dec 1998 19:17:55 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-current@FreeBSD.ORG Subject: Tape Driver Changes Proposed: Variable Mode as default In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still processing and munching on the responses from the last call on this- but closure is pretty close- in the interim, here's one that should be less controversial: + forcing variable mode for tape devices unless quirked otherwise Do people have an opinion on this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 19:20:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11975 for freebsd-current-outgoing; Tue, 15 Dec 1998 19:20:53 -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 TAA11970 for ; Tue, 15 Dec 1998 19:20:50 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id WAA15405; Tue, 15 Dec 1998 22:19:07 -0500 (EST) Date: Tue, 15 Dec 1998 22:19:07 -0500 (EST) From: Chuck Robey To: Mike Smith cc: freebsd-current@FreeBSD.ORG, John Birrell , forrie@forrie.com Subject: Re: FreeBSD Buildworld fails In-Reply-To: <199812160223.SAA01119@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 Tue, 15 Dec 1998, Mike Smith wrote: > > Mike Smith wrote: > > > > > > I think it's the "case of the missing elf shared loader" that only gets > > reported by the kernel, not into user-space. Perl is really difficult > > to bootstrap build. I wish we had a rule that said it is not allowed > > to be used as a build tool. Perhaps I'll go hide now. 8-) > > If we had Tcl in the base system, this would be trivial. I don't want > to use Perl at all - one is simply told that Perl is the be-all and > end-all of hackish scripting languages, but it truly appears to be too > fragile for that. But the reasons for keeping tcl _out_ of the main systems are a heck of a lot larger than those for perl. Unfortunately, the tcl folks seemingly care very little about maintaining backwards compatibility, and many tcl tools require their own specific version of tcl/tk to run. That's been a major problem with tcl, and I don't quite understand why those folks can't see that. It certainly would have made tcl the ideal language, if they'd just cared a little more about not constantly turning tcl apps into legacy apps. OTOH, perl seems to have just one _really_ incompatible step, going from the very old 4.036 to the more recent 5.* versions. I don't split the 5.* versions apart, because the backwards compatibility is really there. As long as we keep the system perl up to date (and Mark's done a great job of watching perl) then we've heard no complaints, have we? Granted, buildwise, it's a PITA, but that doesn't change the arguments WRT tcl. I wouldn't want to suggest a different scripting language (and there ARE others that would qualify) because perl is becoming as much of a required tool as, say, grep ... changing it out for something that builds easier isn't an option ... you'd need to keep perl anyhow, you'd just get to build it later in the process. Is it worth that? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 19:31:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13297 for freebsd-current-outgoing; Tue, 15 Dec 1998 19:31:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13288 for ; Tue, 15 Dec 1998 19:31:48 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id TAA19404; Tue, 15 Dec 1998 19:31:33 -0800 (PST) Date: Tue, 15 Dec 1998 19:31:33 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199812160331.TAA19404@math.berkeley.edu> To: grog@lemis.com Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour Cc: dan@math.berkeley.edu, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I can't see any particular reason to restrict the minor number format > if it's not necessary. So we have 4 densities, n (<=4?) speeds and > compression. That makes 5 bits. Then we have non-rewind, a maximum > of 16 units per drive and (on a PC) probably not more than 16 > controllers. A total of 14 bits of minor number out of the 24 > available: in other words, there should be no problem finding a minor > number format which fits. One good reason for restricting the minor number format is that 16384 (i.e. 2^14) different entries for tape devices in /dev would be painful beyound belief. I claim that the idea of specifying tape drive operating parameters via minor device number was a really bad idea from almost the very beginning (unix v6 I believe) and should have been abandoned after the ioctl() system call became available. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 19:36:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13614 for freebsd-current-outgoing; Tue, 15 Dec 1998 19:36:22 -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 TAA13609 for ; Tue, 15 Dec 1998 19:36:16 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id OAA03849; Wed, 16 Dec 1998 14:06:03 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id OAA24619; Wed, 16 Dec 1998 14:06:04 +1030 (CST) Message-ID: <19981216140604.H15815@freebie.lemis.com> Date: Wed, 16 Dec 1998 14:06:04 +1030 From: Greg Lehey To: Dan Strick Cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour References: <199812160331.TAA19404@math.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812160331.TAA19404@math.berkeley.edu>; from Dan Strick on Tue, Dec 15, 1998 at 07:31:33PM -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 Tuesday, 15 December 1998 at 19:31:33 -0800, Dan Strick wrote: >> I can't see any particular reason to restrict the minor number format >> if it's not necessary. So we have 4 densities, n (<=4?) speeds and >> compression. That makes 5 bits. Then we have non-rewind, a maximum >> of 16 units per drive and (on a PC) probably not more than 16 >> controllers. A total of 14 bits of minor number out of the 24 >> available: in other words, there should be no problem finding a minor >> number format which fits. > > One good reason for restricting the minor number format is that 16384 > (i.e. 2^14) different entries for tape devices in /dev would be painful > beyound belief. You wouldn't automatically create all device nodes, just those that corresponded to real devices and their functions. > I claim that the idea of specifying tape drive operating parameters > via minor device number was a really bad idea from almost the very > beginning (unix v6 I believe) and should have been abandoned after > the ioctl() system call became available. How would you tell tar to make a backup, this time only, which didn't compress? If you did it with mt(1), how would you ensure that nobody dicked with the settings between your running mt(1) and tar(1)? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 20:19:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17962 for freebsd-current-outgoing; Tue, 15 Dec 1998 20:19:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17956 for ; Tue, 15 Dec 1998 20:19:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA00907; Tue, 15 Dec 1998 20:17:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812160417.UAA00907@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa cc: Mike Smith , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 16 Dec 1998 11:50:58 +0900." <199812160250.LAA03052@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 20:17:07 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > config(8) does two things; it builds static tables of configuration > > data, and it arranges for code aggregation into a kernel object. > > newconfig" is not only config(8), but also include bus and device > configuration code. There is code which parses the static configuration data, sure. The same goes for old config. > See: sys/kern/subr_autoconf.c (in "newconfig", it it much better.) Yes, I'm familiar with newconfig. > Now, "newconfig" support static-linked kernel only, but it is > first step. On near future, we support UserConfig, and next target > is dynamic loadable module. These configuration, we support > "newconfig" integrated. If you haven't even looked at the issues involved in dynamic growth of the newconfig-generated device and bus tree, then I'd have to strongly suggest that you're wasting your effort right now. > > > On "new-bus", How to handle boot device like console, fd, wd, ... ? > > > > I can't make sense of this question; could you expand a little? > > I think, some case needs statically-configuration. So, using > boot-time divices, I think that they are > statically-configurated. I want to know if new-bus using another way. You're still not understanding the difference between configuration and aggregation. The new-bus code supports both static (compile-time) and dynamic (run-time) configuration, as well as build-time, load-time and run-time aggregation. Drivers required for the boot process need to be aggregated at either build-time or load-time (console, root disk), and they can either be statically or dynamically configured - static configuration is optional and only required if the driver or its parend bus can't work things out itself. The metainformation required to connect devices and busses is almost entirely contained in the drivers themselves, rather than being constructed at build-time by an extern configuration tool. This is more or less mandatory if you want to be able to add arbitrary bus and device code to a running system, and one of the major marks against newconfig. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 20:45:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21025 for freebsd-current-outgoing; Tue, 15 Dec 1998 20:45:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21017 for ; Tue, 15 Dec 1998 20:45:08 -0800 (PST) (envelope-from furuta@sra.co.jp) Received: from sramhc.sra.co.jp (sramhc [133.137.20.31]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id NAA01713; Wed, 16 Dec 1998 13:44:37 +0900 (JST) Received: from sramhc.sra.co.jp (furuta@localhost [127.0.0.1]) by sramhc.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id NAA07797; Wed, 16 Dec 1998 13:44:51 +0900 (JST) Message-Id: <199812160444.NAA07797@sramhc.sra.co.jp> To: mike@smith.net.au Cc: y-nakaga@nwsl.mesh.ad.jp, current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: Your message of "Tue, 15 Dec 1998 20:17:07 -0800" References: <199812160417.UAA00907@dingo.cdrom.com> X-Mailer: Mew version 1.70 on Emacs 19.28.7 / Mule 2.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 16 Dec 1998 13:44:50 +0900 From: Atsushi Furuta Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In article <199812160417.UAA00907@dingo.cdrom.com>, Mike Smith writes: > If you haven't even looked at the issues involved in dynamic growth of > the newconfig-generated device and bus tree, then I'd have to strongly > suggest that you're wasting your effort right now. Of cource, *our* newconfig will be support dynamic growth of the device instance tree and device directed graph. Actually, I have changed from cfdata structure array to TAILQ. Please look at our repository... > Drivers required for the boot process need to be aggregated at either > build-time or load-time (console, root disk), and they can either be > statically or dynamically configured - static configuration is optional > and only required if the driver or its parend bus can't work things out > itself. I have a different opinion. As noted by Doug, current implementation of new-bus requires config(8) to specify ivars. It is not fair to say "newconfig is static, but new-bus is dynamic" without dynamic parameter specification. > The metainformation required to connect devices and busses is almost > entirely contained in the drivers themselves, rather than being > constructed at build-time by an extern configuration tool. This is > more or less mandatory if you want to be able to add arbitrary bus and > device code to a running system, and one of the major marks against > newconfig. Our newconfig will be able to specify such a metainformation not only at build-time, but also run-time. A key point is a counterpart in newconfig of devclass_add_driver(9) and device_add_child(9) of new-bus. It is not still implemented, but we eventually will implement. (may be soon) -- furuta@sra.co.jp (Atsushi Furuta) Advanced Technology Group. Software Research Associates, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 20:48:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21244 for freebsd-current-outgoing; Tue, 15 Dec 1998 20:48:46 -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 UAA21239 for ; Tue, 15 Dec 1998 20:48:45 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA03988; Tue, 15 Dec 1998 20:45:59 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpddR3986; Wed Dec 16 04:45:54 1998 Message-ID: <36773AFE.4487EB71@whistle.com> Date: Tue, 15 Dec 1998 20:45:50 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: mjacob@feral.com CC: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Variable Mode as default References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > I'm still processing and munching on the responses from the last call on > this- but closure is pretty close- in the interim, here's one that should > be less controversial: > > + forcing variable mode for tape devices unless quirked otherwise > > Do people have an opinion on this? In my original tape driver the default was not fixed, but rather, depended on a heuristic.. Most formats (e.g. QIC) in those days used a fixed mode, though variable mode was becoming more common. (as it had been originally in the 1/2 inch days) If you look in st.c (in 2.2) you should still see the heuristic code that decides which is the most likely default to use. Certainly it depended on the reported format of the drive. Ultimatly if there is a quirk for the drive you allow that to over-ride the default and a user can over-ride the quirk. You should ask the drive immediatly when asked to set a density, and return an error if the drive is not co-operative. I selected 4 sub devices for the tape driver to allow 4 easily available preselected modes and formats. I found this a great thing when presented with a drive that could do several formats or densities. I just used different subdevices to write the density I required. I presume you have looked at st.c in the old scsi system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 20:54:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21649 for freebsd-current-outgoing; Tue, 15 Dec 1998 20:54:58 -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 UAA21641 for ; Tue, 15 Dec 1998 20:54:55 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA04203 for ; Wed, 16 Dec 1998 15:24:41 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id PAA63700; Wed, 16 Dec 1998 15:24:43 +1030 (CST) Message-ID: <19981216152443.B59411@freebie.lemis.com> Date: Wed, 16 Dec 1998 15:24:43 +1030 From: Greg Lehey To: FreeBSD current users Subject: make install breaks in examples/portal Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG install -c -o root -g wheel -m 644 portal/README /usr/share/examples/portal/README install: /usr/share/examples/portal/README: No such file or directory *** Error code 71 (continuing) install -c -o root -g wheel -m 644 portal/portal.conf /usr/share/examples/portal/portal.conf install: /usr/share/examples/portal/portal.conf: No such file or directory *** Error code 71 (continuing) (the continuing was because of the -k option to make install) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 20:59:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA22454 for freebsd-current-outgoing; Tue, 15 Dec 1998 20:59:16 -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 UAA22447 for ; Tue, 15 Dec 1998 20:59:14 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA04207; Tue, 15 Dec 1998 20:53:19 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdRN4203; Wed Dec 16 04:53:15 1998 Message-ID: <36773CB7.52BFA1D7@whistle.com> Date: Tue, 15 Dec 1998 20:53:11 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Alfred Perlstein CC: Oleg Ogurok , freebsd-current@FreeBSD.ORG Subject: Re: /ports/mbone/speakfreely - can't compile. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > this should be posted to ports@freebsd.org, however > > David G recently added a syscall to 3.0, 'sendfile' the point of it is to > send a file through a socket with as little overhead as possible. > > This is really nifty but certain newer interfaces for freebsd syscalls and > freebsd specific library calls are really going to cause C namespace > problems. > > I wish someone would take this into consideration when adding new > functionality. > The name for this syscall was decided by HP in HPUX It has been copied by linux, BSD and soon SUN and SGI. I suggest that any programs on the net that use 'sendfile' as a symbol will very rapidly be changed to not do so... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 21:00:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22583 for freebsd-current-outgoing; Tue, 15 Dec 1998 21:00:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22578 for ; Tue, 15 Dec 1998 21:00:38 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA62002; Tue, 15 Dec 1998 21:00:24 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Dec 1998 21:00:24 -0800 (PST) From: Matthew Dillon Message-Id: <199812160500.VAA62002@apollo.backplane.com> To: Greg Lehey Cc: FreeBSD current users Subject: Re: make install breaks in examples/portal References: <19981216152443.B59411@freebie.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ach. My fault. I forgot to add the mtree entry for portal. -Matt :install -c -o root -g wheel -m 644 portal/README /usr/share/examples/portal/README :install: /usr/share/examples/portal/README: No such file or directory :*** Error code 71 (continuing) :install -c -o root -g wheel -m 644 portal/portal.conf /usr/share/examples/portal/portal.conf :install: /usr/share/examples/portal/portal.conf: No such file or directory :*** Error code 71 (continuing) : :(the continuing was because of the -k option to make install) : :Greg :-- :See complete headers for address, home page and phone numbers :finger grog@lemis.com for PGP public key : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 21:14:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23483 for freebsd-current-outgoing; Tue, 15 Dec 1998 21:14:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23478 for ; Tue, 15 Dec 1998 21:14:43 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id VAA22429; Tue, 15 Dec 1998 21:14:37 -0800 (PST) Date: Tue, 15 Dec 1998 21:14:37 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199812160514.VAA22429@math.berkeley.edu> To: grog@lemis.com Subject: Re: Tape Driver Changes Proposed: Tape Early Warning Behaviour Cc: dan@math.berkeley.edu, freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One good reason for restricting the minor number format is that 16384 > > (i.e. 2^14) different entries for tape devices in /dev would be painful > > beyond belief. > > You wouldn't automatically create all device nodes, just those that > corresponded to real devices and their functions. There are too many of those, even for real devices. For example, the Archive viper 150 could write in 4 different "densities" and at two different speeds. When we throw in auto-rewind and auto-unload on close control, we need 32 different tape devices for which we cannot remember all the names. We might also need another 32 special files for the block devices. (Remember those? They have fallen out of favor and are not always implemented these days, but the concept is still valid.) In practice, we won't be able to have a different entry in /dev/MAKEDEV for each model of tape drive. We will have to use a single scsi tape entry that handles the worst case. The worst case should handle 8 densities, 4 speeds, 4 compression algorithms, auto-rewind, auto-unload, and any other such feature that we might want in the future (e.g. auto-double-eof-mark on close). That amounts to 1024 special files so far. If we were to follow this design philosophy to its logical conclusion, we would also have to specify the tape block size via minor device number (perhaps another 16 bits). > > > I claim that the idea of specifying tape drive operating parameters > > via minor device number was a really bad idea from almost the very > > beginning (unix v6 I believe) and should have been abandoned after > > the ioctl() system call became available. > > How would you tell tar to make a backup, this time only, which didn't > compress? If you did it with mt(1), how would you ensure that nobody > dicked with the settings between your running mt(1) and tar(1)? I would create a mechanism by which a tape drive had to be "allocated" to a particular user before the drive could be used. The allocation process would place the drive in a standard state. Only the user to whom the drive was allocated could change its settings. I implemented such a scheme about 20 years ago and it worked pretty well. There were some additional rules: 1) Any user could reallocate the drive to himself provided that the drive was not open, it didn't have any media loaded, and the current owner of the drive didn't have any processes running. 2) Root could do anything. 3) There is probably more that I don't remember. Implementation was almost trivial. Drive ownership was implemented by setting the owner/group of the special file(s). The program that did drive allocation was a very simple thing that ran setuid root. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 21:20:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24030 for freebsd-current-outgoing; Tue, 15 Dec 1998 21:20:25 -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 VAA24021 for ; Tue, 15 Dec 1998 21:20:22 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id QAA14070 for current@freebsd.org; Wed, 16 Dec 1998 16:33:09 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812160533.QAA14070@cimlogic.com.au> Subject: Kernel module syscall inconsistencies To: current@FreeBSD.ORG Date: Wed, 16 Dec 1998 16:33:09 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ I'm new to kernel modules. ] kldload() can be passed a kernel module filename with path and the kernel links the module as expected, stripping the path and assigning the module name to just foo.ko (instead of ../../foo.ko or /somepath/somewhere/foo.ko). kldfind(), on the otherhand, wants just the module name after the kernel has silently stripped the path. I was expecting to format a string containing the explicit filename I wanted to load (under test, before any eventual installation on /modules), call kldfind to see if the module was already loaded and if not, pass the same string to kldload(). This code results in *lots* of copies of the same module getting loaded -- until I noticed, that is. I think kldfind() should accept the string with the path and behave like kldload() does. And kldload() shouldn't allow more than one module of a particular name. Comments? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 21:55:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27264 for freebsd-current-outgoing; Tue, 15 Dec 1998 21:55:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27259 for ; Tue, 15 Dec 1998 21:55:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA75083; Tue, 15 Dec 1998 21:54:28 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Dec 1998 21:54:28 -0800 (PST) From: Matthew Dillon Message-Id: <199812160554.VAA75083@apollo.backplane.com> To: Chuck Robey Cc: Mike Smith , freebsd-current@FreeBSD.ORG, John Birrell , forrie@forrie.com Subject: Re: FreeBSD Buildworld fails References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :But the reasons for keeping tcl _out_ of the main systems are a heck of :a lot larger than those for perl. Unfortunately, the tcl folks :seemingly care very little about maintaining backwards compatibility, :and many tcl tools require their own specific version of tcl/tk to run. :That's been a major problem with tcl, and I don't quite understand why :those folks can't see that. It certainly would have made tcl the ideal :language, if they'd just cared a little more about not constantly :turning tcl apps into legacy apps. I would just like to add that I have several TCL/TK projects and what Chuck is saying is 100% absolutely true. Porting between releases is a nightmare. Not only that, but tcl/tk-8 is unstable. If we were to make tcl part of the base release, it would be a disaster every time a new version came out. Maybe they've fixed their memory corruption problems, but... :Chuck Robey | Interests include any kind of voice or data Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 22:56:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02205 for freebsd-current-outgoing; Tue, 15 Dec 1998 22:56:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02199 for ; Tue, 15 Dec 1998 22:56:30 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id WAA09566; Tue, 15 Dec 1998 22:56:14 -0800 Date: Tue, 15 Dec 1998 22:56:14 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Julian Elischer cc: freebsd-current@FreeBSD.ORG Subject: Re: Tape Driver Changes Proposed: Variable Mode as default In-Reply-To: <36773AFE.4487EB71@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes- I saw this code. In fact, it was someone's comment about the behaviour changing post-CAM that got me to thinking about this again. What's actually happening now is that whatever the drive shows up as is what it starts as. There are variant behaviours, for example, for different f/w versions of Exabyte f/w that have it show up in fixed or variable mode. When I did the tape driver for Sun, I also used type && and tried to infer from density code if I didn't know the type by name to set things like ST_REEL or ST_QIC, etc.. the trouble is that w/o media inserted, or a lot of the rest of the time you only get 'default' density reported. So rather than having to enumerate all known drives as to whether they should come up in fixed or variable, it seems to me that a slightly more agressive leaning toward a default behaviour (variable) seemes appropriate now. In the current prototype, btw., if the guessed choice fails (e..g, attempting to set variable for an Archive Viper (QIC-24(read)/QIC-120/QIC-150)), the driver will flip back to the other. Yes, as in your original code, there should be both QUIRK_VARIABLE and QUIRK_FIXED. And, also like your original I believe, you set variable/blocksize as well as density and compression at tape mount time (since you can't change these things past BOT (usually) anyway)). Insofar as the subdevices go- I lean multiple ways on this. Thanks for responding, Julian- it's good perspective to see what's been done before here. -matt On Tue, 15 Dec 1998, Julian Elischer wrote: > Matthew Jacob wrote: > > > > I'm still processing and munching on the responses from the last call on > > this- but closure is pretty close- in the interim, here's one that should > > be less controversial: > > > > + forcing variable mode for tape devices unless quirked otherwise > > > > Do people have an opinion on this? > > In my original tape driver the default was not fixed, but rather, > depended on a heuristic.. > > Most formats (e.g. QIC) in those days used a fixed mode, though > variable mode was becoming more common. (as it had been originally > in the 1/2 inch days) > > If you look in st.c (in 2.2) you should still see > the heuristic code that decides which is the most likely default > to use. Certainly it depended on the reported format of the drive. > > Ultimatly if there is a quirk for the drive you allow that to over-ride > the default and a user can over-ride the quirk. > > You should ask the drive immediatly when asked to set a density, > and return an error if the drive is not co-operative. > > I selected 4 sub devices for the tape driver to allow 4 > easily available preselected modes and formats. I found this a great > thing when presented with a drive that could do several formats > or densities. I just used different subdevices to write the density > I required. > > I presume you have looked at st.c in the old scsi system. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 15 23:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03849 for freebsd-current-outgoing; Tue, 15 Dec 1998 23:17:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03843 for ; Tue, 15 Dec 1998 23:17:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id XAA46043; Tue, 15 Dec 1998 23:17:02 -0800 (PST) To: Chuck Robey cc: Mike Smith , freebsd-current@FreeBSD.ORG, John Birrell , forrie@forrie.com Subject: Re: FreeBSD Buildworld fails In-reply-to: Your message of "Tue, 15 Dec 1998 22:19:07 EST." Date: Tue, 15 Dec 1998 23:17:01 -0800 Message-ID: <46039.913792621@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OTOH, perl seems to have just one _really_ incompatible step, going from > the very old 4.036 to the more recent 5.* versions. I don't split the Unfortunately, as I'm now coming to understand, make that 2 highly incompatible steps. 4.036 to 5.004 and 5.004 to 5.005 (which we now use). Yes, that's correct, a bunch of stuff broke in the land of perl when 5.005 came out, some of which is currently causing a good deal of grief to folks like Intel. I've tried to talk them through the process of building a perl-less 3.0 which they can then add their own pre-5.005 version of perl to, but apparently this job is causing them more hassle than I expected it to. I guess our source building tools aren't for everyone. :( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 00:12:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08755 for freebsd-current-outgoing; Wed, 16 Dec 1998 00:12:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08750 for ; Wed, 16 Dec 1998 00:11:55 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem24.masternet.it [194.184.65.34]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id JAA09348; Wed, 16 Dec 1998 09:11:12 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <199812160811.JAA09348@scotty.masternet.it> From: "Gianmarco Giovannelli" To: NAKAGAWA Yoshihisa Date: Wed, 16 Dec 1998 09:19:31 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: PAO Integration? Reply-to: gmarco@giovannelli.it CC: current@FreeBSD.ORG In-reply-to: <199812160250.LAA03052@chandra.eatell.msr.prug.or.jp> References: Your message of "Tue, 15 Dec 1998 04:31:37 PST." <199812151231.EAA05213@dingo.cdrom.com> X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike, new-bus is good; but "newconfig" is also good, I > think. Until now, same purpose drivers stand side by side in > FreeBSD. (example, Voxware and Luigi's new audio driver, BSD ATM > and HARP, ...) > > "new-bus" and "newconfig", I think same relation. Choose by users. > Hello, I am not a programmer but I'd like to express my humble opinion. I think in this way we have a dispersion of resources. Surely we can have both, but perhaps in the double time we can have one, which works, if both party cooperate to a single project. Voxware and Luigi's drivers aren't in this situation, as I know, the first is not developed anymore. Thanks for attention. Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 00:50:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12456 for freebsd-current-outgoing; Wed, 16 Dec 1998 00:50:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12444 for ; Wed, 16 Dec 1998 00:50:52 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id JAA11663; Wed, 16 Dec 1998 09:50:08 +0100 (CET) Received: from wurzelausix (quadratix.cs.uni-sb.de [134.96.222.2]) by cs.uni-sb.de (8.9.1a/1998121400) with ESMTP id JAA26897; Wed, 16 Dec 1998 09:50:08 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:SCQlP124HW7hAyHp37NZkjziV1ArHcfA@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id JAA28103; Wed, 16 Dec 1998 09:50:04 +0100 (CET) Message-Id: <199812160850.JAA28103@wurzelausix> Date: Wed, 16 Dec 1998 09:50:01 +0100 (CET) From: Alexander Leidinger Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? To: dillon@apollo.backplane.com cc: current@FreeBSD.ORG In-Reply-To: <199812151735.SAA22946@wurzelausix> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Dec, To: dillon@apollo.backplane.com wrote: > Ok, works here (testet with nfs ro and local rw, no freebsd.cf in > src/etc/sendmail). Now I have found the problem: mergemaster (script from ports/sysutils, revision 1.17) It creates /usr/src/sendmail/freebsd.cf. (Is the author listening?) Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 01:07:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13638 for freebsd-current-outgoing; Wed, 16 Dec 1998 01:07:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA13633 for ; Wed, 16 Dec 1998 01:07:52 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id RAA00616; Wed, 16 Dec 1998 17:38:20 +0900 (JST) Message-Id: <199812160838.RAA00616@chandra.eatell.msr.prug.or.jp> To: gmarco@giovannelli.it cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 16 Dec 1998 09:19:31 +0100." <199812160811.JAA09348@scotty.masternet.it> Date: Wed, 16 Dec 1998 17:38:19 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think in this way we have a dispersion of resources. > Surely we can have both, but perhaps in the double time we can have one, > which works, if both party cooperate to a single project. It is correct, But already exist two project, "newconfig" and "new-bus". Not yet agree integration of two projects. Already working "newconfig" people and "new-bus" people, in separate. Integrate effort is good; However, we can't integrate if "new-bus" people don't make a compromise. So, for a little while, we will work in separate. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 01:38:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15940 for freebsd-current-outgoing; Wed, 16 Dec 1998 01:38:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15924; Wed, 16 Dec 1998 01:38:50 -0800 (PST) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id KAA12018; Wed, 16 Dec 1998 10:38:21 +0100 (CET) Received: from cs.uni-sb.de (acc1-220.telip.uni-sb.de [134.96.113.220]) by cs.uni-sb.de (8.9.1a/1998121400) with ESMTP id KAA27414; Wed, 16 Dec 1998 10:38:21 +0100 (CET) Message-ID: <36778044.A8FDC865@cs.uni-sb.de> Date: Wed, 16 Dec 1998 10:41:24 +0100 From: "D. Rock" X-Mailer: Mozilla 4.5 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: Matthew Dillon CC: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: kmem, tty, bind security enhancements commit. References: <199812010551.VAA02953@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon schrieb: > > (2) > > Add a 'bind' user and a 'bind' group to master.passwd > > Use bind-8's -u and -g features to run named as bind:bind > in the default rc.conf: > > named_flags="-u bind -g bind" > > (Or find a way to figure out whether this uid/gid exists > and use the options or not use the options based on that, > which is more compatible with prior installations but adds > complexity that will quickly become stale. I suggest simply > making it the default in the CVS tree). > > Cavet: in a multi-interface situation, with an interface > that is brought up later, and so forth, named will not > be able to automatically rebind and must be restarted. > > (Also ensure that named.conf is either group-bind-readable or > world readable). Only a small glitch: % ndc reload now gives you everytime an named[24812]: couldn't create pid file '/var/run/named.pid' error message to syslog. It isn't a big deal, because on reload the pid doesn't change. But it's still annoying. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 01:55:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17261 for freebsd-current-outgoing; Wed, 16 Dec 1998 01:55:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17255 for ; Wed, 16 Dec 1998 01:55:44 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA59096; Wed, 16 Dec 1998 09:54:04 GMT Date: Wed, 16 Dec 1998 09:54:04 +0000 (GMT) From: Doug Rabson To: Atsushi Furuta cc: mike@smith.net.au, y-nakaga@nwsl.mesh.ad.jp, current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812160444.NAA07797@sramhc.sra.co.jp> 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, 16 Dec 1998, Atsushi Furuta wrote: > >> In article <199812160417.UAA00907@dingo.cdrom.com>, > Mike Smith writes: > > > If you haven't even looked at the issues involved in dynamic growth of > > the newconfig-generated device and bus tree, then I'd have to strongly > > suggest that you're wasting your effort right now. > > Of cource, *our* newconfig will be support dynamic growth of the > device instance tree and device directed graph. Actually, I have > changed from cfdata structure array to TAILQ. Please look at our > repository... > > > Drivers required for the boot process need to be aggregated at either > > build-time or load-time (console, root disk), and they can either be > > statically or dynamically configured - static configuration is optional > > and only required if the driver or its parend bus can't work things out > > itself. > > I have a different opinion. As noted by Doug, current implementation > of new-bus requires config(8) to specify ivars. It is not fair to say > "newconfig is static, but new-bus is dynamic" without dynamic > parameter specification. As things stand right now, the only bus which uses (needs) static configuration is the ISA bus. The existing implementation of ISA bus on the alpha platform picks up values for ivars from a simple 'resource' database constructed by config(8). Given that we can easily load arbitrary files using the new bootstrap, this information could be read from a file. I chose to use config(8) to supply the information since that would be most familiar to users of FreeBSD/i386 (and at the time, the new bootstrap wasn't anywhere near as sophisticated as it is now). The best approach for the future may be to supply all configuration data from files loaded by the bootstrap and reduce config(8) to simply constructing the build directory and building a Makefile. > > > The metainformation required to connect devices and busses is almost > > entirely contained in the drivers themselves, rather than being > > constructed at build-time by an extern configuration tool. This is > > more or less mandatory if you want to be able to add arbitrary bus and > > device code to a running system, and one of the major marks against > > newconfig. > > Our newconfig will be able to specify such a metainformation not > only at build-time, but also run-time. A key point is a counterpart > in newconfig of devclass_add_driver(9) and device_add_child(9) of > new-bus. It is not still implemented, but we eventually will > implement. (may be soon) I don't want to spend any time matching features of the two different systems (which is why I have stayed away from this thread mostly). I do think that sharing drivers between the two implementations is possible. Its certainly easy to port from newconfig to new-bus and the usb folks are maintaining a common source tree between NetBSD and FreeBSD. A far more important feature for sharing driver source code between the systems is the use of bus_space and bus_dma for accessing device hardware and this is fully supported in FreeBSD since the CAM integration effort. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 02:42:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22301 for freebsd-current-outgoing; Wed, 16 Dec 1998 02:42:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22293 for ; Wed, 16 Dec 1998 02:42:29 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id LAA01904; Wed, 16 Dec 1998 11:42:25 +0100 (MET) Date: Wed, 16 Dec 1998 11:41:43 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Doug Rabson cc: Atsushi Furuta , mike@smith.net.au, y-nakaga@nwsl.mesh.ad.jp, current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't want to spend any time matching features of the two different > systems (which is why I have stayed away from this thread mostly). I do > think that sharing drivers between the two implementations is possible. > Its certainly easy to port from newconfig to new-bus and the usb folks are > maintaining a common source tree between NetBSD and FreeBSD. I suggest we have a brainstorm on what would be needed to get people working together quickly to make sure we end up somewhere in january. Could someone from the PAO group come up with a list of features that is 'not available' in the new-bus architecture, that they would like to see? It seems to me that a number of people are very sure about the fact that new-bus is the way to go, so we should start integrating those features if necessary. Personally, I am very much interested in getting the PCMCIA sorted on my laptop. 3.0-CURRENT seem to make ep0 go haywire once in a while. > A far more important feature for sharing driver source code between the > systems is the use of bus_space and bus_dma for accessing device hardware > and this is fully supported in FreeBSD since the CAM integration effort. This indeed is a more important problem. UHCI and OHCI USB host controllers both have the register access specified in the specs, so it is not a problem for the USB device drivers in particular. As for the driver porting: Please have a look at dev/usb/ugen.c file to see the differences between NetBSD and FreeBSD. They are trivial (when porting from NetBSD to FreeBSD, the other way around requires some more work as you will have to create a number of files to bind the driver into the tree of devices). Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 04:31:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05613 for freebsd-current-outgoing; Wed, 16 Dec 1998 04:31:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA05561 for ; Wed, 16 Dec 1998 04:30:51 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id LAA10430; Wed, 16 Dec 1998 11:17:48 +0100 From: Luigi Rizzo Message-Id: <199812161017.LAA10430@labinfo.iet.unipi.it> Subject: Re: IPFW screwed up? To: brian@CSUA.Berkeley.EDU (Brian W. Buchanan) Date: Wed, 16 Dec 1998 11:17:47 +0100 (MET) Cc: forrie@forrie.com, freebsd-current@FreeBSD.ORG In-Reply-To: from "Brian W. Buchanan" at Dec 15, 98 02:58:20 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 15 Dec 1998, Forrest Aldrich wrote: > > > Something's really wrong with ipfw... this is what my rules end up looking > > like, and no changes have ever been made: > > Are your kernel and /sbin/ipfw in sync? It appears that some changes have > been made to the ipfw userland<->kernel interface. correct -- the recent inclusion of dummynet requires one to recompile ipfw. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 04:39:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06641 for freebsd-current-outgoing; Wed, 16 Dec 1998 04:39:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06634; Wed, 16 Dec 1998 04:39:03 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id NAA00529; Wed, 16 Dec 1998 13:38:51 +0100 (CET) (envelope-from des) To: "D. Rock" Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: kmem, tty, bind security enhancements commit. References: <199812010551.VAA02953@apollo.backplane.com> <36778044.A8FDC865@cs.uni-sb.de> From: Dag-Erling Smorgrav Date: 16 Dec 1998 13:38:51 +0100 In-Reply-To: "D. Rock"'s message of "Wed, 16 Dec 1998 10:41:24 +0100" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "D. Rock" writes: > Only a small glitch: > % ndc reload > now gives you everytime an > named[24812]: couldn't create pid file '/var/run/named.pid' > error message to syslog. > It isn't a big deal, because on reload the pid doesn't change. But > it's still annoying. There are worse glitches. Interface scanning no longer works, and cache dumping no longer works unless you create a directory writeable by bind and configure named to use that. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 05:53:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15891 for freebsd-current-outgoing; Wed, 16 Dec 1998 05:53:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15884 for ; Wed, 16 Dec 1998 05:53:05 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id HAA11221; Wed, 16 Dec 1998 07:52:56 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812161352.HAA11221@ns.tar.com> From: "Richard Seaman, Jr." To: "Archie Cobbs" Cc: "current@FreeBSD.ORG" Date: Wed, 16 Dec 98 07:52:55 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Linux Threads patches available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Dec 1998 15:57:35 -0800 (PST), Archie Cobbs wrote: >Richard Seaman, Jr. writes: >> Earlier I offered >> to try to implement a "one-to-one" kernel threads library by extending >> the current pthreads code, but almost all the comments I received were >> that people wanted something other than one-to-one kernel threads. >> This was beyond my capabilities and interest. > >Forgive me if I don't completely understand, but... You probably understand it all better than I do. I'm still learning :) >It seems that if the one-to-one implementation were layered the >right way, it would be easy to add a 'shim' layer (later on) that >converts it into a many-to-many version of the same thing. As I posted a while back, a lot of the existing FreeBSD pthreads code could be made "generic", interfacing to just a few functions in what you refer to as the "shim layer". However, each time I've tried to design what these functions should look like, I end up concluding that a decision needs to be make about the design of the threads implementation(s) the "shim layer" would be dealing with. Since I'm not sure what the design of a "many to many" threads would look like, I've put off the project. >In other words, can't you localize the operation 'give me a new >context' to a single place in the code, which to start with always >creates a kernel thread, but later can do some more intelligent >thread management? Sure. Actually, this part of the existing pthreads code is already pretty localized, and could be made somewhat more so. My problem in designing generic pthreads code revolves around a few issues that might vary greatly depending on how the threads are implemented. These include: 1) How do you handle syscall blocking? I'd guess that 50-75% of the existing pthreads code is dedicated to dealing with syscall blocking. If we can know for sure what the "many to many" implementation will do, then coding the pthreads code for either a "one to one" or a "many to many" can proceed logically. 2) How will thread sleep/wakeup (or in linux suspend/restart) be implemented? How will the code handle the "lost wakeup" problem that potentially exists in the mutex and cond routines? How will the sleep/wakeup routines deal with thread cancellation? 3) How will thread cancellation be implemented? 4) What will the signal handling code look like? Will signals be used in the sleep/wakeup routines, in thread cancellation, or for thread preemption? Where is signal delivery handled (kernel vs. user or mixed) in the many/many case? Will signal handling be fully posix compliant, and what additional kernel changes will be made to get us there? 5) How is pthread_exit and thread cleanup processing handled? And, a related question, where is thread creation handled? Does one have a "thread manager thread" that is the parent of every kernel thread entity? There are other issues, but these strike me as the main ones. There are solutions to all these issues, but each time I look at them, I feel the need to design the "many-many" implementation first before proceeding. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 06:01:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17316 for freebsd-current-outgoing; Wed, 16 Dec 1998 06:01:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17311 for ; Wed, 16 Dec 1998 06:01:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id GAA48643 for ; Wed, 16 Dec 1998 06:00:37 -0800 (PST) To: current@FreeBSD.ORG Subject: disklabel baggage. Date: Wed, 16 Dec 1998 06:00:36 -0800 Message-ID: <48639.913816836@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm considering the following changes to disklabel(8), keeping in mind that nothing will prevent the -b and -s flags from overriding these new defaults. Comments? Index: disklabel.8 =================================================================== RCS file: /home/ncvs/src/sbin/disklabel/disklabel.8,v retrieving revision 1.9 diff -u -u -r1.9 disklabel.8 --- disklabel.8 1998/11/28 09:43:31 1.9 +++ disklabel.8 1998/12/16 13:42:10 @@ -251,25 +251,19 @@ the secondary boot program. If the names are not explicitly given, standard boot programs will be used. The boot programs are located in -.Pa /usr/mdec . +.Pa /boot . The names of the programs are taken from the ``b0'' and ``b1'' parameters of the .Xr disktab 5 entry for the disk if .Ar disktype was given and its disktab entry exists and includes those parameters. -Otherwise, boot program names are derived from the name of the disk. -These names are of the form -.Pa basename Ns boot -for the primary (or only) bootstrap, and -.Pf boot Pa basename -for the secondary bootstrap; -for example, -.Pa /usr/mdec/daboot +Otherwise, the default boot image names are used, these being: +.Pa /boot/boot1 and -.Pa /usr/mdec/bootda -if the disk device is -.Em da0 . +.Pa /boot/boot2 +for the standard stage1 and stage2 boot images (details may vary +on architectures like the Alpha, where only a single-stage boot is used). .Pp The first of the three boot-installation forms is used to install bootstrap code without changing the existing label. @@ -281,8 +275,8 @@ .Sh FILES .Bl -tag -width Pa -compact .It Pa /etc/disktab -.It Pa /usr/mdec/ Ns Em xx Ns boot -.It Pa /usr/mdec/boot Ns Em xx +.It Pa /boot/ +.It Pa /boot/boot .El .Sh EXAMPLES .Dl disklabel da0 @@ -318,9 +312,9 @@ .Pp Install a new bootstrap on da0. The boot code comes from -.Pa /usr/mdec/daboot +.Pa /boot/boot1 and possibly -.Pa /usr/mdec/bootda . +.Pa /boot/boot2 . On-disk and in-core labels are unchanged. .Pp .Dl disklabel -w -B /dev/rda0c -b newboot da2212 @@ -329,7 +323,7 @@ The label is derived from disktab information for ``da2212'' and installed both in-core and on-disk. The bootstrap code comes from the file -.Pa /usr/mdec/newboot . +.Pa /boot/newboot . .Sh SEE ALSO .Xr disklabel 5 , .Xr disktab 5 Index: disklabel.c =================================================================== RCS file: /home/ncvs/src/sbin/disklabel/disklabel.c,v retrieving revision 1.23 diff -u -u -r1.23 disklabel.c --- disklabel.c 1998/10/23 18:57:39 1.23 +++ disklabel.c 1998/12/16 13:53:20 @@ -595,25 +595,13 @@ *np++ = '\0'; if (!xxboot) { - (void)sprintf(np, "%s/%sboot", - _PATH_BOOTDIR, dkbasename); - if (access(np, F_OK) < 0 && dkbasename[0] == 'r') - dkbasename++; - xxboot = np; - (void)sprintf(xxboot, "%s/%sboot", - _PATH_BOOTDIR, dkbasename); - np += strlen(xxboot) + 1; + (void)sprintf(boot0, "%s/boot1", _PATH_BOOTDIR); + xxboot = boot0; } #if NUMBOOT > 1 if (!bootxx) { - (void)sprintf(np, "%s/boot%s", - _PATH_BOOTDIR, dkbasename); - if (access(np, F_OK) < 0 && dkbasename[0] == 'r') - dkbasename++; - bootxx = np; - (void)sprintf(bootxx, "%s/boot%s", - _PATH_BOOTDIR, dkbasename); - np += strlen(bootxx) + 1; + (void)sprintf(boot1, "%s/boot2", _PATH_BOOTDIR); + bootxx = boot1; } #endif } Index: pathnames.h =================================================================== RCS file: /home/ncvs/src/sbin/disklabel/pathnames.h,v retrieving revision 1.1.1.1 diff -u -u -r1.1.1.1 pathnames.h --- pathnames.h 1994/05/26 06:34:01 1.1.1.1 +++ pathnames.h 1998/12/16 13:42:28 @@ -35,6 +35,6 @@ #include -#define _PATH_BOOTDIR "/usr/mdec" +#define _PATH_BOOTDIR "/boot" #undef _PATH_TMP #define _PATH_TMP "/tmp/EdDk.aXXXXXX" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 06:34:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21255 for freebsd-current-outgoing; Wed, 16 Dec 1998 06:34:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21250; Wed, 16 Dec 1998 06:34:15 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from atelier.acadiau.ca (atelier.acadiau.ca [131.162.138.103]) by garlic.acadiau.ca (8.8.5/8.8.5) with ESMTP id KAA11222; Wed, 16 Dec 1998 10:34:04 -0400 (AST) Date: Wed, 16 Dec 1998 10:34:39 -0400 (AST) From: "Marc G. Fournier" To: freebsd-scsi@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: any way of gleaming info from these? 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 vnode_pager_putpages: residual I/O 4096 at 113 vnode_pager_putpages: I/O error 6 vnode_pager_putpages: residual I/O 4096 at 113 vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 vnode_pager_putpages: I/O error 6 vnode_pager_putpages: residual I/O 4096 at 113 maybe its totally impossible, but is there no way of detailing which drive is causing this? or is it not a drive? Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 06:48:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23199 for freebsd-current-outgoing; Wed, 16 Dec 1998 06:48:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23193; Wed, 16 Dec 1998 06:47:58 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id GAA09727; Wed, 16 Dec 1998 06:48:06 -0800 (PST) Message-Id: <199812161448.GAA09727@root.com> To: "Marc G. Fournier" cc: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: any way of gleaming info from these? In-reply-to: Your message of "Wed, 16 Dec 1998 10:34:39 -0400." From: David Greenman Reply-To: dg@root.com Date: Wed, 16 Dec 1998 06:48:06 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >vnode_pager_putpages: residual I/O 4096 at 113 >vnode_pager_putpages: I/O error 6 >vnode_pager_putpages: residual I/O 4096 at 113 >vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 >vnode_pager_putpages: I/O error 6 >vnode_pager_putpages: residual I/O 4096 at 113 > >maybe its totally impossible, but is there no way of detailing which drive >is causing this? or is it not a drive? Error 6 is ENXIO - device not configured. This might happen if the device is SCSI and it loses power/goes offline. I can't think of any other reasons offhand. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 07:46:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29627 for freebsd-current-outgoing; Wed, 16 Dec 1998 07:46:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29612 for ; Wed, 16 Dec 1998 07:46:10 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:7zgSHrsgFwFAnVUoFy4NV+Ub8iwKgIRm@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id RAA05300; Wed, 16 Dec 1998 17:45:58 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:TNheFlqTodvsNp6H1BfpLaVqTndN33O+@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id RAA04870; Wed, 16 Dec 1998 17:45:53 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812161545.RAA04870@greenpeace.grondar.za> To: Mike Smith cc: John Birrell , forrie@forrie.com, freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD Buildworld fails In-Reply-To: Your message of " Tue, 15 Dec 1998 18:23:33 PST." <199812160223.SAA01119@dingo.cdrom.com> References: <199812160223.SAA01119@dingo.cdrom.com> Date: Wed, 16 Dec 1998 17:45:49 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > If we had Tcl in the base system, this would be trivial. I don't want > to use Perl at all - one is simply told that Perl is the be-all and > end-all of hackish scripting languages, but it truly appears to be too > fragile for that. I have developed such a hatred for perl, that I may even be convincable that it get kicked out of the base system. ;-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 07:49:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00164 for freebsd-current-outgoing; Wed, 16 Dec 1998 07:49:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00136 for ; Wed, 16 Dec 1998 07:49:52 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:oOcDkQTHfBM0rd8RQ9vVlczhaCdCP+aI@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id RAA05310; Wed, 16 Dec 1998 17:49:15 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:OH+op32PHStdduzpnGZTm//iCG21bLip@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id RAA04913; Wed, 16 Dec 1998 17:49:13 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812161549.RAA04913@greenpeace.grondar.za> To: "Jordan K. Hubbard" cc: Chuck Robey , Mike Smith , freebsd-current@FreeBSD.ORG, John Birrell , forrie@forrie.com Subject: Re: FreeBSD Buildworld fails In-Reply-To: Your message of " Tue, 15 Dec 1998 23:17:01 PST." <46039.913792621@zippy.cdrom.com> References: <46039.913792621@zippy.cdrom.com> Date: Wed, 16 Dec 1998 17:49:13 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Unfortunately, as I'm now coming to understand, make that 2 highly > incompatible steps. 4.036 to 5.004 and 5.004 to 5.005 (which we now > use). Yes, that's correct, a bunch of stuff broke in the land of perl > when 5.005 came out, some of which is currently causing a good deal of > grief to folks like Intel. I've tried to talk them through the > process of building a perl-less 3.0 which they can then add their own > pre-5.005 version of perl to, but apparently this job is causing them > more hassle than I expected it to. I guess our source building tools > aren't for everyone. :( Can I help the Intel folks in any way? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 07:51:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00560 for freebsd-current-outgoing; Wed, 16 Dec 1998 07:51:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00544; Wed, 16 Dec 1998 07:50:57 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from atelier.acadiau.ca (atelier.acadiau.ca [131.162.138.103]) by garlic.acadiau.ca (8.8.5/8.8.5) with ESMTP id LAA17300; Wed, 16 Dec 1998 11:49:41 -0400 (AST) Date: Wed, 16 Dec 1998 11:50:16 -0400 (AST) From: "Marc G. Fournier" To: David Greenman cc: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: any way of gleaming info from these? In-Reply-To: <199812161448.GAA09727@root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Dec 1998, David Greenman wrote: > >vnode_pager_putpages: residual I/O 4096 at 113 > >vnode_pager_putpages: I/O error 6 > >vnode_pager_putpages: residual I/O 4096 at 113 > >vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 > >vnode_pager_putpages: I/O error 6 > >vnode_pager_putpages: residual I/O 4096 at 113 > > > >maybe its totally impossible, but is there no way of detailing which drive > >is causing this? or is it not a drive? > > Error 6 is ENXIO - device not configured. This might happen if the device > is SCSI and it loses power/goes offline. I can't think of any other reasons > offhand. Hrmmm...is vnode_pager_putpages a 'file system' error, or a 'swap' error? The system is locked up right now, awaiting someone to get down to the office and reboot it. Looking through /usr/src/sys, the error message is generated in vm/vnode_pager.c...which, to me, would indicate swap space? Is there no way of adding in the name of the device generating this error to the error message? Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 07:51:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00591 for freebsd-current-outgoing; Wed, 16 Dec 1998 07:51:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00577 for ; Wed, 16 Dec 1998 07:51:06 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id PAA11649; Wed, 16 Dec 1998 15:51:00 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma011639; Wed, 16 Dec 98 15:50:48 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zqJIp-0000QT-00; Wed, 16 Dec 1998 15:55:55 +0000 To: current@FreeBSD.ORG From: Tony Finch Subject: Re: modification to exec in the kernel? Newsgroups: chiark.mail.freebsd.current In-Reply-To: <199812151650.SAA68842@greenpeace.grondar.za> Organization: Deliberate Obfuscation To Amuse Tony References: <19981215120357.B11837@clear.co.nz> <199812142331.RAA17203@home.dragondata.com> <19981215124818.A22526@clear.co.nz> <199812150644.IAA67338@greenpeace.grondar.za> <199812150917.BAA52694@apollo.backplane.com> <19981216053701.B27078@clear.co.nz> <19981216053701.B27078@clear.co.nz> Message-Id: Date: Wed, 16 Dec 1998 15:55:55 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: >Joe Abley wrote: >> So how is this more dangerous than a non-chrooted environment? Surely it >> is _as_ safe - but with the added control that the user sees an appropriate >> subset of the entire filesystem that is controlled, regardless of what the >> system as a whole needs to have installed in order to function? > >You give the user Perl5, you may as well give them a C compiler. >They'll have full access to sockets etc. Who knows what nasty >attacks they can launch against you from inside your own network. I think some sort of firewalling is the answer here. >Given that the chroot'ed environment is "sanitised", it becomes >easy to control (within its limits) and understand. I am not >proposing security-by-obsurity here, just that you either make it >"UNIX" and go with that warts-and-all (security patrols necessary), >or make it tighter than a mouse's arse (and non-useful to >scriptwriters). Depends on the script -- if the only executable you allow the users access to is perl it's still a useful environment. Tony. -- f.a.n.finch.523654357374743743747333764375697569700 fanf@demon.net dot@dotat.at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 08:02:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02551 for freebsd-current-outgoing; Wed, 16 Dec 1998 08:02:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02544 for ; Wed, 16 Dec 1998 08:02:37 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id QAA13175; Wed, 16 Dec 1998 16:02:31 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma013161; Wed, 16 Dec 98 16:02:28 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zqJU7-0000RJ-00; Wed, 16 Dec 1998 16:07:35 +0000 To: current@FreeBSD.ORG From: Tony Finch Subject: Re: modification to exec in the kernel? Newsgroups: chiark.mail.freebsd.current In-Reply-To: <199812151821.KAA56685@apollo.backplane.com> Organization: Deliberate Obfuscation To Amuse Tony References: <19981215120357.B11837@clear.co.nz> <199812142331.RAA17203@home.dragondata.com> <19981215124818.A22526@clear.co.nz> <199812150644.IAA67338@greenpeace.grondar.za> <199812150917.BAA52694@apollo.backplane.com> <19981216053701.B27078@clear.co.nz> Message-Id: Date: Wed, 16 Dec 1998 16:07:35 +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > I don't see the point. Let me put it this way: If you give > the user a non-chrooted environment but do not give the user access > to any suid/sgid programs, how is this different from giving the user > a chroot'd environment without access to any suid/sgid programs? The > only difference that I can think of is access to /tmp. I don't see how > the chroot'd environment is any safer then the non-chroot'd environment. You can throw away a lot of stuff from the chrooted environment and still leave the system useful to the admins. AFAICT breaking root in an environment like this is much more like trying to do so over the network because the machine's services are only accessible in that sort of way. This does assume the integrity of the kernel, though. Tony. -- dxoigmn**f.a.n.finch fanf@demon.net dot@dotat.at To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 08:23:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04932 for freebsd-current-outgoing; Wed, 16 Dec 1998 08:23:11 -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 IAA04913 for ; Wed, 16 Dec 1998 08:22:44 -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.9.1/8.9.1/Netplex) with ESMTP id AAA10511; Thu, 17 Dec 1998 00:20:43 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812161620.AAA10511@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Tony Finch cc: current@FreeBSD.ORG Subject: Re: modification to exec in the kernel? In-reply-to: Your message of "Wed, 16 Dec 1998 16:07:35 GMT." Date: Thu, 17 Dec 1998 00:20:33 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Finch wrote: > Matthew Dillon wrote: > > > > I don't see the point. Let me put it this way: If you give > > the user a non-chrooted environment but do not give the user access > > to any suid/sgid programs, how is this different from giving the user > > a chroot'd environment without access to any suid/sgid programs? The > > only difference that I can think of is access to /tmp. I don't see how > > the chroot'd environment is any safer then the non-chroot'd environment. > > You can throw away a lot of stuff from the chrooted environment and > still leave the system useful to the admins. AFAICT breaking root in > an environment like this is much more like trying to do so over the > network because the machine's services are only accessible in that > sort of way. I've come into this late, I have not seen the original parts of this thread. However, it looks like it might be vaguely related to something I did for somebody ages ago (and is still in use) as a hack to solve a problem at the time. Basically, the objective was to stop users downloading and running random binaries on the systems they had shell access to without those binaries being "blessed". What we did was: - Overload the sticky (t) bit - this was easiest since most things knew of it's existance already, and things like chmod didn't need tweaks. - Users (uid >= 5000) could run any system binary they had access to, or any user binary that hat the sticky bit set. - the "t" bit could be set (by root) on a binary owned by a user. - we were tempted by but didn't use flags since +t was convenient. Basically that stopped people downloading and running things like 20 copies of rc5des, various password cracking programs, IRC bots etc. The determined could run tcl or perl scripts if they wanted to, but nobody ever did. This was implemented^H^H^H^H^H^H^Hhacked in by having kern_exec.c look at the uid of the invoker, the owner uid of the file and whether the +t bit was set. The vfs was (slightly) tweaked to clear the sticky bit if the file was written to. The whole thing wasn't exactly what I'd call clean. It did stop the clueless from doing stupid things, which is what it set out to. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 10:35:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22665 for freebsd-current-outgoing; Wed, 16 Dec 1998 10:35:58 -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 KAA22659 for ; Wed, 16 Dec 1998 10:35:55 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id NAA34944; Wed, 16 Dec 1998 13:33:35 -0500 (EST) Date: Wed, 16 Dec 1998 13:33:34 -0500 (EST) From: Chuck Robey To: Mark Murray cc: Mike Smith , John Birrell , forrie@forrie.com, freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD Buildworld fails In-Reply-To: <199812161545.RAA04870@greenpeace.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Dec 1998, Mark Murray wrote: > Mike Smith wrote: > > If we had Tcl in the base system, this would be trivial. I don't want > > to use Perl at all - one is simply told that Perl is the be-all and > > end-all of hackish scripting languages, but it truly appears to be too > > fragile for that. > > I have developed such a hatred for perl, that I may even be convincable > that it get kicked out of the base system. ;-) Other technically acceptable options exist, including rexx (at least 2 free, actively maintained versions) and ruby (ports/lang/ruby). ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 10:39:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23086 for freebsd-current-outgoing; Wed, 16 Dec 1998 10:39:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23072 for ; Wed, 16 Dec 1998 10:39:12 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id MAA18576 for ; Wed, 16 Dec 1998 12:39:03 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812161839.MAA18576@ns.tar.com> From: "Richard Seaman, Jr." To: "current@freebsd.org" Date: Wed, 16 Dec 98 12:39:02 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Linux Threads patches available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Dec 98 16:41:04 -0600, Richard Seaman, Jr. wrote: >The linux threads patches are available at http://lt.tar.com/ Please note that the installation instructions have been updated if you are installing the "source tree patch". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 10:49:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24297 for freebsd-current-outgoing; Wed, 16 Dec 1998 10:49:27 -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 KAA24292 for ; Wed, 16 Dec 1998 10:49:25 -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 0zqM0Q-0005Yf-00; Wed, 16 Dec 1998 11:49:06 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id LAA19711; Wed, 16 Dec 1998 11:47:36 -0700 (MST) Message-Id: <199812161847.LAA19711@harmony.village.org> To: Mike Smith Subject: Driver config Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 15 Dec 1998 04:14:26 PST." <199812151214.EAA05117@dingo.cdrom.com> References: <199812151214.EAA05117@dingo.cdrom.com> Date: Wed, 16 Dec 1998 11:47:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812151214.EAA05117@dingo.cdrom.com> Mike Smith writes: : You've only used two uniquifiers, the driver name and instance number, : but I'm wondering whether we might not want to support a more general : mechanism where you can specify other uniquifiers for the match. : : eg. : : driver=sio, bus_attribute=removable: powerup_on_open=yes : : This may also be an instance of feeping creaturism... Hmmm. the way that I've seen this overcome in the past is that many things were pushed onto the fetch stack. So that when the aha driver connected to the isa bus unit 0 device.main.isa.aha.unit0.tune_isa would be fetched. The specification would be devices*aha*unit0.tune_isa: 1 And then for the aic driver: device.main.isa.aic.unit0.force_dma device.main.pcmcia.aic.unit0.force_dma To force DMA for differently attached devices. This works well enough in practice, but does lack the flexibility that I see in your stuff. It would likely be easier to implement. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 11:14:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27623 for freebsd-current-outgoing; Wed, 16 Dec 1998 11:14:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27601 for ; Wed, 16 Dec 1998 11:14:34 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA25683; Wed, 16 Dec 1998 19:14:04 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id IAA37602; Wed, 16 Dec 1998 08:11:36 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812160811.IAA37602@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: y-nakaga@nwsl.mesh.ad.jp (NAKAGAWA Yoshihisa), mike@smith.net.au, wollman@khavrinen.lcs.mit.edu, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Tue, 15 Dec 1998 08:42:13 GMT." <199812150842.BAA17883@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Dec 1998 08:11:36 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > Try to name one ting that you could do with "config" that you could > not do with a sufficiently dynamic kernel loadable module framework. [.....] Is it possible to load ``n'' pseudo-devices (without teaching the driver to be dynamic enough to do it itself) ? My kernel config says ``pseudo-device tun 300''.... > Terry Lambert > terry@lambert.org -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 12:01:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02855 for freebsd-current-outgoing; Wed, 16 Dec 1998 12:01:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02846 for ; Wed, 16 Dec 1998 12:01:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA81180; Wed, 16 Dec 1998 12:01:27 -0800 (PST) (envelope-from dillon) Date: Wed, 16 Dec 1998 12:01:27 -0800 (PST) From: Matthew Dillon Message-Id: <199812162001.MAA81180@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: disklabel baggage. References: <48639.913816836@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think it's a good idea to move the boot images from /usr to /, but I don't like the idea of creating a /boot directory. How about /etc/boot/ ? After all, disklabel already references /etc/disktab. Lets keep / as clean as possible. -Matt : :I'm considering the following changes to disklabel(8), keeping in mind :that nothing will prevent the -b and -s flags from overriding these :new defaults. Comments? : :Index: disklabel.8 :=================================================================== :RCS file: /home/ncvs/src/sbin/disklabel/disklabel.8,v :... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 12:07:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03492 for freebsd-current-outgoing; Wed, 16 Dec 1998 12:07:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03480 for ; Wed, 16 Dec 1998 12:07:29 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id MAA16690; Wed, 16 Dec 1998 12:03:37 -0800 (PST) Date: Wed, 16 Dec 1998 12:03:37 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Matthew Dillon cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: disklabel baggage. In-Reply-To: <199812162001.MAA81180@apollo.backplane.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 Amen to this. / is starting to look like a pigpen. On Wed, 16 Dec 1998, Matthew Dillon wrote: > I think it's a good idea to move the boot images from /usr to /, > but I don't like the idea of creating a /boot directory. How > about /etc/boot/ ? After all, disklabel already references /etc/disktab. > Lets keep / as clean as possible. > > -Matt > > : > :I'm considering the following changes to disklabel(8), keeping in mind > :that nothing will prevent the -b and -s flags from overriding these > :new defaults. Comments? > : > :Index: disklabel.8 > :=================================================================== > :RCS file: /home/ncvs/src/sbin/disklabel/disklabel.8,v > :... > > 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 Wed Dec 16 12:45:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07854 for freebsd-current-outgoing; Wed, 16 Dec 1998 12:45:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07846 for ; Wed, 16 Dec 1998 12:45:23 -0800 (PST) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <10724-20085>; Wed, 16 Dec 1998 21:45:01 +0100 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.9.1) with UUCP id UAA01962; Wed, 16 Dec 1998 20:59:47 +0100 (MET) (envelope-from paulz@trantor.stuyts.nl) Received: from trantor.stuyts.nl (localhost [127.0.0.1]) by trantor.stuyts.nl (8.9.1/8.8.5) with ESMTP id UAA31538; Wed, 16 Dec 1998 20:49:41 +0100 (MET) Message-Id: <199812161949.UAA31538@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-reply-to: Your message of "Tue, 15 Dec 1998 17:58:45 PST." <199812160158.RAA00944@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Dec 1998 20:49:41 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I did some testing using the following test program: > > #include > > main() > > { > > int rv; > > rv=open("testfile1",O_CREAT|O_RDWR|O_EXCL,0666); > > if ( rv < 0 ) > > perror("testfile1"); > > rv=open("testfile2",O_CREAT|O_RDWR,0666); > > if ( rv < 0 ) > > perror("testfile2"); > > } > > > > This program results in a file called 'testfile1' being created on the server > > but having the creation of 'testfile2' fail with errno=79 ( which means > > EOVERFLOW 79 /* value too large to be stored in data type */ > > on Solaris ) > > > > If I do a snoop for the create requests sent I se the following request for > > testfile1 : > > RPC: ----- SUN RPC Header ----- > > RPC: > > RPC: Record Mark: last fragment, length = 156 > > RPC: Transaction id = 1478392196 > > RPC: Type = 0 (Call) > > RPC: RPC version = 2 > > RPC: Program = 100003 (NFS), version = 3, procedure = 8 > > RPC: Credentials: Flavor = 1 (Unix), len = 52 bytes > > RPC: Time = 0 > > RPC: Hostname = > > RPC: Uid = 544, Gid = 200 > > RPC: Groups = 200 0 5 14 68 69 70 1000 > > RPC: Verifier : Flavor = 0 (None), len = 0 bytes > > RPC: > > NFS: ----- Sun NFS ----- > > NFS: > > NFS: Proc = 8 (Create file) > > NFS: File handle = [008A] > > NFS: 0080000800000002000A000000000002694370EA000A000000000002694370EA > > NFS: File name = testfile1 > > NFS: Guard = 7F00000103000000 > > NFS: > > > > And the following for testfile2: > > RPC: ----- SUN RPC Header ----- > > RPC: > > RPC: Record Mark: last fragment, length = 192 > > RPC: Transaction id = 1478392200 > > RPC: Type = 0 (Call) > > RPC: RPC version = 2 > > RPC: Program = 100003 (NFS), version = 3, procedure = 8 > > RPC: Credentials: Flavor = 1 (Unix), len = 52 bytes > > RPC: Time = 0 > > RPC: Hostname = > > RPC: Uid = 544, Gid = 200 > > RPC: Groups = 200 0 5 14 68 69 70 1000 > > RPC: Verifier : Flavor = 0 (None), len = 0 bytes > > RPC: > > NFS: ----- Sun NFS ----- > > NFS: > > NFS: Proc = 8 (Create file) > > NFS: File handle = [008A] > > NFS: 0080000800000002000A000000000002694370EA000A000000000002694370EA > > NFS: File name = testfile2 > > NFS: Method = Unchecked > > NFS: Mode = 0644 > > NFS: Setuid = 0, Setgid = 0, Sticky = 0 > > NFS: Owner's permissions = rw- > > NFS: Group's permissions = r-- > > NFS: Other's permissions = r-- > > NFS: User ID = (not set) > > NFS: Group ID = (not set) > > NFS: Size = (not set) > > NFS: Access time = -1 (set to client time) > > NFS: Modification time = -1 (set to client time) > > NFS: > > NFS: > > > > So the open with the O_EXCL flag ( which succeeds ) shows a field decode by > > snoop as Guard and the failing request shows a lot of other fields. > > This looks like snoop is failing to usefully process the packet. Can > you feed the trace to Ethereal and see what it has to say about it? > The version of ethereal I have ( the one from the ports) cannot decode NFS packets. Maybe you have another version. I have checked rfc1813 for the NFS v3 spec and if the client is really setting the times to -1 it is not following the spec. It should fill a struct nfstime3 { uint32 seconds; uint32 nseconds; }; with the current time on the client and -1 is not a legal uint32. I started looking into the client code but haven't located the error ( yet). > > Hope someone can use this to find out what is wrong. > > ( If needed I can send the full snoop capture ) > > If you've got it in a format that can be used by other programs, please > do make it available somewhere. I have put the raw snoop capture on http://www.xs4all.nl/~paulz/snoop.log.gz (it is only 820 bytes) Paul -- Paul van der Zwan paulz @ trantor.stuyts.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 12:45:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07872 for freebsd-current-outgoing; Wed, 16 Dec 1998 12:45:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07866 for ; Wed, 16 Dec 1998 12:45:34 -0800 (PST) (envelope-from rkw@nomad.dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id OAA01018; Wed, 16 Dec 1998 14:45:19 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Wed, 16 Dec 1998 14:45:19 -0600 (CST) From: Richard Wackerbarth To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: disklabel baggage. In-Reply-To: <199812162001.MAA81180@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I agree that we need to keep "/" clean. However, I do not feel that "/etc/" is at all appropriate for boot blocks. "/etc/" is a configuration directory. I routinely overwrite it or mount it remotely. "share/" was the original location for auxillary files. As for "/usr/?" vs "/?", that should be determined by the need to use the blocks in single user salvage mode when we assume that there is only one good disk mounted. Do we need to be able to disklabel another disk? The installed bootfiles are another matter. Obviously, they must be located on the root partition. Traditionally, the kernel was placed in the root so that the boot loader did not have to understand the complexities of traversing directories. Now that we have many more bootstrap files, the root seems cluttered. However, since these files are used only at boot time, they are easy to simply ignore. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 12:51:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08982 for freebsd-current-outgoing; Wed, 16 Dec 1998 12:51:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08973 for ; Wed, 16 Dec 1998 12:51:43 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id OAA26134; Wed, 16 Dec 1998 14:51:09 -0600 (CST) Message-ID: <19981216145109.A26118@Denninger.Net> Date: Wed, 16 Dec 1998 14:51:09 -0600 From: Karl Denninger To: Richard Wackerbarth , Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: disklabel baggage. References: <199812162001.MAA81180@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Richard Wackerbarth on Wed, Dec 16, 1998 at 02:45:19PM -0600 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 16, 1998 at 02:45:19PM -0600, Richard Wackerbarth wrote: > I agree that we need to keep "/" clean. > However, I do not feel that "/etc/" is at all appropriate for boot > blocks. "/etc/" is a configuration directory. I routinely overwrite it > or mount it remotely. "share/" was the original location for auxillary > files. > > As for "/usr/?" vs "/?", that should be determined by the need to > use the blocks in single user salvage mode when we assume that there is > only one good disk mounted. Do we need to be able to disklabel another > disk? > > The installed bootfiles are another matter. Obviously, they > must be located on the root partition. Traditionally, the kernel was > placed in the root so that the boot loader did not have to understand the > complexities of traversing directories. Now that we have many more > bootstrap files, the root seems cluttered. However, since these files are > used only at boot time, they are easy to simply ignore. 1. It is ABSOLUTELY CRITICAL in many recovery situations that you be able to run with only ONE partition mountable (and even that mountable read-only). I cannot COUNT the number of times that I'd have had to reinstall if I could not do things like set up a new disk with only a read-only bootable root slice. 2. I don't care how cluttered "/" is; I never go there unless I'm doing maintenance. I do very MUCH care that the tools that I need to do enough with the system to be able to run a partition of a disk and a full restore (including one over the network) ARE on that partitiion. -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 13:09:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11854 for freebsd-current-outgoing; Wed, 16 Dec 1998 13:09:00 -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 NAA11838 for ; Wed, 16 Dec 1998 13:08:49 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA28347; Wed, 16 Dec 1998 13:07:40 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdq28342; Wed Dec 16 21:07:36 1998 Message-ID: <36782114.2781E494@whistle.com> Date: Wed, 16 Dec 1998 13:07:32 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: "Richard Seaman, Jr." CC: Archie Cobbs , "current@FreeBSD.ORG" Subject: Re: Linux Threads patches available References: <199812161352.HAA11221@ns.tar.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Seaman, Jr. wrote: > > On Tue, 15 Dec 1998 15:57:35 -0800 (PST), Archie Cobbs wrote: > [patches described] The kernel components of this are very self contained and will not jeapardise other sytem code.. I would like to extract them and check them in to assist testing, and to make such things as star-office 3.0 to run "out of the box" Anyone have any objections? julian > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 13:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13723 for freebsd-current-outgoing; Wed, 16 Dec 1998 13:22:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles128.castles.com [208.214.165.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13711 for ; Wed, 16 Dec 1998 13:22:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id DAA00321; Wed, 16 Dec 1998 03:42:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812161142.DAA00321@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Richard Seaman, Jr." cc: "Nate Williams" , "current@freebsd.org" Subject: Re: Linux Threads patches available In-reply-to: Your message of "Tue, 15 Dec 1998 17:18:03 CST." <199812152318.RAA06787@ns.tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Dec 1998 03:41:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 15 Dec 1998 15:53:03 -0700, Nate Williams wrote: > > >Is this code GPL, or BSD copyrighted? If the former, then it can't be a > >'normal' part of the kernel. It also has alot of implications for the > >many vendors who use FreeBSD as an embedded system. > > The kernel patches are not GPL copyrighted. They're just patches > to the existing FreeBSD kernel without any additional copyright > restriction. Perhaps I should have added that I think the kernel > patches included here, or something like them, will be needed with > just about any "kernel threads" implementation. I've had a (quick) look at your current webpage; thanks for collecting all this in one place. Would you care to summarise the changes in a little more detail, and perhaps sort them into 'non-intrusive' and 'intrusive' groups so that we can commit the first set and do whatever needs to be done to resolve any problems with the second ASAP? > The patches allow kernel threads signal handling to move much closer > to the posix requirements, but doesn't quite go all the way (linux > doesn't either at this point). The patches also implement the linux > "clone" call using rfork, and make changes to the linux_mmap and > linux_wait calls in the linux emulation module. I notice that you mention that the posix realtime support is "probably" required for the Linux threads stuff to work; can you confirm this, and perhaps talk to Peter Dufault (dufault@freebsd.org) about what can be done to either ratify and incorporate this code unconditionally, or (perhaps better) to move it into a KLD module on which the Linux module can then depend? > However the Linux Threads code is GPL copyrighted. The additional > code provided in separate files needed to get the port working, > is not GPL copyrighted. However, none of this code goes into > the kernel, its all in a library. ... which would be an excellent candidate for a port/package. > This was beyond my capabilities and interest. When Brian Feldman posted > his patches, which were close to working, it appeared to me that a > port of linux threads could be a "quick fix" for kernel threads, > while someone, eventually, does the real thing for FreeBSD. Its > one-to-one kernel threads, but there's not much that needs to be > changed in the threads library itself. For the sake of reestablishing our compatibility with Linux, I think that your current code should be strongly considered. As for the eventual fate of threading in the FreeBSD kernel, we're still really dependant on the availibility of development resources here, either in the form of willing and able volunteers or funding which would allow us to secure the individuals able to do the work. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 13:41:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16566 for freebsd-current-outgoing; Wed, 16 Dec 1998 13:41:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org ([142.177.186.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16558 for ; Wed, 16 Dec 1998 13:41:38 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id RAA28129 for ; Wed, 16 Dec 1998 17:41:31 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 16 Dec 1998 17:41:30 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: Odd serial console problem... 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 Since my 3.0 machine is several thousand kilometers away, we have the serial console enabled, and plugged inot a port on a Portmaster 2e terminal server...all of a sudden, it won't allow me to login anymore, even thogh I can 'see' the boot sequence and any error messages on teh screen: FreeBSD (hub.org) (ttyd0) login: root Password:Login timed out after 300 seconds FreeBSD (hub.org) (ttyd0) login: The password I type is correct, as I can 'su' in a shell using the same one...it just doesn't let me login through the console... I haven't changed ayting, that I'm aware of, but it definitely used to work...:( Any ideas as to where I should look? connections through ssh work right, and all services (httpd, smtp, etc) all appear to be working correctly... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 13:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17451 for freebsd-current-outgoing; Wed, 16 Dec 1998 13:45:54 -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 NAA17439 for ; Wed, 16 Dec 1998 13:45:50 -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 OAA08529; Wed, 16 Dec 1998 14:45:44 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA25415; Wed, 16 Dec 1998 14:45:43 -0700 Date: Wed, 16 Dec 1998 14:45:43 -0700 Message-Id: <199812162145.OAA25415@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: Odd serial console problem... In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Since my 3.0 machine is several thousand kilometers away, we have the > serial console enabled, and plugged inot a port on a Portmaster 2e > terminal server...all of a sudden, it won't allow me to login anymore, > even thogh I can 'see' the boot sequence and any error messages on teh > screen: > > FreeBSD (hub.org) (ttyd0) > login: root > Password:Login timed out after 300 seconds > > FreeBSD (hub.org) (ttyd0) > login: > > The password I type is correct, as I can 'su' in a shell using the > same one...it just doesn't let me login through the console... Look at /etc/ttys to make sure 'secure' is set on the console. # # @(#)ttys 5.1 (Berkeley) 4/17/89 # # name getty type status comments # # This entry needed for asking password when init goes to single-user mode # If you want to be asked for password, change "secure" to "insecure" here console none unknown off secure Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 14:20:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21281 for freebsd-current-outgoing; Wed, 16 Dec 1998 14:20:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org ([142.177.186.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21276 for ; Wed, 16 Dec 1998 14:20:04 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id SAA28255; Wed, 16 Dec 1998 18:19:54 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 16 Dec 1998 18:19:54 -0400 (AST) From: The Hermit Hacker To: Nate Williams cc: freebsd-current@FreeBSD.ORG Subject: Re: Odd serial console problem... In-Reply-To: <199812162145.OAA25415@mt.sri.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, 16 Dec 1998, Nate Williams wrote: > > Since my 3.0 machine is several thousand kilometers away, we have the > > serial console enabled, and plugged inot a port on a Portmaster 2e > > terminal server...all of a sudden, it won't allow me to login anymore, > > even thogh I can 'see' the boot sequence and any error messages on teh > > screen: > > > > FreeBSD (hub.org) (ttyd0) > > login: root > > Password:Login timed out after 300 seconds > > > > FreeBSD (hub.org) (ttyd0) > > login: > > > > The password I type is correct, as I can 'su' in a shell using the > > same one...it just doesn't let me login through the console... > > Look at /etc/ttys to make sure 'secure' is set on the console. First thing I thought about, and it is set to secure ... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 14:29:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22250 for freebsd-current-outgoing; Wed, 16 Dec 1998 14:29:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22245 for ; Wed, 16 Dec 1998 14:29:31 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id QAA20111; Wed, 16 Dec 1998 16:29:22 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812162229.QAA20111@ns.tar.com> From: "Richard Seaman, Jr." To: "Julian Elischer" Cc: "Archie Cobbs" , "current@FreeBSD.ORG" Date: Wed, 16 Dec 98 16:29:21 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Linux Threads patches available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Dec 1998 13:07:32 -0800, Julian Elischer wrote: >The kernel components of this are very self contained and will not >jeapardise other sytem code.. >I would like to extract them and check them in to assist testing, and >to make such things as star-office 3.0 to run "out of the box" > >Anyone have any objections? Not me. I've been running the patches here for a while with no problems in any non-threaded code (no real problems in threaded code either). Never-the-less, I would feel better if someone looked at the vm stack code carefully before its committed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 14:43:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24174 for freebsd-current-outgoing; Wed, 16 Dec 1998 14:43:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles128.castles.com [208.214.165.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24160 for ; Wed, 16 Dec 1998 14:43:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01310; Wed, 16 Dec 1998 14:41:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812162241.OAA01310@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: disklabel baggage. In-reply-to: Your message of "Wed, 16 Dec 1998 12:01:27 PST." <199812162001.MAA81180@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Dec 1998 14:41:03 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think it's a good idea to move the boot images from /usr to /, > but I don't like the idea of creating a /boot directory. How > about /etc/boot/ ? After all, disklabel already references /etc/disktab. > Lets keep / as clean as possible. /boot has been there for a while now. When thinking about this, consider: /etc may not be on the root filesystem /boot may not be on the root filesystem -- \\ 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 Wed Dec 16 14:46:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24385 for freebsd-current-outgoing; Wed, 16 Dec 1998 14:46:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24380 for ; Wed, 16 Dec 1998 14:46:19 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id QAA20211; Wed, 16 Dec 1998 16:46:00 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812162246.QAA20211@ns.tar.com> From: "Richard Seaman, Jr." To: "Mike Smith" Cc: "current@freebsd.org" , "Nate Williams" Date: Wed, 16 Dec 98 16:45:59 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Linux Threads patches available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Dec 1998 03:41:59 -0800, Mike Smith wrote: >I've had a (quick) look at your current webpage; thanks for collecting >all this in one place. Would you care to summarise the changes in a >little more detail, and perhaps sort them into 'non-intrusive' and >'intrusive' groups so that we can commit the first set and do whatever >needs to be done to resolve any problems with the second ASAP? Yes. I'd planned on more of a description. I'm working on it but won't have time until tomorrow at the earliest. >I notice that you mention that the posix realtime support is "probably" >required for the Linux threads stuff to work; can you confirm this, and >perhaps talk to Peter Dufault (dufault@freebsd.org) about what can be >done to either ratify and incorporate this code unconditionally, or >(perhaps better) to move it into a KLD module on which the Linux module >can then depend? Ok. I'll contact him. I haven't tried the linux emulation code with out them, since the linux threads library calls sched_yield, sched_setscheduler, etc. I will double check for sure that they don't somehow sneek into the kernel without explicitly enabling the real time extensions. >> However the Linux Threads code is GPL copyrighted. The additional >> code provided in separate files needed to get the port working, >> is not GPL copyrighted. However, none of this code goes into >> the kernel, its all in a library. > >... which would be an excellent candidate for a port/package. Yes. The only complication is the integration with libc, where I think you will need the libc source installed to compile the linux threads port. And, there is the problem of working with conflicting pthread.h headers. However, none of this is all that much of a problem. >For the sake of reestablishing our compatibility with Linux, I think >that your current code should be strongly considered. As for the >eventual fate of threading in the FreeBSD kernel Linux threads has its warts. And, I expect kernel threads can be done much better. But, once the kernel patches are done, the linux code doesn't require all that much modification, so it may be a temporary, if imperfect, solution. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 14:46:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24417 for freebsd-current-outgoing; Wed, 16 Dec 1998 14:46:46 -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 OAA24411 for ; Wed, 16 Dec 1998 14:46:44 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id PAA24717; Wed, 16 Dec 1998 15:46:21 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpd024625; Wed Dec 16 15:46:17 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA04524; Wed, 16 Dec 1998 15:46:05 -0700 (MST) From: Terry Lambert Message-Id: <199812162246.PAA04524@usr09.primenet.com> Subject: Re: PAO Integration? To: brian@Awfulhak.org (Brian Somers) Date: Wed, 16 Dec 1998 22:46:03 +0000 (GMT) Cc: tlambert@primenet.com, y-nakaga@nwsl.mesh.ad.jp, mike@smith.net.au, wollman@khavrinen.lcs.mit.edu, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG In-Reply-To: <199812160811.IAA37602@keep.lan.Awfulhak.org> from "Brian Somers" at Dec 16, 98 08:11:36 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [.....] > > Try to name one ting that you could do with "config" that you could > > not do with a sufficiently dynamic kernel loadable module framework. > [.....] > > Is it possible to load ``n'' pseudo-devices (without teaching the > driver to be dynamic enough to do it itself) ? My kernel config says > ``pseudo-device tun 300''.... Not without teaching the driver to do it itself, no. That's basically what a coning device driver is, is a driver that has been taught. I think the correct approach is to use a clone device, but of course if you put the constraint in that I can't use clone devices, then yeah, static limits require static configuration. You could get non-static fairly quickly by putting Julian's devfs and slice code back in, but of course that'd be pretty politically incorrect (regardless of technical merit). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 14:48:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24532 for freebsd-current-outgoing; Wed, 16 Dec 1998 14:48:36 -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 OAA24523 for ; Wed, 16 Dec 1998 14:48:31 -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 PAA09099; Wed, 16 Dec 1998 15:48:13 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA25983; Wed, 16 Dec 1998 15:48:12 -0700 Date: Wed, 16 Dec 1998 15:48:12 -0700 Message-Id: <199812162248.PAA25983@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Matthew Dillon , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: disklabel baggage. In-Reply-To: <199812162241.OAA01310@dingo.cdrom.com> References: <199812162001.MAA81180@apollo.backplane.com> <199812162241.OAA01310@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think it's a good idea to move the boot images from /usr to /, > > but I don't like the idea of creating a /boot directory. How > > about /etc/boot/ ? After all, disklabel already references /etc/disktab. > > Lets keep / as clean as possible. > > /boot has been there for a while now. When thinking about this, > consider: > > /etc may not be on the root filesystem /etc *MUST* be on the root filesystem, because you wouldn't know what to mount w/out it. (/etc/fstab). Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 14:59:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26075 for freebsd-current-outgoing; Wed, 16 Dec 1998 14:59:06 -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 OAA26070 for ; Wed, 16 Dec 1998 14:59:05 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA02658; Wed, 16 Dec 1998 14:58:31 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdAV2645; Wed Dec 16 22:58:21 1998 Message-ID: <36783B03.446B9B3D@whistle.com> Date: Wed, 16 Dec 1998 14:58:11 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Mike Smith CC: "Richard Seaman, Jr." , Nate Williams , "current@freebsd.org" Subject: Re: Linux Threads patches available References: <199812161142.DAA00321@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: > > For the sake of reestablishing our compatibility with Linux, I think > that your current code should be strongly considered. As for the > eventual fate of threading in the FreeBSD kernel, we're still really > dependant on the availibility of development resources here, either in > the form of willing and able volunteers or funding which would allow . The system patch affects the following files: Index: bin/ps/keyword.c Index: lib/libc/i386/sys/sigsuspend.S Index: sys/i386/linux/linux.h Index: sys/i386/linux/linux_dummy.c Index: sys/i386/linux/linux_misc.c Index: sys/i386/linux/linux_proto.h Index: sys/i386/linux/linux_syscall.h Index: sys/i386/linux/linux_sysent.c Index: sys/i386/linux/linux_sysvec.c Index: sys/i386/linux/syscalls.master Index: sys/kern/imgact_elf.c Index: sys/kern/init_main.c Index: sys/kern/kern_exit.c Index: sys/kern/kern_fork.c Index: sys/kern/kern_sig.c Index: sys/sys/proc.h Index: sys/sys/signalvar.h Index: sys/sys/unistd.h Index: sys/sys/user.h Index: sys/vm/vm_glue.c the sys/i386/linux files are not an issue really. the other changes relate to the moving of a couple of fields out of the proc/user structures to a separate sharable entity. vis. + struct procsig { + #define ps_begincopy ps_sigignore + sigset_t ps_sigignore; /* Signals being ignored. */ + sigset_t ps_sigcatch; /* Signals being caught by user. */ + int ps_flag; + struct sigacts ps_sigacts; + #define ps_endcopy ps_refcnt + int ps_refcnt; + int ps_posix; + }; + As I said in other mail. This may not be perfect but if we don't make a start on threads, we'll never get to the end.. This seems like a fair place to start. I don't see that implimenting it would be detrimental to the existing system.. I would vote for an inclusion to allow others to start experimenting with linux-threads based software, (note there is now a linux-threads based java JVM.) thoughts all? julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 15:01:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26417 for freebsd-current-outgoing; Wed, 16 Dec 1998 15:01:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26408 for ; Wed, 16 Dec 1998 15:01:02 -0800 (PST) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <10782-31654>; Thu, 17 Dec 1998 00:00:40 +0100 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.9.1/8.9.1) with UUCP id XAA04350; Wed, 16 Dec 1998 23:39:25 +0100 (MET) (envelope-from paulz@trantor.stuyts.nl) Received: from trantor.stuyts.nl (localhost [127.0.0.1]) by trantor.stuyts.nl (8.9.1/8.8.5) with ESMTP id XAA00548; Wed, 16 Dec 1998 23:33:54 +0100 (MET) Message-Id: <199812162233.XAA00548@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-reply-to: Your message of "Tue, 15 Dec 1998 17:58:45 PST." <199812160158.RAA00944@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Dec 1998 23:33:53 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > And the following for testfile2: > > RPC: ----- SUN RPC Header ----- > > RPC: > > RPC: Record Mark: last fragment, length = 192 > > RPC: Transaction id = 1478392200 > > RPC: Type = 0 (Call) > > RPC: RPC version = 2 > > RPC: Program = 100003 (NFS), version = 3, procedure = 8 > > RPC: Credentials: Flavor = 1 (Unix), len = 52 bytes > > RPC: Time = 0 > > RPC: Hostname = > > RPC: Uid = 544, Gid = 200 > > RPC: Groups = 200 0 5 14 68 69 70 1000 > > RPC: Verifier : Flavor = 0 (None), len = 0 bytes > > RPC: > > NFS: ----- Sun NFS ----- > > NFS: > > NFS: Proc = 8 (Create file) > > NFS: File handle = [008A] > > NFS: 0080000800000002000A000000000002694370EA000A000000000002694370EA > > NFS: File name = testfile2 > > NFS: Method = Unchecked > > NFS: Mode = 0644 > > NFS: Setuid = 0, Setgid = 0, Sticky = 0 > > NFS: Owner's permissions = rw- > > NFS: Group's permissions = r-- > > NFS: Other's permissions = r-- > > NFS: User ID = (not set) > > NFS: Group ID = (not set) > > NFS: Size = (not set) > > NFS: Access time = -1 (set to client time) > > NFS: Modification time = -1 (set to client time) > > NFS: > > NFS: > > > > So the open with the O_EXCL flag ( which succeeds ) shows a field decode by > > snoop as Guard and the failing request shows a lot of other fields. > > This looks like snoop is failing to usefully process the packet. Can > you feed the trace to Ethereal and see what it has to say about it? > To test my theory that the -1 times are causing the error because they violate the protocol, I chanded the #define nfsm_v3sattr in /usr/src/sys/nfs/ nfsm_subs.h to use NFSV3SATTRTIME_TOSERVER in stead of NFSV3SATTRTIME_TOCLIENT. This makes the server ignore the time values. My test program now creates poth testfile1 and testfile2. I might be wrong but I think the bug is in the client code and surfaced because Solaris 7 has become stricter about clients adhering to the protocol specs. Paul -- Paul van der Zwan paulz @ trantor.stuyts.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 15:09:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27115 for freebsd-current-outgoing; Wed, 16 Dec 1998 15:09:00 -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 PAA27110 for ; Wed, 16 Dec 1998 15:08:59 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA02947 for ; Wed, 16 Dec 1998 15:03:49 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdDT2938; Wed Dec 16 23:03:40 1998 Message-ID: <36783C45.794BDF32@whistle.com> Date: Wed, 16 Dec 1998 15:03:33 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Call for testers.. users of synchronous serial cards. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whistle communications wants to make it's WAN networking framework (netgraph) more useful to others and to update the version that people have seen and make it more easily available for free public use. Unfortunatly I have only our proprietary sync cards to play with. I'd like to make versions of the various sync card drivers that can utilise the netgraph facilities but I need people to test the results. I have an modified (old) if_sr.c driver that I can update, and would like to add netgraph support to any other cards I can get testers for. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 15:20:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28619 for freebsd-current-outgoing; Wed, 16 Dec 1998 15:18:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles128.castles.com [208.214.165.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28612 for ; Wed, 16 Dec 1998 15:18:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01530; Wed, 16 Dec 1998 15:15:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812162315.PAA01530@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nate Williams cc: Mike Smith , Matthew Dillon , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: disklabel baggage. In-reply-to: Your message of "Wed, 16 Dec 1998 15:48:12 MST." <199812162248.PAA25983@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Dec 1998 15:15:31 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I think it's a good idea to move the boot images from /usr to /, > > > but I don't like the idea of creating a /boot directory. How > > > about /etc/boot/ ? After all, disklabel already references /etc/disktab. > > > Lets keep / as clean as possible. > > > > /boot has been there for a while now. When thinking about this, > > consider: > > > > /etc may not be on the root filesystem > > /etc *MUST* be on the root filesystem, because you wouldn't know what to > mount w/out it. (/etc/fstab). This presumes you're running a completely stock init, but perhaps I should have been clearer; in some cases you will remount a new /etc over the (minimal) /etc used to bring the system up. -- \\ 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 Wed Dec 16 15:23:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29019 for freebsd-current-outgoing; Wed, 16 Dec 1998 15:23:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles128.castles.com [208.214.165.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29012 for ; Wed, 16 Dec 1998 15:23:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01606; Wed, 16 Dec 1998 15:20:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812162320.PAA01606@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Paul van der Zwan cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-reply-to: Your message of "Wed, 16 Dec 1998 23:33:53 +0100." <199812162233.XAA00548@trantor.stuyts.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Dec 1998 15:20:49 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > To test my theory that the -1 times are causing the error because they violate > the protocol, I chanded the #define nfsm_v3sattr in /usr/src/sys/nfs/ > nfsm_subs.h to use NFSV3SATTRTIME_TOSERVER in stead of NFSV3SATTRTIME_TOCLIENT. > This makes the server ignore the time values. My test program now creates > poth testfile1 and testfile2. This means that the files get the server's timestamp, which is going to break things like make(1) which expect files to be created with the client's time. > I might be wrong but I think the bug is in the client code and surfaced because > Solaris 7 has become stricter about clients adhering to the protocol specs. This sounds like a good starting point; any chance of tracking down where the time values are supposed to be set in the FreeBSD code and fixing that, since that's what seems to be wrong...? -- \\ 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 Wed Dec 16 15:26:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29304 for freebsd-current-outgoing; Wed, 16 Dec 1998 15:26:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29298 for ; Wed, 16 Dec 1998 15:26:25 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id KAA27597 for ; Thu, 17 Dec 1998 10:26:10 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd027595; Wed Dec 16 23:26:09 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id KAA01928 for ; Thu, 17 Dec 1998 10:26:26 +1100 (EST) Message-Id: <199812162326.KAA01928@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: Re: disklabel baggage. In-reply-to: Your message of Wed, 16 Dec 1998 15:15:31 -0800. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Dec 1998 10:26:05 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This presumes you're running a completely stock init, but perhaps I > should have been clearer; in some cases you will remount a new /etc > over the (minimal) /etc used to bring the system up. yeah, but if you're sophisticated enough to be doing this, then silly little things like 'where are the boot loaders?' won't matter much! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 15:43:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01109 for freebsd-current-outgoing; Wed, 16 Dec 1998 15:43:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles353.castles.com [208.214.167.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01077 for ; Wed, 16 Dec 1998 15:43:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01733; Wed, 16 Dec 1998 15:38:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812162338.PAA01733@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Somers cc: Terry Lambert , y-nakaga@nwsl.mesh.ad.jp (NAKAGAWA Yoshihisa), mike@smith.net.au, wollman@khavrinen.lcs.mit.edu, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 16 Dec 1998 08:11:36 GMT." <199812160811.IAA37602@keep.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Dec 1998 15:38:55 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [.....] > > Try to name one ting that you could do with "config" that you could > > not do with a sufficiently dynamic kernel loadable module framework. > [.....] > > Is it possible to load ``n'' pseudo-devices (without teaching the > driver to be dynamic enough to do it itself) ? My kernel config says > ``pseudo-device tun 300''.... You can only do this by setting the compile-time tunable, ie. set NTUN to 300 when you build the module. Pseudo-devices probably want their own bus, whose probe code would be responsible for resolving this. -- \\ 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 Wed Dec 16 17:19:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13621 for freebsd-current-outgoing; Wed, 16 Dec 1998 17:19:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13616 for ; Wed, 16 Dec 1998 17:19:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA50292; Wed, 16 Dec 1998 17:18:22 -0800 (PST) To: Mark Murray cc: Chuck Robey , Mike Smith , freebsd-current@FreeBSD.ORG, John Birrell , forrie@forrie.com Subject: Re: FreeBSD Buildworld fails In-reply-to: Your message of "Wed, 16 Dec 1998 17:49:13 +0200." <199812161549.RAA04913@greenpeace.grondar.za> Date: Wed, 16 Dec 1998 17:18:21 -0800 Message-ID: <50289.913857501@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > use). Yes, that's correct, a bunch of stuff broke in the land of perl > > when 5.005 came out, some of which is currently causing a good deal of > > grief to folks like Intel. I've tried to talk them through the > > process of building a perl-less 3.0 which they can then add their own > > pre-5.005 version of perl to, but apparently this job is causing them > > more hassle than I expected it to. I guess our source building tools > > aren't for everyone. :( > > Can I help the Intel folks in any way? Well, I basically already told them to go solve their own problems since I'm not a PERL wizard, but let me ask them how they're getting on. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 17:24:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14233 for freebsd-current-outgoing; Wed, 16 Dec 1998 17:24:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pav (pm40s44.intergate.bc.ca [207.194.175.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA14228 for ; Wed, 16 Dec 1998 17:24:31 -0800 (PST) (envelope-from promoteit@netscape.net) Date: Wed, 16 Dec 1998 17:24:31 -0800 (PST) From: Promote-It! To: Message-Id: <419.436145.71539560promoteit@netscape.net> Subject: Your website appeared in What's New on Yahoo! this week. 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 CONGRATULATIONS! Your website appeared in What's New on Yahoo! (or What's New Too) this week and will be added to the main Yahoo database in a few days! ************************************************** The Stakes Are Simply Too High To Leave Your Web Success To Chance!!! It is critical that the right people see your website. Simply designing a good site does not guarantee that it will attract visitors. The "if you build, they will come" premise is not true when conducting business on the Internet. So how do you entice prospective customers to your site? We deliver innovative, traffic-building programs that will get your website in front of the audience you want to reach. --->Search Engine Tune-Up! We create "KILLER" Meta Tags for your website. Watch your hit count soar when your site is listed in a top position with Alta Vista, AOL Netfind, Excite, Hotbot, Infoseek, Lycos, WebCrawler, and Yahoo! --->Promote-It! We submit your site to 459 awards sites, business publications, directories, ezines, search engines, what's new pages, yellow pages, and more! This will be done manually, by a real a real person, not by software that can fail! --->Customer-Direct! Using your keywords and description we create 5 "Spider Mirror Sites" and register them in all the major search engines to drive targeted visitors to your site. ************************************************** Please visit our website for more information! Promote-It! http://www.interweb-connections.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 17:30:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14708 for freebsd-current-outgoing; Wed, 16 Dec 1998 17:30:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14701 for ; Wed, 16 Dec 1998 17:30:26 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id KAA00955; Thu, 17 Dec 1998 10:13:54 +0900 (JST) Message-Id: <199812170113.KAA00955@chandra.eatell.msr.prug.or.jp> To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Tue, 15 Dec 1998 20:17:07 PST." <199812160417.UAA00907@dingo.cdrom.com> Date: Thu, 17 Dec 1998 10:13:53 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You're still not understanding the difference between configuration and > aggregation. No, I understand, we choose another way for these devices. > The new-bus code supports both static (compile-time) and dynamic > (run-time) configuration, as well as build-time, load-time and run-time > aggregation. -current UserConfig is override static (ISA) configuration only, our plan's UserConfig is not only override, allow dynamic add at boot-time. And, we use same frame work for PC-Card dynamic driver assign, kernel module dynamic load, ... -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 18:12:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18918 for freebsd-current-outgoing; Wed, 16 Dec 1998 18:12:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from infoteka.nsk.ru (infoteka.nsk.ru [193.124.36.40]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA18911 for ; Wed, 16 Dec 1998 18:12:51 -0800 (PST) (envelope-from nnd@infoteka.nsk.ru) Received: (qmail 22981 invoked by uid 1001); 17 Dec 1998 02:05:50 -0000 Message-ID: <19981217080550.37849@mail.nsk.ru> Date: Thu, 17 Dec 1998 08:05:50 +0600 From: "Nickolay N. Dudorov" To: current@FreeBSD.ORG Subject: What is the problem with CTM/cvs-cur ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last CTM-delta for cvs-cur collection is cvs-cur.4900.gz from December 15 (at least on ftp.freebsd.org and received by mail). N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 19:24:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25858 for freebsd-current-outgoing; Wed, 16 Dec 1998 19:24:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25849 for ; Wed, 16 Dec 1998 19:24:21 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA19180; Wed, 16 Dec 1998 22:23:35 -0500 (EST) Date: Wed, 16 Dec 1998 22:23:34 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Julian Elischer cc: Mike Smith , "Richard Seaman, Jr." , Nate Williams , "current@freebsd.org" Subject: Re: Linux Threads patches available In-Reply-To: <36783B03.446B9B3D@whistle.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, 16 Dec 1998, Julian Elischer wrote: > Mike Smith wrote: > > > > > For the sake of reestablishing our compatibility with Linux, I think > > that your current code should be strongly considered. As for the Yay! Something came of my efforts (even if I stopped working on it myself)! > > eventual fate of threading in the FreeBSD kernel, we're still really > > dependant on the availibility of development resources here, either in > > the form of willing and able volunteers or funding which would allow . > > The system patch affects the following files: > > Index: bin/ps/keyword.c > Index: lib/libc/i386/sys/sigsuspend.S > Index: sys/i386/linux/linux.h > Index: sys/i386/linux/linux_dummy.c > Index: sys/i386/linux/linux_misc.c > Index: sys/i386/linux/linux_proto.h > Index: sys/i386/linux/linux_syscall.h > Index: sys/i386/linux/linux_sysent.c > Index: sys/i386/linux/linux_sysvec.c > Index: sys/i386/linux/syscalls.master > Index: sys/kern/imgact_elf.c > Index: sys/kern/init_main.c > Index: sys/kern/kern_exit.c > Index: sys/kern/kern_fork.c > Index: sys/kern/kern_sig.c > Index: sys/sys/proc.h > Index: sys/sys/signalvar.h > Index: sys/sys/unistd.h > Index: sys/sys/user.h > Index: sys/vm/vm_glue.c > > > the sys/i386/linux files are not an issue really. > > the other changes relate to the moving of a couple of fields out > of the proc/user structures to a separate sharable entity. vis. I tried to keep my patches style(9) compliant, make sure your modifications are too :) > > + struct procsig { > + #define ps_begincopy ps_sigignore > + sigset_t ps_sigignore; /* Signals being ignored. */ > + sigset_t ps_sigcatch; /* Signals being caught by user. */ > + int ps_flag; > + struct sigacts ps_sigacts; > + #define ps_endcopy ps_refcnt > + int ps_refcnt; > + int ps_posix; > + }; > + > > As I said in other mail. This may not be perfect but if we don't > make a start on threads, we'll never get to the end.. This seems like > a fair place to start. I don't see that implimenting it would be > detrimental to the existing system.. > > I would vote for an inclusion to allow others to start experimenting > with linux-threads based software, > (note there is now a linux-threads based java JVM.) > > thoughts all? > I don't think it should quite be included yet, because noone's really thought of the impact of an EXTRA per-process malloc, have they? If this is alright to give up an extra 4k per process (let's see, a max-process-count of 100000, this is a total of 400 mb?!?), then perhaps this should be done. Other than that, I'm not so sure, because this could be a Very Bad Thing. Has anyone really thought about the per-process memory overhead issues that come up nowadays with struct proc growing, and being added to? It seems like to max out a system, there's at LEAST 800 MB of RAM dedicated to struct proc and procsig, right? > julian > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 19:28:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26052 for freebsd-current-outgoing; Wed, 16 Dec 1998 19:28:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26047 for ; Wed, 16 Dec 1998 19:28:27 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA19247; Wed, 16 Dec 1998 22:28:14 -0500 (EST) Date: Wed, 16 Dec 1998 22:28:14 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Julian Elischer cc: "Richard Seaman, Jr." , Archie Cobbs , "current@FreeBSD.ORG" Subject: Re: Linux Threads patches available In-Reply-To: <36782114.2781E494@whistle.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, 16 Dec 1998, Julian Elischer wrote: > Richard Seaman, Jr. wrote: > > > > On Tue, 15 Dec 1998 15:57:35 -0800 (PST), Archie Cobbs wrote: > > > [patches described] > > The kernel components of this are very self contained and will not > jeapardise other sytem code.. > I would like to extract them and check them in to assist testing, and > to make such things as star-office 3.0 to run "out of the box" > > Anyone have any objections? > > julian For one, I object. Keep it as a patchset, or make a vendor branch, but the overhead and memory use of these modifications needs to be considered carefully! I know I did much of the LinuxThreads work, and would love to see it going into the kernel, but the ramifications need to be examined. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 19:46:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27625 for freebsd-current-outgoing; Wed, 16 Dec 1998 19:46: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 TAA27620 for ; Wed, 16 Dec 1998 19:46:19 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA11621; Wed, 16 Dec 1998 19:44:20 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdU11619; Thu Dec 17 03:44:17 1998 Date: Wed, 16 Dec 1998 19:44:14 -0800 (PST) From: Julian Elischer To: Brian Feldman cc: "Richard Seaman, Jr." , Archie Cobbs , "current@FreeBSD.ORG" Subject: Re: Linux Threads patches 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 sounds like you have a good reason.. pitty.. I didn't see the 4KB malloc you mentionned in the other email added in the patches.. I guess I must have missed it.. I'll look again On Wed, 16 Dec 1998, Brian Feldman wrote: > On Wed, 16 Dec 1998, Julian Elischer wrote: > > > Richard Seaman, Jr. wrote: > > > > > > On Tue, 15 Dec 1998 15:57:35 -0800 (PST), Archie Cobbs wrote: > > > > > [patches described] > > > > The kernel components of this are very self contained and will not > > jeapardise other sytem code.. > > I would like to extract them and check them in to assist testing, and > > to make such things as star-office 3.0 to run "out of the box" > > > > Anyone have any objections? > > > > julian > > For one, I object. Keep it as a patchset, or make a vendor branch, but > the overhead and memory use of these modifications needs to be considered > carefully! I know I did much of the LinuxThreads work, and would love to see > it going into the kernel, but the ramifications need to be examined. > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 21:02:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04701 for freebsd-current-outgoing; Wed, 16 Dec 1998 21:02:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04695 for ; Wed, 16 Dec 1998 21:02:36 -0800 (PST) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id VAA07322 for ; Wed, 16 Dec 1998 21:02:29 -0800 Date: Wed, 16 Dec 1998 21:02:29 -0800 (PST) From: Neal Westfall To: current@FreeBSD.ORG Subject: syncing 3.0-src tree with current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there an easy way to get a 3.0 source tree up to current? I will be doing this with CTM. Can I start with my 3.0 source tree or do I need to wipe it out and start clean with the fat delta? I didn't see any info on how to do this without starting from an empty src dir. Can this be done? Thanks.. Neal Westfall nwestfal@odc.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 21:20:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05780 for freebsd-current-outgoing; Wed, 16 Dec 1998 21:18:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05773 for ; Wed, 16 Dec 1998 21:18:27 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id AAA22593; Thu, 17 Dec 1998 00:18:05 -0500 (EST) Date: Thu, 17 Dec 1998 00:18:05 -0500 (EST) Message-Id: <199812170518.AAA22593@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: sendfile() Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Heard some talk of sendfile() in 3.0 Where is that interface? man page? Header file? Is it in a very new kernel or just a rumor? -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 21:21:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06188 for freebsd-current-outgoing; Wed, 16 Dec 1998 21:21:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06182 for ; Wed, 16 Dec 1998 21:21:52 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id QAA00865 for ; Thu, 17 Dec 1998 16:21:43 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd000863; Thu Dec 17 05:21:38 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id QAA13657 for ; Thu, 17 Dec 1998 16:21:56 +1100 (EST) Message-Id: <199812170521.QAA13657@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: Why no "date -a"? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Dec 1998 16:21:35 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This came up on the newsgroup today and I couldn't think of an answer. FreeBSD has adjtime(2) and Poul-Henning et al as nanosecond wranglers, yet no "date -a". This must be a deliberate omission. Why? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 21:36:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06808 for freebsd-current-outgoing; Wed, 16 Dec 1998 21:36:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06803 for ; Wed, 16 Dec 1998 21:36:20 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA14054; Wed, 16 Dec 1998 21:36:12 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id VAA21566; Wed, 16 Dec 1998 21:36:12 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 16 Dec 1998 21:36:12 -0800 (PST) Message-Id: <199812170536.VAA21566@vashon.polstra.com> To: jb@cimlogic.com.au Subject: Re: Kernel module syscall inconsistencies Newsgroups: polstra.freebsd.current In-Reply-To: <199812160533.QAA14070@cimlogic.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199812160533.QAA14070@cimlogic.com.au>, John Birrell wrote: > > I think kldfind() should accept the string with the path and behave like > kldload() does. > > And kldload() shouldn't allow more than one module of a particular name. I agree. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 21:39:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA07212 for freebsd-current-outgoing; Wed, 16 Dec 1998 21:39:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA07205 for ; Wed, 16 Dec 1998 21:39:43 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id VAA14066; Wed, 16 Dec 1998 21:39:36 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id VAA21583; Wed, 16 Dec 1998 21:39:36 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 16 Dec 1998 21:39:36 -0800 (PST) Message-Id: <199812170539.VAA21583@vashon.polstra.com> To: nwestfal@Vorlon.odc.net Subject: Re: syncing 3.0-src tree with current Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Neal Westfall wrote: > Is there an easy way to get a 3.0 source tree up to current? I will be > doing this with CTM. Can I start with my 3.0 source tree or do I need > to wipe it out and start clean with the fat delta? I didn't see any > info on how to do this without starting from an empty src dir. Can > this be done? I'll let others answer about CTM. But you can do it with CVSup. The technique is described in the CVSup FAQ, at: http://www.polstra.com/projects/freeware/CVSup/ John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 21:59:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA08759 for freebsd-current-outgoing; Wed, 16 Dec 1998 21:59:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA08754 for ; Wed, 16 Dec 1998 21:59:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA87886; Wed, 16 Dec 1998 21:59:42 -0800 (PST) (envelope-from dillon) Date: Wed, 16 Dec 1998 21:59:42 -0800 (PST) From: Matthew Dillon Message-Id: <199812170559.VAA87886@apollo.backplane.com> To: HighWind Software Information Cc: current@FreeBSD.ORG Subject: Re: sendfile() References: <199812170518.AAA22593@highwind.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Heard some talk of sendfile() in 3.0 : :Where is that interface? man page? Header file? : :Is it in a very new kernel or just a rumor? : :-Rob : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message Yes, it's been in -current for about a month and a half. Works great! You'll have to download a recent -current and make world. Essentially: int sendfile(int fd, int s, off_t offset, size_t nbytes, struct sf_hdtr *hdtr, off_t *sbytes, int flags) Where sf_hdtr allows headers and trailers to be merged into the stream. If you are thinking of using sendfile with HighWind's news software and you already store the articles in wire format, it should work great! I don't use it in Diablo because I store articles in their binary format :-(. Linux has a similar system call, but I think not quite as sophisticated as DG's FreeBSD implementation. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 22:50:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA13829 for freebsd-current-outgoing; Wed, 16 Dec 1998 22:50:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Vorlon.odc.net (Vorlon.odc.net [207.137.42.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA13823 for ; Wed, 16 Dec 1998 22:50:56 -0800 (PST) (envelope-from nwestfal@Vorlon.odc.net) Received: from localhost (nwestfal@localhost) by Vorlon.odc.net (8.8.7/8.8.7) with ESMTP id WAA10410; Wed, 16 Dec 1998 22:50:41 -0800 Date: Wed, 16 Dec 1998 22:50:41 -0800 (PST) From: Neal Westfall To: John Polstra cc: current@FreeBSD.ORG Subject: Re: syncing 3.0-src tree with current In-Reply-To: <199812170539.VAA21583@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to all for the pointer to cvsup instead of ctm. I've got it updating my src tree now. Neal Westfall nwestfal@odc.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 23:08:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15673 for freebsd-current-outgoing; Wed, 16 Dec 1998 23:08:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15659 for ; Wed, 16 Dec 1998 23:08:47 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA08563; Thu, 17 Dec 1998 00:59:35 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id BAA15858; Thu, 17 Dec 1998 01:00:42 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812170100.BAA15858@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: brian@Awfulhak.org (Brian Somers), y-nakaga@nwsl.mesh.ad.jp, mike@smith.net.au, wollman@khavrinen.lcs.mit.edu, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 16 Dec 1998 22:46:03 GMT." <199812162246.PAA04524@usr09.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Dec 1998 01:00:42 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You could get non-static fairly quickly by putting Julian's devfs > and slice code back in, but of course that'd be pretty politically > incorrect (regardless of technical merit). IMHO, taking SLICE/DEVFS back out of FreeBSD did more harm than good. I'm not trying to start a debate, I'm just voicing my opinion.... > Terry Lambert > terry@lambert.org -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 16 23:48:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19604 for freebsd-current-outgoing; Wed, 16 Dec 1998 23:48:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19598; Wed, 16 Dec 1998 23:48:05 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id XAA19152; Wed, 16 Dec 1998 23:48:07 -0800 (PST) Message-Id: <199812170748.XAA19152@root.com> To: "Marc G. Fournier" cc: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: any way of gleaming info from these? In-reply-to: Your message of "Wed, 16 Dec 1998 11:50:16 -0400." From: David Greenman Reply-To: dg@root.com Date: Wed, 16 Dec 1998 23:48:06 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Wed, 16 Dec 1998, David Greenman wrote: > >> >vnode_pager_putpages: residual I/O 4096 at 113 >> >vnode_pager_putpages: I/O error 6 >> >vnode_pager_putpages: residual I/O 4096 at 113 >> >vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 >> >vnode_pager_putpages: I/O error 6 >> >vnode_pager_putpages: residual I/O 4096 at 113 >> > >> >maybe its totally impossible, but is there no way of detailing which drive >> >is causing this? or is it not a drive? >> >> Error 6 is ENXIO - device not configured. This might happen if the device >> is SCSI and it loses power/goes offline. I can't think of any other reasons >> offhand. > >Hrmmm...is vnode_pager_putpages a 'file system' error, or a 'swap' error? >The system is locked up right now, awaiting someone to get down to the >office and reboot it. vnode_pager_putpages is a routine, not an error (well...:-)). I don't know what is returning ENXIO, but putpages just calls the filesystem VOP_PUTPAGES entry, so you'd have to look at that. vnode_pager_putpages isn't usually called very often in a typical system - it's used when mapped/modified file pages need to be written back to the backing file, which doesn't normally happen on a typical system (modified pages are usually backed by swap, not the file). >Looking through /usr/src/sys, the error message is generated in >vm/vnode_pager.c...which, to me, would indicate swap space? No, the swap_pager pages out to swap. The vnode_pager pages out to files. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 00:05:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21309 for freebsd-current-outgoing; Thu, 17 Dec 1998 00:05:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21302 for ; Thu, 17 Dec 1998 00:05:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id AAA89361; Thu, 17 Dec 1998 00:05:29 -0800 (PST) (envelope-from dillon) Date: Thu, 17 Dec 1998 00:05:29 -0800 (PST) From: Matthew Dillon Message-Id: <199812170805.AAA89361@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: asleep()/await(), M_AWAIT, etc... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I've spent a couple of hours thinking about this and I think I can trivially implement an awesome OS feature I've used in the past in my own OS work into FreeBSD. Here are the semantics. I am presuming people are familiar with tsleep(). We add an asleep() kernel function to complement tsleep(). asleep() works like tsleep() in that it adds the process to the appropriate slpque, but asleep() does *not* put the process to sleep. Instead it returns immediately. The process stays runnable. Additional calls to asleep() (or a call to tsleep()) removes the proc from any slpque and re-adds it to the new one. i.e. only the most recent call is effective. We add an await() kernel function. This function initiates any timeout and puts the process to sleep, but only if it is still on a sleep queue. If someone (i.e. an interrupt) wakes up the sleep address after the process calls asleep() but before it calls await(), the slpque is cleared and the await() winds up being a NOP. I have included a unified diff (DON'T APPLY THIS!, FOR REFERENCE ONLY!) at the bottom. The purpose of the new routines is to allow blocking conditions to propogate up a subroutine chain and get handled at a higher level rather then at a lower level in those areas of code that cannot afford to leave exclusive locks sitting around. For example, if bread() blocks waiting for a low level disk I/O on a block device, the vnode remains locked throughout which badly mars potential parallelism when multiple programs are accessing the same file. There is no reason to leave the high level vnode locked while bringing a page into the VM buffer cache! Another example: If a piece of critically locked code needs to allocate memory but cannot afford to block with the lock intact, we can implement M_AWAIT. The code would allocate memory using M_AWAIT and if the allocation fails would be able to unwind the lock(s), await(), and retry. This is something the current code cannot do at all. We could start 'fixing' not only bread(), but getnewbuf() (adding a new flag for slpflag), malloc(), kmem_malloc(), vm_page_alloc(), and many other routines to support the new mechanism without changing backwards compatibility with the existing tsleep()/M_WAITOK mechanism (which, of course, is still useful). I also believe we can fix known deadlocks with mmap()ed files and vnode interlock situations trivially. There are many other cool things you can do with this sort of functionality.... fixing possible deadlock situations allows us to more easily pull SMP locks deeper into the kernel, for example. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) Index: kern/kern_synch.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_synch.c,v retrieving revision 1.69 diff -u -r1.69 kern_synch.c --- kern_synch.c 1998/11/27 11:44:22 1.69 +++ kern_synch.c 1998/12/17 07:46:39 @@ -407,9 +407,21 @@ if (ident == NULL || p->p_stat != SRUN) panic("tsleep"); /* XXX This is not exhaustive, just the most common case */ +#ifdef NOTDEF + /* + * This can happen legitimately now with asleep()/await() + */ if ((p->p_procq.tqe_prev != NULL) && (*p->p_procq.tqe_prev == p)) panic("sleeping process already on another queue"); #endif +#endif + /* + * Process may be sitting on a slpque if asleep() was called, remove + * it before re-adding. + */ + if (p->p_wchan != NULL) + unsleep(p); + p->p_wchan = ident; p->p_wmesg = wmesg; p->p_slptime = 0; @@ -475,7 +487,166 @@ } /* - * Implement timeout for tsleep. + * asleep() - async sleep call. Place process on wait queue and return + * immediately without blocking. The process stays runnable until await() + * is called. + * + * Only the most recent sleep condition is effective when making successive + * calls to asleep() or when calling tsleep(). + * + * The timeout, if any, is not initiated until await() is called. The sleep + * priority, signal, and timeout is specified in the asleep() call but may be + * overriden in the await() call. + */ + +int +asleep(void *ident, int priority, const char *wmesg, int timo) +{ + struct proc *p = curproc; + int s; + + /* + * splhigh() while manipulating sleep structures and slpque. + * + * Remove preexisting wait condition (if any) and place process + * on appropriate slpque, but do not put process to sleep. + */ + + s = splhigh(); + + if (p->p_wchan != NULL) + unsleep(p); + + if (ident) { + p->p_wchan = ident; + p->p_wmesg = wmesg; + p->p_slptime = 0; + p->p_asleep.as_priority = priority; + p->p_asleep.as_timo = timo; + TAILQ_INSERT_TAIL(&slpque[LOOKUP(ident)], p, p_procq); + } + + splx(s); + + return(0); +} + +/* + * await() - wait for async condition to occur. The process blocks until + * wakeup() is called on the most recent asleep() address. If wakeup is called + * priority to await(), await() winds up being a NOP. + * + * If await() is called more then once (without an intervening asleep() call), + * await() is still effectively a NOP but it calls mi_switch() to give other + * processes some cpu before returning. The process is left runnable. + */ + +int +await(int priority, int timo) +{ + struct proc *p = curproc; + int s; + + s = splhigh(); + + if (p->p_wchan != NULL) { + struct callout_handle thandle; + int sig; + int catch; + + /* + * The call to await() can override defaults specified in + * the original asleep(). + */ + if (priority < 0) + priority = p->p_asleep.as_priority; + if (timo < 0) + timo = p->p_asleep.as_timo; + + /* + * Install timeout + */ + + if (timo) + thandle = timeout(endtsleep, (void *)p, timo); + + sig = 0; + catch = priority & PCATCH; + + if (catch) { + p->p_flag |= P_SINTR; + if ((sig = CURSIG(p))) { + if (p->p_wchan) + unsleep(p); + p->p_stat = SRUN; + goto resume; + } + if (p->p_wchan == NULL) { + catch = 0; + goto resume; + } + } + p->p_stat = SSLEEP; + p->p_stats->p_ru.ru_nvcsw++; + mi_switch(); +resume: + curpriority = p->p_usrpri; + + splx(s); + p->p_flag &= ~P_SINTR; + if (p->p_flag & P_TIMEOUT) { + p->p_flag &= ~P_TIMEOUT; + if (sig == 0) { +#ifdef KTRACE + if (KTRPOINT(p, KTR_CSW)) + ktrcsw(p->p_tracep, 0, 0); +#endif + return (EWOULDBLOCK); + } + } else if (timo) + untimeout(endtsleep, (void *)p, thandle); + if (catch && (sig != 0 || (sig = CURSIG(p)))) { +#ifdef KTRACE + if (KTRPOINT(p, KTR_CSW)) + ktrcsw(p->p_tracep, 0, 0); +#endif + if (p->p_sigacts->ps_sigintr & sigmask(sig)) + return (EINTR); + return (ERESTART); + } +#ifdef KTRACE + if (KTRPOINT(p, KTR_CSW)) + ktrcsw(p->p_tracep, 0, 0); +#endif + } else { + /* + * If as_priority is 0, await() has been called without an + * intervening asleep(). We are still effectively a NOP, + * but we call mi_switch() for safety. + */ + + if (p->p_asleep.as_priority == 0) { + p->p_stats->p_ru.ru_nvcsw++; + mi_switch(); + } + splx(s); + + } + + /* + * clear p_asleep.as_priority as an indication that await() has been + * called. If await() is called again without an intervening asleep(), + * await() is still effectively a NOP but the above mi_switch() code + * is triggered. + */ + p->p_asleep.as_priority = 0; + + return (0); +} + +/* + * Implement timeout for tsleep or asleep()/await() + * * If process hasn't been awakened (wchan non-zero), * set timeout flag and undo the sleep. If proc * is stopped, just unsleep so it will remain stopped. @@ -532,9 +703,15 @@ restart: for (p = qp->tqh_first; p != NULL; p = p->p_procq.tqe_next) { #ifdef DIAGNOSTIC +#ifdef NOTDEF + /* + * The process can legitimately be running now with + * asleep()/await(). + */ if (p->p_stat != SSLEEP && p->p_stat != SSTOP) panic("wakeup"); #endif +#endif if (p->p_wchan == ident) { TAILQ_REMOVE(qp, p, p_procq); p->p_wchan = 0; @@ -577,8 +754,14 @@ for (p = qp->tqh_first; p != NULL; p = p->p_procq.tqe_next) { #ifdef DIAGNOSTIC +#ifdef NOTDEF + /* + * The process can legitimately be running now with + * asleep()/await(). + */ if (p->p_stat != SSLEEP && p->p_stat != SSTOP) panic("wakeup_one"); +#endif #endif if (p->p_wchan == ident) { TAILQ_REMOVE(qp, p, p_procq); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 00:13:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22222 for freebsd-current-outgoing; Thu, 17 Dec 1998 00:13:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22215 for ; Thu, 17 Dec 1998 00:13:29 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.054 #1) id 0zqYY4-0002tb-00; Thu, 17 Dec 1998 10:12:40 +0200 From: Sheldon Hearn To: Alexander Leidinger cc: studded@dal.net, current@FreeBSD.ORG Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? In-reply-to: Your message of "Wed, 16 Dec 1998 09:50:01 +0100." <199812160850.JAA28103@wurzelausix> Date: Thu, 17 Dec 1998 10:12:40 +0200 Message-ID: <11134.913882360@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Dec 1998 09:50:01 +0100, Alexander Leidinger wrote: > Now I have found the problem: mergemaster (script from ports/sysutils, > revision 1.17) > It creates /usr/src/sendmail/freebsd.cf. (Is the author listening?) No, it creates /usr/src/usr.sbin/sendmail/freebsd.cf . I would imagine that this is the offending action: (cd /usr/src/usr.sbin/sendmail/cf/cf && m4 ../m4/cf.m4 freebsd.mc) > freebsd.cf chmod 444 freebsd.cf install -c -o bin -g bin -m 644 freebsd.cf /var/tmp/temproot/etc/sendmail.cf The author has been cc'd on this message, so he's probably "listening". :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 00:24:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23168 for freebsd-current-outgoing; Thu, 17 Dec 1998 00:24:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23120 for ; Thu, 17 Dec 1998 00:23:55 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:cd5EkdMBM0MEKuX7R5AyoClr2wXZSYTB@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id KAA07112; Thu, 17 Dec 1998 10:23:42 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:JsPy7Z0/I+e9+LmqhqskGJBHjmLFjpBN@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id KAA74519; Thu, 17 Dec 1998 10:23:41 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812170823.KAA74519@greenpeace.grondar.za> To: Neal Westfall cc: current@FreeBSD.ORG Subject: Re: syncing 3.0-src tree with current In-Reply-To: Your message of " Wed, 16 Dec 1998 21:02:29 PST." References: Date: Thu, 17 Dec 1998 10:23:39 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Neal Westfall wrote: > Is there an easy way to get a 3.0 source tree up to current? I will be > doing this with CTM. Can I start with my 3.0 source tree or do I need > to wipe it out and start clean with the fat delta? I didn't see any > info on how to do this without starting from an empty src dir. Can > this be done? You need to start with the "Empty" delta. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 01:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28360 for freebsd-current-outgoing; Thu, 17 Dec 1998 01:17:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28352 for ; Thu, 17 Dec 1998 01:17:55 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id KAA19841; Thu, 17 Dec 1998 10:14:15 +0100 (CET) Received: from wurzelausix (quadratix.cs.uni-sb.de [134.96.222.2]) by cs.uni-sb.de (8.9.1a/1998121400) with ESMTP id KAA10095; Thu, 17 Dec 1998 10:14:10 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:6G34X5tTmRrYVo7umbZ2W4K9e/1e7oj3@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id KAA10443; Thu, 17 Dec 1998 10:14:04 +0100 (CET) Message-Id: <199812170914.KAA10443@wurzelausix> Date: Thu, 17 Dec 1998 10:14:02 +0100 (CET) From: Alexander Leidinger Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? To: axl@iafrica.com cc: studded@dal.net, current@FreeBSD.ORG In-Reply-To: <11134.913882360@axl.noc.iafrica.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 17 Dec, Sheldon Hearn wrote: >> Now I have found the problem: mergemaster (script from ports/sysutils, >> revision 1.17) >> It creates /usr/src/sendmail/freebsd.cf. (Is the author listening?) > > No, it creates /usr/src/usr.sbin/sendmail/freebsd.cf . Strange, I have one in /usr/src/sendmail after using mergemaster (no freebsd.cf in usr.sbin/...). netchild@meta:/usr/src% find . -name freebsd.cf -print ./etc/sendmail/freebsd.cf > I would imagine that this is the offending action: > > (cd /usr/src/usr.sbin/sendmail/cf/cf && m4 ../m4/cf.m4 freebsd.mc) > freebsd.cf > chmod 444 freebsd.cf > install -c -o bin -g bin -m 644 freebsd.cf /var/tmp/temproot/etc/sendmail.cf Where is this from, a quick search shows those lines (different options for m4) only in my buildworld.log. netchild@meta:/usr/src% find ../obj -name freebsd.cf -print ../obj/elf/usr/src/etc/sendmail/freebsd.cf Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 02:17:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04780 for freebsd-current-outgoing; Thu, 17 Dec 1998 02:17:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04774; Thu, 17 Dec 1998 02:17:47 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id LAA00429; Thu, 17 Dec 1998 11:18:18 +0100 (MET) Date: Thu, 17 Dec 1998 11:17:35 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: cwt@FreeBSD.ORG, FreeBSD current mailing list , Amanda Hackers List Subject: sigchild breakage on FreeBSD 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 AmandaD (amanda backup software) is broken on FreeBSD-Current as of revision 1.42 of src/usr.sbin/inetd/inetd.c. This fix is posted to FreeBSD current because other packages might be broken for the same reason and the same sort of fix might apply. Chris, it might be useful to add this patch until the patch has been considered by the Amanda group. Description: When running amcheck -c on the client machine a zombie (selfcheck) is created. This indicates that the mother, amandad, started through inetd, does not accept the sigchild signal. The zombie stays there until either the mother accepts that signal or dies. Applicability: FreeBSD-CURRENT as of revision 1.42 of src/usr.sbin/inetd.c. Amanda version: -rw-r--r-- 1 404 601 14117 Jul 4 01:44 amandad.c amanda-2.4.1 (no patches applied, no patches found that looked applicable) Problem: inetd switches off sigchild somewhere before execing the child. Amandad does not do an extra fork to separate itself from the mother, so it inherits that blocked sigCHILD. Solution: One of the options below: 1) Switch signal back on (see fix) 2) Do an extra fork (not checked whether this works) Fix: The fix switches the SigCHILD signal back on (is switched off by inetd.c in revision 1.42). --- amandad.c Sat Jul 4 01:44:41 1998 +++ amandad.c.new Thu Dec 17 10:41:45 1998 @@ -116,6 +116,9 @@ char *errstr = NULL; unsigned long malloc_hist_1, malloc_size_1; unsigned long malloc_hist_2, malloc_size_2; +#ifdef __FreeBSD__ + sigset_t set; +#endif for(fd = 3; fd < FD_SETSIZE; fd++) { /* @@ -313,6 +316,11 @@ /* spawn child to handle request */ +#ifdef __FreeBSD__ + sigemptyset(&set); + sigaddset(&set, SIGCHLD); + sigprocmask(SIG_UNBLOCK, &set, NULL); +#endif signal(SIGCHLD, sigchild_flag); switch(fork()) { Cheers, Nick -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 02:25:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05551 for freebsd-current-outgoing; Thu, 17 Dec 1998 02:25:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05546 for ; Thu, 17 Dec 1998 02:25:20 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.054 #1) id 0zqa4L-00036k-00; Thu, 17 Dec 1998 11:50:05 +0200 From: Sheldon Hearn To: Alexander Leidinger cc: studded@dal.net, current@FreeBSD.ORG Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? In-reply-to: Your message of "Thu, 17 Dec 1998 10:14:02 +0100." <199812170914.KAA10443@wurzelausix> Date: Thu, 17 Dec 1998 11:50:05 +0200 Message-ID: <11949.913888205@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998 10:14:02 +0100, Alexander Leidinger wrote: > Strange, I have one in /usr/src/sendmail after using mergemaster > (no freebsd.cf in usr.sbin/...). > > netchild@meta:/usr/src% find . -name freebsd.cf -print > ./etc/sendmail/freebsd.cf Ah. This is the current mailing list and I'm quoting stuff out of mergemaster operation on a stable box. Dumbass me. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 03:34:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11156 for freebsd-current-outgoing; Thu, 17 Dec 1998 03:34:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA11147 for ; Thu, 17 Dec 1998 03:34:32 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id LAA63273; Thu, 17 Dec 1998 11:34:12 GMT Date: Thu, 17 Dec 1998 11:34:12 +0000 (GMT) From: Doug Rabson To: Mike Smith cc: Paul van der Zwan , current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-Reply-To: <199812162320.PAA01606@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 Wed, 16 Dec 1998, Mike Smith wrote: > > To test my theory that the -1 times are causing the error because they violate > > the protocol, I chanded the #define nfsm_v3sattr in /usr/src/sys/nfs/ > > nfsm_subs.h to use NFSV3SATTRTIME_TOSERVER in stead of NFSV3SATTRTIME_TOCLIENT. > > This makes the server ignore the time values. My test program now creates > > poth testfile1 and testfile2. > > This means that the files get the server's timestamp, which is going to > break things like make(1) which expect files to be created with the > client's time. > > > I might be wrong but I think the bug is in the client code and surfaced because > > Solaris 7 has become stricter about clients adhering to the protocol specs. > > This sounds like a good starting point; any chance of tracking down > where the time values are supposed to be set in the FreeBSD code and > fixing that, since that's what seems to be wrong...? I've been looking into this today. Its clear that we are doing the wrong thing for the attributes passed to CREATE, MKNOD and SYMLINK. I made some changes which I think should do the right thing but I can't test them against a Solaris server. One strange effect on a FreeBSD server (with or without this patch) is that the modtime of testfile1 is set to -1. I'll look into that later. Could someone test this patch and tell me if it improves things for Solaris? Index: nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.114 diff -u -r1.114 nfs_vnops.c --- nfs_vnops.c 1998/11/15 20:36:16 1.114 +++ nfs_vnops.c 1998/12/17 10:17:37 @@ -718,64 +718,7 @@ nfsm_reqhead(vp, NFSPROC_SETATTR, NFSX_FH(v3) + NFSX_SATTR(v3)); nfsm_fhtom(vp, v3); if (v3) { - if (vap->va_mode != (mode_t)VNOVAL) { - nfsm_build(tl, u_int32_t *, 2 * NFSX_UNSIGNED); - *tl++ = nfs_true; - *tl = txdr_unsigned(vap->va_mode); - } else { - nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); - *tl = nfs_false; - } - if (vap->va_uid != (uid_t)VNOVAL) { - nfsm_build(tl, u_int32_t *, 2 * NFSX_UNSIGNED); - *tl++ = nfs_true; - *tl = txdr_unsigned(vap->va_uid); - } else { - nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); - *tl = nfs_false; - } - if (vap->va_gid != (gid_t)VNOVAL) { - nfsm_build(tl, u_int32_t *, 2 * NFSX_UNSIGNED); - *tl++ = nfs_true; - *tl = txdr_unsigned(vap->va_gid); - } else { - nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); - *tl = nfs_false; - } - if (vap->va_size != VNOVAL) { - nfsm_build(tl, u_int32_t *, 3 * NFSX_UNSIGNED); - *tl++ = nfs_true; - txdr_hyper(&vap->va_size, tl); - } else { - nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); - *tl = nfs_false; - } - if (vap->va_atime.tv_sec != VNOVAL) { - if (vap->va_atime.tv_sec != time_second) { - nfsm_build(tl, u_int32_t *, 3 * NFSX_UNSIGNED); - *tl++ = txdr_unsigned(NFSV3SATTRTIME_TOCLIENT); - txdr_nfsv3time(&vap->va_atime, tl); - } else { - nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); - *tl = txdr_unsigned(NFSV3SATTRTIME_TOSERVER); - } - } else { - nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); - *tl = txdr_unsigned(NFSV3SATTRTIME_DONTCHANGE); - } - if (vap->va_mtime.tv_sec != VNOVAL) { - if (vap->va_mtime.tv_sec != time_second) { - nfsm_build(tl, u_int32_t *, 3 * NFSX_UNSIGNED); - *tl++ = txdr_unsigned(NFSV3SATTRTIME_TOCLIENT); - txdr_nfsv3time(&vap->va_mtime, tl); - } else { - nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); - *tl = txdr_unsigned(NFSV3SATTRTIME_TOSERVER); - } - } else { - nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); - *tl = txdr_unsigned(NFSV3SATTRTIME_DONTCHANGE); - } + nfsm_v3attrbuild(vap, TRUE); nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); *tl = nfs_false; } else { @@ -1261,7 +1204,6 @@ register struct vattr *vap; { register struct nfsv2_sattr *sp; - register struct nfsv3_sattr *sp3; register u_int32_t *tl; register caddr_t cp; register int32_t t1, t2; @@ -1293,10 +1235,9 @@ nfsm_fhtom(dvp, v3); nfsm_strtom(cnp->cn_nameptr, cnp->cn_namelen, NFS_MAXNAMLEN); if (v3) { - nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED + NFSX_V3SRVSATTR); + nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); *tl++ = vtonfsv3_type(vap->va_type); - sp3 = (struct nfsv3_sattr *)tl; - nfsm_v3sattr(sp3, vap); + nfsm_v3attrbuild(vap, FALSE); if (vap->va_type == VCHR || vap->va_type == VBLK) { nfsm_build(tl, u_int32_t *, 2 * NFSX_UNSIGNED); *tl++ = txdr_unsigned(major(vap->va_rdev)); @@ -1383,7 +1324,6 @@ register struct vattr *vap = ap->a_vap; register struct componentname *cnp = ap->a_cnp; register struct nfsv2_sattr *sp; - register struct nfsv3_sattr *sp3; register u_int32_t *tl; register caddr_t cp; register int32_t t1, t2; @@ -1416,20 +1356,18 @@ if (v3) { nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); if (fmode & O_EXCL) { - *tl = txdr_unsigned(NFSV3CREATE_EXCLUSIVE); - nfsm_build(tl, u_int32_t *, NFSX_V3CREATEVERF); + *tl = txdr_unsigned(NFSV3CREATE_EXCLUSIVE); + nfsm_build(tl, u_int32_t *, NFSX_V3CREATEVERF); #ifdef INET - if (!TAILQ_EMPTY(&in_ifaddrhead)) - *tl++ = IA_SIN(in_ifaddrhead.tqh_first)->sin_addr.s_addr; - else + if (!TAILQ_EMPTY(&in_ifaddrhead)) + *tl++ = IA_SIN(in_ifaddrhead.tqh_first)->sin_addr.s_addr; + else #endif - *tl++ = create_verf; - *tl = ++create_verf; + *tl++ = create_verf; + *tl = ++create_verf; } else { - *tl = txdr_unsigned(NFSV3CREATE_UNCHECKED); - nfsm_build(tl, u_int32_t *, NFSX_V3SRVSATTR); - sp3 = (struct nfsv3_sattr *)tl; - nfsm_v3sattr(sp3, vap); + *tl = txdr_unsigned(NFSV3CREATE_UNCHECKED); + nfsm_v3attrbuild(vap, FALSE); } } else { nfsm_build(sp, struct nfsv2_sattr *, NFSX_V2SATTR); @@ -1820,8 +1758,7 @@ nfsm_fhtom(dvp, v3); nfsm_strtom(cnp->cn_nameptr, cnp->cn_namelen, NFS_MAXNAMLEN); if (v3) { - nfsm_build(sp3, struct nfsv3_sattr *, NFSX_V3SRVSATTR); - nfsm_v3sattr(sp3, vap); + nfsm_v3attrbuild(vap, FALSE); } nfsm_strtom(ap->a_target, slen, NFS_MAXPATHLEN); if (!v3) { @@ -1895,8 +1832,7 @@ nfsm_fhtom(dvp, v3); nfsm_strtom(cnp->cn_nameptr, len, NFS_MAXNAMLEN); if (v3) { - nfsm_build(sp3, struct nfsv3_sattr *, NFSX_V3SRVSATTR); - nfsm_v3sattr(sp3, vap); + nfsm_v3attrbuild(vap, FALSE); } else { nfsm_build(sp, struct nfsv2_sattr *, NFSX_V2SATTR); sp->sa_mode = vtonfsv2_mode(VDIR, vap->va_mode); Index: nfsm_subs.h =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfsm_subs.h,v retrieving revision 1.21 diff -u -r1.21 nfsm_subs.h --- nfsm_subs.h 1998/05/31 20:08:57 1.21 +++ nfsm_subs.h 1998/12/17 11:23:50 @@ -235,17 +235,68 @@ (f) = ttattrf; \ } } -#define nfsm_v3sattr(s, a) \ - { (s)->sa_modetrue = nfs_true; \ - (s)->sa_mode = vtonfsv3_mode((a)->va_mode); \ - (s)->sa_uidfalse = nfs_false; \ - (s)->sa_gidfalse = nfs_false; \ - (s)->sa_sizefalse = nfs_false; \ - (s)->sa_atimetype = txdr_unsigned(NFSV3SATTRTIME_TOCLIENT); \ - txdr_nfsv3time(&(a)->va_atime, &(s)->sa_atime); \ - (s)->sa_mtimetype = txdr_unsigned(NFSV3SATTRTIME_TOCLIENT); \ - txdr_nfsv3time(&(a)->va_mtime, &(s)->sa_mtime); \ +/* If full is true, set all fields, otherwise just set mode and time fields */ +#define nfsm_v3attrbuild(a, full) \ + { if ((a)->va_mode != (mode_t)VNOVAL) { \ + nfsm_build(tl, u_int32_t *, 2 * NFSX_UNSIGNED); \ + *tl++ = nfs_true; \ + *tl = txdr_unsigned((a)->va_mode); \ + } else { \ + nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); \ + *tl = nfs_false; \ + } \ + if ((full) && (a)->va_uid != (uid_t)VNOVAL) { \ + nfsm_build(tl, u_int32_t *, 2 * NFSX_UNSIGNED); \ + *tl++ = nfs_true; \ + *tl = txdr_unsigned((a)->va_uid); \ + } else { \ + nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); \ + *tl = nfs_false; \ + } \ + if ((full) && (a)->va_gid != (gid_t)VNOVAL) { \ + nfsm_build(tl, u_int32_t *, 2 * NFSX_UNSIGNED); \ + *tl++ = nfs_true; \ + *tl = txdr_unsigned((a)->va_gid); \ + } else { \ + nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); \ + *tl = nfs_false; \ + } \ + if ((full) && (a)->va_size != VNOVAL) { \ + nfsm_build(tl, u_int32_t *, 3 * NFSX_UNSIGNED); \ + *tl++ = nfs_true; \ + txdr_hyper(&(a)->va_size, tl); \ + } else { \ + nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); \ + *tl = nfs_false; \ + } \ + if ((a)->va_atime.tv_sec != VNOVAL) { \ + if ((a)->va_atime.tv_sec != time_second) { \ + nfsm_build(tl, u_int32_t *, 3 * NFSX_UNSIGNED); \ + *tl++ = txdr_unsigned(NFSV3SATTRTIME_TOCLIENT); \ + txdr_nfsv3time(&(a)->va_atime, tl); \ + } else { \ + nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); \ + *tl = txdr_unsigned(NFSV3SATTRTIME_TOSERVER); \ + } \ + } else { \ + nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); \ + *tl = txdr_unsigned(NFSV3SATTRTIME_DONTCHANGE); \ + } \ + if ((a)->va_mtime.tv_sec != VNOVAL) { \ + if ((a)->va_mtime.tv_sec != time_second) { \ + nfsm_build(tl, u_int32_t *, 3 * NFSX_UNSIGNED); \ + *tl++ = txdr_unsigned(NFSV3SATTRTIME_TOCLIENT); \ + txdr_nfsv3time(&(a)->va_mtime, tl); \ + } else { \ + nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); \ + *tl = txdr_unsigned(NFSV3SATTRTIME_TOSERVER); \ + } \ + } else { \ + nfsm_build(tl, u_int32_t *, NFSX_UNSIGNED); \ + *tl = txdr_unsigned(NFSV3SATTRTIME_DONTCHANGE); \ + } \ } + #define nfsm_strsiz(s,m) \ { nfsm_dissect(tl,u_int32_t *,NFSX_UNSIGNED); \ -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 03:54:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA12949 for freebsd-current-outgoing; Thu, 17 Dec 1998 03:54:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (snblitz.sc.scruznet.com [165.227.132.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA12941 for ; Thu, 17 Dec 1998 03:54:43 -0800 (PST) (envelope-from brian@top.worldcontrol.com) Received: (from brian@localhost) by top.worldcontrol.com (8.9.1/8.8.8) id MAA00463 for freebsd-current@freebsd.org; Thu, 17 Dec 1998 12:01:01 GMT (envelope-from brian) Message-ID: <19981217040041.A444@top.worldcontrol.com> Date: Thu, 17 Dec 1998 04:00:41 -0800 From: Brian Litzinger To: freebsd-current@FreeBSD.ORG Subject: mpegtv linux threaded versions work with patches from lt.tar.com Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mpegtv's (http://www.mpegtv.com) real time MPEG player for Linux versions 1.0.7.8 and 1.0.8.0a2 work under -current with the linux threads patches from http://lt.tar.com Yeah! Yippie! Those versions are multi-threaded and higher performance than the 1.0.7.2 version which works under FreeBSD without the aforementioned patches. There is some small audio/video sync drifting which is not in the MPEG streams when played with my hardware MPEG decoder. (It drifts back and forth but on average stays centered) -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 03:55:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA12983 for freebsd-current-outgoing; Thu, 17 Dec 1998 03:55:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA12975 for ; Thu, 17 Dec 1998 03:55:03 -0800 (PST) (envelope-from nordwick@scam.XCF.Berkeley.EDU) Message-Id: <199812171155.DAA12975@hub.freebsd.org> Received: (qmail 9889 invoked by uid 27268); 17 Dec 1998 11:56:13 -0000 Received: from localhost (HELO scam.XCF.Berkeley.EDU) (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Dec 1998 11:56:13 -0000 To: HighWind Software Information Cc: current@FreeBSD.ORG Subject: Re: sendfile() In-Reply-To: Your message of "Thu, 17 Dec 1998 00:18:05 EST." <199812170518.AAA22593@highwind.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9886.913895772.1@scam.XCF.Berkeley.EDU> Date: Thu, 17 Dec 1998 03:56:13 -0800 From: "Jay Nordwick" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG man sendfile turns up: HISTORY sendfile() first appeared in FreeBSD 3.0.1. AUTHORS sendfile() and this manual page were written by David Greenman . BSD November 5, 1998 2 Also, in the rumor mill, I head that CDROM started using it and the load dropped way down. -jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 04:33:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19385 for freebsd-current-outgoing; Thu, 17 Dec 1998 04:33:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19378 for ; Thu, 17 Dec 1998 04:33:09 -0800 (PST) (envelope-from rkw@nomad.dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id GAA09764; Thu, 17 Dec 1998 06:32:25 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Thu, 17 Dec 1998 06:32:25 -0600 (CST) From: Richard Wackerbarth To: Mark Murray cc: current@FreeBSD.ORG Subject: Re: syncing 3.0-src tree with current In-Reply-To: <199812170823.KAA74519@greenpeace.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark, Isn't Sascha still running a cvsup server that is fed from the ctm's? If so, a reasonable alternative is to use the src tree that you have already downloaded (or read from CD) and have Sasha's cvsupd transform it into a starting place to allow you to use ctm for future updates. On Thu, 17 Dec 1998, Mark Murray wrote: > Neal Westfall wrote: > > Is there an easy way to get a 3.0 source tree up to current? I will be > > doing this with CTM. Can I start with my 3.0 source tree or do I need > > to wipe it out and start clean with the fat delta? I didn't see any > > info on how to do this without starting from an empty src dir. Can > > this be done? > > You need to start with the "Empty" delta. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 04:45:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20540 for freebsd-current-outgoing; Thu, 17 Dec 1998 04:45:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.41.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20535 for ; Thu, 17 Dec 1998 04:45:34 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id MAA00282; Thu, 17 Dec 1998 12:54:54 +0100 (CET) To: Gregory Bond cc: current@FreeBSD.ORG Subject: Re: Why no "date -a"? In-reply-to: Your message of "Thu, 17 Dec 1998 16:21:35 +1100." <199812170521.QAA13657@melba.bby.com.au> Date: Thu, 17 Dec 1998 12:54:54 +0100 Message-ID: <280.913895694@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812170521.QAA13657@melba.bby.com.au>, Gregory Bond writes: >This came up on the newsgroup today and I couldn't think of an answer. > >FreeBSD has adjtime(2) and Poul-Henning et al as nanosecond wranglers, yet no >"date -a". This must be a deliberate omission. Why? I havn't needed it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 05:52:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28327 for freebsd-current-outgoing; Thu, 17 Dec 1998 05:52:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28269 for ; Thu, 17 Dec 1998 05:51:59 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id AAA00898 for ; Fri, 18 Dec 1998 00:21:50 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA17642; Fri, 18 Dec 1998 00:21:50 +1030 Date: Fri, 18 Dec 1998 00:21:50 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: current@FreeBSD.ORG Subject: Rebuilding perl after cvsup 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 When I try and rebuild perl after running a cvsup (which removes certain of the generated files), make depend bombs out with: ===> gnu/usr.bin/perl/perl sh config_h.sh Can't find config.sh. and I have to 'make clean' and rebuild the whole thing. This presumably isn't a problem for using make world, but it bites you every time if you're rebuilding using 'make all' (which is much quicker, and usually works just fine). This is not the supported way to do things, I know, but is this problem easy to fix? Remaking perl also seems to spend a lot of time rebuilding manpages and so forth which haven't changed..I guess this is a side-effect of the generally ugly build process for PERL which I've heard rumours about :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 06:24:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01508 for freebsd-current-outgoing; Thu, 17 Dec 1998 06:24:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01502 for ; Thu, 17 Dec 1998 06:24:20 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id JAA01169; Thu, 17 Dec 1998 09:16:32 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 17 Dec 1998 09:16:32 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Doug Rabson cc: current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998, Doug Rabson wrote: > > > I might be wrong but I think the bug is in the client code and surfaced because > > > Solaris 7 has become stricter about clients adhering to the protocol specs. > > > > This sounds like a good starting point; any chance of tracking down > > where the time values are supposed to be set in the FreeBSD code and > > fixing that, since that's what seems to be wrong...? > > I've been looking into this today. Its clear that we are doing the wrong > thing for the attributes passed to CREATE, MKNOD and SYMLINK. I made some > changes which I think should do the right thing but I can't test them > against a Solaris server. One strange effect on a FreeBSD server (with or > without this patch) is that the modtime of testfile1 is set to -1. I'll > look into that later. Could someone test this patch and tell me if it > improves things for Solaris? > > Index: nfs_vnops.c > =================================================================== > RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v > retrieving revision 1.114 > diff -u -r1.114 nfs_vnops.c i'm sorry, what am i looking for? I can test, but i don't know what to report about.... -Alfred Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 06:26:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01993 for freebsd-current-outgoing; Thu, 17 Dec 1998 06:26:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01975; Thu, 17 Dec 1998 06:26:16 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: by fallout.campusview.indiana.edu (Postfix, from userid 8489) id CA67912BF; Thu, 17 Dec 1998 09:26:07 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by fallout.campusview.indiana.edu (Postfix) with ESMTP id BDD791283; Thu, 17 Dec 1998 09:26:07 -0500 (EST) Date: Thu, 17 Dec 1998 09:26:07 -0500 (EST) From: John Fieber X-Sender: jfieber@fallout.campusview.indiana.edu To: Nick Hibma Cc: cwt@FreeBSD.ORG, FreeBSD current mailing list , Amanda Hackers List Subject: Re: sigchild breakage on FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998, Nick Hibma wrote: > AmandaD (amanda backup software) is broken on FreeBSD-Current as of > revision 1.42 of src/usr.sbin/inetd/inetd.c. This fix is posted to > FreeBSD current because other packages might be broken for the same > reason and the same sort of fix might apply. Please check with version 1.43 of inetd.c. Version 1.42 was broken. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 07:06:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06722 for freebsd-current-outgoing; Thu, 17 Dec 1998 07:06:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06301 for ; Thu, 17 Dec 1998 07:04:39 -0800 (PST) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id QAA22328; Thu, 17 Dec 1998 16:04:10 +0100 (CET) Received: from cs.uni-sb.de (acc1-218.telip.uni-sb.de [134.96.113.218]) by cs.uni-sb.de (8.9.1a/1998121400) with ESMTP id QAA13659; Thu, 17 Dec 1998 16:04:08 +0100 (CET) Message-ID: <36791E21.3BE9B18C@cs.uni-sb.de> Date: Thu, 17 Dec 1998 16:07:13 +0100 From: "D. Rock" X-Mailer: Mozilla 4.5 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: Doug Rabson CC: Mike Smith , Paul van der Zwan , current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At least I can touch files again, but not really what I wanted: % touch new_file % ls -l new_file -rwsr-srw- 1 root 726616864 0 Dec 17 16:01 new_file* % rm new_file % touch new_file % ls -l new_file ----rw-r-x 1 root 10537375 0 Dec 17 16:02 new_file* (gid and permissions are set randomly) Daniel Doug Rabson schrieb: > I've been looking into this today. Its clear that we are doing the wrong > thing for the attributes passed to CREATE, MKNOD and SYMLINK. I made some > changes which I think should do the right thing but I can't test them > against a Solaris server. One strange effect on a FreeBSD server (with or > without this patch) is that the modtime of testfile1 is set to -1. I'll > look into that later. Could someone test this patch and tell me if it > improves things for Solaris? > > Index: nfs_vnops.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 07:24:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08656 for freebsd-current-outgoing; Thu, 17 Dec 1998 07:24:48 -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 HAA08538 for ; Thu, 17 Dec 1998 07:24:46 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA28637; Thu, 17 Dec 1998 10:24:26 -0500 (EST) (envelope-from wollman) Date: Thu, 17 Dec 1998 10:24:26 -0500 (EST) From: Garrett Wollman Message-Id: <199812171524.KAA28637@khavrinen.lcs.mit.edu> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812162338.PAA01733@dingo.cdrom.com> References: <199812160811.IAA37602@keep.lan.Awfulhak.org> <199812162338.PAA01733@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Pseudo-devices probably want their own bus, whose probe code would be > responsible for resolving this. No, pseudo-devices shouldn't look like bus-framework devices at all -- after all, they do not represent real hardware! (Of course, they should be constructed as KLD modules when that is possible. It isn't always possible; e.g., bpf.) Pseudo-devices should be written to dynamically allocate new units upon activation, or using some sort of external mechanism (I don't think sysctl is the right tool, but perhaps Warner's Xresources-style proposal is the right direction). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 08:33:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16396 for freebsd-current-outgoing; Thu, 17 Dec 1998 08:33:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16386 for ; Thu, 17 Dec 1998 08:33:32 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:uDxachBFYLMBdHssLktlyuxYpgshEGtw@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id SAA07757; Thu, 17 Dec 1998 18:33:22 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:4RnoEX+kQko78Ow6poenKyoYDBsJqGyp@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id SAA75584; Thu, 17 Dec 1998 18:33:20 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812171633.SAA75584@greenpeace.grondar.za> To: Kris Kennaway cc: current@FreeBSD.ORG Subject: Re: Rebuilding perl after cvsup In-Reply-To: Your message of " Fri, 18 Dec 1998 00:21:50 +1030." References: Date: Thu, 17 Dec 1998 18:33:19 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > This presumably isn't a problem for using make world, but it bites you every > time if you're rebuilding using 'make all' (which is much quicker, and usually > works just fine). This is not the supported way to do things, I know, but is > this problem easy to fix? No; it is _horrendously_ difficult. :-) For any number of simple cases, it is simple, but for the general 2.2.x/3.0.y and aout/elf combinations, the problems are _nasty_. > Remaking perl also seems to spend a lot of time rebuilding manpages and so > forth which haven't changed..I guess this is a side-effect of the generally > ugly build process for PERL which I've heard rumours about :-) Amen, brother! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 08:38:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16866 for freebsd-current-outgoing; Thu, 17 Dec 1998 08:38:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16830 for ; Thu, 17 Dec 1998 08:37:57 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id DAA01709; Fri, 18 Dec 1998 03:07:47 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA02849; Fri, 18 Dec 1998 03:07:47 +1030 Date: Fri, 18 Dec 1998 03:07:47 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Mark Murray Cc: current@FreeBSD.ORG Subject: Re: Rebuilding perl after cvsup In-Reply-To: <199812171633.SAA75584@greenpeace.grondar.za> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998, Mark Murray wrote: > Kris Kennaway wrote: > > This presumably isn't a problem for using make world, but it bites you every > > time if you're rebuilding using 'make all' (which is much quicker, and usually > > works just fine). This is not the supported way to do things, I know, but is > > this problem easy to fix? > > No; it is _horrendously_ difficult. :-) For any number of simple cases, > it is simple, but for the general 2.2.x/3.0.y and aout/elf combinations, > the problems are _nasty_. Ugh. Thankfully you don't need to rebuild PERL that often, unless something changes. I usually have NOPERL=true so it doesnt much matter. > > Remaking perl also seems to spend a lot of time rebuilding manpages and so > > forth which haven't changed..I guess this is a side-effect of the generally > > ugly build process for PERL which I've heard rumours about :-) > > Amen, brother! :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 08:43:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17356 for freebsd-current-outgoing; Thu, 17 Dec 1998 08:43:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from osiris.moc.kw ([139.141.220.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17346 for ; Thu, 17 Dec 1998 08:43:24 -0800 (PST) (envelope-from root@isis.dynip.com) Received: from osiris.moc.kw (localhost.moc.kw [127.0.0.1]) by osiris.moc.kw (8.8.8/8.8.8) with SMTP id TAA11757 for ; Thu, 17 Dec 1998 19:39:45 +0300 (AST) From: Charlie Roots To: freebsd-current@FreeBSD.ORG Subject: FreeBSD 3.0 RELEASE, or CURRENT that can compile NEEDED URGENLY Reply-To: root@isis.dynip.com X-Mailer: KMail [version 0.4.3] Date: Thu, 17 Dec 1998 19:22:26 +0300 MIME-Version: 1.0 Message-Id: <98121719393900.11254@osiris.moc.kw> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys I've been using FreeBSD as I learn it from scratch, I even downloaded it from the net some year and half ago since 2.2.2-RELEASE which was so stable and tolerated my noviceness very nicely. As I learn to do good, sometimes I learn to do BAD, One of the mistakes I did some eight months ago, that I learned how to use CVSUP, and I felt that I must be in heaven to be able to upgrade a full unix system over the net and for FREE. What happened is I upgraded to 3.0-Current (then), and there was a really annoying bug that remained with me whenever I reboot the machine using shutdown -r command, the system goes into PANIc, and next time I have to keep praying that nothing on the filesystems were FUCKED. Fortunately, I was able to discovery thaat hittinh CNRL-ALT-DEL combination did not panic neither that operating system nor me. Next I CVSUPED to 3.0-CURRENT recently as of few days, and I discovered that FreeBSD changed the binary format to ELF, so I read why they did that, and accepted the cause greatfully. When I try to compile the system either on an aout basis or elf basis, the compile fails. So I though to give some desperate email to this list in the hope that someone will have an answer for this problem. All I got was a single email from a very arrogant guy telling me in short to read the archives. I sent him a reply indicating that I have a slow connection to the net and I am trying to get the whole fucken archieve over to my machine so I can spend some year and half searching for the answer. Then I though man you are too stupid to run current, so I cvsuped 3.0-RELEASE in the hope that I so be stupid, and the system compiles. All hours of cvsupping went in vane, Current, and RELESAE both won't compile whatever I do, even to create some symbolic links or manipulating makefiles to bypass a glitchy area, but nothing still successful. ]Some NO-arrogant helpful user tryt to tell me why: Current is not compiling and giving "__error" unknown from text segment. ]Release is not compiling and giving "ld:" not found something .. until I get the HOLLY archieve and read it. I is worth noting that all the goodies in current-ports are not compiling too now. thanks in advance, and sorry for my nervousness. if my email address fails, try osiris2002@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 08:52:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18389 for freebsd-current-outgoing; Thu, 17 Dec 1998 08:52:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18382; Thu, 17 Dec 1998 08:52:36 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id IAA20117; Thu, 17 Dec 1998 08:52:24 -0800 (PST) Date: Thu, 17 Dec 1998 08:52:24 -0800 (PST) From: Chris Timmons To: Nick Hibma cc: cwt@FreeBSD.ORG, FreeBSD current mailing list , Amanda Hackers List Subject: Re: sigchild breakage on FreeBSD 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 Nick, Thanks for your detailed report. I will try and get the FreeBSD amanda24 port up-to-date RSN. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 08:53:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18648 for freebsd-current-outgoing; Thu, 17 Dec 1998 08:53:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dt053n73.san.rr.com (dt053n73.san.rr.com [204.210.34.115]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18642 for ; Thu, 17 Dec 1998 08:53:38 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053n73.san.rr.com (8.8.8/8.8.8) with ESMTP id IAA14078; Thu, 17 Dec 1998 08:52:34 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <367936D1.20D17414@gorean.org> Date: Thu, 17 Dec 1998 08:52:33 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1101 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alexander Leidinger CC: axl@iafrica.com, current@FreeBSD.ORG Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? References: <199812170914.KAA10443@wurzelausix> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First off, thanks to Sheldon for cc'ing me. My new job has left near zero time for freebsd stuff the last two months. Personal note, last time I checked sheldon I still couldn't send you mail at this address. If you could send me an address on another mailhost I will answer your other letters re mergemaster. :) Alexander Leidinger wrote: > >> Now I have found the problem: mergemaster (script from ports/sysutils, > >> revision 1.17) > >> It creates /usr/src/sendmail/freebsd.cf. (Is the author listening?) Mergemaster itself does not create anything. It relies entirely on /usr/src/etc/Makefile to create the proper files and install them to the temporary root "filesystem." So the freebsd.cf file is created wherever that makefile tells it to be. In my experience, it is created in /usr/src/usr.sbin/sendmail/cf/cf/freebsd.cf if I forget to mount /usr/obj before I run mergemaster, or if /usr/obj is an empty directory. If there is a /usr/obj populated with the proper directory structure (as a side-effect of a previous or currently running buildworld) then freebsd.cf is created in it's corresponding /usr/obj directory. I actually sent in a request to have that behaviour changed quite a while ago since TMK that's the last thing that is created in the /usr/src tree "sometimes," but my request was ignored. Maybe now someone will give it another look. Happy holidays to all, Doug -- Now you sailors know where your women come for love. "Zoot Suit Riot" - Cherry Poppin' Daddies To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 09:01:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19324 for freebsd-current-outgoing; Thu, 17 Dec 1998 09:01:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19308 for ; Thu, 17 Dec 1998 09:01:42 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id DAA00227; Fri, 18 Dec 1998 03:31:32 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA09377; Fri, 18 Dec 1998 03:31:31 +1030 Date: Fri, 18 Dec 1998 03:31:31 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Studded Cc: Alexander Leidinger , axl@iafrica.com, current@FreeBSD.ORG Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? In-Reply-To: <367936D1.20D17414@gorean.org> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998, Studded wrote: > Mergemaster itself does not create anything. It relies entirely on > /usr/src/etc/Makefile to create the proper files and install them to the > temporary root "filesystem." So the freebsd.cf file is created wherever that > makefile tells it to be. In my experience, it is created in > /usr/src/usr.sbin/sendmail/cf/cf/freebsd.cf if I forget to mount /usr/obj > before I run mergemaster, or if /usr/obj is an empty directory. If there is > a /usr/obj populated with the proper directory structure (as a side-effect > of a previous or currently running buildworld) then freebsd.cf is created in > it's corresponding /usr/obj directory. Somewhere in here doesn't respect NO_SENDMAIL (e.g. you don't care about a freebsd.cf if you're using qmail). This is a minor nit when using mergemaster, as it always presents that file to be updated. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 09:16:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20442 for freebsd-current-outgoing; Thu, 17 Dec 1998 09:16:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20385 for ; Thu, 17 Dec 1998 09:15:53 -0800 (PST) (envelope-from netchild@wurzelausix.CS.Uni-SB.DE) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id SAA23296; Thu, 17 Dec 1998 18:15:10 +0100 (CET) Received: from wurzelausix (quadratix.cs.uni-sb.de [134.96.222.2]) by cs.uni-sb.de (8.9.1a/1998121400) with ESMTP id SAA15262; Thu, 17 Dec 1998 18:15:01 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (IDENT:ZmTbqHLd5j/fB2MgN9DsZH2t2zeNxuFw@localhost [127.0.0.1]) by wurzelausix (8.9.1/wjp/19980821) with ESMTP id SAA20795; Thu, 17 Dec 1998 18:14:55 +0100 (CET) Message-Id: <199812171714.SAA20795@wurzelausix> Date: Thu, 17 Dec 1998 18:14:53 +0100 (CET) From: Alexander Leidinger Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? To: Studded@gorean.org cc: axl@iafrica.com, current@FreeBSD.ORG In-Reply-To: <367936D1.20D17414@gorean.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Dec, Studded wrote: > Mergemaster itself does not create anything. It relies entirely on > /usr/src/etc/Makefile to create the proper files and install them to the > temporary root "filesystem." So the freebsd.cf file is created wherever that > makefile tells it to be. In my experience, it is created in > /usr/src/usr.sbin/sendmail/cf/cf/freebsd.cf if I forget to mount /usr/obj > before I run mergemaster, or if /usr/obj is an empty directory. If there is > a /usr/obj populated with the proper directory structure (as a side-effect > of a previous or currently running buildworld) then freebsd.cf is created in > it's corresponding /usr/obj directory. In my situation it goes to /usr/src/etc/sendmail/ and I have a populatet /usr/obj (make buildworld; mergemaster) and there is an usr/src/usr.sbin/sendmail/cf/cf/freebsd.cf from the buildworld. Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 09:26:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21099 for freebsd-current-outgoing; Thu, 17 Dec 1998 09:19:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21091 for ; Thu, 17 Dec 1998 09:19:51 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id MAA01383; Thu, 17 Dec 1998 12:20:59 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 17 Dec 1998 12:20:59 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Charlie Roots cc: osiris2002@yahoo.com, freebsd-current@freebsd.org Subject: Re: FreeBSD 3.0 RELEASE, or CURRENT that can compile NEEDED URGENLY In-Reply-To: <98121719393900.11254@osiris.moc.kw> 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, 17 Dec 1998, Charlie Roots wrote: > Hi guys > > I've been using FreeBSD as I learn it from scratch, > I even downloaded it from the net some year and half ago since 2.2.2-RELEASE > which was so stable and tolerated my noviceness very nicely. FreeBSD-2.2-stable is newbie friendly, 3.0-current is a minefield for newbies, think *BOOM*. > As I learn to do good, sometimes I learn to do BAD, > One of the mistakes I did some eight months ago, that I learned how to use > CVSUP, and I felt that I must be in heaven to be able to upgrade a full unix > system over the net and for FREE. > > What happened is I upgraded to 3.0-Current (then), and there was a > really annoying bug that remained with me whenever I reboot the machine > using shutdown -r command, the system goes into PANIc, and next time I have > to keep praying that nothing on the filesystems were FUCKED. ^^^^^^ um, public list, think "this is archived forever" you're not being abusive, but i doubt you want this to show up in a web search one day with your name attached. :) > Fortunately, I was able to discovery thaat hittinh CNRL-ALT-DEL combination > did not panic neither that operating system nor me. > > Next I CVSUPED to 3.0-CURRENT recently as of few days, and I discovered > that FreeBSD changed the binary format to ELF, so I read why they did that, > and accepted the cause greatfully. When I try to compile the system either > on an aout basis or elf basis, the compile fails. *cough* again, 3.0 is not newbie friendly, keep reading i have some advice. :) > So I though to give some desperate email to this list in the hope that someone > will have an answer for this problem. All I got was a single email from a > very arrogant guy telling me in short to read the archives. The FreeBSD team works very hard to make sure the tree will build under any system, however this isn't always possible whether you followed directions or not. Here's what may fix things: rm -rf /usr/obj chflags -noschg /usr/obj rm -rf /usr/obj echo OBJFORMAT=elf > /etc/objformat cd /usr/src make includes make clean make aout-to-elf (don't forget to recompile your kernel and install it afterwards if this works) If this doesn't do it for you, I recommend backing up your /etc and forcing an upgrade with sysinstall, considering how broken your box is at this point it's really the only/best option. you can download a newer installdisk from current.freebsd.org. Better yet, if you can't name anything specific from 3.0 that you need, reinstall 2.2-stable. You can get SNAP install disks for 3.0 and 2.2 from ftp://current.freebsd.org > I sent him a reply indicating that I have a slow connection to the net and > I am trying to get the whole fucken archieve over to my machine so I can > spend some year and half searching for the answer. > > Then I though man you are too stupid to run current, so I cvsuped 3.0-RELEASE > in the hope that I so be stupid, and the system compiles. uh? Generally, if you think you can't do something, then you may want to hold off till you understand the implications better. > > All hours of cvsupping went in vane, Current, and RELESAE both > won't compile whatever I do, even to create some symbolic links > or manipulating makefiles to bypass a glitchy area, but nothing still successful. > > ]Some NO-arrogant helpful user tryt to tell me why: > > Current is not compiling and giving "__error" unknown from text segment. > ]Release is not compiling and giving "ld:" not found something .. > > until I get the HOLLY archieve and read it. This was in the archives a LONG time ago but i forget what the solution was. > > I is worth noting that all the goodies in current-ports are not compiling too now. > > thanks in advance, and sorry for my nervousness. > if my email address fails, try > osiris2002@yahoo.com i'm cc'ing to that address. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 09:28:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21844 for freebsd-current-outgoing; Thu, 17 Dec 1998 09:28:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21835; Thu, 17 Dec 1998 09:28:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id JAA93559; Thu, 17 Dec 1998 09:28:16 -0800 (PST) (envelope-from dillon) Date: Thu, 17 Dec 1998 09:28:16 -0800 (PST) From: Matthew Dillon Message-Id: <199812171728.JAA93559@apollo.backplane.com> To: Nick Hibma Cc: cwt@FreeBSD.ORG, FreeBSD current mailing list , Amanda Hackers List Subject: Re: sigchild breakage on FreeBSD References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :AmandaD (amanda backup software) is broken on FreeBSD-Current as of :revision 1.42 of src/usr.sbin/inetd/inetd.c. This fix is posted to :FreeBSD current because other packages might be broken for the same :... : :Description: : :When running amcheck -c on the client machine a zombie :(selfcheck) is created. This indicates that the mother, amandad, :started through inetd, does not accept the sigchild signal. The zombie :stays there until either the mother accepts that signal or dies. I'm hoping this is fixed with revision 1.43 of inetd.c -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 09:54:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24314 for freebsd-current-outgoing; Thu, 17 Dec 1998 09:54:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24308 for ; Thu, 17 Dec 1998 09:54:12 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 0zqhZq-0001tb-00; Thu, 17 Dec 1998 19:51:06 +0200 From: Sheldon Hearn To: Alfred Perlstein cc: Charlie Roots , osiris2002@yahoo.com, freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD 3.0 RELEASE, or CURRENT that can compile NEEDED URGENLY In-reply-to: Your message of "Thu, 17 Dec 1998 12:20:59 EST." Date: Thu, 17 Dec 1998 19:51:06 +0200 Message-ID: <7290.913917066@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998 12:20:59 EST, Alfred Perlstein wrote: > Here's what may fix things: > > rm -rf /usr/obj > chflags -noschg /usr/obj ^^^ chflags -R -noschg /usr/obj Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 10:00:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24901 for freebsd-current-outgoing; Thu, 17 Dec 1998 10:00:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24891 for ; Thu, 17 Dec 1998 10:00:45 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA01500; Thu, 17 Dec 1998 13:02:32 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 17 Dec 1998 13:02:32 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Charlie Roots cc: osiris2002@yahoo.com, freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD 3.0 RELEASE, or CURRENT that can compile NEEDED URGENLY In-Reply-To: <98121720280801.11254@osiris.moc.kw> 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, 17 Dec 1998, Charlie Roots wrote: > Thanks very much Mr. Alfred. > Your advice successfully reached my machine. > at least I'm capable of running sendmail on a vertual host :-) > > I'll try the things you mentioned , starting from the least invasive and up. > > Can't tell you how much I appreciate your cooperation. > > Sorry again for my nervousness on the list > bye for now and hoping for further cooperation. ok, please post what worked for you back to the list, anyone facing the same problem might pick it up in the archives and it could also be of use to them. thanks, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 10:01:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24982 for freebsd-current-outgoing; Thu, 17 Dec 1998 10:01:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24977 for ; Thu, 17 Dec 1998 10:01:57 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA01505; Thu, 17 Dec 1998 13:03:31 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 17 Dec 1998 13:03:31 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Sheldon Hearn cc: Charlie Roots , osiris2002@yahoo.com, freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD 3.0 RELEASE, or CURRENT that can compile NEEDED URGENLY In-Reply-To: <7290.913917066@axl.noc.iafrica.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, 17 Dec 1998, Sheldon Hearn wrote: > > > On Thu, 17 Dec 1998 12:20:59 EST, Alfred Perlstein wrote: > > > Here's what may fix things: > > > > rm -rf /usr/obj > > chflags -noschg /usr/obj > ^^^ > chflags -R -noschg /usr/obj ack, you're correct, thanks. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current > Ciao, > Sheldon. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 11:42:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06675 for freebsd-current-outgoing; Thu, 17 Dec 1998 11:42:28 -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 LAA06669; Thu, 17 Dec 1998 11:42:27 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA03006; Thu, 17 Dec 1998 11:31:04 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdfc3003; Thu Dec 17 19:31:03 1998 Date: Thu, 17 Dec 1998 11:30:59 -0800 (PST) From: Julian Elischer To: David Greenman cc: "Marc G. Fournier" , freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: any way of gleaming info from these? In-Reply-To: <199812170748.XAA19152@root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Dec 1998, David Greenman wrote: > >On Wed, 16 Dec 1998, David Greenman wrote: > > > >> >vnode_pager_putpages: residual I/O 4096 at 113 > >> >vnode_pager_putpages: I/O error 6 > >> >vnode_pager_putpages: residual I/O 4096 at 113 > >> >vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 > >> >vnode_pager_putpages: I/O error 6 > >> >vnode_pager_putpages: residual I/O 4096 at 113 > >> > > >> >maybe its totally impossible, but is there no way of detailing which drive > >> >is causing this? or is it not a drive? > >> > >> Error 6 is ENXIO - device not configured. This might happen if the device > >> is SCSI and it loses power/goes offline. I can't think of any other reasons > >> offhand. > > > >Hrmmm...is vnode_pager_putpages a 'file system' error, or a 'swap' error? > >The system is locked up right now, awaiting someone to get down to the > >office and reboot it. > > vnode_pager_putpages is a routine, not an error (well...:-)). I don't know > what is returning ENXIO, but putpages just calls the filesystem VOP_PUTPAGES > entry, so you'd have to look at that. vnode_pager_putpages isn't usually > called very often in a typical system - it's used when mapped/modified file > pages need to be written back to the backing file, which doesn't normally > happen on a typical system (modified pages are usually backed by swap, not > the file). > > >Looking through /usr/src/sys, the error message is generated in > >vm/vnode_pager.c...which, to me, would indicate swap space? > > No, the swap_pager pages out to swap. The vnode_pager pages out to files. I THINK the vnode pager is called if you are writing to a mmapped file, right? > > -DG > > David Greenman > Co-founder/Principal Architect, The FreeBSD Project > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 11:44:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06898 for freebsd-current-outgoing; Thu, 17 Dec 1998 11:44:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles141.castles.com [208.214.165.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06845 for ; Thu, 17 Dec 1998 11:43:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA07169; Thu, 17 Dec 1998 11:41:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812171941.LAA07169@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Garrett Wollman cc: Mike Smith , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 17 Dec 1998 10:24:26 EST." <199812171524.KAA28637@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Dec 1998 11:41:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > Pseudo-devices probably want their own bus, whose probe code would be > > responsible for resolving this. > > No, pseudo-devices shouldn't look like bus-framework devices at all -- > after all, they do not represent real hardware! > > (Of course, they should be constructed as KLD modules when that is > possible. It isn't always possible; e.g., bpf.) > > Pseudo-devices should be written to dynamically allocate new units > upon activation, or using some sort of external mechanism (I don't > think sysctl is the right tool, but perhaps Warner's Xresources-style > proposal is the right direction). Sysctl is just an access mechanism; I'm starting to think Warner's proposal is going to be a fairly good compromise too. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 11:53:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08527 for freebsd-current-outgoing; Thu, 17 Dec 1998 11:53:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08510; Thu, 17 Dec 1998 11:53:17 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id LAA25533; Thu, 17 Dec 1998 11:52:59 -0800 (PST) Message-Id: <199812171952.LAA25533@root.com> To: Julian Elischer cc: "Marc G. Fournier" , freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: any way of gleaming info from these? In-reply-to: Your message of "Thu, 17 Dec 1998 11:30:59 PST." From: David Greenman Reply-To: dg@root.com Date: Thu, 17 Dec 1998 11:52:59 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> >vnode_pager_putpages: residual I/O 4096 at 113 >> >> >vnode_pager_putpages: I/O error 6 >> >> >vnode_pager_putpages: residual I/O 4096 at 113 >> >> >vnode_pager_putpag_putpage_pager_putpages: residual I/O 4096 at 113 >> >> >vnode_pager_putpages: I/O error 6 >> >> >vnode_pager_putpages: residual I/O 4096 at 113 >> >> > >> >> >maybe its totally impossible, but is there no way of detailing which drive >> >> >is causing this? or is it not a drive? >> >> >> >> Error 6 is ENXIO - device not configured. This might happen if the device >> >> is SCSI and it loses power/goes offline. I can't think of any other reasons >> >> offhand. >> > >> >Hrmmm...is vnode_pager_putpages a 'file system' error, or a 'swap' error? >> >The system is locked up right now, awaiting someone to get down to the >> >office and reboot it. >> >> vnode_pager_putpages is a routine, not an error (well...:-)). I don't know >> what is returning ENXIO, but putpages just calls the filesystem VOP_PUTPAGES >> entry, so you'd have to look at that. vnode_pager_putpages isn't usually >> called very often in a typical system - it's used when mapped/modified file >> pages need to be written back to the backing file, which doesn't normally >> happen on a typical system (modified pages are usually backed by swap, not >> the file). >> >> >Looking through /usr/src/sys, the error message is generated in >> >vm/vnode_pager.c...which, to me, would indicate swap space? >> >> No, the swap_pager pages out to swap. The vnode_pager pages out to files. > >I THINK the vnode pager is called if you are writing to a mmapped file, >right? Yes, if it is mapped shared and writable. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 11:55:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08976 for freebsd-current-outgoing; Thu, 17 Dec 1998 11:55:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08951 for ; Thu, 17 Dec 1998 11:55:33 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id OAA06535 for ; Thu, 17 Dec 1998 14:58:51 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 17 Dec 1998 14:58:51 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: anyone notice the flurry of warnings when compiling kernel? 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 compiling a kernel spews a LOT of warnings, but the compile works fine and the resulting kernel seems ok. (yes i made clean) ../../kern/kern_mib.c:96: warning: `sysctl___kern_ngroups' defined but not used ../../kern/kern_mib.c:98: warning: `sysctl___kern_job_control' defined but not used ../../kern/subr_devstat.c:245: warning: `sysctl___kern_devstat_generation' defined but not used ../../kern/subr_devstat.c:247: warning: `sysctl___kern_devstat_version' defined but not used just FYI. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 12:28:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12417 for freebsd-current-outgoing; Thu, 17 Dec 1998 12:28:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from omahpop1.omah.uswest.net (omahpop1.omah.uswest.net [204.26.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA12410 for ; Thu, 17 Dec 1998 12:28:34 -0800 (PST) (envelope-from opsys@open-systems.net) Received: (qmail 5074 invoked by alias); 17 Dec 1998 20:28:17 -0000 Delivered-To: fixup-current@FreeBSD.ORG@fixme Received: (qmail 5057 invoked by uid 0); 17 Dec 1998 20:28:16 -0000 Received: from dialupd191.ne.uswest.net (HELO pinkfloyd.open-systems.net) (209.180.98.191) by omahpop1.omah.uswest.net with SMTP; 17 Dec 1998 20:28:16 -0000 Date: Thu, 17 Dec 1998 14:28:15 -0600 (CST) From: "Open Systems Inc." To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: anyone notice the flurry of warnings when compiling kernel? 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 Yeah noticed it last night when building a new kernel. I didnt think this would slip by anyone :-) Just looking up for a second while compiling the kernel bombards you with these. Seems harmless enough though. Chris -- "Join Team-FreeBSD on cracking RC5-64! grab you client now and HELP OUT! http://www.distributed.net/cgi/select.cgi" ===================================| Open Systems FreeBSD Consulting. FreeBSD 2.2.8 is available now! | Phone: 402-573-9124 -----------------------------------| 3335 N. 103 Plaza #14, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 12:47:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14398 for freebsd-current-outgoing; Thu, 17 Dec 1998 12:47:12 -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 MAA14391 for ; Thu, 17 Dec 1998 12:47:08 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id HAA19912; Fri, 18 Dec 1998 07:59:39 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812172059.HAA19912@cimlogic.com.au> Subject: Re: FreeBSD 3.0 RELEASE, or CURRENT that can compile NEEDED URGENLY In-Reply-To: from Alfred Perlstein at "Dec 17, 98 12:20:59 pm" To: bright@hotjobs.com (Alfred Perlstein) Date: Fri, 18 Dec 1998 07:59:38 +1100 (EST) Cc: root@isis.dynip.com, osiris2002@yahoo.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred, I have a few problems with your advice to someone who shouldn't be building from source on a single machine with a poor net connection. Alfred Perlstein wrote: [ build advice ] > rm -rf /usr/obj rm -rf /usr/obj/* > chflags -noschg /usr/obj chflags -R noschg /usr/obj > rm -rf /usr/obj rm -rf /usr/obj/* > echo OBJFORMAT=elf > /etc/objformat Don't do that. If a 3.0-RELEASE system has been installed, it will default to ELF. > cd /usr/src > make includes Don't do that. Installing include files without the corresponding libraries is what causes undefined references to __error. The make world procedure handles that correctly. > make clean Not necessary if you've rm'd /usr/obj/*. > make aout-to-elf Do this with a clean /etc/make.conf. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 13:23:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18115 for freebsd-current-outgoing; Thu, 17 Dec 1998 13:23:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18103 for ; Thu, 17 Dec 1998 13:23:33 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id VAA64758; Thu, 17 Dec 1998 21:23:48 GMT Date: Thu, 17 Dec 1998 21:23:48 +0000 (GMT) From: Doug Rabson To: Alfred Perlstein cc: current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998, Alfred Perlstein wrote: > > On Thu, 17 Dec 1998, Doug Rabson wrote: > > > > > I might be wrong but I think the bug is in the client code and surfaced because > > > > Solaris 7 has become stricter about clients adhering to the protocol specs. > > > > > > This sounds like a good starting point; any chance of tracking down > > > where the time values are supposed to be set in the FreeBSD code and > > > fixing that, since that's what seems to be wrong...? > > > > I've been looking into this today. Its clear that we are doing the wrong > > thing for the attributes passed to CREATE, MKNOD and SYMLINK. I made some > > changes which I think should do the right thing but I can't test them > > against a Solaris server. One strange effect on a FreeBSD server (with or > > without this patch) is that the modtime of testfile1 is set to -1. I'll > > look into that later. Could someone test this patch and tell me if it > > improves things for Solaris? > > > > Index: nfs_vnops.c > > =================================================================== > > RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v > > retrieving revision 1.114 > > diff -u -r1.114 nfs_vnops.c > > i'm sorry, what am i looking for? I can test, but i don't know > what to report about.... The original problem was that with this test program: #include main() { int rv; rv=open("testfile1",O_CREAT|O_RDWR|O_EXCL,0666); if ( rv < 0 ) perror("testfile1"); rv=open("testfile2",O_CREAT|O_RDWR,0666); if ( rv < 0 ) perror("testfile2"); } the first create succeeded but the second failed. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 13:26:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18339 for freebsd-current-outgoing; Thu, 17 Dec 1998 13:26:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18331 for ; Thu, 17 Dec 1998 13:26:20 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id PAA01921; Thu, 17 Dec 1998 15:25:46 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812172125.PAA01921@ns.tar.com> From: "Richard Seaman, Jr." To: "Mike Smith" Cc: "Julian Elischer" , "current@freebsd.org" Date: Thu, 17 Dec 98 15:25:46 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Linux Threads patches available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Dec 1998 03:41:59 -0800, Mike Smith wrote: >I've had a (quick) look at your current webpage; thanks for collecting >all this in one place. Would you care to summarise the changes in a >little more detail, and perhaps sort them into 'non-intrusive' and >'intrusive' groups so that we can commit the first set and do whatever >needs to be done to resolve any problems with the second ASAP? I've added a summary at http://lt.tar.com/patchsum.html. I can send to you if its inconvenient to read it there. I thought it was a little long to post to this list, but it could be done if someone wants it that way. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 13:39:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20555 for freebsd-current-outgoing; Thu, 17 Dec 1998 13:39:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20550 for ; Thu, 17 Dec 1998 13:39:06 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id VAA64789; Thu, 17 Dec 1998 21:39:33 GMT Date: Thu, 17 Dec 1998 21:39:33 +0000 (GMT) From: Doug Rabson To: "D. Rock" cc: Mike Smith , Paul van der Zwan , current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-Reply-To: <36791E21.3BE9B18C@cs.uni-sb.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, 17 Dec 1998, D. Rock wrote: > At least I can touch files again, but not really what I wanted: > % touch new_file > % ls -l new_file > -rwsr-srw- 1 root 726616864 0 Dec 17 16:01 new_file* > % rm new_file > % touch new_file > % ls -l new_file > ----rw-r-x 1 root 10537375 0 Dec 17 16:02 new_file* > > (gid and permissions are set randomly) Well thats a start anyway. Can you send me another packet trace showing what happens. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 13:41:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20922 for freebsd-current-outgoing; Thu, 17 Dec 1998 13:41:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20917 for ; Thu, 17 Dec 1998 13:41:46 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id VAA64820; Thu, 17 Dec 1998 21:42:46 GMT Date: Thu, 17 Dec 1998 21:42:46 +0000 (GMT) From: Doug Rabson To: Mike Smith cc: Paul van der Zwan , current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998, Doug Rabson wrote: > .... One strange effect on a FreeBSD server (with or without this > patch) is that the modtime of testfile1 is set to -1. I'll look into > that later. It turns out that there is a minor problem with ufs_setattr(). The setting of atime and mtime is confused (this appeared in revision 1.91 I think). Index: ufs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ufs/ufs_vnops.c,v retrieving revision 1.101 diff -u -r1.101 ufs_vnops.c --- ufs_vnops.c 1998/12/09 02:06:27 1.101 +++ ufs_vnops.c 1998/12/17 21:41:52 @@ -506,9 +506,9 @@ if (vap->va_mtime.tv_sec != VNOVAL) ip->i_flag |= IN_CHANGE | IN_UPDATE; ufs_itimes(vp); - if (vap->va_mtime.tv_sec != VNOVAL) - ip->i_atime = vap->va_atime.tv_sec; if (vap->va_atime.tv_sec != VNOVAL) + ip->i_atime = vap->va_atime.tv_sec; + if (vap->va_mtime.tv_sec != VNOVAL) ip->i_mtime = vap->va_mtime.tv_sec; error = UFS_UPDATE(vp, (struct timeval *)0, (struct timeval *)0, 0); -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 14:04:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24562 for freebsd-current-outgoing; Thu, 17 Dec 1998 14:04:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24556 for ; Thu, 17 Dec 1998 14:04:08 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id RAA17287; Thu, 17 Dec 1998 17:03:59 -0500 (EST) (envelope-from luoqi) Date: Thu, 17 Dec 1998 17:03:59 -0500 (EST) From: Luoqi Chen Message-Id: <199812172203.RAA17287@lor.watermarkgroup.com> To: lists@tar.com, mike@smith.net.au Subject: Re: Linux Threads patches available Cc: current@FreeBSD.ORG, nate@mt.sri.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For the sake of reestablishing our compatibility with Linux, I think > that your current code should be strongly considered. As for the > eventual fate of threading in the FreeBSD kernel, we're still really > dependant on the availibility of development resources here, either in > the form of willing and able volunteers or funding which would allow us > to secure the individuals able to do the work. > Just an FYI for those interested, I have been working on address space sharing on SMP with certain success. This would allow multiple threads of the same process running on different cpus simultaneously. It's a prerequisite for threading to be useful on a multiprocessor machine. A set of patch is available at http://www.freebsd.org/~luoqi/pmap.diff . -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 14:08:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24906 for freebsd-current-outgoing; Thu, 17 Dec 1998 14:08:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24901 for ; Thu, 17 Dec 1998 14:08:52 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id RAA17346; Thu, 17 Dec 1998 17:08:43 -0500 (EST) (envelope-from luoqi) Date: Thu, 17 Dec 1998 17:08:43 -0500 (EST) From: Luoqi Chen Message-Id: <199812172208.RAA17346@lor.watermarkgroup.com> To: julian@whistle.com, mike@smith.net.au Subject: Re: Linux Threads patches available Cc: current@FreeBSD.ORG, lists@tar.com, nate@mt.sri.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As I said in other mail. This may not be perfect but if we don't > make a start on threads, we'll never get to the end.. This seems like > a fair place to start. I don't see that implimenting it would be > detrimental to the existing system.. > I agree. There have been much talking about kernel threads, but nobody actually works on it. I say it's time to get our hands dirty. > I would vote for an inclusion to allow others to start experimenting > with linux-threads based software, > (note there is now a linux-threads based java JVM.) > > thoughts all? > 4.0-KTHREAD branch? > julian > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 14:48:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29397 for freebsd-current-outgoing; Thu, 17 Dec 1998 14:48:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29392 for ; Thu, 17 Dec 1998 14:48:54 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id QAA03892 for ; Thu, 17 Dec 1998 16:48:45 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812172248.QAA03892@ns.tar.com> From: "Richard Seaman, Jr." To: "current@freebsd.org" Date: Thu, 17 Dec 98 16:48:45 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Linux Threads patches available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Dec 98 16:41:04 -0600, Richard Seaman, Jr. wrote: >The linux threads patches are available at http://lt.tar.com/ Ok. I found a mistake in the linux threads port (liblinuxthreads.tar.gz). You can either re-download the corrected version or apply this in the liblinuxthreads directory. *** condvar.c~ Fri Dec 4 16:58:13 1998 --- condvar.c Thu Dec 17 16:20:46 1998 *************** *** 71,77 **** { volatile pthread_descr self = thread_self(); int retsleep; ! #ifndef __FreeBSD__ sigset_t unblock, initial_mask; sigjmp_buf jmpbuf; --- 71,77 ---- { volatile pthread_descr self = thread_self(); int retsleep; ! #ifndef USETHR_FUNCTIONS sigset_t unblock, initial_mask; sigjmp_buf jmpbuf; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 16:10:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10441 for freebsd-current-outgoing; Thu, 17 Dec 1998 16:10:14 -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 QAA10415 for ; Thu, 17 Dec 1998 16:10:04 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA13024; Thu, 17 Dec 1998 16:02:24 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpda13022; Fri Dec 18 00:02:21 1998 Message-ID: <36799B88.2781E494@whistle.com> Date: Thu, 17 Dec 1998 16:02:16 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Brian Feldman CC: "current@FreeBSD.ORG" Subject: Re: Linux Threads patches available References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > For one, I object. Keep it as a patchset, or make a vendor > branch, but the overhead and memory use of these modifications > needs to be considered carefully! I know I did much of the > LinuxThreads work, and would love to see > it going into the kernel, but the ramifications need to be > examined. I've been looking closely at the linux_clone() and signal changes as modified by Richard. I really see no change that I consider harmful. I won't check this in without a couple of core sponsors but I think that the patches as they stand are really close enough to production-quality to be usable. A slight change might be to make the process signal structure a zone allocated item rather than a malloc'd structure, however I don't think that that should be a real problem. The sructure is 328 (?) bytes long, but it already exists. The fields are simply being shifted from one place to another. The biggest thing is the (struct sigacts) which moves from the u area to kvm. Since the U area is fixed in size (always has a page available) We do lose some KVM. However with the amount of work going into Linux Threads we really will gain by piggybacking on this, and we will need these changes anyway to be able to develope and POSIX complient code. People have been very silent on thi which is amazing considering what a step forwards this is... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 16:45:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14742 for freebsd-current-outgoing; Thu, 17 Dec 1998 16:45:29 -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 QAA14737 for ; Thu, 17 Dec 1998 16:45:26 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA22820; Fri, 18 Dec 1998 11:15:05 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <36799B88.2781E494@whistle.com> Date: Fri, 18 Dec 1998 11:15:57 +1030 (CST) From: "Daniel O'Connor" To: Julian Elischer Subject: Re: Linux Threads patches available Cc: "current@FreeBSD.ORG" Cc: "current@FreeBSD.ORG" , Brian Feldman Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Dec-98 Julian Elischer wrote: > People have been very silent on thi which is amazing > considering what a step forwards this is... Personally the end result sounds very very nice, but the technical discussion is not so interesting :) --- 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 Dec 17 16:53:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15316 for freebsd-current-outgoing; Thu, 17 Dec 1998 16:53:01 -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 QAA15310 for ; Thu, 17 Dec 1998 16:53:00 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id TAA00340; Thu, 17 Dec 1998 19:52:46 -0500 (EST) (envelope-from wollman) Date: Thu, 17 Dec 1998 19:52:46 -0500 (EST) From: Garrett Wollman Message-Id: <199812180052.TAA00340@khavrinen.lcs.mit.edu> To: Julian Elischer Cc: "current@FreeBSD.ORG" Subject: Re: Linux Threads patches available In-Reply-To: <36799B88.2781E494@whistle.com> References: <36799B88.2781E494@whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > The sructure is 328 (?) bytes long, but it already exists. > The fields are simply being shifted from one place to another. > The biggest thing is the (struct sigacts) > which moves from the u area to kvm. Since the U area is fixed in size > (always has a page available) > We do lose some KVM. More importantly, you lose the ability to page the suckers out. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 17:00:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16180 for freebsd-current-outgoing; Thu, 17 Dec 1998 17:00:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16175 for ; Thu, 17 Dec 1998 17:00:46 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id UAA06414 for ; Thu, 17 Dec 1998 20:04:01 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 17 Dec 1998 20:04:01 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "current@FreeBSD.ORG" Subject: Re: Linux Threads patches available In-Reply-To: <36799B88.2781E494@whistle.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 Does this in any positive way impact on running Linux oracle? :) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 17:17:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18388 for freebsd-current-outgoing; Thu, 17 Dec 1998 17:17:47 -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 RAA18379 for ; Thu, 17 Dec 1998 17:17:43 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id UAA47396; Thu, 17 Dec 1998 20:15:55 -0500 (EST) Date: Thu, 17 Dec 1998 20:15:55 -0500 (EST) From: Chuck Robey To: "Daniel O'Connor" cc: Julian Elischer , "current@FreeBSD.ORG" , Brian Feldman Subject: Re: Linux Threads patches 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, 18 Dec 1998, Daniel O'Connor wrote: > > On 18-Dec-98 Julian Elischer wrote: > > People have been very silent on thi which is amazing > > considering what a step forwards this is... > Personally the end result sounds very very nice, but the technical discussion is not so > interesting :) It's interesting .. how does this compare with Luoqi Chen's recently announced modifications? I suspect that might be some of the reason this is not yet generating excitement. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 17:48:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22142 for freebsd-current-outgoing; Thu, 17 Dec 1998 17:48:42 -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 RAA22130 for ; Thu, 17 Dec 1998 17:48:39 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA16341; Thu, 17 Dec 1998 17:44:20 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdH16337; Fri Dec 18 01:44:15 1998 Message-ID: <3679B36C.15FB7483@whistle.com> Date: Thu, 17 Dec 1998 17:44:12 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Chuck Robey CC: "Daniel O'Connor" , "current@FreeBSD.ORG" , Brian Feldman Subject: Re: Linux Threads patches available References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > On Fri, 18 Dec 1998, Daniel O'Connor wrote: > > > > > On 18-Dec-98 Julian Elischer wrote: > > > People have been very silent on thi which is amazing > > > considering what a step forwards this is... > > Personally the end result sounds very very nice, but the technical discussion is not so > > interesting :) > > It's interesting .. how does this compare with Luoqi Chen's recently > announced modifications? I suspect that might be some of the reason > this is not yet generating excitement. I believe they are orthogonal changes, eh luoqi? > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (NetBSD). > ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 18:22:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26154 for freebsd-current-outgoing; Thu, 17 Dec 1998 18:22:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26102 for ; Thu, 17 Dec 1998 18:21:58 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id AAA26251 for current@freebsd.org; Fri, 18 Dec 1998 00:21:50 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199812180221.AAA26251@roma.coe.ufrj.br> Subject: aout compats in elf dir To: current@FreeBSD.ORG Date: Fri, 18 Dec 1998 00:21:49 -0200 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey, I've just installed a 3.0 SNAP, and found that some compat libs are in the wrong place. Here an example, from 3.0-19981209-SNAP: roma::jonny [608] cat compat21.?? | tar tfvz - drwxr-xr-x root/wheel 0 Dec 9 14:29 1998 ./ drwxr-xr-x root/wheel 0 Dec 9 14:29 1998 usr/ drwxr-xr-x root/wheel 0 Dec 9 14:29 1998 usr/lib/ drwxr-xr-x root/wheel 0 Dec 9 14:29 1998 usr/lib/compat/ -r--r--r-- root/wheel 435857 Dec 9 12:28 1998 usr/lib/compat/libc.so.2.2 -r--r--r-- root/wheel 494649 Dec 9 12:28 1998 usr/lib/compat/libg++.so.3.0 -r--r--r-- root/wheel 46237 Dec 9 12:28 1998 usr/lib/compat/libgmp.so.2.0 roma::jonny [609] Shouldn't these be in /usr/lib/compat/aout, where ldconfig expects them ??? And compat20 and compat1x suffer from this problem also. Just in case, I've sent a PR for this, numbered bin/9118. Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 19:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05155 for freebsd-current-outgoing; Thu, 17 Dec 1998 19:28:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05140 for ; Thu, 17 Dec 1998 19:28:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id TAA82337; Thu, 17 Dec 1998 19:28:06 -0800 (PST) To: Julian Elischer cc: Brian Feldman , "current@FreeBSD.ORG" Subject: Re: Linux Threads patches available In-reply-to: Your message of "Thu, 17 Dec 1998 16:02:16 PST." <36799B88.2781E494@whistle.com> Date: Thu, 17 Dec 1998 19:28:05 -0800 Message-ID: <82333.913951685@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > People have been very silent on thi which is amazing > considering what a step forwards this is... Silence in the FreeBSD project is equivalent to assent. It's one of our oldest and most cherished philosophies, without which much would never get done at all. ;)' - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 19:40:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07083 for freebsd-current-outgoing; Thu, 17 Dec 1998 19:40:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07077; Thu, 17 Dec 1998 19:40:36 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: by fallout.campusview.indiana.edu (Postfix, from userid 8489) id F07221283; Thu, 17 Dec 1998 22:40:27 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by fallout.campusview.indiana.edu (Postfix) with ESMTP id A1A4111E1; Thu, 17 Dec 1998 22:40:27 -0500 (EST) Date: Thu, 17 Dec 1998 22:40:27 -0500 (EST) From: John Fieber X-Sender: jfieber@fallout.campusview.indiana.edu To: Alfred Perlstein Cc: "current@FreeBSD.ORG" , database@FreeBSD.ORG Subject: Re: Linux Threads patches 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 Thu, 17 Dec 1998, Alfred Perlstein wrote: > Does this in any positive way impact on running Linux oracle? :) I was under the impression that the main Oracle problem was with pipes. A pipe fix went recently. Who was working on Oracle? -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 19:48:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08118 for freebsd-current-outgoing; Thu, 17 Dec 1998 19:48:18 -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 TAA08113 for ; Thu, 17 Dec 1998 19:48:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA01088; Thu, 17 Dec 1998 19:45:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812180345.TAA01088@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Richard Seaman, Jr." cc: "Mike Smith" , "Julian Elischer" , "current@freebsd.org" Subject: Re: Linux Threads patches available In-reply-to: Your message of "Thu, 17 Dec 1998 15:25:46 CST." <199812172125.PAA01921@ns.tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Dec 1998 19:45:01 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 16 Dec 1998 03:41:59 -0800, Mike Smith wrote: > > >I've had a (quick) look at your current webpage; thanks for collecting > >all this in one place. Would you care to summarise the changes in a > >little more detail, and perhaps sort them into 'non-intrusive' and > >'intrusive' groups so that we can commit the first set and do whatever > >needs to be done to resolve any problems with the second ASAP? > > I've added a summary at http://lt.tar.com/patchsum.html. I can > send to you if its inconvenient to read it there. I thought it was > a little long to post to this list, but it could be done if someone > wants it that way. Thanks again for the summary; it's made the situation fairly clear. >From my first reading, a couple of questions: - Completeness would suggest that you should use vm_map_stack for the "original" process stack as well as for subsequent thread stacks. Is there a counter-argument? - Any reason (again for completeness) you couldn't add the remaining syscalls you list in the sigsuspend.S change to the patch? - Any guesses at Alpha-related issues? And one finally, presuming you're interested in pursuing this sort of thing further (we'd like that I expect): - Any reason you don't want to become a committer? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 19:48:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08232 for freebsd-current-outgoing; Thu, 17 Dec 1998 19:48:49 -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 TAA08227 for ; Thu, 17 Dec 1998 19:48:48 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA19168; Thu, 17 Dec 1998 19:43:40 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdD19165; Fri Dec 18 03:43:32 1998 Message-ID: <3679CF61.3F54BC7E@whistle.com> Date: Thu, 17 Dec 1998 19:43:29 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Alfred Perlstein CC: "current@FreeBSD.ORG" Subject: Re: Linux Threads patches available References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > Does this in any positive way impact on running Linux oracle? :) > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 3.0-current > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message possibly.. does it use the clone() call? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 19:50:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08473 for freebsd-current-outgoing; Thu, 17 Dec 1998 19:50:08 -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 TAA08414; Thu, 17 Dec 1998 19:50:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA01102; Thu, 17 Dec 1998 19:46:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812180346.TAA01102@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Fieber cc: Alfred Perlstein , "current@FreeBSD.ORG" , database@FreeBSD.ORG Subject: Re: Linux Threads patches available In-reply-to: Your message of "Thu, 17 Dec 1998 22:40:27 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Dec 1998 19:46:07 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 17 Dec 1998, Alfred Perlstein wrote: > > > Does this in any positive way impact on running Linux oracle? :) > > I was under the impression that the main Oracle problem was with > pipes. A pipe fix went recently. Who was working on Oracle? Soren, before his machine was stolen. Any chance you could look at these changes in the light of the pipe-related problems you were having with Sybase? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 19:54:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09254 for freebsd-current-outgoing; Thu, 17 Dec 1998 19:54:58 -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 TAA09242 for ; Thu, 17 Dec 1998 19:54:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id TAA01153; Thu, 17 Dec 1998 19:52:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812180352.TAA01153@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: Alfred Perlstein , "current@FreeBSD.ORG" Subject: Re: Linux Threads patches available In-reply-to: Your message of "Thu, 17 Dec 1998 19:43:29 PST." <3679CF61.3F54BC7E@whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Dec 1998 19:52:19 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Alfred Perlstein wrote: > > > > Does this in any positive way impact on running Linux oracle? :) > > > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > > -- There are operating systems, and then there's FreeBSD. > > -- http://www.freebsd.org/ 3.0-current > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > possibly.. > does it use the clone() call? It dies mysteriously before it gets that far, almost certainly due to the corruption of %edx after calling pipe(). I don't have it installed here at the moment, but installing it is *relatively* painless, so if nobody else has the wherewithal to do it before tomorrow, I might give it a try. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 19:58:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09593 for freebsd-current-outgoing; Thu, 17 Dec 1998 19:58:55 -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 TAA09577 for ; Thu, 17 Dec 1998 19:58:52 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA19502; Thu, 17 Dec 1998 19:57:37 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdZ19500; Fri Dec 18 03:57:34 1998 Message-ID: <3679D2AA.237C228A@whistle.com> Date: Thu, 17 Dec 1998 19:57:30 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Mike Smith CC: "Richard Seaman, Jr." , "current@freebsd.org" Subject: Re: Linux Threads patches available References: <199812180345.TAA01088@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: > [...] > Thanks again for the summary; it's made the situation fairly clear. > From my first reading, a couple of questions: > > - Completeness would suggest that you should use vm_map_stack for the > "original" process stack as well as for subsequent thread stacks. > Is there a counter-argument? I was wondering this too. > > - Any reason (again for completeness) you couldn't add the remaining > syscalls you list in the sigsuspend.S change to the patch? probably only because they are unrelated. [...] > > - Any reason you don't want to become a committer? good one... :-) The only downside I see to this is the addition of 328 bytes to the size of the proc struct. when those structs were in the U area, they were swapable. mind you, how many processes are swapped entirely on most systems? julian (who wants to see this committed but wants a few backers) Maybe it should be 'conditionally' integrated.. (all dependent on #ifdef SHAREDSIGS or LINUX_CLONE) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 17 23:48:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03559 for freebsd-current-outgoing; Thu, 17 Dec 1998 23:48:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03540; Thu, 17 Dec 1998 23:48:30 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA55168; Fri, 18 Dec 1998 08:47:47 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199812180747.IAA55168@freebsd.dk> Subject: Re: Linux Threads patches available In-Reply-To: <199812180346.TAA01102@dingo.cdrom.com> from Mike Smith at "Dec 17, 1998 7:46: 7 pm" To: mike@smith.net.au (Mike Smith) Date: Fri, 18 Dec 1998 08:47:47 +0100 (CET) Cc: jfieber@indiana.edu, bright@hotjobs.com, current@FreeBSD.ORG, database@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 It seems Mike Smith wrote: > > On Thu, 17 Dec 1998, Alfred Perlstein wrote: > > > > > Does this in any positive way impact on running Linux oracle? :) > > > > I was under the impression that the main Oracle problem was with > > pipes. A pipe fix went recently. Who was working on Oracle? > > Soren, before his machine was stolen. I am again on my latitude, and I keep it close to me at all times :) And the pipe patch doesn't make it work, allready been there.. I'm not sure if its still pipe related or not. There is still problems, and I'm loooking at it when I have a spare hour.... If anybody wants to help, please do so... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 00:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05888 for freebsd-current-outgoing; Fri, 18 Dec 1998 00:12:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05880 for ; Fri, 18 Dec 1998 00:12:44 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA25471; Fri, 18 Dec 1998 09:13:08 +0100 (MET) Date: Fri, 18 Dec 1998 09:12:24 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Alfred Perlstein cc: FreeBSD current mailing list Subject: Re: anyone notice the flurry of warnings when compiling kernel? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There is a few in the USB code, but these are verified to be harmless. I get very paranoia when warnings show up. I use strict in Perl... Nick On Thu, 17 Dec 1998, Alfred Perlstein wrote: > > compiling a kernel spews a LOT of warnings, but the compile works fine and > the resulting kernel seems ok. (yes i made clean) > > ../../kern/kern_mib.c:96: warning: `sysctl___kern_ngroups' defined but not > used > > ../../kern/kern_mib.c:98: warning: `sysctl___kern_job_control' defined but > not used > > ../../kern/subr_devstat.c:245: warning: `sysctl___kern_devstat_generation' > defined but not used > ../../kern/subr_devstat.c:247: warning: `sysctl___kern_devstat_version' > defined but not used > > just FYI. > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 3.0-current > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 03:27:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25946 for freebsd-current-outgoing; Fri, 18 Dec 1998 03:27:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25941 for ; Fri, 18 Dec 1998 03:27:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id DAA31059 for ; Fri, 18 Dec 1998 03:27:44 -0800 (PST) To: current@FreeBSD.ORG Subject: Also seeing IRQ oddness with -current now. Date: Fri, 18 Dec 1998 03:27:44 -0800 Message-ID: <31055.913980464@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, my Tyan S1836DLUAN dual PII board now also prints some interesting messages about "Freeing redirected ISA irqs" it didn't use to before on startup.. 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: Fri Dec 18 00:43:36 PST 1998 jkh@zippy.cdrom.com:/usr/src/sys/compile/ZIPPY Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II (quarter-micron) (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 134217728 (131072K bytes) config> quit avail memory = 127967232 (124968K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x00 on pci0.0.0 chip1: rev 0x00 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x02 on pci0.7.3 chip4: rev 0x03 on pci0.16.0 Freeing (NOT implemented) redirected ISA irq 11. fxp0: rev 0x05 int a irq 19 on pci0.17.0 fxp0: Ethernet address 00:e0:81:10:20:9e Freeing (NOT implemented) redirected ISA irq 10. ahc0: rev 0x04 int a irq 16 on pci0.18.0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs Freeing (NOT implemented) redirected ISA irq 10. ahc1: rev 0x04 int b irq 16 on pci0.18.1 ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs Freeing (NOT implemented) redirected ISA irq 9. Probing for devices on PCI bus 1: Freeing (NOT implemented) redirected ISA irq 10. vga0: rev 0x04 int a irq 16 on pci1.0.0 Probing for devices on PCI bus 2: 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 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 pcm0 at 0x220 irq 5 drq 1 flags 0x3 on isa WARNING: sb: misconfigured secondary DMA channel 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: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 03:39:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27097 for freebsd-current-outgoing; Fri, 18 Dec 1998 03:39:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27091 for ; Fri, 18 Dec 1998 03:39:02 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id LAA11902; Fri, 18 Dec 1998 11:38:32 GMT Message-ID: <367A3EA0.793C5806@tdx.co.uk> Date: Fri, 18 Dec 1998 11:38:08 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: current@FreeBSD.ORG Subject: Re: Also seeing IRQ oddness with -current now. References: <31055.913980464@zippy.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 "Jordan K. Hubbard" wrote: > > FWIW, my Tyan S1836DLUAN dual PII board now also prints some > interesting messages about "Freeing redirected ISA irqs" it didn't use > to before on startup.. > [snip] > Freeing (NOT implemented) redirected ISA irq 10. > Freeing (NOT implemented) redirected ISA irq 10. > Freeing (NOT implemented) redirected ISA irq 9. My SuperMicro P6DNF has done this since the first time I ran SMP -current on it... I vaguely remember talking to someone about it - I'm sure they said it was benign... Something to do with the way SMP assigns the IRQ's (e.g. SCSI controllers 'appearing' on IRQ #16 ;-)... The system certainly runs fine... :) (I've not seen any increase in the number on recent -currents either) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 03:50:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27745 for freebsd-current-outgoing; Fri, 18 Dec 1998 03:50:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27739 for ; Fri, 18 Dec 1998 03:50:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id DAA31119; Fri, 18 Dec 1998 03:50:05 -0800 (PST) To: Karl Pielorz cc: current@FreeBSD.ORG Subject: Re: Also seeing IRQ oddness with -current now. In-reply-to: Your message of "Fri, 18 Dec 1998 11:38:08 GMT." <367A3EA0.793C5806@tdx.co.uk> Date: Fri, 18 Dec 1998 03:50:05 -0800 Message-ID: <31115.913981805@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My SuperMicro P6DNF has done this since the first time I ran SMP -current on > it... I vaguely remember talking to someone about it - I'm sure they said it OK, well, let me ask you another question then: Going from a single to dual CPU configuration, did you see any change in your "worldstone" times? Before I added a second CPU to my PII/450 tonite (and started seeing those messages as a consequence of added SMP support), I carefully timed a `make -j4 world' running off a single 9GB Cheetah with soft updates enabled for all file systems. With one CPU, it's 1:05. With two CPUs, it's 1:01. This either proves that I'm seriously I/O bound or that multiple CPUs aren't helping the compile times for some weird reason. :-) None of the other benchmarks I've found (GENERICstone, rc5, calculating pi :-) seem to be affected by single-vs-dual CPU, but this doesn't particularly surprise me either. The fact that rc5crack claims to use multiple CPUs doesn't necessarily make it so and none of the others are designed to benefit from SMP at all. Hmmmm. As usual, we come down to the fact that we really don't have any decent benchmarks for measuring the effectiveness of SMP. I've asked the folks who sell SMP Linux systems at VA Research about this and they've also confessed to not really having any decent ways of actually testing Linux's effectiveness for SMP. Looks like we can at least claim parity with Linux as far as that one is concerned. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 04:07:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01047 for freebsd-current-outgoing; Fri, 18 Dec 1998 04:07:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01042 for ; Fri, 18 Dec 1998 04:07:32 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id MAA12014; Fri, 18 Dec 1998 12:07:20 GMT Message-ID: <367A455F.2D9C0ED4@tdx.co.uk> Date: Fri, 18 Dec 1998 12:06:55 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: current@FreeBSD.ORG Subject: Re: Also seeing IRQ oddness with -current now. References: <31115.913981805@zippy.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 "Jordan K. Hubbard" wrote: > > > My SuperMicro P6DNF has done this since the first time I ran SMP -current on > > it... I vaguely remember talking to someone about it - I'm sure they said it > > OK, well, let me ask you another question then: > > Going from a single to dual CPU configuration, did you see any change > in your "worldstone" times? Before I added a second CPU to my PII/450 > tonite (and started seeing those messages as a consequence of added > SMP support), I carefully timed a `make -j4 world' running off a > single 9GB Cheetah with soft updates enabled for all file systems. I don't see much difference - you tend to get more of a difference with a higher '-j' factor ;-) I tend to use anything from 8 to 16 (higher the number, bigger the gain, bigger the chance of a foulup with makeworld)... > With one CPU, it's 1:05. With two CPUs, it's 1:01. This either > proves that I'm seriously I/O bound or that multiple CPUs aren't > helping the compile times for some weird reason. :-) > > None of the other benchmarks I've found (GENERICstone, rc5, > calculating pi :-) seem to be affected by single-vs-dual CPU, but this > doesn't particularly surprise me either. The fact that rc5crack > claims to use multiple CPUs doesn't necessarily make it so and none of > the others are designed to benefit from SMP at all. If I run rc5 twice on the same machine - appart from things getting a bit 'choppy' - it does appear to crack keys roughly twice as fast... Maybe if you run things like 'pi' twice? And see if the aggregate throughput is better than it 'should' be (i.e. both instances don't sink down to half the throughput)... > Hmmmm. As usual, we come down to the fact that we really don't have > any decent benchmarks for measuring the effectiveness of SMP. I've > asked the folks who sell SMP Linux systems at VA Research about this > and they've also confessed to not really having any decent ways of > actually testing Linux's effectiveness for SMP. Looks like we can at > least claim parity with Linux as far as that one is concerned. :-) True... :) I've noticed since I've gone SMP - I can 'get away' with higher load averages on the machine, I've quite often managed to push this up to around 30-40 - and it's still been nice and responsive... I have a lot of drives in the box (i.e. seperates for root, usr, usr obj, web server, home dirs etc.) - I think this helps... Other winners seem to be things like Apache (i.e. lots of processes) - mind you until we lose the 'big lock' on the Kernel anything that's kernel bound (i.e. probably I/O bound, 'system' bound whatever) is not going to show much improvement... -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 06:56:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16601 for freebsd-current-outgoing; Fri, 18 Dec 1998 06:56:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16596 for ; Fri, 18 Dec 1998 06:56:34 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id PAA22393; Fri, 18 Dec 1998 15:56:16 +0100 (CET) (envelope-from des) To: Jaye Mathisen Cc: Matthew Dillon , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: disklabel baggage. References: From: Dag-Erling Smorgrav Date: 18 Dec 1998 15:56:15 +0100 In-Reply-To: Jaye Mathisen's message of "Wed, 16 Dec 1998 12:03:37 -0800 (PST)" Message-ID: Lines: 23 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaye Mathisen writes: > Amen to this. / is starting to look like a pigpen. I beg your pardon? How does the following look like a pigpen: # ls / COPYRIGHT dev/ kernel.old* pub/ sys@ bin/ etc/ mnt/ root/ tmp/ boot/ home/ modules/ sbin/ usr/ compat@ kernel* proc/ stand/ var/ (I've removed .profile and .cshrc, which are useless, and lkm/, which is empty since this is an Elf system; home/ and pub/ are mount points.) If you want to clean up /, start by removing what's *really* useless, such as /.cshrc, /.profile and /stand/. And if you want to call something a pigpen, take a look at /etc. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 06:59:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17042 for freebsd-current-outgoing; Fri, 18 Dec 1998 06:59:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from liberty.bulinfo.net (liberty.bulinfo.net [195.10.36.71]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA17022 for ; Fri, 18 Dec 1998 06:59:43 -0800 (PST) (envelope-from krassi@liberty.bulinfo.net) Received: (qmail 1026 invoked from network); 18 Dec 1998 14:59:24 -0000 Received: from liberty.bulinfo.net (195.10.36.71) by liberty.bulinfo.net with SMTP; 18 Dec 1998 14:59:24 -0000 Message-ID: <367A6DCB.3C7FD331@liberty.bulinfo.net> Date: Fri, 18 Dec 1998 16:59:23 +0200 From: Krassimir Slavchev Organization: Bulinfo Ltd. X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: ru, bg, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Current Sync Serial Adapters Support Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have bought Digi Sync/570ip (PCI version) serial multiport adapter but it is currently unsupported in the FreeBSD source tree. Are there some plans for including such a driver in Current FreeBSD. If anyone plans to make something about this, pls be so kind to contact us. Best Regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 07:07:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17728 for freebsd-current-outgoing; Fri, 18 Dec 1998 07:07:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17723 for ; Fri, 18 Dec 1998 07:07:29 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id JAA10246; Fri, 18 Dec 1998 09:06:56 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812181506.JAA10246@ns.tar.com> From: "Richard Seaman, Jr." To: "Mike Smith" Cc: "current@freebsd.org" , "Julian Elischer" Date: Fri, 18 Dec 98 09:06:56 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Linux Threads patches available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998 19:45:01 -0800, Mike Smith wrote: >Thanks again for the summary; it's made the situation fairly clear. >>From my first reading, a couple of questions: > > - Completeness would suggest that you should use vm_map_stack for the > "original" process stack as well as for subsequent thread stacks. > Is there a counter-argument? Not that I know of. I coded the option as part of my initial debugging. I didn't want the original process stack to use the new code until I could try it out elsewhere. > > - Any reason (again for completeness) you couldn't add the remaining > syscalls you list in the sigsuspend.S change to the patch? No. I just haven't done the patches yet. They could easily be added later too. > - Any guesses at Alpha-related issues? No. I don't have an alpha machine and didn't really look. > >And one finally, presuming you're interested in pursuing this sort of >thing further (we'd like that I expect): > > - Any reason you don't want to become a committer? Learning how to really use cvs? :) Actually, the idea scares me a little. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 07:32:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20538 for freebsd-current-outgoing; Fri, 18 Dec 1998 07:32:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20533 for ; Fri, 18 Dec 1998 07:32:24 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id JAA10366; Fri, 18 Dec 1998 09:31:33 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812181531.JAA10366@ns.tar.com> From: "Richard Seaman, Jr." To: "Julian Elischer" , "Mike Smith" Cc: "current@freebsd.org" Date: Fri, 18 Dec 98 09:31:32 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Linux Threads patches available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998 19:57:30 -0800, Julian Elischer wrote: >The only downside I see to this is the addition of >328 bytes to the size of the proc struct. >when those structs were in the U area, they were swapable. > >mind you, how many processes are swapped entirely on most systems? When Brian Feldman posted the first version of his patches for shared sigacts, someone (I'd have to check the archives to find out who) suggested leaving the sigacts structure in the U area, and only allocating the additional proc area structure in the event of an rforked process with the RFSIGSHARE option. This would involve then copying the values from the U area into the new malloc'd structure and resetting the p_sigacts pointer in both the parent and child. Then when the refcnt of the proc area structure gets back down to one, the values are copied back out to the U area structure, the proc pointer is reset and the area freed. It involves a little more coding, but would avoid most of the increase in the proc structure for non-threaded processes (but involves lugging around an unused U area structure per thread (ie. per process) for the RFSIGSHARE rforked process. If the extra proc size is a problem, this idea could be pursued. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 07:46:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22345 for freebsd-current-outgoing; Fri, 18 Dec 1998 07:46:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22306 for ; Fri, 18 Dec 1998 07:46:17 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id QAA11705 for ; Fri, 18 Dec 1998 16:45:46 +0100 (MET) Message-ID: <367A78A5.3FBF4CBA@we.lc.ehu.es> Date: Fri, 18 Dec 1998 16:45:41 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. de Electricidad y Electrónica X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: SMP benchmarks Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After reading a recent message from Jordan (I lost its reference) about the "makeworldbench" test results, I was a bit worried: is one of the two CPUs of my new computer being wasted by the FreeBSD kernel? Uh-oh! Then I did a little test running one of the BYTE benchmarks (arithoh). I did three runs with one, two and three simultaneous processes. These are the results: ---------------------------------------------------- TEST 1 - ONE process ALONE: TEST|Arithmetic Test (type = arithoh) FLAVOR|BSD 318250006 loops 10.00 real 9.99 user 0.00 sys 318090368 loops 10.00 real 9.99 user 0.00 sys 318006936 loops 10.00 real 9.98 user 0.00 sys 318271812 loops 10.00 real 10.00 user 0.00 sys 318086538 loops 10.00 real 9.99 user 0.00 sys 318002117 loops 10.00 real 9.99 user 0.00 sys ---------------------------------------------------- TEST 2 - TWO simultaneous processes: ===>PROCESS 1: TEST|Arithmetic Test (type = arithoh) FLAVOR|BSD 317440824 loops 10.00 real 9.98 user 0.00 sys 317409417 loops 10.00 real 9.98 user 0.00 sys 317367675 loops 10.00 real 9.99 user 0.00 sys 317256654 loops 10.00 real 9.98 user 0.00 sys 317141118 loops 10.00 real 9.97 user 0.00 sys 317716271 loops 10.00 real 10.00 user 0.00 sys ===>PROCESS 2: TEST|Arithmetic Test (type = arithoh) FLAVOR|BSD 317661019 loops 10.00 real 9.97 user 0.00 sys 317213738 loops 10.00 real 9.97 user 0.03 sys 316201777 loops 10.00 real 9.95 user 0.00 sys 317520076 loops 10.00 real 9.99 user 0.00 sys 317297652 loops 10.00 real 9.98 user 0.00 sys 317758290 loops 10.00 real 10.00 user 0.00 sys ---------------------------------------------------- TEST 3 - THREE simultaneous processes: ===>PROCESS 1: TEST|Arithmetic Test (type = arithoh) FLAVOR|BSD 218048189 loops 10.00 real 6.86 user 0.00 sys 211899735 loops 10.00 real 6.66 user 0.01 sys 212672592 loops 10.03 real 6.69 user 0.00 sys 218775511 loops 10.03 real 6.88 user 0.00 sys 212323294 loops 10.01 real 6.69 user 0.00 sys 211117933 loops 10.00 real 6.64 user 0.00 sys ===>PROCESS 2: TEST|Arithmetic Test (type = arithoh) FLAVOR|BSD 217233937 loops 10.00 real 6.84 user 0.00 sys 218657533 loops 10.02 real 6.88 user 0.00 sys 218244791 loops 10.00 real 6.86 user 0.00 sys 217716665 loops 10.03 real 6.85 user 0.00 sys 214327742 loops 10.03 real 6.74 user 0.00 sys 213706676 loops 10.03 real 6.72 user 0.00 sys ===>PROCESS 3: TEST|Arithmetic Test (type = arithoh) FLAVOR|BSD 220732030 loops 10.00 real 6.95 user 0.00 sys 226138300 loops 10.00 real 7.12 user 0.00 sys 214511860 loops 10.00 real 6.74 user 0.00 sys 209003767 loops 10.00 real 6.57 user 0.00 sys 217434544 loops 10.00 real 6.83 user 0.00 sys 218595421 loops 10.00 real 6.87 user 0.01 sys ---------------------------------------------------- Obviously this is only a number-crunching test. It does not measure kernel (syscall) SMP performance. However, it is significant. Observe that the results of tests 1 and 2 (one process alone and two simultaneous processes) are essentially identical. Even the "user time" is almost equal to the "real time" for both tests. But test 3 shows important differences: first, the number of loops is about 32% less than the two process test; and the "user time" is about 68% of the time dedicated to each process of test 2. In summary, at least making pure arithmetic computing, SMP does its work. (BTW, I'm also getting the "Freeing (NOT implemented) redirected ISA irq" messages at startup. The machine is a Supermicro P6DBU, two PII-450, 256 MB RAM). -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 08:04:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24577 for freebsd-current-outgoing; Fri, 18 Dec 1998 08:04:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24572 for ; Fri, 18 Dec 1998 08:04:51 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id QAA12983; Fri, 18 Dec 1998 16:04:03 GMT Message-ID: <367A7CDA.EF67AF5E@tdx.co.uk> Date: Fri, 18 Dec 1998 16:03:38 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?Jos=E9=20M=AA?= Alcaide CC: freebsd-current@FreeBSD.ORG Subject: Re: SMP benchmarks References: <367A78A5.3FBF4CBA@we.lc.ehu.es> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "José Mª Alcaide" wrote: > After reading a recent message from Jordan (I lost its reference) > about the "makeworldbench" test results, I was a bit worried: is one > of the two CPUs of my new computer being wasted by the FreeBSD > kernel? Uh-oh! Then I did a little test running one of the BYTE > benchmarks (arithoh). I did three runs with one, two and three > simultaneous processes. These are the results: > > [snip] > > In summary, at least making pure arithmetic computing, SMP does > its work. Yes, this is what I was saying to Jordan - as the FreeBSD kernel currently has a 'big lock' around it, meaning on an SMP machine AFAIK only one CPU can be 'in the kernel' at a time, if the other tries - it will get blocked (and probably go carry on with something else?) SMP is still a winner on FreeBSD though - because of Unix's nature to be very 'multi-processed', i.e. when you run Apache you don't just run 1 instance of apache, you run 4 or 5 (or more as the load increases) - so you get to the advantages of more CPU's - up until the system gets kernel bound (or IO bound)... This is what your test results proved... :) So, if you have something like rc5des - your better off running 2 copies of it on an SMP system... ;-) -Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 12:11:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23908 for freebsd-current-outgoing; Fri, 18 Dec 1998 12:11:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from anch01.customcpu.com ([198.70.210.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23900 for ; Fri, 18 Dec 1998 12:11:55 -0800 (PST) (envelope-from al7oj@customcpu.com) Received: from default ([207.14.79.52]) by anch01.customcpu.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42538U2500L250S0) with SMTP id AAA153 for ; Fri, 18 Dec 1998 11:11:56 -0900 Message-Id: <3.0.5.32.19981218111138.0082cae0@customcpu.com> X-Sender: al7oj@customcpu.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 18 Dec 1998 11:11:38 -0900 To: freebsd-current@FreeBSD.ORG From: "Michael A. Endsley" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I took my new 3.0-R cd down to the computer store and tried different Cd-Rom drives till I found a brand that would boot FreeBSD from the CD. Several did and one of them is Mitsumi FX3400S!B. I bought a new one (same thing), took it home and installed the CD Drive onto my Aptiva E-26. After running Win95 and testing the new drive, I did a soft reboot with the new 3.0-R CD in the drive. It didn't boot (kernel not found). I then rebooted into Win95, accessed the CD, and did soft reboot again. This time, I booted FreeBSD from the HD. Not only did fbsd not find the CD-Rom, the probe couldn't find anything at the 170 address! What am I missing? I also did a cold reboot, booted from the HD with -c and then quit and let the probing start. Still nothing. Any help would be appreciated, ie- I can't really take the Mitsumi back. Mike __________________________________________________________ OS of CHOICE? UNIX (FreeBSD), LINUX (Debian), and OS/2Warp al7oj@customcpu.com al7oj@al7oj.ampr.org or al7oj@al7oj.#nak.ak.usa.noam http://www.customcpu.com/personal/al7oj/ __________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 12:39:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28409 for freebsd-current-outgoing; Fri, 18 Dec 1998 12:39:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28404 for ; Fri, 18 Dec 1998 12:39:03 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id MAA05514; Fri, 18 Dec 1998 12:38:52 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Fri, 18 Dec 1998 12:38:51 -0800 (PST) From: Doug White To: "Michael A. Endsley" cc: freebsd-current@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <3.0.5.32.19981218111138.0082cae0@customcpu.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, 18 Dec 1998, Michael A. Endsley wrote: > I took my new 3.0-R cd down to the computer store and tried different > Cd-Rom drives till I found a brand that would boot FreeBSD from the CD. > Several did and one of them is Mitsumi FX3400S!B. I bought a new one (same > thing), took it home and installed the CD Drive onto my Aptiva E-26. After > running Win95 and testing the new drive, I did a soft reboot with the new > 3.0-R CD in the drive. It didn't boot (kernel not found). The primary determinant of CD bootability is the system BIOS. Not all BIOSen support it. My Toshiba at home with a newer AMIBIOS will do it, and my ASUS/Award BIOS P133 probably would if I had ATAPI CDROMs. :) > I then rebooted into Win95, accessed the CD, and did soft reboot again. > This time, I booted FreeBSD from the HD. Not only did fbsd not find the > CD-Rom, the probe couldn't find anything at the 170 address! > What am I missing? There is a potential bogon in the second IDE controller detection code. Try attaching the CD to your primary CD controller. > I also did a cold reboot, booted from the HD with -c and then quit and let > the probing start. Still nothing. > Any help would be appreciated, ie- I can't really take the Mitsumi back. It's not related to the CD-ROM drive itself. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 12:43:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA28874 for freebsd-current-outgoing; Fri, 18 Dec 1998 12:43:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from anch01.customcpu.com ([198.70.210.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA28867 for ; Fri, 18 Dec 1998 12:43:42 -0800 (PST) (envelope-from al7oj@customcpu.com) Received: from default ([207.14.79.52]) by anch01.customcpu.com (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-42538U2500L250S0) with SMTP id AAA165; Fri, 18 Dec 1998 11:43:43 -0900 Message-Id: <3.0.5.32.19981218114327.008384f0@customcpu.com> X-Sender: al7oj@customcpu.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 18 Dec 1998 11:43:27 -0900 To: Doug White From: "Michael A. Endsley" Subject: Re: your mail Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.19981218111138.0082cae0@customcpu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Aptiva bios supports booting from CD. Also, fwiw, Linux (Debian 2.0) boots from it flawlessly. When I run FBSD3.0-R from my HD, it won't even mount the CD drive. Mike At 12:38 PM 12/18/98 -0800, Doug White wrote: >On Fri, 18 Dec 1998, Michael A. Endsley wrote: > >> I took my new 3.0-R cd down to the computer store and tried different >> Cd-Rom drives till I found a brand that would boot FreeBSD from the CD. >> Several did and one of them is Mitsumi FX3400S!B. I bought a new one (same >> thing), took it home and installed the CD Drive onto my Aptiva E-26. After >> running Win95 and testing the new drive, I did a soft reboot with the new >> 3.0-R CD in the drive. It didn't boot (kernel not found). > >The primary determinant of CD bootability is the system BIOS. Not all >BIOSen support it. My Toshiba at home with a newer AMIBIOS will do it, >and my ASUS/Award BIOS P133 probably would if I had ATAPI CDROMs. :) > >> I then rebooted into Win95, accessed the CD, and did soft reboot again. >> This time, I booted FreeBSD from the HD. Not only did fbsd not find the >> CD-Rom, the probe couldn't find anything at the 170 address! >> What am I missing? > >There is a potential bogon in the second IDE controller detection code. >Try attaching the CD to your primary CD controller. > >> I also did a cold reboot, booted from the HD with -c and then quit and let >> the probing start. Still nothing. >> Any help would be appreciated, ie- I can't really take the Mitsumi back. > >It's not related to the CD-ROM drive itself. > >Doug White >Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve >http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > > __________________________________________________________ OS of CHOICE? UNIX (FreeBSD), LINUX (Debian), and OS/2Warp al7oj@customcpu.com al7oj@al7oj.ampr.org or al7oj@al7oj.#nak.ak.usa.noam http://www.customcpu.com/personal/al7oj/ __________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 12:44:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29193 for freebsd-current-outgoing; Fri, 18 Dec 1998 12:44:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29178 for ; Fri, 18 Dec 1998 12:44:03 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.10 #1) id 0zr6XX-00005T-00 for freebsd-current@freebsd.org; Fri, 18 Dec 1998 20:30:23 +0000 Date: Fri, 18 Dec 1998 20:30:23 +0000 From: Ben Smithurst To: freebsd-current@FreeBSD.ORG Subject: CD-ROM drive stays locked Message-ID: <19981218203023.A315@scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I do `mount /cdrom' without a CD-ROM in the (IDE) drive, the drive remains locked, and I can't eject the drive after that without disconnecting/reconnecting its power. The following patch seems to fix it, although is it possible there will be some unwanted side-effects? (Also, why does the error message say `audio disc'? If there's no disc in I don't see why it should care about it being an audio disc or not.) --- wcd.c~ Fri Dec 18 19:31:34 1998 +++ wcd.c Fri Dec 18 19:22:33 1998 @@ -692,6 +692,7 @@ if (result.error & ~AER_SKEY) { /* Audio disc. */ printf ("wcd%d: cannot read audio disc\n", t->lun); + t->flags &= ~F_LOCKED; return; } /* Tray open. */ -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 13:09:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02143 for freebsd-current-outgoing; Fri, 18 Dec 1998 13:09:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02138 for ; Fri, 18 Dec 1998 13:09:16 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id QAA11268; Fri, 18 Dec 1998 16:12:34 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 18 Dec 1998 16:12:34 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Michael A. Endsley" cc: freebsd-current@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <3.0.5.32.19981218111138.0082cae0@customcpu.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, 18 Dec 1998, Michael A. Endsley wrote: > I took my new 3.0-R cd down to the computer store and tried different > Cd-Rom drives till I found a brand that would boot FreeBSD from the CD. > Several did and one of them is Mitsumi FX3400S!B. I bought a new one (same > thing), took it home and installed the CD Drive onto my Aptiva E-26. After > running Win95 and testing the new drive, I did a soft reboot with the new > 3.0-R CD in the drive. It didn't boot (kernel not found). > I then rebooted into Win95, accessed the CD, and did soft reboot again. > This time, I booted FreeBSD from the HD. Not only did fbsd not find the > CD-Rom, the probe couldn't find anything at the 170 address! > What am I missing? > I also did a cold reboot, booted from the HD with -c and then quit and let > the probing start. Still nothing. > Any help would be appreciated, ie- I can't really take the Mitsumi back. > Mike > 1) have you tried a boot floppy? 2) check your master/slave jumpers on the harddrive and cdrom. 3) my mitsumi works really nicely. you may have a very annoying bios(tm) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current > __________________________________________________________ > OS of CHOICE? UNIX (FreeBSD), LINUX (Debian), and OS/2Warp > al7oj@customcpu.com > al7oj@al7oj.ampr.org or al7oj@al7oj.#nak.ak.usa.noam > http://www.customcpu.com/personal/al7oj/ > > __________________________________________________________ > > 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 Dec 18 18:25:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09411 for freebsd-current-outgoing; Fri, 18 Dec 1998 18:25:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from salmon.hei.net (salmon.hei.net [209.222.163.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09402 for ; Fri, 18 Dec 1998 18:25:29 -0800 (PST) (envelope-from john@hei.net) Received: from trout (hst-trout.hei.net [209.222.163.131]) by salmon.hei.net (8.8.8/8.8.5) with SMTP id SAA24444 for ; Fri, 18 Dec 1998 18:25:18 -0800 (PST) From: "John Hengstler" To: Subject: Buildworld fails Date: Fri, 18 Dec 1998 18:57:55 -0800 Message-ID: <001301be2afb$602c33a0$83a3ded1@trout.heicomm.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I did full install of 3.0-RELEASE onto a spare box. Installed and boot perfect with GENERIC. S So I installed current version of cvsup and have have been slurping updates on everything withno problems. When I go to do a make buildworld. It has been bombing everytime. Here is the output of the last try: /usr/include -c /usr/src/lib/libskey/skey_crypt.c -o skey_crypt.o cc -O -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/libskey -W -Wal l -Werror -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skey_getpass.c -o skey_getpass.o cc -O -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/libskey -W -Wal l -Werror -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skeylogin.c -o skeylogin.o cc -O -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/libskey -W -Wal l -Werror -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skeysubr.c -o skeysubr.o building standard skey library ranlib libskey.a cc -fpic -DPIC -O -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/lib skey -W -Wall -Werror -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skeyaccess.c -o skeyaccess.so cc -fpic -DPIC -O -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/lib skey -W -Wall -Werror -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libskey/put.c -o put.so cc -fpic -DPIC -O -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/lib skey -W -Wall -Werror -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skey_crypt.c -o skey_crypt.so cc -fpic -DPIC -O -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/lib skey -W -Wall -Werror -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skey_getpass.c -o skey_getpass.so cc -fpic -DPIC -O -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/lib skey -W -Wall -Werror -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skeylogin.c -o skeylogin.so cc -fpic -DPIC -O -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/usr/src/lib/lib skey -W -Wall -Werror -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libskey/skeysubr.c -o skeysubr.so building shared skey library (version 2) install -C -o root -g wheel -m 444 /usr/src/lib/libskey/skey.h /usr/obj/elf/usr/src/tmp/usr/include install -c -o root -g wheel -m 444 libskey.a /usr/obj/elf/usr/src/tmp/usr/lib install -c -o root -g wheel -m 444 libskey.so.2 /usr/obj/elf/usr/src/tmp/usr/lib ln -sf libskey.so.2 /usr/obj/elf/usr/src/tmp/usr/lib/libskey.so cd /usr/src/lib/libtacplus; /usr/obj/elf/usr/src/tmp/usr/bin/make all; /usr/obj/elf/usr/src/tmp/usr/bin/make -B install cc -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libtacplus/taclib.c -o taclib.o building standard tacplus library ranlib libtacplus.a cc -fpic -DPIC -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libtacplus/taclib.c -o taclib.so cc: Internal compiler error: program cc1 got fatal signal 11 *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. su-2.02# I did do a make update this morning (around 10am pst) before I did this buildworld. Other buildworlds have had similiar results. Late last night I did build a new kernel no problem thinking that GENERIC was bad. Same results as prior times. Any suggestions? John Hengstler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 18:33:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10249 for freebsd-current-outgoing; Fri, 18 Dec 1998 18:33:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from salmon.hei.net (salmon.hei.net [209.222.163.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10241; Fri, 18 Dec 1998 18:32:57 -0800 (PST) (envelope-from john@hei.net) Received: from trout (hst-trout.hei.net [209.222.163.131]) by salmon.hei.net (8.8.8/8.8.5) with SMTP id SAA24483; Fri, 18 Dec 1998 18:32:48 -0800 (PST) From: "John Hengstler" To: Cc: Subject: 16 port boca board Date: Fri, 18 Dec 1998 19:05:25 -0800 Message-ID: <001401be2afc$6cc7a120$83a3ded1@trout.heicomm.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I have a 16 port boca board which I have been using for dialup accounts for a while now on all releases of 2.2.5-stable through 2.2.7-stable on a 486 box. With no problems. I have been wanting to move them to my p-100 box with kernel compiled same was as 486 (with the obvious pentium options). Every reboot I have to watch for the silo errors immediately after the ports initialize. If I don't get them then the board works fine. If I get them, then typically most of the ports don't work, and the errors keep coming, which of course requires a reboot. I also notice the all the ports aren't being found, which sometimes is the master port, which of course requires a reboot. What can I do to fix this problem. Again everything runs fine on the 486.. Oh yeah I do have 2 different pentium machines that I have tried it on, but same results. Any help would be appreciated... John Hengstler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 18:59:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12864 for freebsd-current-outgoing; Fri, 18 Dec 1998 18:59:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA12852 for ; Fri, 18 Dec 1998 18:59:33 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id WAA11658; Fri, 18 Dec 1998 22:02:48 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 18 Dec 1998 22:02:48 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: John Hengstler cc: freebsd-current@FreeBSD.ORG Subject: Re: Buildworld fails In-Reply-To: <001301be2afb$602c33a0$83a3ded1@trout.heicomm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Dec 1998, John Hengstler wrote: > Greetings, > > I did full install of 3.0-RELEASE onto a spare box. Installed and boot > perfect with GENERIC. S > > So I installed current version of cvsup and have have been slurping updates > on everything withno problems. > > When I go to do a make buildworld. It has been bombing everytime. Here is > the output of the last try: > .... > cc -fpic -DPIC -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c > /usr/src/lib/libtacplus/taclib.c -o taclib.so > cc: Internal compiler error: program cc1 got fatal signal 11 > *** Error code 1 > > Stop. > *** Error code 1 > .... > I did do a make update this morning (around 10am pst) before I did this > buildworld. Other buildworlds have had similiar results. Late last > night I did build a new kernel no problem thinking that GENERIC was bad. > Same results as prior times. > > Any suggestions? > > John Hengstler > Unless this happens in the same spot every time you have a hardware problem. Aren't there about 10 FAQs out there at least that explain this? Try swapping ram, disabling cache, swapping boards. Something has gone rotten in your box. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 19:33:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15354 for freebsd-current-outgoing; Fri, 18 Dec 1998 19:33:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from salmon.hei.net (salmon.hei.net [209.222.163.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15349 for ; Fri, 18 Dec 1998 19:33:23 -0800 (PST) (envelope-from john@salmon.hei.net) Received: from localhost (john@localhost) by salmon.hei.net (8.8.8/8.8.5) with SMTP id TAA24727; Fri, 18 Dec 1998 19:32:53 -0800 (PST) Date: Fri, 18 Dec 1998 19:32:53 -0800 (PST) From: "John A. Hengstler" To: Alfred Perlstein cc: freebsd-current@FreeBSD.ORG Subject: Re: Buildworld fails 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 Normally I would agree with this, except, 2.2.8 make buildworlds and installworlds, work fine on same machine.. On Fri, 18 Dec 1998, Alfred Perlstein wrote: > On Fri, 18 Dec 1998, John Hengstler wrote: > > > Greetings, > > > > I did full install of 3.0-RELEASE onto a spare box. Installed and boot > > perfect with GENERIC. S > > > > So I installed current version of cvsup and have have been slurping updates > > on everything withno problems. > > > > When I go to do a make buildworld. It has been bombing everytime. Here is > > the output of the last try: > > > .... > > cc -fpic -DPIC -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c > > /usr/src/lib/libtacplus/taclib.c -o taclib.so > > cc: Internal compiler error: program cc1 got fatal signal 11 > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > .... > > I did do a make update this morning (around 10am pst) before I did this > > buildworld. Other buildworlds have had similiar results. Late last > > night I did build a new kernel no problem thinking that GENERIC was bad. > > Same results as prior times. > > > > Any suggestions? > > > > John Hengstler > > > > Unless this happens in the same spot every time you have a hardware > problem. Aren't there about 10 FAQs out there at least that explain this? > > Try swapping ram, disabling cache, swapping boards. Something has gone > rotten in your box. > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > -- There are operating systems, and then there's FreeBSD. > -- http://www.freebsd.org/ 3.0-current > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 19:50:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16687 for freebsd-current-outgoing; Fri, 18 Dec 1998 19:50:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16682 for ; Fri, 18 Dec 1998 19:50:36 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id WAA11750; Fri, 18 Dec 1998 22:53:53 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 18 Dec 1998 22:53:53 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "John A. Hengstler" cc: freebsd-current@FreeBSD.ORG Subject: Re: Buildworld fails 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, 18 Dec 1998, John A. Hengstler wrote: > Normally I would agree with this, except, 2.2.8 make buildworlds and > installworlds, work fine on same machine.. > hmmm, are you thrashing at all? how is your memory/swap? maybe you have dying deamons, but with regular processes? can you successfully do a non-parallel build? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 20:15:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18412 for freebsd-current-outgoing; Fri, 18 Dec 1998 20:15:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ida.net (mail.ida.net [204.228.203.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18406 for ; Fri, 18 Dec 1998 20:15:35 -0800 (PST) (envelope-from muck@ida.net) Received: from tc-pt2-33.ida.net (tc-pt2-33.ida.net [208.141.181.90]) by mail.ida.net (8.8.7/8.8.7) with ESMTP id VAA16405; Fri, 18 Dec 1998 21:15:57 -0700 (MST) Date: Fri, 18 Dec 1998 21:13:56 -0700 (MST) From: Mike Jackson X-Sender: muck@falcon.hinterlands.com To: Alfred Perlstein cc: "John A. Hengstler" , freebsd-current@FreeBSD.ORG Subject: Re: Buildworld fails 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, 18 Dec 1998, Alfred Perlstein wrote: > > On Fri, 18 Dec 1998, John A. Hengstler wrote: > > > Normally I would agree with this, except, 2.2.8 make buildworlds and > > installworlds, work fine on same machine.. > > > > hmmm, are you thrashing at all? how is your memory/swap? maybe you have > dying deamons, but with regular processes? > > can you successfully do a non-parallel build? > Why don't you see what happens when you mount /usr with softupdates? Let me guess, the build has been going on for quite some time before it dies? Also, are you running X Windows at the same time as doing the make world? Which would cause you to start swapping. I've seen the problems you describe on my machine, but have been able to get around them by mounting /usr with softupdates/noatime and not using the box when the world is being built (hence, very little swap space is used). Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 20:28:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20033 for freebsd-current-outgoing; Fri, 18 Dec 1998 20:28:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20023 for ; Fri, 18 Dec 1998 20:28:48 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id XAA26379 for ; Fri, 18 Dec 1998 23:28:37 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA09179; Fri, 18 Dec 1998 23:28:36 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id XAA29321 for freebsd-current@freebsd.org; Fri, 18 Dec 1998 23:28:36 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812190428.XAA29321@bb01f39.unx.sas.com> Subject: make release failure: osreldate.h To: freebsd-current@FreeBSD.ORG Date: Fri, 18 Dec 1998 23:28:36 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Subject says it all... I remember some discussion about this file not too long ago... Thanks! John auth.h types.h xdr.h auth_des.h des.h des_crypt.h /R/stage/trees/bin/usr/include/rpc install -C -o root -g wheel -m 444 /usr/src/include/osreldate.h /R/stage/trees/bin/usr/include install: /usr/src/include/osreldate.h: No such file or directory *** Error code 71 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 21:04:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23698 for freebsd-current-outgoing; Fri, 18 Dec 1998 21:04:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23693 for ; Fri, 18 Dec 1998 21:04:17 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id VAA14039; Fri, 18 Dec 1998 21:04:06 -0800 (PST) Date: Fri, 18 Dec 1998 21:04:05 -0800 (PST) From: Chris Timmons To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: Also seeing IRQ oddness with -current now. In-Reply-To: <31115.913981805@zippy.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 I think the irq messages have been there all along for SMP. The most dramatic performance increase I perceive from SMP is in overall throughput on a machine with diverse tasks running concurrently. Put your 'make -j12 buildworld' in a loop, and put the build of ports/x11/XFree86 in a loop, such that you get a new logfile of stdout for each iteration of the builds. Try this for a while with one CPU, and then add the 2nd CPU. You'll see a pretty pronounced difference in your buildworld time then. And that is the real value of SMP right now - not breathtaking speed for single tasks (even when aided by make's parallelism) but increased throughput for highly loaded machines. I'm going to put cvsup.freebsd.org on a dual ppro machine shortly which will maybe help me decide the question of how ready for prime time 3.0-current is. Right now the uniprocessor pro/512 2.2-stable machine looks like this: 9:00PM up 16 days, 22:14, 2 users, load averages: 9.82, 9.07, 9.40 certainly no wcarchive but it does do it's share :) -Chris On Fri, 18 Dec 1998, Jordan K. Hubbard wrote: [...] > With one CPU, it's 1:05. With two CPUs, it's 1:01. This either > proves that I'm seriously I/O bound or that multiple CPUs aren't > helping the compile times for some weird reason. :-) [...] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 21:06:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24176 for freebsd-current-outgoing; Fri, 18 Dec 1998 21:06:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from salmon.hei.net (salmon.hei.net [209.222.163.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24167 for ; Fri, 18 Dec 1998 21:06:24 -0800 (PST) (envelope-from john@salmon.hei.net) Received: from localhost (john@localhost) by salmon.hei.net (8.8.8/8.8.5) with SMTP id VAA25105; Fri, 18 Dec 1998 21:05:55 -0800 (PST) Date: Fri, 18 Dec 1998 21:05:55 -0800 (PST) From: "John A. Hengstler" To: Mike Jackson cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: Buildworld fails 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 Nothing running on machine, except the release startup programs. It is not a production machine, so no other user activity. swapspace is 12% used, machine has 16 megs of ram, with 150meg of swap. John On Fri, 18 Dec 1998, Mike Jackson wrote: > > > On Fri, 18 Dec 1998, Alfred Perlstein wrote: > > > > > On Fri, 18 Dec 1998, John A. Hengstler wrote: > > > > > Normally I would agree with this, except, 2.2.8 make buildworlds and > > > installworlds, work fine on same machine.. > > > > > > > hmmm, are you thrashing at all? how is your memory/swap? maybe you have > > dying deamons, but with regular processes? > > > > can you successfully do a non-parallel build? > > > > Why don't you see what happens when you mount /usr with softupdates? Let > me guess, the build has been going on for quite some time before it dies? > Also, are you running X Windows at the same time as doing the make world? > Which would cause you to start swapping. > > I've seen the problems you describe on my machine, but have been able to > get around them by mounting /usr with softupdates/noatime and not using > the box when the world is being built (hence, very little swap space is > used). > > Mike > > > 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 Dec 18 21:23:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26085 for freebsd-current-outgoing; Fri, 18 Dec 1998 21:23:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA26080 for ; Fri, 18 Dec 1998 21:23:39 -0800 (PST) (envelope-from nordwick@scam.XCF.Berkeley.EDU) Message-Id: <199812190523.VAA26080@hub.freebsd.org> Received: (qmail 28798 invoked by uid 27268); 19 Dec 1998 05:18:06 -0000 Received: from localhost (HELO scam.XCF.Berkeley.EDU) (sendmail-bs@127.0.0.1) by localhost with SMTP; 19 Dec 1998 05:18:06 -0000 To: freebsd-current@FreeBSD.ORG Subject: system projects and Linux wishlist. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28795.914044685.1@scam.XCF.Berkeley.EDU> Date: Fri, 18 Dec 1998 21:18:06 -0800 From: "Jay Nordwick" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was looking at the Linux kernel wishlist for two things: a simple personal project to attempt and to make a list of FreeBSD related kenel/userland project for people that are interested (I have seen multiple requests for this). While looking through the lists (http://www.cs.uml.edu/~acahalan/linux/22wishlist.html http://www.phys.uu.nl/~riel/mm-patch/todo.html http://roadrunner.swansea.uk.linux.org/jobs.shtml), I had a few questions: some of these appear to already be done and I just wanted general feedback. If people could get back to me, I would be happy to add the information to a project page for aspiring system hackers. If not, you get to hear people keep asking about things to do. -jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 21:44:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27443 for freebsd-current-outgoing; Fri, 18 Dec 1998 21:44:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27438 for ; Fri, 18 Dec 1998 21:44:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA65015; Fri, 18 Dec 1998 21:44:25 -0800 (PST) To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: make release failure: osreldate.h In-reply-to: Your message of "Fri, 18 Dec 1998 23:28:36 EST." <199812190428.XAA29321@bb01f39.unx.sas.com> Date: Fri, 18 Dec 1998 21:44:25 -0800 Message-ID: <65011.914046265@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > auth.h types.h xdr.h auth_des.h des.h des_crypt.h /R/stage/trees/bin/usr/inc lude/rpc > install -C -o root -g wheel -m 444 /usr/src/include/osreldate.h /R/stage/tr ees/bin/usr/include > install: /usr/src/include/osreldate.h: No such file or directory > *** Error code 71 Yeah, somebody busted this recently. Still looking into why. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 23:04:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04330 for freebsd-current-outgoing; Fri, 18 Dec 1998 23:04:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04324 for ; Fri, 18 Dec 1998 23:04:28 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id XAA65270 for ; Fri, 18 Dec 1998 23:04:27 -0800 (PST) To: current@FreeBSD.ORG Subject: I almost hate to suggest this... Date: Fri, 18 Dec 1998 23:04:26 -0800 Message-ID: <65265.914051066@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Because if phk's well-described "bike shelter effect" takes place here, where the smallest most inconsequential changes generate the largest number of flames and general commentary, we're in for a very rough ride indeed over the following suggestion: Index: Makefile =================================================================== RCS file: /home/ncvs/src/sbin/mount/Makefile,v retrieving revision 1.7 diff -u -u -r1.7 Makefile --- Makefile 1998/03/08 14:50:00 1.7 +++ Makefile 1998/12/19 06:58:21 @@ -6,6 +6,8 @@ MAN8= mount.8 # We do NOT install the getmntopts.3 man page. +LINKS= ${BINDIR}/mount ${BINDIR}/mount_ufs + # We support the ROOTSLICE_HUNT hack CFLAGS+=-DROOTSLICE_HUNT The idea here is that there's a mount_foo for every value of foo EXCEPT for ufs, an omission which has always bugged me. It makes the shell script writer's job harder since you can't just cons together "mount_", an fs type and some device/mountpoint args to build a mount command for any arbitrary fs type - you have to special-case UFS just for lack of this one silly link and plus it just looks less orthogonal to have a single exception. Not that this is the poor-man's work-around. A more proper fix would entail hacking mount(8) to recognise the argv(0) == "mount_ufs" case and spit out a usage message in the event that you just say "mount_ufs" without args, just as the other mount_foo options do. As a symlink, it still functions properly as mount_ufs but the default argless behavior is to show the list of mounted filesystems, as one would expect with an unmodified mount(8). Let the flames begin! :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 18 23:58:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09274 for freebsd-current-outgoing; Fri, 18 Dec 1998 23:58:18 -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 XAA09269 for ; Fri, 18 Dec 1998 23:58:17 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA00562; Fri, 18 Dec 1998 23:56:45 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdeoU560; Sat Dec 19 07:56:43 1998 Date: Fri, 18 Dec 1998 23:56:39 -0800 (PST) From: Julian Elischer To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: make release failure: osreldate.h In-Reply-To: <199812190428.XAA29321@bb01f39.unx.sas.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this fails when you use SHARED=symlinks one time and then try use SHARED=copies. certainly the installation of /usr/share/examples fails miserably in that way and I think it's related.. I've had problems with osreldate.h for ages. I often need to do some kludges (something to do with breaking some links somewhere. julian On Fri, 18 Dec 1998, John W. DeBoskey wrote: > Hi, > > Subject says it all... I remember some discussion about this file > not too long ago... > > Thanks! > John > > auth.h types.h xdr.h auth_des.h des.h des_crypt.h /R/stage/trees/bin/usr/include/rpc > install -C -o root -g wheel -m 444 /usr/src/include/osreldate.h /R/stage/trees/bin/usr/include > install: /usr/src/include/osreldate.h: No such file or directory > *** Error code 71 > > Stop. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 00:11:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10982 for freebsd-current-outgoing; Sat, 19 Dec 1998 00:11:00 -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 AAA10974 for ; Sat, 19 Dec 1998 00:10:56 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id AAA14887; Sat, 19 Dec 1998 00:10:24 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma014875; Sat, 19 Dec 98 00:09:58 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id AAA27615; Sat, 19 Dec 1998 00:09:58 -0800 (PST) From: Archie Cobbs Message-Id: <199812190809.AAA27615@bubba.whistle.com> Subject: Re: asleep()/await(), M_AWAIT, etc... In-Reply-To: <199812170805.AAA89361@apollo.backplane.com> from Matthew Dillon at "Dec 17, 98 00:05:29 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sat, 19 Dec 1998 00:09:58 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > We add an asleep() kernel function to complement tsleep(). asleep() > works like tsleep() in that it adds the process to the appropriate > slpque, but asleep() does *not* put the process to sleep. Instead it > returns immediately. The process stays runnable. Additional calls > to asleep() (or a call to tsleep()) removes the proc from any slpque > and re-adds it to the new one. i.e. only the most recent call is > effective. > > We add an await() kernel function. This function initiates any timeout > and puts the process to sleep, but only if it is still on a sleep queue. > If someone (i.e. an interrupt) wakes up the sleep address after the > process calls asleep() but before it calls await(), the slpque is > cleared and the await() winds up being a NOP. Hmm.. sounds interesting. Seems like one problem is that most function calls have the semantics that they don't return until the job they are supposed to do is finished. This would change. So you would have to adjust all the upper layer functions to take account of this change in semantics (they'd have to know to call await() at the least, of course). Also, this only works once; you can't call two subroutines in a row that both call asleep(), because the second asleep() will erase the first. But in certain cases where you don't need to hold a lock for the duration of the lengthy operation it would definitely help reduce contention. It would be interesting to see a list of specific cases where this could be used and would make a significant difference. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 00:32:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12925 for freebsd-current-outgoing; Sat, 19 Dec 1998 00:32:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12919 for ; Sat, 19 Dec 1998 00:32:35 -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 TAA26239; Sat, 19 Dec 1998 19:32:31 +1100 Date: Sat, 19 Dec 1998 19:32:31 +1100 From: Bruce Evans Message-Id: <199812190832.TAA26239@godzilla.zeta.org.au> To: current@FreeBSD.ORG, jkh@zippy.cdrom.com Subject: Re: I almost hate to suggest this... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Because if phk's well-described "bike shelter effect" takes place >here, where the smallest most inconsequential changes generate the >largest number of flames and general commentary, we're in for >a very rough ride indeed over the following suggestion: Especially when they are "wrong" :-). >Index: Makefile >=================================================================== >RCS file: /home/ncvs/src/sbin/mount/Makefile,v >retrieving revision 1.7 >diff -u -u -r1.7 Makefile >--- Makefile 1998/03/08 14:50:00 1.7 >+++ Makefile 1998/12/19 06:58:21 >@@ -6,6 +6,8 @@ > MAN8= mount.8 > # We do NOT install the getmntopts.3 man page. > >+LINKS= ${BINDIR}/mount ${BINDIR}/mount_ufs >+ > # We support the ROOTSLICE_HUNT hack > CFLAGS+=-DROOTSLICE_HUNT > > >The idea here is that there's a mount_foo for every value of foo >EXCEPT for ufs, an omission which has always bugged me. It makes the mount_foo should almost never be used directly. It should be in /libexec to inhibit misuse. Use `mount -t foo'. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 00:36:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13393 for freebsd-current-outgoing; Sat, 19 Dec 1998 00:36:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13387 for ; Sat, 19 Dec 1998 00:36:06 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id AAA81425; Sat, 19 Dec 1998 00:35:57 -0800 (PST) To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-reply-to: Your message of "Sat, 19 Dec 1998 19:32:31 +1100." <199812190832.TAA26239@godzilla.zeta.org.au> Date: Sat, 19 Dec 1998 00:35:57 -0800 Message-ID: <81421.914056557@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > mount_foo should almost never be used directly. It should be in /libexec Then why have mount_foo at all? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 00:44:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13998 for freebsd-current-outgoing; Sat, 19 Dec 1998 00:44:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13993 for ; Sat, 19 Dec 1998 00:44:07 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA27053; Sat, 19 Dec 1998 00:44:05 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id AAA26204; Sat, 19 Dec 1998 00:44:04 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA11936; Sat, 19 Dec 1998 00:44:03 -0800 (PST) From: Don Lewis Message-Id: <199812190844.AAA11936@salsa.gv.tsc.tdk.com> Date: Sat, 19 Dec 1998 00:44:03 -0800 In-Reply-To: Matthew Dillon "asleep()/await(), M_AWAIT, etc..." (Dec 17, 12:05am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: asleep()/await(), M_AWAIT, etc... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 17, 12:05am, Matthew Dillon wrote: } Subject: asleep()/await(), M_AWAIT, etc... } We add an await() kernel function. This function initiates any timeout } and puts the process to sleep, but only if it is still on a sleep queue. } If someone (i.e. an interrupt) wakes up the sleep address after the } process calls asleep() but before it calls await(), the slpque is } cleared and the await() winds up being a NOP. How likely is this to happen if the process doesn't go to sleep for some other reason inbetween the asleep() and the await()? The CPU can execute a *lot* of code in the time it takes for physical I/O to happen. } The purpose of the new routines is to allow blocking conditions to } propogate up a subroutine chain and get handled at a higher level rather } then at a lower level in those areas of code that cannot afford to } leave exclusive locks sitting around. For example, if bread() blocks } waiting for a low level disk I/O on a block device, the vnode remains } locked throughout which badly mars potential parallelism when multiple } programs are accessing the same file. There is no reason to leave the } high level vnode locked while bringing a page into the VM buffer cache! What happens if some other process decides to truncate the file while another process is in the middle of paging in a piece of it? If there is no reason to care about this sort of thing, then there is no reason to hold the lock across the bread(), which would probably be a simple tweak to the existing code. I suspect that's not the case. If you want to get some parallelism, it might be simpler to implement shared and exclusive locks. Operations that can operate in parallel (such as reads) would use shared locks, whereas some other operations would need to use exclusive locks. } Another example: If a piece of critically locked code needs to allocate } memory but cannot afford to block with the lock intact, we can implement } M_AWAIT. The code would allocate memory using M_AWAIT and if the } allocation fails would be able to unwind the lock(s), await(), and retry. } This is something the current code cannot do at all. Most things that allocate memory want to scribble on it right after they allocate it. Using M_AWAIT would take a fair amount of rewriting. You can already do something similar without M_AWAIT by using M_NOWAIT. If that fails, unwind the lock, use M_WAITOK, and relock the object. However, it would probably be cleaner to just do do MALLOC(..., M_WAITOK) before grabbing the lock, if possible. There may be cases where this is not possible. For example, the amount of the memory you need to allocate depends on the object that you have locked. If you have the object unlocked while the memory is being allocated, another process may touch the object while it is unlocked and you'll end up allocating the wrong amount of memory. The only scheme that works in this case is locking the object first and leaving it locked across MALLOC(..., M_WAITOK). NOTE: some of the softupdates panics before 3.0-RELEASE were caused by vnodes inadvertently being unlocked and then relocked in some low level routines, which allowed files to be fiddled with by one process while another process thought it had exclusive access. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 00:56:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14931 for freebsd-current-outgoing; Sat, 19 Dec 1998 00:56:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14926 for ; Sat, 19 Dec 1998 00:56:23 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA27086 for ; Sat, 19 Dec 1998 00:56:23 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id AAA26341 for ; Sat, 19 Dec 1998 00:56:21 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA11948 for current@freebsd.org; Sat, 19 Dec 1998 00:56:20 -0800 (PST) From: Don Lewis Message-Id: <199812190856.AAA11948@salsa.gv.tsc.tdk.com> Date: Sat, 19 Dec 1998 00:56:19 -0800 X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: current@FreeBSD.ORG Subject: adding policy tuning knobs to my F_SETOWN/SIGIO/SIGURG enhancements Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still looking for comments on this. Eivind was the only one who spoke up when I posted it to -hackers. He was in favor of leaving the policy compiled in. I'd like to commit this or something like it in the next couple of days. The questions still stand. ===== Forwarded from -hackers ============== My previous security enhancements to the F_SETOWN/SIGIO/SIGURG in the 3.0 kernel code made some policy decisions that were hard-wired into the code but were commented in case someone needed to change them. I've decided that would be good to allow the security policy to be tuned using some sysctl knobs. The attached patch adds two policy adjustments, kern.security.setown_restrict, and kern.security.async_io_cred_check, which can be used to limit the process or process group that can be specified to F_SETOWN, and whether credentials should be checked before delivering the signals. Questions: Should these variables live under kern.security, directly under kern, or elsewhere? I also want to add some other security related tunables in other parts of the kernel. Assuming they should also live under kern.security, where should "SYSCTL_NODE(_kern, OID_AUTO, security, ...)" live? I've already got kern.security sysctl variables in two different files ... Any other comments on this patch are welcome. --- kern_descrip.c.orig Wed Nov 11 03:08:32 1998 +++ kern_descrip.c Sat Dec 12 23:39:50 1998 @@ -392,7 +392,24 @@ * * After permission checking, add a sigio structure to the sigio list for * the process or process group. + * + * The setown_restrict variable sets a policy which may restrict the allowable + * process/group argument for F_SETOWN/FIOSETOWN. An argument of 0 is + * always allowed. + * 0 - There are no restrictions, any existing process or process group + * may be specified. + * 1 - Any process or process group specified must belong to the same + * session as the current process. + * 2 - Only the current process group or a process in the current process + * group may be specified. This is the default. + * 3 - Only the current process may be specified. + * */ +static int setown_restrict = 2; +SYSCTL_NODE(_kern, OID_AUTO, security, CTLFLAG_RW, 0, ""); +SYSCTL_INT(_kern_security, OID_AUTO, setown_restrict, + CTLFLAG_RW|CTLFLAG_SECURE, &setown_restrict, 0, ""); + int fsetown(pgid, sigiop) pid_t pgid; @@ -411,30 +428,20 @@ proc = pfind(pgid); if (proc == NULL) return (ESRCH); - /* - * Policy - Don't allow a process to FSETOWN a process - * in another session. - * - * Remove this test to allow maximum flexibility or - * restrict FSETOWN to the current process or process - * group for maximum safety. - */ - else if (proc->p_session != curproc->p_session) + if (setown_restrict > 2 && proc != curproc || + setown_restrict > 1 && proc->p_pgrp != curproc->p_pgrp || + setown_restrict > 0 && + proc->p_session != curproc->p_session) return (EPERM); pgrp = NULL; } else /* if (pgid < 0) */ { pgrp = pgfind(-pgid); if (pgrp == NULL) return (ESRCH); - /* - * Policy - Don't allow a process to FSETOWN a process - * in another session. - * - * Remove this test to allow maximum flexibility or - * restrict FSETOWN to the current process or process - * group for maximum safety. - */ - else if (pgrp->pg_session != curproc->p_session) + if (setown_restrict > 2 || + setown_restrict > 1 && pgrp != curproc->p_pgrp || + setown_restrict > 0 && + pgrp->pg_session != curproc->p_session) return (EPERM); proc = NULL; } --- kern_sig.c.orig Tue Dec 8 20:40:50 1998 +++ kern_sig.c Sun Dec 13 00:10:50 1998 @@ -1358,9 +1358,16 @@ } /* - * Send a signal to a SIGIO or SIGURG to a process or process group using - * stored credentials rather than those of the current process. + * Send a SIGIO or SIGURG signal to a process or process group in + * response to an I/O event. + * + * If async_io_cred_check is nonzero, the stored credentials from + * the process that did the F_SETOWN/FIOSETOWN are first checked + * to see if it is permissible to send the signal. */ +static int async_io_cred_check = 1; +SYSCTL_INT(_kern_security, OID_AUTO, async_io_cred_check, + CTLFLAG_RW|CTLFLAG_SECURE, &async_io_cred_check, 0, ""); void pgsigio(sigio, signum, checkctty) struct sigio *sigio; @@ -1370,15 +1377,17 @@ return; if (sigio->sio_pgid > 0) { - if (CANSIGIO(sigio->sio_ruid, sigio->sio_ucred, - sigio->sio_proc)) + if (!async_io_cred_check || + CANSIGIO(sigio->sio_ruid, sigio->sio_ucred, + sigio->sio_proc)) psignal(sigio->sio_proc, signum); } else if (sigio->sio_pgid < 0) { struct proc *p; for (p = sigio->sio_pgrp->pg_members.lh_first; p != NULL; p = p->p_pglist.le_next) - if (CANSIGIO(sigio->sio_ruid, sigio->sio_ucred, p) && + if ((!async_io_cred_check || + CANSIGIO(sigio->sio_ruid, sigio->sio_ucred, p)) && (checkctty == 0 || (p->p_flag & P_CONTROLT))) psignal(p, signum); } =========================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 01:53:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA18859 for freebsd-current-outgoing; Sat, 19 Dec 1998 01:53:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18854 for ; Sat, 19 Dec 1998 01:53:09 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id BAA07138; Sat, 19 Dec 1998 01:53:06 -0800 (PST) (envelope-from dillon) Date: Sat, 19 Dec 1998 01:53:06 -0800 (PST) From: Matthew Dillon Message-Id: <199812190953.BAA07138@apollo.backplane.com> To: Don Lewis Cc: freebsd-current@FreeBSD.ORG Subject: Re: asleep()/await(), M_AWAIT, etc... References: <199812190844.AAA11936@salsa.gv.tsc.tdk.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Dec 17, 12:05am, Matthew Dillon wrote: :} Subject: asleep()/await(), M_AWAIT, etc... : :} We add an await() kernel function. This function initiates any timeout :} and puts the process to sleep, but only if it is still on a sleep queue. :} If someone (i.e. an interrupt) wakes up the sleep address after the :} process calls asleep() but before it calls await(), the slpque is :} cleared and the await() winds up being a NOP. : :How likely is this to happen if the process doesn't go to sleep for some :other reason inbetween the asleep() and the await()? The CPU can execute :a *lot* of code in the time it takes for physical I/O to happen. Well, the idea is for asleep() to not interfere with a normal sleep. If a process does an asleep() and then, for some reason, does a normal sleep or another asleep() without waiting for the prior event to occur, the original asleep() condition is lost and an await() later on that, code-wise, was expecting to wait for the condition earmarked by the original asleep() will not wait for it, instead causing an immediate return and thus an immediate retry. This shouldn't cause a problem, though. The chance of a condition being signalled after an asleep() but before the associated await(), assuming no blocking inbetween, is not very high but I expect it would happen under normal operating conditions maybe 1 out of every 5000 or so uses. The situation becomes more interesting when you get into SMP situations, especially once we start allowing all N processors to enter into supervisor mode and run mainstream supervisor code simultaniously. It should be noted that event interlocks can be done very easily with asleep()/await() without having to mess with the ipl mask. Since the ipl mask doesn't work when SMP supervisor operation is allowed on > 1 cpu at a time, it is just as well that another mechanism exists. :} The purpose of the new routines is to allow blocking conditions to :} propogate up a subroutine chain and get handled at a higher level rather :} then at a lower level in those areas of code that cannot afford to :} leave exclusive locks sitting around. For example, if bread() blocks :} waiting for a low level disk I/O on a block device, the vnode remains :} locked throughout which badly mars potential parallelism when multiple :} programs are accessing the same file. There is no reason to leave the :} high level vnode locked while bringing a page into the VM buffer cache! : :What happens if some other process decides to truncate the file while :another process is in the middle of paging in a piece of it? If there :is no reason to care about this sort of thing, then there is no reason :to hold the lock across the bread(), which would probably be a simple Well, in this particular case we don't care because it isn't the pagein into the process's VM space that we are waiting on, it's the bringing of the page from the underlying block device into the filesystem cache, which is independant of the overlayed filesystem structure and was queued to the disk device on the original attempt. In the case of a truncate, this higher level operation will not effect the lower level I/O in progress (or, if it does abort it, will wakeup anybody waiting for that page anyway). The wakeup occurs and the original requesting task retries its vm fault. On this attempt it notices the fact that the file has been truncated and does the right thing. Effectively we are retrying an operation 'from scratch', so the fact that the truncate occured is handled properly. Another indirect use for asleep() would be to unwind locks when an inner lock cannot be obtained and to then retry the entire sequence later when the inner lock 'might' become attainable. You do this by asleep()ing on the event of the inner lock getting unlocked, then popping back through the call stack and unwinding the locks you were able to get, then sleeping (calling await()) at the top level (holding no locks) and retrying when you wake up again. This wouldn't work very well for complex locking (4 or more levels), but I would guess that it would work quite nicely for the 2-layer locking that we typically do in the kernel. :} allocation fails would be able to unwind the lock(s), await(), and retry. :} This is something the current code cannot do at all. : :Most things that allocate memory want to scribble on it right after they :allocate it. Using M_AWAIT would take a fair amount of rewriting. You :can already do something similar without M_AWAIT by using M_NOWAIT. If :that fails, unwind the lock, use M_WAITOK, and relock the object. However, :it would probably be cleaner to just do do MALLOC(..., M_WAITOK) before :grabbing the lock, if possible. The point here is that if you cannot afford to block in the procedure that is doing the memory allocation, you may be able to block in a higher level procedure. M_NOWAIT and M_WAITOK cannot cover that situation at all. M_AWAIT (which is like M_NOWAIT but it calls asleep() as well as returns NULL) *can*. The only implementation requirement is that the procedure call chain being implemented with asleep() understand a temporary failure condition and do the right thing with it (eventually await() and retry from the top level). :There may be cases where this is not possible. For example, the amount of :the memory you need to allocate depends on the object that you have locked. Oh, certainly, but asleep/await do not have to be implemented everywhere, only in those places where it makes sense to. We aren't removing any of the prior functionality, we are adding new functionality to allow us to solve deadlock situations that occur with the old functionality. :If you have the object unlocked while the memory is being allocated, another :process may touch the object while it is unlocked and you'll end up allocating :the wrong amount of memory. The only scheme that works in this case is :locking the object first and leaving it locked across MALLOC(..., M_WAITOK). : :NOTE: some of the softupdates panics before 3.0-RELEASE were caused by I think you missed the primary point of asleep()/await(). The idea is that you pop back through subroutine levels, undoing the entire operation (or a good portion of it), the 'retry later'. What you describe is precisely the already-existant situation that asleep() and await() can be used to fix. This might sound expensive, but most of the places where we would need to use asleep()/await() would not actually have to pop back more then a few subroutine levels to be effective. -Matt :vnodes inadvertently being unlocked and then relocked in some low level :routines, which allowed files to be fiddled with by one process while :another process thought it had exclusive access. Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 01:55:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19190 for freebsd-current-outgoing; Sat, 19 Dec 1998 01:55:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19185 for ; Sat, 19 Dec 1998 01:55:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id BAA07155; Sat, 19 Dec 1998 01:55:09 -0800 (PST) (envelope-from dillon) Date: Sat, 19 Dec 1998 01:55:09 -0800 (PST) From: Matthew Dillon Message-Id: <199812190955.BAA07155@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... References: <65265.914051066@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Index: Makefile :=================================================================== :RCS file: /home/ncvs/src/sbin/mount/Makefile,v :retrieving revision 1.7 :diff -u -u -r1.7 Makefile :--- Makefile 1998/03/08 14:50:00 1.7 :+++ Makefile 1998/12/19 06:58:21 :@@ -6,6 +6,8 @@ : MAN8= mount.8 : # We do NOT install the getmntopts.3 man page. : :+LINKS= ${BINDIR}/mount ${BINDIR}/mount_ufs :+ : # We support the ROOTSLICE_HUNT hack : CFLAGS+=-DROOTSLICE_HUNT : : :The idea here is that there's a mount_foo for every value of foo :EXCEPT for ufs, an omission which has always bugged me. It makes the :shell script writer's job harder since you can't just cons together :"mount_", an fs type and some device/mountpoint args to build a mount :command for any arbitrary fs type - you have to special-case UFS just :for lack of this one silly link and plus it just looks less orthogonal :to have a single exception. : :Not that this is the poor-man's work-around. A more proper fix :would entail hacking mount(8) to recognise the argv(0) == "mount_ufs" :case and spit out a usage message in the event that you just :say "mount_ufs" without args, just as the other mount_foo options do. :As a symlink, it still functions properly as mount_ufs but the default :argless behavior is to show the list of mounted filesystems, as one :would expect with an unmodified mount(8). : :Let the flames begin! :-) : :- Jordan When someone has time available, making a separate mount_ufs and rewriting mount itself to always exec a sub-mount binary would be even better. But as a poor-man's fix the above would work fine. -Matt :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 01:58:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19591 for freebsd-current-outgoing; Sat, 19 Dec 1998 01:58:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19585 for ; Sat, 19 Dec 1998 01:58:22 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id UAA15663 for ; Sat, 19 Dec 1998 20:58:04 +1100 (EST) Date: Sat, 19 Dec 1998 20:58:04 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: freebsd-current@FreeBSD.ORG Subject: an addition to top(1) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've always thought that top(1) should display the system uptime. Here's a patch. The code was cut straight out of /usr/src/usr.bin/w/w.c Merry Christmas! # cd /usr/src/contrib/top # rcsdiff -r1.1 -u display.c =================================================================== RCS file: display.c,v retrieving revision 1.1 diff -u -r1.1 display.c --- display.c 1998/12/18 02:23:39 1.1 +++ display.c 1998/12/19 09:12:03 @@ -30,6 +30,10 @@ #include #include +#include +#include +#include + #include "screen.h" /* interface to screen package */ #include "layout.h" /* defines for screen position layout */ #include "display.h" @@ -240,11 +244,51 @@ } } +struct timeval boottime; +time_t now; +time_t uptime; + i_timeofday(tod) time_t *tod; { + int days, hrs, i, mins, secs; + int mib[2]; + size_t size; + + (void)time(&now); + + /* + * Print how long system has been up. + * (Found by looking getting "boottime" from the kernel) + */ + mib[0] = CTL_KERN; + mib[1] = KERN_BOOTTIME; + size = sizeof(boottime); + if (sysctl(mib, 2, &boottime, &size, NULL, 0) != -1 && + boottime.tv_sec != 0) { + uptime = now - boottime.tv_sec; + uptime += 30; + days = uptime / 86400; + uptime %= 86400; + hrs = uptime / 3600; + uptime %= 3600; + mins = uptime / 60; + secs = uptime % 60; + + if (smart_terminal) + { + Move_to((screen_width - 24) - (days > 9 ? 1 : 0), 0); + } + else + { + fputs(" ", stdout); + } + + printf(" up %d+%02d:%02d:%02d", days, hrs, mins, secs); + } + /* * Display the current time. * "ctime" always returns a string that looks like this: -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 02:00:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19934 for freebsd-current-outgoing; Sat, 19 Dec 1998 02:00:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19929 for ; Sat, 19 Dec 1998 02:00:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id CAA81873; Sat, 19 Dec 1998 02:00:40 -0800 (PST) To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-reply-to: Your message of "Sat, 19 Dec 1998 01:55:09 PST." <199812190955.BAA07155@apollo.backplane.com> Date: Sat, 19 Dec 1998 02:00:39 -0800 Message-ID: <81864.914061639@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When someone has time available, making a separate mount_ufs > and rewriting mount itself to always exec a sub-mount binary > would be even better. But as a poor-man's fix the above Hmmm. I always got the feeling that the original CSRG folk deliberately stuck "ufs mounting" into mount(8) so that one binary could be copied around easily for fixit purposes, ufs being the one fs that could be deemed somewhat in the "bootstrap" class and perhaps worthy of special treatment. Then again, maybe not, I'm just saying that this most obvious lack of orthogonality (not writing mount(8) as a minimal wrapper) may well have been deliberate. I've bcc'd somebody who might know the real story in any case. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 02:06:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20158 for freebsd-current-outgoing; Sat, 19 Dec 1998 02:06:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20141 for ; Sat, 19 Dec 1998 02:05:55 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id CAA07224; Sat, 19 Dec 1998 02:05:54 -0800 (PST) (envelope-from dillon) Date: Sat, 19 Dec 1998 02:05:54 -0800 (PST) From: Matthew Dillon Message-Id: <199812191005.CAA07224@apollo.backplane.com> To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Re: asleep()/await(), M_AWAIT, etc... References: <199812190809.AAA27615@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Matthew Dillon writes: :> We add an asleep() kernel function to complement tsleep(). asleep() :> works like tsleep() in that it adds the process to the appropriate :> slpque, but asleep() does *not* put the process to sleep. Instead it :> returns immediately. The process stays runnable. Additional calls :> to asleep() (or a call to tsleep()) removes the proc from any slpque :> and re-adds it to the new one. i.e. only the most recent call is :> effective. :> :> We add an await() kernel function. This function initiates any timeout :> and puts the process to sleep, but only if it is still on a sleep queue. :> If someone (i.e. an interrupt) wakes up the sleep address after the :> process calls asleep() but before it calls await(), the slpque is :> cleared and the await() winds up being a NOP. : :Hmm.. sounds interesting. Seems like one problem is that most :function calls have the semantics that they don't return until :the job they are supposed to do is finished. This would change. : :So you would have to adjust all the upper layer functions to take :account of this change in semantics (they'd have to know to call :await() at the least, of course). : :Also, this only works once; you can't call two subroutines :in a row that both call asleep(), because the second asleep() :will erase the first. : :But in certain cases where you don't need to hold a lock for :the duration of the lengthy operation it would definitely help :reduce contention. : :It would be interesting to see a list of specific cases where :this could be used and would make a significant difference. It's something we could work on from the bottom-up. We would not have to change everything at once. For example, giving the (kernel) malloc an M_AWAIT capability would require fixing kmem_malloc and vm_page_alloc, but nothing else. We can then 'fix' routines that call malloc individually (and then only if necessary or prudent). Those routines can still maintain the fully-synchronous semantics their callers expect and still use the new malloc feature. Ultimately the capability can be propogated back further, especially with those functions that are already passed a flags argument and can thus operate both fully synchronously and semi-synchronously. Truth be said, we don't want to necessarily change the semantics for all the routines to be totally asynchronous - probably 80% of the cases can remain synchronous because they guarentee the lock order. Ultimately I think around 20% of the current code would benefit from a new locking scheme, especially when SMP locks are brought in further. The biggest use of the feature would be the short-term unwinding of locks in order to be able to block without holding any (or too many), and the second biggest use would be to unwind an upper-level lock when we fail to get a lower-level lock in a non-blocking fashion (i.e. unwind a potential deadlock) in order to retry both locks later when we 'might' be able to get the inner lock again. ( This situation is actually somewhat more complex since the issue of deadlock detection is rather complex, but it would solve most 2-level deadlock situations almost trivially ). -Matt :-Archie : :___________________________________________________________________________ :Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 02:07:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20245 for freebsd-current-outgoing; Sat, 19 Dec 1998 02:07:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20237 for ; Sat, 19 Dec 1998 02:07:27 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id CAA07232; Sat, 19 Dec 1998 02:07:24 -0800 (PST) (envelope-from dillon) Date: Sat, 19 Dec 1998 02:07:24 -0800 (PST) From: Matthew Dillon Message-Id: <199812191007.CAA07232@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... References: <81864.914061639@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hmmm. I always got the feeling that the original CSRG folk :deliberately stuck "ufs mounting" into mount(8) so that one binary :could be copied around easily for fixit purposes, ufs being the one fs :that could be deemed somewhat in the "bootstrap" class and perhaps :worthy of special treatment. : :Then again, maybe not, I'm just saying that this most obvious lack of :orthogonality (not writing mount(8) as a minimal wrapper) may well :have been deliberate. I've bcc'd somebody who might know the real :story in any case. :) : :- Jordan Well, a fixit floppy could just contain mount_ufs :-). I've gotten into the habit of calling mount_mfs directly myself, and even mount_nfs on my old nfs boot floppy. I don't even think I had 'mount' on that floppy! -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 03:01:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24772 for freebsd-current-outgoing; Sat, 19 Dec 1998 03:01:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24758 for ; Sat, 19 Dec 1998 03:01:26 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id MAA36252; Sat, 19 Dec 1998 12:00:18 +0100 (CET) To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-reply-to: Your message of "Fri, 18 Dec 1998 23:04:26 PST." <65265.914051066@zippy.cdrom.com> Date: Sat, 19 Dec 1998 12:00:17 +0100 Message-ID: <36250.914065217@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <65265.914051066@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >Because if phk's well-described "bike shelter effect" takes place >here, where the smallest most inconsequential changes generate the >largest number of flames and general commentary, we're in for >a very rough ride indeed over the following suggestion: > >Index: Makefile >=================================================================== >RCS file: /home/ncvs/src/sbin/mount/Makefile,v >retrieving revision 1.7 >diff -u -u -r1.7 Makefile >--- Makefile 1998/03/08 14:50:00 1.7 >+++ Makefile 1998/12/19 06:58:21 >@@ -6,6 +6,8 @@ > MAN8= mount.8 > # We do NOT install the getmntopts.3 man page. > >+LINKS= ${BINDIR}/mount ${BINDIR}/mount_ufs >+ > # We support the ROOTSLICE_HUNT hack > CFLAGS+=-DROOTSLICE_HUNT Jordan, you forgot I also told you how to avoid the bike-shelter effect: The trick is to cut and past a couple of Terrys emails into the commit message, that way nobody reads though to the bottom where they would discover the telling +1 mumble/foo/bar line :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 03:06:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25333 for freebsd-current-outgoing; Sat, 19 Dec 1998 03:06:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25326 for ; Sat, 19 Dec 1998 03:06:18 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.56.86]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA6D7; Sat, 19 Dec 1998 12:06:14 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 19 Dec 1998 12:12:29 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Mike Jackson Subject: Re: Buildworld fails Cc: freebsd-current@FreeBSD.ORG, Alfred Perlstein , "John A. Hengstler" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 18 Dec 1998, Mike Jackson wrote: > >> On Fri, 18 Dec 1998, Alfred Perlstein wrote: >> >> > On Fri, 18 Dec 1998, John A. Hengstler wrote: >> > >> > > Normally I would agree with this, except, 2.2.8 make buildworlds and >> > > installworlds, work fine on same machine.. >> > hmmm, are you thrashing at all? how is your memory/swap? maybe you have >> > dying deamons, but with regular processes? >> Why don't you see what happens when you mount /usr with softupdates? Let >> me guess, the build has been going on for quite some time before it dies? >> Also, are you running X Windows at the same time as doing the make world? >> Which would cause you to start swapping. >> >> I've seen the problems you describe on my machine, but have been able to >> get around them by mounting /usr with softupdates/noatime and not using >> the box when the world is being built (hence, very little swap space is >> used). But a make world remains a compiler pass if somewhat large. How on earth does a make world justify the reason that a box cannot be used? I may be thick regarding this but every make world I have done was under X and with me reading/writing email. Sure the compilation take somewhat longer, but in no way does it justify the reason to not touch the box. And I can also not see what swapping should have to do with the failure of a compiler pass. Someone is bound to point me in the right direction if I am spewing forth erroneously thought-up ideas. --- Jeroen Ruigrok van der Werven Pax vobiscum... asmodai(at)wxs.nl Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 03:16:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26322 for freebsd-current-outgoing; Sat, 19 Dec 1998 03:16:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26317 for ; Sat, 19 Dec 1998 03:16:01 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id DAA27751; Sat, 19 Dec 1998 03:15:50 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id DAA28140; Sat, 19 Dec 1998 03:15:49 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id DAA12134; Sat, 19 Dec 1998 03:15:48 -0800 (PST) From: Don Lewis Message-Id: <199812191115.DAA12134@salsa.gv.tsc.tdk.com> Date: Sat, 19 Dec 1998 03:15:47 -0800 In-Reply-To: Matthew Dillon "Re: asleep()/await(), M_AWAIT, etc..." (Dec 19, 1:53am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Matthew Dillon , Don Lewis Subject: Re: asleep()/await(), M_AWAIT, etc... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 19, 1:53am, Matthew Dillon wrote: } Subject: Re: asleep()/await(), M_AWAIT, etc... } } :What happens if some other process decides to truncate the file while } :another process is in the middle of paging in a piece of it? If there } :is no reason to care about this sort of thing, then there is no reason } :to hold the lock across the bread(), which would probably be a simple } In the case of a truncate, this higher level operation will not effect } the lower level I/O in progress (or, if it does abort it, will wakeup } anybody waiting for that page anyway). The wakeup occurs and the } original requesting task retries its vm fault. On this attempt it } notices the fact that the file has been truncated and does the right } thing. Effectively we are retrying an operation 'from scratch', so } the fact that the truncate occured is handled properly. It should work ok if you start 'from scratch', but this might require quite a bit of rewinding. } Another indirect use for asleep() would be to unwind locks when an inner } lock cannot be obtained and to then retry the entire sequence later when } the inner lock 'might' become attainable. You do this by asleep()ing on } the event of the inner lock getting unlocked, then popping back through } the call stack and unwinding the locks you were able to get, then } sleeping (calling await()) at the top level (holding no locks) and retrying } when you wake up again. This wouldn't work very well for complex locking } (4 or more levels), but I would guess that it would work quite nicely } for the 2-layer locking that we typically do in the kernel. One case that I thought of could cause you to spin. lock object (succeeds) MALLOC(..., M_AWAIT) (succeeds) MALLOC(..., M_AWAIT) (fails) After the second MALLOC fails, you'll free the first chunk of memory allocated and unlock the object. When you call await(), it'll succeed because memory is available because of the memory that was just freed. The first MALLOC() will succeed, and the second one will fail again. The way this code is written, it looks like only two levels, but it really is 3 by your criteria and thus is getting into questionable territory. } :} allocation fails would be able to unwind the lock(s), await(), and retry. } :} This is something the current code cannot do at all. } : } :Most things that allocate memory want to scribble on it right after they } :allocate it. Using M_AWAIT would take a fair amount of rewriting. You } :can already do something similar without M_AWAIT by using M_NOWAIT. If } :that fails, unwind the lock, use M_WAITOK, and relock the object. However, } :it would probably be cleaner to just do do MALLOC(..., M_WAITOK) before } :grabbing the lock, if possible. } } The point here is that if you cannot afford to block in the procedure } that is doing the memory allocation, you may be able to block in a } higher level procedure. M_NOWAIT and M_WAITOK cannot cover that } situation at all. M_AWAIT (which is like M_NOWAIT but it calls } asleep() as well as returns NULL) *can*. The only implementation } requirement is that the procedure call chain being implemented with } asleep() understand a temporary failure condition and do the right } thing with it (eventually await() and retry from the top level). This really only buys you something if the memory allocation is conditional. If it is unconditional and you can block in the higher level procedure, then you could just use M_WAITOK there and pass in the buffer (or call a procedure that hides the memory allocation to satisfy your object oriented programming sensibilites), but this is more or less equivalent to doing the allocation at the beginning of the lower level procedure. } :NOTE: some of the softupdates panics before 3.0-RELEASE were caused by } } I think you missed the primary point of asleep()/await(). The idea } is that you pop back through subroutine levels, undoing the entire } operation (or a good portion of it), the 'retry later'. What you } describe is precisely the already-existant situation that asleep() and } await() can be used to fix. This might sound expensive, but most } of the places where we would need to use asleep()/await() would not } actually have to pop back more then a few subroutine levels to be } effective. For pathname traversal, if you give up a lock, I think you have to restart from the beginning. This scheme definitely changes the way you need to think about locking. In the traditional locking scheme, one wants to minimize the time that locks are held in order to minimize contention, and the correct locking order must be obeyed in order to avoid deadlocks. In your scheme, the amount of work done between locking nested locks should be minimized, since all this work must be undone and then redone if the inner lock can't be immediately obtained. One still wants to mimimize the amount of time locks are held, and your scheme does reduce the time the outer locks are held, but it is contention for the inner locks that is costly. Deadlocks should not occur due to incorrect locking order, but performance could be bad if locks are done in the wrong order. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 04:10:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA04861 for freebsd-current-outgoing; Sat, 19 Dec 1998 04:10:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA04855 for ; Sat, 19 Dec 1998 04:10:15 -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 XAA06347; Sat, 19 Dec 1998 23:10:08 +1100 Date: Sat, 19 Dec 1998 23:10:08 +1100 From: Bruce Evans Message-Id: <199812191210.XAA06347@godzilla.zeta.org.au> To: bde@zeta.org.au, jkh@zippy.cdrom.com Subject: Re: I almost hate to suggest this... Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> mount_foo should almost never be used directly. It should be in /libexec > >Then why have mount_foo at all? So that mount(8) is easy to extend. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 04:20:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05604 for freebsd-current-outgoing; Sat, 19 Dec 1998 04:20:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05580 for ; Sat, 19 Dec 1998 04:20:02 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id NAA36646; Sat, 19 Dec 1998 13:18:16 +0100 (CET) To: Bruce Evans cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-reply-to: Your message of "Sat, 19 Dec 1998 23:10:08 +1100." <199812191210.XAA06347@godzilla.zeta.org.au> Date: Sat, 19 Dec 1998 13:18:16 +0100 Message-ID: <36644.914069896@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812191210.XAA06347@godzilla.zeta.org.au>, Bruce Evans writes: >>> mount_foo should almost never be used directly. It should be in /libexec >> >>Then why have mount_foo at all? > >So that mount(8) is easy to extend. So that you don't get a spagetti program (like for instance ifconfig) which needs to know about all sorts of weird filesystems ideosyncracies. In difference from Bruce I think that mount_XXX is the primary interface, (and as such agree with jordan that mount_ufs should be there). Mount is just a backwards compatibility gadget now. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 05:03:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07587 for freebsd-current-outgoing; Sat, 19 Dec 1998 05:03:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www0f.netaddress.usa.net (www0f.netaddress.usa.net [204.68.24.35]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA07582 for ; Sat, 19 Dec 1998 05:03:50 -0800 (PST) (envelope-from slpalmer@netscape.net) Received: (qmail 11044 invoked by uid 60001); 19 Dec 1998 13:03:49 -0000 Message-ID: <19981219130349.11043.qmail@www0f.netaddress.usa.net> Received: from 204.68.24.35 by www0f via web-mailer(R2.6) on Sat Dec 19 13:03:49 GMT 1998 Date: 19 Dec 98 13:03:49 America/Fort_Wayne From: Stephen Palmer To: gp@oitunix.oit.umass.edu, freebsd-current@FreeBSD.ORG Subject: Request fo help with Zip Drive on vpo0 in -current] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id FAA07583 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It doesn't look like the crospost to -current worked.. I'm re-sending it. slpalmer slpalmer@netscape.net gp@oitunix.oit.umass.edu wrote: > On Fri, Dec 18, 1998 at 02:46:24AM +0000, Stephen Palmer wrote: > > Can someone offer assistance in getting a Parallel Port Zip Drive > > working under FreeBSD 3.0-current? I've searched the mailing lists > > and LINT, and added what I thought were the correct options. > > As you can read in my dmesg output below, my ppbus and vpo0 do > > get detected, but da0 and scbus do not. A gentle nudge in the right > > direction would be most graciously appreciated! > > > > Stephen L. Palmer > > slpalmer@netscape.net > > I think this got broken in -current. I had my ||-port zip running > on -current from the last week or so of Nov., but it didn't work > with sources from Dec. 12. > > I hope the cross-post is appropriate here. I thought some > -current types should see this. > > Greg > > > > > KERNEL CONFIG FILE > > > > machine "i386" > > cpu "I486_CPU" > > cpu "I586_CPU" > > cpu "I686_CPU" > > ident MIDEARTH > > maxusers 32 > > options MATH_EMULATE #Support for x87 emulation > > options INET #InterNETworking > > options FFS #Berkeley Fast Filesystem > > options FFS_ROOT #FFS usable as root device [keep this!] > > options MFS #Memory Filesystem > > options MFS_ROOT #MFS usable as root device, "MFS" req'ed > > options NFS #Network Filesystem > > options NFS_ROOT #NFS usable as root device, "NFS" req'ed > > options MSDOSFS #MSDOS Filesystem > > options "CD9660" #ISO 9660 Filesystem > > options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed > > options PROCFS #Process filesystem > > options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] > > options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device > > options UCONSOLE #Allow users to grab the console > > options FAILSAFE #Be conservative > > options USERCONFIG #boot -c editor > > options VISUAL_USERCONFIG #visual boot -c editor > > config kernel root on wd0 > > controller isa0 > > controller eisa0 > > controller pci0 > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 > > disk fd0 at fdc0 drive 0 > > disk fd1 at fdc0 drive 1 > > tape ft0 at fdc0 drive 2 > > options "CMD640" # work around CMD640 chip deficiency > > controller wdc0 at isa? port "IO_WD1" bio irq 14 > > disk wd0 at wdc0 drive 0 > > disk wd1 at wdc0 drive 1 > > controller wdc1 at isa? port "IO_WD2" bio irq 15 > > 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 > > device wfd0 #IDE Floppy (e.g. LS-120) > > controller dpt0 > > device sc0 at isa? port IO_KBD conflicts tty irq 1 > > device npx0 at isa? port IO_NPX irq 13 > > device apm0 at isa? disable flags 0x31 # Advanced Power Management > > device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 > > device sio1 at isa? port "IO_COM2" tty irq 5 > > device sio2 at isa? disable port "IO_COM3" tty irq 5 > > device sio3 at isa? disable port "IO_COM4" tty irq 9 > > device psm0 at isa? port IO_KBD conflicts tty irq 12 > > pseudo-device loop > > pseudo-device ether > > pseudo-device sl 1 > > pseudo-device ppp 1 > > pseudo-device tun 1 > > pseudo-device pty 16 > > pseudo-device gzip # Exec gzipped a.out's > > options KTRACE #kernel tracing > > options SYSVSHM > > > > controller pnp0 > > device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 > > > > controller smbus0 > > device smb0 at smbus? > > controller iicbus0 > > controller iicbb0 > > device ic0 at iicbus? > > device iic0 at iicbus? > > device iicsmb0 at iicbus? > > controller ppc0 at isa? port ? tty irq 7 > > controller ppbus0 > > controller vpo0 at ppbus? > > controller scbus0 at vpo0 > > device da0 > > > > END KERNEL CONFIG FILE > > > > OUTPUT FROM 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 #5: Wed Dec 16 23:46:24 CST 1998 > > slpalmer@midearth.dyn.ml.org:/usr/src/sys/compile/MIDEARTH > > Timecounter "i8254" frequency 1193182 Hz > > CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) > > Origin = "AuthenticAMD" Id = 0x562 Stepping=2 > > Features=0x8001bf > > real memory = 67108864 (65536K bytes) > > config> quit > > avail memory = 62722048 (61252K bytes) > > Probing for devices on PCI bus 0: > > chip0: rev 0x01 on pci0.0.0 > > chip1: rev 0x01 on pci0.7.0 > > ide_pci0: rev 0x01 on pci0.7.1 > > chip2: rev 0x01 on pci0.7.3 > > vga0: rev 0x03 int a irq 10 on pci0.8.0 > > Probing for PnP devices: > > CSN 1 Vendor ID: CTL00c5 [0xc5008c0e] Serial 0x1b9e4f4c Comp ID: PNPb02f > > [0x2fb0d041] > > pcm1 (SB16pnp sn 0x1b9e4f4c) at 0x220-0x22f irq 9 drq 1 flags 0x17 > > on isa > > 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 5 on isa > > sio1: type 16550A > > psm0 not found at 0x60 > > ppc: parallel port found at 0x378 > > ppc0 at 0x378 irq 7 on isa > > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > > vpo0: on ppbus 0 > > vpo0: EPP 1.9 mode > > pcm0 not probed due to drq conflict with pcm1 at 1 > > 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: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S > > wdc1 at 0x170-0x177 irq 15 on isa > > wdc1: unit 0 (atapi): , removable, intr, dma, iordis > > wcd0: 4134KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray > > wcd0: no disc inside, unlocked > > wdc1: unit 1 (atapi): , removable, dma, iordy > > wcd1: 344/1034KB/sec, 1024KB cache, audio play, 128 volume levels, ejectable > > tray > > wcd1: no disc inside, unlocked, lock protected > > npx0 on motherboard > > npx0: INT 16 interface > > Waiting 15 seconds for SCSI devices to settle > > changing root device to wd0s2a > > > > END DMESG OUTPUT > > > > --- | > > Stephen L. Palmer | Sprint Paranet > > slpalmer@netscape.net \|/ slpalmer@sprintparanet.com > > "There are thousands of intelligent species in the > > Universe, and they all own cats." -Unknown > > > > ____________________________________________________________________ > > More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message --- | Stephen L. Palmer | Sprint Paranet slpalmer@netscape.net \|/ slpalmer@sprintparanet.com "There are thousands of intelligent species in the Universe, and they all own cats." -Unknown ____________________________________________________________________ More than just email--Get your FREE Netscape WebMail account today at http://home.netscape.com/netcenter/mail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 07:57:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20324 for freebsd-current-outgoing; Sat, 19 Dec 1998 07:57:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA20310 for ; Sat, 19 Dec 1998 07:57:08 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 22996 invoked by uid 1001); 19 Dec 1998 15:57:05 +0000 (GMT) To: jkh@zippy.cdrom.com Cc: bde@zeta.org.au, current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-Reply-To: Your message of "Sat, 19 Dec 1998 00:35:57 -0800" References: <81421.914056557@zippy.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 19 Dec 1998 16:57:05 +0100 Message-ID: <22994.914083025@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > mount_foo should almost never be used directly. It should be in /libexec > > Then why have mount_foo at all? Please don't remove mount_foo. I've been able to save several installations by using mount_nfs directly from a nearby FreeBSD box (and have been unable to use the fixit floppy because of floppy drive problems). 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 Sat Dec 19 08:24:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22478 for freebsd-current-outgoing; Sat, 19 Dec 1998 08:24:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22473 for ; Sat, 19 Dec 1998 08:24:25 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id RAA21540 for ; Sat, 19 Dec 1998 17:30:32 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sat, 19 Dec 1998 17:30:31 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: BootFORTH - demo floppy 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, Some people asked me to prepare a demo floppy for our new bootloader. Well, here's an early Christmas gift for you: http://www.freebsd.org/~picobsd/bootldr.bin For those of you already familiar with it, the only surprise will be a cons25-compatible terminal emulator, together with some screen manipulation Forth words (at-xy, clear, but also frame drawing). The kernel provided on the floppy is standard PicoBSD "dial" version, so it's not only a demo - you can do some real things with it as well. Thing which needs to be done IMHO before we can really make use of Forth in the bootloader is to change built-in commands so that they accept arguments from stack. As it is now, you can create a word which contains 'boot', but you cannot use 'boot kernel1'. Have fun! Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 08:31:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23259 for freebsd-current-outgoing; Sat, 19 Dec 1998 08:31:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA23254 for ; Sat, 19 Dec 1998 08:31:44 -0800 (PST) (envelope-from nordwick@scam.XCF.Berkeley.EDU) Message-Id: <199812191631.IAA23254@hub.freebsd.org> Received: (qmail 4225 invoked by uid 27268); 19 Dec 1998 16:33:00 -0000 Received: from localhost (HELO scam.XCF.Berkeley.EDU) (sendmail-bs@127.0.0.1) by localhost with SMTP; 19 Dec 1998 16:33:00 -0000 To: Matthew Dillon To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-Reply-To: Your message of "Sat, 19 Dec 1998 01:55:09 PST." <199812190955.BAA07155@apollo.backplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4222.914085179.1@scam.XCF.Berkeley.EDU> Date: Sat, 19 Dec 1998 08:33:00 -0800 From: "Jay Nordwick" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When someone has time available, making a separate mount_ufs > and rewriting mount itself to always exec a sub-mount binary > would be even better. But as a poor-man's fix the above > would work fine. > > -Matt > This was embarrasingly easy. I just got the binaries done in about 2 minutes, but didn't do anything to the man pages. I can send a patch, but sense I don't know where to even begin on hacking the man pages, I didn't think that it was useful. It looks like it might have been a seperate executable originally. -jay (P.S., for somebody who can fix the man page, here is how to do the rest: in mount.c get rid of the 2 line test to see if type is ufs, in mount_ufs.c change mount_ufs(int,char*[]) to main(int,char*[]), of course fix the makefiles) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 10:27:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02910 for freebsd-current-outgoing; Sat, 19 Dec 1998 10:27:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news2.du.gtn.com (news2.du.gtn.com [194.77.9.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02904 for ; Sat, 19 Dec 1998 10:27:11 -0800 (PST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by news2.du.gtn.com (8.8.6/8.8.6) with ESMTP id TAA00089 for ; Sat, 19 Dec 1998 19:27:04 +0100 (MET) Received: (from ticso@localhost) by cicely7.cicely.de (8.9.0/8.9.0) id TAA00973; Sat, 19 Dec 1998 19:26:56 +0100 (CET) Message-ID: <19981219192655.22722@cicely.de> Date: Sat, 19 Dec 1998 19:26:55 +0100 From: Bernd Walter To: freebsd-current@FreeBSD.ORG Subject: buildworld broken in linux_sysvec.c Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -DCOMPAT_LINUX -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/elf/var/d1/src-c5/src/sys/modules/linux -I/usr/obj/elf/var/d1/src-c5/src/sys/modules/linux/@ -I/usr/obj/elf/var/d1/src-c5/src/tmp/usr/include -c /var/d1/src-c5/src/sys/modules/linux/../../i386/linux/linux_util.c /var/d1/src-c5/src/sys/modules/linux/../../i386/linux/linux_sysvec.c: In function `linux_sendsig': /var/d1/src-c5/src/sys/modules/linux/../../i386/linux/linux_sysvec.c:242: parse error before `)' /var/d1/src-c5/src/sys/modules/linux/../../i386/linux/linux_sysvec.c:196: warning: unused variable `frame' /var/d1/src-c5/src/sys/modules/linux/../../i386/linux/linux_sysvec.c: At top level: /var/d1/src-c5/src/sys/modules/linux/../../i386/linux/linux_sysvec.c:259: parse error before `if' /var/d1/src-c5/src/sys/modules/linux/../../i386/linux/linux_sysvec.c:273: parse error before `:' /var/d1/src-c5/src/sys/modules/linux/../../i386/linux/linux_sysvec.c:274: parse error before `:' cc -O -pipe -DCOMPAT_LINUX -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/elf/var/d1/src-c5/src/sys/modules/linux -I/usr/obj/elf/var/d1/src-c5/src/sys/modules/linux/@ -I/usr/obj/elf/var/d1/src-c5/src/tmp/usr/include -c /var/d1/src-c5/src/sys/modules/linux/../../i386/linux/imgact_linux.c *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error -- B.Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 10:41:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03958 for freebsd-current-outgoing; Sat, 19 Dec 1998 10:41:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03949; Sat, 19 Dec 1998 10:41:22 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id NAA00390; Sat, 19 Dec 1998 13:41:19 -0500 (EST) (envelope-from lee) Message-ID: <19981219134118.A311@tidalwave.net> Date: Sat, 19 Dec 1998 13:41:18 -0500 From: Lee Cremeans To: Howard , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c Reply-To: lcremean@tidalwave.net References: <199812191605.IAA12460@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812191605.IAA12460@freefall.freebsd.org>; from Howard on Sat, Dec 19, 1998 at 08:05:20AM -0800 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 19, 1998 at 08:05:20AM -0800, Howard wrote: > foxfair 1998/12/19 08:05:20 PST > > Modified files: > sys/pci pcisupport.c > Log: > Add more non-Intel family ((new)) chipset, just like VIA technology MVP3 > AcerLabs Aladdin-V. It makes the PCI probing work when system booting. I > will try to merge some additional funtion(i.e. wdc1 problem cause tons of > PR appear :<) ASAP if I could. I've been poking around ide_pci.c, and it seems that not having explicit Acer Aladdin support in there not only screws with UDMA support, it also keeps the second channel from working correctly. This chipset fsr has its BMISTA_SIMPLEX flag set, and ide_pci.c is seeing this and assuming (wrongly) that the Aladdin IDE controller is single-channel. (Yes, it says it's just disabling DMA, but the code actually disables _everything_ on the second channel since wd.c uses ide_pci.c to probe for devices. It'd probably be a good idea to not check for SIMPLEX anymore.) Also, I'm looking at how to set up the Aladdin UDMA regsters, and I want to do it in a similar way to the PIIX4, but the different settings and such confuse me a bit. I'll keep reading. -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 11:07:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06399 for freebsd-current-outgoing; Sat, 19 Dec 1998 11:07:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-sfx201--064.sirius.net [205.134.235.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06391 for ; Sat, 19 Dec 1998 11:07:50 -0800 (PST) (envelope-from parag@cgt.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id LAA80764 for ; Sat, 19 Dec 1998 11:07:13 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199812191907.LAA80764@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: More symptoms of VM (or related) oddities in 3.0-CURRENT X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-5132980690" Date: Sat, 19 Dec 1998 11:07:12 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_-5132980690 Content-Type: text/plain; charset=us-ascii I've been following the discussions about folks having a variety of problems with what appears to be VM in the latest versions: running out of processes, swap space, and daemons dying. I thought I'd add my observations of my latest kernel (and system) upgrade. I just found some time to upgrade to the latest CURRENT of Dec 18: @(#)FreeBSD 3.0-CURRENT #19: Fri Dec 18 15:52:34 PST 1998 from my previous kernel of Oct 23: @(#)FreeBSD 3.0-CURRENT #9: Fri Oct 23 21:33:56 PDT 1998 I've also installed the latest boot-loader and am running an ELF kernel, as well as ELF binaries. I did this in steps and found the same symptoms below as I did with the latest CURRENT in the aout flavor. My previous kernel was aout, and while the install distribution was ELF, all of X was still aout as I wasn't keen on downloading those huge binaries over modem. (I just picked up the latest 3.0 CDs.) The "dmesg" output is appended to this note. Essentially, I'm running SMP on a dual-PII/300 system with 256Mb RAM and 256Mb swap, two UW SCSI disks, and softupdates enabled on all partitions. Each night I run cvsup and then fire off a "make buildworld -j8", just to keep the machine warm :-). I'm the only user of this machine - it's both my daily desktop and work-related build system. When I have time, it's handy to have a prebuilt world to install instead of having to wait another 1.5 hours or so. Now the interesting bit: With the earlier kernel, it would never touch swap space. It ran just fine out of RAM pretty much no matter what load I put on the machine and ran without touching swap for weeks at a time. With the latest kernel, it's actually touched the swap space for the first time ever - and only in a few hours after bootup when I fired off one buildworld -j8. Addmittedly, it only used 309K of swap, and with last nights (failed) build, it's now used 608K. But it's very odd that it's used any at all. Another oddness. With the earlier kernel, I had no trouble running -j12 builds. With the latest kernel, -j8 initially started failing until I bumped up maxusers from 10 to 32. There were no compiler errors - it looked like it ran out of file-descriptors (!) for some reason and either compiles or makes started failing. So I bumped up maxusers as a temporary workaround. I've also appended my config file below. top always shows quite a lot of inactive memory - from 90M and up. There's plenty of cache, buffers, and free space, so I don't understand why it ever touches swap now when it didn't before. Are the ELF X binaries taking up *that* much more memory? Perhaps something odd with ELF shared-libs? I haven't managed to crash the machine but I can see where people with less RAM and less swap could start running out of resources fairly easily. I do have some time to experiment so an pointers to areas of code to examine or patches to try would be much appreciated. Thanks! -- Parag Patel --==_Exmh_-5132980690 Content-Type: text/plain ; name="PINHEAD"; charset=us-ascii Content-Description: PINHEAD Content-Disposition: attachment; filename="PINHEAD" # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.112 1998/07/20 20:00:29 msmith Exp $ machine "i386" #cpu "I386_CPU" #cpu "I486_CPU" cpu "I586_CPU" # for npx0 cpu "I686_CPU" ident PINHEAD maxusers 32 #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options NETATALK #Appletalk communications protocols #options NETATALKDEBUG options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MFS #Memory File System options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root device options FFS_ROOT #FFS usable as root device [keep this!] options NFS_ROOT #NFS usable as root device options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] #options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options SCSI_DELAY=2000 options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options USER_LDT #allow user-level control of i386 ldt - wine options "MD5" options "VM86" #options VESA options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options SOFTUPDATES #Copyrighted FFS changes # These provide support for System V shared memory/semaphores/message-queues # options SYSVSHM options SYSVSEM options SYSVMSG # POSIX P1003.1B # # Real time extensions added int the 1993 Posix # P1003_1B: Infrastructure # _KPOSIX_PRIORITY_SCHEDULING: Build in _POSIX_PRIORITY_SCHEDULING # _KPOSIX_VERSION: Version kernel is built for # options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # Turn on kernel debugging # options DDB config kernel root on da0 controller isa0 #controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # Unless you know very well what you're doing, leave ft0 at drive 2, or # remove the line entirely if you don't need it. Trying to configure # it on another unit might cause surprises, see PR kern/7176. #tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xA0FFA0FF vector wdintr #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller wdc1 at isa? disable port "IO_WD2" bio irq 15 flags 0xA0FFA0FF vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 disk wd0 at wdc1 drive 0 disk wd1 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM #device acd0 #IDE CD-ROM, CD-R/RW device wcd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) # Enable PnP support in the kernel. This allows you to automaticly # attach to PnP cards for drivers that support it and allows you to # configure cards from USERCONFIG. See pnp(4) for more info. controller pnp0 # Luigi's snd code (use INSTEAD of snd0 and all VOXWARE drivers!). # You may also wish to enable the pnp controller with this, for pnp # sound cards. # device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 vector pcmintr # Joystick(s) # device joy0 at isa? port "IO_GAME" device joy1 at isa? port "IO_GAME" # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ncr0 #controller amd0 #controller ahb0 controller ahc0 #controller isp0 # The aic7xxx driver will attempt to use memory mapped I/O for all PCI # controllers that have it configured only if this option is set. Unfortunately, # this doesn't work on some motherboards, which prevents it from being the # default. options AHC_ALLOW_MEMIO # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. The options # line following dpt0 here is also currently a *required* option for it. #controller dpt0 #options DPT_MEASURE_PERFORMANCE #controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 #base SCSI code #device ch0 #SCSI media changers device da0 #SCSI direct access devices (aka disks) device sa0 #SCSI tapes device cd0 #SCSI CD-ROMs #device od0 #SCSI optical disk device pass0 #CAM passthrough driver #device worm0 at scbus? # SCSI worm #device pt0 at scbus? # SCSI processor type #device sctarg0 at scbus? # SCSI target #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # #device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device lpt1 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device de0 device fxp0 #device tl0 #device tx0 #device vx0 #device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device ex0 at isa? port? net irq? vector exintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr #device cs0 at isa? port 0x300 net irq ? vector csintr pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 16 #Berkeley packet filter pseudo-device vn #Vnode driver (turns a file into a device) #pseudo-device ccd 4 #Concatenated disk driver --==_Exmh_-5132980690 Content-Type: text/plain ; name="dmesg"; charset=us-ascii Content-Description: dmesg Content-Disposition: attachment; filename="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 #19: Fri Dec 18 15:52:34 PST 1998 parag@pinhead.parag.codegen.com:/usr/src/sys/compile/PINHEAD Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II (686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80fbff real memory = 268435456 (262144K bytes) config> quit avail memory = 258289664 (252236K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xf02d9000. 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.4.0 ide_pci0: rev 0x01 on pci0.4.1 chip3: rev 0x01 on pci0.4.3 ahc0: rev 0x00 int a irq 19 on pci0.6.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: rev 0x05 int a irq 17 on pci0.11.0 fxp0: Ethernet address 00:a0:c9:da:98:26 Probing for devices on PCI bus 1: vga0: rev 0x00 int a irq 16 on pci1.0.0 Probing for PnP devices: CSN 1 Vendor ID: CTL00e4 [0xe4008c0e] Serial 0x08de2f0a Comp ID: PNPb02f [0x2fb0d041] pcm1 (SB16pnp sn 0x08de2f0a) at 0x220-0x22f irq 10 drq 1 flags 0x15 on isa Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> pcm0 not probed due to drq conflict with pcm1 at 1 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 sio3 at 0x2e8-0x2ef irq 9 on isa sio3: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 at 0x278-0x27f on isa psm0 at 0x60-0x64 irq 12 on motherboard psm0: model MouseMan+, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (atapi): , removable, accel, ovlap, dma, iordis wcd0: 5512KB/sec, 256KB cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked joy0 at 0x201 on isa joy0: joystick joy1 not probed due to I/O address conflict with joy0 at 0x201 npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 2 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! pass4 at ahc0 bus 0 target 6 lun 0 pass4: Fixed Scanner SCSI-2 device pass4: 3.300MB/s transfers changing root device to da0s2a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C) cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable Worm SCSI-2 device cd0: 10.0MB/s transfers (10.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates (da0:ahc0:0:0:0): tagged openings now 64 (da2:ahc0:0:2:0): tagged openings now 64 --==_Exmh_-5132980690-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 11:52:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10787 for freebsd-current-outgoing; Sat, 19 Dec 1998 11:52:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10781 for ; Sat, 19 Dec 1998 11:52:27 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id LAA28234 for ; Sat, 19 Dec 1998 11:52:25 -0800 Date: Sat, 19 Dec 1998 11:52:25 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-current@FreeBSD.ORG Subject: massive compilation breakage in user space Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This seems pretty annoyingly bad: from mt.c:52: /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:11: parse error before `int8_t' /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:11: warning: data definition has no type or storage class /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:12: parse error before `int16_t' /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:12: warning: data definition has no type or storage class /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:13: parse error before `int32_t' /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:13: warning: data definition has no type or storage class /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:16: parse error before `uint8_t' /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:16: warning: data definition has no type or storage class /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:17: parse error before `uint16_t' /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:17: warning: data definition has no type or storage class /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:18: parse error before `uint32_t' /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:18: warning: data definition has no type or storage class /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:21: parse error before `intptr_t' /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:21: warning: data definition has no type or storage class /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:22: parse error before `uintptr_t' /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:22: warning: data definition has no type or storage class In file included from /usr/src/usr.bin/mt/../../sys/sys/types.h:49, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 11:59:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11423 for freebsd-current-outgoing; Sat, 19 Dec 1998 11:59:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thor.pcc.edu (thor.oci.pcc.edu [198.106.46.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11404; Sat, 19 Dec 1998 11:59:55 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from c063.beaverton.stream.com ([208.13.191.137]) by thor.pcc.edu (8.8.5/8.8.5) with SMTP id NAA29560; Sat, 19 Dec 1998 13:08:22 -0800 Message-ID: <00eb01be2b89$b30648c0$f301040a@c063.beaverton.stream.com> From: "Wiliam Woods" To: "FBSD_CURRENT" , "Freebsd_Questions" Subject: StarOffice 4.0 Date: Sat, 19 Dec 1998 11:56:39 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am planning on useing StarOffice for my office suite, unfortunaltely, the only version I can find anywhere is 4.0 sp3. Does this work on FreeBSD? I am running 3.0 curent and I know 5.0 does not 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 Dec 19 12:15:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12760 for freebsd-current-outgoing; Sat, 19 Dec 1998 12:15:04 -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 MAA12755 for ; Sat, 19 Dec 1998 12:15:02 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA20947; Sat, 19 Dec 1998 12:00:40 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma020943; Sat, 19 Dec 98 12:00:37 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA01212; Sat, 19 Dec 1998 12:00:36 -0800 (PST) From: Archie Cobbs Message-Id: <199812192000.MAA01212@bubba.whistle.com> Subject: Re: asleep()/await(), M_AWAIT, etc... In-Reply-To: <199812191005.CAA07224@apollo.backplane.com> from Matthew Dillon at "Dec 19, 98 02:05:54 am" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sat, 19 Dec 1998 12:00:36 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > :> We add an asleep() kernel function to complement tsleep(). asleep() > :> works like tsleep() in that it adds the process to the appropriate > :> slpque, but asleep() does *not* put the process to sleep. Instead it > :> returns immediately. The process stays runnable. Additional calls > :> to asleep() (or a call to tsleep()) removes the proc from any slpque > :> and re-adds it to the new one. i.e. only the most recent call is > :> effective. > :> > :> We add an await() kernel function. This function initiates any timeout > :> and puts the process to sleep, but only if it is still on a sleep queue. > :> If someone (i.e. an interrupt) wakes up the sleep address after the > :> process calls asleep() but before it calls await(), the slpque is > :> cleared and the await() winds up being a NOP. > : > :Hmm.. sounds interesting. Seems like one problem is that most > :function calls have the semantics that they don't return until > :the job they are supposed to do is finished. This would change. > > It's something we could work on from the bottom-up. We > would not have to change everything at once. For example, giving Well, since the amount of code to implement it is not that much, and it allows beneficial changes to be made incrementally and as appropriate, I don't see any reason why it shouldn't be added. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 12:27:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13839 for freebsd-current-outgoing; Sat, 19 Dec 1998 12:27:40 -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 MAA13830 for ; Sat, 19 Dec 1998 12:27:36 -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 NAA07279; Sat, 19 Dec 1998 13:27:23 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA13367; Sat, 19 Dec 1998 13:27:22 -0700 Date: Sat, 19 Dec 1998 13:27:22 -0700 Message-Id: <199812192027.NAA13367@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: Bruce Evans , current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-Reply-To: <81421.914056557@zippy.cdrom.com> References: <199812190832.TAA26239@godzilla.zeta.org.au> <81421.914056557@zippy.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > mount_foo should almost never be used directly. It should be in /libexec > > Then why have mount_foo at all? So you can add new FS types w/out having to hack userland code? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 13:11:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18373 for freebsd-current-outgoing; Sat, 19 Dec 1998 13:11:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18368 for ; Sat, 19 Dec 1998 13:11:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id NAA20772; Sat, 19 Dec 1998 13:11:24 -0800 (PST) (envelope-from dillon) Date: Sat, 19 Dec 1998 13:11:24 -0800 (PST) From: Matthew Dillon Message-Id: <199812192111.NAA20772@apollo.backplane.com> To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG, "Jordan K. Hubbard" , julian@whistle.com (Julian Elischer), Luoqi Chen Subject: Re: asleep()/await(), M_AWAIT, etc... References: <199812192000.MAA01212@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> It's something we could work on from the bottom-up. We :> would not have to change everything at once. For example, giving : :Well, since the amount of code to implement it is not that much, :and it allows beneficial changes to be made incrementally and as :appropriate, I don't see any reason why it shouldn't be added. : :-Archie :___________________________________________________________________________ :Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com I'm kinda at odds with myself in regards to my own feelings :-) On the one hand I want to start moving on a new framework to solve deadlock problems and SMP issues. On the otherhand, we have to make 3.0.1 a rock solid release which means no major changes to the core. But, then also, I really believe that Luoqi's fixes to vfs_bio.c need to go in ASAP. Yesterday, if possible! What I would like to do is to start to commit asleep/await as well as an 'inactive' framework of support around those two functions. i.e. to start to add the capability to low level routines such as adding an M_AWAIT flag to malloc, but not actually commit anything that *uses* those capabilities until after the 3.0.1 release. This would help my own testing greatly because I would be able to commit about 70% of the stuff I have dangling in my cvs tree without incuring any operational changes to other people's kernels. Then, after the 3.0.1 release we can start to make real progress on deadlock and SMP issues throughout the system. The same effort required to clean up potential deadlocks will also go a long way towards helping us move the SMP locks deeper into the kernel and to prevent cascade locking failures from being able to occur. For example, if you have a procedure call situation a->b->c where 'c' may currently block, it is not possible to use a simple_lock in b (much less a) that surrounds c. But if c has a non-blocking capability it can call asleep() instead of tsleep() and pop back up to b. b can detect the situation, unlock it's simple_lock and block, then relock and retry. If a is a vnode op and uses a normal (but SMP capable) exclusive lock on the vnode it operates under, and b is able to use a simple_lock for its critical code section (say a is manipulating the vnode and b is manipulating the buffer cache or page tables), then that is all we need to make syscall 'a' operate concurrently in supervisor mode from multiple cpus. Another big area where this has a major effect is the TCP stack: Use normal (but SMP capable) exclusive locks on individual TCBs, and use simple_locks around core route table and mbuf functions that could previously block in a lower-level allocation but now don't because they use M_AWAIT (and thus can release the simple_lock prior to blocking). And, finally, probably the most significant area of effect in a post-3.0.1 commit of code using the new capability would be in read(), and page faults on VFS nodes - especially important when you have a number of processes accessing the same file, shared library, or binary image. Right now if I understand the code correctly, a blocked read or page fault leaves the associated file vnode locked, which effectively serializes any disk I/O on that file and, worse, blocks access to elements of the file that are already in the cache. post-3.0.1 we would be able to issue the underlying disk I/O to the buffer cache and asleep() on the necessary page, then pop back up and unlock the vnode before blocking. This would allow other processes to do I/O on the same vnode, at least for concurrent read()'s on the same file by different processes. Even better, we could use a secondary fcntl lock like subsystem attached to the vnode to guarentee read() and write() atomicy, allowing us to not have to leave an exclusive lock on the vnode itself for the duration of the syscall, giving us 100% concurrency on file I/O with SMP. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 13:17:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19087 for freebsd-current-outgoing; Sat, 19 Dec 1998 13:17:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19082 for ; Sat, 19 Dec 1998 13:16:58 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id XAA27223; Sat, 19 Dec 1998 23:48:15 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.1/8.9.1) with ESMTP id XAA03412; Sat, 19 Dec 1998 23:34:33 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199812192034.XAA03412@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: mjacob@feral.com cc: freebsd-current@FreeBSD.ORG Subject: Re: massive compilation breakage in user space In-reply-to: Your message of "Sat, 19 Dec 1998 11:52:25 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 19 Dec 1998 23:34:33 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > This seems pretty annoyingly bad: > > from mt.c:52: > /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:11: parse error before > `int8_t' > /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:11: warning: data definition > has no type or storage class Are you building this particular program without 'make world'? I think, this is because you get from source tree, and from /usr/include, and they are not in sync. Remove CFLAGS setting from Makefile should help. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 13:21:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19562 for freebsd-current-outgoing; Sat, 19 Dec 1998 13:21:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19557 for ; Sat, 19 Dec 1998 13:21:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id NAA28457; Sat, 19 Dec 1998 13:20:58 -0800 Date: Sat, 19 Dec 1998 13:20:57 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Dmitrij Tejblum cc: freebsd-current@FreeBSD.ORG Subject: Re: massive compilation breakage in user space In-Reply-To: <199812192034.XAA03412@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 Yes, I had to do a make includes (or make world) to fix this. On Sat, 19 Dec 1998, Dmitrij Tejblum wrote: > Matthew Jacob wrote: > > > > This seems pretty annoyingly bad: > > > > from mt.c:52: > > /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:11: parse error before > > `int8_t' > > /usr/src/usr.bin/mt/../../sys/sys/inttypes.h:11: warning: data definition > > has no type or storage class > > Are you building this particular program without 'make world'? > > I think, this is because you get from source tree, and > from /usr/include, and they are not in sync. Remove CFLAGS > setting from Makefile should help. > > Dima > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 13:22:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19646 for freebsd-current-outgoing; Sat, 19 Dec 1998 13:22:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from namodn.com (namodn.com [207.33.107.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19627; Sat, 19 Dec 1998 13:22:02 -0800 (PST) (envelope-from robert@namodn.com) Received: from localhost (robert@localhost) by namodn.com (8.8.8/8.8.8) with SMTP id NAA04969; Sat, 19 Dec 1998 13:26:43 GMT (envelope-from robert@namodn.com) Date: Sat, 19 Dec 1998 13:26:43 +0000 (GMT) From: Robert To: Wiliam Woods cc: FBSD_CURRENT , Freebsd_Questions Subject: Re: StarOffice 4.0 In-Reply-To: <00eb01be2b89$b30648c0$f301040a@c063.beaverton.stream.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 Have you looked in the freebsd ports collection? There is an older version of Star Office, 3.1 I think. It might be worth it to either test the patches, or else wait for 5.0 to be runnable under Linux emulation. -rob ( www.namodn.com ) ( robert@namodn.com ) On Sat, 19 Dec 1998, Wiliam Woods wrote: > I am planning on useing StarOffice for my office suite, unfortunaltely, the > only version I can find anywhere is 4.0 sp3. Does this work on FreeBSD? I am > running 3.0 curent and I know 5.0 does not work. > > Thanks > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 13:39:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21416 for freebsd-current-outgoing; Sat, 19 Dec 1998 13:39:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21409 for ; Sat, 19 Dec 1998 13:39:35 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id WAA00335 for ; Sat, 19 Dec 1998 22:45:53 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sat, 19 Dec 1998 22:45:52 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: Re: BootFORTH - demo floppy In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Dec 1998, Andrzej Bialecki wrote: > Hi, > > Some people asked me to prepare a demo floppy for our new bootloader. > Well, here's an early Christmas gift for you: > > http://www.freebsd.org/~picobsd/bootldr.bin It seems I should've been more descriptive in this announcement - some people were at loss what to do with it... So, let me add a little to this: this is of course a floppy image, and you're supposed to dd it onto a floppy, and boot from it. It contains the new bootloader, a bunch of helpful Forth words which can be used to build a colorful startup menu, and the kernel is one of standard PicoBSD kernels, so that you can use this for something real as well. The built-ins I was talking about are the original bootloader commands, such as set, show, load, boot, reboot, pnpscan, ls etc..., which need closer integrations with Forth engine. Namely, they should recognize the state (either interpretive, or compiling), and be able to accept parameters either from command line (like: "load -t userconfig_script kernel.config" when interpreting), or from the stack (like: s" kernel.config" s" userconfig_script" s" -t" load when compiling). As it is now, we cannot use the full Forth power to program booting behaviour because of this deficiency. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 14:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25163 for freebsd-current-outgoing; Sat, 19 Dec 1998 14:17:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25155 for ; Sat, 19 Dec 1998 14:17:22 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id AAA27981; Sun, 20 Dec 1998 00:51:36 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.1/8.9.1) with ESMTP id AAA00405; Sun, 20 Dec 1998 00:54:51 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199812192154.AAA00405@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Poul-Henning Kamp cc: Bruce Evans , jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-reply-to: Your message of "Sat, 19 Dec 1998 13:18:16 +0100." <36644.914069896@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Dec 1998 00:54:50 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In difference from Bruce I think that mount_XXX is the primary interface, > (and as such agree with jordan that mount_ufs should be there). Mount > is just a backwards compatibility gadget now. Most mount_XXX programs are somewhat broken if used as user interface. Mount(8) is the only way to mount filesystems from /etc/fstab, anyhow. I think, primary user interface is mount(8) combined with $EDITOR /etc/fstab (unless we are talking about fixit floppy, of course). Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 14:20:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25630 for freebsd-current-outgoing; Sat, 19 Dec 1998 14:20:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles151.castles.com [208.214.165.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25625 for ; Sat, 19 Dec 1998 14:20:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00657; Sat, 19 Dec 1998 14:17:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812192217.OAA00657@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: I almost hate to suggest this... In-reply-to: Your message of "Sat, 19 Dec 1998 00:35:57 PST." <81421.914056557@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 19 Dec 1998 14:17:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > mount_foo should almost never be used directly. It should be in /libexec > > Then why have mount_foo at all? Because dlopen doesn't work on static binaries, so you can't have mount_foo.so -- \\ 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 Dec 19 14:23:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25884 for freebsd-current-outgoing; Sat, 19 Dec 1998 14:23:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles151.castles.com [208.214.165.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25869 for ; Sat, 19 Dec 1998 14:23:33 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00695; Sat, 19 Dec 1998 14:21:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812192221.OAA00695@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Don Lewis cc: current@FreeBSD.ORG Subject: Re: adding policy tuning knobs to my F_SETOWN/SIGIO/SIGURG enhancements In-reply-to: Your message of "Sat, 19 Dec 1998 00:56:19 PST." <199812190856.AAA11948@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 19 Dec 1998 14:21:14 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not sure that we want to open something like this to general manipulation - it provides one more way for someone to make assumptions about the behaviour of the system. If the "secure" mode isn't ridiculously onerous, I think that it's perhaps better to leave that the only mode that's supported, ie. if someone wants to change its behaviour they need to be aware of the consequences. > I'm still looking for comments on this. Eivind was the only one who > spoke up when I posted it to -hackers. He was in favor of leaving > the policy compiled in. > > I'd like to commit this or something like it in the next couple of days. > > The questions still stand. > > > ===== Forwarded from -hackers ============== > > My previous security enhancements to the F_SETOWN/SIGIO/SIGURG in the 3.0 > kernel code made some policy decisions that were hard-wired into the code > but were commented in case someone needed to change them. I've decided > that would be good to allow the security policy to be tuned using some > sysctl knobs. The attached patch adds two policy adjustments, > kern.security.setown_restrict, and kern.security.async_io_cred_check, > which can be used to limit the process or process group that can be > specified to F_SETOWN, and whether credentials should be checked before > delivering the signals. > > Questions: > > Should these variables live under kern.security, directly under > kern, or elsewhere? > > I also want to add some other security related tunables in other > parts of the kernel. Assuming they should also live under > kern.security, where should > "SYSCTL_NODE(_kern, OID_AUTO, security, ...)" live? I've already > got kern.security sysctl variables in two different files ... > > Any other comments on this patch are welcome. > > > --- kern_descrip.c.orig Wed Nov 11 03:08:32 1998 > +++ kern_descrip.c Sat Dec 12 23:39:50 1998 > @@ -392,7 +392,24 @@ > * > * After permission checking, add a sigio structure to the sigio list for > * the process or process group. > + * > + * The setown_restrict variable sets a policy which may restrict the allowable > + * process/group argument for F_SETOWN/FIOSETOWN. An argument of 0 is > + * always allowed. > + * 0 - There are no restrictions, any existing process or process group > + * may be specified. > + * 1 - Any process or process group specified must belong to the same > + * session as the current process. > + * 2 - Only the current process group or a process in the current process > + * group may be specified. This is the default. > + * 3 - Only the current process may be specified. > + * > */ > +static int setown_restrict = 2; > +SYSCTL_NODE(_kern, OID_AUTO, security, CTLFLAG_RW, 0, ""); > +SYSCTL_INT(_kern_security, OID_AUTO, setown_restrict, > + CTLFLAG_RW|CTLFLAG_SECURE, &setown_restrict, 0, ""); > + > int > fsetown(pgid, sigiop) > pid_t pgid; > @@ -411,30 +428,20 @@ > proc = pfind(pgid); > if (proc == NULL) > return (ESRCH); > - /* > - * Policy - Don't allow a process to FSETOWN a process > - * in another session. > - * > - * Remove this test to allow maximum flexibility or > - * restrict FSETOWN to the current process or process > - * group for maximum safety. > - */ > - else if (proc->p_session != curproc->p_session) > + if (setown_restrict > 2 && proc != curproc || > + setown_restrict > 1 && proc->p_pgrp != curproc->p_pgrp || > + setown_restrict > 0 && > + proc->p_session != curproc->p_session) > return (EPERM); > pgrp = NULL; > } else /* if (pgid < 0) */ { > pgrp = pgfind(-pgid); > if (pgrp == NULL) > return (ESRCH); > - /* > - * Policy - Don't allow a process to FSETOWN a process > - * in another session. > - * > - * Remove this test to allow maximum flexibility or > - * restrict FSETOWN to the current process or process > - * group for maximum safety. > - */ > - else if (pgrp->pg_session != curproc->p_session) > + if (setown_restrict > 2 || > + setown_restrict > 1 && pgrp != curproc->p_pgrp || > + setown_restrict > 0 && > + pgrp->pg_session != curproc->p_session) > return (EPERM); > proc = NULL; > } > --- kern_sig.c.orig Tue Dec 8 20:40:50 1998 > +++ kern_sig.c Sun Dec 13 00:10:50 1998 > @@ -1358,9 +1358,16 @@ > } > > /* > - * Send a signal to a SIGIO or SIGURG to a process or process group using > - * stored credentials rather than those of the current process. > + * Send a SIGIO or SIGURG signal to a process or process group in > + * response to an I/O event. > + * > + * If async_io_cred_check is nonzero, the stored credentials from > + * the process that did the F_SETOWN/FIOSETOWN are first checked > + * to see if it is permissible to send the signal. > */ > +static int async_io_cred_check = 1; > +SYSCTL_INT(_kern_security, OID_AUTO, async_io_cred_check, > + CTLFLAG_RW|CTLFLAG_SECURE, &async_io_cred_check, 0, ""); > void > pgsigio(sigio, signum, checkctty) > struct sigio *sigio; > @@ -1370,15 +1377,17 @@ > return; > > if (sigio->sio_pgid > 0) { > - if (CANSIGIO(sigio->sio_ruid, sigio->sio_ucred, > - sigio->sio_proc)) > + if (!async_io_cred_check || > + CANSIGIO(sigio->sio_ruid, sigio->sio_ucred, > + sigio->sio_proc)) > psignal(sigio->sio_proc, signum); > } else if (sigio->sio_pgid < 0) { > struct proc *p; > > for (p = sigio->sio_pgrp->pg_members.lh_first; p != NULL; > p = p->p_pglist.le_next) > - if (CANSIGIO(sigio->sio_ruid, sigio->sio_ucred, p) && > + if ((!async_io_cred_check || > + CANSIGIO(sigio->sio_ruid, sigio->sio_ucred, p)) && > (checkctty == 0 || (p->p_flag & P_CONTROLT))) > psignal(p, signum); > } > > =========================================== > > 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 Dec 19 14:23:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25916 for freebsd-current-outgoing; Sat, 19 Dec 1998 14:23:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thor.pcc.edu (thor.oci.pcc.edu [198.106.46.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25899; Sat, 19 Dec 1998 14:23:50 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from c063.beaverton.stream.com ([208.13.191.137]) by thor.pcc.edu (8.8.5/8.8.5) with SMTP id PAA00398; Sat, 19 Dec 1998 15:32:16 -0800 Message-ID: <015801be2b9d$cd227580$f301040a@c063.beaverton.stream.com> From: "Wiliam Woods" To: "FBSD_QUESTIONS" , "FBSD_CURRENT" Subject: version of Linux Libraries is FreeBSD Emulation.... Date: Sat, 19 Dec 1998 14:20:33 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What version of the libraries (ie; 5.4.22 or ???) does FreeBSD emulate in the linux emulation? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 14:40:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27280 for freebsd-current-outgoing; Sat, 19 Dec 1998 14:40:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles151.castles.com [208.214.165.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27255; Sat, 19 Dec 1998 14:40:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00840; Sat, 19 Dec 1998 14:37:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812192237.OAA00840@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Wiliam Woods" cc: "FBSD_CURRENT" , "Freebsd_Questions" Subject: Re: StarOffice 4.0 In-reply-to: Your message of "Sat, 19 Dec 1998 11:56:39 PST." <00eb01be2b89$b30648c0$f301040a@c063.beaverton.stream.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 19 Dec 1998 14:37:58 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am planning on useing StarOffice for my office suite, unfortunaltely, the > only version I can find anywhere is 4.0 sp3. Does this work on FreeBSD? I am > running 3.0 curent and I know 5.0 does not work. Changes to support 5.0 were just recently committed. If you can hang off a couple more days, you should be able to build a world that will run it. -- \\ 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 Dec 19 14:53:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28336 for freebsd-current-outgoing; Sat, 19 Dec 1998 14:53:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles151.castles.com [208.214.165.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28329; Sat, 19 Dec 1998 14:53:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00922; Sat, 19 Dec 1998 14:51:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812192251.OAA00922@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Wiliam Woods" cc: "FBSD_QUESTIONS" , "FBSD_CURRENT" Subject: Re: version of Linux Libraries is FreeBSD Emulation.... In-reply-to: Your message of "Sat, 19 Dec 1998 14:20:33 PST." <015801be2b9d$cd227580$f301040a@c063.beaverton.stream.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 19 Dec 1998 14:51:22 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What version of the libraries (ie; 5.4.22 or ???) does FreeBSD emulate in > the linux emulation? We use the Linux libaries; the current linux_lib collection (2.6) has libc 5.4.23 as well as glibc. Our baseline is currently RedHat 5.1, will probably move to RedHat 5.2 at some stage. -- \\ 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 Dec 19 15:00:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29012 for freebsd-current-outgoing; Sat, 19 Dec 1998 15:00:56 -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 PAA29000 for ; Sat, 19 Dec 1998 15:00:44 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA15800 for freebsd-current@FreeBSD.ORG; Sun, 20 Dec 1998 00:00:23 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id F13F31513; Sun, 20 Dec 1998 00:00:16 +0100 (CET) Date: Sun, 20 Dec 1998 00:00:16 +0100 From: Ollivier Robert To: FBSD_CURRENT Subject: Re: StarOffice 4.0 Message-ID: <19981220000016.A29094@keltia.freenix.fr> Mail-Followup-To: FBSD_CURRENT References: <00eb01be2b89$b30648c0$f301040a@c063.beaverton.stream.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <00eb01be2b89$b30648c0$f301040a@c063.beaverton.stream.com>; from Wiliam Woods on Sat, Dec 19, 1998 at 11:56:39AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4871 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Wiliam Woods: > I am planning on useing StarOffice for my office suite, unfortunaltely, the > only version I can find anywhere is 4.0 sp3. Does this work on FreeBSD? I am This version works beautifully under 3.0. You have to patch the setup.bin binary and a library afterwards (because they reference /proc directly). Instructions below, taken from a mail in -hackers. > running 3.0 curent and I know 5.0 does not work. It will hopefully soon. -=- From: Andre Albsmeier > On Mon, Jun 29, 1998 at 08:59:40PM +0200, Andre Albsmeier wrote: > > However, the installed thing doesn't run properly and consumes only cpu time > > but I hadn't had time to investigate this yet... > > The installed program requires '/proc//cmdline', too. Doing that > sed-thing again on the soffice.bin will probably help you. Thanks for the hint... After modyfing lib/libsal364.so as well Staroffice 4.0 SP3 is running here. So the complete instructions are: 1. Unpack the sp3 distribution 2. cd into the Install directory (where setup.bin is) 3. sed -e 's,/proc/%u/cmdline,/compat/linux/so,' < setup.bin > setup.new 4. mv setup.new setup.bin 5. chmod 755 setup.bin 6. touch /compat/linux/so 7. ./setup The install program should run and install StarOffice. Maybe I missed some step but this is closely what I have done. Then, after installing it, go to the lib directory and do the sed command on libsal364.so: 1. sed -e 's,/proc/%u/cmdline,/compat/linux/so,' < libsal364.so > libsal364.new 2. mv libsal364.new libsal364.so 3. chmod 755 libsal364.so The new /compat/linux/so path can be anything that does not exceed the 16 characters. It only has to point to an empty file... -Andre -=- -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 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 Dec 19 15:01:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29044 for freebsd-current-outgoing; Sat, 19 Dec 1998 15:01: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 PAA29037 for ; Sat, 19 Dec 1998 15:01:05 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id AAA15851 for freebsd-current@FreeBSD.ORG; Sun, 20 Dec 1998 00:00:59 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id C68061513; Sun, 20 Dec 1998 00:02:08 +0100 (CET) Date: Sun, 20 Dec 1998 00:02:08 +0100 From: Ollivier Robert To: FBSD_CURRENT Subject: Re: version of Linux Libraries is FreeBSD Emulation.... Message-ID: <19981220000208.B29094@keltia.freenix.fr> Mail-Followup-To: FBSD_CURRENT References: <015801be2b9d$cd227580$f301040a@c063.beaverton.stream.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <015801be2b9d$cd227580$f301040a@c063.beaverton.stream.com>; from Wiliam Woods on Sat, Dec 19, 1998 at 02:20:33PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4871 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Wiliam Woods: > What version of the libraries (ie; 5.4.22 or ???) does FreeBSD emulate in > the linux emulation? Whatever version that is in the linux_lib port. The emulation layer is at the syscall one, not the library. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 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 Dec 19 15:03:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29187 for freebsd-current-outgoing; Sat, 19 Dec 1998 15:03:49 -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 PAA29182 for ; Sat, 19 Dec 1998 15:03:47 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA22261; Sat, 19 Dec 1998 15:03:14 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma022258; Sat, 19 Dec 98 15:03:04 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA03836; Sat, 19 Dec 1998 15:03:04 -0800 (PST) From: Archie Cobbs Message-Id: <199812192303.PAA03836@bubba.whistle.com> Subject: Re: asleep()/await(), M_AWAIT, etc... In-Reply-To: <199812192111.NAA20772@apollo.backplane.com> from Matthew Dillon at "Dec 19, 98 01:11:24 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sat, 19 Dec 1998 15:03:03 -0800 (PST) Cc: archie@whistle.com, freebsd-current@FreeBSD.ORG, jkh@zippy.cdrom.com, julian@whistle.com, luoqi@watermarkgroup.com X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > [ deleted ] That all sounds good to me. I'd like to hear some other people's opinions besides just yours and mine though :-) Also, this kind of thing must be very well documented in the code, e.g., at the points in the code that are calling await(). Otherwise, people changing the code later on could inadvertently add race conditions, etc. based on assumptions that are obsolete. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 15:13:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00366 for freebsd-current-outgoing; Sat, 19 Dec 1998 15:13:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from acetylene.vapornet.net (acetylene.vapornet.net [209.100.218.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00159 for ; Sat, 19 Dec 1998 15:13:28 -0800 (PST) (envelope-from john@vapornet.net) Received: from datapit.home.vapornet.net (vapornet.xnet.com. [205.243.141.107]) by acetylene.vapornet.net (8.9.1/8.9.1/VaporServer 1.4) with ESMTP id RAA19935 for ; Sat, 19 Dec 1998 17:13:12 -0600 (CST) (envelope from: john@vapornet.net) Received: from habanero.chili-pepper.net (habanero.chili-pepper.net [192.168.0.11]) by datapit.home.vapornet.net (8.9.1/8.9.1/VaporServer v1.3.1) with ESMTP id RAA62619 for ; Sat, 19 Dec 1998 17:13:23 -0600 (CST) (envelope from: john@vapornet.net) Received: (from john@localhost) by habanero.chili-pepper.net (8.9.1/8.9.1/VaporClient v3.1) id RAA28287; Sat, 19 Dec 1998 17:12:58 -0600 (CST) (envelope from: john@vapornet.net) From: John Preisler MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 19 Dec 1998 17:12:58 -0600 (CST) To: freebsd-current@FreeBSD.ORG Subject: Re: massive compilation breakage in user space X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13948.12852.143790.888545@habanero.chili-pepper.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG less the offending file and see if you dont have a bunch of ^@^@^@^@^@^@^@ in there. Im finding these little boogers creeping into my source here and there. -j To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 15:14:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00500 for freebsd-current-outgoing; Sat, 19 Dec 1998 15:14:49 -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 PAA00493 for ; Sat, 19 Dec 1998 15:14:41 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id SAA11196; Sat, 19 Dec 1998 18:14:23 -0500 (EST) (envelope-from wollman) Date: Sat, 19 Dec 1998 18:14:23 -0500 (EST) From: Garrett Wollman Message-Id: <199812192314.SAA11196@khavrinen.lcs.mit.edu> To: Archie Cobbs Cc: dillon@apollo.backplane.com (Matthew Dillon), freebsd-current@FreeBSD.ORG, jkh@zippy.cdrom.com, julian@whistle.com, luoqi@watermarkgroup.com Subject: Re: asleep()/await(), M_AWAIT, etc... In-Reply-To: <199812192303.PAA03836@bubba.whistle.com> References: <199812192111.NAA20772@apollo.backplane.com> <199812192303.PAA03836@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Also, this kind of thing must be very well documented in the code, > e.g., at the points in the code that are calling await(). > Otherwise, people changing the code later on could inadvertently > add race conditions, etc. based on assumptions that are obsolete. While we're talking about frobbing tsleep and friends, I'd really like to see an implementation of thread-assist. This should be a fairly easy hack: When tsleep is called, if a process flag is set, automatically rfork() the process. Put the running fork on the sleep queue, and return into the new process with an error indication and ETHREADBLOCKED. What the thread kernel would then be expected to do is to invoke the scheduler to find a new thread to run, and set a flag on the old process indicating that it should be destroyed (and its context moved to another process) when the system call does return. This would require one additional system call. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 16:19:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09120 for freebsd-current-outgoing; Sat, 19 Dec 1998 16:19:00 -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 QAA09087; Sat, 19 Dec 1998 16:18:12 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA15897; Sat, 19 Dec 1998 16:13:27 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdH15895; Sun Dec 20 00:13:21 1998 Date: Sat, 19 Dec 1998 16:13:18 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG cc: core@FreeBSD.ORG Subject: Appologies about commit screwup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was trying SO HARD to get it right that I stuffed it in the other direction.. In the last moment after testing, I reapplied a patch to a file because I had accidentally dropped editor cruft into the patched version. I was tired and in a hurry (I was late for an appointment) and stupidly used the -D option for patch. This inserted cpp condidionals into the file where they didn't work. The reason I decided to add the -D argument is probably due to lack of sleep because I wanted to have the code be the same after the patch if teh conditional is not defined on. For complete stupidity, that goes pretty far as an example.. and then to make matters worse, I recompiled the wrong kernel to test it and got the one that didn't include the file in question. remember kids, recompile LINT, not GENERICX!!!! SOS's fix is correct and reflects the file in my original test tree almost down to the added comments on the #endif lines All I can say is "I screwed up and deserve the pointy stick" pointy hat optional.. lessons "Don't commit when in a hurry to leave" "If you fix a screwup, restart all your testing from the beginning rather than try 'shortcut' it" "Don't commit when you are to tired to think straight" "Don't trust patch -D.. always inspect the results" Considering how much I didn't want to screw up this one it's really quite amazing how much it was screwed up. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 17:03:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13793 for freebsd-current-outgoing; Sat, 19 Dec 1998 17:03:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ratz.ficnet.net (ratz.ficnet.net [202.145.136.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13788 for ; Sat, 19 Dec 1998 17:03:53 -0800 (PST) (envelope-from donnylee@usa.net) Received: from usa.net (as6po11.ht.ficnet.net.tw [202.145.175.139]) by ratz.ficnet.net (8.9.1/8.9.1) with ESMTP id JAA25791 for ; Sun, 20 Dec 1998 09:03:39 +0800 (CST) Message-ID: <367C4E4A.BBC5D9DC@usa.net> Date: Sun, 20 Dec 1998 09:09:30 +0800 From: Donny Lee X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: FreeBSD mailing lists References: <199812192111.NAA20772@apollo.backplane.com> <199812192303.PAA03836@bubba.whistle.com> <199812192314.SAA11196@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Subject: Re: asleep()/await(), M_AWAIT, etc... > Date: Sat, 19 Dec 1998 18:14:23 -0500 (EST) > From: Garrett Wollman > To: Archie Cobbs > CC: dillon@apollo.backplane.com (Matthew Dillon), > freebsd-current@FreeBSD.ORG, > jkh@zippy.cdrom.com, > julian@whistle.com, > luoqi@watermarkgroup.com Pardon, do we have to keep replaying messages to so many mainling list members? Then what are those mailing lists for? -- // Donny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 17:46:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16996 for freebsd-current-outgoing; Sat, 19 Dec 1998 17:46:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16990; Sat, 19 Dec 1998 17:46:02 -0800 (PST) (envelope-from jmb) Date: Sat, 19 Dec 1998 17:46:02 -0800 (PST) Message-Id: <199812200146.RAA16990@hub.freebsd.org> From: "Jonathan M. Bresler" To: current Subject: visiting the bar area Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG as part of my new job, i will be in the san jose, sunnyvale, santa clara area from sunday night to tuesday midday. anyone want to get together on monday night? my email access will be sporadic at best ;( i will be staying at EMBASSY SUITES EMBASSY SUITES 901 CALAVERAS BLVD MILPITAS CA 95035 PHONE-408 942-0400 FAX-408 262-8604 jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 18:13:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19707 for freebsd-current-outgoing; Sat, 19 Dec 1998 18:13:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.monmouth.com (shell.monmouth.com [205.231.236.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19702 for ; Sat, 19 Dec 1998 18:13:05 -0800 (PST) (envelope-from support@lomag.net) Received: from lomag.net (bg-tc-ppp103.monmouth.com [209.191.60.104]) by shell.monmouth.com (8.9.0/8.9.0) with ESMTP id VAA26913 for ; Sat, 19 Dec 1998 21:11:40 -0500 (EST) Message-ID: <367C5D10.E1D6F5A5@lomag.net> Date: Sat, 19 Dec 1998 21:12:32 -0500 From: Lomag Organization: Lomag Internet Services X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: identd problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey guys, I run 3.0-current and my identd just suddently died, when i try to restart it (identd -w -t120) i get this error in my /var/log/messages: Dec 19 17:35:56 shell inetd[20730]: ident/tcp: bind: Address already in use Then i tried killall -1 inetd, that doesn't work either. I know the easy solution is to reboot, but I can not do that. If anyone knows please let me know asap. Also if anyone knows when 3.0-stable should be ready, please let me know. My 3.0-current system can't go 10 days without having problems with ftp, inetd, etc.. Regards, support@lomag.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 18:46:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23130 for freebsd-current-outgoing; Sat, 19 Dec 1998 18:46:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23125 for ; Sat, 19 Dec 1998 18:46:50 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id VAA16667 for ; Sat, 19 Dec 1998 21:50:24 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sat, 19 Dec 1998 21:50:24 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: freebsd-current@FreeBSD.ORG Subject: Someone posted a fix for NFS, but not commited In-Reply-To: <199812200157.RAA04126@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 the file: src/sys/kern/vfs_subr.c line: 582 has a bug which can cause nfs 'intr' mounts to hang the machine: while (vp->v_numoutput) { vp->v_flag |= VBWAIT; tsleep((caddr_t)&vp->v_numoutput, slpflag | (PRIBIO + 1), "vinvlbuf", slptimeo); } it's been explained to me that if a signal interupts the tsleep it will cause an infinite loop. the fix i _think_ was: while (vp->v_numoutput) { vp->v_flag |= VBWAIT; error = tsleep((caddr_t)&vp->v_numoutput, slpflag | (PRIBIO + 1), "vinvlbuf", slptimeo); if(error){ splx(s); return(error); } } unfortunatly i accidentally deleted the mail with the fix in it and cvsup checked out the file clobbering my local copy. can someone take a look at getting this commited? it solved the hangs i was having and doesn't seem to adversly affect semantics. i have no clue where this patch went i searched the lists and had no luck finding it. thanks, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 19:12:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24859 for freebsd-current-outgoing; Sat, 19 Dec 1998 19:12:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24850 for ; Sat, 19 Dec 1998 19:12:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id TAA20549; Sat, 19 Dec 1998 19:12:04 -0800 (PST) To: Lomag cc: freebsd-current@FreeBSD.ORG Subject: Re: identd problems In-reply-to: Your message of "Sat, 19 Dec 1998 21:12:32 EST." <367C5D10.E1D6F5A5@lomag.net> Date: Sat, 19 Dec 1998 19:12:03 -0800 Message-ID: <20546.914123523@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hey guys, I run 3.0-current and my identd just suddently > died, when i try to restart it (identd -w -t120) i get this > error in my /var/log/messages: You don't run ident by hand - it's run by inetd. See the example. You're just very very confused. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 19:12:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24860 for freebsd-current-outgoing; Sat, 19 Dec 1998 19:12:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gaylord.async.vt.edu (gaylord.async.vt.edu [128.173.18.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24848 for ; Sat, 19 Dec 1998 19:12:11 -0800 (PST) (envelope-from gaylord@gaylord.async.vt.edu) Received: (from gaylord@localhost) by gaylord.async.vt.edu (8.9.1/8.8.5) id WAA00710; Sat, 19 Dec 1998 22:11:24 -0500 (EST) From: Clark Gaylord Message-Id: <199812200311.WAA00710@gaylord.async.vt.edu> Subject: Re: an addition to top(1) In-Reply-To: from Andy Farkas at "Dec 19, 98 08:58:04 pm" To: andyf@speednet.com.au (Andy Farkas) Date: Sat, 19 Dec 1998 22:11:24 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andy Farkas said: > I've always thought that top(1) should display the system > uptime. Here's a patch. The code was cut straight out of > /usr/src/usr.bin/w/w.c I haven't tested the patch itself yet, but knee-jerk reaction is to nominate the feature for inclusion. Clark -- Clark K. Gaylord Blacksburg, Virginia USA cgaylord@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 19:19:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25274 for freebsd-current-outgoing; Sat, 19 Dec 1998 19:19:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25269 for ; Sat, 19 Dec 1998 19:19:02 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id TAA26243; Sat, 19 Dec 1998 19:27:02 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812200327.TAA26243@troutmask.apl.washington.edu> Subject: Re: FreeBSD mailing lists In-Reply-To: <367C4E4A.BBC5D9DC@usa.net> from Donny Lee at "Dec 20, 1998 9: 9:30 am" To: donnylee@usa.net (Donny Lee) Date: Sat, 19 Dec 1998 19:27:02 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Donny Lee: > >Subject: Re: asleep()/await(), M_AWAIT, etc... > > Date: Sat, 19 Dec 1998 18:14:23 -0500 (EST) > > From: Garrett Wollman > > To: Archie Cobbs > > CC: dillon@apollo.backplane.com (Matthew Dillon), > > freebsd-current@FreeBSD.ORG, > > jkh@zippy.cdrom.com, > > julian@whistle.com, > > luoqi@watermarkgroup.com > > Pardon, do we have to keep replaying messages to so many > mainling list members? It is often the fastest way to communicate when a hot topic or argument breaks loose. > Then what are those mailing lists for? Install procmail. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 19:42:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27122 for freebsd-current-outgoing; Sat, 19 Dec 1998 19:42:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27117 for ; Sat, 19 Dec 1998 19:42:23 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id OAA17015; Sun, 20 Dec 1998 14:42:08 +1100 (EST) Date: Sun, 20 Dec 1998 14:42:07 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: "David O'Brien" cc: freebsd-current@FreeBSD.ORG Subject: Re: an addition to top(1) In-Reply-To: <19981219120930.A24908@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I've always thought that top(1) should display the system > > uptime. Here's a patch. The code was cut straight out of > > /usr/src/usr.bin/w/w.c > > Cute. Committed. > > Um, it'll break scripts that "top -b | head -1 | awk '{print $9}'" Although why you'd do something like that is beyond me :-) -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 20:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01189 for freebsd-current-outgoing; Sat, 19 Dec 1998 20:26:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pobox.com (lafra-84.mdm.mkt.execpc.com [169.207.80.212]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA01184 for ; Sat, 19 Dec 1998 20:26:04 -0800 (PST) (envelope-from hamilton@pobox.com) Message-Id: <199812200426.UAA01184@hub.freebsd.org> Received: (qmail 27572 invoked from network); 19 Dec 1998 22:27:11 -0600 Received: from localhost (HELO pobox.com) (127.0.0.1) by localhost with SMTP; 19 Dec 1998 22:27:11 -0600 To: "Jordan K. Hubbard" cc: Lomag , freebsd-current@FreeBSD.ORG Subject: Re: identd problems In-reply-to: Your message of "Sat, 19 Dec 1998 19:12:03 PST." <20546.914123523@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 19 Dec 1998 22:27:11 -0600 From: Jon Hamilton Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20546.914123523@zippy.cdrom.com>, "Jordan K. Hubbard" wrote: } > Hey guys, I run 3.0-current and my identd just suddently } > died, when i try to restart it (identd -w -t120) i get this } > error in my /var/log/messages: } } You don't run ident by hand - it's run by inetd. See the example. } You're just very very confused. Well, you _can_ run identd by hand, but it's not recommended. Having said that, using -w and -t would not be the correct way to do so, so I suppose you're right and he's simply confused :) -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 20:26:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01490 for freebsd-current-outgoing; Sat, 19 Dec 1998 20:26:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01485 for ; Sat, 19 Dec 1998 20:26:35 -0800 (PST) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id WAA13510; Sat, 19 Dec 1998 22:26:32 -0600 (CST) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id WAA08768; Sat, 19 Dec 1998 22:22:43 -0600 (CST) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13948.31634.827700.625029@zuhause.zuhause.mn.org> Date: Sat, 19 Dec 1998 22:22:42 -0600 (CST) To: Donny Lee Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD mailing lists In-Reply-To: <367C4E4A.BBC5D9DC@usa.net> References: <199812192111.NAA20772@apollo.backplane.com> <199812192303.PAA03836@bubba.whistle.com> <199812192314.SAA11196@khavrinen.lcs.mit.edu> <367C4E4A.BBC5D9DC@usa.net> X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donny Lee writes: > >Subject: Re: asleep()/await(), M_AWAIT, etc... > > Date: Sat, 19 Dec 1998 18:14:23 -0500 (EST) > > From: Garrett Wollman > > To: Archie Cobbs > > CC: dillon@apollo.backplane.com (Matthew Dillon), > > freebsd-current@FreeBSD.ORG, > > jkh@zippy.cdrom.com, > > julian@whistle.com, > > luoqi@watermarkgroup.com > > Pardon, do we have to keep replaying messages to so many > mainling list members? > > Then what are those mailing lists for? I, for one, only read mailing lists on a as-time-permits basis, and anything sent to the mailing list goes to a folder. Anything cc:'d to me, gets read much sooner. I suspect this is true for many people. Still, most of those people on the list probably don't need to have direct replies, unless they're debating something that needs immediate attention. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 20:29:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01681 for freebsd-current-outgoing; Sat, 19 Dec 1998 20:29:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA01676 for ; Sat, 19 Dec 1998 20:29:09 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id WAA05413; Sat, 19 Dec 1998 22:29:07 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.8.8/8.7.3) id WAA06325; Sat, 19 Dec 1998 22:29:06 -0600 (CST) Message-ID: <19981219222906.A6315@cs.rice.edu> Date: Sat, 19 Dec 1998 22:29:06 -0600 From: Alan Cox To: current@FreeBSD.ORG Cc: lcremean@tidalwave.net Subject: Re: cvs commit: src/sys/pci pcisupport.c Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've been poking around ide_pci.c, and it seems that not having explicit > Acer Aladdin support in there not only screws with UDMA support, it also > keeps the second channel from working correctly. This chipset fsr has its > BMISTA_SIMPLEX flag set, and ide_pci.c is seeing this and assuming (wrongly) > that the Aladdin IDE controller is single-channel. (Yes, it says it's just > disabling DMA, but the code actually disables _everything_ on the second > channel since wd.c uses ide_pci.c to probe for devices. It'd probably be a > good idea to not check for SIMPLEX anymore.) Try following patch Index: /usr/src/sys/i386/isa/wd.c =================================================================== RCS file: /home/ncvs/src/sys/i386/isa/wd.c,v retrieving revision 1.181 diff -c -r1.181 wd.c *** wd.c 1998/12/15 09:16:57 1.181 --- wd.c 1998/12/16 08:01:53 *************** *** 313,320 **** interface = du->dk_ctrlr / 2; du->dk_interface = interface; #if !defined(DISABLE_PCI_IDE) && (NPCI > 0) ! if (wddma[interface].wdd_candma) { ! du->dk_dmacookie = wddma[interface].wdd_candma(dvp->id_iobase, du->dk_ctrlr); du->dk_port = dvp->id_iobase; du->dk_altport = wddma[interface].wdd_altiobase(du->dk_dmacookie); } else { --- 313,321 ---- interface = du->dk_ctrlr / 2; du->dk_interface = interface; #if !defined(DISABLE_PCI_IDE) && (NPCI > 0) ! if ((wddma[interface].wdd_candma != NULL) && ! ((du->dk_dmacookie = wddma[interface].wdd_candma(dvp->id_iobase, ! du->dk_ctrlr)) != NULL)) { du->dk_port = dvp->id_iobase; du->dk_altport = wddma[interface].wdd_altiobase(du->dk_dmacookie); } else { DMA will still be limited to devices on wdc0, but at least the devices attached to wdc1 will be detected (and accessible). Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 20:40:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02493 for freebsd-current-outgoing; Sat, 19 Dec 1998 20:40:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02488 for ; Sat, 19 Dec 1998 20:40:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id UAA06679; Sat, 19 Dec 1998 20:40:13 -0800 (PST) (envelope-from obrien) Message-ID: <19981219204013.B6508@nuxi.com> Date: Sat, 19 Dec 1998 20:40:13 -0800 From: "David O'Brien" To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: 'make clean' in /usr/src does not cleanup .o's or shared libs ? Reply-To: obrien@NUXI.com References: <199812150906.KAA01672@wurzelausix> <199812150915.BAA52668@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812150915.BAA52668@apollo.backplane.com>; from Matthew Dillon on Tue, Dec 15, 1998 at 01:15:17AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The object files, .depend files, binaries, synthesized source files, > and other junk residing in /usr/src are typically left-overs from > manual builds of various subprograms. i.e. if I need to > recompile/reinstall, say, inetd I usually do: > > cd /usr/src/usr.sbin/inetd make obj <--- the other piece you are forgetting ;-) > make > make install > make clean <----- the piece I often forget to do -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 21:25:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05580 for freebsd-current-outgoing; Sat, 19 Dec 1998 21:25:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05575 for ; Sat, 19 Dec 1998 21:25:24 -0800 (PST) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id XAA17291 for freebsd-current@freebsd.org; Sat, 19 Dec 1998 23:25:22 -0600 (CST) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id XAA09021; Sat, 19 Dec 1998 23:22:30 -0600 (CST) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13948.35208.923734.90525@zuhause.zuhause.mn.org> Date: Sat, 19 Dec 1998 23:22:16 -0600 (CST) To: freebsd-current@FreeBSD.ORG Subject: GDBM_File and base perl X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way in the base perl build to recognize that gdbm has been installed in /usr/local and include it when building perl? Since it's part of the base perl distribution, there's no tidy way to add it after the fact with something from CPAN. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 19 23:58:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14899 for freebsd-current-outgoing; Sat, 19 Dec 1998 23:58:45 -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 XAA14893; Sat, 19 Dec 1998 23:58:44 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA22923; Sat, 19 Dec 1998 23:49:00 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdq22920; Sun Dec 20 07:48:52 1998 Date: Sat, 19 Dec 1998 23:48:49 -0800 (PST) From: Julian Elischer To: lcremean@tidalwave.net cc: Howard , current@FreeBSD.ORG Subject: Re: cvs commit: src/sys/pci pcisupport.c In-Reply-To: <19981219134118.A311@tidalwave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whistle has some support for Cyrix 5530 UltraDMA support that will come in when cleaned up. Unfortunatly the 5530 UDMA engine has some serious bugs. some of which can't be worked around from ide_pci.c alone.. julian On Sat, 19 Dec 1998, Lee Cremeans wrote: > On Sat, Dec 19, 1998 at 08:05:20AM -0800, Howard wrote: > > foxfair 1998/12/19 08:05:20 PST > > > > Modified files: > > sys/pci pcisupport.c > > Log: > > Add more non-Intel family ((new)) chipset, just like VIA technology MVP3 > > AcerLabs Aladdin-V. It makes the PCI probing work when system booting. I > > will try to merge some additional funtion(i.e. wdc1 problem cause tons of > > PR appear :<) ASAP if I could. > > I've been poking around ide_pci.c, and it seems that not having explicit > Acer Aladdin support in there not only screws with UDMA support, it also > keeps the second channel from working correctly. This chipset fsr has its > BMISTA_SIMPLEX flag set, and ide_pci.c is seeing this and assuming (wrongly) > that the Aladdin IDE controller is single-channel. (Yes, it says it's just > disabling DMA, but the code actually disables _everything_ on the second > channel since wd.c uses ide_pci.c to probe for devices. It'd probably be a > good idea to not check for SIMPLEX anymore.) > > Also, I'm looking at how to set up the Aladdin UDMA regsters, and I want to > do it in a similar way to the PIIX4, but the different settings and such > confuse me a bit. I'll keep reading. > > -- > +--------------------------------------------------------------------+ > | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| > | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | > > > 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