From owner-freebsd-current Sun Jul 6 01:26:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA14508 for current-outgoing; Sun, 6 Jul 1997 01:26:07 -0700 (PDT) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA14501 for ; Sun, 6 Jul 1997 01:26:02 -0700 (PDT) Received: from labs.usn.blaze.net.au (local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.5/8.8.5) with ESMTP id RAA01362; Sun, 6 Jul 1997 17:37:01 +1000 (EST) Message-Id: <199707060737.RAA01362@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: Terry Lambert cc: ache@nagual.pp.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=), wosch@apfel.de, current@FreeBSD.ORG Subject: Re: long usernames in top In-reply-to: Your message of "Sat, 05 Jul 1997 11:39:19 MST." <199707051839.LAA14837@phaeton.artisoft.com> X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Jul 1997 17:36:58 +1000 From: David Nugent Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Better variant will be to calculate maxnamelen at runtime through > > displayed names only, not through all names from /etc/passwd > > Yes. This is what I did for "ps" and "w". The annoying thing > about top is that the name data is potentially variant on each > refresh. Plus the thing is being actively maintained by an agency > other than FreeBSD, so unless the job was done completely, it's > likely that it would become a FreeBSD-only maintenance nightmare. Nightmare? Terry, this is why we use cvs and vendor branches. In any case, FreeBSD is not the only OS with support for >8 length usernames. Regards, David -- David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Sun Jul 6 09:44:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA28121 for current-outgoing; Sun, 6 Jul 1997 09:44:26 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28116 for ; Sun, 6 Jul 1997 09:44:22 -0700 (PDT) Received: from panke.panke.de (anonymous221.ppp.cs.tu-berlin.de [130.149.17.221]) by mail.cs.tu-berlin.de (8.8.6/8.8.6) with ESMTP id SAA04902; Sun, 6 Jul 1997 18:28:34 +0200 (MET DST) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id SAA01012; Sun, 6 Jul 1997 18:14:49 +0200 (MET DST) Date: Sun, 6 Jul 1997 18:14:49 +0200 (MET DST) Message-Id: <199707061614.SAA01012@panke.panke.de> From: Wolfram Schneider To: David Nugent Cc: Terry Lambert , ache@nagual.pp.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=), current@FreeBSD.ORG Subject: Re: long usernames in top In-Reply-To: <199707060737.RAA01362@labs.usn.blaze.net.au> References: <199707051839.LAA14837@phaeton.artisoft.com> <199707060737.RAA01362@labs.usn.blaze.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Yes. This is what I did for "ps" and "w". The annoying thing >> about top is that the name data is potentially variant on each >> refresh. Plus the thing is being actively maintained by an agency >> other than FreeBSD, so unless the job was done completely, it's >> likely that it would become a FreeBSD-only maintenance nightmare. > >Nightmare? Terry, this is why we use cvs and vendor branches. CVS is the personification of a nightmare. Especially vendor branches sucks in CVS. We changed the structure of the source tree and many tools are not up to date due the broken CVS. -- Wolfram Schneider http://www.apfel.de/~wosch/ From owner-freebsd-current Sun Jul 6 09:52:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA28437 for current-outgoing; Sun, 6 Jul 1997 09:52:18 -0700 (PDT) Received: from labs.usn.blaze.net.au (labs.usn.blaze.net.au [203.17.53.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA28430 for ; Sun, 6 Jul 1997 09:52:14 -0700 (PDT) Received: from labs.usn.blaze.net.au (local [127.0.0.1]) by labs.usn.blaze.net.au (8.8.5/8.8.5) with ESMTP id CAA01145; Mon, 7 Jul 1997 02:51:03 +1000 (EST) Message-Id: <199707061651.CAA01145@labs.usn.blaze.net.au> X-Mailer: exmh version 2.0gamma 1/27/96 To: Wolfram Schneider cc: Terry Lambert , ache@nagual.pp.ru (=?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?=), current@FreeBSD.ORG Subject: Re: long usernames in top In-reply-to: Your message of "Sun, 06 Jul 1997 18:14:49 +0200." <199707061614.SAA01012@panke.panke.de> X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Jul 1997 02:51:02 +1000 From: David Nugent Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> likely that it would become a FreeBSD-only maintenance nightmare. > > > >Nightmare? Terry, this is why we use cvs and vendor branches. > > CVS is the personification of a nightmare. Yes, but a *different* nightmare, or a nightmare in different ways. Standard vendor branches do, in fact, work fine as desiigned. That CVS doesn't deal (at all) with moving things around is a different problem. -- David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ From owner-freebsd-current Sun Jul 6 10:58:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA29955 for current-outgoing; Sun, 6 Jul 1997 10:58:44 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA29950 for ; Sun, 6 Jul 1997 10:58:40 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA16050; Sun, 6 Jul 1997 10:53:18 -0700 From: Terry Lambert Message-Id: <199707061753.KAA16050@phaeton.artisoft.com> Subject: Re: long usernames in top To: davidn@labs.usn.blaze.net.au (David Nugent) Date: Sun, 6 Jul 1997 10:53:18 -0700 (MST) Cc: terry@lambert.org, ache@nagual.pp.ru, wosch@apfel.de, current@FreeBSD.ORG In-Reply-To: <199707060737.RAA01362@labs.usn.blaze.net.au> from "David Nugent" at Jul 6, 97 05:36:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ ... top ... ] > > Plus the thing is being actively maintained by an agency > > other than FreeBSD, so unless the job was done completely, it's > > likely that it would become a FreeBSD-only maintenance nightmare. > > Nightmare? Terry, this is why we use cvs and vendor branches. better to contribute the code back to the top maintainer, and not involve FreeBSD directly at all. > In any case, FreeBSD is not the only OS with support for >8 length > usernames. And this is why. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Sun Jul 6 17:00:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA12452 for current-outgoing; Sun, 6 Jul 1997 17:00:14 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA12446 for ; Sun, 6 Jul 1997 17:00:12 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA03444 for ; Sun, 6 Jul 1997 16:55:19 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd003440; Sun Jul 6 23:55:18 1997 Date: Sun, 6 Jul 1997 16:53:49 -0700 (PDT) From: Julian Elischer To: current@freebsd.org Subject: Multicast code broken? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I haven't looked at it fully but it appears that the muticast changes have broken many things.. for example the multicast test program mtest(8) cannot even add a multicast address any more.. I know Garret is off on holiday in Canada, but I wish he'd tested these things first. (it's a 1 line fix) the fact that this simple test program was not even checked doesn't give me a good feeling about the rest of the changes. The Appletalk code has been totally broken by this. I'm struggling my way through it however.. Has anyone seen the multicast code working with the new DE driver? I don't seemto be receiving multicasts on my test setup for the netatalk code. For the record, I notice that garret's new changes (while I agree with them), will once again break every stack in the system except those for IP. This is getting very annoying for those of us maintaining a stack. From owner-freebsd-current Mon Jul 7 00:04:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA29162 for current-outgoing; Mon, 7 Jul 1997 00:04:15 -0700 (PDT) Received: from critter.dk.tfs.com ([140.145.230.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA29156 for ; Mon, 7 Jul 1997 00:04:11 -0700 (PDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.6/8.8.5) with ESMTP id IAA00503; Mon, 7 Jul 1997 08:11:11 +0200 (CEST) To: Julian Elischer cc: current@FreeBSD.org From: Poul-Henning Kamp Subject: Re: Multicast code broken? In-reply-to: Your message of "Sun, 06 Jul 1997 16:53:49 PDT." Date: Mon, 07 Jul 1997 08:11:11 +0200 Message-ID: <501.868255871@critter.dk.tfs.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message , Juli an Elischer writes: >For the record, I notice that garret's new changes (while I agree with >them), will once again break every stack in the system except >those for IP. > >This is getting very annoying for those of us maintaining a stack. It was generally agreed that the 3.0 release was the time to get things like this done, so in a sense this is to be expected, but I agree that the completeness in this case leaves a little to be desired... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-current Mon Jul 7 11:21:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA28483 for current-outgoing; Mon, 7 Jul 1997 11:21:03 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA28471 for ; Mon, 7 Jul 1997 11:20:56 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA24173; Mon, 7 Jul 1997 11:19:47 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd024169; Mon Jul 7 18:19:39 1997 Message-ID: <33C132E1.59E2B600@whistle.com> Date: Mon, 07 Jul 1997 11:18:09 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: netatalk@umich.edu, current@freebsd.org Subject: Patches for netatalk and FreeBSD-current (3.0) Content-Type: multipart/mixed; boundary="------------FF6D5DF3F54BC7E1CFBAE39" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------FF6D5DF3F54BC7E1CFBAE39 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Here are patches for making netatalk work with the latest kernel in FreeBSD. The multicast support has changed slightly and this required that the appletalk code supply it's multicast requests in a slightly more pedantic manner. for a more complete fix the changes should be bracketed in: #if defined(__FreeBSD__) && ( __FreeBSD >= 3 ) ..fix code #endif however I'm not sure if this fix might work just as well for other systems by default. this is for 1.4b2 under FreeBSD 3.0-current as of July 6 julian --------------FF6D5DF3F54BC7E1CFBAE39 Content-Type: text/plain; charset=us-ascii; name="xx" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="xx" diff -c netatalk-dist/etc/atalkd/main.c netatalk-dist.new/etc/atalkd/main.c *** netatalk-dist/etc/atalkd/main.c Mon Oct 21 15:45:03 1996 --- netatalk-dist.new/etc/atalkd/main.c Mon Jul 7 10:51:22 1997 *************** *** 18,23 **** --- 18,24 ---- #include #include #include + #include #include #include *************** *** 1149,1162 **** bootaddr( ciface ); } } else { /* configure multicast for this interface */ ! bzero( &sa, sizeof( struct sockaddr )); ! bcopy( ethermulti, sa.sa_data, sizeof( ethermulti )); ! if ( ifconfig( iface->i_name, SIOCADDMULTI, &sa )) { syslog( LOG_ERR, "addmulti: %m" ); exit( 1 ); } - zip_getnetinfo( iface ); } } --- 1150,1170 ---- bootaddr( ciface ); } } else { + struct sockaddr_dl *sdl = (struct sockaddr_dl *)&sa; /* configure multicast for this interface */ ! bzero( sdl, sizeof( struct sockaddr )); ! sdl->sdl_family = AF_LINK; ! sdl->sdl_nlen = 0 /* strlen(iface->i_name)*/; ! /*strncpy(sdl->sdl_data, iface->i_name, sdl->sdl_nlen);*/ ! bcopy( ethermulti, LLADDR(sdl), sizeof( ethermulti )); ! sdl->sdl_alen = sizeof( ethermulti ); ! sdl->sdl_len = sizeof(*sdl); ! /* (sdl->sdl_data + sdl->sdl_alen + sdl->sdl_nlen) ! - (char *)sdl; */ ! if ( ifconfig( iface->i_name, SIOCADDMULTI, sdl )) { syslog( LOG_ERR, "addmulti: %m" ); exit( 1 ); } zip_getnetinfo( iface ); } } diff -c netatalk-dist/etc/atalkd/nbp.c netatalk-dist.new/etc/atalkd/nbp.c *** netatalk-dist/etc/atalkd/nbp.c Sat Oct 5 08:17:53 1996 --- netatalk-dist.new/etc/atalkd/nbp.c Mon Jul 7 11:07:01 1997 *************** *** 7,13 **** --- 7,15 ---- #include #include #include + #include #include + #include #include #include #include *************** *** 185,190 **** --- 187,201 ---- for ( l = iface->i_rt->rt_zt; l; l = l->l_next ) { if ( zt == (struct ziptab *)l->l_data ) { /* add multicast */ + struct sockaddr_dl *sdl = (struct sockaddr_dl *)&sa; + sdl->sdl_family = AF_LINK; + sdl->sdl_nlen = 0; + bcopy( zt->zt_bcast, sdl->sdl_data, sizeof(ethermulti)); + sdl->sdl_alen = sizeof(ethermulti); + sdl->sdl_len = sizeof (*sdl); + /* (sdl->sdl_data + + sdl->sdl_alen + sdl->sdl_nlen) + - (char *)sdl; */ if ( ifconfig( iface->i_name, SIOCADDMULTI, &sa )) { syslog( LOG_ERR, "addmulti: %m" ); exit( 1 ); diff -c netatalk-dist/etc/atalkd/rtmp.c netatalk-dist.new/etc/atalkd/rtmp.c *** netatalk-dist/etc/atalkd/rtmp.c Wed Sep 18 12:05:18 1996 --- netatalk-dist.new/etc/atalkd/rtmp.c Thu Jun 5 17:48:55 1997 *************** *** 7,12 **** --- 7,13 ---- #include #include #include + #include #include #include #include --------------FF6D5DF3F54BC7E1CFBAE39-- From owner-freebsd-current Mon Jul 7 14:18:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA08928 for current-outgoing; Mon, 7 Jul 1997 14:18:10 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA08922 for ; Mon, 7 Jul 1997 14:18:07 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-38.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA29307 (5.67b/IDA-1.5 for ); Mon, 7 Jul 1997 23:18:04 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id XAA13736; Mon, 7 Jul 1997 23:17:59 +0200 (CEST) X-Face: " Date: Mon, 7 Jul 1997 23:17:59 +0200 From: Stefan Esser To: Janick Taillandier Cc: freebsd-current@FreeBSD.ORG Subject: Re: Problem with HP DAT References: <19970629090606.41531@fugue.noisy.ratp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <19970629090606.41531@fugue.noisy.ratp>; from Janick Taillandier on Sun, Jun 29, 1997 at 09:06:06AM +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 29, Janick Taillandier wrote: > Hello, > > I have just upgraded my system from a rather old 2.2 SNAP to 3.0 > CURRENT (I am using a SMP kernel on a Dell optiplex with 2 Pentium Pro). Hi! Sorry for the late reply ... There are no changes between 2.2 and -current, that I know of and that might account for the problem you are facing. I'm using a HP DAT (1533) myself for quite some time, and never had a problem to get it probed ... > Everything seems to be fine, but the DAT connected to and NCR card is > not recognized during the boot. Here is the relevant part of a > boot -v : > > > Jun 29 08:53:43 chaconne /kernel: ncr0: rev 0x02 int a irq 18 on pci1.10.0 > Jun 29 08:53:43 chaconne /kernel: ncr0: restart (scsi reset). > Jun 29 08:53:44 chaconne /kernel: BIOS values: dmode: 00, dcntl: a1, ctest3: 20 > Jun 29 08:53:44 chaconne /kernel: dmode: ce/00, dcntl: a1/a1, ctest3: 01/20 > Jun 29 08:53:44 chaconne /kernel: ncr0 scanning for targets 0..6 (V2 pl24 96/12/14) > Jun 29 08:53:44 chaconne /kernel: Choosing drivers for scbus configured at 1 > Jun 29 08:53:44 chaconne /kernel: ncr0: waiting for scsi devices to settle > Jun 29 08:53:44 chaconne /kernel: scbus1 at ncr0 bus 0 > Jun 29 08:53:44 chaconne /kernel: cd0 at scbus1 target 3 lun 0 > Jun 29 08:53:44 chaconne /kernel: cd0: type 5 removable SCSI 2 > Jun 29 08:53:44 chaconne /kernel: cd0: CD-ROM > Jun 29 08:53:44 chaconne /kernel: cd0: NCR quirks=0x2 > Jun 29 08:53:44 chaconne /kernel: > Jun 29 08:53:44 chaconne /kernel: cd0: 10.0 MB/s (100 ns, offset 8) > Jun 29 08:53:44 chaconne /kernel: can't get the size > Jun 29 08:53:44 chaconne /kernel: scbus1 target 4 lun 0: COMMAND FAILED (4 1) @f063bb10. > Jun 29 08:53:44 chaconne /kernel: scbus1 target 4 lun 0: phase change 2-3 6@0003ec58 resid=5. Hmmm, this looks like the DAT does reject the command it gets sent. I'm not sure why this happens, though. > I don't think the problem is with the DAT as it is working on > other machines. No, I don't think so, neither. And if it worked with 2.2, then there is even more reason to assume the drive is not broken. > Did I miss something ? Any idea of what is wrong ? Do you know how to compile a kernel with SCSI and NCR debug code included ? Could you please send verbose boot messages from a 2.2 kernel (in case you still got such a kernel), or at least the normal boot messages as stored into /var/log/messages ? Regards, STefan From owner-freebsd-current Mon Jul 7 17:10:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA16671 for current-outgoing; Mon, 7 Jul 1997 17:10:56 -0700 (PDT) Received: from sage.tamis.com (tamis.com [206.24.116.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16661 for ; Mon, 7 Jul 1997 17:10:46 -0700 (PDT) Received: (from daveh@localhost) by sage.tamis.com (8.8.5/8.6.12) id RAA02951; Mon, 7 Jul 1997 17:05:00 -0700 (PDT) Date: Mon, 7 Jul 1997 17:04:59 -0700 (PDT) From: David Holloway To: freebsd-current@FreeBSD.ORG Subject: lsdev In-Reply-To: <19970707231759.08309@mi.uni-koeln.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk what ever happened to lsdev? -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i mQBtAzNlZLYAAAEDAMgNdZzjQLVUlL2iYYC5LXU7hGjB+NB6BPL5OyFM7/iAhhIo Z/u6VCQ9I3ly8c9kYwDcKoFCwn2qmEOFjiCDHdeGoUShtUD3UASm9j0yVlpUrzpS 8i8Rz9Ug1R1YtC9oEQAFEbQfRGF2aWQgSG9sbG93YXk8ZGF2ZWhAdGFtaXMuY29t PokAdQMFEDNlZLYg1R1YtC9oEQEBRJQC/3B3/CUirR2zTi/jxkU8vA1UtCiZXH1x oaUrSpeH3YDbV7zIRNBoIIgtncPgySACdH8+ikLAegfkImcYYqSDtu+y1qslYIAL XzTX9Wk6zE1k0JEPMkkKu8uLhx3Lk7Uscw== =8hwm -----END PGP PUBLIC KEY BLOCK----- On Mon, 7 Jul 1997, Stefan Esser wrote: > On Jun 29, Janick Taillandier wrote: > > Hello, > > > > I have just upgraded my system from a rather old 2.2 SNAP to 3.0 > > CURRENT (I am using a SMP kernel on a Dell optiplex with 2 Pentium Pro). > > Hi! > > Sorry for the late reply ... > > There are no changes between 2.2 and -current, that I know > of and that might account for the problem you are facing. > > I'm using a HP DAT (1533) myself for quite some time, and > never had a problem to get it probed ... > > > Everything seems to be fine, but the DAT connected to and NCR card is > > not recognized during the boot. Here is the relevant part of a > > boot -v : > > > > > > Jun 29 08:53:43 chaconne /kernel: ncr0: rev 0x02 int a irq 18 on pci1.10.0 > > Jun 29 08:53:43 chaconne /kernel: ncr0: restart (scsi reset). > > Jun 29 08:53:44 chaconne /kernel: BIOS values: dmode: 00, dcntl: a1, ctest3: 20 > > Jun 29 08:53:44 chaconne /kernel: dmode: ce/00, dcntl: a1/a1, ctest3: 01/20 > > Jun 29 08:53:44 chaconne /kernel: ncr0 scanning for targets 0..6 (V2 pl24 96/12/14) > > Jun 29 08:53:44 chaconne /kernel: Choosing drivers for scbus configured at 1 > > Jun 29 08:53:44 chaconne /kernel: ncr0: waiting for scsi devices to settle > > Jun 29 08:53:44 chaconne /kernel: scbus1 at ncr0 bus 0 > > Jun 29 08:53:44 chaconne /kernel: cd0 at scbus1 target 3 lun 0 > > Jun 29 08:53:44 chaconne /kernel: cd0: type 5 removable SCSI 2 > > Jun 29 08:53:44 chaconne /kernel: cd0: CD-ROM > > Jun 29 08:53:44 chaconne /kernel: cd0: NCR quirks=0x2 > > Jun 29 08:53:44 chaconne /kernel: > > Jun 29 08:53:44 chaconne /kernel: cd0: 10.0 MB/s (100 ns, offset 8) > > Jun 29 08:53:44 chaconne /kernel: can't get the size > > Jun 29 08:53:44 chaconne /kernel: scbus1 target 4 lun 0: COMMAND FAILED (4 1) @f063bb10. > > Jun 29 08:53:44 chaconne /kernel: scbus1 target 4 lun 0: phase change 2-3 6@0003ec58 resid=5. > > Hmmm, this looks like the DAT does reject the command it gets > sent. I'm not sure why this happens, though. > > > I don't think the problem is with the DAT as it is working on > > other machines. > > No, I don't think so, neither. And if it worked with 2.2, then > there is even more reason to assume the drive is not broken. > > > Did I miss something ? Any idea of what is wrong ? > > Do you know how to compile a kernel with SCSI and NCR debug code > included ? > > Could you please send verbose boot messages from a 2.2 kernel > (in case you still got such a kernel), or at least the normal > boot messages as stored into /var/log/messages ? > > Regards, STefan > From owner-freebsd-current Mon Jul 7 18:16:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA19753 for current-outgoing; Mon, 7 Jul 1997 18:16:18 -0700 (PDT) Received: from pressroom.com (pressroom.com [198.69.131.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA19744 for ; Mon, 7 Jul 1997 18:16:14 -0700 (PDT) Message-ID: <33C192EB.3BE2D75A@pressroom.com> Date: Mon, 07 Jul 1997 21:07:56 -0400 From: May Chang Organization: PressRoom Online Services X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: subscribe X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe From owner-freebsd-current Mon Jul 7 23:27:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA00575 for current-outgoing; Mon, 7 Jul 1997 23:27:57 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA00538 for ; Mon, 7 Jul 1997 23:27:24 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA20656; Tue, 8 Jul 1997 08:27:02 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA06576; Tue, 8 Jul 1997 08:20:29 +0200 (MET DST) Message-ID: <19970708082029.MM26714@uriah.heep.sax.de> Date: Tue, 8 Jul 1997 08:20:29 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Cc: daveh@tamis.com (David Holloway) Subject: Re: lsdev References: <19970707231759.08309@mi.uni-koeln.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from David Holloway on Jul 7, 1997 17:04:59 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As David Holloway wrote: > what ever happened to lsdev? revision 1.7 date: 1996/09/06 23:05:20; author: phk; state: dead; lines: +0 -0 Remove lsdev. Devconf never grew up. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Tue Jul 8 02:16:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA07210 for current-outgoing; Tue, 8 Jul 1997 02:16:00 -0700 (PDT) Received: from sunny.wup.de (www.wup.de [149.237.200.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA07202; Tue, 8 Jul 1997 02:15:51 -0700 (PDT) Received: (from andreas@localhost) by sunny.wup.de (8.8.6/8.8.6) id LAA09506; Tue, 8 Jul 1997 11:11:52 +0200 (MET DST) Message-ID: <19970708111148.42085@sunny.wup.de> Date: Tue, 8 Jul 1997 11:11:48 +0200 From: Andreas Klemm To: current@FreeBSD.ORG Cc: jkh@FreeBSD.ORG Subject: FreeBSD 2.2.2 cdrom installation problem (sysinstall core dump,...) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 X-phone: Wiechers & Partner +49 2173 3964 161 X-fax: Wiechers & Partner +49 2173 3964 222 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi ! I just experienced some problems with the CD-ROM installation. a) In the toplevel configuration menue there is a submenue for different configuration options (editor, ftp active, passive,...) I started to toggle multiple times between debugging yes/no about five times, then the sysinstall program core dumped and the machine reboots b) During custom configuration I made various post installation settings ... After first reboot there was nearly nothing configured in /etc c) When choosing to install the samba package, you have three choices, export home dirs, printers and other additional directories. I want to export additionally: /var/ftp and /usr/local/www Message: "Directory does not exist" "Choose another one ?" On Yes: I get another non working chance On No: samba configuration is rapidly quitted I think you possibly forgot the mount point on which all disks are mounted ... /var/ftp should exist ... or ?! And if such a dir really doesn't exist, I think this should only be a warning ... If somebody knows what he needs, it should be allowed to accespt such a directory. Or it should be created on demand ... Andreas /// -- aklemm@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - From owner-freebsd-current Tue Jul 8 04:42:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12729 for current-outgoing; Tue, 8 Jul 1997 04:42:36 -0700 (PDT) Received: from nagual.pp.ru (ache.relcom.ru [194.58.229.133]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA12722 for ; Tue, 8 Jul 1997 04:42:27 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.8.6/8.8.5) id PAA02426; Tue, 8 Jul 1997 15:42:17 +0400 (MSD) Date: Tue, 8 Jul 1997 15:42:14 +0400 (MSD) From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= To: FreeBSD-current cc: Bruce Evans , cvsup-bugs@polstra.com Subject: CVS Branches hits again! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Please delete following files: Checkout src/usr.bin/bdes/* Checkout src/usr.bin/ld/* Checkout src/usr.bin/m4/* Checkout src/usr.bin/man/* Checkout src/usr.bin/patch/* Checkout src/usr.bin/sccs/* Checkout src/usr.bin/sort/* Checkout src/usr.bin/uucp/* etc. I.e. all recently imported to vendor branch. I got them all via CVSUP. We need to fix this bug somehow! -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ From owner-freebsd-current Tue Jul 8 07:52:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA20795 for current-outgoing; Tue, 8 Jul 1997 07:52:12 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA20788 for ; Tue, 8 Jul 1997 07:52:09 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id AAA18595; Wed, 9 Jul 1997 00:47:51 +1000 Date: Wed, 9 Jul 1997 00:47:51 +1000 From: Bruce Evans Message-Id: <199707081447.AAA18595@godzilla.zeta.org.au> To: ache@nagual.pp.ru, current@freebsd.org Subject: Re: CVS Branches hits again! Cc: bde@zeta.org.au, cvsup-bugs@polstra.com Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Please delete following files: > > Checkout src/usr.bin/bdes/* > Checkout src/usr.bin/ld/* > Checkout src/usr.bin/m4/* > Checkout src/usr.bin/man/* > Checkout src/usr.bin/patch/* > Checkout src/usr.bin/sccs/* > Checkout src/usr.bin/sort/* > Checkout src/usr.bin/uucp/* It is the same problem as with disklabel.5.5. We don't want most of these files even in attics. In m4, only serv.c is dead. It was last released in 2.0.5. The others are all dead. uucp was last released in 2.0. The others have never been released in 2.x. Bruce From owner-freebsd-current Tue Jul 8 10:46:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28397 for current-outgoing; Tue, 8 Jul 1997 10:46:03 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA28392 for ; Tue, 8 Jul 1997 10:46:00 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id KAA25344; Tue, 8 Jul 1997 10:45:35 -0700 (PDT) Message-Id: <199707081745.KAA25344@austin.polstra.com> To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= cc: FreeBSD-current , Bruce Evans Subject: Re: CVS Branches hits again! In-reply-to: Your message of "Tue, 08 Jul 1997 15:42:14 +0400." References: Date: Tue, 08 Jul 1997 10:45:34 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I.e. all recently imported to vendor branch. > I got them all via CVSUP. > > We need to fix this bug somehow! OK, I will try to fix CVSup so that it does the right thing. John From owner-freebsd-current Tue Jul 8 12:23:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA03058 for current-outgoing; Tue, 8 Jul 1997 12:23:13 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA03053 for ; Tue, 8 Jul 1997 12:23:10 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <97626(2)>; Tue, 8 Jul 1997 12:18:55 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177512>; Tue, 8 Jul 1997 12:03:13 -0700 To: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= cc: FreeBSD-current , Bruce Evans , cvsup-bugs@polstra.com Subject: Re: CVS Branches hits again! In-reply-to: Your message of "Tue, 08 Jul 97 04:42:14 PDT." Date: Tue, 8 Jul 1997 12:03:07 PDT From: Bill Fenner Message-Id: <97Jul8.120313pdt.177512@crevenia.parc.xerox.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is cvsup not being bug-compatible with cvs. These files really were brought back from the dead, but cvs doesn't check them out because it left them in the Attic. The repository needs to be fixed; all of the files that are dead on the vendor branch should be updated to be dead but not be on the vendor branch. I know that futzing with the RCS files directly is considered too dangerous to think about, but is probably the easiest way to handle this case since cvs doesn't seem to want to. A sample RCS-file-munching is: --- bdes.1,v.old Tue Jul 8 11:56:53 1997 +++ bdes.1,v Tue Jul 8 12:00:20 1997 @@ -1,5 +1,5 @@ -head 1.1; -branch 1.1.1; +head 1.2; +branch; access; symbols bsd_44_lite_2:1.1.1.3 @@ -15,6 +15,11 @@ branches 1.1.1.1; next ; +1.2 +date 97.07.09.00.00.00; author someone; state dead; +branches; +next 1.1; + 1.1.1.1 date 94.05.27.12.30.50; author rgrimes; state Exp; branches; @@ -36,9 +41,9 @@ desc -1.1 +1.2 log -@Initial revision +@Remove already-dead file @ text @.\" Copyright (c) 1991, 1993 @@ -346,6 +351,13 @@ This is inherent in the DES algorithm (s .I "Advances in Cryptology \- Crypto '86 Proceedings" , Springer-Verlag New York, \(co1987, pp. 9-32.) @ + +1.1 +log +@Initial revision +@ +text +@@ 1.1.1.1 This is a trivial set of transforms that can be applied to any RCS file which has no rev 1.2 and is dead on the vendor branch. Bill From owner-freebsd-current Tue Jul 8 14:41:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA10231 for current-outgoing; Tue, 8 Jul 1997 14:41:06 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA10212; Tue, 8 Jul 1997 14:40:59 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA23624; Tue, 8 Jul 1997 15:40:53 -0600 (MDT) Date: Tue, 8 Jul 1997 15:40:53 -0600 (MDT) Message-Id: <199707082140.PAA23624@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Brian N. Handy" Cc: Nate Williams , freebsd-mobile@freebsd.org, current@freebsd.org Subject: Re: X on a TP560 In-Reply-To: References: <199707082124.PAA23364@rocky.mt.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brian N. Handy writes: > >> To get XF86_SVGA working on my laptop, I had to enable "options XSERVER" > >> in my kernel. It works! (I found this in the XFree documentation, though > >> in practice I've never needed it before I think. But I've always used the > >> S3 servers before as well. Strange.) > > > >XSERVER has been (and continues to be) part of the GENERIC kernels since > >the 1.* days. > > My GENERIC config file has it commented out. This is from > releng22.freebsd.org. Similarly on my desktop box it's also #'d out. Hmm, it *shouldn't* be, AFAIK. Nate From owner-freebsd-current Tue Jul 8 15:20:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA12521 for current-outgoing; Tue, 8 Jul 1997 15:20:25 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA12504 for ; Tue, 8 Jul 1997 15:20:18 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id PAA28704; Tue, 8 Jul 1997 15:20:04 -0700 (PDT) Message-Id: <199707082220.PAA28704@austin.polstra.com> To: fenner@parc.xerox.com Cc: current@FreeBSD.ORG, bde@zeta.org.au, ache@nagual.pp.ru, peter@spinner.dialix.com.au Subject: Re: CVS Branches hits again! Date: Tue, 08 Jul 1997 15:20:03 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is cvsup not being bug-compatible with cvs. These files really > were brought back from the dead, but cvs doesn't check them out > because it left them in the Attic. Bill is right, but it's even worse than that. CVS is not even bug-compatible with CVS. For example, if you do a "cvs export -D tomorrow src/usr.bin" you do not get the same files as you get when you do a "cvs co -P src/usr.bin". The export command brings back the files that were erroneously killed on the vendor branch and then followed by a new import. "cvs co -P -D tomorrow src/usr.bin" does the same thing, even though the "-D tomorrow" shouldn't affect which files are checked out. Furthermore, if you do a "cvs co -P src/usr.bin" and then cd src/usr.bin/bdes cvs status bdes.c it says "Needs Checkout". > The repository needs to be fixed Yes, the repository needs to be fixed. It is a big mess. People who are busily importing lite2, please stop until this can be taken care of. Or at least trim out the files that have been removed from our source tree. I have a "fixed" cvsupd which behaves more like CVS and which will buy us some time. As soon as I test it a little bit more, I'll get it deployed on as many mirrors as I can. Luckily, the change is in the server and not in the client. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Tue Jul 8 16:05:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14772 for current-outgoing; Tue, 8 Jul 1997 16:05:12 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA14765 for ; Tue, 8 Jul 1997 16:05:08 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id QAA20156; Tue, 8 Jul 1997 16:04:21 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199707082304.QAA20156@GndRsh.aac.dev.com> Subject: Re: CVS Branches hits again! In-Reply-To: <199707082220.PAA28704@austin.polstra.com> from John Polstra at "Jul 8, 97 03:20:03 pm" To: jdp@polstra.com (John Polstra) Date: Tue, 8 Jul 1997 16:04:20 -0700 (PDT) Cc: fenner@parc.xerox.com, current@FreeBSD.ORG, bde@zeta.org.au, ache@nagual.pp.ru, peter@spinner.dialix.com.au X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > This is cvsup not being bug-compatible with cvs. These files really > > were brought back from the dead, but cvs doesn't check them out > > because it left them in the Attic. > > Bill is right, but it's even worse than that. CVS is not even > bug-compatible with CVS. > > For example, if you do a "cvs export -D tomorrow src/usr.bin" you > do not get the same files as you get when you do a "cvs co -P > src/usr.bin". The export command brings back the files that were Well of cource you get a different set of files, one command above uses the -P (prune) option and the other does not. You need to add a -P to your ``cvs export''!! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-current Tue Jul 8 16:08:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14992 for current-outgoing; Tue, 8 Jul 1997 16:08:25 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA14984 for ; Tue, 8 Jul 1997 16:08:19 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id QAA00883; Tue, 8 Jul 1997 16:08:05 -0700 (PDT) Message-Id: <199707082308.QAA00883@austin.polstra.com> To: "Rodney W. Grimes" cc: fenner@parc.xerox.com, current@FreeBSD.ORG, bde@zeta.org.au, ache@nagual.pp.ru, peter@spinner.dialix.com.au Subject: Re: CVS Branches hits again! In-reply-to: Your message of "Tue, 08 Jul 1997 16:04:20 PDT." <199707082304.QAA20156@GndRsh.aac.dev.com> References: <199707082304.QAA20156@GndRsh.aac.dev.com> Date: Tue, 08 Jul 1997 16:08:04 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Well of cource you get a different set of files, one command above > uses the -P (prune) option and the other does not. You need to > add a -P to your ``cvs export''!! Incorrect. "cvs export" doesn't even accept "-P". It is implied. Also, as I mentioned, "cvs co -P -D tomorrow src/usr.bin" -- even with the "-P" -- still brings back the pseudo-dead files. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Tue Jul 8 16:12:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA15350 for current-outgoing; Tue, 8 Jul 1997 16:12:23 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA15343 for ; Tue, 8 Jul 1997 16:12:14 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id QAA20195; Tue, 8 Jul 1997 16:11:28 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199707082311.QAA20195@GndRsh.aac.dev.com> Subject: Re: CVS Branches hits again! In-Reply-To: <199707082308.QAA00883@austin.polstra.com> from John Polstra at "Jul 8, 97 04:08:04 pm" To: jdp@polstra.com (John Polstra) Date: Tue, 8 Jul 1997 16:11:28 -0700 (PDT) Cc: fenner@parc.xerox.com, current@FreeBSD.ORG, bde@zeta.org.au, ache@nagual.pp.ru, peter@spinner.dialix.com.au X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Well of cource you get a different set of files, one command above > > uses the -P (prune) option and the other does not. You need to > > add a -P to your ``cvs export''!! > > Incorrect. "cvs export" doesn't even accept "-P". It is implied. > Also, as I mentioned, "cvs co -P -D tomorrow src/usr.bin" -- even > with the "-P" -- still brings back the pseudo-dead files. Then someone should fix the ``usage'' message, or maybe this is due to the 2.1-stable nature of the beast I am on right now: Script started on Tue Jul 8 23:10:28 1997 GndRsh# cvs export -H Usage: cvs export [-NPfln] [-r rev | -D date] [-d dir] [-k kopt] module... ^____ well, HUMM.... BOGUS as shown below!! -N Don't shorten module paths if -d specified. -f Force a head revision match if tag/date not found. -l Local directory only, not recursive -n Do not run module program (if any). -r rev Check out revision or tag. -D date Check out revisions as of date. -d dir Check out into dir instead of module name. -k kopt Use RCS kopt -k option on checkout. GndRsh# cvs export -P ls export: invalid option -- P Usage: cvs export [-NPfln] [-r rev | -D date] [-d dir] [-k kopt] module... -N Don't shorten module paths if -d specified. -f Force a head revision match if tag/date not found. -l Local directory only, not recursive -n Do not run module program (if any). -r rev Check out revision or tag. -D date Check out revisions as of date. -d dir Check out into dir instead of module name. -k kopt Use RCS kopt -k option on checkout. GndRsh# exit GndRsh# exit Script done on Tue Jul 8 23:10:39 1997 > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-current Tue Jul 8 16:29:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16086 for current-outgoing; Tue, 8 Jul 1997 16:29:20 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA16076 for ; Tue, 8 Jul 1997 16:29:17 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id QAA01070; Tue, 8 Jul 1997 16:28:51 -0700 (PDT) Message-Id: <199707082328.QAA01070@austin.polstra.com> To: "Rodney W. Grimes" cc: current@FreeBSD.ORG Subject: Re: CVS Branches hits again! In-reply-to: Your message of "Tue, 08 Jul 1997 16:11:28 PDT." <199707082311.QAA20195@GndRsh.aac.dev.com> References: <199707082311.QAA20195@GndRsh.aac.dev.com> Date: Tue, 08 Jul 1997 16:28:50 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Incorrect. "cvs export" doesn't even accept "-P". It is implied. > > Also, as I mentioned, "cvs co -P -D tomorrow src/usr.bin" -- even > > with the "-P" -- still brings back the pseudo-dead files. > > Then someone should fix the ``usage'' message, or maybe this is > due to the 2.1-stable nature of the beast I am on right now: Yes, the usage message is broken on my somewhat-old 2.2-stable machine. I notice that it's fixed on my -current machine, though, and I think it's fixed in up-to-date 2.2-stable as well. John From owner-freebsd-current Tue Jul 8 17:14:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA18748 for current-outgoing; Tue, 8 Jul 1997 17:14:33 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA18736; Tue, 8 Jul 1997 17:14:24 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id RAA01158; Tue, 8 Jul 1997 17:13:57 -0700 (PDT) To: Andreas Klemm cc: current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: FreeBSD 2.2.2 cdrom installation problem (sysinstall core dump,...) In-reply-to: Your message of "Tue, 08 Jul 1997 11:11:48 +0200." <19970708111148.42085@sunny.wup.de> Date: Tue, 08 Jul 1997 17:13:56 -0700 Message-ID: <1155.868407236@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I started to toggle multiple times between debugging yes/no > about five times, then the sysinstall program core dumped > and the machine reboots Hmmm. Don't do that. :-) Seriously, I'll try and reproduce this and the other "makes the install fall over" bugs you've reported here. > c) When choosing to install the samba package, you have three > choices, export home dirs, printers and other additional > directories. I'm going to kill this anyway - like the Apache setup, it doesn't belong in sysinstall and putting it there only discouraged the development of a post-installation setup utility. :-) Jordan From owner-freebsd-current Tue Jul 8 17:15:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA18812 for current-outgoing; Tue, 8 Jul 1997 17:15:09 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA18803; Tue, 8 Jul 1997 17:15:03 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id JAA09696; Wed, 9 Jul 1997 09:44:36 +0930 (CST) From: Michael Smith Message-Id: <199707090014.JAA09696@genesis.atrad.adelaide.edu.au> Subject: Re: X on a TP560 In-Reply-To: <199707082140.PAA23624@rocky.mt.sri.com> from Nate Williams at "Jul 8, 97 03:40:53 pm" To: nate@mt.sri.com (Nate Williams) Date: Wed, 9 Jul 1997 09:44:35 +0930 (CST) Cc: handy@sag.space.lockheed.com, nate@mt.sri.com, freebsd-mobile@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nate Williams stands accused of saying: > > > > > >XSERVER has been (and continues to be) part of the GENERIC kernels since > > >the 1.* days. > > > > My GENERIC config file has it commented out. This is from > > releng22.freebsd.org. Similarly on my desktop box it's also #'d out. > > Hmm, it *shouldn't* be, AFAIK. XSERVER is only required by pcvt. It is commented out because syscons is the default console driver. > Nate -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Jul 8 21:04:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA25271 for current-outgoing; Tue, 8 Jul 1997 21:04:45 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA25260 for ; Tue, 8 Jul 1997 21:04:41 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id VAA00583; Tue, 8 Jul 1997 21:04:10 -0700 (PDT) To: Chuck Robey cc: FreeBSD current Subject: Re: Install suggestion In-reply-to: Your message of "Tue, 08 Jul 1997 22:13:42 EDT." Date: Tue, 08 Jul 1997 21:04:10 -0700 Message-ID: <579.868421050@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > When setting up the devices, before the installation has begun, sometimes > I am a little too quick with the delete key, and kill something I would > like to have. I have to start the installation all over again then, Not if you catch your error before exiting (after which, of course, it's far too late for any mechanism to catch you before the probes fail and you hit the ground with a meaty thud). It is documented (hit F1) that you can pull things off the inactive list again if you inadvertantly delete them. I do assume that you've read those docs? :-) In any case, this is really Mike Smith's baby so I'll let him respond to your specific UI comments. Jordan From owner-freebsd-current Tue Jul 8 21:34:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26614 for current-outgoing; Tue, 8 Jul 1997 21:34:37 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26605 for ; Tue, 8 Jul 1997 21:34:29 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id OAA11134; Wed, 9 Jul 1997 14:04:09 +0930 (CST) From: Michael Smith Message-Id: <199707090434.OAA11134@genesis.atrad.adelaide.edu.au> Subject: Re: Install suggestion In-Reply-To: <579.868421050@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 8, 97 09:04:10 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 9 Jul 1997 14:04:09 +0930 (CST) Cc: chuckr@glue.umd.edu, freebsd-current@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > When setting up the devices, before the installation has begun, sometimes > > I am a little too quick with the delete key, and kill something I would > > like to have. I have to start the installation all over again then, > > Not if you catch your error before exiting (after which, of course, > it's far too late for any mechanism to catch you before the probes > fail and you hit the ground with a meaty thud). It is documented > (hit F1) that you can pull things off the inactive list again if > you inadvertantly delete them. I do assume that you've read those > docs? :-) *grins* > In any case, this is really Mike Smith's baby so I'll let him respond > to your specific UI comments. Uhh, did I miss something else here? I don't recall the original (but I have been eating my words wrt, Tcl in the base system as we port to Tcl 8) PST has my full support; Tcl and Perl &c need to be bundled in a sane fashion. Ports are bad, but the base system is worse. > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Jul 8 21:41:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27067 for current-outgoing; Tue, 8 Jul 1997 21:41:25 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA27059 for ; Tue, 8 Jul 1997 21:41:22 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id WAA24693; Tue, 8 Jul 1997 22:41:08 -0600 (MDT) Date: Tue, 8 Jul 1997 22:41:08 -0600 (MDT) Message-Id: <199707090441.WAA24693@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Michael Smith Cc: nate@mt.sri.com (Nate Williams), handy@sag.space.lockheed.com, current@freebsd.org Subject: Re: X on a TP560 In-Reply-To: <199707090014.JAA09696@genesis.atrad.adelaide.edu.au> References: <199707082140.PAA23624@rocky.mt.sri.com> <199707090014.JAA09696@genesis.atrad.adelaide.edu.au> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > >XSERVER has been (and continues to be) part of the GENERIC kernels since > > > >the 1.* days. > > > > > > My GENERIC config file has it commented out. This is from > > > releng22.freebsd.org. Similarly on my desktop box it's also #'d out. > > > > Hmm, it *shouldn't* be, AFAIK. > > XSERVER is only required by pcvt. It is commented out because syscons > is the default console driver. Hmm, I remember XSERVER being required to open up certain ports, but now that I've looked through the sources it doesn't appear to be necessary. Brian, you *are* using syscons, right? Nate From owner-freebsd-current Tue Jul 8 23:50:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01072 for current-outgoing; Tue, 8 Jul 1997 23:50:26 -0700 (PDT) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA01065 for ; Tue, 8 Jul 1997 23:50:24 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <61772(4)>; Tue, 8 Jul 1997 23:49:42 PDT Received: by crevenia.parc.xerox.com id <177512>; Tue, 8 Jul 1997 21:13:31 -0700 From: Bill Fenner To: current@freebsd.org, fenner@parc.xerox.com Subject: Re: CVS Branches hits again! Message-Id: <97Jul8.211331pdt.177512@crevenia.parc.xerox.com> Date: Tue, 8 Jul 1997 21:13:22 PDT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I realized that editing the RCS file directly was kinda silly. The appropriate RCS commands are: rcs -b co -l ci -f -sdead -m"Removing already-removed file" Bill From owner-freebsd-current Wed Jul 9 13:24:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA05919 for current-outgoing; Wed, 9 Jul 1997 13:24:02 -0700 (PDT) Received: from lamb.sas.com (daemon@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA05904 for ; Wed, 9 Jul 1997 13:23:54 -0700 (PDT) Received: from mozart by lamb.sas.com (5.65c/SAS/Gateway/01-23-95) id AA04967; Wed, 9 Jul 1997 16:23:51 -0400 Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA05349; Wed, 9 Jul 1997 16:20:08 -0400 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA26603; Wed, 9 Jul 1997 16:20:07 -0400 Message-Id: <199707092020.AA26603@iluvatar.unx.sas.com> Subject: 3.0-970621-SNAP & fxp0 failure To: freebsd-current@freebsd.org Date: Wed, 9 Jul 1997 16:20:07 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've just install the 3.0-970621-SNAP. I have an intel 10/100 card: fxp0: rev 0x01 int a irq 15 on pci0.17.0 when I type the following command in, the machine totally and completely freezes up. ifconfig fxp0 inet 10.26.1.45 netmask 0xffff0000 I must poweroff the machine to recover. If I swap the intel card out for a 3com, the following works just fine: vx0: <3COM 3C905 Fast Etherlink XL PCI> rev 0x00 int a irq 14 on pci1.9.0 ifconfig vx0 inet 10.26.1.45 netmask 0xffff0000 There are no messages being logged to the console, or /var/log/*. Does anyone have any ideas? I'm more than happy to try to debug this problem if someone can point me in the right direction. Thanks, John -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 From owner-freebsd-current Wed Jul 9 13:34:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06564 for current-outgoing; Wed, 9 Jul 1997 13:34:36 -0700 (PDT) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06431 for ; Wed, 9 Jul 1997 13:33:39 -0700 (PDT) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id NAA11285 for ; Wed, 9 Jul 1997 13:34:06 -0700 (PDT) From: Josh MacDonald Message-Id: <199707092034.NAA11285@paris.CS.Berkeley.EDU> To: current@freebsd.org Subject: Re: CVS Branches hits again! MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11278.868480441.1@paris.CS.Berkeley.EDU> Date: Wed, 09 Jul 1997 13:34:03 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk CVS seems to be causing problems. Many of you may already know: I've written a program, PRCS, which has been released for almost a year now. I feel PRCS has now reached levels of stability and dependability exceeding those of CVS, which for all it's design flaws may never be bug free. I'm on the verge of releasing PRCS version 1.2, which irons out all of the initial design problems and nasty implementation spots present in versions 1.0 and 1.1, and am feeling very confident in the program. I don't claim that PRCS is everything, however, as it still lacks a few things that people use in CVS. Some of these are things I wish to add to PRCS for future versions, and some of these things I think are poorly designed and don't belong in the core program itself and should be left to extensions of one sort or another. Mostly these are policy decisions which are likely to be controversial to one person or another and thus don't belong in the core utility. Some things it yet lacks are: 1) a client server environment 2) recursive module semantics 3) developer notification services (mailing-list notification, for example) and other command hooks (I want programmable extensions for the purpose of implementing these and the stuff below). Some things that it lacks and should be left to policy: 1) file locking such as CVS's watch and edit (are you, the freebsd developers, using it?) 2) checkout histories such as CVS's history command (which I beleive you have disabled) Some advantages: 1) Better branching model. 2) Atomic operations (this is this single most losing feature of CVS, IMHO). 3) It's faster. No days spent tagging repositories either. 4) It's easier to use and lacks the incestuous relation to RCS and all it's command semantics. This makes improving PRCS far easier than CVS, because in order to improve CVS now you need to break it and lose compatibility. I plan to replace RCS in the next major release, 1.2 is last 1.x release I have planned. This is done for the benefit of doing what CVSup does for a client-server implementation without all the difficulty of supporting the RCS file format, which only gets in the way of higher level programs like PRCS and CVS. 5) control over symbolic links and keyword replacement, including custom keywords. So while I've admitted that PRCS isn't out-of-the box ready as a drop-in replacement for CVS as you are using it, the purpose of this mail is to see if there was any interest in changing to PRCS now or in the future and if so, offering my services in closing the gap to make it happen. Except for the client/server part, the missing stuff isn't hard to add, and it should be noted that it would be pretty easy to modify CVSup to work with PRCS, since a PRCS repository looks very much like a CVS repository. Basically, in order to keep PRCS pure, I don't want to add a lot of the stuff CVS has because it breaks my orthogonality and economy of design principles. I leave these things to seperate, coordinated extensions and/or applications so that they may be included, excluded, or modified without interfering with the essential task, version control. However, if there are a few things I can hard-code in now to help stir up a lot more users it's probably worth my while. Please let me know what you think. Comments are welcome, particularly if there's something about PRCS that would keep you away from using it. -josh From owner-freebsd-current Wed Jul 9 15:04:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA15019 for current-outgoing; Wed, 9 Jul 1997 15:04:03 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA14981 for ; Wed, 9 Jul 1997 15:03:59 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id PAA24480; Wed, 9 Jul 1997 15:05:11 -0700 (PDT) Message-Id: <199707092205.PAA24480@implode.root.com> To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-970621-SNAP & fxp0 failure In-reply-to: Your message of "Wed, 09 Jul 1997 16:20:07 EDT." <199707092020.AA26603@iluvatar.unx.sas.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 09 Jul 1997 15:05:11 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Hi, > > I've just install the 3.0-970621-SNAP. I have an intel 10/100 >card: > >fxp0: > rev 0x01 int a irq 15 on pci0.17.0 > > when I type the following command in, the machine totally and >completely freezes up. > > ifconfig fxp0 inet 10.26.1.45 netmask 0xffff0000 > >I must poweroff the machine to recover. > > > If I swap the intel card out for a 3com, the following >works just fine: > >vx0: <3COM 3C905 Fast Etherlink XL PCI> rev 0x00 int a irq 14 on pci1.9.0 > >ifconfig vx0 inet 10.26.1.45 netmask 0xffff0000 > > There are no messages being logged to the console, or /var/log/*. > > Does anyone have any ideas? I'm more than happy to try to >debug this problem if someone can point me in the right direction. Looks like an interrupt problem. Many systems have the secondary IDE controller mapped to using irq15, so perhaps that is the problem. Try moving the Intel card to a physically different slot - this should cause the PCI BIOS to assign a different interrupt. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Wed Jul 9 15:07:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA15273 for current-outgoing; Wed, 9 Jul 1997 15:07:32 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA15263 for ; Wed, 9 Jul 1997 15:07:26 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA28979; Wed, 9 Jul 1997 16:06:54 -0600 (MDT) Date: Wed, 9 Jul 1997 16:06:54 -0600 (MDT) Message-Id: <199707092206.QAA28979@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Josh MacDonald Cc: current@freebsd.org Subject: Re: CVS Branches hits again! In-Reply-To: <199707092034.NAA11285@paris.CS.Berkeley.EDU> References: <199707092034.NAA11285@paris.CS.Berkeley.EDU> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ PRCS ] > Some things it yet lacks are: > > 1) a client server environment Becoming more important as FreeBSD developers are now starting to use it. > 2) recursive module semantics Pretty much unused. > 3) developer notification services (mailing-list notification, for > example) and other command hooks (I want programmable extensions > for the purpose of implementing these and the stuff below). This is pretty much critical for FreeBSD, as well as many of the other projects I use CVS for. Having a 'log' trail is good, as well as sending message to the developers. > Some things that it lacks and should be left to policy: > 1) file locking such as CVS's watch and edit (are you, the freebsd > developers, using it?) Not really important to me. > 2) checkout histories such as CVS's history command (which I beleive > you have disabled) Not so important for me or the projects I've used it on. > Some advantages: > 1) Better branching model. Can you expound on this a bit? > 2) Atomic operations (this is this single most losing feature of CVS, > IMHO). No kidding. > 5) control over symbolic links and keyword replacement, including custom > keywords. CVS has this control, though it isn't well documented. Nate From owner-freebsd-current Wed Jul 9 16:55:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA20451 for current-outgoing; Wed, 9 Jul 1997 16:55:39 -0700 (PDT) Received: from paris.CS.Berkeley.EDU (paris.CS.Berkeley.EDU [128.32.34.47]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA20442 for ; Wed, 9 Jul 1997 16:55:36 -0700 (PDT) Received: from paris.CS.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by paris.CS.Berkeley.EDU (8.8.3/8.8.2) with ESMTP id QAA11916; Wed, 9 Jul 1997 16:56:06 -0700 (PDT) From: Josh MacDonald Message-Id: <199707092356.QAA11916@paris.CS.Berkeley.EDU> To: Nate Williams cc: current@freebsd.org Subject: PRCS (was Re: CVS Branches hits again!) In-reply-to: Your message of "Wed, 09 Jul 1997 16:06:54 MDT." <199707092206.QAA28979@rocky.mt.sri.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <11909.868492563.1@paris.CS.Berkeley.EDU> Date: Wed, 09 Jul 1997 16:56:04 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > [ PRCS ] > > > Some things it yet lacks are: > > > > 1) a client server environment > > Becoming more important as FreeBSD developers are now starting to use > it. This is currently my first priority. I've kept pretty quiet and not pushed PRCS in too many places because of this, but spoke up now because I figure PRCS would be no worse than CVS since people seem to be using CVSup. I have a pretty cool design for the client-server archetecture which solves one of the problems I've noticed from users of CVS on these lists: people want to mirror a repository with their own modifications (branches, local changes, etc.) while at the same time participating in the global development effort and being able to synchronize repositories. My solution is to incorporate mirroring capabilities similar to those of CVSup into PRCS and allow branches to be marked LOCAL. Local branches don't participate in global repository synchronization. Towards this goal, as I hinted in previous mail, I've got a design for a new RCS-like version-file library using a delta algorithm of my design to replace the somewhat flawed usage of diff(1) (or any insert/delete delta) in the RCS file (if this doesn't make sense and you're interested, email me). I figured it would be easier to construct a new delta program and solve some outstanding problems than to write yet another RCS file manipulation library to deal with an old, flawed format. (The delta algorithm is implemented, the version-file library is only designed). How many of you are using CVS's client-server capabilities directly? Is it enabled/encouraged on freebsd.org? > > 2) recursive module semantics > > Pretty much unused. What I mean here, is that CVS basically versions a tree of directories and lets you name a module after various locations in the tree. PRCS would rather you treat each CVS-module as a seperate project. This leaves some coordination between modules undealt with. I suspect this is largely not a big deal, as long as a few conventions are maintained so that release engineers don't go crazy. > > 3) developer notification services (mailing-list notification, for > > example) and other command hooks (I want programmable extensions > > for the purpose of implementing these and the stuff below). > > This is pretty much critical for FreeBSD, as well as many of the other > projects I use CVS for. Having a 'log' trail is good, as well as > sending message to the developers. Right, I knew this would be a catch. Were this the only catch, I would be happy to add in everything you need. > > Some things that it lacks and should be left to policy: > > 1) file locking such as CVS's watch and edit (are you, the freebsd > > developers, using it?) > > Not really important to me. > > > 2) checkout histories such as CVS's history command (which I beleive > > you have disabled) > > Not so important for me or the projects I've used it on. > > > Some advantages: > > 1) Better branching model. > > Can you expound on this a bit? Mostly it comes as a result of atomic checkins. There is a big reduction in the complexity by avoiding such issues as vendor branches, tags, sticky tags, magic version numbers, and all that. Since each version is labeled with a unique MAJOR.MINOR pair and RCS-like tags are not used to label individual files, you have a much stronger notion of how your project branches and the events that occur on each branch. Admittedly, you can do the same stuff in CVS and in PRCS, but I argue that with PRCS it is easier to know what you're doing, what to do, and what you've done. CVS branches files for you and asks you to do all the branch management with tags. PRCS branches projects for you and lets you forget about individual file branching (it resembles Perforce in this way, though we both have different terms for what's going on). > > 2) Atomic operations (this is this single most losing feature of CVS, > > IMHO). > > No kidding. > > > 5) control over symbolic links and keyword replacement, including custom > > keywords. > > CVS has this control, though it isn't well documented. > > Nate I also sort of left out the things like the ability to rename, delete, and later readd files and directories. There is no such thing as -P, because PRCS knows about project versions, not individual collections of files. It knows that some directory didn't exist in a certain version and doesn't check it out, simple as that (it also knows how to maintain empty directories). There is no attic. There is no section in the manual describing three different equally bad ways of renaming a file. Nowhere in the PRCS documentation is the structure of the repository defined, it is completely unspecified to prevent people from making direct respository modifications. I neglected to give URLs for people to check it out. Documentation, links, a tutorial on advanced uses of merge (for the version-control impaired) are at: http://www.xcf.berkeley.edu/~jmacd/prcs.html and distributions are available directly from: ftp://ftp.xcf.berkeley.edu/pub/prcs The current latest version there is 1.2.0b8 but as I said, I expect to release 1.2 on public forums in the coming week. -josh From owner-freebsd-current Wed Jul 9 17:00:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA20925 for current-outgoing; Wed, 9 Jul 1997 17:00:36 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA20914 for ; Wed, 9 Jul 1997 17:00:33 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id SAA00009; Wed, 9 Jul 1997 18:00:28 -0600 (MDT) Date: Wed, 9 Jul 1997 18:00:28 -0600 (MDT) Message-Id: <199707100000.SAA00009@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Josh MacDonald Cc: Nate Williams , current@freebsd.org Subject: Re: PRCS (was Re: CVS Branches hits again!) In-Reply-To: <199707092356.QAA11916@paris.CS.Berkeley.EDU> References: <199707092206.QAA28979@rocky.mt.sri.com> <199707092356.QAA11916@paris.CS.Berkeley.EDU> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > How many of you are using CVS's client-server capabilities directly? Is > it enabled/encouraged on freebsd.org? I'm using it at work quite a lot. Would the client/server be limited to unix, or would other OS's be able to participate somewhat easily? (This is one of the benefits of CVS/Perforce.) > > > 2) recursive module semantics > > > > Pretty much unused. > > What I mean here, is that CVS basically versions a tree of directories > and lets you name a module after various locations in the tree. I know, and like I said, it's pretty much unused in my experience. It's not necessary for the most part IMHO. > > > 3) developer notification services (mailing-list notification, for > > > example) and other command hooks (I want programmable extensions > > > for the purpose of implementing these and the stuff below). > > > > This is pretty much critical for FreeBSD, as well as many of the other > > projects I use CVS for. Having a 'log' trail is good, as well as > > sending message to the developers. > > Right, I knew this would be a catch. Were this the only catch, I would be > happy to add in everything you need. *grin* > I neglected to give URLs for people to check it out. Documentation, > links, a tutorial on advanced uses of merge (for the version-control > impaired) are at: > > http://www.xcf.berkeley.edu/~jmacd/prcs.html > > and distributions are available directly from: > > ftp://ftp.xcf.berkeley.edu/pub/prcs ... Thanks Josh! Nate From owner-freebsd-current Thu Jul 10 00:34:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA12584 for current-outgoing; Thu, 10 Jul 1997 00:34:36 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA12564 for ; Thu, 10 Jul 1997 00:34:28 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA22837 for freebsd-current@FreeBSD.org; Thu, 10 Jul 1997 09:34:27 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA00383; Thu, 10 Jul 1997 09:29:03 +0200 (MET DST) Message-ID: <19970710092903.VH26816@uriah.heep.sax.de> Date: Thu, 10 Jul 1997 09:29:03 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.org (FreeBSD-current users) Subject: [pac@bvemx.ppco.com: kern/4068: 'panic: cant mount root' while booting new installation from disk 2.] X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk -----Forwarded message from pac@bvemx.ppco.com----- >Number: 4068 >Category: kern >Synopsis: 'panic: cant mount root' while booting new installation from disk 2. -----End of forwarded message----- Pilot error, as we all know. But that's now the third or fourth bug report of someone who's not intelligent enough to read the documentation. Any suggestions on how to: . make the wdc driver auto-assign wd units in ascending order as the disks have been found, or . either detect the typical case of only wd0 and wd2 existing very early, and perhaps change the root dev to wd2 (instead of wd1), . or at least detect the case post-mortem, and hint to the correct usage in a printf() right before the panic? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Jul 10 01:26:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA14839 for current-outgoing; Thu, 10 Jul 1997 01:26:17 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA14833 for ; Thu, 10 Jul 1997 01:26:13 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id SAA29710; Thu, 10 Jul 1997 18:25:27 +1000 Date: Thu, 10 Jul 1997 18:25:27 +1000 From: Bruce Evans Message-Id: <199707100825.SAA29710@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: [pac@bvemx.ppco.com: kern/4068: 'panic: cant mount root' while booting new installation from disk 2.] Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>Number: 4068 >>Category: kern >>Synopsis: 'panic: cant mount root' while booting new installation from disk 2. > >-----End of forwarded message----- > >Pilot error, as we all know. But that's now the third or fourth bug >report of someone who's not intelligent enough to read the >documentation. People who actually read boot(8) in RELENG_2_2_2_RELEASE should get this wrong :-). ".It unit The unit number of the drive on the controller being used. Either 0 or 1 for wd..." This says that wd2 doesn't exists, and hints that you need to specify a controller number, but there is no way to specify a controller number at boot time. >Any suggestions on how to: >... >. or at least detect the case post-mortem, and hint to the correct > usage in a printf() right before the panic? It should at least hint about booting with -a (which current only works if the kernel was configured with "swap on generic", but should always work), and failed attempts to mount root should lead back to the -a prompt, at least if the kernel was booted with -a (-a is not so good for boots that should work automatically). This probably takes a negative amount of code to implement - just clean up swapgeneric.c and call the active part of it in a loop in init_main.c. Bruce From owner-freebsd-current Thu Jul 10 04:04:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA26136 for current-outgoing; Thu, 10 Jul 1997 04:04:13 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA26102; Thu, 10 Jul 1997 04:03:42 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-18.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA12155 (5.67b/IDA-1.5); Thu, 10 Jul 1997 13:03:34 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id NAA06255; Thu, 10 Jul 1997 13:01:32 +0200 (CEST) X-Face: " Date: Thu, 10 Jul 1997 13:01:31 +0200 From: Stefan Esser To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG, Stefan Esser Subject: Re: 3.0-970621-SNAP & fxp0 failure References: <199707092020.AA26603@iluvatar.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707092020.AA26603@iluvatar.unx.sas.com>; from John W. DeBoskey on Wed, Jul 09, 1997 at 04:20:07PM -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 9, "John W. DeBoskey" wrote: > Hi, > > I've just install the 3.0-970621-SNAP. I have an intel 10/100 > card: > > fxp0: > rev 0x01 int a irq 15 on pci0.17.0 > > when I type the following command in, the machine totally and > completely freezes up. > > ifconfig fxp0 inet 10.26.1.45 netmask 0xffff0000 > > I must poweroff the machine to recover. Please send me a VERBOSE boot message log (i.e. enter "-v" at the "Boot: " prompt). Best if you leave out the "ifconfig" command :) > If I swap the intel card out for a 3com, the following > works just fine: > > vx0: <3COM 3C905 Fast Etherlink XL PCI> rev 0x00 int a irq 14 on pci1.9.0 > > ifconfig vx0 inet 10.26.1.45 netmask 0xffff0000 Please send a VERBOSE boot message log for that configuration, too ... Did you put the 3com into the same slot that previously held the EtherExpress ??? (The probe message seems to indicate you did not ...) > There are no messages being logged to the console, or /var/log/*. > > Does anyone have any ideas? I'm more than happy to try to > debug this problem if someone can point me in the right direction. Well, I'm the meintainer of the PCI code in FreeBSD, and I'll be glad to help you get your system running. It may be necessary to try some patches, and I'd appreciate, if you could try them! Regards, STefan From owner-freebsd-current Thu Jul 10 04:10:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA26373 for current-outgoing; Thu, 10 Jul 1997 04:10:46 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA26366 for ; Thu, 10 Jul 1997 04:10:42 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-18.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA12847 (5.67b/IDA-1.5 for ); Thu, 10 Jul 1997 13:10:39 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id NAA06291; Thu, 10 Jul 1997 13:10:41 +0200 (CEST) X-Face: " Date: Thu, 10 Jul 1997 13:10:40 +0200 From: Stefan Esser To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0-970621-SNAP & fxp0 failure References: <199707092020.AA26603@iluvatar.unx.sas.com> <199707092205.PAA24480@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707092205.PAA24480@implode.root.com>; from David Greenman on Wed, Jul 09, 1997 at 03:05:11PM -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 9, David Greenman wrote: > >fxp0: > > rev 0x01 int a irq 15 on pci0.17.0 > >vx0: <3COM 3C905 Fast Etherlink XL PCI> rev 0x00 int a irq 14 on pci1.9.0 > Looks like an interrupt problem. Many systems have the secondary IDE > controller mapped to using irq15, so perhaps that is the problem. Try moving > the Intel card to a physically different slot - this should cause the PCI > BIOS to assign a different interrupt. True! The PCI/ISA code in FreeBSD does not check for conflicts between bus types, currently. (I have fixed this in my development sources, but wait for a consensus on how conflicts checking is generally approached before I'll commit my code.) It is generally good to avoid using IRQ14 and IRQ15 for PCI devices. Your BIOS may allow to reserve them for ISA devices, even if you don't actually use any IDE drives. In case you *do* have IDE drives connected, the system will most probably crash, if there is an IRQ conflict. But I actually don't know enough about IDE to understand, when IRQ14 is used for a disk drive, and when IRQ15 gets used ... You may want to do a "dmesg | grep 'irq 14'" (and the same for 'irq 15') and look for more than one line matching the conditions. Regards, STefan From owner-freebsd-current Thu Jul 10 07:16:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA03910 for current-outgoing; Thu, 10 Jul 1997 07:16:11 -0700 (PDT) Received: from cliffy.statsci.com (root@cliffy.statsci.com [206.63.206.72]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA03904 for ; Thu, 10 Jul 1997 07:16:04 -0700 (PDT) Received: from knife.statsci.com (knife [206.63.206.137]) by cliffy.statsci.com (8.8.6/8.8.6/Hub) with ESMTP id HAA04207; Thu, 10 Jul 1997 07:15:58 -0700 Received: from knife.statsci.com (localhost [127.0.0.1]) by knife.statsci.com (8.8.6/8.8.6/Client) with ESMTP id HAA14077; Thu, 10 Jul 1997 07:15:56 -0700 (PDT) Message-Id: <199707101415.HAA14077@knife.statsci.com> To: Josh MacDonald cc: Nate Williams , current@FreeBSD.ORG Subject: Re: PRCS (was Re: CVS Branches hits again!) References: <199707092356.QAA11916@paris.CS.Berkeley.EDU> In-reply-to: Your message of "Wed, 09 Jul 1997 16:56:04 -0700." <199707092356.QAA11916@paris.CS.Berkeley.EDU> From: Scott Blachowicz Reply-to: scott@statsci.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <14073.868544156.1@knife.statsci.com> Date: Thu, 10 Jul 1997 07:15:56 -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Josh MacDonald wrote: > > [ PRCS ] > > > > > Some things it yet lacks are: > > > > > > 1) a client server environment > > > > Becoming more important as FreeBSD developers are now starting to use > > it. > > This is currently my first priority. I've kept pretty quiet and not > pushed PRCS in too many places because of this, but spoke up now because > I figure PRCS would be no worse than CVS since people seem to be using > CVSup. Well...for me, the client/server stuff has been pretty handy. I have a few small repositories that I maintain at work, but work on at home occasionally. It's handy to be able to specify things so that syncing with the remote repository goes through a ssh tunnel as opposed to requiring some form of NFS access or maintaing a copy of my _repository_. Also, for use in a general development setting, it'd be real nice to be able to work on a MS Windows type of box... Maybe I should go visit your URL... Thanx, Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div) 1700 Westlake Ave N #500 scott@statsci.com Seattle, WA USA 98109 Scott.Blachowicz@seaslug.org From owner-freebsd-current Thu Jul 10 08:53:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA08509 for current-outgoing; Thu, 10 Jul 1997 08:53:54 -0700 (PDT) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA08502 for ; Thu, 10 Jul 1997 08:53:51 -0700 (PDT) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id RAA11530; Thu, 10 Jul 1997 17:55:25 +0200 (CEST) From: Mikael Karpberg Message-Id: <199707101555.RAA11530@ocean.campus.luth.se> Subject: Re: PRCS (was Re: CVS Branches hits again!) In-Reply-To: <199707101415.HAA14077@knife.statsci.com> from Scott Blachowicz at "Jul 10, 97 07:15:56 am" To: scott@statsci.com Date: Thu, 10 Jul 1997 17:55:24 +0200 (CEST) Cc: jmacd@CS.Berkeley.EDU, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Scott Blachowicz: > Josh MacDonald wrote: > > > > [ PRCS ] > > > > > > > Some things it yet lacks are: > > > > > > > > 1) a client server environment > > > > > > Becoming more important as FreeBSD developers are now starting to use > > > it. > > > > This is currently my first priority. I've kept pretty quiet and not > > pushed PRCS in too many places because of this, but spoke up now because > > I figure PRCS would be no worse than CVS since people seem to be using > > CVSup. > > Well...for me, the client/server stuff has been pretty handy. I have a few > small repositories that I maintain at work, but work on at home occasionally. > It's handy to be able to specify things so that syncing with the remote > repository goes through a ssh tunnel as opposed to requiring some form of NFS > access or maintaing a copy of my _repository_. Speaking of this client/server thing. If you have a repository on one machine and have a lot of developers that you want to give access into the repository, but NOT into the machine otherwise, how do you do? First of all, you need to let the committers name end up in the commit message. Second, you don't want the persons to be able to log in to your machine, just use the repository for storing/sharing/modifying code, etc. Can this be done with in the CVS way of doing things? Build a special "rsh" and "rshd" which does authentication, and then only allows the commands which has to do with CVS? Otherwise it would be nice if you simply had a "prcsd" listening on a port, which took a repository-username (which was in a special file, not in /etc/passwd) and an "athentication key", and checked if the host is allowed to connect in an ".rhosts"-like file. Then you could simply follow a protocol where you send commands and data over this socket. This system could be one way of doing it, the otherone being the normal CVS way with rsh/ssh. This could be done e.g if you set PRCSROOT to remote.machine.org:2050:/cvs or so. There... You can start flaming me now. :-) /Mikael From owner-freebsd-current Thu Jul 10 09:37:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA10631 for current-outgoing; Thu, 10 Jul 1997 09:37:12 -0700 (PDT) Received: from bitbox.follo.net (eivind@bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA10626 for ; Thu, 10 Jul 1997 09:37:06 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.8.5/8.7.3) id SAA04311; Thu, 10 Jul 1997 18:36:32 +0200 (CEST) Date: Thu, 10 Jul 1997 18:36:32 +0200 (CEST) Message-Id: <199707101636.SAA04311@bitbox.follo.net> From: Eivind Eklund To: Mikael Karpberg CC: scott@statsci.com, jmacd@CS.Berkeley.EDU, current@FreeBSD.ORG In-reply-to: Mikael Karpberg's message of Thu, 10 Jul 1997 17:55:24 +0200 (CEST) Subject: Re: PRCS (was Re: CVS Branches hits again!) References: <199707101415.HAA14077@knife.statsci.com> <199707101555.RAA11530@ocean.campus.luth.se> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > According to Scott Blachowicz: > > Josh MacDonald wrote: > > > > > > [ PRCS ] > > > > > > > > > Some things it yet lacks are: > > > > > > > > > > 1) a client server environment > > > > > > > > Becoming more important as FreeBSD developers are now starting to use > > > > it. > > > > > > This is currently my first priority. I've kept pretty quiet and not > > > pushed PRCS in too many places because of this, but spoke up now because > > > I figure PRCS would be no worse than CVS since people seem to be using > > > CVSup. > > > > Well...for me, the client/server stuff has been pretty handy. I have a few > > small repositories that I maintain at work, but work on at home occasionally. > > It's handy to be able to specify things so that syncing with the remote > > repository goes through a ssh tunnel as opposed to requiring some form of NFS > > access or maintaing a copy of my _repository_. > > Speaking of this client/server thing. If you have a repository on one > machine and have a lot of developers that you want to give access into > the repository, but NOT into the machine otherwise, how do you do? Trivially - by setting the shell of the users in question to point at a file containing only #!/bin/sh /usr/bin/cvs server (Not actually tested, but I've done similar things) Eivind. From owner-freebsd-current Thu Jul 10 09:39:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA10726 for current-outgoing; Thu, 10 Jul 1997 09:39:57 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA10720 for ; Thu, 10 Jul 1997 09:39:54 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wmMEl-00010J-00; Thu, 10 Jul 1997 10:38:35 -0600 To: Mikael Karpberg Subject: Re: PRCS (was Re: CVS Branches hits again!) Cc: scott@statsci.com, jmacd@CS.Berkeley.EDU, current@freebsd.org In-reply-to: Your message of "Thu, 10 Jul 1997 17:55:24 +0200." <199707101555.RAA11530@ocean.campus.luth.se> References: <199707101555.RAA11530@ocean.campus.luth.se> Date: Thu, 10 Jul 1997 10:38:35 -0600 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199707101555.RAA11530@ocean.campus.luth.se> Mikael Karpberg writes: : Can this be done with in the CVS way of doing things? Build a special : "rsh" and "rshd" which does authentication, and then only allows the : commands which has to do with CVS? Or you can have a special shell that chroots you to the right place and only allows you to execute the command cvs server. Or you could use the pserver method for CVS, but the security implications are not as strong as when you require ssh to be used :-). Warner From owner-freebsd-current Thu Jul 10 10:02:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA12055 for current-outgoing; Thu, 10 Jul 1997 10:02:54 -0700 (PDT) Received: from fredriks-1.pr.mcs.net (fredriks-1.pr.mcs.net [205.164.50.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA12050 for ; Thu, 10 Jul 1997 10:02:50 -0700 (PDT) Received: (from lars@localhost) by fredriks-1.pr.mcs.net (8.8.5/8.6.6) id MAA00958 for current@freebsd.org; Thu, 10 Jul 1997 12:02:48 -0500 (CDT) From: Lars Fredriksen Message-Id: <199707101702.MAA00958@fredriks-1.pr.mcs.net> Subject: patches to make MSG_BSIZE a tunable To: current@freebsd.org Date: Thu, 10 Jul 1997 12:02:47 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, In ~lars/dmesg.diffs (it is actually a tar file of diffs, sorry about the name mangling), you can find diffs to the current tree that defines MSG_BSIZE as a tunable and osmsgbufsize a MIB variable that one can uses sysctl to get the value of. There are also patches to dmesg and syslogd to use sysctl to find the size of the log buffer. With respect to dmesg there is kind of a cludge. Since dmesg can be used to extract the log out of a core dump, I also had to put in code that would actually read the osmsgbufsize out of the kernel the old fashion way. One could argue that dmesg shouldn't mess with using sysctl just because of this. I haven't tested this otption yet to make sure it works. Now, that being said, I am happy to receive feedback on this. One thing I didn't like is that I had to define osmsgbufsize as an extern in a few kernel files. This should probably be in a header somewhere(like msgbuf.h, and it should probably have a typedef that one could use to make sure that the sizes matches. I don't think that will ever be a probelm, but it looks much cleaner that way. Hope someone has time to look at this. Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@fredriks-1.pr.mcs.net (home-home) From owner-freebsd-current Thu Jul 10 10:20:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA13039 for current-outgoing; Thu, 10 Jul 1997 10:20:49 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA13033 for ; Thu, 10 Jul 1997 10:20:45 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA23393; Thu, 10 Jul 1997 10:15:25 -0700 From: Terry Lambert Message-Id: <199707101715.KAA23393@phaeton.artisoft.com> Subject: Re: CVS Branches hits again! To: jmacd@CS.Berkeley.EDU (Josh MacDonald) Date: Thu, 10 Jul 1997 10:15:25 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: <199707092034.NAA11285@paris.CS.Berkeley.EDU> from "Josh MacDonald" at Jul 9, 97 01:34:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > CVS seems to be causing problems. > > Many of you may already know: I've written a program, PRCS, which > has been released for almost a year now. I feel PRCS has now reached > levels of stability and dependability exceeding those of CVS, which > for all it's design flaws may never be bug free. [ ... ] > Please let me know what you think. Comments are welcome, particularly > if there's something about PRCS that would keep you away from using it. Just my two cents... You would get a much better response if you provided a repository conversion tool for converting CVS repositories. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Jul 10 10:55:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14842 for current-outgoing; Thu, 10 Jul 1997 10:55:17 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA14826; Thu, 10 Jul 1997 10:54:57 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.5/8.8.5) with ESMTP id KAA17938; Thu, 10 Jul 1997 10:54:40 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.6/8.8.5) with SMTP id KAA17454; Thu, 10 Jul 1997 10:54:40 -0700 (PDT) Date: Thu, 10 Jul 1997 10:54:39 -0700 (PDT) From: Chris Timmons To: charnier@freebsd.org cc: freebsd-current@freebsd.org Subject: global broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Revision 1.3 of usr.bin/global/gctags/ctags.c changed the copyright string to be read only. An interesting bit of cruft further down in the file writes to the now const data. Compiler warnings and run-time bus errors follow: The change: RCS file: /home/ncvs//src/usr.bin/global/gctags/ctags.c,v retrieving revision 1.2 retrieving revision 1.3 diff -r1.2 -r1.3 35c35 < static char copyright[] = --- > static const char copyright[] = The compiler warning: cc -g -O -I/usr/src/usr.bin/global/gctags -DGTAGS -DBUGFIX -DMODIFY -DYACC -c /usr/src/usr.bin/global/gctags/ctags.c /usr/src/usr.bin/global/gctags/ctags.c: In function `main': /usr/src/usr.bin/global/gctags/ctags.c:112: warning: assignment of read-only location The bus error Program received signal SIGBUS, Bus error. main (argc=3, argv=0xefbfd758) at /usr/src/usr.bin/global/gctags/ctags.c:112 112 copyright[0] = copyright[0]; /* to satisfy compiler */ (gdb) FIX: IMHO since we are maintaining this on a vendor branch we should just remove the silly line 112 and the #ifdef LINT that surrounds it. -Chris From owner-freebsd-current Thu Jul 10 14:22:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA29513 for current-outgoing; Thu, 10 Jul 1997 14:22:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA29507 for ; Thu, 10 Jul 1997 14:21:53 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA01781 for freebsd-current@FreeBSD.ORG; Thu, 10 Jul 1997 23:21:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA00316; Thu, 10 Jul 1997 22:59:29 +0200 (MET DST) Message-ID: <19970710225929.CA46543@uriah.heep.sax.de> Date: Thu, 10 Jul 1997 22:59:29 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: [pac@bvemx.ppco.com: kern/4068: 'panic: cant mount root' while booting new installation from disk 2.] References: <199707100825.SAA29710@godzilla.zeta.org.au> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199707100825.SAA29710@godzilla.zeta.org.au>; from Bruce Evans on Jul 10, 1997 18:25:27 +1000 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Bruce Evans wrote: > It should at least hint about booting with -a (which current only works if > the kernel was configured with "swap on generic", but should always work), > and failed attempts to mount root should lead back to the -a prompt, at > least if the kernel was booted with -a (-a is not so good for boots > that should work automatically). Sounds reasonable. > This probably takes a negative amount > of code to implement :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Jul 10 15:05:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA01443 for current-outgoing; Thu, 10 Jul 1997 15:05:28 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA01299; Thu, 10 Jul 1997 15:02:29 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id PAA07649; Thu, 10 Jul 1997 15:00:50 -0700 (PDT) To: Chris Timmons cc: charnier@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: global broken In-reply-to: Your message of "Thu, 10 Jul 1997 10:54:39 PDT." Date: Thu, 10 Jul 1997 15:00:50 -0700 Message-ID: <7645.868572050@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > FIX: IMHO since we are maintaining this on a vendor branch we should just > remove the silly line 112 and the #ifdef LINT that surrounds it. Either that or just upgrade to 2.0 since that was just released. It's on the far end of my TODO list. :) Jordan From owner-freebsd-current Fri Jul 11 08:17:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA14779 for current-outgoing; Fri, 11 Jul 1997 08:17:07 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA14771 for ; Fri, 11 Jul 1997 08:17:04 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id IAA01015; Fri, 11 Jul 1997 08:16:04 -0700 (PDT) To: current@freebsd.org cc: hans@brandinnovators.com Subject: Heads up and and a call for a show of hands. Date: Fri, 11 Jul 1997 08:16:03 -0700 Message-ID: <1011.868634163@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've just committed some patches from Hans Zuidam to ldconfig and /etc/rc (in 3.0-current) which allow: 1. ldconfig to accept filenames as well as directory pathnames on the command line, in the file case it being assumed that the file contains directory pathnames (with the usual #'d comment support). 2. An /etc/ld.so.conf file which overrides our current "peek around and add" ldconfig path code in rc - if you have an /etc/ld.so.conf file, it's assumed to contain all the ldconfig path info. Now this is generally a good thing from the vendor's standpoint (and it was, in fact, Xi Graphics, Inc. who first requested it) since they don't have to messily edit the /etc/rc file, they can just tack their own lib paths onto the end of /etc/ld.so.conf. The question which is now raised in my mind, however, is a simple one: Should /etc/ld.so.conf be an _override_ or an _add on_ to the "detected" ldconfig path list? Making it an override is certainly the more flexible of the two options since you could conceivably use it to avoid /usr/lib altogether and set the system up to use your custom library locations. On the other hand, making it an override also means that the minute you "buy in" to /etc/ld.so.conf, you have to buy in all the way. An automated installation can't simply create ld.so.conf and start appending custom paths to it, it has to first detect that it's not there on a user's system and populate it with a sensible initial path, the most up-to-date value for "sensible" being pretty much whatever's auto-detected by default in the no-etc-ld.so.conf clause of /etc/rc. That fact tends to suggest that you'd also sort of like to keep the bit of rc which currently builds up _LDC and just selectively add /etc/ld.so.conf to the _end_ of this list for the localizations. This would also put the file far more our of the critical path and make its introduction less of a shock (at the cost, of course, of being able to use it for overriding anything). What do folks here think? Right now the behavior is "override", but since we're not using it yet, it's still a reasonable time to change that if necessary. :-) Jordan From owner-freebsd-current Fri Jul 11 09:24:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA18357 for current-outgoing; Fri, 11 Jul 1997 09:24:48 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA18352 for ; Fri, 11 Jul 1997 09:24:42 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id JAA02546; Fri, 11 Jul 1997 09:24:19 -0700 (PDT) Message-ID: <19970711092418.17324@hydrogen.nike.efn.org> Date: Fri, 11 Jul 1997 09:24:18 -0700 From: John-Mark Gurney To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, hans@brandinnovators.com Subject: Re: Heads up and and a call for a show of hands. References: <1011.868634163@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <1011.868634163@time.cdrom.com>; from Jordan K. Hubbard on Fri, Jul 11, 1997 at 08:16:03AM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard scribbled this message on Jul 11: > 2. An /etc/ld.so.conf file which overrides our current "peek around > and add" ldconfig path code in rc - if you have an /etc/ld.so.conf > file, it's assumed to contain all the ldconfig path info. why not make a /etc/ld.so.conf that overrides, and then do a /usr/local/etc/ld.so.conf that adds to the list... that way we stay within our current, "don't touch /etc, touch /usr/local" mind set that we seem to be following... > Now this is generally a good thing from the vendor's standpoint (and > it was, in fact, Xi Graphics, Inc. who first requested it) since they > don't have to messily edit the /etc/rc file, they can just tack their > own lib paths onto the end of /etc/ld.so.conf. The question which is > now raised in my mind, however, is a simple one: if we do what I say above, then they can add in /usr/local/etc/ld.so.conf and they don't even touch the base system.. nice for trying to get to a read-only root... > On the other hand, making it an override also means that the minute > you "buy in" to /etc/ld.so.conf, you have to buy in all the way. An > automated installation can't simply create ld.so.conf and start > appending custom paths to it, it has to first detect that it's not > there on a user's system and populate it with a sensible initial path, > the most up-to-date value for "sensible" being pretty much whatever's > auto-detected by default in the no-etc-ld.so.conf clause of /etc/rc. see above, basicly start out /etc/ld.so.conf with just the first or possibly both: /usr/lib /usr/X11R6/lib then you have in /usr/local/etc/ld.so.conf: /usr/local/lib of course it may be argued that /usr/local/lib should be added to the base ld.so.conf... but if there aren't any ports/packages that have installed libs, it would be a "wasted" dir to check... it isn't hard to make sure that a dir is in the file (like /usr/local/lib) so that ports installing libs can auto add themselves to the file... this will also help for ports that want to install the libs someplace other than /usr/local/lib (Modula-3 comes to mind)... this will also make the bsd.port.mk a little more bloated though... but the code would be straight forward... > What do folks here think? Right now the behavior is "override", but > since we're not using it yet, it's still a reasonable time to change > that if necessary. :-) sounds like a good addition the FreeBSD's easy of configurablity... ttyl.. -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-current Fri Jul 11 09:35:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA19172 for current-outgoing; Fri, 11 Jul 1997 09:35:51 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA19164 for ; Fri, 11 Jul 1997 09:35:48 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id KAA09553; Fri, 11 Jul 1997 10:35:26 -0600 (MDT) Date: Fri, 11 Jul 1997 10:35:26 -0600 (MDT) Message-Id: <199707111635.KAA09553@rocky.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: current@freebsd.org, hans@brandinnovators.com Subject: Re: Heads up and and a call for a show of hands. In-Reply-To: <1011.868634163@time.cdrom.com> References: <1011.868634163@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Should /etc/ld.so.conf be an _override_ or an _add on_ to > the "detected" ldconfig path list? _add_on_ for backward compatability. Folks who have modified their /etc/* files shouldn't have to re-write them 'yet again' in order for their system to boot multi-user. Nate From owner-freebsd-current Fri Jul 11 09:44:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA19649 for current-outgoing; Fri, 11 Jul 1997 09:44:54 -0700 (PDT) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA19636 for ; Fri, 11 Jul 1997 09:44:49 -0700 (PDT) Received: from [204.69.236.50] (GATEWAY.SKIPSTONE.COM [198.214.10.129]) by shrimp.dataplex.net (8.8.5/8.8.5) with SMTP id LAA00761; Fri, 11 Jul 1997 11:43:57 -0500 (CDT) Date: 11 Jul 97 11:43:56 -0500 Subject: Re: Heads up and and a call for a show of hands. From: "Richard Wackerbarth" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG X-Mailer: Cyberdog/2.0 MIME-Version: 1.0 Message-Id: Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Jul 11, 1997 10:16 AM, Jordan K. Hubbard wrote: > Should /etc/ld.so.conf be an _override_ or an _add on_ to the "detected" ldconfig path list? [arguments omitted] Why not get both effects. Have two config files, for example, /etc/ld.so.conf and /usr/local/etc/ld.so.conf. If either does not exist, /etc/rc would generate them. /etc/ld.so.conf would be generated to emulate the current "sniffed" configuration. /usr/local/etc/ld.so.conf would initially be empty. It would be the default place to append additional items. If you wish the sniffer to run at every boot, the rc.local can simply rm the /etc/ld.so.conf file. From owner-freebsd-current Fri Jul 11 10:10:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA21442 for current-outgoing; Fri, 11 Jul 1997 10:10:36 -0700 (PDT) Received: from degas.telebyte.nl (root@degas.telebyte.nl [194.235.214.15]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA21433 for ; Fri, 11 Jul 1997 10:10:32 -0700 (PDT) Received: from monet.telebyte.nl (wwanders@monet.telebyte.nl. [194.235.214.12]) by degas.telebyte.nl (8.8.5/8.8.5) with ESMTP id TAA15478 for ; Fri, 11 Jul 1997 19:10:26 +0200 From: "W.G.T.J. Wanders" Received: (from wwanders@localhost) by monet.telebyte.nl (8.8.5/8.8.5) id TAA20550 for current@freebsd.org; Fri, 11 Jul 1997 19:10:25 +0200 Message-Id: <199707111710.TAA20550@monet.telebyte.nl> Subject: Diamond Fireport 40 on FreeBSD. To: current@freebsd.org Date: Fri, 11 Jul 1997 19:10:24 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently installed a Diamond Fireport 40 Symbios/NCR 875 based UW SCSI controller in my PC at home and it has worked very fine since under FreeBSD 2.2.[1,2]. Only a small change in ncr.c was needed to get FreeBSD to see the card: *** ncr.c- Sat Mar 1 06:23:33 1997 --- ncr.c Sun Jun 15 00:28:21 1997 *************** *** 1286,1291 **** --- 1286,1292 ---- #define NCR_825_ID (0x00031000ul) #define NCR_860_ID (0x00061000ul) #define NCR_875_ID (0x000f1000ul) + #define DIAMOND_FIREPORT_40_ID (0x008f1000ul) #ifdef __NetBSD__ *************** *** 3197,3202 **** --- 3198,3206 ---- case NCR_875_ID: return ("ncr 53c875 wide scsi"); + + case DIAMOND_FIREPORT_40_ID: + return("Diamond FirePort 40"); } return (NULL); } I guess the Diamond Fireport 20 should also work with similar change. Greetings, William Wanders From owner-freebsd-current Fri Jul 11 10:13:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA21897 for current-outgoing; Fri, 11 Jul 1997 10:13:10 -0700 (PDT) Received: from Symbion.srrc.usda.gov ([199.78.118.118]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA21873 for ; Fri, 11 Jul 1997 10:13:00 -0700 (PDT) Received: from Symbion (localhost [127.0.0.1]) by Symbion.srrc.usda.gov (8.8.6/8.8.6) with ESMTP id MAA16286 for ; Fri, 11 Jul 1997 12:10:20 -0500 (CDT) Message-Id: <199707111710.MAA16286@Symbion.srrc.usda.gov> X-Mailer: exmh version 2.0delta 6/3/97 To: freebsd-current@freebsd.org From: Glenn Johnson Subject: installing g77 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Jul 1997 12:10:20 -0500 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I hope that this is the appropriate list. I have a Fortran program that is vital to my work and I would like to use g77, as this can provide better optimization. I read the documentation for g77 and it says that gcc must be patched. My question is, what problems might I run into when I update the FreeBSD source and execute 'make world'? Will g77 mess up 'make world' or vice-versa? I looked at the g77 port but got a message that it was broken because gcc needed to be upgraded. The gcc version in 'current' is fine but the port seems to be set to patch gcc-2.6.3, so I am not sure how to proceed with the port. Any help is greatly appreciated. Thanks. -- Glenn Johnson USDA-ARS-SRRC gjohnson@nola.srrc.usda.gov From owner-freebsd-current Fri Jul 11 10:20:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA22336 for current-outgoing; Fri, 11 Jul 1997 10:20:38 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA22330 for ; Fri, 11 Jul 1997 10:20:32 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-43.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA05217 (5.67b/IDA-1.5 for ); Fri, 11 Jul 1997 19:20:29 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id TAA13836; Fri, 11 Jul 1997 19:20:19 +0200 (CEST) X-Face: " Date: Fri, 11 Jul 1997 19:20:18 +0200 From: Stefan Esser To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, hans@brandinnovators.com Subject: Re: Heads up and and a call for a show of hands. References: <1011.868634163@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <1011.868634163@time.cdrom.com>; from Jordan K. Hubbard on Fri, Jul 11, 1997 at 08:16:03AM -0700 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 11, "Jordan K. Hubbard" wrote: > Should /etc/ld.so.conf be an _override_ or an _add on_ to > the "detected" ldconfig path list? Are comments allowed in /etc/ld.so.conf ? Assuming you ignore lines starting with a hash character, you could use "#keep" to preserve the old list, and make the upgrade procedure (which messes around with /etc/rc.* anyway) merge the currently found rc.conf default into the place of that comment, which will trigger the override behaviour ... > Making it an override is certainly the more flexible of the two > options since you could conceivably use it to avoid /usr/lib > altogether and set the system up to use your custom library locations. Yes, and I guess this is useful for a number of situations. But then, you could in such a case just modify the startup code to check for "/etc/rc.ld.prune" and start with a clean path in that case. Somebody needing /usr/lib taken out of the library path will surely be able to modify the scripts in /etc accordingly ... > On the other hand, making it an override also means that the minute > you "buy in" to /etc/ld.so.conf, you have to buy in all the way. An > automated installation can't simply create ld.so.conf and start > appending custom paths to it, it has to first detect that it's not > there on a user's system and populate it with a sensible initial path, > the most up-to-date value for "sensible" being pretty much whatever's > auto-detected by default in the no-etc-ld.so.conf clause of /etc/rc. Well, and that's what I think can be reached by having the "#keep" comment as the only entry of "/etc/rc.ld.conf" by default, and to postpone actually moving the path there to some later time, were the file munging happens anyway. > That fact tends to suggest that you'd also sort of like to keep the > bit of rc which currently builds up _LDC and just selectively add > /etc/ld.so.conf to the _end_ of this list for the localizations. This > would also put the file far more our of the critical path and make its > introduction less of a shock (at the cost, of course, of being able to > use it for overriding anything). > > What do folks here think? Right now the behavior is "override", but > since we're not using it yet, it's still a reasonable time to change > that if necessary. :-) Override is the better long term solution. But as you say, we need a smooth path leading there ... Regards, STefan From owner-freebsd-current Fri Jul 11 11:23:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA26194 for current-outgoing; Fri, 11 Jul 1997 11:23:30 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA26189 for ; Fri, 11 Jul 1997 11:23:26 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-43.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA05820 (5.67b/IDA-1.5 for ); Fri, 11 Jul 1997 20:23:23 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.6/8.6.9) id UAA14148; Fri, 11 Jul 1997 20:23:22 +0200 (CEST) X-Face: " Date: Fri, 11 Jul 1997 20:23:21 +0200 From: Stefan Esser To: "W.G.T.J. Wanders" Cc: current@FreeBSD.ORG Subject: Re: Diamond Fireport 40 on FreeBSD. References: <199707111710.TAA20550@monet.telebyte.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199707111710.TAA20550@monet.telebyte.nl>; from W.G.T.J. Wanders on Fri, Jul 11, 1997 at 07:10:24PM +0200 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 11, "W.G.T.J. Wanders" wrote: > I recently installed a Diamond Fireport 40 Symbios/NCR 875 > based UW SCSI controller in my PC at home and it has worked > very fine since under FreeBSD 2.2.[1,2]. Only a small change > in ncr.c was needed to get FreeBSD to see the card: > > *** ncr.c- Sat Mar 1 06:23:33 1997 > --- ncr.c Sun Jun 15 00:28:21 1997 > *************** > *** 1286,1291 **** > --- 1286,1292 ---- > #define NCR_825_ID (0x00031000ul) > #define NCR_860_ID (0x00061000ul) > #define NCR_875_ID (0x000f1000ul) > + #define DIAMOND_FIREPORT_40_ID (0x008f1000ul) Yes, and a patch to that effect has been applied to -current as of June 11, but not yet been incorporated into 2.2.x (or 2.1.x). I will add the code from -current into -stable, at least. Thanks for reminding me, that I failed to do so ... Regards, STefan From owner-freebsd-current Fri Jul 11 13:54:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA02851 for current-outgoing; Fri, 11 Jul 1997 13:54:25 -0700 (PDT) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA02844 for ; Fri, 11 Jul 1997 13:54:20 -0700 (PDT) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.5/8.7.3) id NAA27593; Fri, 11 Jul 1997 13:53:58 -0700 (PDT) Date: Fri, 11 Jul 1997 13:53:58 -0700 (PDT) Message-Id: <199707112053.NAA27593@vader.cs.berkeley.edu> To: jkh@time.cdrom.com CC: current@freebsd.org, hans@brandinnovators.com In-reply-to: <1011.868634163@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Heads up and and a call for a show of hands. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Now this is generally a good thing from the vendor's standpoint (and * it was, in fact, Xi Graphics, Inc. who first requested it) since they * don't have to messily edit the /etc/rc file, they can just tack their * own lib paths onto the end of /etc/ld.so.conf. The question which is * now raised in my mind, however, is a simple one: And Xi Graphics seems to have ignored my comment about just using the existing framework and adding /usr/{local,X11R6}/etc/rc.d/foo.sh to run ldconfig.sh and any other startup stuff. The -m flag to ldconfig was added for a reason. See what the modula-3-lib port does. I don't think an /etc/ld.so.conf is necessary (much less /usr/local/etc/ld.so.conf). I propose backing it out. Satoshi From owner-freebsd-current Fri Jul 11 15:27:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA06937 for current-outgoing; Fri, 11 Jul 1997 15:27:26 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA06911; Fri, 11 Jul 1997 15:27:04 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199707112227.PAA06911@hub.freebsd.org> Subject: Re: Heads up and and a call for a show of hands. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 11 Jul 1997 15:27:04 -0700 (PDT) Cc: current@freebsd.org, hans@brandinnovators.com In-Reply-To: <1011.868634163@time.cdrom.com> from "Jordan K. Hubbard" at Jul 11, 97 08:16:03 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk /etc/rc.conf used first to satisfy dynamic linking if /etc/ld.so.conf (or /usr/local/etc/ld.so.conf whichever is chosen) exits, then its contents override /etc/rc.conf for each library found in the directories listed. example: /etc/rc.conf: /usr/lib /usr/lib contains libc.so.2.2 libc.so.3.0 /etc/ld.so.conf: /usr/local/lib /usr/local/contains libc.so.3.0 then any programs that require libc.so.3.0, use the one in /usr/local/lib any programs that require libc.so.2.2 use the one in /usr/lib any vendor can install their own library to override the default no one has to rewrite their files unless they choose to populate /etc/ld.so.conf jmb From owner-freebsd-current Fri Jul 11 20:52:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA17483 for current-outgoing; Fri, 11 Jul 1997 20:52:00 -0700 (PDT) Received: from whizzo.TransSys.COM (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA17471 for ; Fri, 11 Jul 1997 20:51:58 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.TransSys.COM (8.8.6/8.7.3) with SMTP id XAA18977; Fri, 11 Jul 1997 23:51:36 -0400 (EDT) Message-Id: <199707120351.XAA18977@whizzo.TransSys.COM> X-Mailer: exmh version 2.0delta 6/3/97 To: asami@cs.berkeley.edu (Satoshi Asami) cc: jkh@time.cdrom.com, current@FreeBSD.ORG, hans@brandinnovators.com From: "Louis A. Mamakos" Subject: Re: Heads up and and a call for a show of hands. References: <199707112053.NAA27593@vader.cs.berkeley.edu> In-reply-to: Your message of "Fri, 11 Jul 1997 13:53:58 PDT." <199707112053.NAA27593@vader.cs.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Jul 1997 23:51:36 -0400 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > And Xi Graphics seems to have ignored my comment about just using the > existing framework and adding /usr/{local,X11R6}/etc/rc.d/foo.sh to > run ldconfig.sh and any other startup stuff. The -m flag to ldconfig > was added for a reason. I agree; this mechanism seems to work pretty nicely for both ports/packages as well as local software. > See what the modula-3-lib port does. I don't think an /etc/ld.so.conf > is necessary (much less /usr/local/etc/ld.so.conf). I propose backing > it out. I've used it locally to handle [incr tcl] which is installed in a different location and it sure beats having to edit a file, etc. And using the /usr/local/etc/rc.d script, you can invoke arbitrary policy (see if a directory that might be on removable media exists, etc) before adding directories to the list. It seems like to opportunity to render you machine inert with a badly "automatically" edited /etc/ld.so.conf file compared with the existing mechanisms argue against this new approach. louie From owner-freebsd-current Fri Jul 11 20:52:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA17546 for current-outgoing; Fri, 11 Jul 1997 20:52:57 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA17539 for ; Fri, 11 Jul 1997 20:52:55 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id UAA03005; Fri, 11 Jul 1997 20:51:52 -0700 (PDT) To: asami@cs.berkeley.edu (Satoshi Asami) cc: current@freebsd.org, hans@brandinnovators.com Subject: Re: Heads up and and a call for a show of hands. In-reply-to: Your message of "Fri, 11 Jul 1997 13:53:58 PDT." <199707112053.NAA27593@vader.cs.berkeley.edu> Date: Fri, 11 Jul 1997 20:51:52 -0700 Message-ID: <3001.868679512@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > And Xi Graphics seems to have ignored my comment about just using the > existing framework and adding /usr/{local,X11R6}/etc/rc.d/foo.sh to > run ldconfig.sh and any other startup stuff. The -m flag to ldconfig > was added for a reason. But that would suck when what you're trying to do is get /usr/dt/lib (CDE's default path) in there - you've got something in /usr/{local,X11R6}/etc/rc.d/foo.sh adding to the search path something completely outside that hierarchy? Bleah! Jordan From owner-freebsd-current Fri Jul 11 21:17:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA18306 for current-outgoing; Fri, 11 Jul 1997 21:17:11 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca9-10.ix.netcom.com [207.93.143.74]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA18296 for ; Fri, 11 Jul 1997 21:17:03 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id VAA04618; Fri, 11 Jul 1997 21:16:47 -0700 (PDT) Date: Fri, 11 Jul 1997 21:16:47 -0700 (PDT) Message-Id: <199707120416.VAA04618@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: current@freebsd.org, hans@brandinnovators.com In-reply-to: <3001.868679512@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Heads up and and a call for a show of hands. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * But that would suck when what you're trying to do is get /usr/dt/lib * (CDE's default path) in there - you've got something in * /usr/{local,X11R6}/etc/rc.d/foo.sh adding to the search path something * completely outside that hierarchy? Bleah! What's the big deal? They are adding a whole bunch of stuff to /usr/X11R6 (and last time I checked, /usr/X386) too anyway. Nobody said /usr/{local,X11R6}/etc/rc.d/foo.sh can't add to a search path to something outside that hierarchy. What I'm concerned most is that the requests from XiG people always seem to go directly to a few individuals, who then add it to the list without consent of (or in the case of /var/mail permissions or /etc/ld.so.conf, despite objection of) the other committers. That way they may get some things done their way, but have also pissed off a few people who are not going to spread any good words for them. Satoshi From owner-freebsd-current Fri Jul 11 21:43:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA19440 for current-outgoing; Fri, 11 Jul 1997 21:43:05 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA19430 for ; Fri, 11 Jul 1997 21:43:01 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id VAA03325; Fri, 11 Jul 1997 21:41:53 -0700 (PDT) To: "Louis A. Mamakos" cc: asami@cs.berkeley.edu (Satoshi Asami), current@FreeBSD.ORG, hans@brandinnovators.com Subject: Re: Heads up and and a call for a show of hands. In-reply-to: Your message of "Fri, 11 Jul 1997 23:51:36 EDT." <199707120351.XAA18977@whizzo.TransSys.COM> Date: Fri, 11 Jul 1997 21:41:53 -0700 Message-ID: <3321.868682513@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've used it locally to handle [incr tcl] which is installed in a different > location and it sure beats having to edit a file, etc. And using the > /usr/local/etc/rc.d script, you can invoke arbitrary policy (see if a > directory that might be on removable media exists, etc) before adding > directories to the list. Heh - actually, I also forgot to mention that the whole rc.d script thing has some inherent limitations as currently implement: What if, for example, you require that certain initialization be done in a given order? Not at all a far-fetched scenario. Jordan From owner-freebsd-current Sat Jul 12 00:03:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA23397 for current-outgoing; Sat, 12 Jul 1997 00:03:43 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA23386; Sat, 12 Jul 1997 00:03:35 -0700 (PDT) From: Julian Elischer Received: (from julian@localhost) by freefall.freebsd.org (8.8.6/8.8.5) id AAA20595; Sat, 12 Jul 1997 00:03:09 -0700 (PDT) Date: Sat, 12 Jul 1997 00:03:09 -0700 (PDT) Message-Id: <199707120703.AAA20595@freefall.freebsd.org> To: current@FreeBSD.ORG Subject: I've broken ping Cc: sef@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sean (SEF) has a fix but I can't check it in as my source machine has just crashed and I'm remote. the symptom is that it doesn't respond to SIGINTR correctly If this is a problem in the next 24 hours then go back a few revisions. I'll check in the fix (I tested it) as soon as my machine is rebooted. thanks or your patience! julian (or if sean can post the patch someone else can check it in) (to 2.2 and 3.0) (don;t you have commit privs sean?) From owner-freebsd-current Sat Jul 12 00:07:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA23555 for current-outgoing; Sat, 12 Jul 1997 00:07:36 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca32-05.ix.netcom.com [199.35.209.69]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA23546 for ; Sat, 12 Jul 1997 00:07:32 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id AAA00860; Sat, 12 Jul 1997 00:07:17 -0700 (PDT) Date: Sat, 12 Jul 1997 00:07:17 -0700 (PDT) Message-Id: <199707120707.AAA00860@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: current@freebsd.org, hans@brandinnovators.com In-reply-to: <3001.868679512@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Heads up and and a call for a show of hands. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * But that would suck when what you're trying to do is get /usr/dt/lib * (CDE's default path) in there - you've got something in * /usr/{local,X11R6}/etc/rc.d/foo.sh adding to the search path something * completely outside that hierarchy? Bleah! Oh, and if you really want to keep everything in the subtrees, you can add /usr/dt/etc/rc.d to the list of startup script directories. It is a nice editable field in /etc/rc.conf now (thanks to you! :). Satoshi From owner-freebsd-current Sat Jul 12 00:08:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA23622 for current-outgoing; Sat, 12 Jul 1997 00:08:02 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA23592; Sat, 12 Jul 1997 00:07:57 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id AAA23391; Sat, 12 Jul 1997 00:07:57 -0700 Date: Sat, 12 Jul 1997 00:07:57 -0700 From: Sean Eric Fagan Message-Id: <199707120707.AAA23391@kithrup.com> To: julian@freebsd.org Subject: Re: I've broken ping Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >(or if sean can post the patch someone else can check it in) >(to 2.2 and 3.0) (don;t you have commit privs sean?) Yeah, I have patches, but I was hoping you'd be able to test it more extensively than I could :). I can check it in tomorrow, otherwise. For the curious, the patches are below. I'm going to bed now :). Index: ping.c =================================================================== RCS file: /home/ncvs/src/sbin/ping/ping.c,v retrieving revision 1.23 diff -u -r1.23 ping.c --- ping.c 1997/07/09 20:33:58 1.23 +++ ping.c 1997/07/12 03:55:41 @@ -423,8 +423,19 @@ else (void)printf("PING %s: %d data bytes\n", hostname, datalen); - (void)signal(SIGINT, stopit); - (void)signal(SIGALRM, catcher); + si_sa.sa_handler = stopit; + sigemptyset(&si_sa.sa_mask); + si_sa.sa_flags = 0; + if (sigaction(SIGINT, &si_sa, 0) == -1) { + err(EX_OSERR, "sigaction SIGINT"); + } + + si_sa.sa_handler = catcher; + sigemptyset(&si_sa.sa_mask); + si_sa.sa_flags = 0; + if (sigaction(SIGALRM, &si_sa, 0) == -1) { + err(EX_OSERR, "sigaction SIGALRM"); + } /* * Use sigaction instead of signal() to get unambiguous semantics @@ -508,9 +519,17 @@ catcher(int sig) { int waittime; + struct sigaction si_sa; pinger(); - (void)signal(SIGALRM, catcher); + + si_sa.sa_handler = catcher; + sigemptyset(&si_sa.sa_mask); + si_sa.sa_flags = 0; + if (sigaction(SIGALRM, &si_sa, 0) == -1) { + err(EX_OSERR, "sigaction"); + } + if (!npackets || ntransmitted < npackets) alarm((u_int)interval); else { @@ -520,7 +539,9 @@ waittime = 1; } else waittime = MAXWAIT; - (void)signal(SIGALRM, stopit); + finish_up = 1; + si_sa.sa_handler = stopit; + (void)sigaction(SIGALRM, &si_sa, 0); (void)alarm((u_int)waittime); } } From owner-freebsd-current Sat Jul 12 00:11:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA23778 for current-outgoing; Sat, 12 Jul 1997 00:11:40 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca32-05.ix.netcom.com [199.35.209.69]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA23773 for ; Sat, 12 Jul 1997 00:11:36 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id AAA00868; Sat, 12 Jul 1997 00:10:48 -0700 (PDT) Date: Sat, 12 Jul 1997 00:10:48 -0700 (PDT) Message-Id: <199707120710.AAA00868@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: louie@TransSys.COM, current@FreeBSD.ORG, hans@brandinnovators.com In-reply-to: <3321.868682513@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Heads up and and a call for a show of hands. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Heh - actually, I also forgot to mention that the whole rc.d script * thing has some inherent limitations as currently implement: What if, * for example, you require that certain initialization be done in a * given order? Not at all a far-fetched scenario. They are run in alphabetical (actually shell globbing) order -- that's why modula-3 installs one with digits in front (you need the shared libraries to be added before you start cvsupd, for instance). We're not saying that that is a perfect mechanism, but I have yet to see a real world example of why it doesn't work. Besides, we're not talking about how to handle automatic startup scripts now (we've gone through that one already) -- it works pretty well for adding shared library paths, and that's all that this is about. Satoshi From owner-freebsd-current Sat Jul 12 01:12:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA25325 for current-outgoing; Sat, 12 Jul 1997 01:12:39 -0700 (PDT) Received: from helbig.informatik.ba-stuttgart.de (rvc1.informatik.ba-stuttgart.de [141.31.112.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA25320 for ; Sat, 12 Jul 1997 01:12:30 -0700 (PDT) Received: (from helbig@localhost) by helbig.informatik.ba-stuttgart.de (8.8.6/8.8.5) id KAA08749 for FreeBSD-current@FreeBSD.org; Sat, 12 Jul 1997 10:12:30 +0200 (MET DST) From: Wolfgang Helbig Message-Id: <199707120812.KAA08749@helbig.informatik.ba-stuttgart.de> Subject: Re: some forgotten submits In-Reply-To: From helbig at "Jul 11, 97 10:54:39 am" To: FreeBSD-current@FreeBSD.org Date: Sat, 12 Jul 1997 10:12:27 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi committers, May I ask you to review some of my proposals/fixes? Most of them don't seem to be *that* important to the FreeBSD project and thus are gathering dust while being ignored by you. But even getting *some* feedback like `leave us allone with that crap' is better than nothing :-(. bin/3741: Document virtual terminals in MAKEDEV's manual page. bin/4064: History search in libedit is broken. E. g. sh(1) uses only the first letter of the search string for matching. conf/3730 conf/3740: The deprecated option `g' of ls(1) is removed, and an an ENV environment file is added to the default skel files. kern/3742: Document the `new' option "CMD640" in the wd(4) manual page. ports/3924: A new port `spinne'--a digital circuit simulator. There is a buggy xview library package in 2.2.[12], but according to Thomas Gellekum it works fine in 2.2-stable so *that* hurdle to commit spinne is taken. The language of spinne is only german. The latest release of spinne is 1.0.1 . The distribution file and port can be found at ftp.ba-stuttgart.de/pub/FreeBSD. Thanks in advance Wolfgang From owner-freebsd-current Sat Jul 12 02:22:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA27095 for current-outgoing; Sat, 12 Jul 1997 02:22:55 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca32-05.ix.netcom.com [199.35.209.69]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA27088 for ; Sat, 12 Jul 1997 02:22:50 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id CAA01296; Sat, 12 Jul 1997 02:22:41 -0700 (PDT) Date: Sat, 12 Jul 1997 02:22:41 -0700 (PDT) Message-Id: <199707120922.CAA01296@silvia.HIP.Berkeley.EDU> To: gjohnson@nola.srrc.usda.gov CC: freebsd-current@FreeBSD.ORG In-reply-to: <199707111710.MAA16286@Symbion.srrc.usda.gov> (message from Glenn Johnson on Fri, 11 Jul 1997 12:10:20 -0500) Subject: Re: installing g77 From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * I hope that this is the appropriate list. I have a Fortran program that is freebsd-ports is probably more appropriate. * I looked at the g77 port but got a message that it was broken because gcc * needed to be upgraded. The gcc version in 'current' is fine but the port seems Sorry if the message was unclear, it means that g77 port needs to be updated to use gcc-2.7.x in the system. If you can fix the port and contribute the change back, it will be most appreciated! Satoshi From owner-freebsd-current Sat Jul 12 02:50:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA27988 for current-outgoing; Sat, 12 Jul 1997 02:50:30 -0700 (PDT) Received: from pegasus.tlk.com (root@pegasus.tlk.com [194.97.84.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA27983 for ; Sat, 12 Jul 1997 02:50:26 -0700 (PDT) Received: from ramsey.tb.9715.org(really [194.97.84.65]) by pegasus.tlk.com via sendmail with esmtp (ident root using rfc1413) id for ; Sat, 12 Jul 1997 11:49:49 +0200 (CEST)) Received: by ramsey.tb.9715.org via sendmail with stdio id for jkh@time.cdrom.com; Sat, 12 Jul 1997 11:49:47 +0200 (CEST) Message-Id: From: torstenb@ramsey.tb.9715.org (Torsten Blum) Subject: Re: Heads up and and a call for a show of hands. In-Reply-To: <199707120707.AAA00860@silvia.HIP.Berkeley.EDU> from Satoshi Asami at "Jul 12, 97 00:07:17 am" To: asami@cs.berkeley.edu (Satoshi Asami) Date: Sat, 12 Jul 1997 11:49:47 +0200 (CEST) Cc: jkh@time.cdrom.com, current@FreeBSD.ORG, hans@brandinnovators.com X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Satoshi Asami wrote: > * But that would suck when what you're trying to do is get /usr/dt/lib > * (CDE's default path) in there - you've got something in > * /usr/{local,X11R6}/etc/rc.d/foo.sh adding to the search path something > * completely outside that hierarchy? Bleah! > > Oh, and if you really want to keep everything in the subtrees, you can > add /usr/dt/etc/rc.d to the list of startup script directories. No need for that. CDE comes with a complete X11R6 distribution installed in /usr/X11R6. They can easily install a script in /usr/X11R6/etc/rc.d. -tb -- Torsten Blum, Friedensstraße 13a, 82110 Gemering, Munich, Germany "Wow, die Leute hier von DEC schreiben Ihre Dokumentation mit LaTeX... Ich bin im gelobten Land... Es gibt also die kommerzielle - PC und M$ freie Welt" -- Arne Steinkamm From owner-freebsd-current Sat Jul 12 03:01:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA28208 for current-outgoing; Sat, 12 Jul 1997 03:01:14 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca32-05.ix.netcom.com [199.35.209.69]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA28203 for ; Sat, 12 Jul 1997 03:01:10 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id DAA06924; Sat, 12 Jul 1997 03:00:42 -0700 (PDT) Date: Sat, 12 Jul 1997 03:00:42 -0700 (PDT) Message-Id: <199707121000.DAA06924@silvia.HIP.Berkeley.EDU> To: torstenb@ramsey.tb.9715.org CC: jkh@time.cdrom.com, current@FreeBSD.ORG, hans@brandinnovators.com In-reply-to: (torstenb@ramsey.tb.9715.org) Subject: Re: Heads up and and a call for a show of hands. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * No need for that. CDE comes with a complete X11R6 distribution installed * in /usr/X11R6. They can easily install a script in /usr/X11R6/etc/rc.d. I know (and I said that already ... mails arriving out of order, Torsten? :).... But maybe they will decide to have an "DT only" installation option, that puts stuff only in the /usr/dt subtree. (Or they might decide to go back to /usr/X386, who knows.) The point is that, either way, there is an existing mechanism that can easily be used without a need for additional features added to ldconfig and/or /etc/rc. Satoshi From owner-freebsd-current Sat Jul 12 04:48:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA02586 for current-outgoing; Sat, 12 Jul 1997 04:48:16 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA02581 for ; Sat, 12 Jul 1997 04:48:14 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id EAA07775; Sat, 12 Jul 1997 04:47:14 -0700 (PDT) To: asami@cs.berkeley.edu (Satoshi Asami) cc: current@freebsd.org, hans@brandinnovators.com Subject: Re: Heads up and and a call for a show of hands. In-reply-to: Your message of "Sat, 12 Jul 1997 00:07:17 PDT." <199707120707.AAA00860@silvia.HIP.Berkeley.EDU> Date: Sat, 12 Jul 1997 04:47:13 -0700 Message-ID: <7771.868708033@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Oh, and if you really want to keep everything in the subtrees, you can > add /usr/dt/etc/rc.d to the list of startup script directories. It is > a nice editable field in /etc/rc.conf now (thanks to you! :). Well, it's a nice field, yes. Editable I'm not so sure about. :-) We need some way of doing this from scripts and other utilities, and I guess that's the next step. But yes, you're right - it wouldn't take a lot of work to make /usr/dt conformant. Jordan From owner-freebsd-current Sat Jul 12 05:01:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA03033 for current-outgoing; Sat, 12 Jul 1997 05:01:36 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca32-05.ix.netcom.com [199.35.209.69]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA03026 for ; Sat, 12 Jul 1997 05:01:32 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id FAA07881; Sat, 12 Jul 1997 05:01:16 -0700 (PDT) Date: Sat, 12 Jul 1997 05:01:16 -0700 (PDT) Message-Id: <199707121201.FAA07881@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: current@freebsd.org, hans@brandinnovators.com In-reply-to: <7771.868708033@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Heads up and and a call for a show of hands. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Well, it's a nice field, yes. Editable I'm not so sure about. :-) * We need some way of doing this from scripts and other utilities, * and I guess that's the next step. I thought the whole point of enforcing a strict syntax to rc.conf (one variable per line, comments in the same line after the `var="value"' pair, etc.) was to make it easily editable from scripts. At least it's not much less auto-editable than the proposed /etc/ld.so.config, considering that they need to delete lines when the user deinstalls the package.... One can even argue that it is just as easy because if they want to be really lazy (i.e., don't even want to use ed/sed/awk), they can just do something like echo "local_startup="${local_startup} /usr/dt/lib # CDE, do not touch" \ >> /etc/rc.conf during installation and mv /etc/rc.conf /etc/rc.conf.tmp grep -v '^local_startup=${local_startup} /usr/dt/lib # CDE, do not touch$' \ /etc/rc.conf.tmp > /etc/rc.conf rm /etc/rc.conf.tmp for deinstallation. * But yes, you're right - it wouldn't take a lot of work to make /usr/dt * conformant. Glad you agree. :) Satoshi From owner-freebsd-current Sat Jul 12 05:25:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA03692 for current-outgoing; Sat, 12 Jul 1997 05:25:36 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA03686 for ; Sat, 12 Jul 1997 05:25:32 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id FAA07886; Sat, 12 Jul 1997 05:24:27 -0700 (PDT) To: asami@cs.berkeley.edu (Satoshi Asami) cc: torstenb@ramsey.tb.9715.org, current@FreeBSD.ORG, hans@brandinnovators.com Subject: Re: Heads up and and a call for a show of hands. In-reply-to: Your message of "Sat, 12 Jul 1997 03:00:42 PDT." <199707121000.DAA06924@silvia.HIP.Berkeley.EDU> Date: Sat, 12 Jul 1997 05:24:27 -0700 Message-ID: <7882.868710267@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The point is that, either way, there is an existing mechanism that can > easily be used without a need for additional features added to > ldconfig and/or /etc/rc. While this is true, I don't see it as an effective argument for mandating only _one_ way of doing things. More to the point, I think that it's actually far more of a stretch to have the local package startup mechanism setting the ldconfig path than it is to have a specific mechanism for that purpose. I've had users ask me why, for example, that "modula3 needed a daemon." It doesn't, of course, but their confusion stems from the fact that during boot, the user sees something like: Local package initialization: apache m3 sshd And jumps to the obvious conclusion. /etc/ld.so.conf also appears in other UN*X environments, it's hardly a BSD first, and a growing number of admins are beginning to look there for override control. Our ${prefix}/etc/rc.d hack is, by contrast, something very FreeBSD specific. As to the question of "override vs overlay", after listening to various people's comments, I'm thinking that the following compromise scenario would also make some sense: First, we change: local_startup="/usr/local/etc/rc.d /usr/X11R6/etc/rc.d" # startup script dirs. To: local_dirs="/usr/local /usr/X11R6" # local hierarchies of importance. local_startup=YES # NO to deactivate local scripts. And then change this code in rc to: if [ "X${local_startup}" != X"NO" ]; then echo -n 'Local package initialization:' for dir in ${local_dirs}; do [ -d ${dir} ] && for script in ${dir}/etc/rc.d/*.sh; do [ -x ${script} ] && ${script} start done done echo . fi Once that's done, we can build the initial ld path by saying: if [ -f /etc/ld.so.conf ]; then _LDC=/etc/ld.so.conf else _LDC=/usr/lib if [ -d /usr/lib/compat ]; then _LDC="${_LDC} /usr/lib/compat" ; fi if [ -d /usr/X11R6/lib ]; then _LDC="${_LDC} /usr/X11R6/lib" ; fi if [ -d /usr/local/lib ]; then _LDC="${_LDC} /usr/local/lib" ; fi for dir in ${local_dirs}; do if [ -f ${dir}/etc/ld.so.conf ]; then _LDC="${dir}/etc/ld.so.conf ${_LDC}" fi done fi and that gives you both an engineer's override and configurable, vendor-editable files which follow the default ldpath. Jordan From owner-freebsd-current Sat Jul 12 06:05:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA04468 for current-outgoing; Sat, 12 Jul 1997 06:05:04 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04449 for ; Sat, 12 Jul 1997 06:04:59 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id WAA28798; Sat, 12 Jul 1997 22:34:39 +0930 (CST) From: Michael Smith Message-Id: <199707121304.WAA28798@genesis.atrad.adelaide.edu.au> Subject: Re: Heads up and and a call for a show of hands. In-Reply-To: <7771.868708033@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 12, 97 04:47:13 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 12 Jul 1997 22:34:39 +0930 (CST) Cc: asami@cs.berkeley.edu, current@FreeBSD.ORG, hans@brandinnovators.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > Oh, and if you really want to keep everything in the subtrees, you can > > add /usr/dt/etc/rc.d to the list of startup script directories. It is > > a nice editable field in /etc/rc.conf now (thanks to you! :). > > Well, it's a nice field, yes. Editable I'm not so sure about. :-) > We need some way of doing this from scripts and other utilities, > and I guess that's the next step. Uhm, well with juliet (which I am thinking of renaming 'sysconfig' now that the name is fading from use). you could say something like : echo ".system.startup.local_startups add " | juliet The script to do this isn't in place yet, but all the infrastructure is. ftp://gsoft.com.au/pub/juliet.tar.gz if you're interested. No, I haven't had time to work on it lately; I'm still waiting to hear from anyone that knows how to bind a Perl interpreter into a Tcl interpreter so that I can invoke Perl functions by name, and take callbacks from the Perl interpreter. > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. Kommando gegen Terrorismus [[ From owner-freebsd-current Sat Jul 12 06:14:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA04772 for current-outgoing; Sat, 12 Jul 1997 06:14:54 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04765 for ; Sat, 12 Jul 1997 06:14:49 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id WAA28818; Sat, 12 Jul 1997 22:44:33 +0930 (CST) From: Michael Smith Message-Id: <199707121314.WAA28818@genesis.atrad.adelaide.edu.au> Subject: Re: Heads up and and a call for a show of hands. In-Reply-To: <7882.868710267@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 12, 97 05:24:27 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 12 Jul 1997 22:44:33 +0930 (CST) Cc: asami@cs.berkeley.edu, torstenb@ramsey.tb.9715.org, current@FreeBSD.ORG, hans@brandinnovators.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > As to the question of "override vs overlay", after listening to > various people's comments, I'm thinking that the following compromise > scenario would also make some sense: Close. > local_dirs="/usr/local /usr/X11R6" # local hierarchies of importance. > local_startup=YES # NO to deactivate local scripts. No good. I want to run startups in /usr/local, but only ldconfig in /usr/X11R6, or vice versa. If you want to do this, the only way that works is to explicitly enumerate both sets of paths : local_loadpath="..." local_startups="..." This is simpler to understand, simpler to parse, and completely covers all possibilities by separating two things that have no reason to be associated in the first place. My personal take on the ldconfig situation : ldconfig should have an internal set of default paths (initiallt just /usr/lib), which can be manually inhibited on the commandline if required, it should support /etc/ld.so.conf by reading it if it exists, and it should take paths on the commandline. As for whether /etc/ld.so.conf should override the inbuilt search path, the obvious answer is _no_; there is a perfectly good control for this on the commandline. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sat Jul 12 06:24:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA05015 for current-outgoing; Sat, 12 Jul 1997 06:24:06 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA05010 for ; Sat, 12 Jul 1997 06:24:02 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id GAA08059; Sat, 12 Jul 1997 06:22:44 -0700 (PDT) To: Michael Smith cc: asami@cs.berkeley.edu, torstenb@ramsey.tb.9715.org, current@FreeBSD.ORG, hans@brandinnovators.com Subject: Re: Heads up and and a call for a show of hands. In-reply-to: Your message of "Sat, 12 Jul 1997 22:44:33 +0930." <199707121314.WAA28818@genesis.atrad.adelaide.edu.au> Date: Sat, 12 Jul 1997 06:22:38 -0700 Message-ID: <8050.868713758@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > No good. I want to run startups in /usr/local, but only ldconfig in > /usr/X11R6, or vice versa. If you want to do this, the only way that works > is to explicitly enumerate both sets of paths : > > local_loadpath="..." > local_startups="..." Hmmmmm. > My personal take on the ldconfig situation : ldconfig should have an > internal set of default paths (initiallt just /usr/lib), which can be > manually inhibited on the commandline if required, it should support > /etc/ld.so.conf by reading it if it exists, and it should take paths on > the commandline. > > As for whether /etc/ld.so.conf should override the inbuilt search > path, the obvious answer is _no_; there is a perfectly good control > for this on the commandline. Yeesh - then by that logic, I guess, I should just throw all of the existing _LDC munging stuff in rc and just make an ldconfig_flags variable which you can set to whatever you want. :-) Jordan From owner-freebsd-current Sat Jul 12 06:40:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA05355 for current-outgoing; Sat, 12 Jul 1997 06:40:27 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA05350 for ; Sat, 12 Jul 1997 06:40:21 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id XAA28883; Sat, 12 Jul 1997 23:10:00 +0930 (CST) From: Michael Smith Message-Id: <199707121340.XAA28883@genesis.atrad.adelaide.edu.au> Subject: Re: Heads up and and a call for a show of hands. In-Reply-To: <8050.868713758@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 12, 97 06:22:38 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sat, 12 Jul 1997 23:10:00 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, asami@cs.berkeley.edu, torstenb@ramsey.tb.9715.org, current@FreeBSD.ORG, hans@brandinnovators.com X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > Yeesh - then by that logic, I guess, I should just throw all of the > existing _LDC munging stuff in rc and just make an ldconfig_flags > variable which you can set to whatever you want. :-) Perhaps; I still see two separate items there; "other" places to search, and whether the default path should be searched. I'd probably default the local_loadpath to /usr/X11R6/lib, /usr/local/lib, to cover the most "normal" cases, and conditionalise the '-s' flag on a libpath_default=YES/NO option. All IMHO, of course 8) > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sat Jul 12 14:56:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA21471 for current-outgoing; Sat, 12 Jul 1997 14:56:06 -0700 (PDT) Received: from sage.tamis.com (tamis.com [206.24.116.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA21464 for ; Sat, 12 Jul 1997 14:56:03 -0700 (PDT) Received: (from daveh@localhost) by sage.tamis.com (8.8.5/8.6.12) id OAA08485; Sat, 12 Jul 1997 14:51:47 -0700 (PDT) Date: Sat, 12 Jul 1997 14:51:46 -0700 (PDT) From: David Holloway To: current@FreeBSD.ORG Subject: DEFCON In-Reply-To: <199707121340.XAA28883@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk DEFCON report: things are pretty informative here folks... lots of fun.. a few Feds, OpenBSD CDROMS being handed out... gotta go.. laterz -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i mQBtAzNlZLYAAAEDAMgNdZzjQLVUlL2iYYC5LXU7hGjB+NB6BPL5OyFM7/iAhhIo Z/u6VCQ9I3ly8c9kYwDcKoFCwn2qmEOFjiCDHdeGoUShtUD3UASm9j0yVlpUrzpS 8i8Rz9Ug1R1YtC9oEQAFEbQfRGF2aWQgSG9sbG93YXk8ZGF2ZWhAdGFtaXMuY29t PokAdQMFEDNlZLYg1R1YtC9oEQEBRJQC/3B3/CUirR2zTi/jxkU8vA1UtCiZXH1x oaUrSpeH3YDbV7zIRNBoIIgtncPgySACdH8+ikLAegfkImcYYqSDtu+y1qslYIAL XzTX9Wk6zE1k0JEPMkkKu8uLhx3Lk7Uscw== =8hwm -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-current Sat Jul 12 15:23:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA22547 for current-outgoing; Sat, 12 Jul 1997 15:23:49 -0700 (PDT) Received: from veda.is (veda.is [193.4.230.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA22542 for ; Sat, 12 Jul 1997 15:23:43 -0700 (PDT) Received: from ubiq.veda.is (ubiq.veda.is [193.4.230.60]) by veda.is (8.8.5/8.8.5) with ESMTP id WAA20508 for ; Sat, 12 Jul 1997 22:23:39 GMT From: Adam David Received: (from adam@localhost) by ubiq.veda.is (8.8.5/8.8.5) id WAA19538 for freebsd-current@freebsd.org; Sat, 12 Jul 1997 22:23:37 GMT Message-Id: <199707122223.WAA19538@ubiq.veda.is> Subject: upgrading jan-jul'97 To: freebsd-current@freebsd.org Date: Sat, 12 Jul 1997 22:23:36 +0000 (GMT) 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-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What caveats are there with upgrading a machine from January to July 1997 -current? Which specific pitfalls should I look out for to accommodate them in advance? -- Adam David From owner-freebsd-current Sat Jul 12 15:43:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA23339 for current-outgoing; Sat, 12 Jul 1997 15:43:09 -0700 (PDT) Received: from mail.MCESTATE.COM (vince@mail.MCESTATE.COM [207.211.200.50]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA23331 for ; Sat, 12 Jul 1997 15:43:05 -0700 (PDT) Received: from localhost (vince@localhost) by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id PAA21922; Sat, 12 Jul 1997 15:42:57 -0700 (PDT) Date: Sat, 12 Jul 1997 15:42:57 -0700 (PDT) From: Vincent Poy To: Adam David cc: freebsd-current@FreeBSD.ORG Subject: Re: upgrading jan-jul'97 In-Reply-To: <199707122223.WAA19538@ubiq.veda.is> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 12 Jul 1997, Adam David wrote: =)What caveats are there with upgrading a machine from January to July 1997 =)-current? Which specific pitfalls should I look out for to accommodate them =)in advance? I think you need to do a make all install in /usr/src/include before making world. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-current Sat Jul 12 16:42:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA24970 for current-outgoing; Sat, 12 Jul 1997 16:42:49 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca32-05.ix.netcom.com [199.35.209.69]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA24965 for ; Sat, 12 Jul 1997 16:42:45 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id QAA10120; Sat, 12 Jul 1997 16:42:27 -0700 (PDT) Date: Sat, 12 Jul 1997 16:42:27 -0700 (PDT) Message-Id: <199707122342.QAA10120@silvia.HIP.Berkeley.EDU> To: jkh@time.cdrom.com CC: torstenb@ramsey.tb.9715.org, current@FreeBSD.ORG, hans@brandinnovators.com In-reply-to: <7882.868710267@time.cdrom.com> (jkh@time.cdrom.com) Subject: Re: Heads up and and a call for a show of hands. From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * > The point is that, either way, there is an existing mechanism that can * > easily be used without a need for additional features added to * > ldconfig and/or /etc/rc. * * While this is true, I don't see it as an effective argument for * mandating only _one_ way of doing things. I see it that way. At least it effectively cancels the argument about "this makes life easier for vendors". * More to the point, I think that it's actually far more of a stretch to * have the local package startup mechanism setting the ldconfig path * than it is to have a specific mechanism for that purpose. I have no idea why you think it that way. This is just a simple application of a very generic mechanism. (Exactly the principle Unix is designed around, if you ask me. :) * I've had * users ask me why, for example, that "modula3 needed a daemon." It * doesn't, of course, but their confusion stems from the fact that * during boot, the user sees something like: * Local package initialization: apache m3 sshd * * And jumps to the obvious conclusion. Maybe the user needs to be educated? ;) Really, we can't help people from jumping to hasty conclusions, but does that matter? If we add a xfree86.sh script to delete old /tmp/.X0-lock files at startup, is that user going to ask why X needs a daemon? * /etc/ld.so.conf also appears in * other UN*X environments, it's hardly a BSD first, and a growing number * of admins are beginning to look there for override control. Our * ${prefix}/etc/rc.d hack is, by contrast, something very FreeBSD * specific. Which systems have it? I don't find it on our Solaris box. * local_dirs="/usr/local /usr/X11R6" # local hierarchies of importance. * local_startup=YES # NO to deactivate local scripts. : * and that gives you both an engineer's override and configurable, * vendor-editable files which follow the default ldpath. I'm sorry, that looks very much like an over-engineered bloat. Having too many ways to do a single thing can often lead to confusion. I also am not comfortable with third party software editing files in /etc -- that should be avoided unless really, really necessary (like /etc/shells). Am I the only one that is disturbed by the recent trend of behind-the-door negotiations with vendors followed by a commit followed by a big controversy? It seems like the vendors were not even properly reminded of our standard way of doing things. I'd hate to see unnecessary knobs and bells and whistles added to our system because some vendor can't be bothered to do even the minimal OS-specific customization. If someone else feels the same way, please speak up. Otherwise, I'll just slink back to my corner and close the rock behind me. ;) Satoshi From owner-freebsd-current Sat Jul 12 18:16:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27978 for current-outgoing; Sat, 12 Jul 1997 18:16:20 -0700 (PDT) Received: from pandora.hh.kew.com (ahd@kendra.ne.mediaone.net [24.128.53.73]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA27970 for ; Sat, 12 Jul 1997 18:16:10 -0700 (PDT) Received: (from ahd@localhost) by pandora.hh.kew.com (8.8.5/8.8.5) id VAA00821 for current@FreeBSD.ORG; Sat, 12 Jul 1997 21:16:08 -0400 (EDT) Date: Sat, 12 Jul 1997 21:16:08 -0400 (EDT) From: Drew Derbyshire Message-Id: <199707130116.VAA00821@pandora.hh.kew.com> To: current@FreeBSD.ORG Subject: ld.so.conf, comments, etc.... Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Stefan Esser > On Jul 11, "Jordan K. Hubbard" wrote: > > Should /etc/ld.so.conf be an _override_ or an _add on_ to > > the "detected" ldconfig path list? > > Are comments allowed in /etc/ld.so.conf ? > Assuming you ignore lines starting with a hash character, > you could use "#keep" to preserve the old list, and make > the upgrade procedure (which messes around with /etc/rc.* > anyway) merge the currently found rc.conf default into > the place of that comment, which will trigger the override > behaviour ... I dislike comments which are not _really_ comments, it pollutes the syntax of files in a very ugly fashion. To create an internal directive, use a unique character, not the comment character. On the particular topic, I agree with the don't make /usr/local/etc's ld.so.conf add to the master list. -ahd- -- Drew Derbyshire Internet: ahd@kew.com Kendra Electronic Wonderworks Telephone: 617-279-9812 "The world is full of compromise and infinite red tape . . ." From owner-freebsd-current Sat Jul 12 18:37:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA28775 for current-outgoing; Sat, 12 Jul 1997 18:37:34 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA28769 for ; Sat, 12 Jul 1997 18:37:30 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id SAA16163; Sat, 12 Jul 1997 18:36:28 -0700 (PDT) To: asami@cs.berkeley.edu (Satoshi Asami) cc: torstenb@ramsey.tb.9715.org, current@FreeBSD.ORG, hans@brandinnovators.com Subject: Re: Heads up and and a call for a show of hands. In-reply-to: Your message of "Sat, 12 Jul 1997 16:42:27 PDT." <199707122342.QAA10120@silvia.HIP.Berkeley.EDU> Date: Sat, 12 Jul 1997 18:36:28 -0700 Message-ID: <16159.868757788@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Which systems have it? I don't find it on our Solaris box. Well, it's in Linux and NetBSD, at least. > Am I the only one that is disturbed by the recent trend of > behind-the-door negotiations with vendors followed by a commit > followed by a big controversy? It seems like the vendors were not There are no black helicopters here, Satoshi, and I wish you'd stop flinging that accusation around. What you've seen as behind-the-door commits in these two occasions (/var/mail and ld.so.conf) are not the result of some secret vendor cabal, plotting to steal your precious bodily fluids while you sleep, they're the result of *ME* getting what I felt to be a reasonable request and then setting out to make what seemed, again to _me_, a very minimal and reasonable change in order to better support such needs. On these two occasions, the subsequent flame wars which erupted were characterised more by their heat than by their light, and as I don't have a lot of time for highly emotional arguments which serve no reasonable purpose other than to piss all over some feature without proposing a reasonable, concrete solution to the same problem, or are driven by what seems to be some greater need to harp endlessly on some diversionary topic of convenience rather than spending the energy more constructively working on real (and harder) problems, I basically switched off it after a few days. I will repeat: There was no secret conspiracy to get the features in, simply what I felt to be a reasonable and very low-overhead commit followed by lots of flaming and me switching the topic off in disgust. So far, the anticipated rash of break-ins and security holes has not accompanied the "dreaded /var/mail change", nor do I think that the ld.so.conf mechanism (modulo a few changes, since I agree that vendor editing of /etc/ld.so.conf is sub-optimal and I've been _trying_ to address that issue) will result in all the fire and brimstone raining from the skies that you predict. It's truly a feature that, if you don't want to use it, lets life goes on _exactly_ as before and no additional complexity in anyone's /etc has to result from this unless they specifically desire it. I think this is Poul-Henning's bike shelter scenario again (what was the name of the law in question again?). Everybody wants to argue about a change which results in no functional changes whatsoever if you don't want them, but nobody wants to debate why (for example) we've had broken mechanisms like DEVFS or LFS lurking in the system for so long without either fixing them or throwing them away so that a competing effort would and could be encouraged. Bah. Let it also be understood that I'm perfectly willing to back this one out if it seems that there's true concensus against it, but so far _most_ people have tended to indicate that _modification_ of the idea is what's warranted, not tossing it out completely. Jordan From owner-freebsd-current Sat Jul 12 18:58:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA29672 for current-outgoing; Sat, 12 Jul 1997 18:58:17 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA29667 for ; Sat, 12 Jul 1997 18:58:14 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA00777; Sun, 13 Jul 1997 11:27:59 +0930 (CST) From: Michael Smith Message-Id: <199707130157.LAA00777@genesis.atrad.adelaide.edu.au> Subject: Re: upgrading jan-jul'97 In-Reply-To: <199707122223.WAA19538@ubiq.veda.is> from Adam David at "Jul 12, 97 10:23:36 pm" To: adam@veda.is (Adam David) Date: Sun, 13 Jul 1997 11:27:58 +0930 (CST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Adam David stands accused of saying: > What caveats are there with upgrading a machine from January to July 1997 > -current? Which specific pitfalls should I look out for to accommodate them > in advance? About the only one I can think of is "make includes" before you start the build. > Adam David -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Sat Jul 12 20:41:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA03358 for current-outgoing; Sat, 12 Jul 1997 20:41:15 -0700 (PDT) Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA03353 for ; Sat, 12 Jul 1997 20:41:13 -0700 (PDT) Received: from lundin.abq.nm.us. (lundin.abq.nm.us [198.59.115.228]) by kitsune.swcp.com (8.8.5/1.2.3) with ESMTP id VAA04679; Sat, 12 Jul 1997 21:41:04 -0600 (MDT) Received: (from aflundi@localhost) by lundin.abq.nm.us. (8.8.5/8.8.5) id VAA04548; Sat, 12 Jul 1997 21:40:21 -0600 (MDT) Date: Sat, 12 Jul 1997 21:40:21 -0600 (MDT) From: Alan Lundin Message-Id: <199707130340.VAA04548@lundin.abq.nm.us.> In-Reply-To: "Richard Wackerbarth" "Re: Heads up and and a call for a show of hands." (Jul 11, 11:43am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Richard Wackerbarth" , "Jordan K. Hubbard" Subject: Re: Heads up and and a call for a show of hands. Cc: current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jul 11, 11:43am, "Richard Wackerbarth" wrote: > Subject: Re: Heads up and and a call for a show of hands. > > On Fri, Jul 11, 1997 10:16 AM, Jordan K. Hubbard > wrote: > > > Should /etc/ld.so.conf be an _override_ or an _add on_ to the "detected" > ldconfig path list? > [arguments omitted] > > Why not get both effects. Have two config files, for example, > /etc/ld.so.conf and /usr/local/etc/ld.so.conf. > [ ... ] Why not just source ld.so.conf if it exists then you can have either behavior depending on what is in ld.so.conf: /etc/rc [...] _LDC=/usr/lib if [ -d /usr/lib/compat ]; then _LDC="${_LDC} /usr/lib/compat" ; fi if [ -d /usr/X11R6/lib ]; then _LDC="${_LDC} /usr/X11R6/lib" ; fi if [ -d /usr/local/lib ]; then _LDC="${_LDC} /usr/local/lib" ; fi echo 'setting ldconfig path:' ${_LDC} if [ -f /etc/ld.so.conf ]; then . /etc/ld.so.conf fi ldconfig ${_LDC} [...] and ld.so.conf can contain something like ${_LDC}="${_LDC} /my/new/lib/dir" for append behavior or ${_LDC}="/usr/X11R6/lib /my/new/lib/dir /usr/local/lib" for override behavior. --alan From owner-freebsd-current Sat Jul 12 20:47:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA03531 for current-outgoing; Sat, 12 Jul 1997 20:47:34 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA03525 for ; Sat, 12 Jul 1997 20:47:30 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id UAA16603; Sat, 12 Jul 1997 20:44:34 -0700 (PDT) To: Alan Lundin cc: "Richard Wackerbarth" , current@FreeBSD.ORG Subject: Re: Heads up and and a call for a show of hands. In-reply-to: Your message of "Sat, 12 Jul 1997 21:40:21 MDT." <199707130340.VAA04548@lundin.abq.nm.us.> Date: Sat, 12 Jul 1997 20:44:34 -0700 Message-ID: <16599.868765474@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Why not just source ld.so.conf if it exists then you > can have either behavior depending on what is in ld.so.conf: That's certainly flexible, but something in me just recoils at the idea of writing ld.so.conf in terms of something which incestuously frobs another file's variable. :-) JOrdan From owner-freebsd-current Sat Jul 12 23:52:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA08532 for current-outgoing; Sat, 12 Jul 1997 23:52:23 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA08525 for ; Sat, 12 Jul 1997 23:52:20 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA04785 for freebsd-current@FreeBSD.ORG; Sun, 13 Jul 1997 08:51:54 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA15637; Sun, 13 Jul 1997 08:36:29 +0200 (MET DST) Message-ID: <19970713083629.KX46006@uriah.heep.sax.de> Date: Sun, 13 Jul 1997 08:36:29 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: upgrading jan-jul'97 References: <199707122223.WAA19538@ubiq.veda.is> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199707122223.WAA19538@ubiq.veda.is>; from Adam David on Jul 12, 1997 22:23:36 +0000 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Adam David wrote: > What caveats are there with upgrading a machine from January to July 1997 > -current? Which specific pitfalls should I look out for to accommodate them > in advance? Nothing in advance, but you might want to upgrade your /etc to the rc.conf paradigm afterwards. (I didn't do yet, but then, my system has never seen an /etc/sysconfig either, it basically runs the FreeBSD 1.1.5.1 rc scripts. :-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)