From owner-freebsd-current Sun Sep 29 00:54:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA17442 for current-outgoing; Sun, 29 Sep 1996 00:54:14 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA17330; Sun, 29 Sep 1996 00:54:06 -0700 (PDT) Received: by sovcom.kiae.su id AA04402 (5.65.kiae-1 ); Sun, 29 Sep 1996 10:53:59 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 29 Sep 96 10:53:59 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id KAA00496; Sun, 29 Sep 1996 10:53:10 +0300 (MSK) Message-Id: <199609290753.KAA00496@nagual.ru> Subject: Warning: dangerous SCSI option: AHC_SCBPAGING_ENABLE To: current@freebsd.org (FreeBSD-current), scsi@freebsd.org Date: Sun, 29 Sep 1996 10:53:10 +0300 (MSK) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL26 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Recently I got bad experience, the story is: I have AHC_SCBPAGING_ENABLE and one SCSI-2 disk, it works right for a long time. When I add second SCSI-2 disk, this option almost immediately seriously damage my root filesystem on _first_ disk with diagnostic: data overrun of bytes detected. Forcing a retry. When I resurrect my root filesystem and remove this option, all works right with two disks. BTW, AHC_TAGENABLE option works right in both cases. Details: ahc0: at 0x1c00-0x1cff irq 11 on eisa0 slot 1 ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4 SCBs ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "CONNER CFP1060S 1.05GB 2135" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1013MB (2074880 512 byte sectors) ^^^^^^^^^^^^^^^^ first disk ahc0: target 1 Tagged Queuing Device (ahc0:1:0): "IBM DORS-32160 S84A" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2063MB (4226725 512 byte sectors) ^^^^^^^^^^^^^^^^ second disk -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sun Sep 29 01:28:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA08921 for current-outgoing; Sun, 29 Sep 1996 01:28:18 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA08892; Sun, 29 Sep 1996 01:28:15 -0700 (PDT) Message-Id: <199609290828.BAA08892@freefall.freebsd.org> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) cc: current@freebsd.org (FreeBSD-current), scsi@freebsd.org Subject: Re: Warning: dangerous SCSI option: AHC_SCBPAGING_ENABLE In-reply-to: Your message of "Sun, 29 Sep 1996 10:53:10 +0300." <199609290753.KAA00496@nagual.ru> Date: Sun, 29 Sep 1996 01:28:15 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Its been stated several times on -current that SCBPAGING is a bad idea right now. This is old news. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Sep 29 01:41:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA16509 for current-outgoing; Sun, 29 Sep 1996 01:41:50 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA16364; Sun, 29 Sep 1996 01:41:33 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.6/BSD4.4) id SAA13277 Sun, 29 Sep 1996 18:41:12 +1000 (EST) From: michael butler Message-Id: <199609290841.SAA13277@asstdc.scgt.oz.au> Subject: Re: Warning: dangerous SCSI option: AHC_SCBPAGING_ENABLE To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Sun, 29 Sep 1996 18:41:11 +1000 (EST) Cc: current@freebsd.org, scsi@freebsd.org In-Reply-To: <199609290753.KAA00496@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Sep 29, 96 10:53:10 am X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Recently I got bad experience, the story is: > I have AHC_SCBPAGING_ENABLE and one SCSI-2 disk, it works right > for a long time. When I add second SCSI-2 disk, this option almost > immediately seriously damage my root filesystem on _first_ > disk with diagnostic: > data overrun of bytes detected. Forcing a retry. That's odd .. it's (almost) the same as the driver in -stable and .. FreeBSD 2.1.5-STABLE #2: Sun Sep 22 03:52:24 EST 1996 root@asstdc.scgt.oz.au:/usr/src/sys/compile/ASSTDC CPU: i486DX (486-class CPU) real memory = 67108864 (65536K bytes) avail memory = 64208896 (62704K bytes) ahc0: at 0x1c00-0x1cff irq 11 on isa ahc0: aic7770 <= Rev C, Single Channel, SCSI Id=7, 4 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "MICROP 2217-15MZ1001904 HQ30" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 1685MB (3450902 512 byte sectors) (ahc0:1:0): "MAXTOR LXT-340S 6.57" type 0 fixed SCSI 1 sd1(ahc0:1:0): Direct-Access 324MB (665154 512 byte sectors) (ahc0:2:0): "ARCHIVE VIPER 150 21247 -005" type 1 removable SCSI 1 st0(ahc0:2:0): Sequential-Access st0: Archive Viper 150 is a known rogue density code 0x0, drive empty ahc0: target 3 Tagged Queuing Device (ahc0:3:0): "Quantum XP34300 81HB" type 0 fixed SCSI 2 sd2(ahc0:3:0): Direct-Access 4101MB (8399520 512 byte sectors) .. this kernel is compiled with both AHC_TAGENABLE and AHC_SCBPAGING_ENABLE (not that there's much to page :-() and has been rock-solid with ~130,000 news articles/day .. 0 = active, 1 = overview and 3 = spool .. Has something changed recently ? michael From owner-freebsd-current Sun Sep 29 03:19:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA16993 for current-outgoing; Sun, 29 Sep 1996 03:19:28 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA16849; Sun, 29 Sep 1996 03:19:15 -0700 (PDT) Received: by sovcom.kiae.su id AA29250 (5.65.kiae-1 ); Sun, 29 Sep 1996 13:05:31 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 29 Sep 96 13:05:31 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id NAA00787; Sun, 29 Sep 1996 13:05:49 +0300 (MSK) Message-Id: <199609291005.NAA00787@nagual.ru> Subject: Re: Warning: dangerous SCSI option: AHC_SCBPAGING_ENABLE In-Reply-To: <199609290828.BAA08892@freefall.freebsd.org> from "Justin T. Gibbs" at "Sep 29, 96 01:28:15 am" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sun, 29 Sep 1996 13:05:48 +0300 (MSK) Cc: current@FreeBSD.org, scsi@FreeBSD.org From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL26 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Its been stated several times on -current that SCBPAGING is a > bad idea right now. This is old news. It looks strange for me, because it work very well with one drive... Could you please add some warning (maybe in LINT?) about very experimental nature of this option? -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sun Sep 29 03:27:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA22445 for current-outgoing; Sun, 29 Sep 1996 03:27:54 -0700 (PDT) Received: from sequent.kiae.su (sequent.kiae.su [193.125.152.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA22328; Sun, 29 Sep 1996 03:27:43 -0700 (PDT) Received: by sequent.kiae.su id AA12613 (5.65.kiae-2 ); Sun, 29 Sep 1996 14:21:01 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Sun, 29 Sep 96 14:21:00 +0400 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id NAA00814; Sun, 29 Sep 1996 13:08:34 +0300 (MSK) Message-Id: <199609291008.NAA00814@nagual.ru> Subject: Re: Warning: dangerous SCSI option: AHC_SCBPAGING_ENABLE In-Reply-To: <199609290841.SAA13277@asstdc.scgt.oz.au> from "michael butler" at "Sep 29, 96 06:41:11 pm" To: imb@scgt.oz.au (michael butler) Date: Sun, 29 Sep 1996 13:08:33 +0300 (MSK) Cc: current@freebsd.org, scsi@freebsd.org From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL26 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Recently I got bad experience, the story is: > > I have AHC_SCBPAGING_ENABLE and one SCSI-2 disk, it works right > > for a long time. When I add second SCSI-2 disk, this option almost > > immediately seriously damage my root filesystem on _first_ > > disk with diagnostic: > > > data overrun of bytes detected. Forcing a retry. > > That's odd .. it's (almost) the same as the driver in -stable and .. I got this diagnostic each boot time (in early rc stage) while I have this option, and all begin to work well when I remove this option, so it is definitely this thing. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sun Sep 29 03:28:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA23046 for current-outgoing; Sun, 29 Sep 1996 03:28:44 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA22987 for ; Sun, 29 Sep 1996 03:28:37 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id LAA09816 for ; Sun, 29 Sep 1996 11:28:55 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id LAA29653 for freebsd-current@freefall.cdrom.com; Sun, 29 Sep 1996 11:35:15 +0100 Date: Sun, 29 Sep 1996 11:35:15 +0100 From: Christoph Kukulies Message-Id: <199609291035.LAA29653@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: kernel build very 'noisy' Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk T_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../kern/sysv_msg.c ../../kern/sysv_msg.c: In function `msginit': ../../kern/sysv_msg.c:66: warning: unused parameter `dummy' ../../kern/sysv_msg.c: In function `msgsys': ../../kern/sysv_msg.c:139: warning: comparison between signed and unsigned ../../kern/sysv_msg.c: In function `msgctl': ../../kern/sysv_msg.c:261: warning: comparison between signed and unsigned ../../kern/sysv_msg.c: In function `msgsnd': ../../kern/sysv_msg.c:678: warning: comparison between signed and unsigned ../../kern/sysv_msg.c: In function `msgrcv': ../../kern/sysv_msg.c:1003: warning: comparison between signed and unsigned or T_43 -DCD9660 -DMSDOSFS -DNFS -DFFS -DINET -DKERNEL ../../miscfs/procfs/procfs_vnops.c ../../miscfs/procfs/procfs_vnops.c: In function `procfs_ioctl': ../../miscfs/procfs/procfs_vnops.c:177: warning: unused parameter `ap' ../../miscfs/procfs/procfs_vnops.c: In function `procfs_setattr': ../../miscfs/procfs/procfs_vnops.c:458: warning: unused parameter `ap' ../../miscfs/procfs/procfs_vnops.c: In function `procfs_lookup': ../../miscfs/procfs/procfs_vnops.c:603: warning: comparison between signed and unsigned ../../miscfs/procfs/procfs_vnops.c: In function `procfs_readdir': ../../miscfs/procfs/procfs_vnops.c:677: warning: comparison between signed and unsigned ../../miscfs/procfs/procfs_vnops.c:701: warning: comparison between signed and unsigned ../../miscfs/procfs/procfs_vnops.c:704: warning: comparison between signed and unsigned ../../miscfs/procfs/procfs_vnops.c:750: warning: comparison between signed and unsigned to name some. I'm building a new kernel at present and I never saw kernel builds spitting out that many warnings on unused variables, pointer comparisons --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Sun Sep 29 03:45:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA03972 for current-outgoing; Sun, 29 Sep 1996 03:45:19 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA03941 for ; Sun, 29 Sep 1996 03:45:16 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id DAA16613; Sun, 29 Sep 1996 03:45:02 -0700 (PDT) To: Christoph Kukulies cc: freebsd-current@freefall.freebsd.org Subject: Re: kernel build very 'noisy' In-reply-to: Your message of "Sun, 29 Sep 1996 11:35:15 BST." <199609291035.LAA29653@gilberto.physik.rwth-aachen.de> Date: Sun, 29 Sep 1996 03:45:01 -0700 Message-ID: <16611.843993901@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm building a new kernel at present and I never saw kernel builds > spitting out that many warnings on unused variables, pointer comparisons You must not be following -current postings very carefully. ;-) This is a direct result of going to gcc 2.7.2, and something quite a few folks have been commenting on since we switched over. I expect that, in time, these warnings will be eradicated just as they were for 2.6.3. Jordan From owner-freebsd-current Sun Sep 29 04:03:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA13203 for current-outgoing; Sun, 29 Sep 1996 04:03:31 -0700 (PDT) Received: from methan.chemie.fu-berlin.de (methan.chemie.fu-berlin.de [160.45.22.81]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA13146 for ; Sun, 29 Sep 1996 04:03:23 -0700 (PDT) Received: by methan.chemie.fu-berlin.de (Smail3.1.29.1) from uriela.in-berlin.de (192.109.42.147) with smtp id ; Sun, 29 Sep 96 13:03 MET DST Received: by uriela.in-berlin.de (/\oo/\ Smail3.1.29.1 #29.8) id ; Sun, 29 Sep 96 12:03 MET Received: from dva.in-berlin.de by never.never.mind.de with uucp (Smail3.1.28.1 #1) id m0v7Jfs-000EomC; Sun, 29 Sep 96 13:04 MET DST Received: by dva.in-berlin.de id m0v7Jd3-000GPkC; Sun, 29 Sep 96 13:01 MET DST (/\oo/\ Smail3.1.29.1 #29.1) Message-Id: From: balu@dva.in-berlin.de (Boris Staeblow) Subject: Problems with login except root To: freebsd-current@freebsd.org Date: Sun, 29 Sep 1996 13:01:45 +0200 (MET DST) 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 Hi.. I've some problems with my second machine. It's now very-current. There are no problems before with the same configuration. All programs are running well except ALL other userlogins and suid-other-than-root programs (like man(1)): [root@reido] /u2/root {ttyp0}:su news su: /bin/sh: Permission denied [root@reido] /u2/root {ttyp0}:telnet reido login: news Password: Last login: Sun Sep 29 12:23:29 from localhost Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. login: /bin/sh: Permission denied Connection closed by foreign host. [root@reido] /u2/root {ttyp0}:man Couldn't open /usr/libexec/ld.so. The permissions are ok: 1 drwxr-xr-x 18 root wheel 512 Apr 28 10:36 usr/ 1 drwxr-xr-x 5 bin bin 1024 Sep 29 12:02 libexec/ 68 -r-xr-xr-x 1 bin bin 65536 Sep 28 18:11 ld.so* 1 drwxr-xr-x 2 bin bin 512 Sep 28 22:03 bin/ 324 -r-xr-xr-x 1 bin bin 327680 Sep 28 22:03 sh* /etc/shells: /bin/sh /bin/csh /usr/local/bin/tcsh /usr/local/bin/bash ------------------------------------------- Can anyone tell me what i've overlooked or what may be the problem? ALL is compiled new - and my first machine with the same sourcetree don't have such problems.. :-/ Boris -- balu@dva.in-berlin.de Boris Staeblow From owner-freebsd-current Sun Sep 29 04:13:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA18489 for current-outgoing; Sun, 29 Sep 1996 04:13:57 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA18404; Sun, 29 Sep 1996 04:13:45 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id MAA11946; Sun, 29 Sep 1996 12:00:38 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.6/8.7.3) with ESMTP id MAA00266; Sun, 29 Sep 1996 12:58:07 +0200 (MET DST) Date: Sun, 29 Sep 1996 12:58:07 +0200 (MET DST) From: Andreas Klemm To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= cc: FreeBSD-current , scsi@freebsd.org Subject: Re: Warning: dangerous SCSI option: AHC_SCBPAGING_ENABLE In-Reply-To: <199609290753.KAA00496@nagual.ru> Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 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 On Sun, 29 Sep 1996, [KOI8-R] áÎÄÒÅÊ þÅÒÎÏ× wrote: > Recently I got bad experience, the story is: > I have AHC_SCBPAGING_ENABLE and one SCSI-2 disk, it works right > for a long time. When I add second SCSI-2 disk, this option almost > immediately seriously damage my root filesystem on _first_ > disk with diagnostic: > > data overrun of bytes detected. Forcing a retry. > > When I resurrect my root filesystem and remove this option, all > works right with two disks. > > BTW, AHC_TAGENABLE option works right in both cases. Puh, I disabled this option last recently because of my hangups ;) But I don't want to say that this was causing the hangups ... Difficult to say. -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Sun Sep 29 04:50:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA10136 for current-outgoing; Sun, 29 Sep 1996 04:50:11 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA10089 for ; Sun, 29 Sep 1996 04:50:07 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id MAA10094; Sun, 29 Sep 1996 12:50:22 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id MAA29886; Sun, 29 Sep 1996 12:56:43 +0100 Message-Id: <199609291156.MAA29886@gilberto.physik.rwth-aachen.de> Date: Sun, 29 Sep 1996 12:56:42 +0100 From: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies), freebsd-current@freefall.freebsd.org Subject: Re: kernel build very 'noisy' In-Reply-To: <16611.843993901@time.cdrom.com>; from Jordan K. Hubbard on Sep 29, 1996 03:45:01 -0700 References: <16611.843993901@time.cdrom.com> X-Mailer: Mutt 0.45 Mime-Version: 1.0 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard writes: > > I'm building a new kernel at present and I never saw kernel builds > > spitting out that many warnings on unused variables, pointer comparisons > > You must not be following -current postings very carefully. ;-) I admit, I often pushed D)elete and only read by subject recently. Sorry for that. And thanks for the twinkle. > This is a direct result of going to gcc 2.7.2, and something > quite a few folks have been commenting on since we switched > over. > > I expect that, in time, these warnings will be eradicated just as they > were for 2.6.3. > > Jordan -- --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Sun Sep 29 04:52:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA11687 for current-outgoing; Sun, 29 Sep 1996 04:52:04 -0700 (PDT) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA11452; Sun, 29 Sep 1996 04:51:44 -0700 (PDT) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.7.6/BSD4.4) id VAA19822 Sun, 29 Sep 1996 21:51:06 +1000 (EST) From: michael butler Message-Id: <199609291151.VAA19822@asstdc.scgt.oz.au> Subject: Re: Warning: dangerous SCSI option: AHC_SCBPAGING_ENABLE To: ache@nagual.ru Date: Sun, 29 Sep 1996 21:51:06 +1000 (EST) Cc: current@freebsd.org, scsi@freebsd.org X-Mailer: ELM [version 2.4 PL24beta] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Recently I got bad experience, the story is: > > I have AHC_SCBPAGING_ENABLE and one SCSI-2 disk, it works right > > for a long time. I just remembered why I didn't have trouble on my news server .. 2842 revisions < 'E' don't get it enabled (news server has a rev 'C') and my web-server is rev >= 'E' but only has one drive, michael From owner-freebsd-current Sun Sep 29 06:22:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA28782 for current-outgoing; Sun, 29 Sep 1996 06:22:17 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA28414 for ; Sun, 29 Sep 1996 06:21:50 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA00849; Sun, 29 Sep 1996 15:21:33 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA28548; Sun, 29 Sep 1996 15:21:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id PAA07088; Sun, 29 Sep 1996 15:07:00 +0200 (MET DST) From: J Wunsch Message-Id: <199609291307.PAA07088@uriah.heep.sax.de> Subject: Re: Problems with login except root To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 29 Sep 1996 15:06:59 +0200 (MET DST) Cc: balu@dva.in-berlin.de (Boris Staeblow) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Boris Staeblow at "Sep 29, 96 01:01:45 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 As Boris Staeblow wrote: > login: /bin/sh: Permission denied > Connection closed by foreign host. > > [root@reido] /u2/root {ttyp0}:man > Couldn't open /usr/libexec/ld.so. > > > The permissions are ok: > > 1 drwxr-xr-x 18 root wheel 512 Apr 28 10:36 usr/ > 1 drwxr-xr-x 5 bin bin 1024 Sep 29 12:02 libexec/ > 68 -r-xr-xr-x 1 bin bin 65536 Sep 28 18:11 ld.so* > > > 1 drwxr-xr-x 2 bin bin 512 Sep 28 22:03 bin/ > 324 -r-xr-xr-x 1 bin bin 327680 Sep 28 22:03 sh* Have you screwed the permissions of your root directory? Have you screwed the permissions of the /usr _mount point_? (For the latter, you cannot actually see this, since it's now shadowed by the root dir of the /usr filesystem. But if the mount point within the root f/s has too restrictive permissions, you get something similar to the above, except that /bin/sh should not be affected.) -- 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 Sun Sep 29 07:57:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA06346 for current-outgoing; Sun, 29 Sep 1996 07:57:54 -0700 (PDT) Received: from spitfire.ecsel.psu.edu (spitfire.ecsel.psu.edu [146.186.218.51]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA06297 for ; Sun, 29 Sep 1996 07:57:47 -0700 (PDT) From: tenser@spitfire.ecsel.psu.edu Received: (qmail 4390 invoked by uid 1000); 29 Sep 1996 14:58:00 -0000 Date: 29 Sep 1996 14:58:00 -0000 Message-ID: <19960929145800.4389.qmail@spitfire.ecsel.psu.edu> To: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Subject: Qmail changes... I decided to set up Qmail on my new -current system down here, but found that mail(1) and from(1) break when not used with a centralized mail drop, ie /var/mail. Looking at the source, I saw that neither mail(1) nor from(1) honor the MAIL environment variable. Seeing no problem with this, since neither command is privaledged, I made the small modifications necessary to support ``MAIL''. Would someone please commit these the the source tree? Thanks! - Dan C. --- *** /usr/src/usr.bin/from/from.c 1996/09/29 01:40:35 1.1 --- /usr/src/usr.bin/from/from.c 1996/09/29 01:58:06 *************** *** 42,50 **** --- 42,52 ---- #endif /* not lint */ #include + #include #include #include + #include #include #include *************** *** 83,98 **** argv += optind; if (!file) { ! if (!(file = *argv)) { ! if (!(pwd = getpwuid(getuid()))) { ! fprintf(stderr, "from: no password file entry for you.\n"); ! exit(1); } - file = pwd->pw_name; } - (void)sprintf(buf, "%s/%s", _PATH_MAILDIR, file); - file = buf; } /* read from stdin */ --- 85,106 ---- argv += optind; if (!file) { ! if (*argv) { ! (void)sprintf(buf, "%s/%s", _PATH_MAILDIR, *argv); ! file = buf; ! } else { ! if (!(file = getenv("MAIL"))) { ! if (!(pwd = getpwuid(getuid()))) { ! (void)fprintf(stderr, "from: no password file entry for you.\n"); ! exit(1); ! } ! file = pwd->pw_name; ! (void)sprintf(buf, ! "%s/%s", _PATH_MAILDIR, file); ! file = buf; } } } /* read from stdin */ *** /usr/src/usr.bin/from/from.1 1996/09/29 01:58:15 1.1 --- /usr/src/usr.bin/from/from.1 1996/09/29 14:45:01 *************** *** 72,77 **** --- 72,82 ---- .Ar user Ns 's mailbox, is examined instead of the invoker's own mailbox. (Privileges are required.) + .Sh ENVIRONMENT + .Bl -tag -width Fl + .It Ev MAIL + If set, the location of the invoker's mailbox. Otherwise, the default + in /var/mail is used. .Sh FILES .Bl -tag -width /var/mail/* -compact .It Pa /var/mail/* *** /usr/src/usr.bin/mail/v7.local.c 1996/09/29 02:00:23 1.1 --- /usr/src/usr.bin/mail/v7.local.c 1996/09/29 02:03:41 *************** *** 55,61 **** findmail(user, buf) char *user, *buf; { ! (void)sprintf(buf, "%s/%s", _PATH_MAILDIR, user); } /* --- 55,66 ---- findmail(user, buf) char *user, *buf; { ! char *tmp = getenv("MAIL"); ! ! if (tmp == NULL) ! (void)sprintf(buf, "%s/%s", _PATH_MAILDIR, user); ! else ! (void)strcpy(buf, tmp); } /* *** /usr/src/usr.bin/mail/mail.1 1996/09/29 14:45:24 1.1 --- /usr/src/usr.bin/mail/mail.1 1996/09/29 14:47:59 *************** *** 30,36 **** .\" SUCH DAMAGE. .\" .\" @(#)mail.1 8.2 (Berkeley) 12/30/93 ! .\" $Id: mail.1,v 1.1 1996/09/29 14:45:24 tenser Exp $ .\" .Dd December 30, 1993 .Dt MAIL 1 --- 30,36 ---- .\" SUCH DAMAGE. .\" .\" @(#)mail.1 8.2 (Berkeley) 12/30/93 ! .\" $Id: mail.1,v 1.2 1996/09/29 14:47:58 tenser Exp $ .\" .Dd December 30, 1993 .Dt MAIL 1 *************** *** 985,991 **** .Ev HOME and .Ev USER ! environment variables. .Sh FILES .Bl -tag -width /usr/share/misc/Mail.help* -compact .It Pa /var/mail/* --- 985,995 ---- .Ev HOME and .Ev USER ! environment variables. Also, if the ! .Ev MAIL ! environment variable is set, it is used as the ! location of the user's mailbox instead of the ! default in /var/mail. .Sh FILES .Bl -tag -width /usr/share/misc/Mail.help* -compact .It Pa /var/mail/* From owner-freebsd-current Sun Sep 29 09:07:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA12836 for current-outgoing; Sun, 29 Sep 1996 09:07:10 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA12820 for ; Sun, 29 Sep 1996 09:07:08 -0700 (PDT) Received: from omnivax (skynet.ctr.columbia.edu [128.59.64.70]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id JAA17852 for ; Sun, 29 Sep 1996 09:07:01 -0700 (PDT) Received: (from wpaul@localhost) by omnivax (8.6.12/8.6.9) id LAA10103; Sun, 29 Sep 1996 11:56:24 -0400 From: Bill Paul Message-Id: <199609291556.LAA10103@omnivax> Subject: Re: Re: Problems with mail-aliasing using NIS To: ccote@gandalf.ec.camitel.com (Claude Cote) Date: Sun, 29 Sep 1996 11:55:49 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: <199609290624.CAA06931@gandalf.ec.camitel.com> from "Claude Cote" at Sep 29, 96 02:24:27 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Claude Cote had to walk into mine and say: > Hi Bill, > > I'm very grateful for your help. Sorry for my bad English... it > sometimes makes me write things I don't really mean %-} So this time, > I'll try to make things a little more explicit. [chop] > > You don't need to reboot, just restart sendmail. This isn't Windoze, > > you know. > > Hopefully! > > I used to send signals, but since nothing was working, I decided to > reboot (to be sure that no esoteric forces was taking over the > machine ;-) Sendmail doesn't re-read /etc/sendmail.cf on a SIGHUP (when running in daemon mode); you actually have to kill -TERM it and restart it. [chop] > Oops! Here's the output of ypcat -k mail.aliases: > > ingres root > @ @ > bin root > postmaster root > webmaster root > mailer-daemon postmaster > nobody root > daemon root > toor root > games root > system root > uucp root > toto ccote Hm, okay: this looks correct. Since the map is formatted correctly and you can read it on the clients, I'm inclined to think the problem isn't stictly with NIS. > >> BTW, the NIS master server is running -current of last Monday (23 sep) > >> and the clients are running 2.2-960801-SNAP. All the others NIS databases > >> (passwd, group, hosts, ...) are working just fine. > > > > You must have compiled -current yourself: check that the latest > > /var/yp/Makefile was installed (it's in the source tree as > > I make a diff and it's the good one. Ok. [chop] > Cut from /usr/src/usr.sbin/sendmail/RELEASE_NOTES: > > Check for @:@ entry in NIS maps before starting up to avoid > (but not prevent, sigh) race conditions. This ought to > ... > Fix a problem that caused aliaswait to go into infinite recursion > if the @:@ metasymbol wasn't found in the alias file. Hunh. Never saw that one before. But then I don't use NIS for the aliases database on my system. > Here's the output of the above commands: > > NIS Map update started on Sun Sep 29 01:29:22 EDT 1996 for domain gandalf > Updating mail.aliases... > /etc/aliases: 12 aliases, longest 10 bytes, 131 bytes total > Pushed mail.aliases map. > NIS Map update completed. Hm... do you actually have an NIS slave server running? Normally, you should only see the 'Pushed %s map' message if you comment out the 'NOPUSH=True' line to enable propagation of maps to slave servers. One possibility here is that you do have a slave server, and the client is bound to it, but your map updates aren't being propagated to the slave properly. If you really do have slaves, did you remember to add them to the /var/yp/ypservers file? > Maybe something is missing on the client side? I will keep on working... I think it is something on the client. Like I said, if you have a slave server, and you aren't pushing map updates to it correctly, that could hose the client. Also, did you check that you enable NIS access to the mail.aliases map in the client's /etc/sendmail.cf file? Did you restart sendmail on the client machines as well as the server after you added NIS support to the config file? Can you confirm that sendmail on the client was really built with NIS map support? If you copy the sendmail binary from the server onto the clients, does that work? If you do % sendmail -bt > 3,0 toto does it resolve the alias correctly? If you can do % ypmatch toto mail.aliases and that works, but sendmail can't resolve the alias when you run it in test mode, then it could be your sendmail configuration. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you." ============================================================================= From owner-freebsd-current Sun Sep 29 09:09:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA14357 for current-outgoing; Sun, 29 Sep 1996 09:09:53 -0700 (PDT) Received: from methan.chemie.fu-berlin.de (methan.chemie.fu-berlin.de [160.45.22.81]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA14306 for ; Sun, 29 Sep 1996 09:09:47 -0700 (PDT) Received: by methan.chemie.fu-berlin.de (Smail3.1.29.1) from uriela.in-berlin.de (192.109.42.147) with smtp id ; Sun, 29 Sep 96 18:09 MET DST Received: by uriela.in-berlin.de (/\oo/\ Smail3.1.29.1 #29.8) id ; Sun, 29 Sep 96 17:09 MET Received: from dva.in-berlin.de by never.never.mind.de with uucp (Smail3.1.28.1 #1) id m0v7OSC-000EomC; Sun, 29 Sep 96 18:10 MET DST Received: by dva.in-berlin.de id m0v7OOJ-000GPkC; Sun, 29 Sep 96 18:06 MET DST (/\oo/\ Smail3.1.29.1 #29.1) Message-Id: From: balu@dva.in-berlin.de (Boris Staeblow) Subject: Re: Problems with login except root In-Reply-To: <199609291307.PAA07088@uriah.heep.sax.de> from J Wunsch at "Sep 29, 96 03:06:59 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 29 Sep 1996 18:06:51 +0200 (MET DST) Cc: freebsd-current@FreeBSD.org 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 J Wunsch writes: > As Boris Staeblow wrote: > > > login: /bin/sh: Permission denied > > Connection closed by foreign host. > > > > [root@reido] /u2/root {ttyp0}:man > > Couldn't open /usr/libexec/ld.so. > > The permissions are ok: [...] > Have you screwed the permissions of your root directory? Uhhh, yes! (I've extracted a tar in the root -> drwx------ ) I've checked all perms - except root.. :-) Thanks for your hint! Boris. -- balu@dva.in-berlin.de Boris Staeblow From owner-freebsd-current Sun Sep 29 10:19:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA22527 for current-outgoing; Sun, 29 Sep 1996 10:19:08 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA22503; Sun, 29 Sep 1996 10:19:05 -0700 (PDT) Message-Id: <199609291719.KAA22503@freefall.freebsd.org> To: michael butler cc: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=), current@freebsd.org, scsi@freebsd.org Subject: Re: Warning: dangerous SCSI option: AHC_SCBPAGING_ENABLE In-reply-to: Your message of "Sun, 29 Sep 1996 18:41:11 +1000." <199609290841.SAA13277@asstdc.scgt.oz.au> Date: Sun, 29 Sep 1996 10:19:04 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >ahc0: aic7770 <= Rev C, Single Channel, SCSI Id=7, 4 SCBs Rev C adapters cannot do paging. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Sep 29 14:28:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA02501 for current-outgoing; Sun, 29 Sep 1996 14:28:59 -0700 (PDT) Received: from ns.eu.org (valerian.glou.eu.org [193.56.58.251]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA02377 for ; Sun, 29 Sep 1996 14:28:46 -0700 (PDT) Received: (from uucp@localhost) by ns.eu.org (8.7.3/8.7.1/951117) with UUCP id XAA26845 for current@freebsd.org; Sun, 29 Sep 1996 23:28:42 +0200 (MET DST) Received: (from regnauld@localhost) by tetard.glou.eu.org (8.7.6/8.7.3/tetard-uucp-2.7) id VAA03745 for current@freebsd.org; Sun, 29 Sep 1996 21:37:11 +0200 (MET DST) From: Philippe Regnauld Message-Id: <199609291937.VAA03745@tetard.glou.eu.org> Subject: Panic with syscons mouse support To: current@freebsd.org (current) Date: Sun, 29 Sep 1996 21:37:11 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL15 (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 Hi, I'm using a fairly-current (ctm 2230 / Sep 22), and the following happened some days ago: - activated moused (moused -t microsoft -p /dev/cuaa0) - activated the cursor: vidcontrol -m on *clunk* fault virtual address : 0xefed7000 fault code : supervisor write, page not present i.point: : 0x8:0xf01a771d stack point : 0x10:0xf01aaf7c frame pointer : 0x10:0xf01aaf84 code seg : base 0x0, limit 0xfffff type 0x1b dpl 0, pres 1, def 32, gran 1 proc eflags : interrupt enable resume, iopl=0 cur proc : idle ->ir mask : stopped at _remove_mouse_image +0x19 movw %ax,0(%ecx) Calling sync() got me another panic with _vget+0x8e movl 0x10(%edx), %eax Using VGA_80x30 mode with iso-thin-8x16.fnt. System is 486/120 w/32MB, NCR 810 SCSI and S3 968 Diamond. -- -- Phil -[ Philippe Regnauld / regnauld@eu.org / +55.4N +11.3E @ Sol3 / +45 31241690 ]- -[ "To kårve or nøt to kårve, that is the qvestion..." -- My sister ]- From owner-freebsd-current Sun Sep 29 15:07:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA27932 for current-outgoing; Sun, 29 Sep 1996 15:07:56 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA27181; Sun, 29 Sep 1996 15:06:22 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA04682; Sun, 29 Sep 1996 15:05:24 -0700 From: Terry Lambert Message-Id: <199609292205.PAA04682@phaeton.artisoft.com> Subject: Getting the OpenBSD tree To: current@freebsd.org Date: Sun, 29 Sep 1996 15:05:23 -0700 (MST) Cc: hackers@freebsd.org 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 Has anyone else tried to use the OpenBSD anoncvs server? Has anyone been successful? I keep getting errors... What environment/other settings did you use? What was your CVSROOT set to? What was your command line for the initial checkout? Thanks... 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 Sep 29 15:38:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA12505 for current-outgoing; Sun, 29 Sep 1996 15:38:07 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA11850; Sun, 29 Sep 1996 15:36:31 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id RAA00317; Sun, 29 Sep 1996 17:35:14 -0500 (EST) From: "John S. Dyson" Message-Id: <199609292235.RAA00317@dyson.iquest.net> Subject: Re: Getting the OpenBSD tree To: terry@lambert.org (Terry Lambert) Date: Sun, 29 Sep 1996 17:35:14 -0500 (EST) Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199609292205.PAA04682@phaeton.artisoft.com> from "Terry Lambert" at Sep 29, 96 03:05:23 pm Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24 ME8] 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 > Has anyone else tried to use the OpenBSD anoncvs server? > > Has anyone been successful? I keep getting errors... > > What environment/other settings did you use? > > What was your CVSROOT set to? > > What was your command line for the initial checkout? > > Thanks... > > It has worked for me (but I use the latest CVS, not necessarily the one in -current.) It is VERY VERY VERY slow. John From owner-freebsd-current Sun Sep 29 17:05:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA02352 for current-outgoing; Sun, 29 Sep 1996 17:05:49 -0700 (PDT) Received: from gallup.cia-g.com (root@gallup.cia-g.com [206.206.162.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA02307 for ; Sun, 29 Sep 1996 17:05:44 -0700 (PDT) Received: from localhost.my.domain (dialup17.gup.cia-g.com [206.206.162.49]) by gallup.cia-g.com (8.7.6/8.6.12) with SMTP id SAA14253; Sun, 29 Sep 1996 18:05:35 -0600 (MDT) Message-ID: X-Mailer: XFMail 0.4 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 29 Sep 1996 17:54:40 -0600 (MDT) From: George Simunovich To: flexfax@sgi.com Subject: DTR dropping for outgoing data call. Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello all, I'm having a problem with Hylafax V4.0pl0 and sharing a modem with outgoing calls. It seems that the DTR isn't being dropped when the program (cu and ppp) using the modem for outgoing data quits. System info: Basic Pentium System FreeBSD-2.2 current Hayes Optima business class modem Hylafax V4.0pl0 using "/dev/cuaa2" After starting all the Hylafax programs (faxq, hfaxd and faxgetty) I can run "cu -l /dev/cuaa2" and do whatever. After quitting cu with "~.", the DTR is not dropped (as seen by the TR light on the modem) and the modem stays connected. After waiting a few seconds it seems faxgetty starts going again and the DTR is dropped and faxgetty reinits the modem. So, if I run "cu -l /dev/cuaa2" and connect to somewhere, quit with "~." and then rerun "cu -l /dev/cuaa2" immediately, it will still be connected from the previous "cu". If I now exit the second "cu" with "~." the DTR is dropped and the modem disconnects. Now the dropping of the DTR works until faxgetty starts up again. Once faxgetty starts up again its back to square one. So, it seems to take a second program to open and close "/dev/cuaa2" for the DTR to drop. Even running something like "cu -l /dev/cuaa2;cat < /dev/null > /dev/cuaa2" will drop the DTR when the "cat" quits instead of the "cu". Everything else works. I can send and receive faxes and use the modem for outgoing and incoming data just fine. It just won't drop DTR after an outgoing data call. I have tried running faxgetty on "/dev/ttyd2" instead of "/dev/cuaa2". Sending and receiving faxes seem to work, but everything that tries to use "/dev/cuaa2" can't open it and reports a "Line Busy" error. Any ideas? Thanks, George ---------------------------------- George Simunovich From owner-freebsd-current Sun Sep 29 17:29:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA20603 for current-outgoing; Sun, 29 Sep 1996 17:29:02 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA18527; Sun, 29 Sep 1996 17:26:34 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.6/8.6.6) with ESMTP id SAA05822; Sun, 29 Sep 1996 18:25:11 -0600 (MDT) Message-Id: <199609300025.SAA05822@rover.village.org> To: dyson@FreeBSD.org Subject: Re: Getting the OpenBSD tree Cc: terry@lambert.org (Terry Lambert), current@FreeBSD.org In-reply-to: Your message of "Sun, 29 Sep 1996 17:35:14 CDT." <199609292235.RAA00317@dyson.iquest.net> References: <199609292235.RAA00317@dyson.iquest.net> Date: Sun, 29 Sep 1996 18:25:10 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199609292235.RAA00317@dyson.iquest.net> "John S. Dyson" writes: : It has worked for me (but I use the latest CVS, not necessarily : the one in -current.) It is VERY VERY VERY slow. Depending on which CVS server you are hitting, it can do that. I turn off all encryption and it seems to help quite a bit. This is, of course, over ssh. Warner From owner-freebsd-current Sun Sep 29 17:46:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04412 for current-outgoing; Sun, 29 Sep 1996 17:46:51 -0700 (PDT) Received: from gandalf.ec.camitel.com (174.ec.camitel.com [206.231.123.174]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA04332 for ; Sun, 29 Sep 1996 17:46:45 -0700 (PDT) Received: (from ccote@localhost) by gandalf.ec.camitel.com (8.7.6/8.7.3) id UAA01381; Sun, 29 Sep 1996 20:48:46 -0400 (EDT) Date: Sun, 29 Sep 1996 20:48:46 -0400 (EDT) Message-Id: <199609300048.UAA01381@gandalf.ec.camitel.com> From: Claude Cote To: wpaul@skynet.ctr.columbia.edu CC: current@freebsd.org Subject: Problems with mail-aliasing using NIS - Solved Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello Bill, Thanks for your hints! I've finally found the problem: it was sendmail. > Also, did you check that you enable NIS access to the mail.aliases > map in the client's /etc/sendmail.cf file? Did you restart sendmail > on the client machines as well as the server after you added NIS > support to the config file? Can you confirm that sendmail on the client > was really built with NIS map support? If you copy the sendmail binary > from the server onto the clients, does that work? If you do We can read this in /usr/src/usr.sbin/sendmail/src/READ_ME: NIS Define this to get NIS (YP) support for aliases and maps. Normally defined in the Makefile. but the option is NOT defined in the Makefile... and that's why it didn't work before. In short, to use mail-aliasing with NIS, we must do the following: 1) Add -DNIS in the DBMDEF line in the file /usr/src/usr.sbin/sendmail/src/Makefile and recompile sendmail; 2) Tell sendmail (in /etc/sendmail.cf) to use also NIS as alias file: # location of alias file O AliasFile=/etc/aliases,nis:mail.aliases 3) Restart sendmail. Et voila! Thanks VERY much!!! Claude From owner-freebsd-current Sun Sep 29 19:51:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA18188 for current-outgoing; Sun, 29 Sep 1996 19:51:38 -0700 (PDT) Received: from po7.andrew.cmu.edu (PO7.ANDREW.CMU.EDU [128.2.10.107]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA18165; Sun, 29 Sep 1996 19:51:32 -0700 (PDT) Received: (from postman@localhost) by po7.andrew.cmu.edu (8.7.5/8.7.3) id WAA16553; Sun, 29 Sep 1996 22:51:25 -0400 Received: via switchmail; Sun, 29 Sep 1996 22:51:25 -0400 (EDT) Received: from unix28.andrew.cmu.edu via qmail ID ; Sun, 29 Sep 1996 22:51:06 -0400 (EDT) Received: from unix28.andrew.cmu.edu via qmail ID ; Sun, 29 Sep 1996 22:51:05 -0400 (EDT) Received: from mms.4.60.Jun.27.1996.03.09.33.hp700.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix28.andrew.cmu.edu.HP9000.777 via MS.5.6.unix28.andrew.cmu.edu.hp700; Sun, 29 Sep 1996 22:51:05 -0400 (EDT) Message-ID: <0mHnKN200YUf0jYEU0@andrew.cmu.edu> Date: Sun, 29 Sep 1996 22:51:05 -0400 (EDT) From: David G Garmire To: freebsd-questions@freebsd.org, current@freebsd.org, freebsd-current@freebsd.org Subject: ifconfig param for EtherPower SMC 8432 PCI ethernet card? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a EtherPower SMC 8432 PCI ethernet card, and I'm trying to install FreeBSD. I would like to know the extra parameters or flags that I need for ifconfig to recognize this card. Please reply via emails as I'm not subscribed to this list. Thx! /david -- David Garmire Carnegie Mellon University, Computer Science From owner-freebsd-current Mon Sep 30 03:47:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA16025 for current-outgoing; Mon, 30 Sep 1996 03:47:04 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA15958 for ; Mon, 30 Sep 1996 03:46:58 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id AAA19403 for ; Mon, 30 Sep 1996 00:05:46 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id IAA20326 for ; Mon, 30 Sep 1996 08:02:37 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id IAA02960 for freebsd-current@freefall.cdrom.com; Mon, 30 Sep 1996 08:08:48 +0100 Date: Mon, 30 Sep 1996 08:08:48 +0100 From: Christoph Kukulies Message-Id: <199609300708.IAA02960@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.freebsd.org Subject: wd0 interrupt timeout Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I brought 'blues' to -current of Sep 29 which was previously running some months old -current and it is the first time I see a wd interrupt timeout message wd0: interrupt timeout: wd0: status 58 error 0 The message was on the screen right at the end of the bootup log so it might be a peculiarity occuring only during startup. Otherwise I cannot say that the system (a 486DX2/66 VLB, 32MB, IDE dual controller, Mitsumi FX-001 CDROM) is unstable with any respect. I built a full world+kernel over the weekend. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Mon Sep 30 03:47:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA16265 for current-outgoing; Mon, 30 Sep 1996 03:47:24 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA16139 for ; Mon, 30 Sep 1996 03:47:12 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id XAA19335 for ; Sun, 29 Sep 1996 23:38:23 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id IAA16051; Mon, 30 Sep 1996 08:37:02 +0200 Message-Id: <199609300637.IAA16051@ra.dkuug.dk> Subject: Re: Panic with syscons mouse support To: regnauld@tetard.glou.eu.org (Philippe Regnauld) Date: Mon, 30 Sep 1996 08:37:02 +0200 (MET DST) Cc: current@FreeBSD.ORG In-Reply-To: <199609291937.VAA03745@tetard.glou.eu.org> from "Philippe Regnauld" at Sep 29, 96 09:37:11 pm From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Philippe Regnauld who wrote: > > Hi, > > I'm using a fairly-current (ctm 2230 / Sep 22), and the following > happened some days ago: > > - activated moused (moused -t microsoft -p /dev/cuaa0) > - activated the cursor: vidcontrol -m on > > *clunk* That sound is known to mee :) > Using VGA_80x30 mode with iso-thin-8x16.fnt. Thats the cue word, there is a problem with != 80x25 modes in some rare situations. I'm currently reworking parts of syscons mode- switching logic, that will cure the problem... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Mon Sep 30 05:10:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA23203 for current-outgoing; Mon, 30 Sep 1996 05:10:34 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA23149 for ; Mon, 30 Sep 1996 05:10:31 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id WAA16538 for current@freebsd.org; Mon, 30 Sep 1996 22:06:48 +1000 Date: Mon, 30 Sep 1996 22:06:48 +1000 From: Bruce Evans Message-Id: <199609301206.WAA16538@godzilla.zeta.org.au> To: current@freebsd.org Subject: Re: cvs commit: src/sys/i386/i386 userconfig.c Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Modified: sys/i386/i386 userconfig.c > Log: > Whaddya know, visual userconfig sort of supports pci, but the support > was always disabled because "pci.h" wasn't included. Now the configured > pci devices are listed and you can edit bogus flags for them. This causes a panic if bogus flags are changed and saved. It seems OK otherwise. Bruce From owner-freebsd-current Mon Sep 30 05:47:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA24333 for current-outgoing; Mon, 30 Sep 1996 05:47:55 -0700 (PDT) Received: from hq.icb.chel.su (hq.icb.chel.su [193.125.10.33]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA24095 for ; Mon, 30 Sep 1996 05:47:40 -0700 (PDT) Received: (babkin@localhost) by hq.icb.chel.su (8.7.5/8.6.5) id SAA18814 for current@freebsd.org; Mon, 30 Sep 1996 18:51:09 +0600 (GMT+0600) From: "Serge A. Babkin" Message-Id: <199609301251.SAA18814@hq.icb.chel.su> Subject: How to correct timezone ? To: current@freebsd.org Date: Mon, 30 Sep 1996 17:51:09 +0500 (ESK) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! The russian government has made a surprize. It changed the day of dayligth saving to normal time change from last sunday of september to the last sunday of october. The question is how to change the timezone description ? I have added the line to /usr/src/share/zoneinfo/europe that described the change and changed the line describing the previous years daylight saving time to limit its effect by 1995 year. Then I made make make install It recreated the /usr/share/zoneinfo directory, then I copied the Yekaterinburg zone (in Asia subdirectory though it is in the europe source file) to /etc/localtime. No effect. Tried stand/sysinstall to change the time zone. Rebooted as recommended. No effect. Whad did I wrong ? I'm running 2.0.5 by the way. Thank you in advance! -SB From owner-freebsd-current Mon Sep 30 07:43:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA21138 for current-outgoing; Mon, 30 Sep 1996 07:43:16 -0700 (PDT) Received: from mailsrv2.zib.de (mailsrv2.zib.de [130.73.108.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA21069 for ; Mon, 30 Sep 1996 07:43:05 -0700 (PDT) Received: from softs11.zib.de by mailsrv2.zib.de (SMI-8.6/SMI-SVR4) id QAA06049; Mon, 30 Sep 1996 16:39:30 +0200 Received: from soft13.zib.de by softs11.zib.de (SMI-8.6/SMI-SVR4) id QAA25885; Mon, 30 Sep 1996 16:39:31 +0200 Received: by soft13.zib.de (SMI-8.6/SMI-SVR4) id QAA00589; Mon, 30 Sep 1996 16:39:26 +0200 Date: Mon, 30 Sep 1996 16:39:26 +0200 From: schneider@zib.de (Wolfram Schneider) Message-Id: <199609301439.QAA00589@soft13.zib.de> To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Getting the OpenBSD tree In-Reply-To: <199609292205.PAA04682@phaeton.artisoft.com> References: <199609292205.PAA04682@phaeton.artisoft.com> 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 Terry Lambert writes: >Has anyone else tried to use the OpenBSD anoncvs server? >Has anyone been successful? I keep getting errors... >What environment/other settings did you use? >What was your CVSROOT set to? >What was your command line for the initial checkout? $ export CVSROOT=anoncvs@anoncvs.no.openbsd.org:/cvs $ time cvs co src/bin/cp cvs server: Updating src/bin/cp U src/bin/cp/Makefile U src/bin/cp/cp.1 U src/bin/cp/cp.c U src/bin/cp/extern.h U src/bin/cp/utils.c real 14.0 user 0.1 sys 0.4 $ cvs -v Concurrent Versions System (CVS) 1.7 (client/server) PS: OpenBSD is available with CTM, see ftp.cs.tu-berlin.de:/pub/bsd/CTM/OpenBSD --Wolfram From owner-freebsd-current Mon Sep 30 12:10:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA25265 for current-outgoing; Mon, 30 Sep 1996 12:10:18 -0700 (PDT) Received: from alpo.whistle.com ([207.76.204.16]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA25189; Mon, 30 Sep 1996 12:10:10 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id MAA19774; Mon, 30 Sep 1996 12:09:12 -0700 (PDT) Message-ID: <32501A69.167EB0E7@whistle.com> Date: Mon, 30 Sep 1996 12:07:21 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: dyson@freebsd.org, current@freebsd.org Subject: Invalid wire count [panic] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm seeing this pretty often on a bunch of machines. it's reproducible to some extent. it seems to be related to either mounting extra filesystems, or unpacking a large tar file. I can try get more info later today Poul, I believe this is what you saw on your 4MB machine? julian From owner-freebsd-current Mon Sep 30 12:40:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA19548 for current-outgoing; Mon, 30 Sep 1996 12:40:05 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA19452; Mon, 30 Sep 1996 12:39:58 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id VAA09141; Mon, 30 Sep 1996 21:39:29 +0200 (MET DST) To: Julian Elischer cc: dyson@freebsd.org, current@freebsd.org Subject: Re: Invalid wire count [panic] In-reply-to: Your message of "Mon, 30 Sep 1996 12:07:21 PDT." <32501A69.167EB0E7@whistle.com> Date: Mon, 30 Sep 1996 21:39:28 +0200 Message-ID: <9139.844112368@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <32501A69.167EB0E7@whistle.com>, Julian Elischer writes: > >Poul, I believe this is what you saw on your 4MB machine? I belive John has it trapped in his sandbox. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Sep 30 18:06:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA08216 for current-outgoing; Mon, 30 Sep 1996 18:06:54 -0700 (PDT) Received: from red.jnx.com (red.jnx.com [208.197.169.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA08146 for ; Mon, 30 Sep 1996 18:06:47 -0700 (PDT) Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.7.6/8.7.3) with ESMTP id SAA01424 for ; Mon, 30 Sep 1996 18:06:13 -0700 (PDT) Received: (from pst@localhost) by base.jnx.com (8.7.5/8.7.3) id SAA00660 for current@freebsd.org; Mon, 30 Sep 1996 18:06:13 -0700 (PDT) Date: Mon, 30 Sep 1996 18:06:13 -0700 (PDT) From: Paul Traina Message-Id: <199610010106.SAA00660@base.jnx.com> To: current@freebsd.org Subject: gdb port testing... gdb-4.16 to move into /usr/src soon... Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Folks, If you're at all concerned about the fact that I will be upgrading our GDB to GDB v4.16 with a completely revised set of FreeBSD changes, then I strongly suggest that you test out the gdb "port" NOW. I'd like people to report bugs *before* we dump this on everyone in -current. Paul From owner-freebsd-current Mon Sep 30 18:07:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA08671 for current-outgoing; Mon, 30 Sep 1996 18:07:35 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-44.ut.nl.ibm.net [139.92.42.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA08551 for ; Mon, 30 Sep 1996 18:07:26 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id WAA13975 for ; Mon, 30 Sep 1996 22:00:34 +0100 (MET) Message-Id: <199609302100.WAA13975@vector.jhs.no_domain> Date: Mon, 30 Sep 1996 22:00:32 +0100 From: "Julian H. Stacey" Subject: Re: DTR dropping for outgoing data call. To: undisclosed-recipients:; Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk ------- Blind-Carbon-Copy To: George Simunovich cc: hylafax@freebsd.org Subject: Re: DTR dropping for outgoing data call. From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ In-reply-to: Your message of "Sun, 29 Sep 1996 17:54:40 CST." Date: Mon, 30 Sep 1996 22:00:32 +0100 Sender: jhs@vector.jhs.no_domain Hi, Reference: > From: George Simunovich > Subject: Re: DTR dropping for outgoing data call. > Date: Sun, 29 Sep 1996 17:54:40 -0600 (MDT) > Message-id: > > > Hello all, > > I'm having a problem with Hylafax V4.0pl0 and sharing a modem with We have a mailing list dedicated for hylafax on freebsd hylafax@freebsd.org so I'm copying this mail in entirety over to that list as To: George Simunovich cc: hylafax@freebsd.org bcc: current@freebsd.org & would request follow up occurs on hylafax@ rather than current@freebsd.org Thanks. > outgoing calls. It seems that the DTR isn't being dropped when the > program (cu and ppp) using the modem for outgoing data quits. > > System info: > > Basic Pentium System > FreeBSD-2.2 current > Hayes Optima business class modem > Hylafax V4.0pl0 using "/dev/cuaa2" > > > After starting all the Hylafax programs (faxq, hfaxd and faxgetty) I can > run "cu -l /dev/cuaa2" and do whatever. After quitting cu with "~.", the > DTR is not dropped (as seen by the TR light on the modem) and the > modem stays connected. After waiting a few seconds it seems faxgetty > starts going again and the DTR is dropped and faxgetty reinits the modem. > > So, if I run "cu -l /dev/cuaa2" and connect to somewhere, quit with > "~." and then rerun "cu -l /dev/cuaa2" immediately, it will still be > connected from the previous "cu". If I now exit the second "cu" with > "~." the DTR is dropped and the modem disconnects. Now the dropping of > the DTR works until faxgetty starts up again. Once faxgetty starts > up again its back to square one. > > So, it seems to take a second program to open and close "/dev/cuaa2" for > the DTR to drop. Even running something like "cu -l /dev/cuaa2;cat < > /dev/null > /dev/cuaa2" will drop the DTR when the "cat" quits instead of > the "cu". > > Everything else works. I can send and receive faxes and use the modem > for outgoing and incoming data just fine. It just won't drop DTR after > an outgoing data call. > > I have tried running faxgetty on "/dev/ttyd2" instead of "/dev/cuaa2". > Sending and receiving faxes seem to work, but everything that tries > to use "/dev/cuaa2" can't open it and reports a "Line Busy" error. > > Any ideas? > > Thanks, > > George > > > ---------------------------------- > George Simunovich > > Julian - -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ ------- End of Blind-Carbon-Copy From owner-freebsd-current Tue Oct 1 01:18:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA05829 for current-outgoing; Tue, 1 Oct 1996 01:18:51 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA05822; Tue, 1 Oct 1996 01:18:48 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id BAA29203; Tue, 1 Oct 1996 01:18:48 -0700 (PDT) To: bde@freebsd.org cc: current@freebsd.org Subject: Your UserConfig changes for unmasking PCI devices... Date: Tue, 01 Oct 1996 01:18:48 -0700 Message-ID: <29201.844157928@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Will have to be either disabled or revamped before I do my next snapshot, I'm afraid. As it stand now, even a non-PCI machine will have a bewildering number of duplicate entries with no apparent rhyme or reason to them and users are going to be _confused_. The drivers listed twice in the current GENERIC kernel are: bt0 ed0 lnc0 And deleting any of the PCI entries, BTW, is now grounds for an immediate panic once you continue. Whups. In any case, I was kind of hoping to do an October snapshot soon - what are your plans for userconfig? Jordan From owner-freebsd-current Tue Oct 1 01:39:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA06826 for current-outgoing; Tue, 1 Oct 1996 01:39:39 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA06817; Tue, 1 Oct 1996 01:39:32 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id SAA19825; Tue, 1 Oct 1996 18:38:26 +1000 Date: Tue, 1 Oct 1996 18:38:26 +1000 From: Bruce Evans Message-Id: <199610010838.SAA19825@godzilla.zeta.org.au> To: bde@freebsd.org, jkh@time.cdrom.com Subject: Re: Your UserConfig changes for unmasking PCI devices... Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >In any case, I was kind of hoping to do an October snapshot soon - >what are your plans for userconfig? I was planning to send bug reports to its submitter and committer :-). Bruce From owner-freebsd-current Tue Oct 1 02:09:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA08528 for current-outgoing; Tue, 1 Oct 1996 02:09:12 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA08521; Tue, 1 Oct 1996 02:09:09 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id CAA29875; Tue, 1 Oct 1996 02:09:02 -0700 (PDT) To: Bruce Evans cc: bde@freebsd.org, current@freebsd.org Subject: Re: Your UserConfig changes for unmasking PCI devices... In-reply-to: Your message of "Tue, 01 Oct 1996 18:38:26 +1000." <199610010838.SAA19825@godzilla.zeta.org.au> Date: Tue, 01 Oct 1996 02:09:02 -0700 Message-ID: <29873.844160942@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >In any case, I was kind of hoping to do an October snapshot soon - > >what are your plans for userconfig? > > I was planning to send bug reports to its submitter and committer :-). "50-foot black monolithic statue of Elvis found on Moon!" "Madonna joins The Artist Formerly Known as Prince in changing name to obscure Egyptian glyph, declaring ``I am the 43rd incarnation of Cleopatra!''" "Software engineer sends bug reports to self!" Naw... Too implausible. Jordan From owner-freebsd-current Tue Oct 1 02:25:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA09367 for current-outgoing; Tue, 1 Oct 1996 02:25:44 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA09361; Tue, 1 Oct 1996 02:25:40 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id SAA10913; Tue, 1 Oct 1996 18:55:28 +0930 From: Michael Smith Message-Id: <199610010925.SAA10913@genesis.atrad.adelaide.edu.au> Subject: Re: Your UserConfig changes for unmasking PCI devices... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 1 Oct 1996 18:55:27 +0930 (CST) Cc: bde@freebsd.org, current@freebsd.org In-Reply-To: <29201.844157928@time.cdrom.com> from "Jordan K. Hubbard" at Oct 1, 96 01:18:48 am 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: > > Will have to be either disabled or revamped before I do my next > snapshot, I'm afraid. As it stand now, even a non-PCI machine will > have a bewildering number of duplicate entries with no apparent rhyme > or reason to them and users are going to be _confused_. I think (MHOO) that things were better when PCI devices weren't listed. I know I meant them to show up, but unless they get grouped seperately (ie. in a seperate class) you're right; people will get confused. > And deleting any of the PCI entries, BTW, is now grounds for an > immediate panic once you continue. Whups. Urk. That's _not_ supposed to happen, and TBH unless Bruce goofed somewhere I can't see how it could. (His changes haven't made it here yet). > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 1 02:34:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA09893 for current-outgoing; Tue, 1 Oct 1996 02:34:26 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA09885; Tue, 1 Oct 1996 02:34:22 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id CAA04210; Tue, 1 Oct 1996 02:34:14 -0700 (PDT) To: Michael Smith cc: bde@freebsd.org, current@freebsd.org Subject: Re: Your UserConfig changes for unmasking PCI devices... In-reply-to: Your message of "Tue, 01 Oct 1996 18:55:27 +0930." <199610010925.SAA10913@genesis.atrad.adelaide.edu.au> Date: Tue, 01 Oct 1996 02:34:14 -0700 Message-ID: <4208.844162454@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I think (MHOO) that things were better when PCI devices weren't listed. > I know I meant them to show up, but unless they get grouped seperately > (ie. in a seperate class) you're right; people will get confused. Even having the bus type displayed in the description string, perhaps in a different text attribute, would be enough. So you'd see: bt0 Buslogic SCSI controller [PCI] bt0 Buslogic SCSI controller [ISA/EISA/VLB] And *only* if the machine in question even had a PCI bus. I can't see any reason to show the PCI entries on my 486/EISA test machine. :-) Jordan From owner-freebsd-current Tue Oct 1 02:39:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA10086 for current-outgoing; Tue, 1 Oct 1996 02:39:26 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA10081; Tue, 1 Oct 1996 02:39:22 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id TAA11012; Tue, 1 Oct 1996 19:09:10 +0930 From: Michael Smith Message-Id: <199610010939.TAA11012@genesis.atrad.adelaide.edu.au> Subject: Re: Your UserConfig changes for unmasking PCI devices... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 1 Oct 1996 19:09:10 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, bde@freebsd.org, current@freebsd.org In-Reply-To: <4208.844162454@time.cdrom.com> from "Jordan K. Hubbard" at Oct 1, 96 02:34:14 am 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: > > Even having the bus type displayed in the description string, perhaps > in a different text attribute, would be enough. So you'd see: > > bt0 Buslogic SCSI controller [PCI] > bt0 Buslogic SCSI controller [ISA/EISA/VLB] > > And *only* if the machine in question even had a PCI bus. I can't see > any reason to show the PCI entries on my 486/EISA test machine. :-) Problems : - "different text attributes" aren't (properly) supported by syscons at that point in the boot process. - how is userconfig supposed to know what hardware the system has? I thought the whole idea behind it was for it to run _before_ hardware had been located, not afterwards. I only planned to put PCI devices in as a calmative for users who might otherwise bitch about not being able to see them. It might make more sense just to rip them right out again. > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 1 02:58:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA10621 for current-outgoing; Tue, 1 Oct 1996 02:58:25 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA10615; Tue, 1 Oct 1996 02:58:20 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id CAA11845; Tue, 1 Oct 1996 02:58:15 -0700 (PDT) To: Michael Smith cc: bde@freebsd.org, current@freebsd.org Subject: Re: Your UserConfig changes for unmasking PCI devices... In-reply-to: Your message of "Tue, 01 Oct 1996 19:09:10 +0930." <199610010939.TAA11012@genesis.atrad.adelaide.edu.au> Date: Tue, 01 Oct 1996 02:58:15 -0700 Message-ID: <11843.844163895@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > - "different text attributes" aren't (properly) supported by syscons > at that point in the boot process. Ah. Phoo. > - how is userconfig supposed to know what hardware the system has? I > thought the whole idea behind it was for it to run _before_ hardware > had been located, not afterwards. Erm. Ya got me there, pardner! :-) > I only planned to put PCI devices in as a calmative for users who > might otherwise bitch about not being able to see them. It might make > more sense just to rip them right out again. I'm leaning that way myself unless we can figure out a way of doing a better job. How about a one-line summary somewhere like this: PCI device support for: bt0 ed0 lnc0 On the screen? :-) Jordan From owner-freebsd-current Tue Oct 1 04:12:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA12718 for current-outgoing; Tue, 1 Oct 1996 04:12:41 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA12709 for ; Tue, 1 Oct 1996 04:12:37 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id VAA24364; Tue, 1 Oct 1996 21:05:38 +1000 Date: Tue, 1 Oct 1996 21:05:38 +1000 From: Bruce Evans Message-Id: <199610011105.VAA24364@godzilla.zeta.org.au> To: bde@zeta.org.au, jkh@time.cdrom.com Subject: Re: Your UserConfig changes for unmasking PCI devices... Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> >In any case, I was kind of hoping to do an October snapshot soon - >> >what are your plans for userconfig? >> >> I was planning to send bug reports to its submitter and committer :-). > >"50-foot black monolithic statue of Elvis found on Moon!" > > "Madonna joins The Artist Formerly Known as Prince in changing name > to obscure Egyptian glyph, declaring ``I am the 43rd incarnation of > Cleopatra!''" > > "Software engineer sends bug reports to self!" > >Naw... Too implausible. It's ambiguous :-). Bruce From owner-freebsd-current Tue Oct 1 04:33:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA13396 for current-outgoing; Tue, 1 Oct 1996 04:33:05 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA13390; Tue, 1 Oct 1996 04:33:02 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id VAA11670; Tue, 1 Oct 1996 21:02:55 +0930 From: Michael Smith Message-Id: <199610011132.VAA11670@genesis.atrad.adelaide.edu.au> Subject: Re: Your UserConfig changes for unmasking PCI devices... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 1 Oct 1996 21:02:54 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, bde@freebsd.org, current@freebsd.org In-Reply-To: <11843.844163895@time.cdrom.com> from "Jordan K. Hubbard" at Oct 1, 96 02:58:15 am 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: > > > I only planned to put PCI devices in as a calmative for users who > > might otherwise bitch about not being able to see them. It might make > > more sense just to rip them right out again. > > I'm leaning that way myself unless we can figure out a way of doing > a better job. How about a one-line summary somewhere like this: > > PCI device support for: bt0 ed0 lnc0 > > On the screen? :-) Ah, how about putting off calling userconfig() until after the PCI and EISA probes? Since it's only _really_ relevant to the ISA probe process, shouldn't it be directly associated with it? > Jordan > -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 1 04:39:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA13529 for current-outgoing; Tue, 1 Oct 1996 04:39:05 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA13524; Tue, 1 Oct 1996 04:39:03 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id EAA15889; Tue, 1 Oct 1996 04:38:49 -0700 (PDT) To: Michael Smith cc: bde@freebsd.org, current@freebsd.org Subject: Re: Your UserConfig changes for unmasking PCI devices... In-reply-to: Your message of "Tue, 01 Oct 1996 21:02:54 +0930." <199610011132.VAA11670@genesis.atrad.adelaide.edu.au> Date: Tue, 01 Oct 1996 04:38:49 -0700 Message-ID: <15887.844169929@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Ah, how about putting off calling userconfig() until after the PCI and > EISA probes? Since it's only _really_ relevant to the ISA probe > process, shouldn't it be directly associated with it? If this doesn't have any unwonted side-effects, sure! Jordan From owner-freebsd-current Tue Oct 1 04:57:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA13973 for current-outgoing; Tue, 1 Oct 1996 04:57:41 -0700 (PDT) Received: from phoenix.csie.nctu.edu.tw (root@phoenix.csie.nctu.edu.tw [140.113.17.171]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA13967 for ; Tue, 1 Oct 1996 04:57:34 -0700 (PDT) Received: from FreeBSD.csie.NCTU.edu.tw (freebsd.csie.nctu.edu.tw [140.113.235.250]) by phoenix.csie.nctu.edu.tw (8.7.5/8.7.5) with ESMTP id TAA25895 for ; Tue, 1 Oct 1996 19:54:43 +0800 (CST) Received: (from jdli@localhost) by FreeBSD.csie.NCTU.edu.tw (8.7.6/8.7.3) id TAA11817 for freebsd-current@freebsd.org; Tue, 1 Oct 1996 19:56:22 +0800 (CST) From: Jian-Da Li Message-Id: <199610011156.TAA11817@FreeBSD.csie.NCTU.edu.tw> Subject: the latest ld.so doesn't work !!! To: freebsd-current@freebsd.org Date: Tue, 1 Oct 1996 19:56:22 +0800 (CST) X-Mailer: ELM [version 2.4ME+ PL11 (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 Hi : I just grab the latest current with the LD_HINT_VERSION = 2, and now make world dies at : -------------------------------------------------------------- Rebuilding tools needed to build the libraries -------------------------------------------------------------- .... ===> rtld .... ld -o ld.so -Bshareable -Bsymbolic -assert nosymbolic mdprologue.o rtld.o malloc.o shlib.o md.o support.o sbrk.o -lc_pic -lgcc_pic ld: Cannot reduce symbol "_RELOC_EXTERN_P" in rtld.o ld: Cannot reduce symbol "_RELOC_SYMBOL" in rtld.o ld: Cannot reduce symbol "_RELOC_PCREL_P" in rtld.o install -c -s -o bin -g bin -m 555 ld /usr/bin ===> ldconfig install -c -s -o bin -g bin -m 555 ldconfig /sbin ===> ldd install -c -s -o bin -g bin -m 555 ldd /usr/bin ===> rtld install -c -s -o bin -g bin -m 555 -fschg -C ld.so /usr/libexec ===> ldconfig Trace/BPT trap *** Error code 133 Then ALL shared binaries DIE !! I have to restore old ld.so and ldconfig to make all shared binary work again. -- §õ «Ø ¹F (Jian-Da Li) ¥æ ¤j ¸ê ¤u E-Mail : http://www.csie.nctu.edu.tw/~jdli From owner-freebsd-current Tue Oct 1 05:19:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA14594 for current-outgoing; Tue, 1 Oct 1996 05:19:38 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA14586 for ; Tue, 1 Oct 1996 05:19:17 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.0/8.8.0) with ESMTP id UAA15170 for ; Tue, 1 Oct 1996 20:19:01 +0800 (WST) Message-Id: <199610011219.UAA15170@spinner.DIALix.COM> X-Mailer: exmh version 1.6.7 5/3/96 To: current@freebsd.org Subject: WARNING: botched ld.so commit! :-( Date: Tue, 01 Oct 1996 20:19:01 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's been pointed out to me that I managed to royally screw up my commit to the rtld/ld.so code, in just about the worst possible way on the only file in the entire system that's vulnerable to this type of screwup. (It's linked -Bsymbolic which allows undefined symbols) I'm still not entirely sure how it happened, but I think it was because I did the commits on a per-directory basis, and must have committed a slightly out of sync file from my last minute testing and "minor" tweaks after John and Nate went over it. I do remote commits, and must have committed from the wrong window/machine. If you get burned, you need to restore /usr/libexec/ld.so from somewhere, it doesn't matter how old as long as it's about 2.0.5 or later vintage. Getting a fixed version in place might be a challenge, you'll need to run "chflags noschg /usr/libexec/ld.so" to turn off the immutable bit and use some statically linked program to copy it in. (/bin/{cp,mv,rcp,pax} may be useful. Ouch... Sorry people, this was my fault and not something the review missed. -Peter From owner-freebsd-current Tue Oct 1 05:48:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA15590 for current-outgoing; Tue, 1 Oct 1996 05:48:22 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA15577; Tue, 1 Oct 1996 05:48:01 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id WAA27507; Tue, 1 Oct 1996 22:35:14 +1000 Date: Tue, 1 Oct 1996 22:35:14 +1000 From: Bruce Evans Message-Id: <199610011235.WAA27507@godzilla.zeta.org.au> To: jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au Subject: Re: Your UserConfig changes for unmasking PCI devices... Cc: bde@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I'm leaning that way myself unless we can figure out a way of doing >> a better job. How about a one-line summary somewhere like this: >> >> PCI device support for: bt0 ed0 lnc0 Good. >Ah, how about putting off calling userconfig() until after the PCI and >EISA probes? Since it's only _really_ relevant to the ISA probe >process, shouldn't it be directly associated with it? Bad. It should become relevant to configuration of everything. Bruce From owner-freebsd-current Tue Oct 1 05:50:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA15684 for current-outgoing; Tue, 1 Oct 1996 05:50:17 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA15679 for ; Tue, 1 Oct 1996 05:50:15 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id OAA25083; Tue, 1 Oct 1996 14:50:02 +0200 Message-Id: <199610011250.OAA25083@ra.dkuug.dk> Subject: Re: WARNING: botched ld.so commit! :-( To: peter@spinner.DIALix.COM (Peter Wemm) Date: Tue, 1 Oct 1996 14:50:01 +0200 (MET DST) Cc: current@freebsd.org In-Reply-To: <199610011219.UAA15170@spinner.DIALix.COM> from "Peter Wemm" at Oct 1, 96 08:19:01 pm From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In reply to Peter Wemm who wrote: > > It's been pointed out to me that I managed to royally screw up my commit > to the rtld/ld.so code, in just about the worst possible way on the only > file in the entire system that's vulnerable to this type of screwup. Damn, where is that pointy hat, damn who had it last ?? :) :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Tue Oct 1 05:54:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA15779 for current-outgoing; Tue, 1 Oct 1996 05:54:20 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA15774; Tue, 1 Oct 1996 05:54:18 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id WAA12204; Tue, 1 Oct 1996 22:24:07 +0930 From: Michael Smith Message-Id: <199610011254.WAA12204@genesis.atrad.adelaide.edu.au> Subject: Re: Your UserConfig changes for unmasking PCI devices... To: bde@zeta.org.au (Bruce Evans) Date: Tue, 1 Oct 1996 22:24:07 +0930 (CST) Cc: jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au, bde@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199610011235.WAA27507@godzilla.zeta.org.au> from "Bruce Evans" at Oct 1, 96 10:35:14 pm 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 Bruce Evans stands accused of saying: > >> > >> PCI device support for: bt0 ed0 lnc0 > > Good. Screen clutter and meaningless names. I would vote for plonking them under a seperate header and making them impossible to remove. > >Ah, how about putting off calling userconfig() until after the PCI and > >EISA probes? Since it's only _really_ relevant to the ISA probe > >process, shouldn't it be directly associated with it? > > Bad. It should become relevant to configuration of everything. Nothing else requires configuration (or can be configured, afaik). > Bruce > -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 1 06:02:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16025 for current-outgoing; Tue, 1 Oct 1996 06:02:34 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA16020; Tue, 1 Oct 1996 06:02:24 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.0/8.8.0) with ESMTP id VAA15470; Tue, 1 Oct 1996 21:02:15 +0800 (WST) Message-Id: <199610011302.VAA15470@spinner.DIALix.COM> X-Mailer: exmh version 1.6.7 5/3/96 To: sos@freebsd.org cc: current@freebsd.org Subject: Re: WARNING: botched ld.so commit! :-( In-reply-to: Your message of "Tue, 01 Oct 1996 14:50:01 +0200." <199610011250.OAA25083@ra.dkuug.dk> Date: Tue, 01 Oct 1996 21:02:15 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk sos@freebsd.org wrote: > In reply to Peter Wemm who wrote: > > > > It's been pointed out to me that I managed to royally screw up my commit > > to the rtld/ld.so code, in just about the worst possible way on the only > > file in the entire system that's vulnerable to this type of screwup. > > > Damn, where is that pointy hat, damn who had it last ?? :) :) Yeah, especially considering the only two tools that can easily fix it are dynamically linked :-( (chflags and install). In case it's any help to anybody, I've uploaded a static linked chflags executable (and a working ld.so) to ftp://freefall.freebsd.org/pub/peter/*. /bin/rcp is statically linked on most FreeBSD systems, so getting executables to a nearby machine may be enough to get out of the jam. Oh, another thought.. from a root login: # /bin/mv /usr/libexec /usr/libexec.fubar # /bin/mkdir /usr/libexec # /bin/cp /whereever/ld.so /usr/libexec # chflags noschg /usr/libexec.fubar/ld.so # cp /wherever/ld.so /usr/libexec.fubar # mv /usr/libexec /usr/libexec.fresh # mv /usr/libexec.fubar /usr/libexec (I think I'll leave for Antarctica before anybody catches me... :-] ) -Peter From owner-freebsd-current Tue Oct 1 06:15:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16517 for current-outgoing; Tue, 1 Oct 1996 06:15:17 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA16509; Tue, 1 Oct 1996 06:15:14 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id GAA03805; Tue, 1 Oct 1996 06:14:37 -0700 (PDT) To: Michael Smith cc: bde@zeta.org.au (Bruce Evans), bde@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Your UserConfig changes for unmasking PCI devices... In-reply-to: Your message of "Tue, 01 Oct 1996 22:24:07 +0930." <199610011254.WAA12204@genesis.atrad.adelaide.edu.au> Date: Tue, 01 Oct 1996 06:14:37 -0700 Message-ID: <3803.844175677@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Screen clutter and meaningless names. I would vote for plonking them > under a seperate header and making them impossible to remove. Heck, if you're doing the implementation, you can plonk them wherever you like! :-) Jordan From owner-freebsd-current Tue Oct 1 06:17:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16628 for current-outgoing; Tue, 1 Oct 1996 06:17:30 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA16623; Tue, 1 Oct 1996 06:17:27 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id IAA20544; Tue, 1 Oct 1996 08:17:19 -0500 (EST) From: "John S. Dyson" Message-Id: <199610011317.IAA20544@dyson.iquest.net> Subject: Re: WARNING: botched ld.so commit! :-( To: sos@FreeBSD.org Date: Tue, 1 Oct 1996 08:17:19 -0500 (EST) Cc: peter@spinner.DIALix.COM, current@FreeBSD.org In-Reply-To: <199610011250.OAA25083@ra.dkuug.dk> from "sos@FreeBSD.org" at Oct 1, 96 02:50:01 pm Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] 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 > > In reply to Peter Wemm who wrote: > > > > It's been pointed out to me that I managed to royally screw up my commit > > to the rtld/ld.so code, in just about the worst possible way on the only > > file in the entire system that's vulnerable to this type of screwup. > > > Damn, where is that pointy hat, damn who had it last ?? :) :) > Even I don't touch rtld :-). Scary thought if I worked on it :-). John From owner-freebsd-current Tue Oct 1 06:46:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA17983 for current-outgoing; Tue, 1 Oct 1996 06:46:40 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA17964; Tue, 1 Oct 1996 06:46:35 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id XAA30133; Tue, 1 Oct 1996 23:40:20 +1000 Date: Tue, 1 Oct 1996 23:40:20 +1000 From: Bruce Evans Message-Id: <199610011340.XAA30133@godzilla.zeta.org.au> To: bde@zeta.org.au, msmith@atrad.adelaide.edu.au Subject: Re: Your UserConfig changes for unmasking PCI devices... Cc: bde@FreeBSD.org, current@FreeBSD.org, jkh@time.cdrom.com Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> >Ah, how about putting off calling userconfig() until after the PCI and >> >EISA probes? Since it's only _really_ relevant to the ISA probe >> >process, shouldn't it be directly associated with it? >> >> Bad. It should become relevant to configuration of everything. > >Nothing else requires configuration (or can be configured, afaik). That's because configuration is broken. Bruce From owner-freebsd-current Tue Oct 1 06:53:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA18196 for current-outgoing; Tue, 1 Oct 1996 06:53:03 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA18191; Tue, 1 Oct 1996 06:53:00 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id XAA12573; Tue, 1 Oct 1996 23:22:56 +0930 From: Michael Smith Message-Id: <199610011352.XAA12573@genesis.atrad.adelaide.edu.au> Subject: Re: Your UserConfig changes for unmasking PCI devices... To: bde@zeta.org.au (Bruce Evans) Date: Tue, 1 Oct 1996 23:22:55 +0930 (CST) Cc: bde@zeta.org.au, msmith@atrad.adelaide.edu.au, bde@FreeBSD.org, current@FreeBSD.org, jkh@time.cdrom.com In-Reply-To: <199610011340.XAA30133@godzilla.zeta.org.au> from "Bruce Evans" at Oct 1, 96 11:40:20 pm 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 Bruce Evans stands accused of saying: > >> > >> Bad. It should become relevant to configuration of everything. > > > >Nothing else requires configuration (or can be configured, afaik). > > That's because configuration is broken. I think we're all in agreement here. OK, if nobody else gets to it, I'll undertake tomorrow to relocate and reattribute PCI devices so that they are visible but unfrobbable. If/when it becomes possible to frob them, we can worry about where and how. > Bruce > -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 1 07:11:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA19106 for current-outgoing; Tue, 1 Oct 1996 07:11:31 -0700 (PDT) Received: from pc040e.ihcc.cc.ia.us (pc040e.ihcc.cc.ia.us [205.221.194.40]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA19100 for ; Tue, 1 Oct 1996 07:11:28 -0700 (PDT) Received: from pc031e.ihcc.cc.ia.us ([205.221.194.31]) by pc040e.ihcc.cc.ia.us (8.7.5/8.7.3) with SMTP id JAA07915 for ; Tue, 1 Oct 1996 09:07:57 -0500 (CDT) Message-ID: <32512645.52C2@www1.ihcc.cc.ia.us> Date: Tue, 01 Oct 1996 09:10:13 -0500 From: chris Organization: Green Prairie Iowa Realty X-Mailer: Mozilla 2.02 (Win16; I) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: MAILING LIST X-URL: http://www.freebsd.org/handbook/handbook194.html Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk SUBSRIBE FREEBSD-CURRENT AT ADDRESS FROGGER1@JUNO.COM From owner-freebsd-current Tue Oct 1 07:18:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA19480 for current-outgoing; Tue, 1 Oct 1996 07:18:18 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA19473; Tue, 1 Oct 1996 07:18:14 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id QAA11650; Tue, 1 Oct 1996 16:17:29 +0200 (MET DST) To: Peter Wemm cc: sos@freebsd.org, current@freebsd.org Subject: Re: WARNING: botched ld.so commit! :-( In-reply-to: Your message of "Tue, 01 Oct 1996 21:02:15 +0800." <199610011302.VAA15470@spinner.DIALix.COM> Date: Tue, 01 Oct 1996 16:17:28 +0200 Message-ID: <11648.844179448@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199610011302.VAA15470@spinner.DIALix.COM>, Peter Wemm writes: >(I think I'll leave for Antarctica before anybody catches me... :-] ) > I belive I have positive confirmation of at least one FreeBSD laptop down there already :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Oct 1 07:28:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA19925 for current-outgoing; Tue, 1 Oct 1996 07:28:04 -0700 (PDT) Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA19920 for ; Tue, 1 Oct 1996 07:28:01 -0700 (PDT) From: garyj@frt.dec.com Received: from cssmuc.frt.dec.com by mail13.digital.com (8.7.5/UNX 1.2/1.0/WV) id KAA16668; Tue, 1 Oct 1996 10:20:20 -0400 (EDT) Received: from localhost by cssmuc.frt.dec.com; (5.65v3.2/1.1.8.2/14Nov95-0232PM) id AA04046; Tue, 1 Oct 1996 15:20:13 +0100 Message-Id: <9610011420.AA04046@cssmuc.frt.dec.com> X-Mailer: exmh version 1.6.4 10/10/95 To: current@freebsd.org In-Reply-To: Message from Paul Traina of Mon, 30 Sep 96 18:06:13 PDT. Reply-To: gjennejohn@frt.dec.com Subject: Re: gdb port testing... gdb-4.16 to move into /usr/src soon... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Oct 96 16:20:13 +0200 X-Mts: smtp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk pst@jnx.com writes: > Folks, > If you're at all concerned about the fact that I will be upgrading our > GDB to GDB v4.16 with a completely revised set of FreeBSD changes, then > I strongly suggest that you test out the gdb "port" NOW. > > I'd like people to report bugs *before* we dump this on everyone in -current. > the testing I've done, mainly looking at crash dumps, indicates that the new gdb works at least as well as the old version. --- Gary Jennejohn (work) gjennejohn@frt.dec.com (home) Gary.Jennejohn@munich.netsurf.de (play) gj@freebsd.org From owner-freebsd-current Tue Oct 1 07:39:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA20628 for current-outgoing; Tue, 1 Oct 1996 07:39:10 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA20613; Tue, 1 Oct 1996 07:39:04 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id AAA32208; Wed, 2 Oct 1996 00:35:48 +1000 Date: Wed, 2 Oct 1996 00:35:48 +1000 From: Bruce Evans Message-Id: <199610011435.AAA32208@godzilla.zeta.org.au> To: peter@spinner.DIALix.COM, sos@freebsd.org Subject: Re: WARNING: botched ld.so commit! :-( Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Damn, where is that pointy hat, damn who had it last ?? :) :) > >Yeah, especially considering the only two tools that can easily fix it are >dynamically linked :-( (chflags and install). Actually, chflags is linked static (except my version of course). >Oh, another thought.. from a root login: ># /bin/mv /usr/libexec /usr/libexec.fubar ># /bin/mkdir /usr/libexec ># /bin/cp /whereever/ld.so /usr/libexec ># chflags noschg /usr/libexec.fubar/ld.so ># cp /wherever/ld.so /usr/libexec.fubar ># mv /usr/libexec /usr/libexec.fresh ># mv /usr/libexec.fubar /usr/libexec This shows that the chflags on ld.so is mainly to [prevent] shoot[ing] yourself in the foot. It doesn't improve security. Bruce From owner-freebsd-current Tue Oct 1 08:53:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA25384 for current-outgoing; Tue, 1 Oct 1996 08:53:59 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA25369; Tue, 1 Oct 1996 08:53:54 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.6/8.6.6) with ESMTP id JAA02207; Tue, 1 Oct 1996 09:25:50 -0600 (MDT) Message-Id: <199610011525.JAA02207@rover.village.org> To: Poul-Henning Kamp Subject: Re: WARNING: botched ld.so commit! :-( Cc: Peter Wemm , sos@freebsd.org, current@freebsd.org In-reply-to: Your message of "Tue, 01 Oct 1996 16:17:28 +0200." <11648.844179448@critter.tfs.com> References: <11648.844179448@critter.tfs.com> Date: Tue, 01 Oct 1996 09:25:49 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <11648.844179448@critter.tfs.com> Poul-Henning Kamp writes: : In message <199610011302.VAA15470@spinner.DIALix.COM>, Peter Wemm writes: : >(I think I'll leave for Antarctica before anybody catches me... :-] ) : I belive I have positive confirmation of at least one FreeBSD laptop : down there already :-) I know that another will be travelling down there in a few weeks... You can run, but you can't hide :-) Warner From owner-freebsd-current Tue Oct 1 08:55:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA25573 for current-outgoing; Tue, 1 Oct 1996 08:55:39 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA25563 for ; Tue, 1 Oct 1996 08:55:36 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id IAA03239; Tue, 1 Oct 1996 08:55:10 -0700 (PDT) Message-Id: <199610011555.IAA03239@austin.polstra.com> To: Jian-Da Li Cc: freebsd-current@FreeBSD.ORG Subject: Re: the latest ld.so doesn't work !!! In-reply-to: <199610011156.TAA11817@FreeBSD.csie.NCTU.edu.tw> Date: Tue, 01 Oct 1996 08:55:10 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I just grab the latest current with the LD_HINT_VERSION = 2, and now > make world dies at : > > -------------------------------------------------------------- > Rebuilding tools needed to build the libraries > -------------------------------------------------------------- > .... > ===> rtld > .... > ld -o ld.so -Bshareable -Bsymbolic -assert nosymbolic mdprologue.o > rtld.o malloc.o shlib.o md.o support.o sbrk.o -lc_pic -lgcc_pic > ld: Cannot reduce symbol "_RELOC_EXTERN_P" in rtld.o > ld: Cannot reduce symbol "_RELOC_SYMBOL" in rtld.o > ld: Cannot reduce symbol "_RELOC_PCREL_P" in rtld.o It looks like you still have the old version of "rtld.c". The current version doesn't even reference those symbols. It used to reference them, and "ld.h" used to define them. In the current version, both the references and definitions were removed. I think you have the old version of "rtld.c", but the new version of "ld.h". That would explain the symptoms. Perhaps you got unlucky, and supped your sources at just the wrong time. John -- 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 Oct 1 09:15:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA27418 for current-outgoing; Tue, 1 Oct 1996 09:15:46 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA27413 for ; Tue, 1 Oct 1996 09:15:42 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id JAA03350 for ; Tue, 1 Oct 1996 09:15:40 -0700 (PDT) Message-Id: <199610011615.JAA03350@austin.polstra.com> To: current@FreeBSD.ORG Subject: Re: WARNING: botched ld.so commit! :-( In-reply-to: <199610011317.IAA20544@dyson.iquest.net> Date: Tue, 01 Oct 1996 09:15:40 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Dyson wrote: > > In reply to Peter Wemm who wrote: > > > > > > It's been pointed out to me that I managed to royally screw up my commit > > > to the rtld/ld.so code, in just about the worst possible way on the only > > > file in the entire system that's vulnerable to this type of screwup. > > > > > > Damn, where is that pointy hat, damn who had it last ?? :) :) > > > Even I don't touch rtld :-). Scary thought if I worked on it :-). Just to reinforce that sentiment, I worked on rtld for a while, and it's nerve-wracking! It's like trying to replace a rope that you and the rest of the world are hanging from. (By the neck, if you screw up.) I think we all know Peter well enough to forego giving him too much flack over this. (Same goes for John Dyson and the occasional hiccups that come with the great things he's doing for us.) John -- 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 Oct 1 09:28:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28429 for current-outgoing; Tue, 1 Oct 1996 09:28:50 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA28421; Tue, 1 Oct 1996 09:28:46 -0700 (PDT) Message-Id: <199610011628.JAA28421@freefall.freebsd.org> To: "Jordan K. Hubbard" cc: Michael Smith , bde@FreeBSD.org, current@FreeBSD.org Subject: Re: Your UserConfig changes for unmasking PCI devices... In-reply-to: Your message of "Tue, 01 Oct 1996 02:34:14 PDT." <4208.844162454@time.cdrom.com> Date: Tue, 01 Oct 1996 09:28:45 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> I think (MHOO) that things were better when PCI devices weren't listed. >> I know I meant them to show up, but unless they get grouped seperately >> (ie. in a seperate class) you're right; people will get confused. > >Even having the bus type displayed in the description string, perhaps >in a different text attribute, would be enough. So you'd see: > >bt0 Buslogic SCSI controller [PCI] >bt0 Buslogic SCSI controller [ISA/EISA/VLB] > >And *only* if the machine in question even had a PCI bus. I can't see >any reason to show the PCI entries on my 486/EISA test machine. :-) > > Jordan At the time UserConfig comes up, you haven't even probed for a PCI bus, so you don't know if one exists or not. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Oct 1 09:30:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA28639 for current-outgoing; Tue, 1 Oct 1996 09:30:46 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA28633; Tue, 1 Oct 1996 09:30:42 -0700 (PDT) Message-Id: <199610011630.JAA28633@freefall.freebsd.org> To: Michael Smith cc: jkh@time.cdrom.com (Jordan K. Hubbard), bde@freebsd.org, current@freebsd.org Subject: Re: Your UserConfig changes for unmasking PCI devices... In-reply-to: Your message of "Tue, 01 Oct 1996 21:02:54 +0930." <199610011132.VAA11670@genesis.atrad.adelaide.edu.au> Date: Tue, 01 Oct 1996 09:30:42 -0700 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Jordan K. Hubbard stands accused of saying: >> >> > I only planned to put PCI devices in as a calmative for users who >> > might otherwise bitch about not being able to see them. It might make >> > more sense just to rip them right out again. >> >> I'm leaning that way myself unless we can figure out a way of doing >> a better job. How about a one-line summary somewhere like this: >> >> PCI device support for: bt0 ed0 lnc0 >> >> On the screen? :-) > >Ah, how about putting off calling userconfig() until after the PCI and >EISA probes? Since it's only _really_ relevant to the ISA probe >process, shouldn't it be directly associated with it? > >> Jordan That may be a solution for now, but in the future, I'd like to see UserConfig expand its role, not narrow it. >-- >]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ >]] Genesis Software genesis@atrad.adelaide.edu.au [[ >]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ >]] realtime instrument control (ph/fax) +61-8-267-3039 [[ >]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Oct 1 11:20:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA07448 for current-outgoing; Tue, 1 Oct 1996 11:20:24 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA07433 for ; Tue, 1 Oct 1996 11:20:20 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id UAA01971 for ; Tue, 1 Oct 1996 20:20:06 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id UAA14774 for freebsd-current@FreeBSD.ORG; Tue, 1 Oct 1996 20:19:52 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.0/keltia-uucp-2.9) id UAA07552; Tue, 1 Oct 1996 20:18:55 +0200 (MET DST) Message-Id: <199610011818.UAA07552@keltia.freenix.fr> Date: Tue, 1 Oct 1996 20:18:55 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Subject: ELFKit on current X-Mailer: Mutt 0.45i Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2522 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Has anyone tried to merge (I saw Peter do at least) John Polstra's ELFKit into current ? I've generated cross-compiling tools into /usr/local/elf but libc generation is more difficult. There are too many differences between 2.1.0 and CURRENT in libc for the merge to be done. I've tried going with a 2.1.5 libc but there are still a few things to merge manually. It would be nice to have ELF generating tools directly in CURRENT :-) I could use 2.1.0 libc but it would not be fun :-) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #23: Sun Sep 29 14:56:23 MET DST 1996 From owner-freebsd-current Tue Oct 1 11:46:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA10208 for current-outgoing; Tue, 1 Oct 1996 11:46:29 -0700 (PDT) Received: from Central.KeyWest.MPGN.COM (Central.TanSoft.COM [206.175.4.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA10110; Tue, 1 Oct 1996 11:45:10 -0700 (PDT) Received: from devious.Tansoft.com (Devious.TanSoft.COM [206.175.4.10]) by Central.KeyWest.MPGN.COM (8.6.9/8.6.9) with SMTP id OAA11919; Tue, 1 Oct 1996 14:44:13 -0400 Message-Id: <3.0b24.32.19961001144413.006e4040@central.TanSoft.COM> X-Sender: rwm@central.TanSoft.COM X-Mailer: Windows Eudora Pro Version 3.0b24 (32) Date: Tue, 01 Oct 1996 14:44:14 -0400 To: freebsd-current@freebsd.org, freebsd-smp@freebsd.org From: Rob Miracle Subject: Problem w/ New Kernels Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just put up the lastest SMP kernel (and I had the same problem with the normal Kernel when I ftp'ed the sys tree from ftp.freebsd.org last week) and I have an odd problem: If I do a 'ps' or a 'w' I get a message back saying ps: proc size mismatch (18960 total, 612 chunks) or w: proc size mismatch (18960 total, 612 chunks) Any ideas? Thanks Rob -- Rob Miracle Tantalus Inc. Be patient or be a patient. -- Anton Devious From owner-freebsd-current Tue Oct 1 12:54:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA20160 for current-outgoing; Tue, 1 Oct 1996 12:54:58 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA20104; Tue, 1 Oct 1996 12:54:29 -0700 (PDT) Received: from localhost (scrappy@localhost) by quagmire.ki.net (8.7.5/8.7.5) with SMTP id PAA05103; Tue, 1 Oct 1996 15:54:18 -0400 (EDT) Date: Tue, 1 Oct 1996 15:54:17 -0400 (EDT) From: "Marc G. Fournier" To: Rob Miracle cc: freebsd-current@freebsd.org, freebsd-smp@freebsd.org Subject: Re: Problem w/ New Kernels In-Reply-To: <3.0b24.32.19961001144413.006e4040@central.TanSoft.COM> 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 Tue, 1 Oct 1996, Rob Miracle wrote: > I just put up the lastest SMP kernel (and I had the same problem with the > normal Kernel when I ftp'ed the sys tree from ftp.freebsd.org last week) > and I have an odd problem: > > If I do a 'ps' or a 'w' I get a message back saying > > ps: proc size mismatch (18960 total, 612 chunks) > > or > > w: proc size mismatch (18960 total, 612 chunks) > > Any ideas? > Did you remember to recompile ps/w? If *that* doesn't do it, then libkvm has to be recompiled as well... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Tue Oct 1 13:05:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA20897 for current-outgoing; Tue, 1 Oct 1996 13:05:21 -0700 (PDT) Received: from alpo.whistle.com ([207.76.204.16]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA20891 for ; Tue, 1 Oct 1996 13:05:14 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id NAA07016; Tue, 1 Oct 1996 13:02:39 -0700 (PDT) Message-ID: <3251786E.59E2B600@whistle.com> Date: Tue, 01 Oct 1996 13:00:46 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: gjennejohn@frt.dec.com CC: current@FreeBSD.ORG Subject: Re: gdb port testing... gdb-4.16 to move into /usr/src soon... References: <9610011420.AA04046@cssmuc.frt.dec.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk garyj@frt.dec.com wrote: > > pst@jnx.com writes: > > Folks, > > If you're at all concerned about the fact that I will be upgrading our > > GDB to GDB v4.16 with a completely revised set of FreeBSD changes, then > > I strongly suggest that you test out the gdb "port" NOW. > > > > I'd like people to report bugs *before* we dump this on everyone in -current. > > > > the testing I've done, mainly looking at crash dumps, indicates that the > new gdb works at least as well as the old version. for me, looking at stack traces on the new one (using the dgb stubs) on a running kernel, were not as good on the new one as in the old one.. I'll try to give examples soon. hmmmm now that I want to, the act the same..... I guess this means I'm happy with the new one. (I'm sure they acted differntly before, but.. as long as they work ok now) > > --- > Gary Jennejohn (work) gjennejohn@frt.dec.com > (home) Gary.Jennejohn@munich.netsurf.de > (play) gj@freebsd.org From owner-freebsd-current Tue Oct 1 13:09:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21205 for current-outgoing; Tue, 1 Oct 1996 13:09:06 -0700 (PDT) Received: from mailserver.KOM.th-darmstadt.de (bagpipe.kom.e-technik.th-darmstadt.de [130.83.139.249]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA21193 for ; Tue, 1 Oct 1996 13:09:02 -0700 (PDT) Received: from KOM.th-darmstadt.de by mailserver.KOM.th-darmstadt.de (8.7.5/8.7.5) with ESMTP id WAA05051 for ; Tue, 1 Oct 1996 22:09:33 +0200 (MET DST) Message-Id: <199610012009.WAA05051@mailserver.KOM.th-darmstadt.de> X-Mailer: exmh version 1.6.9 8/22/96 To: current@freefall.freebsd.org Subject: Compilation of ip_fil3.1.0 Reply-To: Reinhard.Bertram@KOM.th-darmstadt.de X-Pgp-Fingerprint: 33 1B BE A7 E0 20 D3 F0 18 7C BC 0D DF 2E 53 3B X-Face: Us\Fi6APYO-#d#:e?77J]X@g:O`^>BG/.7i7D`]csjk{+Y[gPU=nCV w|Y4YAs;g3%APq`;>eZI,K_-#"dwmW@NRy-aIl,O/Hc`6?jne_IZ^' %TL<"{6C216:Rv2pI"nzU*i\EGeT5|aVf#l4hpixy-&*.4|;#*l-6w vr#=c^a]Aw267ivfK?KE53'yU\Ewe5+*K:gi'81ez>~`~FmrDt8li !ua>=)D"= Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_-807184474P"; micalg=pgp-md5; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Tue, 01 Oct 1996 22:09:31 +0200 From: Reinhard Bertram Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk --==_Exmh_-807184474P Content-Type: text/plain; charset=us-ascii Hi, has anybody successfully compiled ip_fil3.1.0 on 2.2-960801-SNAP? I'm quite new to FreeBSD, but I would like to use it as a firewall system and I like the enhanced functionality of ip_fil3.1.0 more than ipfirewall. This is mainly true as I'm using ip_fil3.1.0 on Solaris Systems too and I don't want to fiddle around with different syntax on different systems. Is there anything I'm missing? It bails out of a missing ioconf.h, which should be autogenerated by the kernel compile process. It does get genereated, but ip_fil3.1.0 trys to find includes in /sys/arch and /sys/i386. If I manually link the kernel compile directory I get other errors, so this doesn't work. TNX for your help cu, Reinhard _______________________________________________________________________ Visit the KOM homepage! echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D3F204445524F42snlbxq' | dc --==_Exmh_-807184474P Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3i iQEVAwUBMlF6dlMZI0Qqq6rFAQHWDAf+LZugONdnu4Qi/SlM1xVZTXJyFjIBmT7y feaCpxQ+54K2bj8Xu7n9mUKlR8idhmdNBdIa92cWX+p9kl2Dd0NH9MafLNnIykMS 0Sg4nLCu9llWRgF86HvfWOl9gniPqqgQ/9QiTXTa+aenL4m+NKBp3htA4SLXtgC+ ptekPPViah1N004TdKCzOSQQ6BlBnPoPJ+xEmVramd/MoHp04iFbwC2KX/VSKu+C DgHCBf3i/t+V9zY059mZ6L3iMcibilf7IADRNqDdaF86AMl5e78UFMeng/67aIwN 58tI+O3EjBHfUeKj8VEFZ5KLDg+uSdAj+t0SBRfI2LtVY+dvcm2iIw== =mlPZ -----END PGP MESSAGE----- --==_Exmh_-807184474P-- From owner-freebsd-current Tue Oct 1 13:13:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21774 for current-outgoing; Tue, 1 Oct 1996 13:13:39 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA21769; Tue, 1 Oct 1996 13:13:36 -0700 (PDT) Received: from gilligan.eng.umd.edu (gilligan.eng.umd.edu [129.2.103.21]) by po1.glue.umd.edu (8.8.Gamma.0/8.7.3) with ESMTP id QAA08449; Tue, 1 Oct 1996 16:13:33 -0400 (EDT) Received: from localhost (chuckr@localhost) by gilligan.eng.umd.edu (8.7.5/8.7.3) with SMTP id QAA29168; Tue, 1 Oct 1996 16:13:32 -0400 (EDT) X-Authentication-Warning: gilligan.eng.umd.edu: chuckr owned process doing -bs Date: Tue, 1 Oct 1996 16:13:32 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@gilligan.eng.umd.edu To: Peter Wemm cc: sos@FreeBSD.org, current@FreeBSD.org Subject: Re: WARNING: botched ld.so commit! :-( In-Reply-To: <199610011302.VAA15470@spinner.DIALix.COM> 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 Tue, 1 Oct 1996, Peter Wemm wrote: > sos@freebsd.org wrote: > > In reply to Peter Wemm who wrote: > > > > > > It's been pointed out to me that I managed to royally screw up my commit > > > to the rtld/ld.so code, in just about the worst possible way on the only > > > file in the entire system that's vulnerable to this type of screwup. > > > > > > Damn, where is that pointy hat, damn who had it last ?? :) :) You know, when it came out this morning, besides thinking I would wait to see if someone else howled, I was thinking that it would have been real nice is there was some kind of safety flag that was settable on a make world to get it to skip the install phase, and let me try installing things a little gingerly. You made it all the way thru the gcc upgrade without a bobble; this was overdue. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Tue Oct 1 13:17:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21966 for current-outgoing; Tue, 1 Oct 1996 13:17:00 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA21959 for ; Tue, 1 Oct 1996 13:16:50 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA00447; Tue, 1 Oct 1996 16:16:36 -0400 Date: Tue, 1 Oct 1996 16:16:36 -0400 From: Garrett Wollman Message-Id: <9610012016.AA00447@halloran-eldar.lcs.mit.edu> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: gdb port testing... gdb-4.16 to move into /usr/src soon... In-Reply-To: <3251786E.59E2B600@whistle.com> References: <9610011420.AA04046@cssmuc.frt.dec.com> <3251786E.59E2B600@whistle.com> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk < said: > for me, looking at stack traces on the new one (using the dgb stubs) > on a running kernel, were not as good on the new one as in the old one.. > I'll try to give examples soon. I have hacked a bit on the code to make it properly decode special frames when debugging the kernel. Patches follow, beware cut&paste lossage... -GAWollman diff -u -r1.1 -r1.7 --- kvm-fbsd.c 1996/09/30 21:04:19 1.1 +++ kvm-fbsd.c 1996/10/01 20:13:15 1.7 @@ -40,6 +40,7 @@ #include #include +#include static void kcore_files_info PARAMS ((struct target_ops *)); @@ -105,6 +106,92 @@ */ #define kvread(addr, p) \ (target_read_memory ((CORE_ADDR)(addr), (char *)(p), sizeof(*(p)))) + + +/* + * The following is FreeBSD-specific hackery to decode special frames + * and elide the assembly-language stub. This could be made faster by + * defining a frame_type field in the machine-dependent frame information, + * but we don't think that's too important right now. + */ +enum frametype { tf_normal, tf_trap, tf_interrupt, tf_syscall }; + +CORE_ADDR +fbsd_kern_frame_saved_pc (fr) +struct frame_info *fr; +{ + struct minimal_symbol *sym; + CORE_ADDR this_saved_pc; + enum frametype frametype; + + this_saved_pc = read_memory_integer (fr->frame + 4, 4); + sym = lookup_minimal_symbol_by_pc (this_saved_pc); + frametype = tf_normal; + if (sym != NULL) { + if (strcmp (SYMBOL_NAME(sym), "calltrap") == 0) + frametype = tf_trap; + else if (strncmp (SYMBOL_NAME(sym), "Xresume", 7) == 0) + frametype = tf_interrupt; + else if (strcmp (SYMBOL_NAME(sym), "Xsyscall") == 0) + frametype = tf_syscall; + } + + switch (frametype) { + case tf_normal: + return (this_saved_pc); + +#define oEIP offsetof(struct trapframe, tf_eip) + + case tf_trap: + return (read_memory_integer (fr->frame + 8 + oEIP, 4)); + + case tf_interrupt: + return (read_memory_integer (fr->frame + 16 + oEIP, 4)); + + case tf_syscall: + return (read_memory_integer (fr->frame + 8 + oEIP, 4)); +#undef oEIP + } +} + +CORE_ADDR +fbsd_kern_frame_chain (fr) +struct frame_info *fr; +{ + struct minimal_symbol *sym; + CORE_ADDR this_saved_pc; + enum frametype frametype; + + this_saved_pc = read_memory_integer (fr->frame + 4, 4); + sym = lookup_minimal_symbol_by_pc (this_saved_pc); + frametype = tf_normal; + if (sym != NULL) { + if (strcmp (SYMBOL_NAME(sym), "calltrap") == 0) + frametype = tf_trap; + else if (strncmp (SYMBOL_NAME(sym), "Xresume", 7) == 0) + frametype = tf_interrupt; + else if (strcmp (SYMBOL_NAME(sym), "_Xsyscall") == 0) + frametype = tf_syscall; + } + + switch (frametype) { + case tf_normal: + return (read_memory_integer (fr->frame, 4)); + +#define oEBP offsetof(struct trapframe, tf_ebp) + + case tf_trap: + return (read_memory_integer (fr->frame + 8 + oEBP, 4)); + + case tf_interrupt: + return (read_memory_integer (fr->frame + 16 + oEBP, 4)); + + case tf_syscall: + return (read_memory_integer (fr->frame + 8 + oEBP, 4)); +#undef oEBP + } +} + static CORE_ADDR ksym_lookup (name) diff -u -r1.1 -r1.2 --- tm-fbsd.h 1996/09/30 21:04:48 1.1 +++ tm-fbsd.h 1996/10/01 18:54:36 1.2 @@ -35,4 +35,30 @@ #define IN_SOLIB_CALL_TRAMPOLINE(pc, name) STREQ (name, "_DYNAMIC") +/* FRAME_CHAIN takes a frame's nominal address and produces the frame's + chain-pointer. + In the case of the i386, the frame's nominal address + is the address of a 4-byte word containing the calling frame's address. */ + +extern CORE_ADDR fbsd_kern_frame_chain (struct frame_info *); +#undef FRAME_CHAIN +#define FRAME_CHAIN(thisframe) \ + (kernel_debugging ? fbsd_kern_frame_chain(thisframe) : \ + ((thisframe)->signal_handler_caller \ + ? (thisframe)->frame \ + : (!inside_entry_file ((thisframe)->pc) \ + ? read_memory_integer ((thisframe)->frame, 4) \ + : 0))) + +/* Saved Pc. Get it from sigcontext if within sigtramp. */ + +extern CORE_ADDR fbsd_kern_frame_saved_pc (struct frame_info *); +#undef FRAME_SAVED_PC +#define FRAME_SAVED_PC(FRAME) \ + (kernel_debugging ? fbsd_kern_frame_saved_pc(FRAME) : \ + (((FRAME)->signal_handler_caller \ + ? sigtramp_saved_pc (FRAME) \ + : read_memory_integer ((FRAME)->frame + 4, 4)) \ + )) + #endif /* TM_FBSD_H */ From owner-freebsd-current Tue Oct 1 14:45:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA29201 for current-outgoing; Tue, 1 Oct 1996 14:45:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA29183; Tue, 1 Oct 1996 14:44:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA02547; Tue, 1 Oct 1996 14:43:33 -0700 From: Terry Lambert Message-Id: <199610012143.OAA02547@phaeton.artisoft.com> Subject: Re: WARNING: botched ld.so commit! :-( To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Tue, 1 Oct 1996 14:43:33 -0700 (MST) Cc: peter@spinner.DIALix.COM, sos@freebsd.org, current@freebsd.org In-Reply-To: <11648.844179448@critter.tfs.com> from "Poul-Henning Kamp" at Oct 1, 96 04:17:28 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 > >(I think I'll leave for Antarctica before anybody catches me... :-] ) > > > > I belive I have positive confirmation of at least one FreeBSD laptop > down there already :-) There is a 486DX/2-66 running FreeBSD at Amundsen station (yes, I tend to keep track of people who post and where they post from). 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 Tue Oct 1 14:49:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA29697 for current-outgoing; Tue, 1 Oct 1996 14:49:43 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA29683; Tue, 1 Oct 1996 14:49:37 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA02571; Tue, 1 Oct 1996 14:47:39 -0700 From: Terry Lambert Message-Id: <199610012147.OAA02571@phaeton.artisoft.com> Subject: Re: Your UserConfig changes for unmasking PCI devices... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 1 Oct 1996 14:47:39 -0700 (MST) Cc: msmith@atrad.adelaide.edu.au, bde@FreeBSD.org, current@FreeBSD.org In-Reply-To: <15887.844169929@time.cdrom.com> from "Jordan K. Hubbard" at Oct 1, 96 04:38:49 am 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 > > Ah, how about putting off calling userconfig() until after the PCI and > > EISA probes? Since it's only _really_ relevant to the ISA probe > > process, shouldn't it be directly associated with it? > > If this doesn't have any unwonted side-effects, sure! I believe it would have the side effect of making relocatable PCI devices immovable, potentially resulting in name space (DMA, IRQ, MEM) conflits with ISA device that would require physically openning the machine to fix. This is the problem with continuing to support ISA in otherwise decent hardware designs. I suspect that the best compromise would be to leave it alone (since it is just noisy, not harmful) until the bus probes can be completely seperated from the bus drivers. This would let you only put up PCI messages when a PCI bus is found (or EISA for EISA, PCMCIA for PCMCIA, etc.). 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 Tue Oct 1 14:52:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00148 for current-outgoing; Tue, 1 Oct 1996 14:52:52 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA00127 for ; Tue, 1 Oct 1996 14:52:45 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA02594; Tue, 1 Oct 1996 14:51:34 -0700 From: Terry Lambert Message-Id: <199610012151.OAA02594@phaeton.artisoft.com> Subject: Re: WARNING: botched ld.so commit! :-( To: jdp@polstra.com (John Polstra) Date: Tue, 1 Oct 1996 14:51:34 -0700 (MST) Cc: current@FreeBSD.ORG In-Reply-To: <199610011615.JAA03350@austin.polstra.com> from "John Polstra" at Oct 1, 96 09:15:40 am 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 > > Even I don't touch rtld :-). Scary thought if I worked on it :-). > > Just to reinforce that sentiment, I worked on rtld for a while, and it's > nerve-wracking! It's like trying to replace a rope that you and the > rest of the world are hanging from. (By the neck, if you screw up.) > > I think we all know Peter well enough to forego giving him too much > flack over this. (Same goes for John Dyson and the occasional > hiccups that come with the great things he's doing for us.) For what it's worth: a correct ELF implemented is expected to have the kernel execution class loader map the ld.so into the process address space instead of relying on the crt0.o to do it for you. That's the reason for the "large enough" offset at the start of the SVR4 EABI specification prior to the image mapping location. Going to something like this would allow the kernel to automatically establish correct versioning, and you could overrride using userconfig in case you *really* screwed up. 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 Tue Oct 1 18:27:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18290 for current-outgoing; Tue, 1 Oct 1996 18:27:23 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA18283; Tue, 1 Oct 1996 18:27:20 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id BAA01798; Wed, 2 Oct 1996 01:25:43 GMT Date: Wed, 2 Oct 1996 10:25:43 +0900 (JST) From: Michael Hancock To: Bruce Evans cc: peter@spinner.DIALix.COM, sos@freebsd.org, current@freebsd.org Subject: Re: WARNING: botched ld.so commit! :-( In-Reply-To: <199610011435.AAA32208@godzilla.zeta.org.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 On Wed, 2 Oct 1996, Bruce Evans wrote: > This shows that the chflags on ld.so is mainly to [prevent] shoot[ing] > yourself in the foot. It doesn't improve security. > I was thinking of asking why we're evening using it when INITIAL_IMMUTABLE_LEVEL is not configurable without hardcoding the source. Regards, Mike From owner-freebsd-current Tue Oct 1 18:47:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA19693 for current-outgoing; Tue, 1 Oct 1996 18:47:36 -0700 (PDT) Received: from Central.KeyWest.MPGN.COM (Central.TanSoft.COM [206.175.4.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA19687 for ; Tue, 1 Oct 1996 18:47:33 -0700 (PDT) Received: (from rwm@localhost) by Central.KeyWest.MPGN.COM (8.6.9/8.6.9) id VAA18241 for freebsd-current@freebsd.org; Tue, 1 Oct 1996 21:46:36 -0400 From: Rob Miracle Message-Id: <199610020146.VAA18241@Central.KeyWest.MPGN.COM> Subject: Keeping up with this thing To: freebsd-current@freebsd.org Date: Tue, 1 Oct 1996 21:46:35 -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 I read the FAQ and the handbook and I still have some confusion about how to keep my system semi recent without catching things in a state of flux. For example I grabbed the source tree off of ftp.freebsd.org this morning. I tried a make world and it blew up compiling the cc compiler when the prototypes in the contrib/gcc directory differed from the actual source in /usr/src/gnu/usr.bin/blah blah blah. I understand fully that copying from that source may lead to headaches and that "sup" and the cvs trees are better. The thing is I don't have a lot of time to play with figuring out how to use sup and cvs. So I guess I am requesting a supfile and set of commands where I can fetch the recently changed files in a compilable version of the system. While I realize that Freebsd-stable is probably more for what kind of updates we need, we are unfortunatly wanting to try out the SMP kernel and have some other needs addressed by 2.2. So maybe if someone could explain this in a bit clearer sense and provide some real world examples of using sup and cvs to keep my system upto date with the most recent compilable version I would greatly appreciate it. Thanks Rob -- Rob Miracle rwm@mpgn.com for webmaster@mpgn.com From owner-freebsd-current Tue Oct 1 19:02:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA20797 for current-outgoing; Tue, 1 Oct 1996 19:02:01 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA20785; Tue, 1 Oct 1996 19:01:57 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA17100; Wed, 2 Oct 1996 11:30:29 +0930 From: Michael Smith Message-Id: <199610020200.LAA17100@genesis.atrad.adelaide.edu.au> Subject: Re: Your UserConfig changes for unmasking PCI devices... To: terry@lambert.org (Terry Lambert) Date: Wed, 2 Oct 1996 11:30:29 +0930 (CST) Cc: jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au, bde@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199610012147.OAA02571@phaeton.artisoft.com> from "Terry Lambert" at Oct 1, 96 02:47:39 pm 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 Terry Lambert stands accused of saying: > > > > Ah, how about putting off calling userconfig() until after the PCI and > > > EISA probes? Since it's only _really_ relevant to the ISA probe > > > process, shouldn't it be directly associated with it? > > > > If this doesn't have any unwonted side-effects, sure! > > I believe it would have the side effect of making relocatable PCI > devices immovable, potentially resulting in name space (DMA, IRQ, MEM) > conflits with ISA device that would require physically openning the > machine to fix. Huh? What crap is this? Moving userconfig close to the ISA probes has nothing to do with whether "potentially relocatable" PCI devices can be stuck sideways up the user's nostril. Unless/until the PCI support code starts taking over from the BIOS in regard to controlling IRQ mapping across PCI-ISA bridges, the space from which PCI devices can be allocated IRQs cannot (by definition) overlap with the IRQ which are available to ISA devices. Under this scheme, if an ISA device is misconfigured (ie. it has an IRQ that is free for use by a PCI device), it's gonna stay misconfigured until it's manually corrected, regardless of at which point in the boot process the user is offered the option of changing the parameters for the driver which may end up talking to it. > This is the problem with continuing to support ISA in otherwise decent > hardware designs. And fire is hot. Care to wave any other examples of the bleedin' obvious around? Regardless, some people are actually making headway with this sort of thing. I'm loth to do much more with userconfig because it's the wrong way to go. I'm watching GRUB with mild interest, but I think it doesn't go far enough. > I suspect that the best compromise would be to leave it alone (since it > is just noisy, not harmful) until the bus probes can be completely > seperated from the bus drivers. This would let you only put up PCI > messages when a PCI bus is found (or EISA for EISA, PCMCIA for PCMCIA, > etc.). The idea of seperating the probe and attach/support code for a driver, or at least making them seperately callable, is very attractive. If we ever go for a kernel approach where the last-stage loader (I call it "strap" in what passes for my grand plan) has BIOS access to the disk and assembles the kernel (maybe from ELF segments) in memory before launching it, then this will be a useful and wonderful thing. But all this has been done to death already. > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Tue Oct 1 19:13:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA21459 for current-outgoing; Tue, 1 Oct 1996 19:13:47 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA21454; Tue, 1 Oct 1996 19:13:42 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA03048; Tue, 1 Oct 1996 19:11:48 -0700 From: Terry Lambert Message-Id: <199610020211.TAA03048@phaeton.artisoft.com> Subject: Re: Your UserConfig changes for unmasking PCI devices... To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Tue, 1 Oct 1996 19:11:48 -0700 (MST) Cc: terry@lambert.org, jkh@time.cdrom.com, msmith@atrad.adelaide.edu.au, bde@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199610020200.LAA17100@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 2, 96 11:30:29 am 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 > > > If this doesn't have any unwonted side-effects, sure! > > > > I believe it would have the side effect of making relocatable PCI > > devices immovable, potentially resulting in name space (DMA, IRQ, MEM) > > conflits with ISA device that would require physically openning the > > machine to fix. > > Huh? What crap is this? Moving userconfig close to the ISA probes has > nothing to do with whether "potentially relocatable" PCI devices can > be stuck sideways up the user's nostril. > > Unless/until the PCI support code starts taking over from the BIOS in > regard to controlling IRQ mapping across PCI-ISA bridges, the space > from which PCI devices can be allocated IRQs cannot (by definition) > overlap with the IRQ which are available to ISA devices. Under this > scheme, if an ISA device is misconfigured (ie. it has an IRQ that is > free for use by a PCI device), it's gonna stay misconfigured until > it's manually corrected, regardless of at which point in the boot > process the user is offered the option of changing the parameters for the > driver which may end up talking to it. Obviously, the PCI support code wants to be able to relocate PCI devices. In general, BIOS is too stupid to set up PCI to avoid existing ISA devices bridged on the motherboard, let alone ISA device you plug in (like, oh, say, a GUS card). > > This is the problem with continuing to support ISA in otherwise decent > > hardware designs. > > And fire is hot. Care to wave any other examples of the bleedin' obvious > around? Regardless, some people are actually making headway with this > sort of thing. I'm loth to do much more with userconfig because it's > the wrong way to go. I'm watching GRUB with mild interest, but I think > it doesn't go far enough. GRUB is interesting. OpenBoot is more interesting. Passive PCI backplane based hardware is most interesting. > > I suspect that the best compromise would be to leave it alone (since it > > is just noisy, not harmful) until the bus probes can be completely > > seperated from the bus drivers. This would let you only put up PCI > > messages when a PCI bus is found (or EISA for EISA, PCMCIA for PCMCIA, > > etc.). > > The idea of seperating the probe and attach/support code for a driver, > or at least making them seperately callable, is very attractive. If > we ever go for a kernel approach where the last-stage loader (I call > it "strap" in what passes for my grand plan) has BIOS access to the > disk and assembles the kernel (maybe from ELF segments) in memory > before launching it, then this will be a useful and wonderful thing. Yeah; I'm not holding my breath. 8-). > But all this has been done to death already. Yes, it has, which is why disabling the PCI messages (which would otherwise encourage fixing things The Right Way 8-)) would be A Bad Thing. 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 Tue Oct 1 19:17:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA21667 for current-outgoing; Tue, 1 Oct 1996 19:17:27 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA21647; Tue, 1 Oct 1996 19:17:22 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id TAA04685; Tue, 1 Oct 1996 19:16:11 -0700 (PDT) To: Terry Lambert cc: msmith@atrad.adelaide.edu.au (Michael Smith), bde@FreeBSD.org, current@FreeBSD.org Subject: Re: Your UserConfig changes for unmasking PCI devices... In-reply-to: Your message of "Tue, 01 Oct 1996 19:11:48 PDT." <199610020211.TAA03048@phaeton.artisoft.com> Date: Tue, 01 Oct 1996 19:16:10 -0700 Message-ID: <4682.844222570@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Yes, it has, which is why disabling the PCI messages (which would otherwise > encourage fixing things The Right Way 8-)) would be A Bad Thing. PCI probe messages or entries in UserConfig? I can tell you that the latter is just about driving me spare - there's a big difference between conceptual elegance and usability, and the UserConfig of today is far less useful than it was 2 days ago, when I didn't have to skip around all this junk just to set up my ISA cards. Jordan From owner-freebsd-current Tue Oct 1 20:52:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA27700 for current-outgoing; Tue, 1 Oct 1996 20:52:32 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA27691 for ; Tue, 1 Oct 1996 20:52:27 -0700 (PDT) Received: from gilligan.eng.umd.edu (gilligan.eng.umd.edu [129.2.103.21]) by po1.glue.umd.edu (8.8.Gamma.0/8.7.3) with ESMTP id XAA20673 for ; Tue, 1 Oct 1996 23:52:23 -0400 (EDT) Received: from localhost (chuckr@localhost) by gilligan.eng.umd.edu (8.7.5/8.7.3) with SMTP id XAA29910 for ; Tue, 1 Oct 1996 23:52:23 -0400 (EDT) X-Authentication-Warning: gilligan.eng.umd.edu: chuckr owned process doing -bs Date: Tue, 1 Oct 1996 23:52:23 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@gilligan.eng.umd.edu To: FreeBSD current Subject: contrib/src 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 noticed that large parts of FreeBSD are making their way into contrib/src, including stuff I would not have thought really qualified as contributed. As an example, bin/cat is now located in /usr/src/contrib/src/bin/cat. Has the definition of contributed software been expanded? Or maybe I should ask what the definition is? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Tue Oct 1 23:16:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA10017 for current-outgoing; Tue, 1 Oct 1996 23:16:54 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA10008 for ; Tue, 1 Oct 1996 23:16:49 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.6/8.7.3) with ESMTP id IAA28306; Wed, 2 Oct 1996 08:16:34 +0200 (SAT) Message-Id: <199610020616.IAA28306@grumble.grondar.za> To: Chuck Robey cc: FreeBSD current Subject: Re: contrib/src Date: Wed, 02 Oct 1996 08:16:33 +0200 From: Mark Murray Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chuck Robey wrote: > I noticed that large parts of FreeBSD are making their way into > contrib/src, including stuff I would not have thought really qualified as > contributed. As an example, bin/cat is now located in > /usr/src/contrib/src/bin/cat. Has the definition of contributed software > been expanded? Or maybe I should ask what the definition is? There is something wrong on your system - perhaps a missing / in a supfile. On my copy of the CVS tree, bin/cat is in the right place. I don't even have a contrib/src directory, so that should give you a hint :-) M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Tue Oct 1 23:20:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA10298 for current-outgoing; Tue, 1 Oct 1996 23:20:04 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA10244; Tue, 1 Oct 1996 23:19:58 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id IAA01518; Wed, 2 Oct 1996 08:19:05 +0200 (MET DST) To: Terry Lambert cc: peter@spinner.DIALix.COM, sos@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: WARNING: botched ld.so commit! :-( In-reply-to: Your message of "Tue, 01 Oct 1996 14:43:33 PDT." <199610012143.OAA02547@phaeton.artisoft.com> Date: Wed, 02 Oct 1996 08:19:04 +0200 Message-ID: <1512.844237144@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199610012143.OAA02547@phaeton.artisoft.com>, Terry Lambert writes: >> >(I think I'll leave for Antarctica before anybody catches me... :-] ) >> > >> >> I belive I have positive confirmation of at least one FreeBSD laptop >> down there already :-) > >There is a 486DX/2-66 running FreeBSD at Amundsen station (yes, I tend >to keep track of people who post and where they post from). > "FreeBSD -- It's all over the place..." Ok, who's the first to get a FreeBSD launched into space ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Tue Oct 1 23:20:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA10421 for current-outgoing; Tue, 1 Oct 1996 23:20:33 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA10414 for ; Tue, 1 Oct 1996 23:20:30 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id XAA07334; Tue, 1 Oct 1996 23:20:20 -0700 (PDT) Message-Id: <199610020620.XAA07334@austin.polstra.com> To: chuckr@glue.umd.edu Cc: freebsd-current@freefall.freebsd.org Subject: Re: contrib/src In-reply-to: Date: Tue, 01 Oct 1996 23:20:20 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I noticed that large parts of FreeBSD are making their way into > contrib/src, including stuff I would not have thought really > qualified as contributed. As an example, bin/cat is now located > in /usr/src/contrib/src/bin/cat. Huh?! Which sources are you looking at? In the CVS repository on freefall, bin/cat is where it's always been. And there is no subdirectory named "src" in /home/ncvs/src/contrib. The -current tree on freefall (in "/c/src") looks consistent with the repository, too. John -- 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 Wed Oct 2 01:12:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA19552 for current-outgoing; Wed, 2 Oct 1996 01:12:32 -0700 (PDT) Received: from masternet.it (root@masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA19538 for ; Wed, 2 Oct 1996 01:12:27 -0700 (PDT) Received: from gmarco (ts1port10d.masternet.it [194.184.65.32]) by masternet.it (8.6.12/8.6.9) with SMTP id KAA11138 for ; Mon, 2 Oct 1995 10:07:42 +0100 Message-Id: <3.0b26.32.19961002090639.00744b34@masternet.it> X-Sender: gmarco@masternet.it X-Mailer: Windows Eudora Pro Version 3.0b26 (32) Date: Wed, 02 Oct 1996 09:08:41 +0100 To: current@freebsd.org From: Gianmarco Giovannelli Subject: Desperately seeking ctm src-curr.1968 to 2000 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry for the off topics message, but I am looking for some missing ctm files, from src-curr.1968 to src-curr.2000. They are from this summer, when I was off the list . If someone have and want to send to me can attach them to an email (obviusly if it is not a problem). Thanks again to everybody and sorry for the off-topics Regards... +-------------------------------------+--------------------+ | Internet: gmarco@masternet.it | ,,, | | Internet: gmarco@fi.nettuno.it | (o o) | | BIX : ggiovannelli@bix.com | ---oo0-(_)-0oo--- | | http://www.masternet.it/dsc/gmarco | Gianmarco | +-------------------------------------+--------------------+ From owner-freebsd-current Wed Oct 2 01:22:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA20086 for current-outgoing; Wed, 2 Oct 1996 01:22:05 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA20076 for ; Wed, 2 Oct 1996 01:22:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA01304; Wed, 2 Oct 1996 10:21:24 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA03073; Wed, 2 Oct 1996 10:21:19 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id KAA21312; Wed, 2 Oct 1996 10:12:29 +0200 (MET DST) From: J Wunsch Message-Id: <199610020812.KAA21312@uriah.heep.sax.de> Subject: Re: Keeping up with this thing To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 2 Oct 1996 10:12:28 +0200 (MET DST) Cc: rwm@MPGN.COM (Rob Miracle) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199610020146.VAA18241@Central.KeyWest.MPGN.COM> from Rob Miracle at "Oct 1, 96 09:46:35 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 As Rob Miracle wrote: > I read the FAQ and the handbook and I still have some confusion about > how to keep my system semi recent without catching things in a state > of flux. By subscribing to freebsd-current@freebsd.org, and rebuilding the systems only if you are feeling that the chances for a working environment are good. Sacrifice the disk space for the CVS tree. This gives you the option to update parts of the system to a known date, or to pull just a single fix that you are seriously needing, without risking too much by upgrading everything. If you want a stable system, never upgrade, but only apply those bug fixes you know you need. ;-) -- 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 Wed Oct 2 02:00:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA22256 for current-outgoing; Wed, 2 Oct 1996 02:00:00 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA22251 for ; Wed, 2 Oct 1996 01:59:58 -0700 (PDT) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id BAA25356 for ; Wed, 2 Oct 1996 01:58:07 -0700 (PDT) Received: (from bsdcur@localhost) by shadows.aeon.net (8.7.5/8.6.9) id LAA13469 for freebsd-current@freebsd.org; Wed, 2 Oct 1996 11:48:30 +0200 (EET) From: mika ruohotie Message-Id: <199610020948.LAA13469@shadows.aeon.net> Subject: tacacs and tacacs+ To: freebsd-current@freebsd.org Date: Wed, 2 Oct 1996 11:48:30 +0200 (EET) 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'm still wondering if this works with freebsd-current? (or 2.1.5?) mickey -- mika@aeon.net mika ruohotie net/sys admin From owner-freebsd-current Wed Oct 2 05:51:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA03285 for current-outgoing; Wed, 2 Oct 1996 05:51:01 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA03280 for ; Wed, 2 Oct 1996 05:50:58 -0700 (PDT) Received: from maryann.eng.umd.edu (maryann.eng.umd.edu [129.2.103.22]) by po1.glue.umd.edu (8.8.Gamma.0/8.7.3) with ESMTP id IAA27004; Wed, 2 Oct 1996 08:50:50 -0400 (EDT) Received: from localhost (chuckr@localhost) by maryann.eng.umd.edu (8.7.5/8.7.3) with SMTP id IAA00900; Wed, 2 Oct 1996 08:50:50 -0400 (EDT) X-Authentication-Warning: maryann.eng.umd.edu: chuckr owned process doing -bs Date: Wed, 2 Oct 1996 08:50:49 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@maryann.eng.umd.edu To: Mark Murray cc: FreeBSD current Subject: Re: contrib/src In-Reply-To: <199610020616.IAA28306@grumble.grondar.za> 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 Wed, 2 Oct 1996, Mark Murray wrote: > Chuck Robey wrote: > > I noticed that large parts of FreeBSD are making their way into > > contrib/src, including stuff I would not have thought really qualified as > > contributed. As an example, bin/cat is now located in > > /usr/src/contrib/src/bin/cat. Has the definition of contributed software > > been expanded? Or maybe I should ask what the definition is? > > There is something wrong on your system - perhaps a missing / in a > supfile. On my copy of the CVS tree, bin/cat is in the right place. > I don't even have a contrib/src directory, so that should give you > a hint :-) Thanks, I guess there might be. If it's true, I can guess when it happened ... looks like I'll have to resync my cvs archive, which I keep up via ctm. First corruption I've noticed. > > M > -- > Mark Murray > 46 Harvey Rd, Claremont, Cape Town 7700, South Africa > +27 21 61-3768 GMT+0200 > Finger mark@grondar.za for PGP key > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Wed Oct 2 07:41:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA12308 for current-outgoing; Wed, 2 Oct 1996 07:41:52 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA12299 for ; Wed, 2 Oct 1996 07:41:47 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA28734; Wed, 2 Oct 1996 10:41:41 -0400 Date: Wed, 2 Oct 1996 10:41:41 -0400 From: Garrett Wollman Message-Id: <9610021441.AA28734@halloran-eldar.lcs.mit.edu> To: Michael Hancock Cc: current@freebsd.org Subject: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: References: <199610011435.AAA32208@godzilla.zeta.org.au> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > On Wed, 2 Oct 1996, Bruce Evans wrote: >> This shows that the chflags on ld.so is mainly to [prevent] shoot[ing] >> yourself in the foot. It doesn't improve security. > I was thinking of asking why we're evening using it when > INITIAL_IMMUTABLE_LEVEL is not configurable without hardcoding the source. Ummm, INITIAL_IMMUTABLE_LEVEL? This doesn't mean anything to me. In any case, the immutable bits are set for two reasons: 1) They were set on the code we got from Berkeley. 2) We wanted to make it easier for people to secure their systems by pre-configuring those files. There are a number of files which are necessary for system recovery which probably should be set immutable but aren't; these include /bin/sh, /bin/test, /sbin/fsck, and a number of others. In addition, administrators will have to remember for themselves to set their configuration files immutable and their important system directories append-only, which can only be done after a machine is set up to the administrator's satisfaction. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Wed Oct 2 07:50:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA12857 for current-outgoing; Wed, 2 Oct 1996 07:50:56 -0700 (PDT) Received: from watson.grauel.com (watson.grauel.com [199.233.104.36]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA12851 for ; Wed, 2 Oct 1996 07:50:53 -0700 (PDT) Received: from sparcmill.grauel.com (sparcmill.grauel.com [199.233.104.34]) by watson.grauel.com (8.7.6/8.7.3) with SMTP id JAA10044; Wed, 2 Oct 1996 09:56:24 -0500 (EST) Received: by sparcmill.grauel.com (SMI-8.6/SMI-SVR4) id JAA03710; Wed, 2 Oct 1996 09:51:27 -0500 Date: Wed, 2 Oct 1996 09:51:27 -0500 Message-Id: <199610021451.JAA03710@sparcmill.grauel.com> From: Richard J Kuhns To: Rob Miracle Cc: freebsd-current@FreeBSD.ORG Subject: Keeping up with this thing In-Reply-To: <199610020146.VAA18241@Central.KeyWest.MPGN.COM> References: <199610020146.VAA18241@Central.KeyWest.MPGN.COM> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Rob Miracle writes: > I read the FAQ and the handbook and I still have some confusion about > how to keep my system semi recent without catching things in a state > of flux. For example I grabbed the source tree off of ftp.freebsd.org > this morning. I tried a make world and it blew up compiling the cc > compiler when the prototypes in the contrib/gcc directory differed from > the actual source in /usr/src/gnu/usr.bin/blah blah blah. > > I understand fully that copying from that source may lead to headaches > and that "sup" and the cvs trees are better. The thing is I don't have > a lot of time to play with figuring out how to use sup and cvs. > > So I guess I am requesting a supfile and set of commands where I can > fetch the recently changed files in a compilable version of the system. > While I realize that Freebsd-stable is probably more for what kind of > updates we need, we are unfortunatly wanting to try out the SMP kernel > and have some other needs addressed by 2.2. > > So maybe if someone could explain this in a bit clearer sense and provide > some real world examples of using sup and cvs to keep my system upto date > with the most recent compilable version I would greatly appreciate it. > > Thanks > Rob > FWIW, here's what I've been doing that's (so far) worked out very well. First, I'm using ctm -- I subscribe to the ctm-current mailling list, so I get patches via email several times per day. I usually apply the patches more-or-less immediately, watching the output from ctm. If, for example, the kernel or loader are extensively modified (functionally, that is -- watch the -commits mailling list for details), I'll wait another day or two to give some other sucke^H^H^H^H^H brave soul a chance to rebuild it first. If you've not used it before, ctm is wonderful. To start, ftp to freefall.freebsd.org and find the ctm directory (it may be under /pub/FreeBSD, I'm not sure and can't check right now -- Sprint's having trouble again). Grab the highest-numbered file ending with `A.gz' (about 30 MB) along with all higher-numbered files. In your (empty) src directory, do a `ctm -v files_you_just_grabbed'. That'll build the source tree (that's the 30MB file), and apply all updates since then. Now subscribe to ctm-current and -commits, and enjoy. Just remember two things: 1) you're still not _guarranteed_ a buildable system (tho it almost always is), since -current is a work-in-progress; and 2) if something stops working, let other people know. Hope this helps. -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (317)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / From owner-freebsd-current Wed Oct 2 08:34:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA15960 for current-outgoing; Wed, 2 Oct 1996 08:34:09 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA15953 for ; Wed, 2 Oct 1996 08:34:06 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id IAA25992 for ; Wed, 2 Oct 1996 08:33:59 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA09522; Wed, 2 Oct 1996 09:30:11 -0600 (MDT) Date: Wed, 2 Oct 1996 09:30:11 -0600 (MDT) Message-Id: <199610021530.JAA09522@rocky.mt.sri.com> From: Nate Williams To: Poul-Henning Kamp Cc: current@freebsd.org Subject: It's everywhere, it's everywhere (Was Re: WARNING: botched ld.so ...) In-Reply-To: <1512.844237144@critter.tfs.com> References: <199610012143.OAA02547@phaeton.artisoft.com> <1512.844237144@critter.tfs.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > "FreeBSD -- It's all over the place..." > > Ok, who's the first to get a FreeBSD launched into space ? Send email to handy@sag.space.lockheed.com. He's working on a satellite now, and maybe you can get him to shoot it up there. :) Nate ps. You're welcome Brian. :) From owner-freebsd-current Wed Oct 2 09:08:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA17987 for current-outgoing; Wed, 2 Oct 1996 09:08:27 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA17976; Wed, 2 Oct 1996 09:08:21 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id JAA20950; Wed, 2 Oct 1996 09:06:29 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199610021606.JAA20950@GndRsh.aac.dev.com> Subject: Re: WARNING: botched ld.so commit! :-( In-Reply-To: <1512.844237144@critter.tfs.com> from Poul-Henning Kamp at "Oct 2, 96 08:19:04 am" To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Wed, 2 Oct 1996 09:06:29 -0700 (PDT) Cc: terry@lambert.org, peter@spinner.DIALix.COM, sos@FreeBSD.ORG, current@FreeBSD.ORG 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 > In message <199610012143.OAA02547@phaeton.artisoft.com>, Terry Lambert writes: > >> >(I think I'll leave for Antarctica before anybody catches me... :-] ) > >> > > >> > >> I belive I have positive confirmation of at least one FreeBSD laptop > >> down there already :-) > > > >There is a 486DX/2-66 running FreeBSD at Amundsen station (yes, I tend > >to keep track of people who post and where they post from). > > > > "FreeBSD -- It's all over the place..." > > Ok, who's the first to get a FreeBSD launched into space ? It may not be too far away, both NASA Ames and LMSC Moffet Field are using FreeBSD for some pretty wild stuff.... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Oct 2 10:16:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA21788 for current-outgoing; Wed, 2 Oct 1996 10:16:04 -0700 (PDT) Received: from wwwi.com (root@voltimand.csd.wwwi.com [199.1.92.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA21760 for ; Wed, 2 Oct 1996 10:15:57 -0700 (PDT) Received: from cornelius (cornelius.csd.wwwi.com [199.1.92.20]) by wwwi.com (8.7.5/8.7.3) with SMTP id KAA29070; Wed, 2 Oct 1996 10:11:53 -0700 (MST) Date: Wed, 2 Oct 1996 10:11:53 -0700 (MST) Message-Id: <199610021711.KAA29070@wwwi.com> X-Sender: jdw@pop.wwwi.com X-Mailer: Windows Eudora Pro Version 2.1.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: mika ruohotie , freebsd-current@freebsd.org From: "Jeffrey D. Wheelhouse" Subject: Re: tacacs and tacacs+ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've successfully used TACACS+ with 2.1.5. Later, Jeff At 11:48 AM 10/2/96 +0200, mika ruohotie wrote: >i'm still wondering if this works with freebsd-current? (or 2.1.5?) > > >mickey >-- > mika@aeon.net mika ruohotie net/sys admin > > From owner-freebsd-current Wed Oct 2 12:34:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00644 for current-outgoing; Wed, 2 Oct 1996 12:34:30 -0700 (PDT) Received: from spinner.DIALix.COM (root@spinner.DIALix.COM [192.203.228.67]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA00633 for ; Wed, 2 Oct 1996 12:34:25 -0700 (PDT) Received: from spinner.DIALix.COM (peter@localhost.DIALix.oz.au [127.0.0.1]) by spinner.DIALix.COM (8.8.0/8.8.0) with ESMTP id DAA00393 for ; Thu, 3 Oct 1996 03:34:21 +0800 (WST) Message-Id: <199610021934.DAA00393@spinner.DIALix.COM> To: current@freebsd.org Subject: ETA for libg++-2.7.2 between 12 and 24 hours Date: Thu, 03 Oct 1996 03:34:20 +0800 From: Peter Wemm Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think I've finally finished it. I've not tested many canonical C++ programs to make sure they link, but it pretty well builds OK now. Some "highlights" of the experience: - the exception code in g++ appears very buggy. It generates invalid assembler code in -fpic mode... (how can you have something in the Global Offset Table(GOT) if it's not global?) - gas attempted to deal with this, but got it wrong. - ld dumped core when faced with gas's workaround. - bsd.lib.mk is driving me *insane*. libstdc++ needs a lot of different compiler options for different files, bsd.lib.mk doesn't handle this so you have to copy out the default rules three times over (one normal, one pic, one profiled) - the standard configure scripts seem to freak out when running with --srcdir (which I was using to seperate the sources from the test build I did to see how it worked), and since I was using the generated file lists and Makefiles from the output of configure I got burned by only being told about a subset of the files and had to start some of it again. - some of the libstdc++ files are compiled several times with different compiler options each time. Sigh. At least it compiles cleanly, unlike the old libg++ in the tree. BTW, does anybody use genclass? The old version in the tree was missing it, is it worth getting it going? I'll be doing this sometime tomorrow (my time) after I've had some sleep and tested a 'make world' (and implicitly, groff which is a C++ beast). It's pretty big.. I do not know that I can trim the disk space down too much without risking breaking the stand-alone compile: (ie: cd src/contrib/libg++; ./configure).. Perhaps the saved disk space would be worth it though. -Peter From owner-freebsd-current Wed Oct 2 12:50:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01424 for current-outgoing; Wed, 2 Oct 1996 12:50:27 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01419 for ; Wed, 2 Oct 1996 12:50:22 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id MAA23098 for ; Wed, 2 Oct 1996 12:50:19 -0700 (PDT) Date: Wed, 2 Oct 1996 12:49:57 -0700 (PDT) From: Tom Bartol To: current@FreeBSD.org Subject: make world fails during gcc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I'm new to this game so it might be a problem on this end but... I just supped the latest -current from sup.freebsd.org minutes ago (with make update) and then during make world I get a failure with the output below during the make of gcc. This the first time I've tried to sup -current but I've followed the directions carefully. Any help would be greatly appreciated. Thanks, Tom Here's the snippet leading up to the failure: ===> cc_int rm -f .depend mkdep -f .depend -a -DFREEBSD_AOUT -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.1\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools /usr/src/gnu/usr.bin/cc/cc_int/bc-emit.c /usr/src/gnu/usr.bin/cc/cc_int/bc-optab.c /usr/src/gnu/usr.bin/cc/cc_int/c-common.c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-pragma.c /usr/src/gnu/usr.bin/cc/cc_int/caller-save.c /usr/src/gnu/usr.bin/cc/cc_int/calls.c /usr/src/gnu/usr.bin/cc/cc_int/combine.c /usr/src/gnu/usr.bin/cc/cc_int/convert.c /usr/src/gnu/usr.bin/cc/cc_int/cse.c /usr/src/gnu/usr.bin/cc/cc_int/dbxout.c /usr/src/gnu/usr.bin/cc/cc_int/dwarfout.c /usr/src/gnu/usr.bin/cc/cc_int/emit-rtl.c /usr/src/gnu/usr.bin/cc/cc_int/explow.c /usr/src/gnu/usr.bin/cc/cc_int/expmed.c /usr/src/gnu/usr.bin/cc/cc_int/expr.c /usr/src/gnu/usr.bin/cc/cc_int/final.c /usr/src/gnu/usr.bin/cc/cc_int/flow.c /usr/src/gnu/usr.bin/cc/cc_int/fold-const.c /usr/src/gnu/usr.bin/cc/cc_int/function.c /usr/src/gnu/usr.bin/cc/cc_int/getpwd.c /usr/src/gnu/usr.bin/cc/cc_int/global.c /usr/src/gnu/usr.bin/cc/cc_int/insn-attrtab.c /usr/src/gnu/usr.bin/cc/cc_int/insn-emit.c /usr/src/gnu/usr.bin/cc/cc_int/insn-extract.c /usr/src/gnu/usr.bin/cc/cc_int/insn-opinit.c /usr/src/gnu/usr.bin/cc/cc_int/insn-output.c /usr/src/gnu/usr.bin/cc/cc_int/insn-peep.c /usr/src/gnu/usr.bin/cc/cc_int/insn-recog.c /usr/src/gnu/usr.bin/cc/cc_int/integrate.c /usr/src/gnu/usr.bin/cc/cc_int/jump.c /usr/src/gnu/usr.bin/cc/cc_int/local-alloc.c /usr/src/gnu/usr.bin/cc/cc_int/loop.c /usr/src/gnu/usr.bin/cc/cc_int/obstack.c /usr/src/gnu/usr.bin/cc/cc_int/optabs.c /usr/src/gnu/usr.bin/cc/cc_int/print-rtl.c /usr/src/gnu/usr.bin/cc/cc_int/print-tree.c /usr/src/gnu/usr.bin/cc/cc_int/real.c /usr/src/gnu/usr.bin/cc/cc_int/recog.c /usr/src/gnu/usr.bin/cc/cc_int/reg-stack.c /usr/src/gnu/usr.bin/cc/cc_int/regclass.c /usr/src/gnu/usr.bin/cc/cc_int/reload.c /usr/src/gnu/usr.bin/cc/cc_int/reload1.c /usr/src/gnu/usr.bin/cc/cc_int/reorg.c /usr/src/gnu/usr.bin/cc/cc_int/rtl.c /usr/src/gnu/usr.bin/cc/cc_int/rtlanal.c /usr/src/gnu/usr.bin/cc/cc_int/sched.c /usr/src/gnu/usr.bin/cc/cc_int/sdbout.c /usr/src/gnu/usr.bin/cc/cc_int/stmt.c /usr/src/gnu/usr.bin/cc/cc_int/stor-layout.c /usr/src/gnu/usr.bin/cc/cc_int/stupid.c /usr/src/gnu/usr.bin/cc/cc_int/toplev.c /usr/src/gnu/usr.bin/cc/cc_int/tree.c /usr/src/gnu/usr.bin/cc/cc_int/unroll.c /usr/src/gnu/usr.bin/cc/cc_int/varasm.c /usr/src/gnu/usr.bin/cc/cc_int/version.c /usr/src/gnu/usr.bin/cc/cc_int/xcoffout.c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config/i386/i386.c /usr/src/gnu/usr.bin/cc/cc_int/calls.c:366: macro `RETURN_POPS_ARGS' used with only 2 args /usr/src/gnu/usr.bin/cc/cc_int/calls.c:368: macro `RETURN_POPS_ARGS' used with only 2 args /usr/src/gnu/usr.bin/cc/cc_int/calls.c:445: macro `RETURN_POPS_ARGS' used with only 2 args /usr/src/gnu/usr.bin/cc/cc_int/calls.c:452: macro `RETURN_POPS_ARGS' used with only 2 args /usr/src/gnu/usr.bin/cc/cc_int/function.c:3846: macro `RETURN_POPS_ARGS' used with only 2 args mkdep: compile failed. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. From owner-freebsd-current Wed Oct 2 14:30:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08435 for current-outgoing; Wed, 2 Oct 1996 14:30:43 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA08425 for ; Wed, 2 Oct 1996 14:30:36 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id VAA10921; Wed, 2 Oct 1996 21:30:23 GMT Date: Thu, 3 Oct 1996 06:30:22 +0900 (JST) From: Michael Hancock To: Garrett Wollman cc: current@freebsd.org Subject: Re: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: <9610021441.AA28734@halloran-eldar.lcs.mit.edu> 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 Wed, 2 Oct 1996, Garrett Wollman wrote: > Ummm, INITIAL_IMMUTABLE_LEVEL? This doesn't mean anything to me. It was just a suggestion for a kernel config opt. BSDI and NetBSD uses INSECURE, but this convention would surprise many people. I would like to have an option, I don't really care what it is called. /kernel is marked immutable. I'd like to be able to configure systems such that you can't change the flags unless you are in single user mode even if you're root. Regards, Mike Hancock From owner-freebsd-current Wed Oct 2 15:00:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA10060 for current-outgoing; Wed, 2 Oct 1996 15:00:11 -0700 (PDT) Received: from shogun.tdktca.com ([206.26.1.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA10048 for ; Wed, 2 Oct 1996 15:00:05 -0700 (PDT) Received: from shogun.tdktca.com (daemon@localhost) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id RAA20666 for ; Wed, 2 Oct 1996 17:00:03 -0500 (CDT) Received: from fa.tdktca.com (bsd.fa.tdktca.com [163.49.131.129]) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id RAA20659 for ; Wed, 2 Oct 1996 17:00:02 -0500 (CDT) Received: (from alex@localhost) by fa.tdktca.com (8.7.5/8.6.12) id RAA19676; Wed, 2 Oct 1996 17:01:07 -0500 (CDT) Date: Wed, 2 Oct 1996 17:01:07 -0500 (CDT) From: Alex Nash To: Michael Hancock cc: Garrett Wollman , current@freebsd.org Subject: Re: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: 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 Thu, 3 Oct 1996, Michael Hancock wrote: > On Wed, 2 Oct 1996, Garrett Wollman wrote: > > > Ummm, INITIAL_IMMUTABLE_LEVEL? This doesn't mean anything to me. > > It was just a suggestion for a kernel config opt. > > BSDI and NetBSD uses INSECURE, but this convention would surprise many > people. I would like to have an option, I don't really care what it is > called. > > /kernel is marked immutable. I'd like to be able to configure systems > such that you can't change the flags unless you are in single user mode > even if you're root. I believe you can do this by booting up with securelevel == 0 (as opposed to the default of -1). When the system switches to multi-user mode, init upgrades securelevel to 1, preventing the immutable flags from being changed. When downgraded to single-user mode, init changes securelevel back to 0, allowing you to alter the immutable flags. Alex From owner-freebsd-current Wed Oct 2 15:06:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA10460 for current-outgoing; Wed, 2 Oct 1996 15:06:52 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA10453; Wed, 2 Oct 1996 15:06:46 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA04913; Wed, 2 Oct 1996 15:05:03 -0700 From: Terry Lambert Message-Id: <199610022205.PAA04913@phaeton.artisoft.com> Subject: Re: WARNING: botched ld.so commit! :-( To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Wed, 2 Oct 1996 15:05:03 -0700 (MST) Cc: terry@lambert.org, peter@spinner.DIALix.COM, sos@FreeBSD.org, current@FreeBSD.org In-Reply-To: <1512.844237144@critter.tfs.com> from "Poul-Henning Kamp" at Oct 2, 96 08:19:04 am 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 > "FreeBSD -- It's all over the place..." > > Ok, who's the first to get a FreeBSD launched into space ? NASA? 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 Wed Oct 2 16:12:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA13803 for current-outgoing; Wed, 2 Oct 1996 16:12:16 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA13791 for ; Wed, 2 Oct 1996 16:12:11 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id QAA25170; Wed, 2 Oct 1996 16:12:03 -0700 (PDT) Date: Wed, 2 Oct 1996 16:11:40 -0700 (PDT) From: Tom Bartol To: Michael Hancock cc: Garrett Wollman , current@freebsd.org Subject: Re: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: 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 Thu, 3 Oct 1996, Michael Hancock wrote: > On Wed, 2 Oct 1996, Garrett Wollman wrote: > > > Ummm, INITIAL_IMMUTABLE_LEVEL? This doesn't mean anything to me. > > It was just a suggestion for a kernel config opt. > > BSDI and NetBSD uses INSECURE, but this convention would surprise many > people. I would like to have an option, I don't really care what it is > called. > > /kernel is marked immutable. I'd like to be able to configure systems > such that you can't change the flags unless you are in single user mode > even if you're root. > I think this is an excellent idea! Tom From owner-freebsd-current Wed Oct 2 18:20:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA19577 for current-outgoing; Wed, 2 Oct 1996 18:20:42 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA19563; Wed, 2 Oct 1996 18:20:40 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id SAA28269; Wed, 2 Oct 1996 18:20:39 -0700 (PDT) To: bde@freebsd.org cc: current@freebsd.org, phk@freebsd.org Subject: Weird boot problem we've picked up post-2.1-RELEASE Date: Wed, 02 Oct 1996 18:20:39 -0700 Message-ID: <28267.844305639@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The following error report: >From: matt@bdd.net (Matthew Stein) >Organization: ButtonDown Digital > >I've installed FreeBSD 2.2-960801-SNAP on a machine which previously ran >FreeBSD without error. Now that I've reinstalled, and changed the boot >drive, I'm at a loss. > >When booting off of /dev/wd1, the boot process stops right after the first >prompt, and scrolls this error repeatedly up the screen. If I enter >"wd(1,a)kernel" at the first prompt, the machine boots perfectly. Has now become something of an unpleasantly recurring theme. One of Walnut Creek CDROM's own Customers From Hell had this problem with a Packard Bell machine, scrolling the "C:0 H:0 S:0" errors right after the boot prompt and then quickly resetting (that's the old bit). That customer, unfortunately, chose to burn his bridges so we won't be talking to him anymore, but Yet Another report from the considerably more cooperative Mischka Hughes says: >Yup - I get the 4 or so lines of boot info then the Boot: prompt, >then I wait 5 secs and then I get the scrolling errors. >If this is consistent with the previous boot.flp then pressing a key >or typing -c will produce the same scroling errors instantly. About his Gateway system. Aleksander Wittlin says much the same thing about his Gateway, though with an interesting "solution" at the end: >Well, I had the same problem with Gateway 2000 P5-100. The floppy >was OK, I tried several ones. And they worked on another PCs. Also >2.1.0 boot floppy worked without problems. > Then I updated the BIOS ROM of my motherboard (Triton rev. 1) >from rev. BR0T 1.005 to BR01.010 (with update files from Gateway 2000 >web site) and bingo. Now the same floppy boots and I can finally install >2.1.5. I still do not understand what was the reason for that error, >but obviously it was not a floppy. In all cases, the 2.1.5 boot floppy was verified to be perfectly correct, it worked in other PCs and, furthermore, the 2.1 boot floppy worked fine where the 2.1.5 version exhibited these symptoms. I've also verified with Mischka that the problem occurs with the latest 2.2 SNAP, so it's still very much there. I know that Aleksander's solution tends to suggest that there are just these Packard Bells and Gateways out there with non-conformant BIOSes, but asking everyone to upgrade their BIOS is not much of a solution, especially when we somehow managed to avoid the problem entirely in 2.1-RELEASE. Any ideas? Jordan From owner-freebsd-current Wed Oct 2 18:26:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA20015 for current-outgoing; Wed, 2 Oct 1996 18:26:39 -0700 (PDT) Received: from alpo.whistle.com (s204m16.whistle.com [207.76.204.16]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA20010; Wed, 2 Oct 1996 18:26:35 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id SAA26533; Wed, 2 Oct 1996 18:25:18 -0700 (PDT) Message-ID: <3253158B.2C67412E@whistle.com> Date: Wed, 02 Oct 1996 18:23:23 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org CC: announce@freebsd.org Subject: 1.4 Beta 1 release of netatalk Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This release compiles and runs "out of the box" with FreeBSD 2.2 -current and any version of such, dated after about Sept 19. (it will compile with earlier versions too but the kernel support will have [more] bugs) It can be found at: ftp://ftp.freebsd.org/pub/FreeBSD/incoming/netatalk-1.4b1.tar.Z ftp://freefall.cdrom.com/incoming/netatalk-1.4b1.tar.Z ftp://terminator.rs.itd.umich.edu/unix/netatalk/netatalk-1.4b1.tar.Z It should be possible to port the netatalk stack from -current back to 2.1.5 with minor work. Just copy /sys/netatalk and fix. Note that under -current the following support has also been added: * ifconfig can add atalk addresses to interfaces and can add 'netranges' * route can add routes to atalk addresses. I personally haven't tried using the machine as an appletalk router so I dont know if that works. * netstat can report on atalk routes, sockets and interface addresses. full appletalk printer support is included, as well as some appletalk debugging support in the form of (aecho) appletalk version of ping is also present as is a full set of man pages by default it installs into /usr/local/atalk/{etc,bin,man,include,lib) some optimisation for FreeBSD might still be done in this part. julian From owner-freebsd-current Wed Oct 2 20:31:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA25598 for current-outgoing; Wed, 2 Oct 1996 20:31:08 -0700 (PDT) Received: from night.primate.wisc.edu (night.primate.wisc.edu [144.92.43.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA25583; Wed, 2 Oct 1996 20:31:02 -0700 (PDT) Received: by night.primate.wisc.edu; id WAA27223; 8.6.10/41.8; Wed, 2 Oct 1996 22:30:58 -0500 Message-Id: <199610030330.WAA27223@night.primate.wisc.edu> Date: Wed, 2 Oct 1996 22:30:58 -0500 From: dubois@primate.wisc.edu (Paul DuBois) To: current@freebsd.org, announce@freebsd.org Subject: Re: 1.4 Beta 1 release of netatalk In-Reply-To: <3253158B.2C67412E@whistle.com>; from Julian Elischer on Oct 2, 1996 18:23:23 -0700 References: <3253158B.2C67412E@whistle.com> X-Mailer: Mutt 0.45 Mime-Version: 1.0 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Julian Elischer writes: > This release compiles and runs "out of the box" with FreeBSD 2.2 > -current and any version of such, dated after about Sept 19. > > (it will compile with earlier versions too but the kernel > support will have [more] bugs) > > It should be possible to port the netatalk stack from -current back to > 2.1.5 with minor work. Just copy /sys/netatalk and fix. If anyone does this, please post a note here! -- Paul DuBois dubois@primate.wisc.edu Home page: http://www.primate.wisc.edu/people/dubois Software: http://www.primate.wisc.edu/software From owner-freebsd-current Wed Oct 2 21:10:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA27576 for current-outgoing; Wed, 2 Oct 1996 21:10:08 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA27566 for ; Wed, 2 Oct 1996 21:10:02 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id EAA13382; Thu, 3 Oct 1996 04:09:43 GMT Date: Thu, 3 Oct 1996 13:09:43 +0900 (JST) From: Michael Hancock To: Alex Nash cc: Garrett Wollman , current@freebsd.org Subject: Re: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: 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 Wed, 2 Oct 1996, Alex Nash wrote: > > /kernel is marked immutable. I'd like to be able to configure systems > > such that you can't change the flags unless you are in single user mode > > even if you're root. > > I believe you can do this by booting up with securelevel == 0 (as opposed > to the default of -1). When the system switches to multi-user mode, init > upgrades securelevel to 1, preventing the immutable flags from being > changed. When downgraded to single-user mode, init changes securelevel > back to 0, allowing you to alter the immutable flags. What am asking for is a kernel config file option so that I don't have to repeatedly edit the source. options INITIAL_SECURE_LEVEL=0 Regards, Mike Hancock From owner-freebsd-current Wed Oct 2 22:39:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA02273 for current-outgoing; Wed, 2 Oct 1996 22:39:34 -0700 (PDT) Received: (from julian@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA02269 for current; Wed, 2 Oct 1996 22:39:33 -0700 (PDT) Date: Wed, 2 Oct 1996 22:39:33 -0700 (PDT) From: Julian Elischer Message-Id: <199610030539.WAA02269@freefall.freebsd.org> To: current Subject: HELP!! kernel deadlock found.. Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Take the following 3 processes: proc N, with a lock on file / (inode 2) wchan of that inode, waitstring of "ufslk2" is waiting for inode for /mnt in the root filesystem (inode M) proc N+1 with a lock on the inode M (/mnt in root filesystem) is waiting for inode for / (inode 2) in the mounted filesystem /mnt it is showing "uihget" as a waitstring. proc N+2 with a lock on inode 2 of the mnt filesystem (/ of that filesystem) is waiting for the inode for / and is showing "ufslk2" as a waitstring. It is my suspicion that process N+2 may be trying to unmount /mnt. Unfortunatly though I have the system stopped in gdb I don't know how to examine the stacktrace of arbitrary processes so I can't say how those 3 processes got where they are. All other processes on the system that need to access the filesystem are locked in "ufslk2" e.g. any new logins go there immediatly. :( if anyone knows how to examine an arbitrary process stacktrace I'd like to hear about it....... I'll leave the system frozen in this state, and I can arange to get other people with internet access to be able to run gdb and examine whatever they want.. David? Terry? John? any takers? I'd love to be able to see what those 3 stack traces show..... julian From owner-freebsd-current Thu Oct 3 03:11:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA18782 for current-outgoing; Thu, 3 Oct 1996 03:11:12 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA18773; Thu, 3 Oct 1996 03:11:09 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id DAA27669 ; Thu, 3 Oct 1996 03:11:05 -0700 (PDT) Received: from minnow.render.com (minnow.render.com [193.195.178.1]) by minnow.render.com (8.6.12/8.6.9) with SMTP id LAA25801; Thu, 3 Oct 1996 11:09:15 +0100 Date: Thu, 3 Oct 1996 11:09:13 +0100 (BST) From: Doug Rabson To: Julian Elischer cc: current@freefall.freebsd.org Subject: Re: HELP!! kernel deadlock found.. In-Reply-To: <199610030539.WAA02269@freefall.freebsd.org> 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 Wed, 2 Oct 1996, Julian Elischer wrote: > > Take the following 3 processes: > > proc N, with a lock on file / (inode 2) > wchan of that inode, waitstring of "ufslk2" > is waiting for inode for /mnt in the root filesystem (inode M) > > proc N+1 with a lock on the inode M (/mnt in root filesystem) > is waiting for inode for / (inode 2) in the mounted filesystem /mnt > it is showing "uihget" as a waitstring. > > proc N+2 with a lock on inode 2 of the mnt filesystem (/ of that filesystem) > is waiting for the inode for / and is showing "ufslk2" as a waitstring. > > It is my suspicion that process N+2 may be trying to unmount /mnt. It looks as if N+2 is attempting to perform a pathname lookup while it has a locked vnode. > > Unfortunatly though I have the system stopped in gdb > I don't know how to examine the stacktrace of arbitrary > processes so I can't say how those 3 processes got where > they are. All other processes on the system > that need to access the filesystem are locked in "ufslk2" > > e.g. any new logins go there immediatly. :( > > if anyone knows how to examine an arbitrary process stacktrace > I'd like to hear about it....... I wanted to do this with DDB once and I think I was stumped by the kernel stack being in the u-area which is mapped to the same place for each process. Since the process I wanted to backtrace was not curproc, I couldn't see its stack :-(. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 734 3761 FAX: +44 171 734 6426 From owner-freebsd-current Thu Oct 3 03:18:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA19036 for current-outgoing; Thu, 3 Oct 1996 03:18:37 -0700 (PDT) Received: from whale.gu.kiev.ua (news.gu.net [193.124.51.77]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA19027 for ; Thu, 3 Oct 1996 03:18:05 -0700 (PDT) Received: from creator.gu.kiev.ua (stesin@creator.gu.kiev.ua [193.124.51.73]) by whale.gu.kiev.ua (8.7.5/8.7.3) with SMTP id NAA34786; Thu, 3 Oct 1996 13:13:39 +0300 Date: Thu, 3 Oct 1996 13:13:38 +0300 (EET DST) From: Andrew Stesin X-Sender: stesin@creator.gu.kiev.ua To: Michael Hancock cc: Garrett Wollman , current@freebsd.org Subject: Re: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, On Thu, 3 Oct 1996, Michael Hancock wrote: > /kernel is marked immutable. I'd like to be able to configure systems > such that you can't change the flags unless you are in single user mode > even if you're root. May be the following is dumb... What about an append-only / if securelevel > 0 ? This way one can create a subtree of appendonly dirs with immutable files in them, thus an Immutable Subtree in the filesystem. I think this might be very useful. > > Regards, > > > Mike Hancock > Best, Andrew nic-hdl: ST73-RIPE From owner-freebsd-current Thu Oct 3 03:36:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA19908 for current-outgoing; Thu, 3 Oct 1996 03:36:29 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA19901; Thu, 3 Oct 1996 03:36:18 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id UAA10965; Thu, 3 Oct 1996 20:28:26 +1000 Date: Thu, 3 Oct 1996 20:28:26 +1000 From: Bruce Evans Message-Id: <199610031028.UAA10965@godzilla.zeta.org.au> To: bde@freebsd.org, jkh@time.cdrom.com Subject: Re: Weird boot problem we've picked up post-2.1-RELEASE Cc: current@freebsd.org, phk@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>When booting off of /dev/wd1, the boot process stops right after the first >>prompt, and scrolls this error repeatedly up the screen. If I enter >>"wd(1,a)kernel" at the first prompt, the machine boots perfectly. Apparently the initial drive number is wrong. >Has now become something of an unpleasantly recurring theme. One of >Walnut Creek CDROM's own Customers From Hell had this problem with a >Packard Bell machine, scrolling the "C:0 H:0 S:0" errors right after >the boot prompt and then quickly resetting (that's the old bit). That This message should contain the drive number. >>Well, I had the same problem with Gateway 2000 P5-100. The floppy >>was OK, I tried several ones. And they worked on another PCs. Also >>2.1.0 boot floppy worked without problems. I can't see how wrong drive numbers could work in 2.1 but not in 2.1.5. Both require the 0x80 bit for hard drives and use the other bits for the unit number >>Well, I had the same problem with Gateway 2000 P5-100. The floppy >>was OK, I tried several ones. And they worked on another PCs. Also >>2.1.0 boot floppy worked without problems. >> Then I updated the BIOS ROM of my motherboard (Triton rev. 1) >>from rev. BR0T 1.005 to BR01.010 (with update files from Gateway 2000 >>web site) and bingo. Now the same floppy boots and I can finally install >>2.1.5. I still do not understand what was the reason for that error, >>but obviously it was not a floppy. Bugs involving the floppy drive number are more common. FreeBSD forces the floppy drive number to 0, but only after deciding that the boot drive is a floppy by looking at the 0x80 bit in the register that usually gives the drive number. The bootstrap could be smarter about retrying the reads of the MBR on the drive that it was supposedly loaded from. Bruce From owner-freebsd-current Thu Oct 3 06:34:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26618 for current-outgoing; Thu, 3 Oct 1996 06:34:29 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA26609 for ; Thu, 3 Oct 1996 06:34:26 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA12862; Thu, 3 Oct 1996 09:34:21 -0400 Date: Thu, 3 Oct 1996 09:34:21 -0400 From: Garrett Wollman Message-Id: <9610031334.AA12862@halloran-eldar.lcs.mit.edu> To: Michael Hancock Cc: current@freebsd.org Subject: Re: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: References: <9610021441.AA28734@halloran-eldar.lcs.mit.edu> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > /kernel is marked immutable. I'd like to be able to configure systems > such that you can't change the flags unless you are in single user mode > even if you're root. sysctl -w kern.securelevel=0 #in /etc/rc.local -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Thu Oct 3 06:49:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA27835 for current-outgoing; Thu, 3 Oct 1996 06:49:43 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA27827; Thu, 3 Oct 1996 06:49:35 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id XAA16899; Thu, 3 Oct 1996 23:47:42 +1000 Date: Thu, 3 Oct 1996 23:47:42 +1000 From: Bruce Evans Message-Id: <199610031347.XAA16899@godzilla.zeta.org.au> To: dfr@render.com, julian@freefall.freebsd.org Subject: Re: HELP!! kernel deadlock found.. Cc: current@freefall.freebsd.org Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >It looks as if N+2 is attempting to perform a pathname lookup while it has >a locked vnode. I usually "solve" ufslk2 hangs by rebooting. There was one longstanding reproducible one that seems to be fixed now. The following script is supposed to exercise a bug in rename() for ufs, but the system usually used to hang on ufslk2. I saw the bug once and hangs many times in 20+ hours of testing. Today I've seen the bug twice and no hangs in 4 hours of testing. --- #!/bin/sh a=/tmp/foo.now b=/tmp/foo.prev while true do for n in 1 2 3 4 5 6 7 8 9 0 do (mv $a $b ; touch $a) & done wait done --- >> if anyone knows how to examine an arbitrary process stacktrace >> I'd like to hear about it....... The proc struct contains a pointer to the pcb and the pcb contains the call-saved registers for savectx() including %esp and %ebp. %ebp is actually for savectx()'s caller. BTW, what should happen if the pcb (or other data that you're looking at) is paged out? Interrupts are disabled, so disk i/o may not work. I'm fixing ddb so that interrupts are always disabled, and gdb-remote should probably keep them disabled too. I think pagefaults should be fatal if interrupts are disabled (or spl >= splbio). The debugger's setjmp handler will make them non fatal (just like when you attempt to access an unmappable address). >I wanted to do this with DDB once and I think I was stumped by the kernel >stack being in the u-area which is mapped to the same place for each >process. Since the process I wanted to backtrace was not curproc, I >couldn't see its stack :-(. There should be a ddb function for this. ddb functions are now easy to add :-). Bruce From owner-freebsd-current Thu Oct 3 08:30:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02966 for current-outgoing; Thu, 3 Oct 1996 08:30:55 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA02957 for ; Thu, 3 Oct 1996 08:30:49 -0700 (PDT) Received: by sovcom.kiae.su id AA13138 (5.65.kiae-1 ); Thu, 3 Oct 1996 18:23:35 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Thu, 3 Oct 96 18:23:34 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id TAA00926; Thu, 3 Oct 1996 19:23:05 +0400 (MSD) Message-Id: <199610031523.TAA00926@nagual.ru> Subject: 'howmany' cruft To: bde@zeta.org.au (Bruce Evans) Date: Thu, 3 Oct 1996 19:23:04 +0400 (MSD) Cc: current@freebsd.org (FreeBSD-current) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL26 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What I find in sys/types.h: #ifndef howmany #define howmany(x, y) (((x) + ((y) - 1)) / (y)) #endif I find it because netpbm redifines it and gcc produce warning on this place. It looks very suspicious for me (I mean ANSI namespace violation). Do we really need it? Can we rename it to _howmany at least? -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Thu Oct 3 08:47:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04274 for current-outgoing; Thu, 3 Oct 1996 08:47:18 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04267 for ; Thu, 3 Oct 1996 08:47:14 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id IAA17525; Thu, 3 Oct 1996 08:45:31 -0700 (PDT) Message-Id: <199610031545.IAA17525@austin.polstra.com> To: roberto@keltia.freenix.fr (Ollivier Robert) Cc: freebsd-current@freebsd.org Subject: Re: ELFKit on current In-reply-to: <199610011818.UAA07552@keltia.freenix.fr> Date: Thu, 03 Oct 1996 08:45:31 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Has anyone tried to merge (I saw Peter do at least) John Polstra's > ELFKit into current ? I would like to see this happen, but I just haven't had time to do it myself lately. I know that Peter had it merged at one point months ago, but I don't know whether he's kept it up to date or not. If I were going to do it myself, I'd use this approach: 1. Take a look and make sure it hasn't already been done. :-) 2. Ask Peter if he's done anything with it lately. 3. Do it: mkdir work cd work cvs co -r RELENG_2_1_0_RELEASE libc cd libc [Apply the Elfkit patches] cvs update -APd [Resolve conflicts] [Check modified files for bogosity] [Try to compile it for both a.out and ELF] [Test test test] [Cajole somebody into reviewing it] [Commit it] I hope/plan to get this done some day, but I can't promise that I'll get to it any time soon. If somebody else wants to work on it in the meantime, it will be just fine with me. (Check with Peter first. It might save you a lot of time.) John -- 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 Thu Oct 3 08:50:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04484 for current-outgoing; Thu, 3 Oct 1996 08:50:42 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04459 for ; Thu, 3 Oct 1996 08:50:29 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA14548; Thu, 3 Oct 1996 09:46:43 -0600 (MDT) Date: Thu, 3 Oct 1996 09:46:43 -0600 (MDT) Message-Id: <199610031546.JAA14548@rocky.mt.sri.com> From: Nate Williams To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Cc: bde@zeta.org.au (Bruce Evans), current@freebsd.org (FreeBSD-current) Subject: Re: 'howmany' cruft In-Reply-To: <199610031523.TAA00926@nagual.ru> References: <199610031523.TAA00926@nagual.ru> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk KOI8-R writes: > What I find in > sys/types.h: > #ifndef howmany > #define howmany(x, y) (((x) + ((y) - 1)) / (y)) > #endif > I find it because netpbm redifines it and gcc produce warning on this place. > It looks very suspicious for me (I mean ANSI namespace violation). > Do we really need it? Can we rename it to _howmany at least? Please! Nate From owner-freebsd-current Thu Oct 3 09:04:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA05110 for current-outgoing; Thu, 3 Oct 1996 09:04:34 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA05103 for ; Thu, 3 Oct 1996 09:04:29 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id CAA20441; Fri, 4 Oct 1996 02:00:33 +1000 Date: Fri, 4 Oct 1996 02:00:33 +1000 From: Bruce Evans Message-Id: <199610031600.CAA20441@godzilla.zeta.org.au> To: ache@nagual.ru, bde@zeta.org.au Subject: Re: 'howmany' cruft Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >What I find in >sys/types.h: >#ifndef howmany >#define howmany(x, y) (((x) + ((y) - 1)) / (y)) >#endif >I find it because netpbm redifines it and gcc produce warning on this place. >It looks very suspicious for me (I mean ANSI namespace violation). >Do we really need it? Can we rename it to _howmany at least? Lite2 changed the whitespace in it and netpbm presumably has the old version. Grep shows that it is used in a few places in /usr/src/*bin (subdirs not checked): ls, dump, fsck, newfs, restore, du, systat and diskpart. These would be easy to fix, but I'm worried about ports. Other macro pollution in found by inspecting the output of cc -E -dM: ntohl, BYTE_ORDER_LITTLE_ENDIAN, ntohs, LITTLE_ENDIAN, FD_SET, HTONL, HTONS, NTOHL, NTOHS, minor, PDP_ENDIAN, NFDBITS, FD_ZERO, NBBY, FD_COPY, FD_ISSET, makedev, FD_SETSIZE, FD_CLR, major, htonl, htons, BIG_ENDIAN. Other pollution in found by inspecting the output of cc -E -P | grep -v '^[ ]*$': physaddr, u_char, u_short, u_int, u_long, ushort, uint, lseek, fd_mask, fd_set. Pollution that is still present if _POSIX_SOURCE is defined: Everything from (*ENDIAN*, ntoh*, NTOH*); lseek. Bruce From owner-freebsd-current Thu Oct 3 10:56:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11543 for current-outgoing; Thu, 3 Oct 1996 10:56:14 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA11538; Thu, 3 Oct 1996 10:56:12 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA06374; Thu, 3 Oct 1996 10:53:50 -0700 From: Terry Lambert Message-Id: <199610031753.KAA06374@phaeton.artisoft.com> Subject: Re: HELP!! kernel deadlock found.. To: dfr@render.com (Doug Rabson) Date: Thu, 3 Oct 1996 10:53:50 -0700 (MST) Cc: julian@freefall.freebsd.org, current@freefall.freebsd.org In-Reply-To: from "Doug Rabson" at Oct 3, 96 11:09:13 am 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 > > Take the following 3 processes: > > > > proc N, with a lock on file / (inode 2) > > wchan of that inode, waitstring of "ufslk2" > > is waiting for inode for /mnt in the root filesystem (inode M) > > > > proc N+1 with a lock on the inode M (/mnt in root filesystem) > > is waiting for inode for / (inode 2) in the mounted filesystem /mnt > > it is showing "uihget" as a waitstring. > > > > proc N+2 with a lock on inode 2 of the mnt filesystem (/ of that filesystem) > > is waiting for the inode for / and is showing "ufslk2" as a waitstring. > > > > It is my suspicion that process N+2 may be trying to unmount /mnt. > > It looks as if N+2 is attempting to perform a pathname lookup while it has > a locked vnode. I'm glad Doug jumped in here. 8-). I think the lookup might be the result of the NFS export handling. Is this system an NFS server? Do you remember what the exports list looked like? I think the current handling of the NFS stuff is a bit bogus. I'd like to eventually see an exportfs mechanism used instea, and take the string list mechanism out of the kernel entirely. The idea that I have to enable an FS for NFS export irks me a bit. All FS's, by their very nature as FS's, should be intrinsically consumable by all VFS consumers. NFS is a VFS consumer, just like the system calls are a VFS consumer. Just like a decent LKM system or kernel threading system would be a VFS consumer. 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 Oct 3 12:49:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA18160 for current-outgoing; Thu, 3 Oct 1996 12:49:05 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA18153 for ; Thu, 3 Oct 1996 12:48:58 -0700 (PDT) Received: from ns.ge.com by mail.crl.com with SMTP id AA04358 (5.65c/IDA-1.5 for ); Thu, 3 Oct 1996 12:49:15 -0700 Received: from burg.is.ge.com ([3.19.120.24]) by ns.ge.com (8.7.5/8.7.3) with ESMTP id PAA26942 for ; Thu, 3 Oct 1996 15:44:16 -0400 (EDT) Received: (from burg@localhost) by burg.is.ge.com (8.8.0/8.7.3) id VAA04092; Thu, 3 Oct 1996 21:41:06 +0200 (MET DST) Date: Thu, 3 Oct 1996 21:41:06 +0200 (MET DST) Message-Id: <199610031941.VAA04092@burg.is.ge.com> From: Dick van den Burg To: current@freebsd.org Subject: Linux ext2fs problems. Mime-Version: 1.0 (generated by tm-edit 7.88) Content-Type: text/plain; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If I have a Linux partition mounted during a reboot, I ALWAYS get a message on the console similar to: syncing disks... 7 7 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 giving up and the Fbsd filesystem is not marked clean and will go through a full fsck after the boot. If I umount the linux partition before a reboot everything is ok. What data is needed to solve this particular problem? Thanks, Dick van den Burg burg@is.ge.com /usr/home/burg# fdisk ******* Working on device /dev/rsd0 ******* parameters extracted from in-core disklabel are: cylinders=1048 heads=127 sectors/track=63 (8001 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1048 heads=127 sectors/track=63 (8001 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 0 is: sysid 6,(Primary 'big' DOS (> 32MB)) start 63, size 1031562 (503 Meg), flag 80 beg: cyl 0/ sector 1/ head 1; end: cyl 128/ sector 63/ head 118 The data for partition 1 is: sysid 5,(Extended DOS) start 1032129, size 1024128 (500 Meg), flag 0 beg: cyl 129/ sector 1/ head 0; end: cyl 256/ sector 63/ head 126 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 2056257, size 4800600 (2344 Meg), flag 0 beg: cyl 257/ sector 1/ head 0; end: cyl 856/ sector 63/ head 126 The data for partition 3 is: sysid 131,(Linux filesystem) start 6856857, size 1520190 (742 Meg), flag 0 beg: cyl 857/ sector 1/ head 0; end: cyl 1023/ sector 63/ head 126 /usr/home/burg# mount /dev/sd0a on / (local) /dev/sd0s3f on /usr (local) /dev/sd0s3e on /var (local) procfs on /proc (local) /dev/sd0s1 on /dos (local, read-only) /dev/sd0s4 on /linux (local) From owner-freebsd-current Thu Oct 3 13:57:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA22785 for current-outgoing; Thu, 3 Oct 1996 13:57:44 -0700 (PDT) Received: from alpo.whistle.com (s204m38.isp.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA22779 for ; Thu, 3 Oct 1996 13:57:38 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id NAA06339 for ; Thu, 3 Oct 1996 13:56:55 -0700 (PDT) Message-ID: <32542824.64880EEB@whistle.com> Date: Thu, 03 Oct 1996 13:55:00 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Re: HELP!! kernel deadlock.. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Last night our mail was screwd up accidentally anyone sending mail to me would have received bouced messages. I see terry's ansewer to this mail and her refers to other answers if you send a response, please resend.. ESPECIALLY if you know how to get gdb in kernel debugging mode to show stacktraces from other processes. I want to hear from you! julian a recap on the problem: Take the following 3 processes: > > proc N, with a lock on file / (inode 2) > wchan of that inode, waitstring of "ufslk2" > is waiting for inode for /mnt in the root filesystem (inode M) > > proc N+1 with a lock on the inode M (/mnt in root filesystem) > is waiting for inode for / (inode 2) in the mounted filesystem /mnt > it is showing "uihget" as a waitstring. > > proc N+2 with a lock on inode 2 of the mnt filesystem (/ of that filesystem) > is waiting for the inode for / and is showing "ufslk2" as a waitstring. > > It is my suspicion that process N+2 may be trying to unmount /mnt P.S. Terry it is NOT running NFS.. NFS is not even loaded. From owner-freebsd-current Thu Oct 3 14:25:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25939 for current-outgoing; Thu, 3 Oct 1996 14:25:15 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA25932 for ; Thu, 3 Oct 1996 14:25:11 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA06812; Thu, 3 Oct 1996 14:23:38 -0700 From: Terry Lambert Message-Id: <199610032123.OAA06812@phaeton.artisoft.com> Subject: Re: HELP!! kernel deadlock.. To: julian@whistle.com (Julian Elischer) Date: Thu, 3 Oct 1996 14:23:37 -0700 (MST) Cc: current@FreeBSD.org In-Reply-To: <32542824.64880EEB@whistle.com> from "Julian Elischer" at Oct 3, 96 01:55:00 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 > P.S. Terry it is NOT running NFS.. NFS is not even loaded. OK. That's one potential cause shot to hell. 8-). 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 Oct 3 17:33:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA15244 for current-outgoing; Thu, 3 Oct 1996 17:33:51 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA15235 for ; Thu, 3 Oct 1996 17:33:48 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id AAA21011; Fri, 4 Oct 1996 00:30:49 GMT Date: Fri, 4 Oct 1996 09:30:49 +0900 (JST) From: Michael Hancock To: Andrew Stesin cc: current@freebsd.org Subject: Re: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: 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 Thu, 3 Oct 1996, Andrew Stesin wrote: > Hello, > > On Thu, 3 Oct 1996, Michael Hancock wrote: > > > /kernel is marked immutable. I'd like to be able to configure systems > > such that you can't change the flags unless you are in single user mode > > even if you're root. > > May be the following is dumb... > > What about an append-only / if securelevel > 0 ? > > This way one can create a subtree of appendonly dirs > with immutable files in them, thus an Immutable Subtree > in the filesystem. I think this might be very useful. The functionality is fine as it is, it's just not exported to you when you configure your kernel. From owner-freebsd-current Thu Oct 3 17:48:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA17340 for current-outgoing; Thu, 3 Oct 1996 17:48:32 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA17321 for ; Thu, 3 Oct 1996 17:48:29 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id AAA21159; Fri, 4 Oct 1996 00:48:10 GMT Date: Fri, 4 Oct 1996 09:48:10 +0900 (JST) From: Michael Hancock To: Garrett Wollman cc: current@freebsd.org Subject: Re: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: <9610031334.AA12862@halloran-eldar.lcs.mit.edu> 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 Thu, 3 Oct 1996, Garrett Wollman wrote: > < said: > > > /kernel is marked immutable. I'd like to be able to configure systems > > such that you can't change the flags unless you are in single user mode > > even if you're root. > > sysctl -w kern.securelevel=0 #in /etc/rc.local How many deamons are running by the time you get to this line? This isn't satisfactory, I don't want the -1 to 0 window fullstop. This is a yet another 4.4 advance over other Unix implementations, yet we hide it. If this security level stuff has a holes in it we are unlikely to find them and fix them if the initialization isn't exported to us in kernel config because hardly anyone will use it. The false sense of security argument is bogus. Why can't we export it like all the other BSDs? They call it INSECURE which toggles -1 or 0, we can call it something else following the "principle of least astonishment to newbies". options INITIAL_SECURITY_LEVEL=0 #man init for details Regards, Mike From owner-freebsd-current Thu Oct 3 17:50:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA17629 for current-outgoing; Thu, 3 Oct 1996 17:50:38 -0700 (PDT) Received: from sed.cs.fsu.edu (sed.cs.fsu.edu [128.186.121.157]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA17623 for ; Thu, 3 Oct 1996 17:50:35 -0700 (PDT) Received: by sed.cs.fsu.edu (8.7.6/56) id AAA27130; Fri, 4 Oct 1996 00:50:32 GMT From: Gang-Ryung Uh Message-Id: <199610040050.AAA27130@sed.cs.fsu.edu> Subject: Make world fails To: current@FreeBSD.org Date: Thu, 3 Oct 1996 20:50:32 -0400 (EDT) Reply-To: bartol@salk.edu In-Reply-To: from "Tom Bartol" at Oct 2, 96 12:49:57 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 Hi, I supped the current src last night, and tried to build current by "make world". But I could not go through. I am pretty sure that I may miss some critical steps. Thanks in advance. Regards, Gang-Ryung Uh ================================ mkdep -f .depend -a -DFREEBSD_AOUT -I/usr/src/gnu/usr.bin/cc/cc_tools/../../..\ /../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/conf\ ig -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.1\" -DDEFAULT_TARGET_MACHI\ NE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_to\ ols bi-parser.c insn-emit.c insn-recog.c insn-opinit.c insn-extract.c insn-pee\ p.c insn-attrtab.c insn-output.c c-parse.c objc-parse.c ===> cc_int make: don't know how to make insn-attrtab.c. Stop *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. From owner-freebsd-current Thu Oct 3 19:05:42 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA24459 for current-outgoing; Thu, 3 Oct 1996 19:05:42 -0700 (PDT) Received: from intercore.com (num1sun.intercore.com [199.181.243.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA24447 for ; Thu, 3 Oct 1996 19:05:35 -0700 (PDT) Received: (robin@localhost) by intercore.com (8.7.1/8.6.4) id VAA11131; Thu, 3 Oct 1996 21:59:38 -0400 (EDT) From: Robin Cutshaw Message-Id: <199610040159.VAA11131@intercore.com> Subject: Re: Problem w/ New Kernels To: scrappy@ki.net (Marc G. Fournier) Date: Thu, 3 Oct 1996 21:59:35 -0400 (EDT) Cc: freebsd-current@freebsd.org In-Reply-To: from "Marc G. Fournier" at Oct 1, 96 03:54:17 pm X-Mailer: ELM [version 2.4 PL21] 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 > > > > w: proc size mismatch (18960 total, 612 chunks) > > > > Any ideas? > > > Did you remember to recompile ps/w? If *that* doesn't do it, > then libkvm has to be recompiled as well... > Yep, I had to copy sys/i386/include/* to /usr/include/machine, remake libkvm, and then ps. robin -- ---- Robin Cutshaw internet: robin@interlabs.com robin@intercore.com Internet Labs, Inc. BellNet: 404-817-9787 "Time is just one damn thing after another" -- PBS/Nova ---- -- From owner-freebsd-current Thu Oct 3 23:06:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA23169 for current-outgoing; Thu, 3 Oct 1996 23:06:10 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA23164 for ; Thu, 3 Oct 1996 23:06:07 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id XAA11847; Thu, 3 Oct 1996 23:06:04 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SFrom owner-freebsd-current Fri Oct 4 02:25:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA05369 for current-outgoing; Fri, 4 Oct 1996 02:25:47 -0700 (PDT) Received: from masternet.it (root@masternet.it [194.184.65.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA05361 for ; Fri, 4 Oct 1996 02:25:40 -0700 (PDT) Received: from gmarco (ts1port9d.masternet.it [194.184.65.31]) by masternet.it (8.6.12/8.6.9) with SMTP id LAA31674 for ; Wed, 4 Oct 1995 11:20:44 +0100 Message-Id: <3.0b26.32.19961004102145.00692194@masternet.it> X-Sender: gmarco@masternet.it X-Mailer: Windows Eudora Pro Version 3.0b26 (32) Date: Fri, 04 Oct 1996 10:21:51 +0100 To: current@freebsd.org From: Gianmarco Giovannelli Subject: 960501 to -current --> Error code 1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello to everybody, I tried to arrive to current starting from the old SNAP 960501 (src-curr.1600A.gz) and then applying all the ctm delta till ~2270 (thanks very much to Gary Jennejohn and J.Wunsch for their help) Everythings works fine but when I arrive to do: make world DDEFAULT_TARGET_VERSION=\"2.7.2.1\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/libgcc/../cc_tools -DL_eprintf -o _eprintf.o /usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc/libgcc2.c /usr/obj/usr/src/gnu/usr.bin/cc/libgcc/../cc/cc -B/usr/obj/usr/src/gnu/usr.bin/cc/libgcc/../cc1/ -B/usr/obj/usr/src/gnu/usr.bin/cc/libgcc/../cpp/ -c -O -DFREEBSD_AOUT -I/usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc/config -DFREEBSD_NATIVE -DDEFAULT_TARGET_VERSION=\"2.7.2.1\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/usr/obj/usr/src/gnu/usr.bin/cc/libgcc/../cc_tools -DL_op_new -o _op_new.o /usr/src/gnu/usr.bin/cc/libgcc/../../../../contrib/gcc/libgcc2.c /var/tmp/cc013925.s: Assembler messages: /var/tmp/cc013925.s:4: Error: Unknown pseudo-op: `.weak' *** Error code 1 for my little knowledge of the make process the only solution I was able to do was : make cleandir --> OK make obj --> OK make depend --> OK make --> FAIL cc -O -I/usr/src/bin/csh -I. -DBUILTIN -DFILEC -DNLS -DSHORT_STRINGS -c /usr/src/bin/csh/../../usr.bin/printf/printf.c cc -O -I/usr/src/bin/csh -I. -DBUILTIN -DFILEC -DNLS -DSHORT_STRINGS -c /usr/src/bin/csh/proc.c cc -O -I/usr/src/bin/csh -I. -DBUILTIN -DFILEC -DNLS -DSHORT_STRINGS -c /usr/src/bin/csh/sem.c cc -O -I/usr/src/bin/csh -I. -DBUILTIN -DFILEC -DNLS -DSHORT_STRINGS -c /usr/src/bin/csh/set.c cc -O -I/usr/src/bin/csh -I. -DBUILTIN -DFILEC -DNLS -DSHORT_STRINGS -c /usr/src/bin/csh/str.c cc -O -I/usr/src/bin/csh -I. -DBUILTIN -DFILEC -DNLS -DSHORT_STRINGS -c /usr/src/bin/csh/time.c cc -O -I/usr/src/bin/csh -I. -DBUILTIN -DFILEC -DNLS -DSHORT_STRINGS -static -o csh alloc.o char.o const.o csh.o dir.o dol.o err.o exec.o exp.o file.o func.o glob.o hist.o init.o lex.o misc.o parse.o printf.o proc.o sem.o set.o str.o time.o glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment *** Error code 1 Probably I must rebuild something before commit a make world, but I really don't know what since I was off this list in the summer. Thanks in advance to everyone for attention.... Regards... +-------------------------------------+--------------------+ | Internet: gmarco@masternet.it | ,,, | | Internet: gmarco@fi.nettuno.it | (o o) | | BIX : ggiovannelli@bix.com | ---oo0-(_)-0oo--- | | http://www.masternet.it/dsc/gmarco | Gianmarco | +-------------------------------------+--------------------+ From owner-freebsd-current Fri Oct 4 07:30:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA21829 for current-outgoing; Fri, 4 Oct 1996 07:30:41 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA21824 for ; Fri, 4 Oct 1996 07:30:38 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA18858; Fri, 4 Oct 1996 10:29:52 -0400 Date: Fri, 4 Oct 1996 10:29:52 -0400 From: Garrett Wollman Message-Id: <9610041429.AA18858@halloran-eldar.lcs.mit.edu> To: Michael Hancock Cc: current@freebsd.org Subject: Re: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: References: <9610031334.AA12862@halloran-eldar.lcs.mit.edu> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: >> sysctl -w kern.securelevel=0 #in /etc/rc.local > How many deamons are running by the time you get to this line? > This isn't satisfactory, I don't want the -1 to 0 window fullstop. THERE IS NO OPERATIONAL DIFFERENCE BETWEEN -1 AND 0. Period. The ONLY difference is in what /sbin/init does AFTER /etc/rc is finished executing. This is all documented in the init(8) man page; there is no excuse for you not reading it. -1 Permanently insecure mode - always run system in level 0 mode. 0 Insecure mode - immutable and append-only flags may be turned off. All devices may be read or written subject to their permissions. [...] Normally, the system runs in level 0 mode while single user and in level 1 mode while multiuser. If the level 2 mode is desired while running multiuser, it can be set in the startup script /etc/rc using sysctl(8). > Why can't we export it like all the other BSDs? Because it's a waste of effort any creates Yet Another Useless Configuration Option. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Fri Oct 4 13:18:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11612 for current-outgoing; Fri, 4 Oct 1996 13:18:03 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA11590 for ; Fri, 4 Oct 1996 13:17:56 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA01930; Fri, 4 Oct 1996 22:17:40 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA03268; Fri, 4 Oct 1996 22:17:40 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA04603; Fri, 4 Oct 1996 21:42:42 +0200 (MET DST) From: J Wunsch Message-Id: <199610041942.VAA04603@uriah.heep.sax.de> Subject: Re: 960501 to -current --> Error code 1 To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 4 Oct 1996 21:42:41 +0200 (MET DST) Cc: gmarco@masternet.it (Gianmarco Giovannelli) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <3.0b26.32.19961004102145.00692194@masternet.it> from Gianmarco Giovannelli at "Oct 4, 96 10:21:51 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 As Gianmarco Giovannelli wrote: > /var/tmp/cc013925.s: Assembler messages: > /var/tmp/cc013925.s:4: Error: Unknown pseudo-op: `.weak' > *** Error code 1 Not yet finalized gcc 2.7 import. Peter has announced that he finalized it since, so you should update again. > glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment > glob.o: Undefined symbol `_collate_range_cmp' referenced from text segment > *** Error code 1 I think i've seen this, too, but it went away after rebuilding some tool. Forgot which one though... Re-read the archives for the -current mailing list. -- 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 Fri Oct 4 13:51:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA14809 for current-outgoing; Fri, 4 Oct 1996 13:51:28 -0700 (PDT) Received: from covina.lightside.com (covina.lightside.com [207.67.176.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA14800 for ; Fri, 4 Oct 1996 13:51:23 -0700 (PDT) Received: from localhost (jehamby@localhost) by covina.lightside.com (8.7.6/8.7.3) with SMTP id NAA13921 for ; Fri, 4 Oct 1996 13:50:53 -0700 (PDT) Date: Fri, 4 Oct 1996 13:50:53 -0700 (PDT) From: Jake Hamby To: current@freebsd.org Subject: Wow, CVSup is cool! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After complaining about some problems I had with sup4.freebsd.org (it repeatedly fetched large chunks of contrib even though nothing, other than the datestamp, had changed!), I decided to try out CVSup, even though it involves installing the 5MB Modula-3 package first. I was _very_ impressed! My favorite features: 1) Doesn't get confused by datestamps. It uses checksums and the embedded RCS version to tell if the file has changed. This was especially a problem with Sup when I tried to switch to an alternate sup server, because many datestamps were different (different time zones?). Not a problem with CVSup. 2) When a file changes, it applies the CVS deltas directly rather than redownloading the entire file. This saves a tremendous amount of time, and combined with built-in compression support, makes CVSup a godsend for people on slow links (like my 28.8kbps modem!). 3) Compatible with my existing sup configuration. It includes an awk script to convert existing supfiles to CVSup format. I thought I would need to download the CVS Repository to take advantage of CVSup, but the mode I used only downloaded /usr/src, exactly like sup. If I decide to devote disk space for the CVS repository later on, CVSup will support that too, and with the same benefits in speed. Anyway, kudos to John Polstra for an excellent piece of software (it even has a nifty X11 GUI!). The savings in time will make up for the initial 5MB Modula-3 download in your first or second usage. EVERYONE who is currently using SUP to get FreeBSD-current should give CVSup a try, it is that good! (Another happy FreeBSD customer who is right now reading the Modula-3 web page, since I've got the compiler installed :-) -- Jake From owner-freebsd-current Fri Oct 4 15:12:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA22169 for current-outgoing; Fri, 4 Oct 1996 15:12:19 -0700 (PDT) Received: from print.gfmurray.com ([207.6.88.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA22159 for ; Fri, 4 Oct 1996 15:12:14 -0700 (PDT) From: tim@print.gfmurray.com Received: from client3.gfmurray.com (client3.gfmurray.com [207.6.88.13]) by print.gfmurray.com (8.7.5/8.6.12) with SMTP id PAA03983 for ; Fri, 4 Oct 1996 15:12:25 -0700 (PDT) Date: Fri, 4 Oct 1996 15:12:25 -0700 (PDT) Message-Id: <199610042212.PAA03983@print.gfmurray.com> X-Sender: tim@print.gfmurray.com X-Mailer: Windows Eudora Version 1.4.4 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-current@freebsd.org Subject: Re: firewall/gateway/proxy question Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >I'm looking for suggestions on what to run to do this. > >I have one computer that connects to my ISP (NetBSD-current), with a >single, fixed IP#. I have two other machines (one Windows NT, and one >FreeBSD/NetBSD/hacking/test machine) behind it, which I would like to >gateway through it. However, with only this single IP# to the outside >world. > >I think that means I need to run some kind of firewall and/or proxy >server. I don't think socks will be sufficient, since it doesn't >transparently proxy my NT box, through the NetBSD gateway, to the >world. What protocols do you want to be able to gate through to the Internet? If its only FTP and HTTP, then It is EASY with 'cached' from the Harvest collection...I suggest that this be tried first...before you get into any spooky ip mapping...... > >I've never paid much attention to this before, so I'm not sure where >to start looking. Suggestions? > >----------------------------------------------------------------------------- > Michael L. VanLoon michaelv@MindBender.serv.net > --< Free your mind and your machine -- NetBSD free un*x >-- > NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, > Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... > NetBSD ports in progress: PICA, others... >----------------------------------------------------------------------------- > > > > Tim Baird Dominus Fecit "The Lord Made" Opinions expressed are not necessarily those of my employer etc. etc From owner-freebsd-current Fri Oct 4 16:23:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA01175 for current-outgoing; Fri, 4 Oct 1996 16:23:40 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA01164 for ; Fri, 4 Oct 1996 16:23:36 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id XAA29208; Fri, 4 Oct 1996 23:23:14 GMT Date: Sat, 5 Oct 1996 08:23:14 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: Garrett Wollman cc: current@freebsd.org Subject: Re: Immutable flags (was: Re: WARNING: botched ld.so commit! :-() In-Reply-To: <9610041429.AA18858@halloran-eldar.lcs.mit.edu> 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 Fri, 4 Oct 1996, Garrett Wollman wrote: > < said: > > >> sysctl -w kern.securelevel=0 #in /etc/rc.local > > > How many deamons are running by the time you get to this line? > > > This isn't satisfactory, I don't want the -1 to 0 window fullstop. > > THERE IS NO OPERATIONAL DIFFERENCE BETWEEN -1 AND 0. Period. There's a difference when you initialize it and this is different from securelevel operational mode when in multi-user mode. > The ONLY difference is in what /sbin/init does AFTER /etc/rc is finished > executing. This is all documented in the init(8) man page; there is > no excuse for you not reading it. The man pages don't tell me anything about when this happens. > -1 Permanently insecure mode - always run system in level 0 mode. > > 0 Insecure mode - immutable and append-only flags may be turned off. > All devices may be read or written subject to their permissions. Added part you deleted. 1 Secure mode - immutable and append-only flags may not be changed; disks for mounted filesystems, /dev/mem, and /dev/kmem are read-only. 2 Highly secure mode - same as secure mode, plus disks are always read-only whether mounted or not. This level precludes tampering with filesystems by unmounting them, but also inhibits running newfs(8) while the system is multi-user. I initialize securelevel to 0 if I want securelevel 1 as the operational mode for multi-user. > > Normally, the system runs in level 0 mode while single user and in level > 1 mode while multiuser. If the level 2 mode is desired while running > multiuser, it can be set in the startup script /etc/rc using sysctl(8). Normally, but not FreeBSD. It does this ... If it is desired to run the system in level 0 mode while multiuser, the administrator must build a kernel with the variable securelevel defined in the file /sys/compile/MACHINE/param.c and initialize it to -1. Originally, 4.4BSD just didn't initialize securelevel, so it when into .bss and was zfod'ed by the system. FreeBSD hardcodes it to permanently insecure. Regards, Mike From owner-freebsd-current Fri Oct 4 16:35:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA02553 for current-outgoing; Fri, 4 Oct 1996 16:35:21 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA02542 for ; Fri, 4 Oct 1996 16:35:18 -0700 (PDT) Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id QAA04120 for ; Fri, 4 Oct 1996 16:35:16 -0700 (PDT) Date: Fri, 4 Oct 1996 16:34:41 -0700 (PDT) From: Tom Bartol To: current@freebsd.org Subject: Help! /bin/csh is gone! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, We'll I'm slightly hosed here. I ftp'd src for current from ftp.freebsd.org, did a make update and make world. The make world got really far along and was in the midst of doing: install -c -s -o bin -g bin -m 555 csh /bin which returned: install: csh: Input/Output error and at which point /bin/csh was gone from the system. A cp of /usr/obj/usr/src/bin/csh/csh to /bin/csh also fails. /bin/csh is the default shell for root and for several other users who were logged in at the time. I'm new to this -current thing. What should I do? HELP!!! Tom From owner-freebsd-current Fri Oct 4 17:29:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA07814 for current-outgoing; Fri, 4 Oct 1996 17:29:04 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA07789; Fri, 4 Oct 1996 17:28:56 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id CAA06476; Sat, 5 Oct 1996 02:15:40 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.6/8.7.3) with SMTP id BAA03244; Sat, 5 Oct 1996 01:09:14 +0200 (MET DST) Date: Sat, 5 Oct 1996 01:09:14 +0200 (MET DST) From: Andreas Klemm To: current@freebsd.org cc: hackers@freebsd.org Subject: Problems getting Window Manager to run, X11 hangs ... Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi ! I'm just fiddeling around with another FreeBSD-current machine since two days. Whenever I try to start afterstep as window manager, the machine hangs in X11 display. Plain Window Managers like twm work perfectly. I grabbed the newest -current sources and did a make world. After that I installed xpm and afterstep from the ports collection. With afterstep the console display changes to X11 and hangs, parts of X11 (afterstep's wharf) initialization are displayed. I even re-made XFree86 from the ports collection... No luck. Is there a known problem with gcc 2.7.2.1, the new .weak support, or whatelse ... it's driving me nuts ... since 2 days I don't get a working X11 running ... Any ideas ?! Now I made a package of afterstep, xpm 3.4i from a 2 days older -current machine and installed it on the machine that has the problems... I also copied the XF86_S3 server from there ... Well, afterstep's wharf now initializes more complete, a x11 xterm appears, I click on it, try to move it ... and again the whole X11 screen freezes ... *sigh* Heeelp ;-)) Andreas /// -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Fri Oct 4 17:53:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA11088 for current-outgoing; Fri, 4 Oct 1996 17:53:36 -0700 (PDT) Received: from white.dogwood.com (root@white.dogwood.com [140.174.96.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA11074 for ; Fri, 4 Oct 1996 17:53:32 -0700 (PDT) Received: (from dave@localhost) by white.dogwood.com (8.8.0/8.8.0) id RAA08568 for current@freebsd.org; Fri, 4 Oct 1996 17:53:25 -0700 (PDT) From: Dave Cornejo Message-Id: <199610050053.RAA08568@white.dogwood.com> Subject: groff compilation problem (probably just me) X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: current@freebsd.org Date: Fri, 4 Oct 1996 17:53:25 -0700 (PDT) Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a system which quite regularly hits .../groff/devX100 in 'make world' which dies with an error 'make: don't know how to make S. Stop' If I delete /usr/src and /usr/obj and then recopy them, it'll work, but then a few sups later it seems to be back. I've tried deleting just parts of the directories to no avail... Any clues anybody? Thanks, -- Dave Cornejo - Dogwood Media, Fremont, California From owner-freebsd-current Fri Oct 4 17:56:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA11714 for current-outgoing; Fri, 4 Oct 1996 17:56:36 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA11705 for ; Fri, 4 Oct 1996 17:56:33 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id RAA04443; Fri, 4 Oct 1996 17:56:31 -0700 (PDT) Message-Id: <199610050056.RAA04443@austin.polstra.com> To: freebsd-current@freebsd.org Cc: Jake Hamby Subject: Re: Wow, CVSup is cool! In-reply-to: Date: Fri, 04 Oct 1996 17:56:31 -0700 From: John Polstra Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just one small point ... > The savings in time will make up for the initial 5MB Modula-3 > download in your first or second usage. Or get the statically linked executable. It's around 1.1 MB, and you don't need anything else in order to run it. It's available from: ftp://freefall.freebsd.org/pub/CVSup/ ftp://ftp.freebsd.org/pub/FreeBSD/incoming/ ftp://ftp.polstra.com/pub/FreeBSD/CVSup/ (slow; avoid if possible) in the file "cvsup-bin-13.4.tar.gz". > (it even has a nifty X11 GUI!) ... with the _ugliest_ scrollbars in the world! Jordan hates them. The GUI is pretty worthless right now, as a tool for configuring the program. It's mostly just a very complicated pacifier. :-) I have lots of ideas for it, but more important features keep coming first. FWIW, in the next release it will be easy to build the client without the GUI, in case you don't have X11 or don't want such a large memory image. > (Another happy FreeBSD customer who is right now reading the Modula-3 > web page, since I've got the compiler installed :-) It's a clunky looking language, until you get used to it. But it sure has been a pleasure to work with, for this application. John -- 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 Fri Oct 4 17:59:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA12201 for current-outgoing; Fri, 4 Oct 1996 17:59:37 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA12189 for ; Fri, 4 Oct 1996 17:59:34 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id RAA04463; Fri, 4 Oct 1996 17:59:30 -0700 (PDT) Message-Id: <199610050059.RAA04463@austin.polstra.com> To: Tom Bartol Cc: current@FreeBSD.org Subject: Re: Help! /bin/csh is gone! In-reply-to: Date: Fri, 04 Oct 1996 17:59:30 -0700 From: John Polstra Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > install -c -s -o bin -g bin -m 555 csh /bin > > which returned: > > install: csh: Input/Output error > > and at which point /bin/csh was gone from the system. > > A cp of /usr/obj/usr/src/bin/csh/csh to /bin/csh also fails. It sounds to me like you've run out of disk space. Use "df" to check. Delete some stuff you don't need, and then try again to copy csh to /bin. John -- 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 Fri Oct 4 18:44:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA16499 for current-outgoing; Fri, 4 Oct 1996 18:44:31 -0700 (PDT) Received: from apolo.biblos.unal.edu.co ([168.176.37.75]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA16263 for ; Fri, 4 Oct 1996 18:42:13 -0700 (PDT) Received: (from pgiffuni@localhost) by apolo.biblos.unal.edu.co (8.8.0/8.7.3) id SAA00202; Fri, 4 Oct 1996 18:21:31 -0500 (EST) Date: Fri, 4 Oct 1996 18:21:26 -0500 (EST) From: Pedro Giffuni To: current@freebsd.org Subject: New Sendmail... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Msybe you already know, but the latest release fo sendmail is 8.8.0, it works fine on FreeBSD. Pedro From owner-freebsd-current Fri Oct 4 19:10:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA18859 for current-outgoing; Fri, 4 Oct 1996 19:10:51 -0700 (PDT) Received: from relay.hp.com (relay.hp.com [15.255.152.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA18851 for ; Fri, 4 Oct 1996 19:10:48 -0700 (PDT) Received: from srmail.sr.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA190421385; Fri, 4 Oct 1996 19:09:45 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA218171384; Fri, 4 Oct 1996 19:09:44 -0700 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA244811383; Fri, 4 Oct 1996 19:09:43 -0700 Message-Id: <199610050209.AA244811383@hpnmhjw.sr.hp.com> To: Jake Hamby Cc: current@freefall.freebsd.org Subject: Re: Wow, CVSup is cool! In-Reply-To: Your message of "Fri, 04 Oct 1996 13:50:53 PDT." Date: Fri, 04 Oct 1996 19:09:43 -0700 From: Darryl Okahata Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > After complaining about some problems I had with sup4.freebsd.org (it > repeatedly fetched large chunks of contrib even though nothing, other than > the datestamp, had changed!), I decided to try out CVSup, even though it > involves installing the 5MB Modula-3 package first. John has precompiled cvsup binaries available, and so you didn't have to install M3. > Anyway, kudos to John Polstra for an excellent piece of software (it even > has a nifty X11 GUI!). The savings in time will make up for the initial > 5MB Modula-3 download in your first or second usage. EVERYONE who is > currently using SUP to get FreeBSD-current should give CVSup a try, it is > that good! I'll second the notion! -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-current Fri Oct 4 22:32:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA26754 for current-outgoing; Fri, 4 Oct 1996 22:32:19 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA26731; Fri, 4 Oct 1996 22:32:09 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id HAA05200; Sat, 5 Oct 1996 07:15:45 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.6/8.7.3) with SMTP id HAA00837; Sat, 5 Oct 1996 07:12:57 +0200 (MET DST) Date: Sat, 5 Oct 1996 07:12:57 +0200 (MET DST) From: Andreas Klemm To: current@freebsd.org cc: hackers@freebsd.org Subject: Re: Problems getting Window Manager to run, X11 hangs ... In-Reply-To: Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 5 Oct 1996, Andreas Klemm wrote: > Hi ! > > I'm just fiddeling around with another FreeBSD-current machine since > two days. Whenever I try to start afterstep as window manager, the > machine hangs in X11 display. Plain Window Managers like twm work > perfectly. [...] Wrong /etc/XFree86 settings. Works now ... good night ;) -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Fri Oct 4 23:50:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA29875 for current-outgoing; Fri, 4 Oct 1996 23:50:51 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA29869 for ; Fri, 4 Oct 1996 23:50:48 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA12419; Sat, 5 Oct 1996 08:50:43 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA13368; Sat, 5 Oct 1996 08:50:42 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA07960; Sat, 5 Oct 1996 08:23:55 +0200 (MET DST) From: J Wunsch Message-Id: <199610050623.IAA07960@uriah.heep.sax.de> Subject: Re: Help! /bin/csh is gone! To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 5 Oct 1996 08:23:55 +0200 (MET DST) Cc: bartol@salk.edu Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199610050059.RAA04463@austin.polstra.com> from John Polstra at "Oct 4, 96 05:59:30 pm" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 As John Polstra wrote: > > install: csh: Input/Output error > > > > and at which point /bin/csh was gone from the system. > > > > A cp of /usr/obj/usr/src/bin/csh/csh to /bin/csh also fails. > > It sounds to me like you've run out of disk space. Use "df" to check. > Delete some stuff you don't need, and then try again to copy csh to > /bin. Or, he's got a real hardware error. Should be accompanied by some console message (see /var/log/messages, too). -- 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 Sat Oct 5 00:38:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA01506 for current-outgoing; Sat, 5 Oct 1996 00:38:13 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA01501 for ; Sat, 5 Oct 1996 00:38:11 -0700 (PDT) Received: from helmholtz (helmholtz [198.202.70.34]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id AAA10089; Sat, 5 Oct 1996 00:38:06 -0700 (PDT) Date: Sat, 5 Oct 1996 00:38:06 -0700 (PDT) From: Tom Bartol X-Sender: bartol@helmholtz To: Joerg Wunsch cc: FreeBSD-current users Subject: Re: Help! /bin/csh is gone! In-Reply-To: <199610050623.IAA07960@uriah.heep.sax.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 On Sat, 5 Oct 1996, J Wunsch wrote: > As John Polstra wrote: > > > > install: csh: Input/Output error > > > > > > and at which point /bin/csh was gone from the system. > > > > > > A cp of /usr/obj/usr/src/bin/csh/csh to /bin/csh also fails. > > > > It sounds to me like you've run out of disk space. Use "df" to check. > > Delete some stuff you don't need, and then try again to copy csh to > > /bin. > > Or, he's got a real hardware error. Should be accompanied by some > console message (see /var/log/messages, too). > You guessed it! Thanks for the hint: sd0(ahc0:0:0): MEDIUM ERROR info:189e1c asc:14,1 Record not found , retries:4 sd0(ahc0:0:0): MEDIUM ERROR info:189e1b asc:14,1 Record not found , retries:3 sd0(ahc0:0:0): MEDIUM ERROR info:189e1d asc:11,0 Unrecovered read error , retries:2 sd0(ahc0:0:0): MEDIUM ERROR info:189e1c asc:11,0 Unrecovered read error , retries:1 sd0(ahc0:0:0): MEDIUM ERROR info:189e1b asc:14,1 Record not found , FAILURE spec_getpages: I/O read error vm_fault: pager input (probably hardware) error, PID 198 failure pid 198 (csh), uid 1116: exited on signal 11 Yuck! I guess this looks like bad blocks on the SCSI hard drive a "SEAGATE ST51080N" -- Oh poop!! Luckily almost new and still under warranty. Guess I'll be out of commission for awhile fixing this one. Down but not out. I'll be back on -current before you all can do a "make world" on a 200 MHz P6... Thanks for the help, quick replies, and hard work, :-) Tom From owner-freebsd-current Sat Oct 5 01:56:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA04036 for current-outgoing; Sat, 5 Oct 1996 01:56:27 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA04029; Sat, 5 Oct 1996 01:56:23 -0700 (PDT) Received: by sovcom.kiae.su id AA29852 (5.65.kiae-1 ); Sat, 5 Oct 1996 11:43:56 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sat, 5 Oct 96 11:43:55 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id MAA00671; Sat, 5 Oct 1996 12:35:21 +0400 (MSD) Message-Id: <199610050835.MAA00671@nagual.ru> Subject: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610041822.UAA03607@uriah.heep.sax.de> from "J Wunsch" at "Oct 4, 96 08:22:33 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 5 Oct 1996 12:35:20 +0400 (MSD) Cc: freebsd-hackers@freebsd.org, current@freebsd.org (FreeBSD-current) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast 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 > I don't think so. But they are much better with random(). See xmine, > if you wanna get a nice example. It generates totally predictable > layouts when using rand(). Totally predictable layouts not rand() illness only but random() too. It not depends well on different initial state, producing the same sequence. I finally dig out initial posting (below). IMHO we need to change our random() as suggested. ------------------------------- cut me here! -------------------------- >From warwick@cs.uq.edu.au Fri Jul 5 21:11:08 1996 From: warwick@cs.uq.edu.au (Warwick Allison) Newsgroups: comp.os.linux.development.system,comp.bugs.4bsd Subject: Re: Random Number Generation with Linux (using BSD) and BSD Date: 29 Mar 1996 02:12:03 GMT Organization: Computer Science Dept, University of Queensland Message-ID: <4jfgtk$d71@miso.cs.uq.edu.au> References: <1996Mar28.154520.1@rmcs.cranfield.ac.uk> NNTP-Posting-Host: isa.cs.uq.edu.au X-Newsreader: NN version 6.5.0 #7 (NOV) Status: RO warner@rmcs.cranfield.ac.uk (Alistair (Joe) Warner) writes: > BSD: state[i] = 1103515245 * state[i - 1] + 12345; > Linux: state[i] = 1103515145 * state[i - 1] + 12345; > ^ Ha! How amusing. That line is utterly WRONG in BOTH implementations. The state it creates is so incredibly UNRANDOM, that seeding is almost pointless. The following program outputs a PBM image showing a bit in the result of successive calls to random(), for consecutive values of srandom(). The results are TERRIBLE (for example, the 151st value returned by random() is 0 for seed 0..14, then 1 for seed 15..30, then 0 for seed 31..46, etc.) The reason? That stupid line above. Appended are my previous warnings about this, which have been ignored I presume this is because most people just don't understand the problem. Let me tell you one consequence: In one build of NetHack, it was impossible to get a Chaotic Priest. Why you ask? Because the alignment was chosen based on to successive 0th bits from random() calls, and the 0th bit is the worst of all (for some number of calls of random(), it always has the same value, regardless of initial srandom value!!!). I have tested this under Solaris, and I get similar abysmal errors. Changing to the BSD value will make NO DIFFERENCE. The change I give below is of the type required for success. #include #define LOOP 200 #define ITER 200 main() { int s=time(0); int i,l,m,j; int seed=0; printf("P1\n%d %d\n",ITER,LOOP); for (l=0; l>8)&1; /* remove >>8 for WORSE */ printf("%d\n",b); } } } >To: bug-glibc@prep.ai.mit.edu >cc: >Subject: PARTIAL FIX FOR: srandom() in libc -------- The implementation of srandom() is not good. By using a poor LCRNG for the seeding, the whole algorithm is suffering. I realize this is the same algorithm used in every Unix C library, but hopefully *GNU* software doesn't have to live under known errors forever. For example, if only the zeroth bit is used from successive calls to random(), it will give almost identical output, regardless of the seed. This can be verified by this simple program which generates a PBM image of streams of random numbers from different starting seeds: main() { int i,l; int seed=0; printf("P1\n%d %d\n",100,100); for (l=0; l<100; l++) { srandom(seed); seed+=1; for (i=0; i<100; i++) { int b=random()&1; printf("%d\n",b); } } } Nothing can be done to change the EXTREME uniformity of the resulting image, as the code in srandom() makes a fundamental mistake: it uses a power of two as the modulo which is mathematically a `poor' choice. Code I suggest is better uses the largest 31-bit prime (2^31-1), which is a `good' choice mentioned in the literature (I can find references, if that would be useful) - the image resulting from the above is then very random. BTW, I discovered the flaw when I noticed my version of NetHack was NEVER giving me a lawful priest :) [nethack, like thousands of programs, calls srandom(time(0)) to seed the generator] Below is a patch of __srandom(), relative to glibc-1.09. Also required would be setting the initial value of randtbl to be that achieved by srandom(1), as these values are now different. I see that difference as being the only argument against using the improved randomizer. *** stdlib/__random.c Tue Jul 19 08:02:39 1994 --- stdlib/__random.c-new Mon Feb 20 11:02:46 1995 *************** *** 179,185 **** { register long int i; for (i = 1; i < rand_deg; ++i) ! state[i] = (1103515145 * state[i - 1]) + 12345; fptr = &state[rand_sep]; rptr = &state[0]; for (i = 0; i < 10 * rand_deg; ++i) --- 179,197 ---- { register long int i; for (i = 1; i < rand_deg; ++i) ! { ! /* ! * Implements the following, without overflowing 31 bits: ! * ! * state[i] = (16807 * state[i - 1]) % 2147483647; ! * ! * 2^31-1 (prime) = 2147483647 = 127773*16807+2836 ! */ ! long int hi = state[i-1] / 127773; ! long int lo = state[i-1] % 127773; ! long int test = 16807*lo - 2836*hi; ! state[i] = test + (test<0 ? 2147483647 : 0); ! } fptr = &state[rand_sep]; rptr = &state[0]; for (i = 0; i < 10 * rand_deg; ++i) Newsgroups: gnu.g++.help Subject: Re: Random Numbers References: <47qu5b$m4q@mozo.cc.purdue.edu> <47to1e$3fc@yuma.ACNS.ColoState.EDU> steffend@lamar.colostate.edu (Dave Steffen) writes: >In your code I don't see any call to a "seeding" function; WARNING WARNING WARNING WARNING WARNING WARNING WARNING WARNING The gnu libc random()/srandom() functions have (IMO) a fundamental flaw in their implementation (as do every implementation I've tested: rand()/srand(), lrand48()/srand48()). The random sequences do not vary much with the seed. This can be demonstrated with: main() { int i,l; int seed=0; printf("P1\n%d %d\n",100,100); for (l=0; l<100; l++) { srandom(seed); seed+=1; for (i=0; i<100; i++) { int b=random()&1; printf("%d\n",b); } } } (generates a PBM image of streams of random numbers from different starting seeds. The result SHOULD be white noise, but it looks more like a MacPaint fill pattern!!) Below is a patch of __srandom(), relative to glibc-1.09. Also required would be setting the initial value of randtbl to be that achieved by srandom(1), as these values are now different. (this has been reported to bug-glibc@prep.ai.mit.edu, but I've had no reply) *** stdlib/__random.c Tue Jul 19 08:02:39 1994 --- stdlib/__random.c-new Mon Feb 20 11:02:46 1995 *************** *** 179,185 **** { register long int i; for (i = 1; i < rand_deg; ++i) ! state[i] = (1103515145 * state[i - 1]) + 12345; fptr = &state[rand_sep]; rptr = &state[0]; for (i = 0; i < 10 * rand_deg; ++i) --- 179,197 ---- { register long int i; for (i = 1; i < rand_deg; ++i) ! { ! /* ! * Implements the following, without overflowing 31 bits: ! * ! * state[i] = (16807 * state[i - 1]) % 2147483647; ! * ! * 2^31-1 (prime) = 2147483647 = 127773*16807+2836 ! */ ! long int hi = state[i-1] / 127773; ! long int lo = state[i-1] % 127773; ! long int test = 16807*lo - 2836*hi; ! state[i] = test + (test<0 ? 2147483647 : 0); ! } fptr = &state[rand_sep]; rptr = &state[0]; for (i = 0; i < 10 * rand_deg; ++i) -- _-_|\ warwick@cs.uq.edu.au Linux: Say `No' to broken windows. / * <- Comp Sci Department, McD: http://student.uq.edu.au/~s002434/mcl.html \_.-._/ Univ. of Queensland, POV: http://student.uq.edu.au/~s002434/pov.html v Brisbane, Australia. ME: http://student.uq.edu.au/~s002434 ------------------------------- cut me here! -------------------------- -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sat Oct 5 02:35:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA05592 for current-outgoing; Sat, 5 Oct 1996 02:35:38 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-51.ut.nl.ibm.net [139.92.42.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA05578; Sat, 5 Oct 1996 02:35:30 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id XAA23464; Thu, 3 Oct 1996 23:58:03 +0100 (MET) Message-Id: <199610032258.XAA23464@vector.jhs.no_domain> To: Peter Wemm cc: current@freebsd.org Subject: Re: ETA for libg++-2.7.2 between 12 and 24 hours From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ In-reply-to: Your message of "Thu, 03 Oct 1996 03:34:20 +0800." <199610021934.DAA00393@spinner.DIALix.COM> Date: Thu, 03 Oct 1996 23:58:02 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: Peter Wemm > > I think I've finally finished it. I've not tested many canonical C++ > programs to make sure they link, but it pretty well builds OK now. If you need more C++ things: ports/comms/hylafax: 10M of src, not sure how much is C++ & how much C. For the new current compiler you'll need http://www.freebsd.org/~jhs/src/bsd/fixes/FreeBSD/\ ports/generic/comms/hylafax/patches/patch-ae (or something similar) (Discussed in: hylafax@freebsd.org)> Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Sat Oct 5 02:35:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA05614 for current-outgoing; Sat, 5 Oct 1996 02:35:46 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-51.ut.nl.ibm.net [139.92.42.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA05600; Sat, 5 Oct 1996 02:35:40 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id XAA23388; Thu, 3 Oct 1996 23:37:09 +0100 (MET) Message-Id: <199610032237.XAA23388@vector.jhs.no_domain> To: Gianmarco Giovannelli cc: current@freebsd.org Subject: Re: Desperately seeking ctm src-curr.1968 to 2000 From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ In-reply-to: Your message of "Wed, 02 Oct 1996 09:08:41 +0100." <3.0b26.32.19961002090639.00744b34@masternet.it> Date: Thu, 03 Oct 1996 23:37:08 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: Gianmarco Giovannelli > Subject: Re: Desperately seeking ctm src-curr.1968 to 2000 > Date: Wed, 02 Oct 1996 09:08:41 +0100 > Message-id: <3.0b26.32.19961002090639.00744b34@masternet.it> > > > Sorry for the off topics message, but I am looking for some missing ctm > files, from src-curr.1968 to src-curr.2000. I have that stuff, but you can also find it at ncftp -N ftp:freebsd.org/b/ftp/pub/CTM/src-cur/src-cur.WHATEVER unless its been zapped or moved mail me privately if you want mine. > > They are from this summer, when I was off the list . > > If someone have and want to send to me can attach them to an email > (obviusly if it is not a problem). > > Thanks again to everybody and sorry for the off-topics > > > > > > Regards... > > +-------------------------------------+--------------------+ > | Internet: gmarco@masternet.it | ,,, | > | Internet: gmarco@fi.nettuno.it | (o o) | > | BIX : ggiovannelli@bix.com | ---oo0-(_)-0oo--- | > | http://www.masternet.it/dsc/gmarco | Gianmarco | > +-------------------------------------+--------------------+ > Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Sat Oct 5 04:25:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA09123 for current-outgoing; Sat, 5 Oct 1996 04:25:07 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA09052; Sat, 5 Oct 1996 04:24:41 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id VAA21012; Sat, 5 Oct 1996 21:15:05 +1000 Date: Sat, 5 Oct 1996 21:15:05 +1000 From: Bruce Evans Message-Id: <199610051115.VAA21012@godzilla.zeta.org.au> To: ache@nagual.ru, joerg_wunsch@uriah.heep.sax.de Subject: Re: I plan to change random() for -current (was Re: rand() and random()) Cc: current@FreeBSD.org, freebsd-hackers@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> I don't think so. But they are much better with random(). See xmine, >> if you wanna get a nice example. It generates totally predictable >> layouts when using rand(). > >Totally predictable layouts not rand() illness only but random() too. >It not depends well on different initial state, producing the same >sequence. I finally dig out initial posting (below). It says that the 0th bit is the most non-random. In fact, it is obvious from the formula for rand() that (rand() & 1) == previous_value_returned_by_rand ^ 1 :-(. The posting also says that the bad values for rand() make the seeding for random() bad. This seems reasonable. >IMHO we need to change our random() as suggested. How do you know that the suggested method is better? --- >From: warwick@cs.uq.edu.au (Warwick Allison) >... >warner@rmcs.cranfield.ac.uk (Alistair (Joe) Warner) writes: > >> BSD: state[i] = 1103515245 * state[i - 1] + 12345; >> Linux: state[i] = 1103515145 * state[i - 1] + 12345; ISO C example: next = 1103515245 * next + 12345; return (unsigned int)(next / 65536) % 32768; I.e., it returns bits 16-31 of the current state (right shifted 16). This is said to be better. Folklore says that someone broke rand() by not discarding the low bits when ints became 32 bits. >value will make NO DIFFERENCE. The change I give below is of the type >required for success. > > >#include > >#define LOOP 200 >#define ITER 200 > >main() >{ > int s=time(0); > int i,l,m,j; > > int seed=0; > > printf("P1\n%d %d\n",ITER,LOOP); > for (l=0; l srandom(seed); seed+=1; > for (i=0; i int b=(random()>>8)&1; /* remove >>8 for WORSE */ > printf("%d\n",b); > } > } >} Similarly for rand(). You can throw away the lowest 16 bits yourself to get a rand() no worse than the example in the ISO C standard. This is said to be bad, but I think the badness is more in the brokenness as specified (the number of starting states is limited by the srand() interface) and in the limited period (which is inherent in the LCRNG implementation) than in the coefficients for the LCRNG. >>To: bug-glibc@prep.ai.mit.edu >>cc: >>Subject: PARTIAL FIX FOR: srandom() in libc >-------- >... >Nothing can be done to change the EXTREME uniformity of the resulting >image, as the code in srandom() makes a fundamental mistake: it uses a >power of two as the modulo which is mathematically a `poor' choice. >Code I suggest is better uses the largest 31-bit prime (2^31-1), which >is a `good' choice mentioned in the literature (I can find references, >if that would be useful) - the image resulting from the above is then According to Knuth, moduli of the form 2^n+1 and 2^n-1 have the advantage that the low order bits are just as random as the high order ones. However, "In most applications, the low-order bits are insignificant, and the choice m=w [modulus = 2^n] is quite satisfactory - provided the programmer using the random numbers does so wisely". In the ISO example, it is actually an advantage to have randomness concentrated in the high order bits (is it?). ISO only guarantees 16 bit integers, so a portably example can only return 15 bits of randomness, so the low bits are not useful; OTOH, longs have to be used to get a reasonably large period - 16 bit ints are too small. >! /* >! * Implements the following, without overflowing 31 bits: >! * >! * state[i] = (16807 * state[i - 1]) % 2147483647; >! * >! * 2^31-1 (prime) = 2147483647 = 127773*16807+2836 >! */ >! long int hi = state[i-1] / 127773; >! long int lo = state[i-1] % 127773; >! long int test = 16807*lo - 2836*hi; >! state[i] = test + (test<0 ? 2147483647 : 0); This method is also found in the BSD4.4Lite libkern/rand.c. I guess it can be trusted (as much as the BSD rand.c :-). Bruce From owner-freebsd-current Sat Oct 5 05:17:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA13188 for current-outgoing; Sat, 5 Oct 1996 05:17:58 -0700 (PDT) Received: from al.imforei.apana.org.au (pjchilds@al.imforei.apana.org.au [202.12.89.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA13166 for ; Sat, 5 Oct 1996 05:17:49 -0700 (PDT) Received: (from pjchilds@localhost) by al.imforei.apana.org.au (8.8.0/8.7.3) id VAA16637; Sat, 5 Oct 1996 21:47:41 +0930 (CST) Date: Sat, 5 Oct 1996 21:47:41 +0930 (CST) From: Peter Childs Message-Id: <199610051217.VAA16637@al.imforei.apana.org.au> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch), freebsd-current@freebsd.org Subject: Re: 960501 to -current --> Error code 1 X-Newsreader: TIN [version 1.2 PL2] Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199610041942.VAA04603@uriah.heep.sax.de> you wrote: : I think i've seen this, too, but it went away after rebuilding some : tool. Forgot which one though... Re-read the archives for the : -current mailing list. "as". But as noted the gcc/as/libc stuff is still settling, so it would pay to be right up to date. Peter -- Peter Childs --- http://www.imforei.apana.org.au/~pjchilds Finger pjchilds@al.imforei.apana.org.au for public PGP key Drag me, drop me, treat me like an object! From owner-freebsd-current Sat Oct 5 06:51:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA17935 for current-outgoing; Sat, 5 Oct 1996 06:51:44 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA17923 for ; Sat, 5 Oct 1996 06:51:40 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA19206; Sat, 5 Oct 1996 15:51:00 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA19420; Sat, 5 Oct 1996 15:50:59 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id PAA00595; Sat, 5 Oct 1996 15:37:12 +0200 (MET DST) From: J Wunsch Message-Id: <199610051337.PAA00595@uriah.heep.sax.de> Subject: Re: Help! /bin/csh is gone! To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sat, 5 Oct 1996 15:37:12 +0200 (MET DST) Cc: bartol@salk.edu (Tom Bartol) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Tom Bartol at "Oct 5, 96 00:38:06 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 As Tom Bartol wrote: > sd0(ahc0:0:0): MEDIUM ERROR info:189e1c asc:14,1 Record not found > , retries:4 Try turning on bad sector reallocation. Have a look into the FAQ about the required procedure (search for the term ``AWRE''). Bad sectors are quite normal on a magnetic storage medium, and the vendor should have reserved enough replacement storage. Btw., my new Seacrate ST32155N turns out to be the first disk i've ever seen that has it enabled by default. -- 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 Sat Oct 5 07:44:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA19943 for current-outgoing; Sat, 5 Oct 1996 07:44:59 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [193.91.212.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA19938 for ; Sat, 5 Oct 1996 07:44:56 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail-queue invoked from smtpd); 5 Oct 1996 14:44:51 +0000 (GMT) Received: from localhost (HELO verdi.nethelp.no) (@127.0.0.1) by localhost with SMTP; 5 Oct 1996 14:44:51 +0000 (GMT) To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-current@freebsd.org Subject: Re: Help! /bin/csh is gone! In-Reply-To: Your message of "Sat, 5 Oct 1996 15:37:12 +0200 (MET DST)" References: <199610051337.PAA00595@uriah.heep.sax.de> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 05 Oct 1996 16:44:50 +0200 Message-ID: <7249.844526690@verdi.nethelp.no> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Try turning on bad sector reallocation. Have a look into the FAQ > about the required procedure (search for the term ``AWRE''). Bad > sectors are quite normal on a magnetic storage medium, and the vendor > should have reserved enough replacement storage. > > Btw., my new Seacrate ST32155N turns out to be the first disk i've > ever seen that has it enabled by default. I bought an IBM 2.16 GByte SCSI-disk (Ultrastar ES) a couple of weeks ago - it also had reallocation turned on by default. I was pleasantly surprised. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Sat Oct 5 09:30:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA24593 for current-outgoing; Sat, 5 Oct 1996 09:30:39 -0700 (PDT) Received: from math.psu.edu (root@leibniz.math.psu.edu [146.186.130.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA24584 for ; Sat, 5 Oct 1996 09:30:33 -0700 (PDT) Received: from augusta.math.psu.edu (cross@augusta.math.psu.edu [146.186.132.2]) by math.psu.edu (8.7.5/8.7.3) with ESMTP id MAA04232 for ; Sat, 5 Oct 1996 12:30:31 -0400 (EDT) Received: (cross@localhost) by augusta.math.psu.edu (8.7.5/8.6.9) id MAA18939 for current@freebsd.org; Sat, 5 Oct 1996 12:30:28 -0400 (EDT) Date: Sat, 5 Oct 1996 12:30:28 -0400 (EDT) Message-Id: <199610051630.MAA18939@augusta.math.psu.edu> From: Dan Cross Subject: Qmail changes... (repost) To: undisclosed-recipients:; Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk About a week ago, I posted some diffs for from(1) and mail(1) that make them honor the $MAIL environment variable. My motivation was supporting the mailboxes created by qmail, which are not put into /var/mail but instead into the user's home directory. (ie, ~/Mailbox is the user's default maildrop.) However, these changes were never committed to the source tree, and I never heard anything back about them. Anyway, it would be really great if someone could commit these to the source tree, but if not, could someone at least tell me so that I can make provisions on my own system? Thanks! - Dan C. --- *** /usr/src/usr.bin/from/from.c 1996/09/29 01:40:35 1.1 --- /usr/src/usr.bin/from/from.c 1996/09/29 01:58:06 *************** *** 42,50 **** --- 42,52 ---- #endif /* not lint */ #include + #include #include #include + #include #include #include *************** *** 83,98 **** argv += optind; if (!file) { ! if (!(file = *argv)) { ! if (!(pwd = getpwuid(getuid()))) { ! fprintf(stderr, "from: no password file entry for you.\n"); ! exit(1); } - file = pwd->pw_name; } - (void)sprintf(buf, "%s/%s", _PATH_MAILDIR, file); - file = buf; } /* read from stdin */ --- 85,106 ---- argv += optind; if (!file) { ! if (*argv) { ! (void)sprintf(buf, "%s/%s", _PATH_MAILDIR, *argv); ! file = buf; ! } else { ! if (!(file = getenv("MAIL"))) { ! if (!(pwd = getpwuid(getuid()))) { ! (void)fprintf(stderr, "from: no password file entry for you.\n"); ! exit(1); ! } ! file = pwd->pw_name; ! (void)sprintf(buf, ! "%s/%s", _PATH_MAILDIR, file); ! file = buf; } } } /* read from stdin */ *** /usr/src/usr.bin/from/from.1 1996/09/29 01:58:15 1.1 --- /usr/src/usr.bin/from/from.1 1996/09/29 14:45:01 *************** *** 72,77 **** --- 72,82 ---- .Ar user Ns 's mailbox, is examined instead of the invoker's own mailbox. (Privileges are required.) + .Sh ENVIRONMENT + .Bl -tag -width Fl + .It Ev MAIL + If set, the location of the invoker's mailbox. Otherwise, the default + in /var/mail is used. .Sh FILES .Bl -tag -width /var/mail/* -compact .It Pa /var/mail/* *** /usr/src/usr.bin/mail/v7.local.c 1996/09/29 02:00:23 1.1 --- /usr/src/usr.bin/mail/v7.local.c 1996/09/29 02:03:41 *************** *** 55,61 **** findmail(user, buf) char *user, *buf; { ! (void)sprintf(buf, "%s/%s", _PATH_MAILDIR, user); } /* --- 55,66 ---- findmail(user, buf) char *user, *buf; { ! char *tmp = getenv("MAIL"); ! ! if (tmp == NULL) ! (void)sprintf(buf, "%s/%s", _PATH_MAILDIR, user); ! else ! (void)strcpy(buf, tmp); } /* *** /usr/src/usr.bin/mail/mail.1 1996/09/29 14:45:24 1.1 --- /usr/src/usr.bin/mail/mail.1 1996/09/29 14:47:59 *************** *** 985,991 **** .Ev HOME and .Ev USER ! environment variables. .Sh FILES .Bl -tag -width /usr/share/misc/Mail.help* -compact .It Pa /var/mail/* --- 985,995 ---- .Ev HOME and .Ev USER ! environment variables. Also, if the ! .Ev MAIL ! environment variable is set, it is used as the ! location of the user's mailbox instead of the ! default in /var/mail. .Sh FILES .Bl -tag -width /usr/share/misc/Mail.help* -compact .It Pa /var/mail/* From owner-freebsd-current Sat Oct 5 10:10:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26775 for current-outgoing; Sat, 5 Oct 1996 10:10:59 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA26765 for ; Sat, 5 Oct 1996 10:10:52 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA20694; Sat, 5 Oct 1996 12:50:09 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sat, 5 Oct 1996 12:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id IAA11248; Sat, 5 Oct 1996 08:53:58 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id IAA05170; Sat, 5 Oct 1996 08:53:49 -0400 (EDT) Date: Sat, 5 Oct 1996 08:53:49 -0400 (EDT) From: Thomas David Rivers Message-Id: <199610051253.IAA05170@lakes.water.net> To: ache@nagual.ru, ponds!uriah.heep.sax.de!joerg_wunsch Subject: Re: I plan to change random() for -current (was Re: rand() and random()) Cc: ponds!freebsd.org!current, ponds!freebsd.org!freebsd-hackers Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I don't think so. But they are much better with random(). See xmine, > > if you wanna get a nice example. It generates totally predictable > > layouts when using rand(). > > Totally predictable layouts not rand() illness only but random() too. > It not depends well on different initial state, producing the same > sequence. I finally dig out initial posting (below). > > IMHO we need to change our random() as suggested. > When working with the Data General runtime library's on AOS/VS (remember that?) we discovered a similar situation - our rand() wasn't random... A user had sent in a marvelous demonstration of this - generate several thousand X/Y pairs with calls to rand() and make a scatter plot of them. (i.e. a monte-carlo idea..) When we plotted these points, we got a definite line!!!! I agree - fix rand()... - Dave R. - From owner-freebsd-current Sat Oct 5 10:56:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA28827 for current-outgoing; Sat, 5 Oct 1996 10:56:00 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA28802; Sat, 5 Oct 1996 10:55:50 -0700 (PDT) Received: by sovcom.kiae.su id AA07653 (5.65.kiae-1 ); Sat, 5 Oct 1996 20:54:40 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sat, 5 Oct 96 20:54:40 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id VAA03726; Sat, 5 Oct 1996 21:52:28 +0400 (MSD) Message-Id: <199610051752.VAA03726@nagual.ru> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610051115.VAA21012@godzilla.zeta.org.au> from "Bruce Evans" at "Oct 5, 96 09:15:05 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sat, 5 Oct 1996 21:52:27 +0400 (MSD) Cc: joerg_wunsch@uriah.heep.sax.de, current@FreeBSD.org, freebsd-hackers@FreeBSD.org From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast 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 > >IMHO we need to change our random() as suggested. > > How do you know that the suggested method is better? Well, I am not research random generators area personally, but given formulae is 1) well-known as good one, 2) give good results with proposed test, 3) already used in libkern/random.c, 4) better than previous one in all parameters. > ISO C example: next = 1103515245 * next + 12345; > return (unsigned int)(next / 65536) % 32768; > > I.e., it returns bits 16-31 of the current state (right shifted 16). This > is said to be better. Folklore says that someone broke rand() by not > discarding the low bits when ints became 32 bits. It is not good enough to live due to unrandom nature of original formulae. I.e. _all_ bits are unrandom, and lower ones are more unrandom. This formulae not good enough even for 16bits. At this moment I worry about random() only, lets consider rand() things after it. > >! /* > >! * Implements the following, without overflowing 31 bits: > >! * > >! * state[i] = (16807 * state[i - 1]) % 2147483647; > >! * > >! * 2^31-1 (prime) = 2147483647 = 127773*16807+2836 > >! */ > >! long int hi = state[i-1] / 127773; > >! long int lo = state[i-1] % 127773; > >! long int test = 16807*lo - 2836*hi; > >! state[i] = test + (test<0 ? 2147483647 : 0); > > This method is also found in the BSD4.4Lite libkern/rand.c. I guess it > can be trusted (as much as the BSD rand.c :-). So we can safely import it even not from this posting (which can be GNU diseased) but from our own libkern/rand.c Here proposed patch, initial table regenerated to conform default seed value (1): *** random.c.orig Sat Oct 5 20:41:57 1996 --- random.c Sat Oct 5 21:45:01 1996 *************** *** 122,128 **** /* * Initially, everything is set up as if from: * ! * initstate(1, &randtbl, 128); * * Note that this initialization takes advantage of the fact that srandom() * advances the front and rear pointers 10*rand_deg times, and hence the --- 122,128 ---- /* * Initially, everything is set up as if from: * ! * initstate(1, randtbl, 128); * * Note that this initialization takes advantage of the fact that srandom() * advances the front and rear pointers 10*rand_deg times, and hence the *************** *** 135,146 **** static long randtbl[DEG_3 + 1] = { TYPE_3, ! 0x9a319039, 0x32d9c024, 0x9b663182, 0x5da1f342, 0xde3b81e0, 0xdf0a6fb5, ! 0xf103bc02, 0x48f340fb, 0x7449e56b, 0xbeb1dbb0, 0xab5c5918, 0x946554fd, ! 0x8c2e680f, 0xeb3d799f, 0xb11ee0b7, 0x2d436b86, 0xda672e2a, 0x1588ca88, ! 0xe369735d, 0x904f35f7, 0xd7158fd6, 0x6fa6f051, 0x616e6b96, 0xac94efdc, ! 0x36413f93, 0xc622c298, 0xf5a42ab8, 0x8a88d77b, 0xf5ad9d0e, 0x8999220b, ! 0x27fb47b9, }; /* --- 135,146 ---- static long randtbl[DEG_3 + 1] = { TYPE_3, ! 0x991539b1, 0x16a5bce3, 0x6774a4cd, 0x3e01511e, 0x4e508aaa, 0x61048c05, ! 0xf5500617, 0x846b7115, 0x6a19892c, 0x896a97af, 0xdb48f936, 0x14898454, ! 0x37ffd106, 0xb58bff9c, 0x59e17104, 0xcf918a49, 0x09378c83, 0x52c7a471, ! 0x8d293ea9, 0x1f4fc301, 0xc3db71be, 0x39b44e1c, 0xf8a44ef9, 0x4c8b80b1, ! 0x19edc328, 0x87bf4bdd, 0xc9b240e5, 0xe9ee4b1b, 0x4382aee7, 0x535b6b41, ! 0xf3bec5da }; /* *************** *** 192,206 **** srandom(x) unsigned int x; { ! register int i, j; if (rand_type == TYPE_0) state[0] = x; else { - j = 1; state[0] = x; ! for (i = 1; i < rand_deg; i++) ! state[i] = 1103515245 * state[i - 1] + 12345; fptr = &state[rand_sep]; rptr = &state[0]; for (i = 0; i < 10 * rand_deg; i++) --- 192,221 ---- srandom(x) unsigned int x; { ! register int i; if (rand_type == TYPE_0) state[0] = x; else { state[0] = x; ! for (i = 1; i < rand_deg; i++) { ! /* ! * Compute state[i] = (7^5 * state[i - 1]) mod (2^31 - 1) ! * wihout overflowing 31 bits: ! * (2^31 - 1) = 127773 * (7^5) + 2836 ! * From "Random number generators: good ones are hard to find", ! * Park and Miller, Communications of the ACM, vol. 31, no. 10, ! * October 1988, p. 1195. ! */ ! long hi, lo, t; ! ! hi = state[i - 1] / 127773; ! lo = state[i - 1] % 127773; ! t = 16807 * lo - 2836 * hi; ! if (t <= 0) ! t += 0x7fffffff; ! state[i] = t; ! } fptr = &state[rand_sep]; rptr = &state[0]; for (i = 0; i < 10 * rand_deg; i++) *************** *** 348,356 **** { long i; ! if (rand_type == TYPE_0) ! i = state[0] = (state[0] * 1103515245 + 12345) & 0x7fffffff; ! else { *fptr += *rptr; i = (*fptr >> 1) & 0x7fffffff; /* chucking least random bit */ if (++fptr >= end_ptr) { --- 363,386 ---- { long i; ! if (rand_type == TYPE_0) { ! /* ! * Compute i = (7^5 * state[0]) mod (2^31 - 1) ! * wihout overflowing 31 bits: ! * (2^31 - 1) = 127773 * (7^5) + 2836 ! * From "Random number generators: good ones are hard to find", ! * Park and Miller, Communications of the ACM, vol. 31, no. 10, ! * October 1988, p. 1195. ! */ ! long hi, lo; ! ! hi = state[0] / 127773; ! lo = state[0] % 127773; ! i = 16807 * lo - 2836 * hi; ! if (i <= 0) ! i += 0x7fffffff; ! state[0] = i; ! } else { *fptr += *rptr; i = (*fptr >> 1) & 0x7fffffff; /* chucking least random bit */ if (++fptr >= end_ptr) { -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sat Oct 5 11:49:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA01976 for current-outgoing; Sat, 5 Oct 1996 11:49:20 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA01953; Sat, 5 Oct 1996 11:49:03 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.6/8.7.3) with ESMTP id UAA23755; Sat, 5 Oct 1996 20:47:51 +0200 (SAT) Message-Id: <199610051847.UAA23755@grumble.grondar.za> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) cc: bde@zeta.org.au (Bruce Evans), joerg_wunsch@uriah.heep.sax.de, current@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: I plan to change random() for -current (was Re: rand() and random()) Date: Sat, 05 Oct 1996 20:47:50 +0200 From: Mark Murray Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= wrote: > > >IMHO we need to change our random() as suggested. > > > > How do you know that the suggested method is better? > > Well, I am not research random generators area personally, > but given formulae is 1) well-known as good one, 2) give > good results with proposed test, 3) already used in libkern/random.c, > 4) better than previous one in all parameters. Why don't you use the RNG engine from /dev/random in random_machdep.c? There is even a routine in ther (#ifdef'ed out) for this use. That thing gives _great_ random numbers, and it is already in the kernel. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Sat Oct 5 11:59:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA02635 for current-outgoing; Sat, 5 Oct 1996 11:59:18 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA02616; Sat, 5 Oct 1996 11:59:12 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id EAA30329; Sun, 6 Oct 1996 04:56:27 +1000 Date: Sun, 6 Oct 1996 04:56:27 +1000 From: Bruce Evans Message-Id: <199610051856.EAA30329@godzilla.zeta.org.au> To: ache@nagual.ru, bde@zeta.org.au Subject: Re: I plan to change random() for -current (was Re: rand() and random()) Cc: current@freebsd.org, freebsd-hackers@freebsd.org, joerg_wunsch@uriah.heep.sax.de Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> ISO C example: next = 1103515245 * next + 12345; >> return (unsigned int)(next / 65536) % 32768; >> >> I.e., it returns bits 16-31 of the current state (right shifted 16). This >> is said to be better. Folklore says that someone broke rand() by not >> discarding the low bits when ints became 32 bits. > >It is not good enough to live due to unrandom nature of original formulae. >I.e. _all_ bits are unrandom, and lower ones are more unrandom. >This formulae not good enough even for 16bits. No, it is probably fine for 16 bits (see Knuth), but probably no good for random() since random() wants to use all the bits. >At this moment I worry about random() only, lets consider rand() things >after it. OK. >> This method is also found in the BSD4.4Lite libkern/rand.c. I guess it >> can be trusted (as much as the BSD rand.c :-). > >So we can safely import it even not from this posting (which can be >GNU diseased) but from our own libkern/rand.c Not so safe. Something might depend on the doemented behaviour that the sequence after srandom() depends on the seed (not even on the library version :-). >Here proposed patch, initial table regenerated to conform default >seed value (1): Commit it and see if we get complaints. ! * initstate(1, randtbl, 128); Lost a tab here. >! for (i = 1; i < rand_deg; i++) { >! /* >! * Compute state[i] = (7^5 * state[i - 1]) mod (2^31 - 1) >! * wihout overflowing 31 bits: >! * (2^31 - 1) = 127773 * (7^5) + 2836 >! * From "Random number generators: good ones are hard to find", >! * Park and Miller, Communications of the ACM, vol. 31, no. 10, >! * October 1988, p. 1195. >! */ >! long hi, lo, t; >! >! hi = state[i - 1] / 127773; >! lo = state[i - 1] % 127773; >! t = 16807 * lo - 2836 * hi; This is much slower than the current rand() or random(). On a P133, measured over 10^7 calls to statically linked libraries: rand: 174 nsec random: 275 nsec random from libkern: 673 nsec The division in the libkern random() is apparently very expensive, although gcc optimizes it nicely. Knuth gives an algorithm for dividing by (2^n + 1) using only one multiplication, one subtraction, one test and 2 additions. The method for (2^n - 1) is an exercise :-). I think these methods depend on a double width multiplication, which the i386 has. The portable C method is slow because it must work without overflowing 32 bits. We can write the Knuth algorithm in unportable gCc using long long. Gcc optimizes multiplications of the form `(long long)x * y' (where x and y are 32 bit) nicely on the i386. ! /* ! * Compute i = (7^5 * state[0]) mod (2^31 - 1) Perhaps make this a subroutine to avoid duplication and allow easy changing. Division takes 10-20 times longer than a subroutine call on Pentiums. Bruce From owner-freebsd-current Sat Oct 5 12:29:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA03874 for current-outgoing; Sat, 5 Oct 1996 12:29:15 -0700 (PDT) Received: from scooter.quickweb.com (scooter.quickweb.com [199.212.134.8]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA03811; Sat, 5 Oct 1996 12:26:52 -0700 (PDT) Received: from localhost (mark@localhost) by scooter.quickweb.com (8.6.12/8.6.12) with SMTP id PAA00426; Sat, 5 Oct 1996 15:26:14 -0400 Date: Sat, 5 Oct 1996 15:26:13 -0400 (EDT) From: Mark Mayo X-Sender: mark@scooter.quickweb.com To: freebsd-questions@freebsd.org cc: freebsd-current@freebsd.org Subject: Java,Netscape, & AccelX Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I still haven't got Java working under Netscape 3.0 yet, and I thought maybe somebody has already dealt with this problem. First of all, I run the August 2.2-SNAP, on a PPRO 150, with a Matrox Millenium video card. To get the Matrox working I bought the AcceleratedX server from Xinside -- I think this may be the problem. When I hit a java applet, the browser leaves space for the applet, but it never actually displays. However, when I set my display over to my 486 win95 machine (running eXceed 5) the java applets show up just fine... which pretty much means my X server is the cause of my problems, no? When I installed the AccelX server, I only had one problem - it couldn't find libc.so.2.2 -> so I linked it to /usr/lib/libc.so.3.0. Everything seemed fine.. the X server ran with no problems, and I was amazed at the performance of AccelX!! Until it wouldn't show Java, that is :-) So, after it displayed on the PC, I grabbed the older libc.so.2.2 from the 2.1.5 CD and threw it in /usr/lib. I rebooted and the system seemed to come up fine. But still no Java -- plus, now when I display to the PC, I don't get Java either, and the JDK appletviewer doesn't work.. So I quickly put the link from libc.so.2.2 -> lib.so.3.0 back and now I'm back to the original problem. I'm guessing it's some sort of clash between libc.so and the AccelX server -- am I correct in assuming this? Someone please tell me they've solver this problem and that I'm not a random incident with no hope... I'm contacting Xinside as well, but I believe they only support up to v2.1R. TIA, -Mark ------------------------------------------- | Mark Mayo mark@quickweb.com | | C-Soft www.quickweb.com | ------------------------------------------- "To iterate is human, to recurse divine." - L. Peter Deutsch From owner-freebsd-current Sat Oct 5 13:09:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA05200 for current-outgoing; Sat, 5 Oct 1996 13:09:12 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA05195 for ; Sat, 5 Oct 1996 13:09:02 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.7.6/8.7.3) id WAA24973 for freebsd-current@FreeBSD.ORG; Sat, 5 Oct 1996 22:08:51 +0200 (SAT) From: John Hay Message-Id: <199610052008.WAA24973@zibbi.mikom.csir.co.za> Subject: Proposed addition to build-tools target To: freebsd-current@FreeBSD.ORG (FreeBSD-current) Date: Sat, 5 Oct 1996 22:08:51 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL24 (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, I have been trying to build an 2.2 SNAP on a 2.1.5 machine again. Except for two problems it seems to work fine. The first problem is awk. In 2.1.5 it is linked to libgnuregex.so.2.0, libm.so.2.0 and libc.so.2.2. During the "make world" process all the libraries are rebuild, also libgnuregex.so.2.0 which then needs some new functionality from libc.so.3.0. Awk is still linked to libc.so.2.0 so when it is needed during the "make includes" fase it fails with: -------------- angel:/usr/src/usr.bin/kdump # make clean rm -f a.out Errs errs mklog kdump kdump.o ioctl.o subr.o ioctl.c kdump.1.gz angel:/usr/src/usr.bin/kdump # make depend /bin/sh /usr/src/usr.bin/kdump/mkioctls > ioctl.c (null): Undefined symbol "_collate_range_cmp" called from awk:/usr/lib/libgnuregex.so.2.0 at 0x80390cc cpp: output pipe has been closed *** Error code 1 Stop. angel:/usr/src/usr.bin/kdump # --------------- To work around this problem I would recommend that we add awk to the "build-tools" target. It will not help to add it to the "bootstrap" target because at that stage the libc.so.3.0 library does not exist. I attach a patch for that at the end. With this patch the "make world" target should be able to take a 2.1.5 machine to 2.2-current. The reason I say this is a workaround is that I think libgnuregex.so should have been bumped from version 2.0 to 3.0 when it started to depend on libc.so.3.0 features. The way it is now we can't use a 2.1.5 compiled program that use those functions on a -current system. I think it is an unnecessary incompatability which we can easily avoid. My second problem is that the latest version of release/doFS.sh (1.8) breaks on a 2.1.5 machine. Something with the labels on a vn device. The previous version does work. I will have a look into that. John -- John Hay -- John.Hay@mikom.csir.co.za *** Makefile.org Fri Oct 4 10:48:27 1996 --- Makefile Fri Oct 4 23:50:30 1996 *************** *** 517,522 **** --- 517,524 ---- ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} cd ${.CURDIR}/usr.sbin/zic && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} + cd ${.CURDIR}/gnu/usr.bin/awk && ${MAKE} depend && \ + ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} cd ${.CURDIR}/gnu/usr.bin/groff && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all install ${CLEANDIR} ${OBJDIR} From owner-freebsd-current Sat Oct 5 13:23:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA05997 for current-outgoing; Sat, 5 Oct 1996 13:23:08 -0700 (PDT) Received: from quagmire.ki.net (root@quagmire.ki.net [205.150.102.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA05950; Sat, 5 Oct 1996 13:22:21 -0700 (PDT) Received: from spirit.ki.net (root@spirit.ki.net [205.150.102.51]) by quagmire.ki.net (8.7.5/8.7.5) with ESMTP id QAA01977; Sat, 5 Oct 1996 16:21:56 -0400 (EDT) Received: from localhost (scrappy@localhost) by spirit.ki.net (8.7.5/8.7.3) with SMTP id QAA13782; Sat, 5 Oct 1996 16:22:06 -0400 (EDT) X-Authentication-Warning: spirit.ki.net: scrappy owned process doing -bs Date: Sat, 5 Oct 1996 16:22:02 -0400 (EDT) From: "Marc G. Fournier" To: current@freebsd.org cc: questions@freebsd.org Subject: yp_first error on WWW virtual domains... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I'm attempting to combine IP aliasing and HTTP virtual domains on my 2.2-Current box, and am failing miserably... I've got my ed0 device setup so that it is aliased for: 205.150.102.[51-62] 204.101.125.[200-211] As soon as I try to enable a 13th Web server, I start getting: yp_first: clnt_call: RPC: Timed out And if I go back down to 12, its all fine. I'm thinking that there is either a setting I should be increasing in the kernel, or it has something to do with the IP aliasing... Anyone have experience with this? Thanks... Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org From owner-freebsd-current Sat Oct 5 13:58:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07796 for current-outgoing; Sat, 5 Oct 1996 13:58:52 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA07782; Sat, 5 Oct 1996 13:57:26 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA11278; Sat, 5 Oct 1996 13:53:11 -0700 From: Terry Lambert Message-Id: <199610052053.NAA11278@phaeton.artisoft.com> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Sat, 5 Oct 1996 13:53:11 -0700 (MST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org, current@freebsd.org In-Reply-To: <199610050835.MAA00671@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Oct 5, 96 12:35:20 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 > > I don't think so. But they are much better with random(). See xmine, > > if you wanna get a nice example. It generates totally predictable > > layouts when using rand(). > > Totally predictable layouts not rand() illness only but random() too. > It not depends well on different initial state, producing the same > sequence. I finally dig out initial posting (below). > > IMHO we need to change our random() as suggested. There is a historical dependence of much physics code on the repeatability of identical seeding for the linear congruential generator as a "randomness" base for repeatable Monte Carlo based testing of relativistically invariant P-P, N-P, and N-N pair production collisions. Such collisions are used to test "allowability" of given target states using the soloutions of multiple Feynman-Dyson diagrams as constraints on the resulting pairs (velocity, direction, angular momentum, etc.). The idea is that the real world has more constraints on allowable pair production events than simple relatavistic invariance. If you *do* change the random algorithms, then you should *leave the rand48() code along*. I can not stress this enough. You will damage repeatability of experiments for which source code is unavailable, and only the results remain. This is only *one* example of a real dependence on the algorithm used to implement random functions. Please be sure that you are not damaging anything in your zeal to "correct" thjis problem. 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 Sat Oct 5 14:34:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09518 for current-outgoing; Sat, 5 Oct 1996 14:34:35 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09502 for ; Sat, 5 Oct 1996 14:34:29 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id XAA14873 for ; Sat, 5 Oct 1996 23:34:03 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id XAA14444 for freebsd-current@FreeBSD.ORG; Sat, 5 Oct 1996 23:34:08 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.0/keltia-uucp-2.9) id XAA04869; Sat, 5 Oct 1996 23:31:25 +0200 (MET DST) Message-Id: <199610052131.XAA04869@keltia.freenix.fr> Date: Sat, 5 Oct 1996 23:31:24 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@FreeBSD.ORG (FreeBSD-current users) Subject: Re: Help! /bin/csh is gone! In-Reply-To: <199610051337.PAA00595@uriah.heep.sax.de>; from J Wunsch on Oct 5, 1996 15:37:12 +0200 References: <199610051337.PAA00595@uriah.heep.sax.de> X-Mailer: Mutt 0.45i Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2522 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > Btw., my new Seacrate ST32155N turns out to be the first disk i've > ever seen that has it enabled by default. It wasn't enabled on my Conner 1080S but the brand new IBM DORS 32160 I just brought has both AWRE and write-back cache enabled. Works like a charm and is faster than the Conner (5.5 MB/s read and 5.5 MB/s write). I am happy. (bt0:0:0): "IBM DORS-32160 WA6A" type 0 fixed SCSI 2 sd0(bt0:0:0): Direct-Access 2063MB (4226725 512 byte sectors) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #23: Sun Sep 29 14:56:23 MET DST 1996 From owner-freebsd-current Sat Oct 5 14:36:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09762 for current-outgoing; Sat, 5 Oct 1996 14:36:26 -0700 (PDT) Received: from synwork.com (synwork.com [199.3.234.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA09748; Sat, 5 Oct 1996 14:36:18 -0700 (PDT) Received: from localhost (flaq@localhost) by synwork.com (8.7.5/8.6.12) with SMTP id QAA25374; Sat, 5 Oct 1996 16:34:41 -0500 (CDT) Date: Sat, 5 Oct 1996 16:34:41 -0500 (CDT) From: SysAdmin To: Mark Mayo cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Java,Netscape, & AccelX In-Reply-To: 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, 5 Oct 1996, Mark Mayo wrote: > > Hi all, I still haven't got Java working under Netscape 3.0 yet, and I > thought maybe somebody has already dealt with this problem. > > First of all, I run the August 2.2-SNAP, on a PPRO 150, with a Matrox > Millenium video card. To get the Matrox working I bought the AcceleratedX > server from Xinside -- I think this may be the problem. When I hit a java > applet, the browser leaves space for the applet, but it never actually > displays. However, when I set my display over to my 486 win95 machine > (running eXceed 5) the java applets show up just fine... which pretty much > means my X server is the cause of my problems, no? > > When I installed the AccelX server, I only had one problem - it couldn't > find libc.so.2.2 -> so I linked it to /usr/lib/libc.so.3.0. Everything > seemed fine.. the X server ran with no problems, and I was amazed at the > performance of AccelX!! Until it wouldn't show Java, that is :-) > > So, after it displayed on the PC, I grabbed the older libc.so.2.2 from the > 2.1.5 CD and threw it in /usr/lib. I rebooted and the system seemed to > come up fine. But still no Java -- plus, now when I display to the PC, I > don't get Java either, and the JDK appletviewer doesn't work.. > So I quickly put the link from libc.so.2.2 -> lib.so.3.0 back and now I'm > back to the original problem. > > I'm guessing it's some sort of clash between libc.so and the AccelX server > -- am I correct in assuming this? > > Someone please tell me they've solver this problem and that I'm not a > random incident with no hope... I'm contacting Xinside as well, but I > believe they only support up to v2.1R. > It's starting to sound more and more like it is an AcceleratedX problem! Mike ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ Syn-Work Media, Inc. | WWW Development & Hosting | Life Safety http://www.synwork.com | Systems Integration | CCTV mike@synwork.com | Voice/Data/Fiber | Access Control Flaq on IRC | Dukane Distributor | BICSI/RCDD :|:|:|: Powered By FreeBSD :|:|:|: Turning PC's Into Workstations ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ From owner-freebsd-current Sat Oct 5 14:57:34 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10833 for current-outgoing; Sat, 5 Oct 1996 14:57:34 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA10814; Sat, 5 Oct 1996 14:57:20 -0700 (PDT) Received: by sovcom.kiae.su id AA23425 (5.65.kiae-1 ); Sun, 6 Oct 1996 00:42:15 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 6 Oct 96 00:42:15 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id BAA06368; Sun, 6 Oct 1996 01:39:30 +0400 (MSD) Message-Id: <199610052139.BAA06368@nagual.ru> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610051856.EAA30329@godzilla.zeta.org.au> from "Bruce Evans" at "Oct 6, 96 04:56:27 am" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 6 Oct 1996 01:39:29 +0400 (MSD) Cc: bde@zeta.org.au, current@FreeBSD.org, freebsd-hackers@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast 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 > This is much slower than the current rand() or random(). On a P133, > measured over 10^7 calls to statically linked libraries: You forget the fact that srandom() called only _once_ (usually), so speed is unimportant here. TYPE_0 case in random() is very rare thing too, it seems nobody use it. > Perhaps make this a subroutine to avoid duplication and allow easy > changing. Division takes 10-20 times longer than a subroutine call > on Pentiums. We can't relay on Pentium times in machine-independent code. I am thinking about making it #define or inline, which one is better? -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sat Oct 5 15:16:00 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA11724 for current-outgoing; Sat, 5 Oct 1996 15:16:00 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA11608; Sat, 5 Oct 1996 15:13:15 -0700 (PDT) Received: by sovcom.kiae.su id AA26728 (5.65.kiae-1 ); Sun, 6 Oct 1996 01:05:22 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 6 Oct 96 01:05:22 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id CAA07197; Sun, 6 Oct 1996 02:04:17 +0400 (MSD) Message-Id: <199610052204.CAA07197@nagual.ru> Subject: Re: I plan to change random() for -current (was Re: rand() and random()) In-Reply-To: <199610052053.NAA11278@phaeton.artisoft.com> from "Terry Lambert" at "Oct 5, 96 01:53:11 pm" To: terry@lambert.org (Terry Lambert) Date: Sun, 6 Oct 1996 02:04:17 +0400 (MSD) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-hackers@freebsd.org, current@freebsd.org From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast 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 > There is a historical dependence of much physics code on the > repeatability of identical seeding for the linear congruential > generator as a "randomness" base for repeatable Monte Carlo based > testing of relativistically invariant P-P, N-P, and N-N pair production > collisions. The fix _not_ breaks repeatability of identical seeding. > If you *do* change the random algorithms, then you should *leave the > rand48() code along*. I can not stress this enough. You will damage > repeatability of experiments for which source code is unavailable, and > only the results remain. I don't understand your statement well, random() already have different implementations in different OSes. If you mean that previous FreeBSD dynamic-linked binaries can produce different results, yes, it is any upgrade cost. Make static binaries if source code is unavailable. Depending on predictable system function results which claimed to be 'random' is bad idea in general (and mans/docs/standards not declare such possibility too). They only say that "this function [not all possible versions of this function] gives the same sequence for the same seed". Real practice when rand() and random() functions changes between different OSes and inside one OS too confirms it. I remember that Unix v6 rand() was different with what we have currently, so we must return to Unix v6 variant according to your logic. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sat Oct 5 16:05:10 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA15447 for current-outgoing; Sat, 5 Oct 1996 16:05:10 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [193.91.212.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA15437 for ; Sat, 5 Oct 1996 16:05:03 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 9969 invoked by uid 1001); 5 Oct 1996 23:04:46 +0000 (GMT) To: roberto@keltia.freenix.fr Cc: freebsd-current@FreeBSD.ORG Subject: Re: Help! /bin/csh is gone! In-Reply-To: Your message of "Sat, 5 Oct 1996 23:31:24 +0200" References: <199610052131.XAA04869@keltia.freenix.fr> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 06 Oct 1996 01:04:46 +0200 Message-ID: <9967.844556686@verdi.nethelp.no> Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > It wasn't enabled on my Conner 1080S but the brand new IBM DORS 32160 I > just brought has both AWRE and write-back cache enabled. Works like a charm > and is faster than the Conner (5.5 MB/s read and 5.5 MB/s write). > > I am happy. > > (bt0:0:0): "IBM DORS-32160 WA6A" type 0 fixed SCSI 2 > sd0(bt0:0:0): Direct-Access 2063MB (4226725 512 byte sectors) I just bought one of these too, and I like it alot. Will probably buy more of the same. Mine reports WA0A instead of WA6A, but otherwise the same. Btw, I *think* this is the model IBM refers to as Ultrastar. See http://www.pc.ibm.com/options/g2216009.html Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Sat Oct 5 18:23:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA25873 for current-outgoing; Sat, 5 Oct 1996 18:23:15 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA25862 for ; Sat, 5 Oct 1996 18:23:07 -0700 (PDT) Received: from bonsai.hiwaay.net by fly.HiWAAY.net; (8.7.5/1.1.8.2/21Sep95-1003PM) id UAA00296; Sat, 5 Oct 1996 20:22:56 -0500 (CDT) Message-ID: <325709DE.1F567D97@hiwaay.net> Date: Sat, 05 Oct 1996 20:22:38 -0500 From: Steve Price X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: compiling -current with -Dlint Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anybody tried to compile src/lib/csu/i386/crt0.c with -Dlint lately? I just did to get rid of the warning messages about "'sccsid' defined but not used" (I **hate** seeing bogus warning messages) while make'ing world and here is what I saw. cc -Dlint -O2 -m486 -Wall -pipe -fno-strength-reduce -DLIBC_SCCS -fno-omit-frame-pointer -c -DCRT0 -DDYNAMIC /usr/src/lib/csu/i386/crt0.c -o crt0.o /usr/src/lib/csu/i386/crt0.c: In function `start': /usr/src/lib/csu/i386/crt0.c:150: `initcode' undeclared (first use this function) /usr/src/lib/csu/i386/crt0.c:150: (Each undeclared identifier is reported only once /usr/src/lib/csu/i386/crt0.c:150: for each function it appears in.) *** Error code 1 Stop. Here is the offending code (from ctr0.c): #ifdef lint kfp = 0; initcode = initcode = 0; #else /* not lint */ /* just above the saved frame pointer */ asm ("lea 4(%%ebp), %0" : "=r" (kfp) ); #endif /* not lint */ It doesn't appear from 'cvs log' output that the crt0.c file has changed recently. Any startup code gurus know where initcode is/was declared? Or can it safely be removed? TIA, Steve From owner-freebsd-current Sat Oct 5 18:58:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA27431 for current-outgoing; Sat, 5 Oct 1996 18:58:17 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA27426 for ; Sat, 5 Oct 1996 18:58:15 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id SAA29076; Sat, 5 Oct 1996 18:58:09 -0700 (PDT) To: Dan Cross Cc: current@freebsd.org Subject: Re: Qmail changes... (repost) In-reply-to: Your message of "Sat, 05 Oct 1996 12:30:28 EDT." <199610051630.MAA18939@augusta.math.psu.edu> Date: Sat, 05 Oct 1996 18:58:09 -0700 Message-ID: <29074.844567089@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > About a week ago, I posted some diffs for from(1) and mail(1) that make > them honor the $MAIL environment variable. My motivation was supporting > ... > However, these changes were never committed to the source tree, and I > never heard anything back about them. Anyway, it would be really great Sorry, these have been sitting in my inbox awaiting attention. Committed! Jordan From owner-freebsd-current Sat Oct 5 19:14:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA28506 for current-outgoing; Sat, 5 Oct 1996 19:14:55 -0700 (PDT) Received: from cicerone.uunet.ca (root@cicerone.uunet.ca [142.77.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA28468; Sat, 5 Oct 1996 19:14:46 -0700 (PDT) Received: from why.whine.com ([205.150.249.1]) by mail.uunet.ca with ESMTP id <115721-10577>; Sat, 5 Oct 1996 22:14:32 -0400 Received: from why (andrew@why [205.150.249.1]) by why.whine.com (8.7.6/8.6.12) with SMTP id WAA00930; Sat, 5 Oct 1996 22:14:24 -0400 (EDT) Date: Sat, 5 Oct 1996 22:14:24 -0400 From: Andrew Herdman X-Sender: andrew@why To: SysAdmin cc: Mark Mayo , freebsd-questions@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: Java,Netscape, & AccelX In-Reply-To: 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 used to run AccelX but gave up on it. When i switched back to XFree Java started to work again. This is with Netscape 3.0 Andrew On Sat, 5 Oct 1996, SysAdmin wrote: > On Sat, 5 Oct 1996, Mark Mayo wrote: > > > > > Hi all, I still haven't got Java working under Netscape 3.0 yet, and I > > thought maybe somebody has already dealt with this problem. > > > > First of all, I run the August 2.2-SNAP, on a PPRO 150, with a Matrox > > Millenium video card. To get the Matrox working I bought the AcceleratedX > > server from Xinside -- I think this may be the problem. When I hit a java > > applet, the browser leaves space for the applet, but it never actually > > displays. However, when I set my display over to my 486 win95 machine > > (running eXceed 5) the java applets show up just fine... which pretty much > > means my X server is the cause of my problems, no? > > > > When I installed the AccelX server, I only had one problem - it couldn't > > find libc.so.2.2 -> so I linked it to /usr/lib/libc.so.3.0. Everything > > seemed fine.. the X server ran with no problems, and I was amazed at the > > performance of AccelX!! Until it wouldn't show Java, that is :-) > > > > So, after it displayed on the PC, I grabbed the older libc.so.2.2 from the > > 2.1.5 CD and threw it in /usr/lib. I rebooted and the system seemed to > > come up fine. But still no Java -- plus, now when I display to the PC, I > > don't get Java either, and the JDK appletviewer doesn't work.. > > So I quickly put the link from libc.so.2.2 -> lib.so.3.0 back and now I'm > > back to the original problem. > > > > I'm guessing it's some sort of clash between libc.so and the AccelX server > > -- am I correct in assuming this? > > > > Someone please tell me they've solver this problem and that I'm not a > > random incident with no hope... I'm contacting Xinside as well, but I > > believe they only support up to v2.1R. > > > > It's starting to sound more and more like it is an AcceleratedX problem! > > Mike > > ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ > Syn-Work Media, Inc. | WWW Development & Hosting | Life Safety > http://www.synwork.com | Systems Integration | CCTV > mike@synwork.com | Voice/Data/Fiber | Access Control > Flaq on IRC | Dukane Distributor | BICSI/RCDD > :|:|:|: Powered By FreeBSD :|:|:|: > Turning PC's Into Workstations > ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ > From owner-freebsd-current Sat Oct 5 19:54:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA01525 for current-outgoing; Sat, 5 Oct 1996 19:54:44 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA01503 for ; Sat, 5 Oct 1996 19:54:28 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id MAA08128; Sun, 6 Oct 1996 12:51:06 +1000 Date: Sun, 6 Oct 1996 12:51:06 +1000 From: Bruce Evans Message-Id: <199610060251.MAA08128@godzilla.zeta.org.au> To: current@FreeBSD.ORG, sprice@hiwaay.net Subject: Re: compiling -current with -Dlint Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Has anybody tried to compile src/lib/csu/i386/crt0.c with -Dlint >lately? I just did to get rid of the warning messages about Apparently not. >"'sccsid' defined but not used" (I **hate** seeing bogus warning >messages) while make'ing world and here is what I saw. Id strings should be declared as const and possibly as __unused, and possibly in a macro so that the details can be changed. >Here is the offending code (from ctr0.c): > >#ifdef lint > kfp = 0; > initcode = initcode = 0; >#else /* not lint */ > /* just above the saved frame pointer */ > asm ("lea 4(%%ebp), %0" : "=r" (kfp) ); >#endif /* not lint */ > >It doesn't appear from 'cvs log' output that the crt0.c file has >changed recently. Any startup code gurus know where initcode >is/was declared? Or can it safely be removed? Initcode is garbage. Bruce From owner-freebsd-current Sat Oct 5 20:02:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA01994 for current-outgoing; Sat, 5 Oct 1996 20:02:27 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [204.214.4.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA01988 for ; Sat, 5 Oct 1996 20:02:23 -0700 (PDT) Received: from bonsai.hiwaay.net by fly.HiWAAY.net; (8.7.5/1.1.8.2/21Sep95-1003PM) id WAA11028; Sat, 5 Oct 1996 22:01:44 -0500 (CDT) Message-ID: <32572107.2620D7A2@hiwaay.net> Date: Sat, 05 Oct 1996 22:01:27 -0500 From: Steve Price X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Bruce Evans CC: current@freebsd.org Subject: Re: compiling -current with -Dlint References: <199610060251.MAA08128@godzilla.zeta.org.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans wrote: > > Id strings should be declared as const and possibly as __unused, and > possibly in a macro so that the details can be changed. > I have been able to get rid of the offending warning without -Dlint by using a declaration like: static char const sccsid[] = "..."; I have been meaning to make a few of these changes, but have not for fear of retribution. :) > Initcode is garbage. > > Bruce Do you want the honors or shall I remove the offending line from crt0.c? Steve From owner-freebsd-current Sat Oct 5 20:14:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA02642 for current-outgoing; Sat, 5 Oct 1996 20:14:36 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA02633 for ; Sat, 5 Oct 1996 20:14:26 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id NAA08530; Sun, 6 Oct 1996 13:13:14 +1000 Date: Sun, 6 Oct 1996 13:13:14 +1000 From: Bruce Evans Message-Id: <199610060313.NAA08530@godzilla.zeta.org.au> To: bde@zeta.org.au, sprice@hiwaay.net Subject: Re: compiling -current with -Dlint Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Initcode is garbage. >> >> Bruce > >Do you want the honors or shall I remove the offending line from >crt0.c? You do it. I have 600+ files with mostly trivial changes to commit first. This might take a while :-). Bruce From owner-freebsd-current Sat Oct 5 20:19:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA03316 for current-outgoing; Sat, 5 Oct 1996 20:19:45 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA03298 for ; Sat, 5 Oct 1996 20:19:40 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id NAA08695; Sun, 6 Oct 1996 13:17:55 +1000 Date: Sun, 6 Oct 1996 13:17:55 +1000 From: Bruce Evans Message-Id: <199610060317.NAA08695@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, jhay@mikom.csir.co.za Subject: Re: Proposed addition to build-tools target Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >My second problem is that the latest version of release/doFS.sh (1.8) >breaks on a 2.1.5 machine. Something with the labels on a vn device. >The previous version does work. I will have a look into that. The default label was slightly broken in 2.1.5. dosFS.sh now depends on it being directly usable. Bruce From owner-freebsd-current Sat Oct 5 20:30:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA04393 for current-outgoing; Sat, 5 Oct 1996 20:30:02 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA04318; Sat, 5 Oct 1996 20:29:44 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id NAA08899; Sun, 6 Oct 1996 13:27:32 +1000 Date: Sun, 6 Oct 1996 13:27:32 +1000 From: Bruce Evans Message-Id: <199610060327.NAA08899@godzilla.zeta.org.au> To: ache@nagual.ru, bde@zeta.org.au Subject: Re: I plan to change random() for -current (was Re: rand() and random()) Cc: current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >You forget the fact that srandom() called only _once_ (usually), >so speed is unimportant here. I was thinking of getting it right here and copying it to the kernel random() and the user rand(). >> Perhaps make this a subroutine to avoid duplication and allow easy >> changing. Division takes 10-20 times longer than a subroutine call >> on Pentiums. Actually 5-10 times on Pentiums, 3-5 times on 486's, 1-2 times on 386's. >We can't relay on Pentium times in machine-independent code. Speed is unimportant here :-). >I am thinking about making it #define or inline, which one >is better? Inline. Bruce From owner-freebsd-current Sat Oct 5 20:41:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA05591 for current-outgoing; Sat, 5 Oct 1996 20:41:16 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA05582 for ; Sat, 5 Oct 1996 20:41:10 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id DAA05809 for ; Sun, 6 Oct 1996 03:41:00 GMT Date: Sun, 6 Oct 1996 12:41:00 +0900 (JST) From: Michael Hancock To: current@freebsd.org Subject: secure level diffs to kern_mib.c, LINT In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk FreeBSD defaults securelevel to -1, use the following diffs if you prefer normal bsd operations or want a choice. Man init(8) for details. systm.h also has securelevel related comments. The note about securelevel initialization in .bss is controversial, please draw your own conclusions. Regards, Mike Hancock *** /sys/kern/kern_mib.c Sun Sep 29 00:53:30 1996 --- kern_mib.c Sun Oct 6 12:07:58 1996 *************** *** 112,118 **** --- 112,122 ---- SYSCTL_STRING(_kern, KERN_HOSTNAME, hostname, CTLFLAG_RW, hostname, sizeof(hostname), ""); + #ifdef SECURE_MODE + int securelevel; + #else int securelevel = -1; + #endif static int sysctl_kern_securelvl SYSCTL_HANDLER_ARGS Documentation for SECURE_MODE in LINT... *** /sys/i386/conf/LINT Sun Oct 6 02:16:19 1996 --- LINT Sun Oct 6 12:18:10 1996 *************** *** 54,59 **** --- 54,64 ---- options EXTRAVNODES=1 # + # For convenience FreeBSD initializes securelevel to -1. You might + # prefer secure mode when in multi-user mode. man init(8) for details. + options SECURE_MODE + + # # A math emulator is mandatory if you wish to run on hardware which # does not have a floating-point processor. Pick either the original, # bogus (but freely-distributable) math emulator, or a much more From owner-freebsd-current Sat Oct 5 21:06:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA07564 for current-outgoing; Sat, 5 Oct 1996 21:06:33 -0700 (PDT) Received: from covina.lightside.com (covina.lightside.com [207.67.176.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA07544; Sat, 5 Oct 1996 21:06:26 -0700 (PDT) Received: from localhost (jehamby@localhost) by covina.lightside.com (8.8.0/8.7.3) with SMTP id VAA26386; Sat, 5 Oct 1996 21:03:32 -0700 (PDT) Date: Sat, 5 Oct 1996 21:03:31 -0700 (PDT) From: Jake Hamby To: Andrew Herdman cc: SysAdmin , Mark Mayo , freebsd-questions@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: Java,Netscape, & AccelX In-Reply-To: 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, 5 Oct 1996, Andrew Herdman wrote: > I used to run AccelX but gave up on it. When i switched back to XFree > Java started to work again. This is with Netscape 3.0 > > Andrew Hmm, I think I know one possible cause of this problem. I used to have the same problem getting Java to work in Netscape (blank space for applets), this time I installed Netscape from the port (instead of manually) and received the following message: Note: If Java applets fail to display. Type this as root: cd /usr/X11R6/lib/X11/fonts/misc /usr/X11R6/bin/mkfontdir chmod 444 fonts.dir And then exit and restart your X server. I tried that, and lo and behold, it worked! It seems that Netscape needs particular font aliases that for some reason XFree86 didn't define properly. Mkfontdir fixed the problem for XFree86, perhaps it can help Accelerated-X? -- Jake From owner-freebsd-current Sat Oct 5 21:44:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA11020 for current-outgoing; Sat, 5 Oct 1996 21:44:43 -0700 (PDT) Received: from scooter.quickweb.com (scooter.quickweb.com [199.212.134.8]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA11009; Sat, 5 Oct 1996 21:44:29 -0700 (PDT) Received: from localhost (mark@localhost) by scooter.quickweb.com (8.6.12/8.6.12) with SMTP id AAA01136; Sun, 6 Oct 1996 00:44:24 -0400 Date: Sun, 6 Oct 1996 00:44:23 -0400 (EDT) From: Mark Mayo X-Sender: mark@scooter.quickweb.com To: SysAdmin cc: freebsd-questions@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: Java,Netscape, & AccelX In-Reply-To: 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, 5 Oct 1996, SysAdmin wrote: > On Sat, 5 Oct 1996, Mark Mayo wrote: > > > > > Hi all, I still haven't got Java working under Netscape 3.0 yet, and I > > thought maybe somebody has already dealt with this problem. > > > > Someone please tell me they've solver this problem and that I'm not a > > random incident with no hope... I'm contacting Xinside as well, but I > > believe they only support up to v2.1R. > > > > It's starting to sound more and more like it is an AcceleratedX problem! > > Mike Well, I'm sure it is some sort of problem with AcceleratedX - but I'm also quite sure they won't give me any support considering I'm running a 2.2 SNAP.... I was just praying someone else is having similar problems and has come up with a solution. Also, does anyone run AcceleratedX 1.3 on a 2.1.5 system (and can successfully run Java applets in Netscape)?? Does everything work fine with this combo?? -mark ------------------------------------------- | Mark Mayo mark@quickweb..com | | C-Soft www.quickweb.com | ------------------------------------------- "To iterate is human, to recurse divine." - L. Peter Deutsch > > ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ > Syn-Work Media, Inc. | WWW Development & Hosting | Life Safety > http://www.synwork.com | Systems Integration | CCTV > mike@synwork.com | Voice/Data/Fiber | Access Control > Flaq on IRC | Dukane Distributor | BICSI/RCDD > :|:|:|: Powered By FreeBSD :|:|:|: > Turning PC's Into Workstations > ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~ > > From owner-freebsd-current Sat Oct 5 22:01:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA12383 for current-outgoing; Sat, 5 Oct 1996 22:01:38 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA12377 for ; Sat, 5 Oct 1996 22:01:32 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id OAA10795; Sun, 6 Oct 1996 14:56:39 +1000 Date: Sun, 6 Oct 1996 14:56:39 +1000 From: Bruce Evans Message-Id: <199610060456.OAA10795@godzilla.zeta.org.au> To: current@freebsd.org, michaelh@cet.co.jp Subject: Re: secure level diffs to kern_mib.c, LINT Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >FreeBSD defaults securelevel to -1, use the following diffs if you prefer >normal bsd operations or want a choice. Man init(8) for details. Use `sysctl -w kern.securelevel=0' in /etc/rc.local if you want the BSD4.4Lite default. If you want the securelevels > 0 to actually work, then you must do considerably more to fix security holes in certain device drivers. If you want securelevels > 0 to be useful, then you must do considerably more to make all critical system directories and log files immutable or append-only, and be prepared to check and restore all files on the system which aren't immutable if the log files show that there may have been a breakin. >systm.h also has securelevel related comments. The note about securelevel >initialization in .bss is controversial, please draw your own conclusions. No, the part about the bss is just bogus. I removed that part and rewrote the rest of the comment to avoid documenting (previous) policy in systm.h. Bruce diff -c2 systm.h~ systm.h *** systm.h~ Tue Oct 1 04:47:17 1996 --- systm.h Sun Sep 15 07:33:36 1996 *************** *** 61,74 **** * newfs while the system is secured. * ! * In normal operation, the system runs in level 0 mode while single user ! * and in level 1 mode while multiuser. If level 2 mode is desired while ! * running multiuser, it can be set in the multiuser startup script ! * (/etc/rc.local) using sysctl(1). If it is desired to run the system ! * in level 0 mode while multiuser, initialize the variable securelevel ! * in /sys/kern/kern_sysctl.c to -1. Note that it is NOT initialized to ! * zero as that would allow the kernel binary to be patched to -1. ! * Without initialization, securelevel loads in the BSS area which only ! * comes into existence when the kernel is loaded and hence cannot be ! * patched by a stalking hacker. */ extern int securelevel; /* system security level */ --- 61,71 ---- * newfs while the system is secured. * ! * If `securelevel' is initially 0, then process 1 normally arranges to run ! * the system in level 0 mode while single user and in level 1 mode while ! * multiuser. If `securelevel' is initially -1, then process 1 normally ! * leaves it unchanged, so that the system always runs in level 0 mode. In ! * both cases, if a more secure mode is desired, it can be set using ! * sysctl(8) in the multi-user startup script (/etc/rc.local) or earlier. ! * Process 1 will then reduce the level to 0 if single user mode is resumed. */ extern int securelevel; /* system security level */ From owner-freebsd-current Sat Oct 5 23:20:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA18158 for current-outgoing; Sat, 5 Oct 1996 23:20:41 -0700 (PDT) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA18153 for ; Sat, 5 Oct 1996 23:20:39 -0700 (PDT) Received: from helmholtz (helmholtz [198.202.70.34]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id XAA17169; Sat, 5 Oct 1996 23:20:31 -0700 (PDT) Date: Sat, 5 Oct 1996 23:20:31 -0700 (PDT) From: Tom Bartol X-Sender: bartol@helmholtz To: sthaug@nethelp.no cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org Subject: Re: Help! /bin/csh is gone! In-Reply-To: <7249.844526690@verdi.nethelp.no> 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, 5 Oct 1996 sthaug@nethelp.no wrote: > > Try turning on bad sector reallocation. Have a look into the FAQ > > about the required procedure (search for the term ``AWRE''). Bad > > sectors are quite normal on a magnetic storage medium, and the vendor > > should have reserved enough replacement storage. > > > > Btw., my new Seacrate ST32155N turns out to be the first disk i've > > ever seen that has it enabled by default. > > I bought an IBM 2.16 GByte SCSI-disk (Ultrastar ES) a couple of weeks > ago - it also had reallocation turned on by default. I was pleasantly > surprised. > And, as I've just learned, so does my Quantum XP32150. But, alas my Seagate ST51080N did not. Tom From owner-freebsd-current Sat Oct 5 23:30:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA18550 for current-outgoing; Sat, 5 Oct 1996 23:30:01 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA18519 for ; Sat, 5 Oct 1996 23:29:57 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.0/CET-v2.1) with SMTP id GAA06426; Sun, 6 Oct 1996 06:23:44 GMT Date: Sun, 6 Oct 1996 15:23:44 +0900 (JST) From: Michael Hancock To: Bruce Evans cc: current@freebsd.org Subject: Re: secure level diffs to kern_mib.c, LINT In-Reply-To: <199610060456.OAA10795@godzilla.zeta.org.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 What changes would be necessary to *guarantee* that the system increments securelevel to 1, *before* any deamons are started? Putting it in rc.local assumes that the securelevel's definition of multi-user mode will never be made more precise. I'm less concerned with putting securelevel=2 in rc, because this is just locking another deadbolt and isn't as critical as the transition from 0 to 1. On Sun, 6 Oct 1996, Bruce Evans wrote: > >FreeBSD defaults securelevel to -1, use the following diffs if you prefer > >normal bsd operations or want a choice. Man init(8) for details. > > Use `sysctl -w kern.securelevel=0' in /etc/rc.local if you want the > BSD4.4Lite default. If you want the securelevels > 0 to actually work, At least it's an easy start for the /kernel case. > then you must do considerably more to fix security holes in certain > device drivers. If you want securelevels > 0 to be useful, then you > must do considerably more to make all critical system directories and > log files immutable or append-only, and be prepared to check and restore > all files on the system which aren't immutable if the log files show > that there may have been a breakin. > > >systm.h also has securelevel related comments. The note about securelevel > >initialization in .bss is controversial, please draw your own conclusions. > No, the part about the bss is just bogus. I removed that part and rewrote > the rest of the comment to avoid documenting (previous) policy in systm.h. I see it as a small speed bump and I'll take anything in my favor. On the otherhand taking it away outright on grounds that the kernel can be patched elsewhere is questionable. Regards, Mike Hancock > Bruce > > diff -c2 systm.h~ systm.h > *** systm.h~ Tue Oct 1 04:47:17 1996 > --- systm.h Sun Sep 15 07:33:36 1996 > *************** > *** 61,74 **** > * newfs while the system is secured. > * > ! * In normal operation, the system runs in level 0 mode while single user > ! * and in level 1 mode while multiuser. If level 2 mode is desired while > ! * running multiuser, it can be set in the multiuser startup script > ! * (/etc/rc.local) using sysctl(1). If it is desired to run the system > ! * in level 0 mode while multiuser, initialize the variable securelevel > ! * in /sys/kern/kern_sysctl.c to -1. Note that it is NOT initialized to > ! * zero as that would allow the kernel binary to be patched to -1. > ! * Without initialization, securelevel loads in the BSS area which only > ! * comes into existence when the kernel is loaded and hence cannot be > ! * patched by a stalking hacker. > */ > extern int securelevel; /* system security level */ > --- 61,71 ---- > * newfs while the system is secured. > * > ! * If `securelevel' is initially 0, then process 1 normally arranges to run > ! * the system in level 0 mode while single user and in level 1 mode while > ! * multiuser. If `securelevel' is initially -1, then process 1 normally > ! * leaves it unchanged, so that the system always runs in level 0 mode. In > ! * both cases, if a more secure mode is desired, it can be set using > ! * sysctl(8) in the multi-user startup script (/etc/rc.local) or earlier. > ! * Process 1 will then reduce the level to 0 if single user mode is resumed. > */ > extern int securelevel; /* system security level */ >