From owner-freebsd-current Sun May 24 03:51:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29934 for freebsd-current-outgoing; Sun, 24 May 1998 03:51:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from out4.ibm.net (out4.ibm.net [165.87.194.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29905 for ; Sun, 24 May 1998 03:50:20 -0700 (PDT) (envelope-from feigler@ibm.net) Received: from ibm.net (slip129-37-161-22.on.ca.ibm.net [129.37.161.22]) by out4.ibm.net (8.8.5/8.6.9) with ESMTP id KAA188392 for ; Sun, 24 May 1998 10:50:11 GMT Message-ID: <3567FB60.18391347@ibm.net> Date: Sun, 24 May 1998 06:50:08 -0400 From: "Frank J. Eigler" Reply-To: feigler@ibm.net Organization: Frank J. Eigler X-Mailer: Mozilla 4.05 [en] (Win95; U) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Subscription Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current -- Frank J. Eigler mailto:feigler@ibm.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 05:26:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09940 for freebsd-current-outgoing; Sun, 24 May 1998 05:26:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09928 for ; Sun, 24 May 1998 05:26:39 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id IAA08694; Sun, 24 May 1998 08:03:02 -0400 (EDT) From: Peter Dufault Message-Id: <199805241203.IAA08694@hda.hda.com> Subject: Re: Failed to make libc In-Reply-To: <199805240546.JAA06198@minas-tirith.pol.ru> from Alex Povolotsky at "May 24, 98 09:46:01 am" To: tarkhil@asteroid.svib.ru Date: Sun, 24 May 1998 08:03:01 -0400 (EDT) Cc: 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-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > === > cc -O2 -m486 -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include > -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale > -DBROKEN_DES -DYP -c /usr/src/lib/libc/../libc/gen/sysconf.c -o sysconf.o > /usr/src/lib/libc/../libc/gen/sysconf.c:41: sys/_posix.h: No such file or > directory > *** Error code 1 > > Stop. > === > And where is _posix.h?... In /sys/sys. It holds defines needed only by modules picking out pieces of posix functionality so they don't percolate to other header files. Hopefully you didn't make includes first. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 06:04:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13709 for freebsd-current-outgoing; Sun, 24 May 1998 06:04:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13702 for ; Sun, 24 May 1998 06:04:26 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id VAA16711; Sun, 24 May 1998 21:04:04 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805241304.VAA16711@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Thyer cc: Greg Lehey , FreeBSD current users Subject: Re: More about NFS problems under current In-reply-to: Your message of "Sat, 23 May 1998 19:03:00 +0930." <356697CC.E809D7C7@camtech.net.au> Date: Sun, 24 May 1998 21:04:03 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Thyer wrote: > It's happening to me. > > Greg Lehey wrote: > > > > I haven't been able to get my NFS to work reliably yet, but I noticed > > the following message while booting: > > > > struct nfsmount bloated (> 512bytes) > > Try reducing NFS_MUIDHASHSIZ > > > > I don't know to what extent that is related, but I suppose it's worth > > trying. Presumably this is happening to everybody. Question: > > NFS_MUIDHASHSIZ is currently 63. Should I reduce it to 31, or is the > > value not used as a mask? > > > > Greg > > -- > > See complete headers for address and phone numbers > > finger grog@lemis.com for PGP public key This is harmless. If you've got NFS problems, it's not because of this. This is a courtesy warning that certain large structure has gone over a convenient power-of-two size, and that means that we get a large (nearly 0.5KB) block of "lost" space. Since we're malloc'ing a 544 byte struct, malloc assigns a 1024 byte block. Quite harmless, and generally not a problem unless you've got more than a few hundred NFS mounts to other servers. I've changed my copy to use the zone allocator for space efficiency, but on the downside, it can use up a 4K page for a single 544byte nfsmount struct. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 06:51:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19669 for freebsd-current-outgoing; Sun, 24 May 1998 06:51:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19663 for ; Sun, 24 May 1998 06:51:08 -0700 (PDT) (envelope-from forrie@tiac.net) Received: from forrie (forrie.ne.mediaone.net [24.128.72.136]) by chmls05.mediaone.net (8.8.7/8.8.7) with SMTP id JAA01155 for ; Sun, 24 May 1998 09:51:02 -0400 (EDT) Message-Id: <199805241351.JAA01155@chmls05.mediaone.net> X-Sender: forrie@tiac.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sun, 24 May 1998 09:51:41 -0400 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: sub Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 08:53:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03192 for freebsd-current-outgoing; Sun, 24 May 1998 08:53:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (root@asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03186 for ; Sun, 24 May 1998 08:53:43 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id TAA17157; Sun, 24 May 1998 19:53:37 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id TAA23994; Sun, 24 May 1998 19:54:18 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199805241554.TAA23994@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Dufault cc: current@FreeBSD.ORG Subject: Re: Failed to make libc In-reply-to: Your message "Sun, 24 May 1998 08:03:01 EDT." <199805241203.IAA08694@hda.hda.com> Reply-To: tarkhil@asteroid.svib.ru X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 May 1998 19:54:17 +0400 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG <199805241203.IAA08694@hda.hda.com>Peter Dufault writes: >> === >> cc -O2 -m486 -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include >> -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale >> -DBROKEN_DES -DYP -c /usr/src/lib/libc/../libc/gen/sysconf.c -o sysconf.o >> /usr/src/lib/libc/../libc/gen/sysconf.c:41: sys/_posix.h: No such file or >> directory >> *** Error code 1 >In /sys/sys. It holds defines needed only by modules >picking out pieces of posix functionality so they don't percolate >to other header files. Hopefully you didn't make includes first. make include in /usr/src doesn't result in altering /sys/sys/_posix.h, and attempt to copy /sys/sys/_posix.h to /usr/include/sys resulted in LOTS of errors... It doesn't hold many definitions required by sysconf.c. Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 09:10:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06092 for freebsd-current-outgoing; Sun, 24 May 1998 09:10:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from elephants.dyn.ml.org (root@mki4-pl-ri5.kos.net [206.186.40.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06082; Sun, 24 May 1998 09:10:49 -0700 (PDT) (envelope-from jake@elephants.dyn.ml.org) Received: from elephants.dyn.ml.org (jake@elephants.dyn.ml.org [127.0.0.1]) by elephants.dyn.ml.org (8.8.8/8.8.8) with ESMTP id MAA02028; Sun, 24 May 1998 12:13:02 -0700 (PDT) (envelope-from jake@elephants.dyn.ml.org) Message-Id: <199805241913.MAA02028@elephants.dyn.ml.org> X-Mailer: exmh version 1.6.9 8/22/96 To: questions@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: devfs on /dev? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 May 1998 12:13:01 -0700 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is the purpose of devfs to be mounted on /dev? can I safely move /dev to /dev.old and use devfs /dev devfs rw 0 0 in /etc/fstab? Should I put "options DEVFS_ROOT" in my kernel config? I saw that in a search of the mailing lists, but don't think its in LINT. I'm running -current from a few days ago. Thanks -- http://www.checker.org/~jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 09:24:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07812 for freebsd-current-outgoing; Sun, 24 May 1998 09:24:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07803 for ; Sun, 24 May 1998 09:24:17 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id MAA09089; Sun, 24 May 1998 12:00:46 -0400 (EDT) From: Peter Dufault Message-Id: <199805241600.MAA09089@hda.hda.com> Subject: Re: Failed to make libc In-Reply-To: <199805241554.TAA23994@minas-tirith.pol.ru> from Alex Povolotsky at "May 24, 98 07:54:17 pm" To: tarkhil@asteroid.svib.ru Date: Sun, 24 May 1998 12:00:46 -0400 (EDT) Cc: 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-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > make include in /usr/src doesn't result in altering /sys/sys/_posix.h, and > attempt to copy /sys/sys/_posix.h to /usr/include/sys resulted in LOTS of > errors... It doesn't hold many definitions required by sysconf.c. It is copied in in the Makefile in /usr/src/include with everything else. I assume this happens in make includes but won't swear on it. What are the lots of errors? It's been like this since March. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 10:38:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16917 for freebsd-current-outgoing; Sun, 24 May 1998 10:38:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16885; Sun, 24 May 1998 10:38:37 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id RAA10310; Sun, 24 May 1998 17:38:12 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA19617; Sun, 24 May 1998 19:37:59 +0200 (MET DST) Message-ID: <19980524193759.30829@follo.net> Date: Sun, 24 May 1998 19:37:59 +0200 From: Eivind Eklund To: Jake , questions@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: devfs on /dev? References: <199805241913.MAA02028@elephants.dyn.ml.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805241913.MAA02028@elephants.dyn.ml.org>; from Jake on Sun, May 24, 1998 at 12:13:01PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 24, 1998 at 12:13:01PM -0700, Jake wrote: > Is the purpose of devfs to be mounted on /dev? > can I safely move /dev to /dev.old and use > devfs /dev devfs rw 0 0 > in /etc/fstab? > Should I put "options DEVFS_ROOT" in my kernel config? > I saw that in a search of the mailing lists, but don't think its in LINT. > I'm running -current from a few days ago. Just put # DEVFS and SLICE are experimental but work. # SLICE disables too much old code so enabling it in LINT would be bad options DEVFS #devices filesystem options SLICE #devfs based disk handling in your config. This is from LINT (but SLICE is commented out there). Be aware that this break disklabel -e and handling disks from sysinstall. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 11:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19239 for freebsd-current-outgoing; Sun, 24 May 1998 11:06:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xyzzy.machaon.ru ([195.218.138.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19177; Sun, 24 May 1998 11:06:04 -0700 (PDT) (envelope-from dima@xyzzy.machaon.ru) Received: from localhost (localhost [127.0.0.1]) by xyzzy.machaon.ru (8.8.8/8.8.5) with ESMTP id WAA00993; Sun, 24 May 1998 22:05:50 +0400 (MSD) Message-Id: <199805241805.WAA00993@xyzzy.machaon.ru> X-Mailer: exmh version 2.0.1 12/23/97 To: Peter Wemm cc: current@FreeBSD.ORG, dima@bog.msu.su Subject: Re: cvs commit: src/sys/nfs nfs.h nfs_node.c nfs_nqlease.c nfs_subs.c nfs_vfsops.c In-Reply-To: Your message of "Sun, 24 May 1998 07:41:58 PDT." <199805241441.HAA24955@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 May 1998 22:05:50 +0400 From: Dmitry Khrustalev Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm not sure this is a good idea. Memory allocated from zone is never returned to the system. There could be periods of high NFS activity and periods of no NFS activity at all when this allocation of wired kernel memory would be wasted. -Dima > peter 1998/05/24 07:41:58 PDT > > Modified files: > sys/nfs nfs.h nfs_node.c nfs_nqlease.c nfs_subs.c > nfs_vfsops.c > Log: > Convert a couple of large allocations to use zones rather than malloc > for better packing. This means that we can choose better values for the > various hash entries without having to try and get it all to fit within > an artificial power of two limit for malloc's sake. > > Revision Changes Path > 1.36 +6 -4 src/sys/nfs/nfs.h > 1.27 +9 -14 src/sys/nfs/nfs_node.c > 1.35 +4 -2 src/sys/nfs/nfs_nqlease.c > 1.55 +3 -9 src/sys/nfs/nfs_subs.c > 1.63 +8 -6 src/sys/nfs/nfs_vfsops.c > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 12:15:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26378 for freebsd-current-outgoing; Sun, 24 May 1998 12:15:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gorillanet.gorilla.net (gorillanet.gorilla.net [208.128.8.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA26372 for ; Sun, 24 May 1998 12:15:38 -0700 (PDT) (envelope-from tom@gorilla.net) Received: from [208.143.84.102] by gorillanet.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id la114775 for ; Sun, 24 May 1998 14:14:51 -0500 Received: (from tom@localhost) by gorilla.net (8.8.8/8.8.8) id OAA11501; Sun, 24 May 1998 14:15:43 -0500 (CDT) (envelope-from tom) Message-ID: <19980524141513.32054@TOJ.org> Date: Sun, 24 May 1998 14:15:13 -0500 From: Tom Jackson To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: panic: locking against myself (on very straight kernel) Mail-Followup-To: "Jordan K. Hubbard" , current@FreeBSD.ORG References: <19980523151000.43935@TOJ.org> <13937.895971636@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <13937.895971636@time.cdrom.com>; from Jordan K. Hubbard on Sat, May 23, 1998 at 06:00:36PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 23, 1998 at 06:00:36PM -0700, Jordan K. Hubbard wrote: > > Got this also with sysinstall. As far as I can see, /stand/sysinstall is > > unuesable for setting slices and partitions. After I manually set a sd1s1e > > partition, devfs/slice chokes on it. I've learned the hard way *NOT* to run > > fsck on the partition when slice chokes on a partition ;-> > > Any attempt to use sysinstall with the new SLICE or DEVFS code is > almost certainly doomed to fail since it has not been made aware of > those additions, nor are their semantics 100% backwards compatible > with the previous. > > - Jordan I apologize for not being clear. These attempts to use sysinstall were under non-devfs/slice kernels. Sysinstall woulg get to the newfs stage and panic/hang at newfs sd1s1a. This was under smp kernel. Then tried it under a up kernel and got the same thing. This is a updated sysinstall btw. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 13:04:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04021 for freebsd-current-outgoing; Sun, 24 May 1998 13:04:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03919; Sun, 24 May 1998 13:03:55 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id PAA02028; Sun, 24 May 1998 15:03:12 -0500 (EST) (envelope-from toor) Message-Id: <199805242003.PAA02028@dyson.iquest.net> Subject: Re: cvs commit: src/sys/nfs nfs.h nfs_node.c nfs_nqlease.c nfs_subs.c nfs_vfsops.c In-Reply-To: <199805241805.WAA00993@xyzzy.machaon.ru> from Dmitry Khrustalev at "May 24, 98 10:05:50 pm" To: dima@xyzzy.machaon.ru (Dmitry Khrustalev) Date: Sun, 24 May 1998 15:03:12 -0500 (EST) Cc: peter@FreeBSD.ORG, current@FreeBSD.ORG, dima@bog.msu.su From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Khrustalev said: > I'm not sure this is a good idea. Memory allocated from zone is never returned > to the system. There could be periods of high NFS activity and periods of no > NFS activity at all when this allocation of wired kernel memory would be > wasted. > The malloc pool only grows (in the case of sub-page size allocations) also. The difference is that the zone pool is managed per data item type, while the malloc pool is managed per size. There IS a tradeoff, but I have found that the lossage of using zone vs. malloc is small in most cases. One advantage of zone is that the allocation is very very fast, even with stats gathering. Additionally, there is less internal fragmentation. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 13:15:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05653 for freebsd-current-outgoing; Sun, 24 May 1998 13:15:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05647 for ; Sun, 24 May 1998 13:15:49 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id UAA14481; Sun, 24 May 1998 20:15:47 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id WAA28107; Sun, 24 May 1998 22:15:32 +0200 (MET DST) Message-ID: <19980524221531.08545@follo.net> Date: Sun, 24 May 1998 22:15:31 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" , Tom Jackson Cc: current@FreeBSD.ORG Subject: Re: panic: locking against myself (on very straight kernel) References: <19980523151000.43935@TOJ.org> <13937.895971636@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <13937.895971636@time.cdrom.com>; from Jordan K. Hubbard on Sat, May 23, 1998 at 06:00:36PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 23, 1998 at 06:00:36PM -0700, Jordan K. Hubbard wrote: > > Got this also with sysinstall. As far as I can see, /stand/sysinstall is > > unuesable for setting slices and partitions. After I manually set a sd1s1e > > partition, devfs/slice chokes on it. I've learned the hard way *NOT* to run > > fsck on the partition when slice chokes on a partition ;-> > > Any attempt to use sysinstall with the new SLICE or DEVFS code is > almost certainly doomed to fail since it has not been made aware of > those additions, nor are their semantics 100% backwards compatible > with the previous. Sorry I if didn't Cc: you on this previously. libdisk doesn't work with DEVFS/SLICE. It is not just 'almost certain' - it plain doesn't work, and it won't work until we've done either a compatibility hack in SLICE, or have updated libdisk to work with SLICE. I think the a compatibility hack would be the wrong solution - the two models don't map too well on each other. Julian is in favour of making libdisk walk /dev/ and pick out information that way - I'm not certain that is a good idea, either, but I agree that the right part to upgrade is libdisk. The panic() is probably due to a bug in the locking semantics for mount(), and some way sysinstall doing wrong calls. I got a patch from Tor Egge to fix the kernel end of this (so it won't panic()). Eivind, who did his homework this time :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 13:55:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11581 for freebsd-current-outgoing; Sun, 24 May 1998 13:55:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11576; Sun, 24 May 1998 13:55:15 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA08572; Sun, 24 May 1998 13:47:17 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd008570; Sun May 24 20:47:13 1998 Date: Sun, 24 May 1998 13:47:10 -0700 (PDT) From: Julian Elischer To: Jake cc: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: devfs on /dev? In-Reply-To: <199805241913.MAA02028@elephants.dyn.ml.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NO use option SLICE it will mount it for you and use it to mount root from as well. On Sun, 24 May 1998, Jake wrote: > Is the purpose of devfs to be mounted on /dev? > can I safely move /dev to /dev.old and use > devfs /dev devfs rw 0 0 > in /etc/fstab? > Should I put "options DEVFS_ROOT" in my kernel config? > I saw that in a search of the mailing lists, but don't think its in LINT. > I'm running -current from a few days ago. > > Thanks > -- > http://www.checker.org/~jake > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 15:00:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19932 for freebsd-current-outgoing; Sun, 24 May 1998 15:00:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19888 for ; Sun, 24 May 1998 15:00:03 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id VAA04891; Sun, 24 May 1998 21:59:02 GMT Date: Mon, 25 May 1998 06:59:01 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: scrappy@hub.org, freebsd-current@FreeBSD.ORG Subject: Re: May 17th UP machine 'panic' In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 24 May 1998, Michael Hancock wrote: > > The problem is in the vput in quotaoff for the group quota file > > when doing a quotaoff on the user quota file. > > > > Basically, the locking semantics of vget/vput pairings have apparently > > become assymetric? > > vget() is confusing, because the lock flag means don't lock when 0, but > lock if LK_{lock flags} are passed. vput() will always unlock. But I > don't think this is the problem. Tor or Julian might have a patch for this soon. Tor might have identified the problem. vput() doesn't take a process argument and always uses curproc. I suggested splitting up the offending vput() into vrele() and VOP_UNLOCK(). So I guess you are right, vput() is assymetric in that it doesn't take a proc arg, but this would be too much work to fix. I think separating the call to vput() into calls to vrele() and VOP_UNLOCK() only in cases where it's needed would be sufficient. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 15:07:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20844 for freebsd-current-outgoing; Sun, 24 May 1998 15:07:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20831 for ; Sun, 24 May 1998 15:07:30 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA17086 for ; Sun, 24 May 1998 22:07:26 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA25691; Mon, 25 May 1998 00:07:12 +0200 (MET DST) Message-ID: <19980525000710.48512@follo.net> Date: Mon, 25 May 1998 00:07:10 +0200 From: Eivind Eklund To: current@FreeBSD.ORG Subject: buildworld from read-only filesystem References: <199805242151.OAA27063@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805242151.OAA27063@freefall.freebsd.org>; from Eivind Eklund on Sun, May 24, 1998 at 02:51:53PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 24, 1998 at 02:51:53PM -0700, Eivind Eklund wrote: > eivind 1998/05/24 14:51:51 PDT > > Modified files: > gnu/lib/libgmp Makefile > Log: > Don't blow away parts of the sourcetree on a 'make clean'. This was > only harmful for building from a read-only filesystem - the parts > blown away were old rm'ed directories. Now, building from readonly filesystems seems to work. I had only a single problem with my build - I got a few warnings from 'static' declarations in ctype.h, and these hit -Werror a few places in the tree. I don't know how to fix this, except for maybe disabling -Werror. Possibly builds from normal filesystems have this problem at the moment, too - I haven't tested. Eivind, on to testing 'installworld' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 15:23:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23642 for freebsd-current-outgoing; Sun, 24 May 1998 15:23:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23637 for ; Sun, 24 May 1998 15:23:23 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA17516 for ; Sun, 24 May 1998 22:23:23 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA07717; Mon, 25 May 1998 00:23:07 +0200 (MET DST) Message-ID: <19980525002303.28702@follo.net> Date: Mon, 25 May 1998 00:23:03 +0200 From: Eivind Eklund To: current@FreeBSD.ORG Subject: Re: buildworld from read-only filesystem References: <199805242151.OAA27063@freefall.freebsd.org> <19980525000710.48512@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980525000710.48512@follo.net>; from Eivind Eklund on Mon, May 25, 1998 at 12:07:11AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 25, 1998 at 12:07:11AM +0200, Eivind Eklund wrote: > > Eivind, on to testing 'installworld' ... from readonly, of course. This worked without a hitch. I think we can say thanks to Bruce for that :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 15:53:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26866 for freebsd-current-outgoing; Sun, 24 May 1998 15:53:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26861 for ; Sun, 24 May 1998 15:53:40 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id RAA00577; Sun, 24 May 1998 17:33:52 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199805241633.RAA00577@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Brian Somers cc: Julian Elischer , freebsd-current@FreeBSD.ORG, Archie Cobbs Subject: Re: **HEADS UP** user-ppp has changed ! In-reply-to: Your message of "Sat, 23 May 1998 13:34:57 BST." <199805231234.NAA07729@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 May 1998 17:33:52 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > did you test it against mpd? [.....] > Anyway, the upshot of it all is that YES, PPP TALKS TO MPD OK (first [.....] I've tested with two links now and things seem ok. I have to implement a ``use /bin/cat for tty devices'' patch before server mode will work ok though. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 17:23:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12601 for freebsd-current-outgoing; Sun, 24 May 1998 17:23:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12596 for ; Sun, 24 May 1998 17:23:50 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id KAA18501; Mon, 25 May 1998 10:30:00 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805250030.KAA18501@cimlogic.com.au> Subject: Re: buildworld from read-only filesystem In-Reply-To: <19980525000710.48512@follo.net> from Eivind Eklund at "May 25, 98 00:07:10 am" To: eivind@yes.no (Eivind Eklund) Date: Mon, 25 May 1998 10:30:00 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > I don't know how to fix this, except for maybe disabling -Werror. > Possibly builds from normal filesystems have this problem at the > moment, too - I haven't tested. Fix the "big bug" in gcc? 8-) The semantics differ depending on the use of -nostdinc. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 20:57:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08840 for freebsd-current-outgoing; Sun, 24 May 1998 20:57:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08831 for ; Sun, 24 May 1998 20:57:01 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA08934; Sun, 24 May 1998 20:56:54 -0700 (PDT) (envelope-from jdp) Message-Id: <199805250356.UAA08934@austin.polstra.com> To: Terry Lambert cc: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Sat, 23 May 1998 21:07:51 -0000." <199805232107.OAA13753@usr07.primenet.com> Date: Sun, 24 May 1998 20:56:54 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > No. I'm saying if I have shared libraries A, B, C, with link > order > > A > B > C > > And I'm resolving a weak symbol that exists in all three, then > I should get the definition from C, not from A or B. > > So the inversion of priority only applies to weak symbols. It seems like that behavior would be awfully surprising to most users. I don't think any other linkers treat weak symbols like this, do they? > In practice, ld.so does the right thing right now. The problem is > when I have a statically linked weak symbol in the same compilation > unit, and I want to link shared against something with a strong > version of the symbol, the shared objects symbol does not override. > > This is a bug in ld. Yes, it's been there for years. :-( > Another interesting bug in ld is that the code that would tell me > that a dependent symbol was not resolved in my cshared library, and > save my bacon at runtime, is "#if 0"'ed out for no reason that I can > discern. > > This relates to a previous bug I reported against ld, where I have > an object O that takes symbol q from shared library A, and symbol q > requires symbol r as a dependency, the lack of the symbol r in A or > any other shared library fails to evoke an undefined symbol error. Yes, another old bug. :-( > Basically, ld is a mess. 8-(. Exactly. Several people including myself have gone into ld with the idea of fixing the above bugs. We all still have nightmares about the experience. The bugs aren't just bugs, they're major design problems. That's why everybody who really scrutinizes ld decides it would be a lot easier to throw it out and switch to ELF. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 21:01:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09707 for freebsd-current-outgoing; Sun, 24 May 1998 21:01:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09701 for ; Sun, 24 May 1998 21:01:15 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id DAA19774; Mon, 25 May 1998 03:39:42 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199805250239.DAA19774@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Brian Somers cc: Julian Elischer , freebsd-current@FreeBSD.ORG, Archie Cobbs Subject: Re: **HEADS UP** user-ppp has changed ! In-reply-to: Your message of "Sun, 24 May 1998 17:33:52 BST." <199805241633.RAA00577@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 May 1998 03:39:42 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > did you test it against mpd? > [.....] > > Anyway, the upshot of it all is that YES, PPP TALKS TO MPD OK (first > [.....] > > I've tested with two links now and things seem ok. I have to > implement a ``use /bin/cat for tty devices'' patch before server mode > will work ok though. Well, I've done the `/bin/cat' bit now. Ppp itself can bring up 8 simultaneous links to itself at the same time, four serial and four network. Trying to bring up mpd with the 4 serial links seems to cause a problem though :-( I've seen something about carrier loss (which I thought was disabled), but I'm too tired now.... -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 21:50:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15656 for freebsd-current-outgoing; Sun, 24 May 1998 21:50:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15647 for ; Sun, 24 May 1998 21:50:53 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id OAA29833; Mon, 25 May 1998 14:41:59 +1000 Date: Mon, 25 May 1998 14:41:59 +1000 From: Bruce Evans Message-Id: <199805250441.OAA29833@godzilla.zeta.org.au> To: current@FreeBSD.ORG, eivind@yes.no Subject: Re: buildworld from read-only filesystem Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Now, building from readonly filesystems seems to work. I had only a >single problem with my build - I got a few warnings from 'static' >declarations in ctype.h, and these hit -Werror a few places in the >tree. > >I don't know how to fix this, except for maybe disabling -Werror. >Possibly builds from normal filesystems have this problem at the >moment, too - I haven't tested. The warning occurs for unused static inline functions if the sources are compiled without optimization, except for functions in standard headers ("standard" = under /usr/include or something like that), except under alpha it apparently occurs even with optimization. Why aren't you using the standard CFLAGS which have -O in them? :-) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 22:10:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18050 for freebsd-current-outgoing; Sun, 24 May 1998 22:10:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18004 for ; Sun, 24 May 1998 22:09:58 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id PAA19101; Mon, 25 May 1998 15:16:09 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805250516.PAA19101@cimlogic.com.au> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805250356.UAA08934@austin.polstra.com> from John Polstra at "May 24, 98 08:56:54 pm" To: jdp@polstra.com (John Polstra) Date: Mon, 25 May 1998 15:16:08 +1000 (EST) Cc: tlambert@primenet.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > Exactly. Several people including myself have gone into ld with the > idea of fixing the above bugs. We all still have nightmares about the > experience. The bugs aren't just bugs, they're major design problems. > That's why everybody who really scrutinizes ld decides it would be a > lot easier to throw it out and switch to ELF. Oh, so _that_ is the reason for switching to ELF. Chuckle. It solves the old ld problems. Just a matter of perspective, I guess. 8-) -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 22:12:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18466 for freebsd-current-outgoing; Sun, 24 May 1998 22:12:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18405; Sun, 24 May 1998 22:12:16 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id NAA19722; Mon, 25 May 1998 13:11:42 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805250511.NAA19722@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: dyson@FreeBSD.ORG cc: dima@xyzzy.machaon.ru (Dmitry Khrustalev), peter@FreeBSD.ORG, current@FreeBSD.ORG, dima@bog.msu.su Subject: Re: cvs commit: src/sys/nfs nfs.h nfs_node.c nfs_nqlease.c nfs_subs.c nfs_vfsops.c In-reply-to: Your message of "Sun, 24 May 1998 15:03:12 EST." <199805242003.PAA02028@dyson.iquest.net> Date: Mon, 25 May 1998 13:11:41 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "John S. Dyson" wrote: > Dmitry Khrustalev said: > > I'm not sure this is a good idea. Memory allocated from zone is never retur ned > > to the system. There could be periods of high NFS activity and periods of n o > > NFS activity at all when this allocation of wired kernel memory would be > > wasted. > > > The malloc pool only grows (in the case of sub-page size allocations) also. > The difference is that the zone pool is managed per data item type, while > the malloc pool is managed per size. There IS a tradeoff, but I have found > that the lossage of using zone vs. malloc is small in most cases. > > One advantage of zone is that the allocation is very very fast, even > with stats gathering. Additionally, there is less internal fragmentation. Perhaps we should do some sort of periodic reclaim of unused zone pages? I was planning on moving some of the other nfs structs to zones as well, especially those that are allocated and freed by the tens or hundreds of thousands of times per "busy" session (eg: doing a cvs update over nfs). The 'never freed' bit worrys me a little since these can be busty and temporarily larger than usual. The speed of zone based allocation will be nice here, since one one machine that's been running with some nfs activity over a day or two has clocked up 300K requests for a 64 byte object, and yet the high water mark is only 1KB. I'd be happy to trade an entire page to supercharge that. :-) Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 22:41:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22005 for freebsd-current-outgoing; Sun, 24 May 1998 22:41:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21985; Sun, 24 May 1998 22:40:39 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id AAA02151; Mon, 25 May 1998 00:40:21 -0500 (EST) (envelope-from toor) Message-Id: <199805250540.AAA02151@dyson.iquest.net> Subject: Re: cvs commit: src/sys/nfs nfs.h nfs_node.c nfs_nqlease.c nfs_subs.c nfs_vfsops.c In-Reply-To: <199805250511.NAA19722@spinner.netplex.com.au> from Peter Wemm at "May 25, 98 01:11:41 pm" To: peter@netplex.com.au (Peter Wemm) Date: Mon, 25 May 1998 00:40:18 -0500 (EST) Cc: dyson@FreeBSD.ORG, dima@xyzzy.machaon.ru, peter@FreeBSD.ORG, current@FreeBSD.ORG, dima@bog.msu.su From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm said: > > Perhaps we should do some sort of periodic reclaim of unused zone pages? I > was planning on moving some of the other nfs structs to zones as well, > especially those that are allocated and freed by the tens or hundreds of > thousands of times per "busy" session (eg: doing a cvs update over nfs). > The 'never freed' bit worrys me a little since these can be busty and ^^^^^^^^^^^^^ > temporarily larger than usual. The speed of zone based allocation will be > nice here, since one one machine that's been running with some nfs activity > over a day or two has clocked up 300K requests for a 64 byte object, and > yet the high water mark is only 1KB. I'd be happy to trade an entire page > to supercharge that. :-) > Malloc doesn't free things effectively either. Making zone "free" pages on the fly would require a significant increase in the amount of logic. To make it do a "garbage collection-style" operation would be easier, and I am not adverse to it. As it is today, it won't be much worse (if any) than malloc is. (Once a piece of memory is committed to a certain size, it is going to be that size forever in malloc. The zone allocator commits a piece of memory to a "type" instead of a size. In both cases, the memory will remain wired for the lifetime of the system.) At one time, a long time ago, I taught malloc to free memory back to the system, and it didn't help much. Maybe sometime in the future, we can add a zone attribute to try to free memory when it seems to be a good thing to do (as you suggest) (perhaps when the pageout daemon decides to.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 22:46:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22949 for freebsd-current-outgoing; Sun, 24 May 1998 22:46:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (root@asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22935; Sun, 24 May 1998 22:46:11 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id JAA25269; Mon, 25 May 1998 09:45:57 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id JAA21636; Mon, 25 May 1998 09:46:27 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199805250546.JAA21636@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: hackers@FreeBSD.ORG Reply-To: tarkhil@asteroid.svib.ru Subject: Sendmail 8.9 X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 May 1998 09:46:27 +0400 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Has anyone checked this new version? It is claimed to be more spam-proof. Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 23:19:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29115 for freebsd-current-outgoing; Sun, 24 May 1998 23:19:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (firewall-user@ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29096 for ; Sun, 24 May 1998 23:19:35 -0700 (PDT) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id QAA18046; Mon, 25 May 1998 16:19:26 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma017997; Mon, 25 May 98 16:19:09 +1000 Received: from troll.dtir.qld.gov.au (troll-8.dtir.qld.gov.au [167.123.8.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id QAA05798; Mon, 25 May 1998 16:19:08 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id QAA14093; Mon, 25 May 1998 16:19:04 +1000 (EST) Message-Id: <199805250619.QAA14093@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: Terry Lambert cc: freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <199805231951.MAA10260@usr07.primenet.com> In-Reply-To: <199805231951.MAA10260@usr07.primenet.com> from Terry Lambert at "Sat, 23 May 1998 19:51:36 +0000" Date: Mon, 25 May 1998 16:19:04 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 23rd May 1998, Terry Lambert wrote: >The weak symbol is apparently being screwed over by our linker *before* >the libraries are examined for identical non-weak symbols. >This is *WRONG*. The ld program is *BROKEN*. At this point then, someone else will have to pursue changes to ld proper, as I have insufficient knowledge of ld and insufficient time to repair it. >In the shared library case, the loading of shared objects and the >resoloution of weak symbols is, in fact, correct. > >Practically, this means that the weak __error definition to ___error >*WILL* work, but *ONLY* if it occurs in shared objects, and *NOT* >in the main program. Sorry, not true. I've already done the experiment that shows that it fails in shared objects too. Allow me to cut and paste: >> Output of ldd: >> >> foo: >> -l__error.0 => /syshome/syssgm/lib/lib__error.so.0.0 (0x20014000) >> -lc_r.3 => /usr/lib/libc_r.so.3.0 (0x20019000) >> -lc.3 => /usr/lib/libc.so.3.1 (0x2009b000) >> ----------------------------------------------------------------------------- >> Output of foo: >> ----------------------------------------------------------------------------- >> errno is 0 >> count is 1 >> errno is 21 >> count is 3 >> ----------------------------------------------------------------------------- > >The problem here is that foo is getting the __error = ___error from >foo.o, not from teh shared library. I was not clear enough when packaging my previous message. This version of foo did not have your errno.h patch, and thus did not put your ___error in foo.o. The example shows that although libc_r and libc have __error, it is instead linked from lib__error, simply because it is first, without regard to weak or non-weak symbols. >I would expect the strong __error in /usr/lib/libc_r.so.3.0 to override >the weak __error = ___error in /syshome/syssgm/lib/lib__error.so.0.0 Unfortunately, this is not the case. >[ ... hack to ld.so ... ] > >I'm anxious about this hack because what you are doing is covering a >bug in ld that is interfering with your test case. I think this can >be adequately dispensed with by doing the right thing in errno.h >and bsd.lib.mk. It may be covering a defect in ld, but it's the best I can do right now. I intend to polish my ld.so hack as time permits. Eventually we have to do something. >> So, for the folks that really care about this, we now have 3 possible >> options: >> >> 1) back out the errno change, and possibly put it back after ELF. >> >> 2) hack ld.so (prototype works fine) >> >> 3) bump ALL library major numbers >> >> Which will it be? > >There are two more: > > 4) hack errno.h to define the weak symbol mechanism I proposed, and > fix ld so that errno.h doesn't have to know that a shared library > compilation unit is including it. > > 5) hack errno.h to define the weak symbol mechanism I proposed, and > hack bsd.lib.mk that errno.h knows that a shared library > compilation unit is including it. Is it likely that ld will be fixed? I doubt that I will find time to fix it, especially as Nate claims it is much harder than it looks. >About 8 hours of work on ld could fix it. Please finish it then. Forget about USENET for a time! Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 23:35:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02763 for freebsd-current-outgoing; Sun, 24 May 1998 23:35:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02755 for ; Sun, 24 May 1998 23:35:03 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id IAA15904; Mon, 25 May 1998 08:30:17 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id IAA02213; Mon, 25 May 1998 08:20:36 +0200 (CEST) (envelope-from andreas) Message-ID: <19980525082036.A2194@klemm.gtn.com> Date: Mon, 25 May 1998 08:20:36 +0200 From: Andreas Klemm To: Julian Elischer , Zach Heilig Cc: current@FreeBSD.ORG Subject: Re: Softupdates panic (got it!) References: <19980523024530.44245@gaffaneys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Julian Elischer on Sat, May 23, 1998 at 02:30:09AM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 23, 1998 at 02:30:09AM -0700, Julian Elischer wrote: > thanks > we're collecting these for a blitz next week. Here on my SMP system it runs flawlessly since days. Just wanted to let you know. FreeBSD titan.klemm.gtn.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Wed May 20 20:54:51 CEST 1998 root@titan.klemm.gtn.com:/home/data/sys.bisdn/compile/BISDNSMP i386 /dev/sd0s2a on / (local, soft-updates, writes: sync 5 async 7795) /dev/sd0s2e on /var (local, soft-updates, writes: sync 62 async 9205) /dev/sd0s2f on /usr (local, soft-updates, writes: sync 8 async 19005) /dev/ccd0c on /obj (local, noatime, soft-updates, writes: sync 2 async 0) /dev/ccd1c on /news (local, noatime, soft-updates, writes: sync 6 async 3449) /dev/ccd2c on /proxy (local, noatime, soft-updates, writes: sync 2 async 2914) /dev/ccd3c on /home (local, soft-updates, writes: sync 351 async 241344) mfs:33 on /tmp (asynchronous, local, writes: sync 99 async 1575) -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 23:39:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03534 for freebsd-current-outgoing; Sun, 24 May 1998 23:39:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hermes.iaccess.com.au (hermes.iaccess.com.au [203.5.74.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03510 for ; Sun, 24 May 1998 23:38:52 -0700 (PDT) (envelope-from andrew@iaccess.com.au) Received: from alpine.iaccess (alpine.iaccess.com.au [203.5.74.227]) by hermes.iaccess.com.au (8.8.5/8.8.5) with SMTP id QAA07848 for ; Mon, 25 May 1998 16:40:18 +1000 (EST) Message-ID: <03e601bd87a8$4f61b1e0$e34a05cb@alpine.iaccess> From: "Andrew Specht" To: Subject: tx driver at 100Mbps!!! Date: Mon, 25 May 1998 16:42:34 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I posted this about a month ago and I am still having the same problem. My SMC9432 ethernet card gives me these errors at boot up and when i type ifconfig tx0 up. May 25 11:41:37 /kernel: tx0: device timeout 1 packets May 25 11:41:37 /kernel: tx0: can't stop TX DMA This will go as high as 16 packets and then the ethernet card would fail. It runs fine on 10Mbps though. Thanks again Andrew Specht | System Administrator E-mail: andrew@iaccess.com.au | Internet Access Australia Internet: http://www.iaccess.com.au | Melbourne, Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun May 24 23:43:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04580 for freebsd-current-outgoing; Sun, 24 May 1998 23:43:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles213.castles.com [208.214.165.213]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04570 for ; Sun, 24 May 1998 23:43:33 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA10671; Sun, 24 May 1998 22:39:20 -0700 (PDT) Message-Id: <199805250539.WAA10671@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Amancio Hasty cc: Philippe Regnauld , Luigi Rizzo , current@FreeBSD.ORG Subject: Re: ATAPI CDDA Extraction under FreeBSD In-reply-to: Your message of "Mon, 18 May 1998 09:36:03 PDT." <199805181636.JAA04038@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 May 1998 22:39:20 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How many outstanding dma requests can the IDE bus handle? The issue isn't the bus but the controller(s) and drive(s). I'm not aware of any drives on the market that support more than a single outstanding transaction (although the standard allows for drives to support tagged transactions). > For instance do you expect to be able to read audio CDs while > doing heavy i/o on the IDE disks? This depends on the relative priorities attached to I/O to the disk/ CDROM. If the two are serviced fairly, and the net throughput is less than the capacity of the bus, then all should be fine. Otherwise, it would probably be necessary to modify things so that the CDROM is preferentially serviced or the CDROM will overrun. ie. no different from the SCSI case. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 02:03:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA04190 for freebsd-current-outgoing; Mon, 25 May 1998 02:03:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA04167 for ; Mon, 25 May 1998 02:03:39 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id KAA07880; Mon, 25 May 1998 10:03:26 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <356933DE.351525C9@tdx.co.uk> Date: Mon, 25 May 1998 10:03:26 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: tarkhil@asteroid.svib.ru CC: current@FreeBSD.ORG Subject: Re: Sendmail 8.9 References: <199805250546.JAA21636@minas-tirith.pol.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Povolotsky wrote: > Hello! > > Has anyone checked this new version? It is claimed to be more spam-proof. > > Alex. Yes, I'm running it on 2 production boxes here - it seems pretty good - I like the 'default to no relay' options (caused a few headaches during install ;-) - And other features like the 'access database' - so you can accept, relay, dump to null or reject mail based on where it's coming from :-) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 02:19:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06485 for freebsd-current-outgoing; Mon, 25 May 1998 02:19:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06477 for ; Mon, 25 May 1998 02:19:30 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id JAA03946; Mon, 25 May 1998 09:19:01 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA01709; Mon, 25 May 1998 11:18:50 +0200 (MET DST) Message-ID: <19980525111850.27126@follo.net> Date: Mon, 25 May 1998 11:18:50 +0200 From: Eivind Eklund To: Bruce Evans , current@FreeBSD.ORG Subject: Re: buildworld from read-only filesystem References: <199805250441.OAA29833@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805250441.OAA29833@godzilla.zeta.org.au>; from Bruce Evans on Mon, May 25, 1998 at 02:41:59PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 25, 1998 at 02:41:59PM +1000, Bruce Evans wrote: > The warning occurs for unused static inline functions if the sources > are compiled without optimization, except for functions in standard > headers ("standard" = under /usr/include or something like that), > except under alpha it apparently occurs even with optimization. Why > aren't you using the standard CFLAGS which have -O in them? :-) Because I was expecting to do _many_ testbuilds before getting things to work from a readonly FS, and had hoped to save some time. Thanks for the info :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 03:25:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17823 for freebsd-current-outgoing; Mon, 25 May 1998 03:25:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17810 for ; Mon, 25 May 1998 03:25:19 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id KAA06906; Mon, 25 May 1998 10:25:17 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA02074; Mon, 25 May 1998 12:25:07 +0200 (MET DST) Message-ID: <19980525122507.46281@follo.net> Date: Mon, 25 May 1998 12:25:07 +0200 From: Eivind Eklund To: Michael Hancock , Terry Lambert Cc: freebsd-current@FreeBSD.ORG Subject: Re: May 17th UP machine 'panic' References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Michael Hancock on Mon, May 25, 1998 at 06:59:01AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 25, 1998 at 06:59:01AM +0900, Michael Hancock wrote: > Tor might have identified the problem. vput() doesn't take a process > argument and always uses curproc. I suggested splitting up the offending > vput() into vrele() and VOP_UNLOCK(). > > So I guess you are right, vput() is assymetric in that it doesn't take a > proc arg, but this would be too much work to fix. How? If it is usually only interested in curproc, doing a search/replace shouldn't be too hard. It is used "only" about 300 places ;-) (There are about five calls to vput that is used on another call, to create trouble for a straight regexp replace. Not so much it would make it hard to handle.) I don't know which effect such a change would have on performance - that's for you expert to answer :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 03:37:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19991 for freebsd-current-outgoing; Mon, 25 May 1998 03:37:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from current.gaffaneys.com (dialup2.gaffaneys.com [208.155.161.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA19983 for ; Mon, 25 May 1998 03:37:33 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by current.gaffaneys.com (8.8.8/8.8.8) id FAA02810; Mon, 25 May 1998 05:39:44 -0500 (CDT) (envelope-from zach) Message-ID: <19980525053943.56833@gaffaneys.com> Date: Mon, 25 May 1998 05:39:43 -0500 From: Zach Heilig To: Andreas Klemm , Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: Softupdates panic (got it!) References: <19980523024530.44245@gaffaneys.com> <19980525082036.A2194@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980525082036.A2194@klemm.gtn.com>; from Andreas Klemm on Mon, May 25, 1998 at 08:20:36AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 25, 1998 at 08:20:36AM +0200, Andreas Klemm wrote: > On Sat, May 23, 1998 at 02:30:09AM -0700, Julian Elischer wrote: > > thanks > > we're collecting these for a blitz next week. > Here on my SMP system it runs flawlessly since days. > Just wanted to let you know. Ah, but how full are your disks, I have my system partitioned like: Filesystem 1K-blocks Used Avail Capacity Mounted on ... /dev/wd1s4a 89287 73519 8626 89% /usr ... When there is softupdates on '/usr', 'make installworld' causes a kernel panic regularly. After watching it in action for awhile, and seeing that space is not reclaimed for several seconds; I can guess that the deletion delay causes /usr to fill up, and that causes the problem I see. -- Zach Heilig -- zach@gaffaneys.com Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 03:55:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22792 for freebsd-current-outgoing; Mon, 25 May 1998 03:55:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22787 for ; Mon, 25 May 1998 03:55:25 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id DAA21424; Mon, 25 May 1998 03:47:25 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd021422; Mon May 25 10:47:22 1998 Date: Mon, 25 May 1998 03:47:20 -0700 (PDT) From: Julian Elischer To: Zach Heilig cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: Softupdates panic (got it!) In-Reply-To: <19980525053943.56833@gaffaneys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That shouldn't cause the problem.. there is code to specially handle that case. On Mon, 25 May 1998, Zach Heilig wrote: > On Mon, May 25, 1998 at 08:20:36AM +0200, Andreas Klemm wrote: > > On Sat, May 23, 1998 at 02:30:09AM -0700, Julian Elischer wrote: > > > thanks > > > we're collecting these for a blitz next week. > > > Here on my SMP system it runs flawlessly since days. > > Just wanted to let you know. > > Ah, but how full are your disks, I have my system partitioned like: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > ... > /dev/wd1s4a 89287 73519 8626 89% /usr > ... > > When there is softupdates on '/usr', 'make installworld' causes a kernel panic > regularly. After watching it in action for awhile, and seeing that space is > not reclaimed for several seconds; I can guess that the deletion delay causes > /usr to fill up, and that causes the problem I see. > > -- > Zach Heilig -- zach@gaffaneys.com > Real Programs don't use shared text. Otherwise, how can they use > functions for scratch space after they are finished calling them? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 04:56:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03454 for freebsd-current-outgoing; Mon, 25 May 1998 04:56:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03445 for ; Mon, 25 May 1998 04:56:57 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id LAA10471; Mon, 25 May 1998 11:55:44 GMT Date: Mon, 25 May 1998 20:55:44 +0900 (JST) From: Michael Hancock To: Eivind Eklund cc: Terry Lambert , freebsd-current@FreeBSD.ORG Subject: Re: May 17th UP machine 'panic' In-Reply-To: <19980525122507.46281@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The argument should be p or curproc depending on whether or not an appropriate proc p is defined. I suppose you could just search and replace adding curproc, but that's ugly. We might have to bite the bullet and do it sometime later. BTW, I noticed that vrele() also uses curproc in the usecount == 1 case so if it is possible for usecount to be 1 then the following would be be necessary: VREF(vp); vrele(vp); VOP_UNLOCK(vp, 0, p); vrele(vp); /* This one possibly does vn_lock() and VOP_INACTIVE() */ Regards, Mike On Mon, 25 May 1998, Eivind Eklund wrote: > On Mon, May 25, 1998 at 06:59:01AM +0900, Michael Hancock wrote: > > Tor might have identified the problem. vput() doesn't take a process > > argument and always uses curproc. I suggested splitting up the offending > > vput() into vrele() and VOP_UNLOCK(). > > > > So I guess you are right, vput() is assymetric in that it doesn't take a > > proc arg, but this would be too much work to fix. > > How? If it is usually only interested in curproc, doing a search/replace > shouldn't be too hard. It is used "only" about 300 places ;-) > (There are about five calls to vput that is used on another call, to create > trouble for a straight regexp replace. Not so much it would make it hard to > handle.) > > I don't know which effect such a change would have on performance - that's > for you expert to answer :-) > > Eivind. > -- michaelh@cet.co.jp http://www.cet.co.jp CET Inc., Daiichi Kasuya BLDG 8F, 2-5-12 Higashi Shinbashi, Minato-ku, Tokyo 105 Japan Tel: +81-3-3437-1761 Fax: +81-3-3437-1766 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 05:04:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05087 for freebsd-current-outgoing; Mon, 25 May 1998 05:04:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05079 for ; Mon, 25 May 1998 05:04:53 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id MAA11684; Mon, 25 May 1998 12:04:45 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA02410; Mon, 25 May 1998 14:04:35 +0200 (MET DST) Message-ID: <19980525140435.34553@follo.net> Date: Mon, 25 May 1998 14:04:35 +0200 From: Eivind Eklund To: Michael Hancock Cc: Terry Lambert , freebsd-current@FreeBSD.ORG Subject: Re: May 17th UP machine 'panic' References: <19980525122507.46281@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Michael Hancock on Mon, May 25, 1998 at 08:55:44PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 25, 1998 at 08:55:44PM +0900, Michael Hancock wrote: > The argument should be p or curproc depending on whether or not an > appropriate proc p is defined. I suppose you could just search and replace > adding curproc, but that's ugly. We might have to bite the bullet and do > it sometime later. If the problem is only the amount of work with doing the actual, physical replacements, I can do that. I estimate it to less than 6 hours of work (that's approx 1 minute 12 seconds per entry :-) If the problem is deciding if this is the way to go, that's something I can't help much with - I don't know the interactions in this area well enough. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 06:26:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17268 for freebsd-current-outgoing; Mon, 25 May 1998 06:26:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (firewall-user@ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17262 for ; Mon, 25 May 1998 06:26:36 -0700 (PDT) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id XAA06690; Mon, 25 May 1998 23:26:29 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma006680; Mon, 25 May 98 23:26:20 +1000 Received: from troll.dtir.qld.gov.au (troll-8.dtir.qld.gov.au [167.123.8.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with ESMTP id XAA09469; Mon, 25 May 1998 23:26:20 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id XAA17411; Mon, 25 May 1998 23:26:16 +1000 (EST) Message-Id: <199805251326.XAA17411@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: Eivind Eklund cc: freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: buildworld from read-only filesystem References: <19980525111850.27126@follo.net> In-Reply-To: <19980525111850.27126@follo.net> from Eivind Eklund at "Mon, 25 May 1998 11:18:50 +0200" Date: Mon, 25 May 1998 23:26:16 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 25th May 1998, Eivind Eklund wrote: >Because I was expecting to do _many_ testbuilds before getting things to >work from a readonly FS, and had hoped to save some time. I'm puzzled. I have been building with a readonly source tree for quite a while now. I recall having some trouble last September, so I've been doing this at least since then. Last time I checked, it also worked with -stable. Are you doing something trickier? Stephen. PS I also build using NFS, using MAKEOBJDIRPREFIX, and sometimes still use a 386, though my really slow 386 died suddenly last year. :-) My 486SX takes 22 hours to complete a buildworld. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 06:33:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18336 for freebsd-current-outgoing; Mon, 25 May 1998 06:33:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18325 for ; Mon, 25 May 1998 06:33:03 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id NAA16981; Mon, 25 May 1998 13:33:00 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA02957; Mon, 25 May 1998 15:32:50 +0200 (MET DST) Message-ID: <19980525153245.29293@follo.net> Date: Mon, 25 May 1998 15:32:45 +0200 From: Eivind Eklund To: Stephen McKay Cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld from read-only filesystem References: <19980525111850.27126@follo.net> <199805251326.XAA17411@troll.dtir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805251326.XAA17411@troll.dtir.qld.gov.au>; from Stephen McKay on Mon, May 25, 1998 at 11:26:16PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 25, 1998 at 11:26:16PM +1000, Stephen McKay wrote: > On Monday, 25th May 1998, Eivind Eklund wrote: > > >Because I was expecting to do _many_ testbuilds before getting things to > >work from a readonly FS, and had hoped to save some time. > > I'm puzzled. I have been building with a readonly source tree for quite > a while now. I recall having some trouble last September, so I've been > doing this at least since then. Last time I checked, it also worked with > -stable. Are you doing something trickier? I've just had many people complain that 'buildworld' from a RO FS didn't work, with the last being Terry Lambert a few weeks ago. Thus, I didn't believe it was close to working. The only 'tricky' part I did was checking out without '-P', triggering some bugs in libgmp. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 09:03:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11451 for freebsd-current-outgoing; Mon, 25 May 1998 09:03:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA11443 for ; Mon, 25 May 1998 09:03:45 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0ydziy-00021C-00; Mon, 25 May 1998 10:03:44 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id KAA20388 for ; Mon, 25 May 1998 10:03:04 -0600 (MDT) Message-Id: <199805251603.KAA20388@harmony.village.org> To: current@FreeBSD.ORG Subject: boot message Date: Mon, 25 May 1998 10:03:04 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Should I worry about: struct nfsmount bloated (> 512bytes) Try reducing NFS_MUIDHASHSIZ when I boot a new kernel? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 09:31:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16398 for freebsd-current-outgoing; Mon, 25 May 1998 09:31:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16388 for ; Mon, 25 May 1998 09:31:51 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA24512; Mon, 25 May 1998 16:31:36 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA03926; Mon, 25 May 1998 18:31:25 +0200 (MET DST) Message-ID: <19980525183125.25188@follo.net> Date: Mon, 25 May 1998 18:31:25 +0200 From: Eivind Eklund To: Warner Losh , current@FreeBSD.ORG Subject: Re: boot message References: <199805251603.KAA20388@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805251603.KAA20388@harmony.village.org>; from Warner Losh on Mon, May 25, 1998 at 10:03:04AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 25, 1998 at 10:03:04AM -0600, Warner Losh wrote: > > Should I worry about: > > struct nfsmount bloated (> 512bytes) > Try reducing NFS_MUIDHASHSIZ > > when I boot a new kernel? Only in that NFS waste memory. Besides, that problem was fixed by Peter Wemm two days ago. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 09:33:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16872 for freebsd-current-outgoing; Mon, 25 May 1998 09:33:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA16864 for ; Mon, 25 May 1998 09:33:35 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0ye0Bp-000224-00; Mon, 25 May 1998 10:33:33 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id KAA20891; Mon, 25 May 1998 10:32:52 -0600 (MDT) Message-Id: <199805251632.KAA20891@harmony.village.org> To: Eivind Eklund Subject: Re: boot message Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 25 May 1998 18:31:25 +0200." <19980525183125.25188@follo.net> References: <19980525183125.25188@follo.net> <199805251603.KAA20388@harmony.village.org> Date: Mon, 25 May 1998 10:32:52 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980525183125.25188@follo.net> Eivind Eklund writes: : Only in that NFS waste memory. Besides, that problem was fixed by : Peter Wemm two days ago. Hmmm. I must have grabbed my sources just before the change. They are dated two days ago :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 09:54:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19755 for freebsd-current-outgoing; Mon, 25 May 1998 09:54:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19734; Mon, 25 May 1998 09:54:30 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.8/8.8.8) with SMTP id JAA04979; Mon, 25 May 1998 09:54:18 -0700 (PDT) (envelope-from ejs@bfd.com) Date: Mon, 25 May 1998 09:54:18 -0700 (PDT) From: "Eric J. Schwertfeger" To: Alex Povolotsky cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 In-Reply-To: <199805250546.JAA21636@minas-tirith.pol.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 25 May 1998, Alex Povolotsky wrote: > Hello! > > Has anyone checked this new version? It is claimed to be more spam-proof. Definitely is that, though you can get most of the way there with 8.8.8 and various non-distribution rules. The single most important change is that in 8.9, relaying is off by default, and you can choose several ways to decide what you relay. By IP address, by domain, by HELO, by MX records, etc. It also includes dropin rules for RBL, DNS checking, and regex matches. I'm not sure how the DNS checking works, it seems to have some way of saying "temp failure if we traced to a DNS server that wasn't responding" and "permanant failure if we traced to a DNS dead end." All in all, I'm upgrading our machines as soon as it seems stable enough for production use. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 10:02:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21716 for freebsd-current-outgoing; Mon, 25 May 1998 10:02:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from elephants.dyn.ml.org (root@mki2-pl-ri21.kos.net [206.186.40.160]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21686 for ; Mon, 25 May 1998 10:02:26 -0700 (PDT) (envelope-from jake@elephants.dyn.ml.org) Received: from elephants.dyn.ml.org (jake@elephants.dyn.ml.org [127.0.0.1]) by elephants.dyn.ml.org (8.8.8/8.8.8) with ESMTP id NAA00276 for ; Mon, 25 May 1998 13:04:52 -0700 (PDT) (envelope-from jake@elephants.dyn.ml.org) Message-Id: <199805252004.NAA00276@elephants.dyn.ml.org> X-Mailer: exmh version 1.6.9 8/22/96 To: current@FreeBSD.ORG Subject: some questions about -current Mime-Version: 1.0 Content-Type: text/plain Date: Mon, 25 May 1998 13:04:52 -0700 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, so I've got devfs running, that's pretty cool. I just put soft-updates in my kernel, and enabled it on my filesystems. Is it ok to have it enabled for root? /dev/wd0s1a on / (local, soft-updates, writes: sync 4 async 22) devfs on dummy_mount (local) devfs on /dev (local, noexec, read-only) mfs:20 on /tmp (asynchronous, local, writes: sync 5 async 21) /dev/wd0s1f on /usr (local, soft-updates, writes: sync 2 async 73) /dev/wd0s1e on /var (local, soft-updates, writes: sync 2 async 145) procfs on /proc (local) /dev/wd0s2 on /dos (local) I get some kernel messages on bootup, I guess due to the softupdates : May 25 12:48:40 elephants /kernel: ffs_mountfs: superblock updated May 25 12:48:41 elephants /kernel: ffs_mountfs: superblock updated is that supposed to happen? only other thing out of the ordinary is that I get a couple wierd messages on "shutdown -r now". wall: /dev/jake no such file or directory wall: /dev/ is a directory any idea what's going on? I used dircmp.pl to compare my /etc to the new /etc when I upgraded to -current from -stable, only thing it reported was to copy over rc.shutdown, which I did. Thanks Jake -- http://www.checker.org/~jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 10:19:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24273 for freebsd-current-outgoing; Mon, 25 May 1998 10:19:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24263 for ; Mon, 25 May 1998 10:19:50 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id TAA06127; Mon, 25 May 1998 19:15:06 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id TAA16033; Mon, 25 May 1998 19:08:35 +0200 (CEST) (envelope-from andreas) Message-ID: <19980525190835.A16023@klemm.gtn.com> Date: Mon, 25 May 1998 19:08:35 +0200 From: Andreas Klemm To: Zach Heilig , Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: Softupdates panic (got it!) References: <19980523024530.44245@gaffaneys.com> <19980525082036.A2194@klemm.gtn.com> <19980525053943.56833@gaffaneys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980525053943.56833@gaffaneys.com>; from Zach Heilig on Mon, May 25, 1998 at 05:39:43AM -0500 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, May 25, 1998 at 05:39:43AM -0500, Zach Heilig wrote: > On Mon, May 25, 1998 at 08:20:36AM +0200, Andreas Klemm wrote: > > Here on my SMP system it runs flawlessly since days. > > Just wanted to let you know. > > Ah, but how full are your disks, I have my system partitioned like: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > ... > /dev/wd1s4a 89287 73519 8626 89% /usr Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/sd0s2a 31743 26555 2649 91% 1543 6391 19% / /dev/sd0s2f 1029135 369757 577048 39% 26114 231548 10% /usr /dev/sd0s2e 127023 38875 77987 33% 937 30805 3% /var /dev/ccd0c 198327 148876 33585 82% 15442 34284 31% /obj /dev/ccd1c 198327 37098 145363 20% 14572 35154 29% /news /dev/ccd2c 99055 24498 66633 27% 6395 18691 25% /proxy /dev/ccd3c 3400078 2360099 767973 75% 151903 698271 18% /home mfs:33 30991 20 28492 0% 25 7781 0% /tmp -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 10:27:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25957 for freebsd-current-outgoing; Mon, 25 May 1998 10:27:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25951 for ; Mon, 25 May 1998 10:27:51 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id NAA21015; Mon, 25 May 1998 13:27:36 -0400 (EDT) (envelope-from wollman) Date: Mon, 25 May 1998 13:27:36 -0400 (EDT) From: Garrett Wollman Message-Id: <199805251727.NAA21015@khavrinen.lcs.mit.edu> To: Brian Somers Cc: Bruce Evans , archie@whistle.com, freebsd-current@FreeBSD.ORG, julian@whistle.com Subject: Re: **HEADS UP** user-ppp has changed ! In-Reply-To: <199805232253.XAA26943@awfulhak.org> References: <199805231754.DAA02639@godzilla.zeta.org.au> <199805232253.XAA26943@awfulhak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > What'd be really nice is if there was some way of donating PGRP > rights to the other side of a local socket - I'm not allowed to > tcsetpgrp() 'cos the other ppp isn't part of my session. This > would be similar to SCM_RIGHTS & SCM_CREDS, but would affect the > tty in that the tty would zero its session pointer and change it's > PGRP pointer to that of the receiver. It's probably trickier than > that though :-/ Actually, I think that the unp_{ex,in}ternalize() functions should probably handle this, although describing what the right behavior actually would be is a bit tricky. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 10:51:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00893 for freebsd-current-outgoing; Mon, 25 May 1998 10:51:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lsmarso.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00888 for ; Mon, 25 May 1998 10:51:49 -0700 (PDT) (envelope-from larry@lsmarso.dialup.access.net) Received: (from larry@localhost) by lsmarso.dialup.access.net (8.8.8/8.8.8) id NAA12930 for freebsd-current@freebsd.org; Mon, 25 May 1998 13:52:21 -0400 (EDT) (envelope-from larry) Message-ID: <19980525134215.C905@marso.com> Date: Mon, 25 May 1998 13:42:16 -0400 From: "Larry S. Marso" To: freebsd-questions@FreeBSD.ORG Subject: "Try reducing NFS_MUIDHASHIZ" Mail-Followup-To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get the following message during boot up: May 25 13:35:35 second /kernel: struct nfsmount bloated (>512bytes) May 25 13:35:35 second /kernel: Try reducing NFS_MUIDHASHSIZ Note that, after a few minutes copying files as a NFS client from another FreeBSD NFS server box, the client box locks up. I cant find this documented anywhere. What do I reduce exactly? Thank you kindly. Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 14:33:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09125 for freebsd-current-outgoing; Mon, 25 May 1998 14:33:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09102; Mon, 25 May 1998 14:33:20 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0.Beta7/frmug-2.3/nospam) with UUCP id XAA17457; Mon, 25 May 1998 23:33:13 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id UAA11491; Mon, 25 May 1998 20:12:15 +0200 (CEST) (envelope-from roberto) Message-ID: <19980525201214.A10364@keltia.freenix.fr> Date: Mon, 25 May 1998 20:12:14 +0200 From: Ollivier Robert To: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 Mail-Followup-To: current@FreeBSD.ORG, hackers@FreeBSD.ORG References: <199805250546.JAA21636@minas-tirith.pol.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.3i In-Reply-To: <199805250546.JAA21636@minas-tirith.pol.ru>; from Alex Povolotsky on Mon, May 25, 1998 at 09:46:27AM +0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4311 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Alex Povolotsky: > Has anyone checked this new version? It is claimed to be more spam-proof. It is by a large extend (relaying is disallowed by default). The new anti-spam rules are more versatile than the old ones by C. Assman. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #60: Fri May 15 21:04:22 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 15:40:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22924 for freebsd-current-outgoing; Mon, 25 May 1998 15:40:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22628 for ; Mon, 25 May 1998 15:40:02 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA10906; Mon, 25 May 1998 17:36:41 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805252236.RAA10906@dyson.iquest.net> Subject: Re: May 17th UP machine 'panic' In-Reply-To: <19980525140435.34553@follo.net> from Eivind Eklund at "May 25, 98 02:04:35 pm" To: eivind@yes.no (Eivind Eklund) Date: Mon, 25 May 1998 17:36:36 -0500 (EST) Cc: michaelh@cet.co.jp, tlambert@primenet.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, May 25, 1998 at 08:55:44PM +0900, Michael Hancock wrote: > > The argument should be p or curproc depending on whether or not an > > appropriate proc p is defined. I suppose you could just search and replace > > adding curproc, but that's ugly. We might have to bite the bullet and do > > it sometime later. > > If the problem is only the amount of work with doing the actual, > physical replacements, I can do that. I estimate it to less than 6 > hours of work (that's approx 1 minute 12 seconds per entry :-) > > If the problem is deciding if this is the way to go, that's something > I can't help much with - I don't know the interactions in this area > well enough. > It is a very good idea to explicitly pass down curproc. I am still working on SMP issues, and I believe that it will be a good investment. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 16:07:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28106 for freebsd-current-outgoing; Mon, 25 May 1998 16:07:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28056; Mon, 25 May 1998 16:06:46 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 25 May 1998 19:06:21 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 25 May 1998 16:06:20 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Mon, 25 May 1998 19:06:19 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 In-Reply-To: Ollivier Robert's (roberto@keltia.freenix.fr) message dated Mon, 25 May 1998 20:12:14. <19980525201214.A10364@keltia.freenix.fr> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 May 1998 19:06:19 -0400 Message-ID: <18767.896137579@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is by a large extend (relaying is disallowed by default). The new > anti-spam rules are more versatile than the old ones by C. Assman. Perhaps, but I *know* how to set up and use Claus Assman's stuff, and there are things CA's stuff does that I haven't figured out how to do with 8.9. I also gather that CA's rulesets will support 8.9. Then again, I postponed cutting over from 5.6x+IDA on everything except my firewalls until the mid-8.8.x for similar reasons. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 16:40:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03807 for freebsd-current-outgoing; Mon, 25 May 1998 16:40:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03800 for ; Mon, 25 May 1998 16:40:48 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA11492 for current@freebsd.org; Mon, 25 May 1998 18:40:48 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805252340.SAA11492@dyson.iquest.net> Subject: Current improvements to SMP and other things To: current@FreeBSD.ORG Date: Mon, 25 May 1998 18:40:48 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am going to be unavailable for Tue through Fri this week, but also want to make available the current status of my work on SMP and threads improvements. Not all of the threads improvements that I have been working on in conjunction with the threads team are in these diffs, but most of the kernel infrastructure for context switches are in place. Note that there is improved context switching, working SMP vfork, moved the prezero code out of the idle loop, synchronized TLB flushing, minimal affinity support and many other things in this. For those running recent -current, I would appreciate feedback on this. It might take some energy to use this, and it requires a new rebuild of libkvm and ps, but you might note that SMP works noticably better with this. If you don't want to play with this, feel free just to review it for fun :-). http://www.freebsd.org/~dyson/sys25may98.diff.gz John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 19:01:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24341 for freebsd-current-outgoing; Mon, 25 May 1998 19:01:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from enigami.com (enigami.com [208.140.182.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24335 for ; Mon, 25 May 1998 19:01:31 -0700 (PDT) (envelope-from ckempf@enigami.com) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by enigami.com (8.8.7/8.8.7) with ESMTP id WAA09320 for ; Mon, 25 May 1998 22:01:15 -0400 (EDT) From: Cory Kempf Received: (from ckempf@localhost) by singularity.enigami.com (8.8.8/8.8.8) id VAA16244 for freebsd-current@freebsd.org; Mon, 25 May 1998 21:58:47 -0400 (EDT) (envelope-from ckempf@enigami.com) Date: Mon, 25 May 1998 21:58:47 -0400 (EDT) Message-Id: <199805260158.VAA16244@singularity.enigami.com> To: freebsd-current@FreeBSD.ORG Subject: sio and dk440lx Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, my serial ports don't seem to want to work. According to the intel docs, com1&2 should be at 0x3f8 and 0x2f8 respectively. Dmesg says sio0 not found at 0x3f8, sio1 not found at 0x2f8. Anyone have an idea why not? Thanks, +C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 19:27:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28335 for freebsd-current-outgoing; Mon, 25 May 1998 19:27:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hawks.caro.net (hawks.caro.NET [209.12.201.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28326 for ; Mon, 25 May 1998 19:27:45 -0700 (PDT) (envelope-from root@hawks.caro.net) Received: from hawks.caro.net (localhost.caro.net [127.0.0.1]) by hawks.caro.net (8.8.8/8.8.8) with ESMTP id WAA00814 for ; Mon, 25 May 1998 22:27:48 -0400 (EDT) (envelope-from root@hawks.caro.net) Message-Id: <199805260227.WAA00814@hawks.caro.net> From: awhawks@usa.net To: freebsd-current@FreeBSD.ORG Subject: mtree problem in current Date: Mon, 25 May 1998 22:27:47 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a problem on my -current system that has been happening for a few weeks, but until now I didn't know what was causing it. I first suspected a drive going bad but have recently found that mtree is the culprit. during a make world while it is doing the installworld it calls mtree as follows: cd /usr/src/etc mtree -deu -f /usr/src/etc/mtree/BSD.root.dist -p / at this point my system hangs as far as disk access goes. Anything that requires disk access doesn't work. Network routing continues and I can change windows in my window manager but anything I do that would read or write to disk just hangs at that point. This requires that I hit the reset button to continue. The other mtree steps during make world completes fine till this point. mtree -deU /usr/src/etc/mtree/BSD.include.dist -p /usr/include is an example of one that works fine. Is this a problem in -current or is their something on my system that I need to check/fix? Thanks Adam Hawks awhawks@usa.nwt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 19:37:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00494 for freebsd-current-outgoing; Mon, 25 May 1998 19:37:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00458 for ; Mon, 25 May 1998 19:37:07 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id MAA25638; Tue, 26 May 1998 12:07:04 +0930 (CST) (envelope-from grog) Message-ID: <19980526120704.I24133@freebie.lemis.com> Date: Tue, 26 May 1998 12:07:04 +0930 From: Greg Lehey To: Cory Kempf , freebsd-current@FreeBSD.ORG Subject: Re: sio and dk440lx References: <199805260158.VAA16244@singularity.enigami.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805260158.VAA16244@singularity.enigami.com>; from Cory Kempf on Mon, May 25, 1998 at 09:58:47PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 25 May 1998 at 21:58:47 -0400, Cory Kempf wrote: > Hi again, > my serial ports don't seem to want to work. > > According to the intel docs, com1&2 should be at 0x3f8 and 0x2f8 respectively. > Dmesg says sio0 not found at 0x3f8, sio1 not found at 0x2f8. > > Anyone have an idea why not? ALi UART? Check out http://www.lemis.com/serial-port-patch.html. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 20:10:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05653 for freebsd-current-outgoing; Mon, 25 May 1998 20:10:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05647 for ; Mon, 25 May 1998 20:10:40 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA18048; Mon, 25 May 1998 20:10:28 -0700 (PDT) (envelope-from jdp) Message-Id: <199805260310.UAA18048@austin.polstra.com> To: John Birrell cc: tlambert@primenet.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Mon, 25 May 1998 15:16:08 +1000." <199805250516.PAA19101@cimlogic.com.au> Date: Mon, 25 May 1998 20:10:28 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That's why everybody who really scrutinizes ld decides it would be > > a lot easier to throw it out and switch to ELF. > > Oh, so _that_ is the reason for switching to ELF. Chuckle. It solves > the old ld problems. Just a matter of perspective, I guess. 8-) Well, seriously, for me at least that's a large part of the motivation. Unfortunately, the binutils linker isn't, uh, what you'd call "transparent," either. But at least it has plenty of users and plenty of maintainers. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 20:12:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06017 for freebsd-current-outgoing; Mon, 25 May 1998 20:12:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05997 for ; Mon, 25 May 1998 20:12:38 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id NAA21720; Tue, 26 May 1998 13:19:11 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805260319.NAA21720@cimlogic.com.au> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805260310.UAA18048@austin.polstra.com> from John Polstra at "May 25, 98 08:10:28 pm" To: jdp@polstra.com (John Polstra) Date: Tue, 26 May 1998 13:19:09 +1000 (EST) Cc: jb@cimlogic.com.au, tlambert@primenet.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > Well, seriously, for me at least that's a large part of the > motivation. Unfortunately, the binutils linker isn't, uh, what you'd > call "transparent," either. But at least it has plenty of users and > plenty of maintainers. BTW, what's you opinion of egcs? NetBSD are adopting it as their standard compiler. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 20:52:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11173 for freebsd-current-outgoing; Mon, 25 May 1998 20:52:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11162 for ; Mon, 25 May 1998 20:52:26 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA18333; Mon, 25 May 1998 20:52:19 -0700 (PDT) (envelope-from jdp) Message-Id: <199805260352.UAA18333@austin.polstra.com> To: John Birrell cc: tlambert@primenet.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Tue, 26 May 1998 13:19:09 +1000." <199805260319.NAA21720@cimlogic.com.au> Date: Mon, 25 May 1998 20:52:18 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > BTW, what's you opinion of egcs? It seems to have frequent ups and downs. We have been using the Feb. 21 snapshot for a fairly large C++ project that I'm involved with, and we haven't had any show-stopper problems. But I believe some of the other team members tried a later snapshot and ran into all sorts of bugs. One thing I can say is that the template support is immeasurably better than what was in gcc-2.7.2. I haven't tried gcc-2.8.1, but I've heard that its C++ support is much improved over 2.7.2 as well. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 21:51:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18620 for freebsd-current-outgoing; Mon, 25 May 1998 21:51:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18612 for ; Mon, 25 May 1998 21:51:07 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id XAA11130; Mon, 25 May 1998 23:50:43 -0500 (EST) (envelope-from toor) Message-Id: <199805260450.XAA11130@dyson.iquest.net> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805260352.UAA18333@austin.polstra.com> from John Polstra at "May 25, 98 08:52:18 pm" To: jdp@polstra.com (John Polstra) Date: Mon, 25 May 1998 23:50:43 -0500 (EST) Cc: jb@cimlogic.com.au, tlambert@primenet.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra said: > > BTW, what's you opinion of egcs? > > It seems to have frequent ups and downs. We have been using the > Feb. 21 snapshot for a fairly large C++ project that I'm involved > with, and we haven't had any show-stopper problems. But I believe > some of the other team members tried a later snapshot and ran into all > sorts of bugs. > > One thing I can say is that the template support is immeasurably > better than what was in gcc-2.7.2. I haven't tried gcc-2.8.1, but > I've heard that its C++ support is much improved over 2.7.2 as well. > I have had problems running kernels with the -current egcs code for the last few weeks. I believe that I have been able to build and run a kernel based upon earlier egcs snapshots (several months old.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon May 25 23:24:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00668 for freebsd-current-outgoing; Mon, 25 May 1998 23:24:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00662; Mon, 25 May 1998 23:24:11 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id BAA15779; Tue, 26 May 1998 01:23:15 -0400 (EDT) Date: Tue, 26 May 1998 01:23:15 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@localhost To: "John S. Dyson" cc: John Polstra , jb@cimlogic.com.au, tlambert@primenet.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805260450.XAA11130@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 25 May 1998, John S. Dyson wrote: > John Polstra said: > > > BTW, what's you opinion of egcs? > > > > It seems to have frequent ups and downs. We have been using the > > Feb. 21 snapshot for a fairly large C++ project that I'm involved > > with, and we haven't had any show-stopper problems. But I believe > > some of the other team members tried a later snapshot and ran into all > > sorts of bugs. > > > > One thing I can say is that the template support is immeasurably > > better than what was in gcc-2.7.2. I haven't tried gcc-2.8.1, but > > I've heard that its C++ support is much improved over 2.7.2 as well. > > > I have had problems running kernels with the -current egcs code > for the last few weeks. I believe that I have been able to build > and run a kernel based upon earlier egcs snapshots (several months > old.) I don't know if it counts as a very persuasive data point, but a real large port of mine, octave, won't build under egcs (I got an internal compiler error for which I submitted a bug report). Gcc-2.8.1 compiled and ran it fine, which gcc-2.7.2.1 couldn't do (it could compile but not run it). Octave makes heavy use of templates, libstdc++, and virtual functions. Since our kernel hasn't any c++, it probably won't really matter, but I thought I'd put the data in your hands and let you decide. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 00:17:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07428 for freebsd-current-outgoing; Tue, 26 May 1998 00:17:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07423 for ; Tue, 26 May 1998 00:17:31 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id JAA23979 for current@freebsd.org; Tue, 26 May 1998 09:17:06 +0200 (CEST) (envelope-from sos) Message-Id: <199805260717.JAA23979@sos.freebsd.dk> Subject: ELF preparation step 1 done To: current@FreeBSD.ORG (FreeBSD current) Date: Tue, 26 May 1998 09:17:06 +0200 (CEST) From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those not watching the commit logs: I have commited the first steps in ELF'ifying -current. This means that binutils are now enabled, and the tools has been moved to /usr/libexec/{aout|elf}, and all access go through /usr/bin/objformat which decides what type util to call based on the contents of /etc/objformat and $OBJFORMAT, default is still aout for the time being. More will follow, this has to settle for a while, and I'm away from the 27/5 - 4/6, so just be patient and dont flood my mailbox with question about when/how/what the next steps will be. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 01:03:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12330 for freebsd-current-outgoing; Tue, 26 May 1998 01:03:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles305.castles.com [208.214.167.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12309 for ; Tue, 26 May 1998 01:03:37 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00722; Mon, 25 May 1998 23:59:40 -0700 (PDT) Message-Id: <199805260659.XAA00722@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: awhawks@usa.net cc: freebsd-current@FreeBSD.ORG Subject: Re: mtree problem in current In-reply-to: Your message of "Mon, 25 May 1998 22:27:47 EDT." <199805260227.WAA00814@hawks.caro.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 May 1998 23:59:40 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a problem on my -current system that has been happening for a > few weeks, but until now I didn't know what was causing it. I first > suspected a drive going bad but have recently found that mtree is > the culprit. mtree is not the culprit. mtree may be triggering the problem, but it is incapable of directly causing the symptoms you are seeing. > Is this a problem in -current or is their something on my system that I > need to check/fix? You have not provided enough information to attempt to diagnose your problem. In addition, if you are running -current you are expected to be able to deal with trivial problems like this yourself. Some things to check: - does an older kernel work? - are there any disk-related errors on the console? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 01:05:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12730 for freebsd-current-outgoing; Tue, 26 May 1998 01:05:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles305.castles.com [208.214.167.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12718 for ; Tue, 26 May 1998 01:05:04 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id AAA00753; Tue, 26 May 1998 00:01:04 -0700 (PDT) Message-Id: <199805260701.AAA00753@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: sio and dk440lx In-reply-to: Your message of "Mon, 25 May 1998 21:58:47 EDT." <199805260158.VAA16244@singularity.enigami.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 00:01:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi again, > my serial ports don't seem to want to work. > > According to the intel docs, com1&2 should be at 0x3f8 and 0x2f8 respectively. > Dmesg says sio0 not found at 0x3f8, sio1 not found at 0x2f8. The DK440LX ('Atlanta') board is believed to work just fine. > Anyone have an idea why not? You may have disabled the ports in the BIOS setup. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 02:50:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA27299 for freebsd-current-outgoing; Tue, 26 May 1998 02:50:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA27293 for ; Tue, 26 May 1998 02:50:29 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id KAA02082 for ; Tue, 26 May 1998 10:50:23 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <356A905E.3FF528D8@tdx.co.uk> Date: Tue, 26 May 1998 10:50:22 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Problems with TOSHA... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've just installed the port of TOSHA on 3.0-CURRENT (as of Friday I think) - it runs fine when run for the first time on a cd, but if I run it again on the same CD I get; " SCIOCCOMMAND ioctl: Command accepted. return status 1 (Command Timeout) after 2000 msCommand out (12 of 12): d8 00 00 00 00 21 00 00 00 0a 00 00 Data in (0 of 23520): No sense sent. SCIOCCOMMAND ioctl: Command accepted. return status 1 (Command Timeout) after 2000 msCommand out (12 of 12): d8 00 00 00 00 2b 00 00 00 0a 00 00 " I've double checked the termination etc. - it all seems OK - and if I eject the disk, and put it back in again - it works fine (I've checked the CD for any dirt etc.) The CD is a 7 disk jukebox hanging off a 1542CF Does anyone know what the sense codes etc. are? Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 03:57:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04982 for freebsd-current-outgoing; Tue, 26 May 1998 03:57:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04977 for ; Tue, 26 May 1998 03:57:15 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.8.8/8.8.5) with SMTP id GAA01763; Tue, 26 May 1998 06:56:54 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Chuck Robey Cc: jb@cimlogic.com.au, tlambert@primenet.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning Date: Tue, 26 May 1998 10:59:24 GMT Message-ID: <356a9f0a.251653824@mail.cetlink.net> References: In-Reply-To: X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA04978 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 May 1998 01:23:15 -0400 (EDT), Chuck Robey wrote: >> > > BTW, what's you opinion of egcs? >> > >> > It seems to have frequent ups and downs. >I don't know if it counts as a very persuasive data point, but a real >large port of mine, octave, won't build under egcs (I got an internal >compiler error for which I submitted a bug report). Gcc-2.8.1 compiled >and ran it fine The "e" in egcs does stand for experimental. The NetBSD developers must be confident the bugs will shake out soon since they are planning to move to egcs, or they must think the benefits are worth the bugs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 04:20:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09848 for freebsd-current-outgoing; Tue, 26 May 1998 04:20:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09840 for ; Tue, 26 May 1998 04:20:09 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id MAA14139 for ; Tue, 26 May 1998 12:20:03 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <356AA564.915D1F14@tdx.co.uk> Date: Tue, 26 May 1998 12:20:04 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Error building 'cvsup' on 3.0-CURRENT as of 24th May,1998 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone know why I get: " mkdir FreeBSD2 --- building in FreeBSD2 --- m3 -w1 -why -O -a libm3parseparams.a -F/var/tmp/qkN13279 new source -> compiling ../src/ParseParams.i3 new source -> compiling ../src/ParseParams.m3 *** *** runtime error: *** Segmentation violation - possible attempt to dereference NIL *** *** runtime error: *** ASSERT failed *** file "../src/runtime/common/RTHeapMap.m3", line 35 *** Abort trap - core dumped *** error code 134 (ignored) missing libm3parseparams.a: not building libm3parseparams.so.6.0 [huge amount snipped] *** Error code 255 Stop. *** Error code 1 " Is there any other way of getting cvsup, cvsupd etc. on the system ( I know theres a 'binary' version of cvsup - but it doesn't seem to include the server components)... Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 06:43:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25423 for freebsd-current-outgoing; Tue, 26 May 1998 06:43:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25416 for ; Tue, 26 May 1998 06:43:31 -0700 (PDT) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.8.8/8.8.8) id JAA10484; Tue, 26 May 1998 09:43:21 -0400 (EDT) (envelope-from larry) Message-ID: <19980526094320.C10429@marso.com> Date: Tue, 26 May 1998 09:43:20 -0400 From: "Larry S. Marso&" To: freebsd-current@FreeBSD.ORG Subject: volume control under current? Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm using snd0, sb0. I've made the devices and sound works. However, I can't run ports/audio/cam. It says: SOUND_MIXER_READ_DEVMASK : Error reading /dev/mixer Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 07:11:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29742 for freebsd-current-outgoing; Tue, 26 May 1998 07:11:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from door.bzw.com (www.barclayscapital.com [194.205.158.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29718 for ; Tue, 26 May 1998 07:11:01 -0700 (PDT) (envelope-from Pierre.Dampure@barclayscapital.com) Received: (from mailman@localhost) by door.bzw.com (8.8.8/8.8.7) id PAA25394 for ; Tue, 26 May 1998 15:09:51 +0100 (BST) Received: from gate.bzw.com(194.205.158.68) by door.bzw.com via smap (V2.0) id xmaa25367; Tue, 26 May 98 15:09:47 +0100 Received: (from nobody@localhost) by gate.bzw.com (8.8.7/8.8.7) id PAA15719 for ; Tue, 26 May 1998 15:10:48 +0100 (BST) Received: from fwgw01-dmz(194.205.158.129) by gate.bzw.com via smap (V2.0) id xma015696; Tue, 26 May 98 15:10:45 +0100 Received: (from nobody@localhost) by fwgw01.ldn.bzwint.com (8.8.7/8.8.7) id PAA11250 for ; Tue, 26 May 1998 15:10:44 +0100 (BST) Received: from oplss0001.itops.ldn.bzwint.com(30.75.1.4) by fwgw01.ldn.bzwint.com via smap (V2.0) id xma011199; Tue, 26 May 98 15:10:39 +0100 Received: from nmb01gw01 (smtphost.ldn.bzwint.com [30.10.1.10]) by oplss0001.itops.ldn.bzwint.com (8.8.7/8.8.6) with SMTP id PAA01426 for ; Tue, 26 May 1998 15:10:11 +0100 (BST) Received: from exintgw02.itops.ldn.bzwint.com (exintgw02.itops.ldn.bzwint.com [30.45.1.87]) by nmb01gw01 (NTMail 3.02.13) with ESMTP id ta663669 for ; Tue, 26 May 1998 14:58:44 +0100 Received: by exintgw02.itops.ldn.bzwint.com with Internet Mail Service (5.0.1460.8) id ; Tue, 26 May 1998 15:10:11 +0100 Message-ID: <711DCB8FB391D111B9DD00805F8BDDBA7262F6@exips0019.itops.ldn.bzwint.com> From: "Dampure, Pierre-Yves: IT (LDN)" To: "'Karl Pielorz'" , current@FreeBSD.ORG Subject: RE: Error building 'cvsup' on 3.0-CURRENT as of 24th May,1998 Date: Tue, 26 May 1998 15:11:00 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has been the case for a while now -- at least if you are running on an SMP kernel. John Dyson and John Polstra are both aware of the issue, and John Dyson pledged to look at it at some point Real Soon Now. If you are running SMP (and it looks your are, if you get this), you might want to try John Dyson's latest mods, posted (NOT CVSupped) yesterday. I have applied / make world w/ them and will attempt a Modula-3 rebuild tonight when back from work. Best Regards, Pierre Y. > -----Original Message----- > From: Karl Pielorz [SMTP:kpielorz@tdx.co.uk] > Sent: 26 May 1998 12:20 > To: current@FreeBSD.ORG > Subject: Error building 'cvsup' on 3.0-CURRENT as of 24th May,1998 > > Anyone know why I get: > > " > mkdir FreeBSD2 > --- building in FreeBSD2 --- > m3 -w1 -why -O -a libm3parseparams.a -F/var/tmp/qkN13279 > new source -> compiling ../src/ParseParams.i3 > new source -> compiling ../src/ParseParams.m3 > > > *** > *** runtime error: > *** Segmentation violation - possible attempt to dereference NIL > > *** > *** runtime error: > *** ASSERT failed > *** file "../src/runtime/common/RTHeapMap.m3", line 35 > *** > > Abort trap - core dumped > *** error code 134 (ignored) > missing libm3parseparams.a: not building libm3parseparams.so.6.0 > [huge amount snipped] > *** Error code 255 > > Stop. > *** Error code 1 > " > > Is there any other way of getting cvsup, cvsupd etc. on the system ( I > know > theres a 'binary' version of cvsup - but it doesn't seem to include the > server components)... > > Regards, > > Karl Pielorz > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 07:54:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07530 for freebsd-current-outgoing; Tue, 26 May 1998 07:54:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07520; Tue, 26 May 1998 07:54:04 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id IAA20392; Tue, 26 May 1998 08:53:57 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA04998; Tue, 26 May 1998 08:53:56 -0600 Date: Tue, 26 May 1998 08:53:56 -0600 Message-Id: <199805261453.IAA04998@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: sos@FreeBSD.ORG Cc: current@FreeBSD.ORG (FreeBSD current) Subject: Re: ELF preparation step 1 done In-Reply-To: <199805260717.JAA23979@sos.freebsd.dk> References: <199805260717.JAA23979@sos.freebsd.dk> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For those not watching the commit logs: > > I have commited the first steps in ELF'ifying -current. This means > that binutils are now enabled, and the tools has been moved to > /usr/libexec/{aout|elf} Have the mtree files been updated to create the new directories? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 08:02:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09651 for freebsd-current-outgoing; Tue, 26 May 1998 08:02:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09556; Tue, 26 May 1998 08:02:01 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id RAA26805; Tue, 26 May 1998 17:01:25 +0200 (CEST) (envelope-from sos) Message-Id: <199805261501.RAA26805@sos.freebsd.dk> Subject: Re: ELF preparation step 1 done In-Reply-To: <199805261453.IAA04998@mt.sri.com> from Nate Williams at "May 26, 98 08:53:56 am" To: nate@mt.sri.com (Nate Williams) Date: Tue, 26 May 1998 17:01:25 +0200 (CEST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Nate Williams who wrote: > > For those not watching the commit logs: > > > > I have commited the first steps in ELF'ifying -current. This means > > that binutils are now enabled, and the tools has been moved to > > /usr/libexec/{aout|elf} > > Have the mtree files been updated to create the new directories? Yes long ago... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 08:21:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14537 for freebsd-current-outgoing; Tue, 26 May 1998 08:21:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14520; Tue, 26 May 1998 08:20:59 -0700 (PDT) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.8.8/8.8.8) id LAA04286; Tue, 26 May 1998 11:20:47 -0400 (EDT) (envelope-from larry) Message-ID: <19980526112046.A3058@marso.com> Date: Tue, 26 May 1998 11:20:46 -0400 From: "Larry S. Marso" To: freebsd-mobile@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: hot swapping fails in current Mail-Followup-To: freebsd-mobile@freebsd.org, freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any reason why current as of three days ago would fail to notice the addition or removal of PCMCIA cards, but properly configure them upon boot-up? Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 08:31:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16416 for freebsd-current-outgoing; Tue, 26 May 1998 08:31:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16401 for ; Tue, 26 May 1998 08:31:52 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id JAA22406; Tue, 26 May 1998 09:31:11 -0600 (MDT) Message-Id: <199805261531.JAA22406@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: John Polstra cc: John Birrell , tlambert@primenet.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Mon, 25 May 1998 20:52:18 PDT." <199805260352.UAA18333@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 09:31:11 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > BTW, what's you opinion of egcs? > > It seems to have frequent ups and downs. We have been using the > Feb. 21 snapshot for a fairly large C++ project that I'm involved > with, and we haven't had any show-stopper problems. But I believe > some of the other team members tried a later snapshot and ran into all > sorts of bugs. > > One thing I can say is that the template support is immeasurably > better than what was in gcc-2.7.2. I haven't tried gcc-2.8.1, but > I've heard that its C++ support is much improved over 2.7.2 as well. We're doing a complex c++/pthreads project and found that neither 2.7.2 or 2.8.1 worked for us, but an egcs snap from several months ago works well. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 09:56:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03369 for freebsd-current-outgoing; Tue, 26 May 1998 09:56:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03363 for ; Tue, 26 May 1998 09:56:44 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA19888; Tue, 26 May 1998 11:56:23 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805261656.LAA19888@dyson.iquest.net> Subject: Re: Error building 'cvsup' on 3.0-CURRENT as of 24th May,1998 In-Reply-To: <711DCB8FB391D111B9DD00805F8BDDBA7262F6@exips0019.itops.ldn.bzwint.com> from "Dampure, Pierre-Yves: IT" at "May 26, 98 03:11:00 pm" To: Pierre.Dampure@barclayscapital.com (Dampure Pierre-Yves: IT) Date: Tue, 26 May 1998 11:56:23 -0500 (EST) Cc: kpielorz@tdx.co.uk, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > This has been the case for a while now -- at least if you are running on an > SMP kernel. John Dyson and John Polstra are both aware of the issue, and > John Dyson pledged to look at it at some point Real Soon Now. If you are > running SMP (and it looks your are, if you get this), you might want to try > John Dyson's latest mods, posted (NOT CVSupped) yesterday. I have applied / > make world w/ them and will attempt a Modula-3 rebuild tonight when back > from work. > There have been some problems with my mods. I have cleaned up some bugs, and will be posting them again later on this week. My biggest problem officially committing the mods will be that I have no SMP P5 system (nor do I want one :-)). It will take a little bit of code review to make sure that the code is P5 safe (I made some stupid assumptions in my mods that the code is running on P6 machines.) I believe that there are a few more bugs (even beyond my very stable code -- there was a severe MI bug in my patches.) This SMP stuff is trickier than VM by far :-)... At least I am learning enough about the SMP architecture to know where we are, and know that it isn't precisely where we want to be :-). John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 10:00:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04112 for freebsd-current-outgoing; Tue, 26 May 1998 10:00:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04096 for ; Tue, 26 May 1998 10:00:44 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA19904; Tue, 26 May 1998 11:59:52 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805261659.LAA19904@dyson.iquest.net> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <356a9f0a.251653824@mail.cetlink.net> from John Kelly at "May 26, 98 10:59:24 am" To: jak@cetlink.net (John Kelly) Date: Tue, 26 May 1998 11:59:52 -0500 (EST) Cc: chuckr@glue.umd.edu, jb@cimlogic.com.au, tlambert@primenet.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 26 May 1998 01:23:15 -0400 (EDT), Chuck Robey > wrote: > > >> > > BTW, what's you opinion of egcs? > >> > > >> > It seems to have frequent ups and downs. > > >I don't know if it counts as a very persuasive data point, but a real > >large port of mine, octave, won't build under egcs (I got an internal > >compiler error for which I submitted a bug report). Gcc-2.8.1 compiled > >and ran it fine > > The "e" in egcs does stand for experimental. The NetBSD developers > must be confident the bugs will shake out soon since they are planning > to move to egcs, or they must think the benefits are worth the bugs. > We are also not "controlling" egcs. This means that we are relatively passively dependent on a vendor. It is definitely hit-or-miss whether or not that we can adopt egcs. In a few weeks, I'll try to regression test a couple of egcs releases and/or snapshots. I am hopeful, but definitely not confident that one of the releases is stable enough. I really don't think that we would want to also get into compiler support issues. Tool support issues are complex enough. I can imagine that egcs (could) be stable enough for our c++ compiler, but am much less confident of it being our default c compiler. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 10:08:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06061 for freebsd-current-outgoing; Tue, 26 May 1998 10:08:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from door.bzw.com (door.bzw.com [194.205.158.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06054 for ; Tue, 26 May 1998 10:08:13 -0700 (PDT) (envelope-from Pierre.Dampure@barclayscapital.com) Received: (from mailman@localhost) by door.bzw.com (8.8.8/8.8.7) id SAA26021 for ; Tue, 26 May 1998 18:07:11 +0100 (BST) Received: from gate.bzw.com(194.205.158.68) by door.bzw.com via smap (V2.0) id xma026010; Tue, 26 May 98 18:07:10 +0100 Received: (from nobody@localhost) by gate.bzw.com (8.8.7/8.8.7) id SAA06319 for ; Tue, 26 May 1998 18:08:11 +0100 (BST) Received: from fwgw01-dmz(194.205.158.129) by gate.bzw.com via smap (V2.0) id xma006314; Tue, 26 May 98 18:08:11 +0100 Received: (from nobody@localhost) by fwgw01.ldn.bzwint.com (8.8.7/8.8.7) id SAA00531 for ; Tue, 26 May 1998 18:08:10 +0100 (BST) Received: from oplss0001.itops.ldn.bzwint.com(30.75.1.4) by fwgw01.ldn.bzwint.com via smap (V2.0) id xma000504; Tue, 26 May 98 18:08:06 +0100 Received: from nmb01gw01 (smtphost.ldn.bzwint.com [30.10.1.10]) by oplss0001.itops.ldn.bzwint.com (8.8.7/8.8.6) with SMTP id SAA18886 for ; Tue, 26 May 1998 18:07:39 +0100 (BST) Received: from exintgw02.itops.ldn.bzwint.com (exintgw02.itops.ldn.bzwint.com [30.45.1.87]) by nmb01gw01 (NTMail 3.02.13) with ESMTP id aa669526 for ; Tue, 26 May 1998 17:56:14 +0100 Received: by exintgw02.itops.ldn.bzwint.com with Internet Mail Service (5.0.1460.8) id ; Tue, 26 May 1998 18:07:41 +0100 Message-ID: <711DCB8FB391D111B9DD00805F8BDDBA7262F9@exips0019.itops.ldn.bzwint.com> From: "Dampure, Pierre-Yves: IT (LDN)" To: "'John S. Dyson'" Cc: kpielorz@tdx.co.uk, current@FreeBSD.ORG Subject: RE: Error building 'cvsup' on 3.0-CURRENT as of 24th May,1998 Date: Tue, 26 May 1998 18:08:31 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, On my dual P6 box, here's what I found so far: Only rebuilding the SMP kernel / libkvm / ps failed big time: on reboot, ps was giving a proc size mismatch; a subsequent make -j12 world (using the new kernel) locked the machine solid (shame on me, I did not have the kernel debugger enabled at that time). I then nuked your diffs, rebuild an SMP-current kernel, reapplied your diffs and re-did a make -j12 world, which worked ok. The ps problem did not reoccur --> dependencies ? Best Regards, Pierre Y. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 10:11:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06664 for freebsd-current-outgoing; Tue, 26 May 1998 10:11:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06659 for ; Tue, 26 May 1998 10:11:24 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA20004; Tue, 26 May 1998 12:11:05 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805261711.MAA20004@dyson.iquest.net> Subject: Re: Error building 'cvsup' on 3.0-CURRENT as of 24th May,1998 In-Reply-To: <711DCB8FB391D111B9DD00805F8BDDBA7262F9@exips0019.itops.ldn.bzwint.com> from "Dampure, Pierre-Yves: IT" at "May 26, 98 06:08:31 pm" To: Pierre.Dampure@barclayscapital.com (Dampure Pierre-Yves: IT) Date: Tue, 26 May 1998 12:11:05 -0500 (EST) Cc: toor@dyson.iquest.net, kpielorz@tdx.co.uk, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > John, > > On my dual P6 box, here's what I found so far: > > Only rebuilding the SMP kernel / libkvm / ps failed big time: on reboot, ps > was giving a proc size mismatch; a subsequent make -j12 world (using the new > kernel) locked the machine solid (shame on me, I did not have the kernel > debugger enabled at that time). > > I then nuked your diffs, rebuild an SMP-current kernel, reapplied your diffs > and re-did a make -j12 world, which worked ok. The ps problem did not > reoccur --> dependencies ? > The dependencies problems are problematical. I have also downloaded some new diffs. I believe that I had some problems in what I originally posted, but it is close. The new diffs are probably better (more reliable.) This SMP stuff is really a challenge, much harder than VM :-). John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 10:43:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13103 for freebsd-current-outgoing; Tue, 26 May 1998 10:43:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13094 for ; Tue, 26 May 1998 10:43:44 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id RAA11445; Tue, 26 May 1998 17:43:35 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA16225; Tue, 26 May 1998 19:43:34 +0200 (MET DST) Message-ID: <19980526194334.44185@follo.net> Date: Tue, 26 May 1998 19:43:34 +0200 From: Eivind Eklund To: "John S. Dyson" Cc: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <356a9f0a.251653824@mail.cetlink.net> <199805261659.LAA19904@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805261659.LAA19904@dyson.iquest.net>; from John S. Dyson on Tue, May 26, 1998 at 11:59:52AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 26, 1998 at 11:59:52AM -0500, John S. Dyson wrote: > I really don't think that we would want to also get into compiler > support issues. Tool support issues are complex enough. I can imagine > that egcs (could) be stable enough for our c++ compiler, but am much > less confident of it being our default c compiler. Personally I'd prefer to use TenDRA if at all possible. It seems to be much better than GCC when you look at error control etc. Besides, it has the license we've got as a goal to have overall (ie, a BSD-style license :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 10:50:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14269 for freebsd-current-outgoing; Tue, 26 May 1998 10:50:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14099 for ; Tue, 26 May 1998 10:50:00 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA20256; Tue, 26 May 1998 12:49:52 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805261749.MAA20256@dyson.iquest.net> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <19980526194334.44185@follo.net> from Eivind Eklund at "May 26, 98 07:43:34 pm" To: eivind@yes.no (Eivind Eklund) Date: Tue, 26 May 1998 12:49:52 -0500 (EST) Cc: toor@dyson.iquest.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, May 26, 1998 at 11:59:52AM -0500, John S. Dyson wrote: > > I really don't think that we would want to also get into compiler > > support issues. Tool support issues are complex enough. I can imagine > > that egcs (could) be stable enough for our c++ compiler, but am much > > less confident of it being our default c compiler. > > Personally I'd prefer to use TenDRA if at all possible. It seems to > be much better than GCC when you look at error control etc. > > Besides, it has the license we've got as a goal to have overall (ie, a > BSD-style license :-) > Interesting idea... I wonder how good it's code generation is (what is the cost of using it, performance wise???) If it isn't very slow, it might be a more reliable alternative. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 10:51:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14479 for freebsd-current-outgoing; Tue, 26 May 1998 10:51:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14461 for ; Tue, 26 May 1998 10:51:07 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id LAA21656; Tue, 26 May 1998 11:50:55 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA07058; Tue, 26 May 1998 11:50:53 -0600 Date: Tue, 26 May 1998 11:50:53 -0600 Message-Id: <199805261750.LAA07058@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <19980526194334.44185@follo.net> References: <356a9f0a.251653824@mail.cetlink.net> <199805261659.LAA19904@dyson.iquest.net> <19980526194334.44185@follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I really don't think that we would want to also get into compiler > > support issues. Tool support issues are complex enough. I can imagine > > that egcs (could) be stable enough for our c++ compiler, but am much > > less confident of it being our default c compiler. > > Personally I'd prefer to use TenDRA if at all possible. It seems to > be much better than GCC when you look at error control etc. Can it do shlibs? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 11:16:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19782 for freebsd-current-outgoing; Tue, 26 May 1998 11:16:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19774 for ; Tue, 26 May 1998 11:16:23 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id SAA12246; Tue, 26 May 1998 18:15:54 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA16322; Tue, 26 May 1998 20:15:53 +0200 (MET DST) Message-ID: <19980526201549.35268@follo.net> Date: Tue, 26 May 1998 20:15:49 +0200 From: Eivind Eklund To: Nate Williams Cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <356a9f0a.251653824@mail.cetlink.net> <199805261659.LAA19904@dyson.iquest.net> <19980526194334.44185@follo.net> <199805261750.LAA07058@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805261750.LAA07058@mt.sri.com>; from Nate Williams on Tue, May 26, 1998 at 11:50:53AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 26, 1998 at 11:50:53AM -0600, Nate Williams wrote: > > > I really don't think that we would want to also get into compiler > > > support issues. Tool support issues are complex enough. I can imagine > > > that egcs (could) be stable enough for our c++ compiler, but am much > > > less confident of it being our default c compiler. > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > be much better than GCC when you look at error control etc. > > Can it do shlibs? I don't know - is there much special it would have to do? It create assembly files (as the third stage) and use the system assembler and linker, so I don't think it should be a problem, but I don't really know. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 11:18:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20319 for freebsd-current-outgoing; Tue, 26 May 1998 11:18:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA20306; Tue, 26 May 1998 11:18:51 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0yeOJ5-0002eJ-00; Tue, 26 May 1998 12:18:39 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id MAA15003; Tue, 26 May 1998 12:17:47 -0600 (MDT) Message-Id: <199805261817.MAA15003@harmony.village.org> To: "Larry S. Marso" Subject: Re: hot swapping fails in current Cc: freebsd-mobile@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 26 May 1998 11:20:46 EDT." <19980526112046.A3058@marso.com> References: <19980526112046.A3058@marso.com> Date: Tue, 26 May 1998 12:17:47 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980526112046.A3058@marso.com> "Larry S. Marso" writes: : Any reason why current as of three days ago would fail to notice the : addition or removal of PCMCIA cards, but properly configure them upon : boot-up? Sounds like a problem that I had a while ago. Nate sent me a patch. The pcic doesn't interrupt on card insertion so needs to be polled. I don't have the libretto with me today, so I can't dig out what that patch was. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 11:40:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24559 for freebsd-current-outgoing; Tue, 26 May 1998 11:40:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24535 for ; Tue, 26 May 1998 11:40:18 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA22011; Tue, 26 May 1998 12:40:17 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA07456; Tue, 26 May 1998 12:40:15 -0600 Date: Tue, 26 May 1998 12:40:15 -0600 Message-Id: <199805261840.MAA07456@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Eivind Eklund Cc: Nate Williams , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <19980526201549.35268@follo.net> References: <356a9f0a.251653824@mail.cetlink.net> <199805261659.LAA19904@dyson.iquest.net> <19980526194334.44185@follo.net> <199805261750.LAA07058@mt.sri.com> <19980526201549.35268@follo.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund writes: > On Tue, May 26, 1998 at 11:50:53AM -0600, Nate Williams wrote: > > > > I really don't think that we would want to also get into compiler > > > > support issues. Tool support issues are complex enough. I can imagine > > > > that egcs (could) be stable enough for our c++ compiler, but am much > > > > less confident of it being our default c compiler. > > > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > > be much better than GCC when you look at error control etc. > > > > Can it do shlibs? > > I don't know - is there much special it would have to do? Generating PIC code is a big prerequisite, so the assembly it generates must be capable of being relocated. I'm not 100% sure if this is a function of the compiler, but given that GCC1 couldn't do it and GCC2 could, I suspect it's a function of the compiler. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 11:40:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24619 for freebsd-current-outgoing; Tue, 26 May 1998 11:40:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24584 for ; Tue, 26 May 1998 11:40:39 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id SAA12914; Tue, 26 May 1998 18:40:34 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA16667; Tue, 26 May 1998 20:40:33 +0200 (MET DST) Message-ID: <19980526204032.01510@follo.net> Date: Tue, 26 May 1998 20:40:32 +0200 From: Eivind Eklund To: "John S. Dyson" Cc: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <19980526194334.44185@follo.net> <199805261749.MAA20256@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805261749.MAA20256@dyson.iquest.net>; from John S. Dyson on Tue, May 26, 1998 at 12:49:52PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 26, 1998 at 12:49:52PM -0500, John S. Dyson wrote: > > On Tue, May 26, 1998 at 11:59:52AM -0500, John S. Dyson wrote: > > > I really don't think that we would want to also get into compiler > > > support issues. Tool support issues are complex enough. I can imagine > > > that egcs (could) be stable enough for our c++ compiler, but am much > > > less confident of it being our default c compiler. > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > be much better than GCC when you look at error control etc. > > > > Besides, it has the license we've got as a goal to have overall (ie, a > > BSD-style license :-) > > > Interesting idea... I wonder how good it's code generation is (what is > the cost of using it, performance wise???) If it isn't very slow, it > might be a more reliable alternative. I don't know how fast the compiled code is - from looking at what optimizations the compiler does, it looks like it should be as fast as or faster than GCC. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 11:42:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24848 for freebsd-current-outgoing; Tue, 26 May 1998 11:42:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24773 for ; Tue, 26 May 1998 11:41:51 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id SAA12937; Tue, 26 May 1998 18:41:46 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA16680; Tue, 26 May 1998 20:41:45 +0200 (MET DST) Message-ID: <19980526204145.65179@follo.net> Date: Tue, 26 May 1998 20:41:45 +0200 From: Eivind Eklund To: Nate Williams Cc: current@FreeBSD.ORG Subject: Switching default compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) References: <356a9f0a.251653824@mail.cetlink.net> <199805261659.LAA19904@dyson.iquest.net> <19980526194334.44185@follo.net> <199805261750.LAA07058@mt.sri.com> <19980526201549.35268@follo.net> <199805261840.MAA07456@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805261840.MAA07456@mt.sri.com>; from Nate Williams on Tue, May 26, 1998 at 12:40:15PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 26, 1998 at 12:40:15PM -0600, Nate Williams wrote: > Eivind Eklund writes: > > On Tue, May 26, 1998 at 11:50:53AM -0600, Nate Williams wrote: > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > > > be much better than GCC when you look at error control etc. > > > > > > Can it do shlibs? > > > > I don't know - is there much special it would have to do? > > Generating PIC code is a big prerequisite, so the assembly it generates > must be capable of being relocated. I'm not 100% sure if this is a > function of the compiler, but given that GCC1 couldn't do it and GCC2 > could, I suspect it's a function of the compiler. It can do PIC for ELF on Linux. I suspect this means that we can make it do PIC for ELF on FreeBSD, too. I don't know if making it do PIC for a.out would be significantly different. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 11:56:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27388 for freebsd-current-outgoing; Tue, 26 May 1998 11:56:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rfcnet.com (rfcnet.com [207.227.20.207]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27357 for ; Tue, 26 May 1998 11:55:57 -0700 (PDT) (envelope-from mattc@rfcnet.com) Received: (from mattc@localhost) by rfcnet.com (8.8.8/8.8.8) id NAA08632; Tue, 26 May 1998 13:55:04 -0500 (CDT) (envelope-from mattc) Message-ID: <19980526135504.A8612@rfcnet.com> Date: Tue, 26 May 1998 13:55:04 -0500 From: Matthew Cashdollar To: freebsd-current@FreeBSD.ORG Subject: syslog confusion Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i x-no-archive: yes Organization: RF Communications, Inc. http://www.rfcinc.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is something to ponder... root@ainvar# syslogd -d -a 207.227.20.195 allowaddr: rule 0: numeric, addr = 207.227.20.195, mask = 255.255.255.0; port = 514 off & running.... init cfline("auth.* /var/log/auth", f, "*") cfline("*.* /var/log/ppp", f, "ppp") X X X X 8 X X X X X X X X X X X X X X X X X X X X FILE: /var/log/auth 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 X FILE: /var/log/ppp (ppp) logmsg: pri 56, flags 4, from ainvar, msg syslogd: restart syslogd: restarted readfds = 0x38 readfds = 0x38 got a message (1, 0x10) cvthname(207.227.20.195) Host name for your address (207.227.20.195) unknown validate: dgram from IP 207.227.20.195, port 514, name 207.227.20.195; rejected in rule 0 due to IP mismatch. readfds = 0x38 readfds = 0x38 I am trying to do remote logging of auth messages, from a -stable machine to my -current machine at home.. I can get it to work between two stables which have working dns.. 207.227.20.195 has the name bart.rfcnet.com, but reverse dns doesn't work (thank my isp..) could this be the problem?? how can i get around it? is there any way to 'allow all incoming messages', besides editing the source? from the error message above it seems to think that the ip address is a name.. Thanks, -- Matthew Cashdollar RF Communications, Inc. -- http://www.rfcinc.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 12:13:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00437 for freebsd-current-outgoing; Tue, 26 May 1998 12:13:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00416 for ; Tue, 26 May 1998 12:13:49 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id VAA23526; Tue, 26 May 1998 21:11:48 +0200 (CEST) (envelope-from sos) Message-Id: <199805261911.VAA23526@sos.freebsd.dk> Subject: Re: Switching default compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) In-Reply-To: <19980526204145.65179@follo.net> from Eivind Eklund at "May 26, 98 08:41:45 pm" To: eivind@yes.no (Eivind Eklund) Date: Tue, 26 May 1998 21:11:48 +0200 (CEST) Cc: nate@mt.sri.com, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Eivind Eklund who wrote: > On Tue, May 26, 1998 at 12:40:15PM -0600, Nate Williams wrote: > > Eivind Eklund writes: > > > On Tue, May 26, 1998 at 11:50:53AM -0600, Nate Williams wrote: > > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > > > > be much better than GCC when you look at error control etc. > > > > > > > > Can it do shlibs? > > > > > > I don't know - is there much special it would have to do? > > > > Generating PIC code is a big prerequisite, so the assembly it generates > > must be capable of being relocated. I'm not 100% sure if this is a > > function of the compiler, but given that GCC1 couldn't do it and GCC2 > > could, I suspect it's a function of the compiler. > > It can do PIC for ELF on Linux. I suspect this means that we can make > it do PIC for ELF on FreeBSD, too. I don't know if making it do PIC > for a.out would be significantly different. No, its the same thing.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 12:42:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04647 for freebsd-current-outgoing; Tue, 26 May 1998 12:42:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04635 for ; Tue, 26 May 1998 12:42:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00466; Tue, 26 May 1998 11:36:54 -0700 (PDT) Message-Id: <199805261836.LAA00466@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Tue, 26 May 1998 19:43:34 +0200." <19980526194334.44185@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 11:36:54 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, May 26, 1998 at 11:59:52AM -0500, John S. Dyson wrote: > > I really don't think that we would want to also get into compiler > > support issues. Tool support issues are complex enough. I can imagine > > that egcs (could) be stable enough for our c++ compiler, but am much > > less confident of it being our default c compiler. > > Personally I'd prefer to use TenDRA if at all possible. It seems to > be much better than GCC when you look at error control etc. How much of the world will build with it? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 12:50:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06339 for freebsd-current-outgoing; Tue, 26 May 1998 12:50:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06334 for ; Tue, 26 May 1998 12:50:28 -0700 (PDT) (envelope-from bsd-curr@artorius.sunflower.com) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by artorius.sunflower.com (8.8.8/8.8.7) with SMTP id OAA18472; Tue, 26 May 1998 14:50:07 -0500 (CDT) (envelope-from bsd-curr@artorius.sunflower.com) Date: Tue, 26 May 1998 14:50:07 -0500 (CDT) From: "Stephen D. Spencer" To: John Birrell cc: freebsd-current@FreeBSD.ORG Subject: Re: *** /usr/src/lib/libtermcap/termcap.h (!@#$ :) In-Reply-To: <199805222103.HAA13096@cimlogic.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 May 1998, John Birrell wrote: > [...] > AFAIK, the tree builds cleanly on both i386 and alpha with the code > the way it is. Your patch breaks the alpha build. What makes you > think otherwise? > John, Hello. You are correct in relation to current. -stable (which I was compiling the -current sources under) uses long instead of unsigned int. My bad. Regards, Stephen Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 12:51:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06510 for freebsd-current-outgoing; Tue, 26 May 1998 12:51:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06484 for ; Tue, 26 May 1998 12:51:18 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id MAA05123; Tue, 26 May 1998 12:51:08 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805261951.MAA05123@rah.star-gate.com> To: Eivind Eklund cc: "John S. Dyson" , current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Tue, 26 May 1998 20:40:32 +0200." <19980526204032.01510@follo.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5120.896212268.1@rah.star-gate.com> Date: Tue, 26 May 1998 12:51:08 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you run a simple benchmark to see if the compiler is faster than gcc? Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 13:04:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10028 for freebsd-current-outgoing; Tue, 26 May 1998 13:04:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09977; Tue, 26 May 1998 13:04:25 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id EAA28582; Wed, 27 May 1998 04:04:17 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805262004.EAA28582@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: sos@FreeBSD.ORG cc: eivind@yes.no (Eivind Eklund), nate@mt.sri.com, current@FreeBSD.ORG Subject: Re: Switching default compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) In-reply-to: Your message of "Tue, 26 May 1998 21:11:48 +0200." <199805261911.VAA23526@sos.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Wed, 27 May 1998 04:04:17 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S ren Schmidt wrote: > In reply to Eivind Eklund who wrote: > > On Tue, May 26, 1998 at 12:40:15PM -0600, Nate Williams wrote: > > > Eivind Eklund writes: > > > > On Tue, May 26, 1998 at 11:50:53AM -0600, Nate Williams wrote: > > > > > > Personally I'd prefer to use TenDRA if at all possible. It s= eems t o > > > > > > be much better than GCC when you look at error control etc. > > > > > = > > > > > Can it do shlibs? > > > > = > > > > I don't know - is there much special it would have to do? > > > = > > > Generating PIC code is a big prerequisite, so the assembly it gener= ates > > > must be capable of being relocated. I'm not 100% sure if this is a= > > > function of the compiler, but given that GCC1 couldn't do it and GC= C2 > > > could, I suspect it's a function of the compiler. > > = > > It can do PIC for ELF on Linux. I suspect this means that we can mak= e > > it do PIC for ELF on FreeBSD, too. I don't know if making it do PIC > > for a.out would be significantly different. > = > No, its the same thing.... Almost the same thing, but there are differences.. ELF supports (and requires) PIC jumps, our a.out doesn't. (jumps and calls have an absolut= e address, branches do not. Both require relocation for PIC to work). Hav= e a look at the cerror stuff in libc. I don't think any of the compilers generate code that will run into this though. So yes, at compiler-> assembler level, a.out and ELF have identical PIC output (this was the ea= sy part in dual-format gcc :-). Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 13:23:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12979 for freebsd-current-outgoing; Tue, 26 May 1998 13:23:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12922 for ; Tue, 26 May 1998 13:23:03 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id WAA00329 for current@freebsd.org; Tue, 26 May 1998 22:22:53 +0200 (CEST) (envelope-from sos) Message-Id: <199805262022.WAA00329@sos.freebsd.dk> Subject: ELF preparation step 2 done To: current@FreeBSD.ORG (FreeBSD current) Date: Tue, 26 May 1998 22:22:53 +0200 (CEST) From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just commited part two of the ELF'ifying process. A make world will now leave a system that is no longer using /usr/lib for a.out libraries, they have been moved to /usr/lib/aout. Those that are adventurous can remove all libs & crt files from /usr/lib and they will then have a system that is allmost ready for an ELF world. I will let this whole thing settle for a couble of weeks, before then next (big) step is taken... Enjoy. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 13:49:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17127 for freebsd-current-outgoing; Tue, 26 May 1998 13:49:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-118.joh.za.ibm.net [139.92.122.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17112 for ; Tue, 26 May 1998 13:49:16 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id WAA03686; Tue, 26 May 1998 22:38:11 +0200 (SAT) From: Robert Nordier Message-Id: <199805262038.WAA03686@ceia.nordier.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805261840.MAA07456@mt.sri.com> from Nate Williams at "May 26, 98 12:40:15 pm" To: nate@mt.sri.com (Nate Williams) Date: Tue, 26 May 1998 22:38:09 +0200 (SAT) Cc: eivind@yes.no, nate@mt.sri.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams wrote: > Eivind Eklund writes: > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > > > be much better than GCC when you look at error control etc. > > > > > > Can it do shlibs? > > > > I don't know - is there much special it would have to do? > > Generating PIC code is a big prerequisite, so the assembly it generates > must be capable of being relocated. I'm not 100% sure if this is a > function of the compiler, but given that GCC1 couldn't do it and GCC2 > could, I suspect it's a function of the compiler. TenDRA is capable of generating PIC code. When I initially ported the compiler to FreeBSD, I had this working, but disabled it prior to submitting the code to DERA for the official 4.1.2 release. There are currently some (other) bugs that need sorting out, but this done, I was planning to get PIC support going again. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 13:53:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17970 for freebsd-current-outgoing; Tue, 26 May 1998 13:53:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17959 for ; Tue, 26 May 1998 13:53:02 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id UAA16525; Tue, 26 May 1998 20:52:56 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id WAA17020; Tue, 26 May 1998 22:52:55 +0200 (MET DST) Message-ID: <19980526225254.45152@follo.net> Date: Tue, 26 May 1998 22:52:54 +0200 From: Eivind Eklund To: Amancio Hasty Cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <19980526204032.01510@follo.net> <199805261951.MAA05123@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805261951.MAA05123@rah.star-gate.com>; from Amancio Hasty on Tue, May 26, 1998 at 12:51:08PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 26, 1998 at 12:51:08PM -0700, Amancio Hasty wrote: > Can you run a simple benchmark to see if the compiler is faster than > gcc? For compilation: Yes, I can. For the speed of generated code: Not really. I can test some benchmarks, but they won't really tell the truth. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 13:55:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18412 for freebsd-current-outgoing; Tue, 26 May 1998 13:55:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18405; Tue, 26 May 1998 13:55:12 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id QAA26159; Tue, 26 May 1998 16:55:13 -0400 (EDT) (envelope-from wollman) Date: Tue, 26 May 1998 16:55:13 -0400 (EDT) From: Garrett Wollman Message-Id: <199805262055.QAA26159@khavrinen.lcs.mit.edu> To: Søren Schmidt Cc: current@FreeBSD.ORG Subject: cvs commit: src Makefile src/etc rc src/etc/mtree BSD.usr.dist In-Reply-To: <199805262012.NAA12155@freefall.freebsd.org> References: <199805262012.NAA12155@freefall.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > This will after a make world & reboot give a system that no > longer uses /usr/lib/*, infact one could remove all the old > libraries there, they are not used anymore. Except for all the inconvenient third-party software... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 14:07:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20948 for freebsd-current-outgoing; Tue, 26 May 1998 14:07:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20925; Tue, 26 May 1998 14:07:09 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id XAA27629; Tue, 26 May 1998 23:06:40 +0200 (CEST) (envelope-from sos) Message-Id: <199805262106.XAA27629@sos.freebsd.dk> Subject: Re: cvs commit: src Makefile src/etc rc src/etc/mtree BSD.usr.dist In-Reply-To: <199805262055.QAA26159@khavrinen.lcs.mit.edu> from Garrett Wollman at "May 26, 98 04:55:13 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Tue, 26 May 1998 23:06:40 +0200 (CEST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Garrett Wollman who wrote: > < said: > > > This will after a make world & reboot give a system that no > > longer uses /usr/lib/*, infact one could remove all the old > > libraries there, they are not used anymore. > > Except for all the inconvenient third-party software... Well, there is no real solution for that I'm afraid.. At runtime shared libs wil be resolved via rtld which knows where to look for libs. Systems that rely on libs being in /usr/lib via hard path will fail, ie Makefiles with a wired in hard path, we can then argue to death who is broken... Another story is what we are going to do with /usr/local/lib :( -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 14:38:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25461 for freebsd-current-outgoing; Tue, 26 May 1998 14:38:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25327; Tue, 26 May 1998 14:38:08 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id VAA18120; Tue, 26 May 1998 21:36:25 GMT Date: Wed, 27 May 1998 06:36:25 +0900 (JST) From: Michael Hancock To: "Eric J. Schwertfeger" cc: Alex Povolotsky , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One thing we need to look at is the license. I was working on sendmail 8.9.0 with db-2.0 on SunOS recently and I think I saw some licencing changes in both distributions. The build docs really try hard to steer you into using db-2.0. It worked fine for me. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 14:40:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26133 for freebsd-current-outgoing; Tue, 26 May 1998 14:40:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-121.joh.za.ibm.net [139.92.122.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26018 for ; Tue, 26 May 1998 14:40:17 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id XAA04626; Tue, 26 May 1998 23:31:29 +0200 (SAT) From: Robert Nordier Message-Id: <199805262131.XAA04626@ceia.nordier.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805261749.MAA20256@dyson.iquest.net> from "John S. Dyson" at "May 26, 98 12:49:52 pm" To: toor@dyson.iquest.net (John S. Dyson) Date: Tue, 26 May 1998 23:31:26 +0200 (SAT) Cc: eivind@yes.no, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John S. Dyson wrote: > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > be much better than GCC when you look at error control etc. > > > > Besides, it has the license we've got as a goal to have overall (ie, a > > BSD-style license :-) > > > Interesting idea... I wonder how good it's code generation is (what is > the cost of using it, performance wise???) If it isn't very slow, it > might be a more reliable alternative. I looked at the floating point code generation, specifically, a while ago. This was very agressive (TenDRA optimizes fully by default), though to the extent that values would change, simply due to spilling of a register, and casts were not necessarily honored. Obviously this isn't directly relevant, but probably indicates a high degree of general optimization. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 15:12:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02782 for freebsd-current-outgoing; Tue, 26 May 1998 15:12:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02773 for ; Tue, 26 May 1998 15:12:47 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA18555; Tue, 26 May 1998 22:12:33 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA29678; Wed, 27 May 1998 00:12:31 +0200 (MET DST) Message-ID: <19980527001230.50907@follo.net> Date: Wed, 27 May 1998 00:12:30 +0200 From: Eivind Eklund To: Mike Smith Cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <19980526194334.44185@follo.net> <199805261836.LAA00466@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805261836.LAA00466@dingo.cdrom.com>; from Mike Smith on Tue, May 26, 1998 at 11:36:54AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 26, 1998 at 11:36:54AM -0700, Mike Smith wrote: > > On Tue, May 26, 1998 at 11:59:52AM -0500, John S. Dyson wrote: > > > I really don't think that we would want to also get into compiler > > > support issues. Tool support issues are complex enough. I can imagine > > > that egcs (could) be stable enough for our c++ compiler, but am much > > > less confident of it being our default c compiler. > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > be much better than GCC when you look at error control etc. > > How much of the world will build with it? Very little without custom setup, I suspect. TenDRA is (in the default mode) a pure ANSI compiler, with exact checking against the ANSI API. I think making it support e.g. 'long long' would need modifications of the frontend. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 15:13:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02848 for freebsd-current-outgoing; Tue, 26 May 1998 15:13:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from beast.gu.net (beast-fxp0.gu.net [194.93.191.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02727; Tue, 26 May 1998 15:12:30 -0700 (PDT) (envelope-from stesin@gu.net) Received: from localhost (localhost [127.0.0.1]) by beast.gu.net (8.8.8/8.8.8) with SMTP id BAA23681; Wed, 27 May 1998 01:11:20 +0300 (EEST) (envelope-from stesin@gu.net) Date: Wed, 27 May 1998 01:11:20 +0300 (EEST) From: Andrew Stesin Reply-To: stesin@gu.net To: Michael Hancock cc: "Eric J. Schwertfeger" , Alex Povolotsky , current@FreeBSD.ORG, hackers@FreeBSD.ORG, josh@ican.net Subject: Re: Sendmail 8.9 In-Reply-To: Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 May 1998, Michael Hancock wrote: > One thing we need to look at is the license. I was working on sendmail > 8.9.0 with db-2.0 on SunOS recently and I think I saw some licencing > changes in both distributions. > > The build docs really try hard to steer you into using db-2.0. It worked > fine for me. By the way, BerkeleyDB version in ports is still 2.3.16 as far as I recall, and current version at www.sleepycat.com is db-2.4.10 with 3 patches; 2.3.16 is removed from there. Note: due to the cosmetic but massive changes between 2.3.16 and 2.4.10, 2.4.10 doesn't work at FreeBSD as of today. Best regards, Andrew Stesin nic-hdl: ST73-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 15:18:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04610 for freebsd-current-outgoing; Tue, 26 May 1998 15:18:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04514; Tue, 26 May 1998 15:18:26 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01284; Tue, 26 May 1998 14:12:15 -0700 (PDT) Message-Id: <199805262112.OAA01284@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Hancock cc: "Eric J. Schwertfeger" , Alex Povolotsky , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 In-reply-to: Your message of "Wed, 27 May 1998 06:36:25 +0900." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 14:12:15 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One thing we need to look at is the license. I was working on sendmail > 8.9.0 with db-2.0 on SunOS recently and I think I saw some licencing > changes in both distributions. db-2.0 is bad licensing ju-ju in the default case. If it can't be built to work with 1.8x we may be in trouble. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 15:35:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07956 for freebsd-current-outgoing; Tue, 26 May 1998 15:35:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07885; Tue, 26 May 1998 15:35:36 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.8/8.8.8) with SMTP id PAA22610; Tue, 26 May 1998 15:35:19 -0700 (PDT) (envelope-from ejs@bfd.com) Date: Tue, 26 May 1998 15:35:18 -0700 (PDT) From: "Eric J. Schwertfeger" To: Mike Smith cc: Michael Hancock , Alex Povolotsky , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 In-Reply-To: <199805262112.OAA01284@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 May 1998, Mike Smith wrote: > > One thing we need to look at is the license. I was working on sendmail > > 8.9.0 with db-2.0 on SunOS recently and I think I saw some licencing > > changes in both distributions. > > db-2.0 is bad licensing ju-ju in the default case. If it can't be > built to work with 1.8x we may be in trouble. It compiled cleanly on 2.2.6 for me, without complaining about anything, so I'm assuming that it was working. It does no longer work with db-1.5X and prior, if I remember correctly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 15:42:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09672 for freebsd-current-outgoing; Tue, 26 May 1998 15:42:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09597; Tue, 26 May 1998 15:42:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01464; Tue, 26 May 1998 14:35:34 -0700 (PDT) Message-Id: <199805262135.OAA01464@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Eric J. Schwertfeger" cc: Mike Smith , Michael Hancock , Alex Povolotsky , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 In-reply-to: Your message of "Tue, 26 May 1998 15:35:18 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 14:35:34 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 26 May 1998, Mike Smith wrote: > > > > One thing we need to look at is the license. I was working on sendmail > > > 8.9.0 with db-2.0 on SunOS recently and I think I saw some licencing > > > changes in both distributions. > > > > db-2.0 is bad licensing ju-ju in the default case. If it can't be > > built to work with 1.8x we may be in trouble. > > It compiled cleanly on 2.2.6 for me, without complaining about anything, > so I'm assuming that it was working. It does no longer work with db-1.5X > and prior, if I remember correctly. db-2 works just fine on FreeBSD - that's not the problem. The problem is the *license*. Some time back the relative merits of switching to db-2 were discussed, but the ultimate decision was that the license was not viable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 15:43:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09811 for freebsd-current-outgoing; Tue, 26 May 1998 15:43:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [204.160.242.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09761; Tue, 26 May 1998 15:43:14 -0700 (PDT) (envelope-from ejs@bfd.com) Received: from harlie.bfd.com (bastion.bfd.com [204.160.242.14]) by horst.bfd.com (8.8.8/8.8.8) with SMTP id PAA22728; Tue, 26 May 1998 15:42:58 -0700 (PDT) (envelope-from ejs@bfd.com) Date: Tue, 26 May 1998 15:42:58 -0700 (PDT) From: "Eric J. Schwertfeger" To: Mike Smith cc: Michael Hancock , Alex Povolotsky , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 In-Reply-To: <199805262135.OAA01464@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 May 1998, Mike Smith wrote: > > > db-2.0 is bad licensing ju-ju in the default case. If it can't be > > > built to work with 1.8x we may be in trouble. > > > > It compiled cleanly on 2.2.6 for me, without complaining about anything, > > so I'm assuming that it was working. It does no longer work with db-1.5X > > and prior, if I remember correctly. > > db-2 works just fine on FreeBSD - that's not the problem. The problem > is the *license*. Some time back the relative merits of switching to > db-2 were discussed, but the ultimate decision was that the license was > not viable. Sorry, should have clarified. Sendmail 8.9.0beta5 compiled cleanly on a stock 2.2.6 without asking me to install db-2.0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 16:02:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14855 for freebsd-current-outgoing; Tue, 26 May 1998 16:02:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ian.axess.net (dfe@ian.axess.net [205.247.138.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14784 for ; Tue, 26 May 1998 16:01:57 -0700 (PDT) (envelope-from dfe@ian.axess.net) Received: from localhost (dfe@localhost) by ian.axess.net (8.8.7/8.8.7) with SMTP id TAA02213 for ; Tue, 26 May 1998 19:01:48 -0400 Date: Tue, 26 May 1998 19:01:48 -0400 (EDT) From: Doug Elznic To: freebsd-current@FreeBSD.ORG Subject: which directories? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am interested in testing out the current release. What directories do I need to download. i am trying to burn my own cd and I never found a definitive answer for what directories to grab... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 17:08:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25983 for freebsd-current-outgoing; Tue, 26 May 1998 17:08:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25906 for ; Tue, 26 May 1998 17:08:10 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id RAA06110; Tue, 26 May 1998 17:07:56 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805270007.RAA06110@rah.star-gate.com> To: Eivind Eklund cc: Amancio Hasty , "John S. Dyson" , current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Tue, 26 May 1998 22:52:54 +0200." <19980526225254.45152@follo.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6107.896227676.1@rah.star-gate.com> Date: Tue, 26 May 1998 17:07:56 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since, most of the time over here all I do is compile this or compile that makes me interested on the speed of the compiler . for instance, if it can speed up make world that would be great and it the compiler generates decent code all the much better. For selected applications I am very interested on the code generation . Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 19:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22773 for freebsd-current-outgoing; Tue, 26 May 1998 19:44:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22756; Tue, 26 May 1998 19:44:17 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA06654; Tue, 26 May 1998 19:44:17 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805270244.TAA06654@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sos@FreeBSD.ORG cc: current@FreeBSD.ORG (FreeBSD current) Subject: Re: ELF preparation step 2 done In-reply-to: Your message of "Tue, 26 May 1998 22:22:53 +0200." <199805262022.WAA00329@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 19:44:16 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tnks a lot! Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 19:58:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25649 for freebsd-current-outgoing; Tue, 26 May 1998 19:58:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25644 for ; Tue, 26 May 1998 19:58:36 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.48.34]) by mailman.cs.ucla.edu (8.8.8/UCLACS-4.0) with ESMTP id TAA13754 for ; Tue, 26 May 1998 19:58:35 -0700 (PDT) Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id TAA00291 for freebsd-current@freebsd.org; Tue, 26 May 1998 19:58:35 -0700 (PDT) (envelope-from scottm) Date: Tue, 26 May 1998 19:58:35 -0700 (PDT) From: Scott Michel Message-Id: <199805270258.TAA00291@mordred.cs.ucla.edu> To: freebsd-current@FreeBSD.ORG Subject: MSDOSFS question/bug? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's what my partitioning looks like: - sd0s1: MSDOS primary - sd0s2: FreeBSD - sd0s3: MSDOS ext (I split the MSDOS primary in twain at one point after installing FreeBSD, another can 'o worms, but eventually I got back on track.) My problem is that pmp->pm_Heads and pmp->pm_SecPerTrack = 0 for the extended partition, which causes the kernel to not want to mount the partition. Question: How do I go about fixing FreeBSD (if possible) or the DOS partition data w/o wiping out the FreeBSD disklabel? -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 20:24:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02383 for freebsd-current-outgoing; Tue, 26 May 1998 20:24:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from m2.findmail.com (m2.findmail.com [209.185.96.135]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA02357 for ; Tue, 26 May 1998 20:24:29 -0700 (PDT) (envelope-from brianfeldman@hotmail.com) Received: (qmail 16264 invoked by uid 505); 27 May 1998 03:23:29 -0000 Date: 27 May 1998 03:23:29 -0000 Message-ID: <19980527032329.16263.qmail@m2.findmail.com> From: "Brian Feldman" Subject: current instabilities To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 1) Heads up Julian, Luoqi, it took an amazing 6 days but SoftUpdates FINALLY crashed during a make -j4 world; the panic was dangling deps, but I didn't save the core, so I lost it, besides the fact I'm sure vmcore's from SoftUpdates crashes aren't in short supply ;) But good job guys, you've got it stable enough to stay up almost a week 2) "options VM86" - EVIL EVIL EVIL! This really allows way too much access to the memory by a mortal, and it's an effective DoS attack if a user runs doscmd, say, and a certain executable (this time, I happened to try ZSnes). Think there may be a way to make this safer? (I locked myself up, and it didn't panic so I don't know what exact function caused it). Also, could USER_LDT possibly be used as a DoS attack, like it seems to me it could? Cheers, Brian Feldman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 20:36:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04467 for freebsd-current-outgoing; Tue, 26 May 1998 20:36:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04362 for ; Tue, 26 May 1998 20:35:39 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id UAA17413 for ; Tue, 26 May 1998 20:30:59 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd017409; Wed May 27 03:30:51 1998 Message-ID: <356B88E7.ABD322C@whistle.com> Date: Tue, 26 May 1998 20:30:47 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: possible breakage (objformat.c) in -current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This new file (why does it have to be compiled at install time?) fails to compile here because CFLAGS at install-time contains -nostdinc which means that it can't find any include files. Thus make installworld fails. I've looked to see if the -nostdinc is a local feature but it doesn't appear to be so. My quick workaround is to add CFLAGS= to the Makefile to get rif of incoming values. Anyone else see this? I see no reason why this couldn't be build at built at make time, as it only gets it's default behaviour from that, and you could just as easily check it in with the default behaviour you want as check the default behaviour into the Makefile. That way it'd at least compile :-) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 20:57:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09203 for freebsd-current-outgoing; Tue, 26 May 1998 20:57:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dfw-ix10.ix.netcom.com (dfw-ix10.ix.netcom.com [206.214.98.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09071 for ; Tue, 26 May 1998 20:56:57 -0700 (PDT) (envelope-from sherwink@ix.netcom.com) Received: (from smap@localhost) by dfw-ix10.ix.netcom.com (8.8.4/8.8.4) id WAA19985; Tue, 26 May 1998 22:55:31 -0500 (CDT) Received: from scz-ca6-03.ix.netcom.com(199.182.129.195) by dfw-ix10.ix.netcom.com via smap (V1.3) id rma019975; Tue May 26 22:55:15 1998 Date: Tue, 26 May 1998 20:55:20 -0700 (PDT) From: Sherwin X-Sender: sherwin@doorstop.ix.netcom.com To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: sio and dk440lx In-Reply-To: <199805260701.AAA00753@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running 2.2.5 on the Atlanta. I had no problems with the serial ports. Just FYI, there is a register conflict with the board and the S3 Trio 64 qnd S3 Virge families of video chipsets. The problem is documented in the FAQ for the board on the Intel Website. I got freezes in X, until I switched to an ATI Xpression. Since then, the machine has had a problem-free uptime of 50 days, and still going. Good luck! -------------------------------------------------------------------------- On Tue, 26 May 1998, Mike Smith wrote: > > Hi again, > > my serial ports don't seem to want to work. > > > > According to the intel docs, com1&2 should be at 0x3f8 and 0x2f8 respectively. > > Dmesg says sio0 not found at 0x3f8, sio1 not found at 0x2f8. > > The DK440LX ('Atlanta') board is believed to work just fine. > > > Anyone have an idea why not? > > You may have disabled the ports in the BIOS setup. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 21:26:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15946 for freebsd-current-outgoing; Tue, 26 May 1998 21:26:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from puck.nether.net (jared@puck.nether.net [204.42.254.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15726 for ; Tue, 26 May 1998 21:24:34 -0700 (PDT) (envelope-from jared@puck.nether.net) Received: (from jared@localhost) by puck.nether.net (8.9.0/8.7.3) id AAA04201; Wed, 27 May 1998 00:24:15 -0400 Message-ID: <19980527002414.A3954@puck.nether.net> Date: Wed, 27 May 1998 00:24:14 -0400 From: Jared Mauch To: freebsd-current@FreeBSD.ORG Subject: kernel panics.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a program that i can use to panic the kernel consistently that just does a lot of FD I/O w/ the network. I don't have the ability nor familiarity w/ the kernel internals to hack source. Anyone want the source for my program that nukes the system? :) It causes some mbuf related crash... here's the message it prints on the console of the box: Out of mbuf clusters - increase maxusers! Then it does this: Fatal trap 12: page fault while in kernel mode mp_lock = 0100000002; cpuid = 1; lapic.id = 01000000 fault virtual address = 0x18 fault code = supervisor write, page not present instruction pointer = 0x8:0xf0128571 stack pointer = 0x10:0xf49ecec8 frame pointer = 0x10:0xf49ecee8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 180 (sshd1) interrupt mask = <- SMP: XXX kernel: type 12 trap, code=0 stopped at _sosend+0x301: movl $0,0x18(%ebx) previous crashes included (instead of sshd) my program causing the system to puke I've had this problem with other systems that are not SMP also. Anything that I can provide to help? let me know. - jared To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 21:29:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16916 for freebsd-current-outgoing; Tue, 26 May 1998 21:29:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16688 for ; Tue, 26 May 1998 21:28:46 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id VAA26084; Tue, 26 May 1998 21:28:31 -0700 (PDT) (envelope-from jdp) Message-Id: <199805270428.VAA26084@austin.polstra.com> To: kpielorz@tdx.co.uk Subject: Re: Error building 'cvsup' on 3.0-CURRENT as of 24th May,1998 In-Reply-To: <356AA564.915D1F14@tdx.co.uk> References: <356AA564.915D1F14@tdx.co.uk> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 26 May 1998 21:28:31 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <356AA564.915D1F14@tdx.co.uk>, Karl Pielorz wrote: > Is there any other way of getting cvsup, cvsupd etc. on the system ( I know > theres a 'binary' version of cvsup - but it doesn't seem to include the > server components)... ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsupd-bin-15.4.tar.gz (server) ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsup-bin-15.4.tar.gz (client) ftp://ftp.freebsd.org/pub/FreeBSD/CVSup/cvsup.nogui-bin-15.4.tar.gz (client without GUI) -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 21:31:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17268 for freebsd-current-outgoing; Tue, 26 May 1998 21:31:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17012; Tue, 26 May 1998 21:30:08 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id MAA00351; Wed, 27 May 1998 12:29:52 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805270429.MAA00351@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: sos@FreeBSD.ORG cc: current@FreeBSD.ORG (FreeBSD current) Subject: Re: ELF preparation step 2 done In-reply-to: Your message of "Tue, 26 May 1998 22:22:53 +0200." <199805262022.WAA00329@sos.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Wed, 27 May 1998 12:29:51 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S ren Schmidt wrote: > = > I have just commited part two of the ELF'ifying process. > = > A make world will now leave a system that is no longer using /usr/lib > for a.out libraries, they have been moved to /usr/lib/aout. > Those that are adventurous can remove all libs & crt files from > /usr/lib and they will then have a system that is allmost ready for > an ELF world. > = > I will let this whole thing settle for a couble of weeks, before then > next (big) step is taken... = Just as a BTW for people watching from the side, I have been running a pure-elf -current system for nearly a year. The system is completely functional and can generate and run both a.out and elf executables (share= d and dynamic) at the drop of a hat. All that is really missing is a 3 stage boot so that we can squeeze in co= de for loading the elf symbol table on an elf kernel. Presently the BAD144 support has to go to make room, since there are *zero* bytes free at the = moment. I've been using both elf and a.out kernels over the last year, = a.out kernels are needed for ddb's symbol functions at present. Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 21:53:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21343 for freebsd-current-outgoing; Tue, 26 May 1998 21:53:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from asteroid.svib.ru (root@asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21090 for ; Tue, 26 May 1998 21:51:43 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.8.8/8.8.8) with ESMTP id IAA03008; Wed, 27 May 1998 08:51:22 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from minas-tirith.pol.ru (minas-tirith.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.8/8.8.7) with ESMTP id IAA02859; Wed, 27 May 1998 08:51:24 +0400 (MSD) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199805270451.IAA02859@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.2 2/24/98 To: Eivind Eklund Cc: current@FreeBSD.ORG Subject: TenDRA C++ In-reply-to: Your message "Tue, 26 May 1998 19:43:34 +0200." <19980526194334.44185@follo.net> Reply-To: tarkhil@asteroid.svib.ru X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 08:51:22 +0400 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG <19980526194334.44185@follo.net>Eivind Eklund writes: >Personally I'd prefer to use TenDRA if at all possible. It seems to >be much better than GCC when you look at error control etc. I've tried to compile Qt with TenDRA, and got more errors than I've got earlier this year at all ;-) Looks like TenDRA has SOMETHING very different from GCC inside it. Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 21:53:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21392 for freebsd-current-outgoing; Tue, 26 May 1998 21:53:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20465; Tue, 26 May 1998 21:48:44 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id MAA00317; Wed, 27 May 1998 12:24:05 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805270424.MAA00317@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: "Eric J. Schwertfeger" , Michael Hancock , Alex Povolotsky , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 In-reply-to: Your message of "Tue, 26 May 1998 14:35:34 MST." <199805262135.OAA01464@dingo.cdrom.com> Date: Wed, 27 May 1998 12:24:04 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > On Tue, 26 May 1998, Mike Smith wrote: > > > > > > One thing we need to look at is the license. I was working on sendmail > > > > 8.9.0 with db-2.0 on SunOS recently and I think I saw some licencing > > > > changes in both distributions. > > > > > > db-2.0 is bad licensing ju-ju in the default case. If it can't be > > > built to work with 1.8x we may be in trouble. > > > > It compiled cleanly on 2.2.6 for me, without complaining about anything, > > so I'm assuming that it was working. It does no longer work with db-1.5X > > and prior, if I remember correctly. > > db-2 works just fine on FreeBSD - that's not the problem. The problem > is the *license*. Some time back the relative merits of switching to > db-2 were discussed, but the ultimate decision was that the license was > not viable. There are problems with the sendmail license too. There are some wording problems that make it ambiguous, and one interpretation makes it far worse than some of the restrictions in the GPL. For starters: - the scope of "distribution" and "the complete source code" are not defined. One interpretation is that it covers distribution of sendmail and the source to sendmail, on the other end of the scale it could mean the *entire* system, including OS, any proprietary components etc. - there is no time limit to the 'irrevokable offer to provide source code' at cost (in the case of for-profit binary distributions). At least the GPL has an upper limit of 3 years here, and even that's a rather long time.. especially if you *loose* the source somehow or have legal restrictions (eg: the USL lawsuit settlement that prevented any more freebsd-1.x CD distributions going out from WC). These are not practical problems that anybody is going to be faced with yet, since everybody that I know of that distributes FreeBSD at present does so with source, (at least those that use sendmail, anyway). However, there are now some companies that use FreeBSD embedded within the product or hardware, so it's not something that we can take for granted. Moving it to src/contrib might be a safer way since it's going to be part of the system that would need to be carefully scrutinized or jetisoned in some situations. Before everybody jumps up and says "use xyzmail[er] instead" or "just don't ship anything in the base", I'm not sure that we can do that as parts of the base *assume* that sendmail (or a workalike) is present. Maybe it's time to bring back a basic local-only mail transport that gets blown away when a real sendmail or comparable (qmail, smail, vmailer, exim, etc etc) gets installed from a port. Sigh. Anyway, things would be helped a lot if the Sendmail, Inc folks would clarify the scope of the license. If there's no danger to co-shipped proprietary code, then it can go in. Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 22:28:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29185 for freebsd-current-outgoing; Tue, 26 May 1998 22:28:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29111; Tue, 26 May 1998 22:28:06 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA00675; Tue, 26 May 1998 22:28:04 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805270528.WAA00675@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sos@FreeBSD.ORG cc: current@FreeBSD.ORG (FreeBSD current) Subject: Re: ELF preparation step 2 done In-reply-to: Your message of "Tue, 26 May 1998 22:22:53 +0200." <199805262022.WAA00329@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 May 1998 22:28:04 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just cvsuped the system a couple of hours ago , did a make world , wiped out my /usr/lib 8) ls -ald /usr/lib/* drwxr-xr-x 2 bin bin 2560 May 26 21:43 /usr/lib/aout drwxr-xr-x 2 bin bin 512 May 26 21:36 /usr/lib/compat Cool, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 23:19:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08893 for freebsd-current-outgoing; Tue, 26 May 1998 23:19:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08853; Tue, 26 May 1998 23:19:29 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id IAA00329; Wed, 27 May 1998 08:19:17 +0200 (CEST) (envelope-from sos) Message-Id: <199805270619.IAA00329@sos.freebsd.dk> Subject: Re: ELF preparation step 2 done In-Reply-To: <199805270528.WAA00675@rah.star-gate.com> from Amancio Hasty at "May 26, 98 10:28:04 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 27 May 1998 08:19:17 +0200 (CEST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Amancio Hasty who wrote: > Just cvsuped the system a couple of hours ago , did a make world , > wiped out my /usr/lib 8) > > ls -ald /usr/lib/* > drwxr-xr-x 2 bin bin 2560 May 26 21:43 /usr/lib/aout > drwxr-xr-x 2 bin bin 512 May 26 21:36 /usr/lib/compat > > Cool, > Amancio Yup, thats what intended :), its now verified that it works on other than my 3 development machines currently dedicated to this. Well, we've worked long on this, we being John Polstra, Peter Wemm and myself, we have been running systems totally ELF for over a year now, I think my first patches was dated back in september 1996 :) Oh well, we havn't had the time to pull it off, until now when I decided to "just do it", the other times it allways died out in some fancy technical discussion on how to do things. I having a week of vacation now, lets use that period to have the dust settle, then I plan to take the next big step, taking userland into a complete ELF world, its all planned for. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 23:20:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09067 for freebsd-current-outgoing; Tue, 26 May 1998 23:20:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09013 for ; Tue, 26 May 1998 23:20:16 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0/frmug-2.3/nospam) with UUCP id IAA17626 for current@FreeBSD.ORG; Wed, 27 May 1998 08:20:09 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id IAA19975 for current@FreeBSD.ORG; Wed, 27 May 1998 08:15:40 +0200 (CEST) (envelope-from roberto) Message-ID: <19980527081540.A19950@keltia.freenix.fr> Date: Wed, 27 May 1998 08:15:40 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning Mail-Followup-To: current@FreeBSD.ORG References: <19980526194334.44185@follo.net> <199805261836.LAA00466@dingo.cdrom.com> <19980527001230.50907@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.3i In-Reply-To: <19980527001230.50907@follo.net>; from Eivind Eklund on Wed, May 27, 1998 at 12:12:30AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4311 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Eivind Eklund: > I think making it support e.g. 'long long' would need modifications of > the frontend. lcc, now at 4.0, still has the same problem I think. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #60: Fri May 15 21:04:22 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 23:33:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11452 for freebsd-current-outgoing; Tue, 26 May 1998 23:33:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11422 for ; Tue, 26 May 1998 23:33:37 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id IAA00384; Wed, 27 May 1998 08:33:23 +0200 (CEST) (envelope-from sos) Message-Id: <199805270633.IAA00384@sos.freebsd.dk> Subject: Re: possible breakage (objformat.c) in -current In-Reply-To: <356B88E7.ABD322C@whistle.com> from Julian Elischer at "May 26, 98 08:30:47 pm" To: julian@whistle.com (Julian Elischer) Date: Wed, 27 May 1998 08:33:23 +0200 (CEST) Cc: current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Julian Elischer who wrote: > This new file (why does it have to be compiled at install time?) > fails to compile here because > CFLAGS at install-time contains -nostdinc which means that > it can't find any include files. Thus make installworld fails. Nope not seen that, I'll check.... > I've looked to see if the -nostdinc is a local feature but it > doesn't appear to be so. > > My quick workaround is to add CFLAGS= > to the Makefile to get rif of incoming values. > > I see no reason why this couldn't be build at built at > make time, as it only gets it's default behaviour from > that, and you could just as easily check it in with the > default behaviour you want as check the default behaviour > into the Makefile. Peter left in a way to do it via OBJFORMAT_PATH, but I couldn't get it to work right. The problem is that you need one path "/usr/obj/usr/src/tmp" build in when you do the buildworld, or the buildowrld process cannot find ar, as, ld etc, then when you go to the install fase, it needs the "real" path /usr/lib build in instead, if you just install the buildworld verison then it fails. You could try to patch it back to its original to see if it works for you that way, and add: OBJFORMAT_PATH=${WORLDTMP}/usr/libexec to COMPILER_ENV, thats the way Peter intended it to be, but for unknown reasons it failed when I tried to update a pure just fresh installed SNAP, whereas the method I hacked (yes its ugly) worked on all my test platforms... I'll try to get time and test this out today, and commit it if I get it to work... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 23:42:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12890 for freebsd-current-outgoing; Tue, 26 May 1998 23:42:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12822; Tue, 26 May 1998 23:41:35 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id OAA01119; Wed, 27 May 1998 14:41:24 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805270641.OAA01119@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: sos@FreeBSD.ORG cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG Subject: Re: cvs commit: src Makefile src/etc rc src/etc/mtree BSD.usr.dist In-reply-to: Your message of "Tue, 26 May 1998 23:06:40 +0200." <199805262106.XAA27629@sos.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Wed, 27 May 1998 14:41:24 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG S ren Schmidt wrote: > In reply to Garrett Wollman who wrote: > > < = said: > > = > > > This will after a make world & reboot give a system that no > > > longer uses /usr/lib/*, infact one could remove all the old > > > libraries there, they are not used anymore. > > = > > Except for all the inconvenient third-party software... > = > Well, there is no real solution for that I'm afraid.. > = > At runtime shared libs wil be resolved via rtld which knows > where to look for libs. Yes, this really isn't a problem.. Both the a.out ld itself and ld.so = know to look in /usr/lib/aout. Old programs will still work just as = before. The only thing that will have trouble is stuff that wants to do a 'nm /us= r/ lib/libc.a' to detect if a system has a given function. In any case, = programs that do this are pretty limited these days (autoconf tests = properly, it's only the old metaconfig stuff that is likely to have = trouble, and even then those config systems allow the location of libc an= d = the commands to get the name list to be configured at config time). > Systems that rely on libs being in /usr/lib via hard path will > fail, ie Makefiles with a wired in hard path, we can then argue > to death who is broken... > = > Another story is what we are going to do with /usr/local/lib :( This is true. It's going to be fun doing plists since ELF and a.out have= = got different versioning strategies.. (elf has a library and a symlink, = while a.out uses libraries and a combination of ldconfig caching and = runtime directory scanning) Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue May 26 23:57:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15991 for freebsd-current-outgoing; Tue, 26 May 1998 23:57:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15906; Tue, 26 May 1998 23:57:01 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id XAA01063; Tue, 26 May 1998 23:56:58 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805270656.XAA01063@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sos@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: Re: ELF preparation step 2 done In-reply-to: Your message of "Wed, 27 May 1998 08:19:17 +0200." <199805270619.IAA00329@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 26 May 1998 23:56:58 -0700 From: Amancio Hasty Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA15924 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Enjoy your vacation . I am going to be busy shooting myself on foot 8) cc -fpic -DPIC -O -pipe -elf -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -elf -D__DBINTERFACE_PRIVATE -D_NLIST_DO_ELF -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -c /usr/src/lib/libc/../libc/gen/arc4random.c -o arc4random.so Cheers, Amancio > In reply to Amancio Hasty who wrote: > > Just cvsuped the system a couple of hours ago , did a make world , > > wiped out my /usr/lib 8) > > > > ls -ald /usr/lib/* > > drwxr-xr-x 2 bin bin 2560 May 26 21:43 /usr/lib/aout > > drwxr-xr-x 2 bin bin 512 May 26 21:36 /usr/lib/compat > > > > Cool, > > Amancio > > Yup, thats what intended :), its now verified that it works on other > than my 3 development machines currently dedicated to this. > > Well, we've worked long on this, we being John Polstra, Peter Wemm and > myself, we have been running systems totally ELF for over a year now, > I think my first patches was dated back in september 1996 :) > > Oh well, we havn't had the time to pull it off, until now when I > decided to "just do it", the other times it allways died out in > some fancy technical discussion on how to do things. > > I having a week of vacation now, lets use that period to have > the dust settle, then I plan to take the next big step, taking > userland into a complete ELF world, its all planned for. > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end > .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 00:04:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17506 for freebsd-current-outgoing; Wed, 27 May 1998 00:04:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA17374; Wed, 27 May 1998 00:03:58 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id JAA06331; Wed, 27 May 1998 09:03:49 +0200 (CEST) (envelope-from sos) Message-Id: <199805270703.JAA06331@sos.freebsd.dk> Subject: Re: ELF preparation step 2 done In-Reply-To: <199805270656.XAA01063@rah.star-gate.com> from Amancio Hasty at "May 26, 98 11:56:58 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 27 May 1998 09:03:49 +0200 (CEST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Amancio Hasty who wrote: > Enjoy your vacation . I am going to be busy shooting myself on foot 8) > cc -fpic -DPIC -O -pipe -elf -DLIBC_RCS -DSYSLIBC_RCS > -I/usr/src/lib/libc/include -elf -D__DBINTERFACE_PRIVATE -D_NLIST_DO_ELF > -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -c > /usr/src/lib/libc/../libc/gen/arc4random.c -o arc4random.so OK, if you intend to run ELF all over you should set BINFORMAT=elf in make.conf and OBJFORMAT=elf in either the environment or better in /etc/objformat. I'm not sure this is going to get through a make world yet, it did once, but Bruce has been tampering heavily with the makefiles since then... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 00:32:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22880 for freebsd-current-outgoing; Wed, 27 May 1998 00:32:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA22806 for ; Wed, 27 May 1998 00:31:52 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 10364 invoked from network); 27 May 1998 07:31:48 -0000 Received: from userb140.uk.uudial.com (HELO jfsebastian) (193.149.71.123) by smtp.dial.pipex.com with SMTP; 27 May 1998 07:31:48 -0000 Message-ID: <001c01bd8940$e20591d0$0242000a@jfsebastian.k2c.co.uk> From: "Pierre Y. Dampure" To: "Julian Elischer" , Subject: Re: possible breakage (objformat.c) in -current Date: Wed, 27 May 1998 08:27:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian, I just finished a make world on -current (CVSupped from around 05:00 BST) and I didn't have any problems with objformat. Any particularity in your make world? Best Regards, Pierre Y. -----Original Message----- From: Julian Elischer To: current@FreeBSD.ORG Date: 27 May 1998 07:25 Subject: possible breakage (objformat.c) in -current >This new file (why does it have to be compiled at install time?) >fails to compile here because >CFLAGS at install-time contains -nostdinc which means that >it can't find any include files. Thus make installworld fails. > >I've looked to see if the -nostdinc is a local feature but it >doesn't appear to be so. > >My quick workaround is to add CFLAGS= >to the Makefile to get rif of incoming values. > >Anyone else see this? > >I see no reason why this couldn't be build at built at >make time, as it only gets it's default behaviour from >that, and you could just as easily check it in with the >default behaviour you want as check the default behaviour >into the Makefile. > >That way it'd at least compile :-) > > >julian > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 00:36:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23470 for freebsd-current-outgoing; Wed, 27 May 1998 00:36:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23335; Wed, 27 May 1998 00:35:07 -0700 (PDT) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id JAA18392; Wed, 27 May 1998 09:31:38 +0200 (CEST) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199805270731.JAA18392@ocean.campus.luth.se> Subject: Re: ELF preparation step 2 done In-Reply-To: <199805262022.WAA00329@sos.freebsd.dk> from =?ISO-8859-1?Q?S=F8ren_Schmidt?= at "May 26, 98 10:22:53 pm" To: sos@FreeBSD.ORG Date: Wed, 27 May 1998 09:31:38 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Søren Schmidt: > > I have just commited part two of the ELF'ifying process. > > A make world will now leave a system that is no longer using /usr/lib > for a.out libraries, they have been moved to /usr/lib/aout. > Those that are adventurous can remove all libs & crt files from > /usr/lib and they will then have a system that is allmost ready for > an ELF world. > > I will let this whole thing settle for a couble of weeks, before then > next (big) step is taken... Cool. Will the ELF libs go into /usr/lib/elf/ or is the reason that a.out libs are moved that we want to put ELF libs in /usr/lib since that's the way of the future, and a.out libs will be there just for compability after a while? Also a more general question about ELF and FreeBSD. Do we allow for an easy way to distinguish a FreeBSD ELF binary from other binaries, no matter if it's static or dymanic, or whatever? I'm thinking about the problems that we have emulating Linux static ELF binaries without "brandelf"-ing them first, and thought that it would be bad to put other OSes in the same position when they try to emulate FreeBSD. Also FreeBSD wants to know it's fed a FreeBSD binary for sure, and not an unknown ELF binary, when it's asked to run something. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 01:03:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27953 for freebsd-current-outgoing; Wed, 27 May 1998 01:03:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27851; Wed, 27 May 1998 01:03:29 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id KAA17092; Wed, 27 May 1998 10:03:10 +0200 (CEST) (envelope-from sos) Message-Id: <199805270803.KAA17092@sos.freebsd.dk> Subject: Re: ELF preparation step 2 done In-Reply-To: <199805270731.JAA18392@ocean.campus.luth.se> from Mikael Karpberg at "May 27, 98 09:31:38 am" To: karpen@ocean.campus.luth.se (Mikael Karpberg) Date: Wed, 27 May 1998 10:03:09 +0200 (CEST) Cc: sos@FreeBSD.ORG, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Mikael Karpberg who wrote: > > Will the ELF libs go into /usr/lib/elf/ or is the reason that a.out > libs are moved that we want to put ELF libs in /usr/lib since that's > the way of the future, and a.out libs will be there just for compability > after a while? ELF will go into /usr/lib, /usr/lib/aout is for backward compat. > Also a more general question about ELF and FreeBSD. Do we allow for an > easy way to distinguish a FreeBSD ELF binary from other binaries, no > matter if it's static or dymanic, or whatever? I'm thinking about the > problems that we have emulating Linux static ELF binaries without > "brandelf"-ing them first, and thought that it would be bad to put other > OSes in the same position when they try to emulate FreeBSD. Also FreeBSD > wants to know it's fed a FreeBSD binary for sure, and not an unknown ELF > binary, when it's asked to run something. The tools does the "branding" on the fly so we know that it is our binary. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 01:14:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00411 for freebsd-current-outgoing; Wed, 27 May 1998 01:14:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00314 for ; Wed, 27 May 1998 01:13:38 -0700 (PDT) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id MAA14339; Wed, 27 May 1998 12:05:02 +0400 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id MAA01740; Wed, 27 May 1998 12:07:56 +0400 (MSD) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199805270807.MAA01740@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Scott Michel Cc: freebsd-current@FreeBSD.ORG Subject: Re: MSDOSFS question/bug? In-reply-to: Your message of "Tue, 26 May 1998 19:58:35 PDT." <199805270258.TAA00291@mordred.cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 12:07:56 +0400 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Michel wrote: > Here's what my partitioning looks like: > > - sd0s1: MSDOS primary > - sd0s2: FreeBSD > - sd0s3: MSDOS ext > > My problem is that pmp->pm_Heads and pmp->pm_SecPerTrack = 0 for the > extended partition, which causes the kernel to not want to mount the > partition. You certainly should mount sd0s5, not sd0s3. It is probably a FAQ. Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 01:32:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03946 for freebsd-current-outgoing; Wed, 27 May 1998 01:32:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA03885 for ; Wed, 27 May 1998 01:32:06 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 23297 invoked from network); 27 May 1998 08:32:00 -0000 Received: from userk473.uk.uudial.com (HELO jfsebastian) (193.149.70.49) by smtp.dial.pipex.com with SMTP; 27 May 1998 08:32:00 -0000 Message-ID: <004601bd8949$4b195050$0242000a@jfsebastian.k2c.co.uk> From: "Pierre Y. Dampure" To: Subject: ELF Step 2 Date: Wed, 27 May 1998 09:26:40 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0043_01BD8951.8DCD9A20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0043_01BD8951.8DCD9A20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable After a make world on -current 05:00 BST : - cannot login; sorted out by booting single user and changing the = password; it seems the system switched from DES to MD5 (verified by = checking at the symbolic links) -- why? - ppp cannot load the alias library, because the path is hardcoded in = /usr/src/usr.sbin/ppp/loadalias.c Me thinks it's time to grep the source tree for hardcoded paths... Best Regards, Pierre Y. ------=_NextPart_000_0043_01BD8951.8DCD9A20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
After a make world on -current 05:00 BST = :
 
- cannot login; sorted out by booting single user = and changing=20 the password; it seems the system switched from DES to MD5 (verified by = checking=20 at the symbolic links) -- why?
 
- ppp cannot load the alias library, because the = path is=20 hardcoded in /usr/src/usr.sbin/ppp/loadalias.c
 
Me thinks it's time to grep the source tree for = hardcoded=20 paths...
 
 
Best Regards,
 
 
Pierre Y.
------=_NextPart_000_0043_01BD8951.8DCD9A20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 02:01:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08465 for freebsd-current-outgoing; Wed, 27 May 1998 02:01:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from comp.polyu.edu.hk (csns02.comp.polyu.edu.hk [158.132.25.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA08453 for ; Wed, 27 May 1998 02:01:50 -0700 (PDT) (envelope-from c5666305@comp.polyu.edu.hk) Received: from cssolar82.COMP.HKP.HK by comp.polyu.edu.hk (SMI-8.6/SMI-SVR4) id RAA15374; Wed, 27 May 1998 17:01:31 +0800 Received: (from c5666305@localhost) by cssolar82.COMP.HKP.HK (SMI-8.6/) id RAA04026 for freebsd-current@freebsd.org; Wed, 27 May 1998 17:01:31 +0800 Message-Id: <199805270901.RAA04026@cssolar82.COMP.HKP.HK> Subject: where can I find the fig2dev for xfig3.2 To: freebsd-current@FreeBSD.ORG Date: Wed, 27 May 1998 17:01:30 +0800 (HKT) From: "c5666305" X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I need fig2dev 3.2 for xfig 3.2 and I cannot find it under ftp.FreeBSD.org. Can anyone tell me where can I get it ? Thanks. Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 02:20:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11122 for freebsd-current-outgoing; Wed, 27 May 1998 02:20:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11007; Wed, 27 May 1998 02:20:09 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id CAA01664; Wed, 27 May 1998 02:20:06 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805270920.CAA01664@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: sos@FreeBSD.ORG cc: karpen@ocean.campus.luth.se (Mikael Karpberg), current@FreeBSD.ORG Subject: Re: ELF preparation step 2 done In-reply-to: Your message of "Wed, 27 May 1998 10:03:09 +0200." <199805270803.KAA17092@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 02:20:06 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any way of converting a a.out library to elf? I am mostly thinking about my motif libraries. Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 02:28:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13057 for freebsd-current-outgoing; Wed, 27 May 1998 02:28:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13034 for ; Wed, 27 May 1998 02:28:32 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id LAA17320; Wed, 27 May 1998 11:28:19 +0200 (CEST) (envelope-from sos) Message-Id: <199805270928.LAA17320@sos.freebsd.dk> Subject: Re: possible breakage (objformat.c) in -current In-Reply-To: <001c01bd8940$e20591d0$0242000a@jfsebastian.k2c.co.uk> from "Pierre Y. Dampure" at "May 27, 98 08:27:18 am" To: pierre.dampure@k2c.co.uk (Pierre Y. Dampure) Date: Wed, 27 May 1998 11:28:18 +0200 (CEST) Cc: julian@whistle.com, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Pierre Y. Dampure who wrote: > Julian, > > I just finished a make world on -current (CVSupped from around 05:00 BST) > and I didn't have any problems with objformat. Any particularity in your > make world? I have just reverted objformat back to its original usage, it works here (suddenly again, I dont know why), and it shouldn't have this problem, infact its much cleaner... > > Best Regards, > > Pierre Y. > > -----Original Message----- > From: Julian Elischer > To: current@FreeBSD.ORG > Date: 27 May 1998 07:25 > Subject: possible breakage (objformat.c) in -current > > > >This new file (why does it have to be compiled at install time?) > >fails to compile here because > >CFLAGS at install-time contains -nostdinc which means that > >it can't find any include files. Thus make installworld fails. > > > >I've looked to see if the -nostdinc is a local feature but it > >doesn't appear to be so. > > > >My quick workaround is to add CFLAGS= > >to the Makefile to get rif of incoming values. > > > >Anyone else see this? > > > >I see no reason why this couldn't be build at built at > >make time, as it only gets it's default behaviour from > >that, and you could just as easily check it in with the > >default behaviour you want as check the default behaviour > >into the Makefile. > > > >That way it'd at least compile :-) > > > > > >julian > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 02:34:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14838 for freebsd-current-outgoing; Wed, 27 May 1998 02:34:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from door.bzw.com (www.barclayscapital.com [194.205.158.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14783 for ; Wed, 27 May 1998 02:34:05 -0700 (PDT) (envelope-from Pierre.Dampure@barclayscapital.com) Received: (from mailman@localhost) by door.bzw.com (8.8.8/8.8.7) id KAA23220 for ; Wed, 27 May 1998 10:32:59 +0100 (BST) Received: from gate.bzw.com(194.205.158.68) by door.bzw.com via smap (V2.0) id xma023182; Wed, 27 May 98 10:32:45 +0100 Received: (from nobody@localhost) by gate.bzw.com (8.8.7/8.8.7) id KAA20127 for ; Wed, 27 May 1998 10:33:46 +0100 (BST) Received: from fwgw01-dmz(194.205.158.129) by gate.bzw.com via smap (V2.0) id xma020094; Wed, 27 May 98 10:33:43 +0100 Received: (from nobody@localhost) by fwgw01.ldn.bzwint.com (8.8.7/8.8.7) id KAA16982 for ; Wed, 27 May 1998 10:33:41 +0100 (BST) Received: from oplss0001.itops.ldn.bzwint.com(30.75.1.4) by fwgw01.ldn.bzwint.com via smap (V2.0) id xma016953; Wed, 27 May 98 10:33:39 +0100 Received: from nmb01gw01 (smtphost.ldn.bzwint.com [30.10.1.10]) by oplss0001.itops.ldn.bzwint.com (8.8.7/8.8.6) with SMTP id KAA10925 for ; Wed, 27 May 1998 10:33:11 +0100 (BST) Received: from exintgw02.itops.ldn.bzwint.com (exintgw02.itops.ldn.bzwint.com [30.45.1.87]) by nmb01gw01 (NTMail 3.02.13) with ESMTP id fa688407 for ; Wed, 27 May 1998 10:20:52 +0100 Received: by exintgw02.itops.ldn.bzwint.com with Internet Mail Service (5.0.1460.8) id ; Wed, 27 May 1998 10:33:19 +0100 Message-ID: <711DCB8FB391D111B9DD00805F8BDDBA7262FB@exips0019.itops.ldn.bzwint.com> From: "Dampure, Pierre-Yves: IT (LDN)" To: "'current@FreeBSD.org'" Subject: ELF Stage 2: results Date: Wed, 27 May 1998 10:34:03 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some problems after a make world of -current cvsupped 05:00 BST today: - The links created for the crypt libraries under /usr/lib/aout do not necessarily match what was present in /usr/lib; in effect, I was suddenly switched from DES to MD5 (which of course caused some problems when trying to log in...). Of course, this is just a one off, so it doesn't matter that much. - PPP could not load libalias any further, since the path is hardcoded in /usr/src/usr.bin/ppp/loadalias.c. This should be easy to fix, but also means we might have some more hardcoded paths in the tree. - I tried to recompile modula-3 (still willing to see if John Dyson's SMP mods sort the problem we have currently -- the port does not build under SMP) but apparently ld is still looking for /usr/lib/crt0 (see below). Where can I fix this? ---------------------- building m3 ---------------------- mkdir FreeBSD2 --- building in FreeBSD2 --- m3 -w1 -why -O -times -o m3 -F/var/tmp/qkcV8998 new source -> compiling ../src/M3Backend.i3 new source -> compiling ../src/Arg.i3 new source -> compiling ../src/Msg.i3 new source -> compiling ../src/M3Path.i3 new source -> compiling ../src/Unit.i3 new source -> compiling ../src/Utils.i3 new source -> compiling ../src/WebFile.i3 new source -> compiling ../src/M3BackPosix.m3 new source -> compiling ../src/Arg.m3 new source -> compiling ../src/Msg.m3 new source -> compiling ../src/M3Path.m3 new source -> compiling ../src/Unit.m3 new source -> compiling ../src/Utils.m3 new source -> compiling ../src/WebFile.m3 new source -> compiling ../src/Main.m3 -> linking m3 ld: /usr/lib/crt0.o: No such file or directory Fatal Error: program "ld" failed, exit status = 256 Best Regards, Pierre Y. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 02:39:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16123 for freebsd-current-outgoing; Wed, 27 May 1998 02:39:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16105; Wed, 27 May 1998 02:39:20 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id LAA17351; Wed, 27 May 1998 11:39:12 +0200 (CEST) (envelope-from sos) Message-Id: <199805270939.LAA17351@sos.freebsd.dk> Subject: Re: ELF preparation step 2 done In-Reply-To: <199805270920.CAA01664@rah.star-gate.com> from Amancio Hasty at "May 27, 98 02:20:06 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 27 May 1998 11:39:12 +0200 (CEST) Cc: sos@FreeBSD.ORG, karpen@ocean.campus.luth.se, current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Amancio Hasty who wrote: > Any way of converting a a.out library to elf? Not yet I belive, but I know John Polstra /has been/is/is going to/ work on such a beast... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 02:45:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17304 for freebsd-current-outgoing; Wed, 27 May 1998 02:45:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17261; Wed, 27 May 1998 02:45:18 -0700 (PDT) (envelope-from avalon@coombs.anu.edu.au) Message-Id: <199805270945.CAA17261@hub.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA073492063; Wed, 27 May 1998 19:41:03 +1000 From: Darren Reed Subject: Re: Sendmail 8.9 To: peter@netplex.com.au (Peter Wemm) Date: Wed, 27 May 1998 19:41:03 +1000 (EST) Cc: mike@smith.net.au, ejs@bfd.com, michaelh@cet.co.jp, tarkhil@asteroid.svib.ru, current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199805270424.MAA00317@spinner.netplex.com.au> from "Peter Wemm" at May 27, 98 12:24:04 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In some mail from Peter Wemm, sie said: [...] > Anyway, things would be helped a lot if the Sendmail, Inc folks would > clarify the scope of the license. If there's no danger to co-shipped > proprietary code, then it can go in. SO you, or someone else, is taking this up with them ? Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 03:35:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA27338 for freebsd-current-outgoing; Wed, 27 May 1998 03:35:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA27324 for ; Wed, 27 May 1998 03:35:47 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id MAA17500; Wed, 27 May 1998 12:35:40 +0200 (CEST) (envelope-from sos) Message-Id: <199805271035.MAA17500@sos.freebsd.dk> Subject: Re: ELF Step 2 In-Reply-To: <004601bd8949$4b195050$0242000a@jfsebastian.k2c.co.uk> from "Pierre Y. Dampure" at "May 27, 98 09:26:40 am" To: pierre.dampure@k2c.co.uk (Pierre Y. Dampure) Date: Wed, 27 May 1998 12:35:39 +0200 (CEST) Cc: current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to Pierre Y. Dampure who wrote: > After a make world on -current 05:00 BST : > > - cannot login; sorted out by booting single user and changing the password; it seems the system switched from DES to MD5 (verified by checking at the symbolic links) -- why? No idea.. > - ppp cannot load the alias library, because the path is hardcoded in /usr/src/usr.sbin/ppp/loadalias.c BAD coding style :( > Me thinks it's time to grep the source tree for hardcoded paths... Yup, thats what the next couple of weeks should be used for... I've allready changed those that I found on the way, but there is got to be more... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 04:04:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01867 for freebsd-current-outgoing; Wed, 27 May 1998 04:04:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01779 for ; Wed, 27 May 1998 04:04:01 -0700 (PDT) (envelope-from croot@btp1da.phy.uni-bayreuth.de) Received: (from root@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id NAA10680; Wed, 27 May 1998 13:03:13 +0200 (MEST) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199805270901.RAA04026@cssolar82.COMP.HKP.HK> Date: Wed, 27 May 1998 13:03:13 +0200 (MEST) Organization: university of bayreuth From: Werner Griessl To: c5666305 Subject: RE: where can I find the fig2dev for xfig3.2 Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-May-98 c5666305 wrote: > Hello, > > I need fig2dev 3.2 for xfig 3.2 and I cannot find it under ftp.FreeBSD.org. > Can anyone tell me where can I get it ? Thanks. > > Clarence > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: Werner Griessl Date: 27-May-98 Time: 13:02:44 This message was sent by XFMail ---------------------------------- /usr/ports/print/transfig Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 04:11:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03540 for freebsd-current-outgoing; Wed, 27 May 1998 04:11:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03494 for ; Wed, 27 May 1998 04:11:45 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA17050; Wed, 27 May 1998 21:11:41 +1000 Date: Wed, 27 May 1998 21:11:41 +1000 From: Bruce Evans Message-Id: <199805271111.VAA17050@godzilla.zeta.org.au> To: current@FreeBSD.ORG, pierre.dampure@k2c.co.uk Subject: Re: ELF Step 2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >After a make world on -current 05:00 BST : > >- cannot login; sorted out by booting single user and changing the = >password; it seems the system switched from DES to MD5 (verified by = >checking at the symbolic links) -- why? /usr/src/Makefile has the md5 libcrypt hard-coded in one place. I'm not sure why it doesn't get replaced by the correct ${_libcrypt} later. NOCLEAN? The wrong version should only be used to build perl. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 05:07:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14513 for freebsd-current-outgoing; Wed, 27 May 1998 05:07:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from serv.unibest.ru (serv.unibest.ru [194.87.33.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA14498 for ; Wed, 27 May 1998 05:07:34 -0700 (PDT) (envelope-from osa@unibest.ru) Received: (qmail 26405 invoked from network); 27 May 1998 12:07:18 -0000 Received: from unknown (HELO hole.etrust.ru) (192.168.30.2) by serv.unibest.ru with SMTP; 27 May 1998 12:07:18 -0000 Date: Wed, 27 May 1998 16:10:24 +0400 (MSD) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: Doug Elznic cc: freebsd-current@FreeBSD.ORG Subject: Re: which directories? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 May 1998, Doug Elznic wrote: > Hello, > I am interested in testing out the current release. What directories do I > need to download. i am trying to burn my own cd and I never found a > definitive answer for what directories to grab... > I think its minimum : bin + floppyes + src Rgdz, oZZ, osa@unibest.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 05:12:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15473 for freebsd-current-outgoing; Wed, 27 May 1998 05:12:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15462 for ; Wed, 27 May 1998 05:12:03 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id VAA05576; Wed, 27 May 1998 21:42:00 +0930 (CST) (envelope-from grog) Message-ID: <19980527214200.O24133@freebie.lemis.com> Date: Wed, 27 May 1998 21:42:00 +0930 From: Greg Lehey To: FreeBSD current users Subject: select: protocol failure in circuit setup Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anybody seen this message? select: protocol failure in circuit setup Since the last build (about 2 days ago), it happens when I do a $ rsh localhost echo foo Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 05:49:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA21777 for freebsd-current-outgoing; Wed, 27 May 1998 05:49:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA21756; Wed, 27 May 1998 05:49:34 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id WAA24357; Wed, 27 May 1998 22:49:28 +1000 Date: Wed, 27 May 1998 22:49:28 +1000 From: Bruce Evans Message-Id: <199805271249.WAA24357@godzilla.zeta.org.au> To: eivind@yes.no, mike@smith.net.au Subject: Re: DPT install problem Cc: current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >However, as long as the issue is only the size of the partitions, I >think there are better ways of solving this - e.g, a compressing >variant of the vn device. This would let regression testing run on >any box, instead of having to throw away 20GB of diskspace. (There >were also some hints about more issues in one of Tom's messages). Or the standard variant of the vn devices. It already compresses never-written-to blocks to 4 bytes each. I have tested files of size 16TB-1 and filesystems of size 1TB-512 on vn devices. A 1TB file system with 33 cylinder groups of size 31GB each took only 78 seconds to newfs and 70 seconds to fsck (when it was empty :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 05:56:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23092 for freebsd-current-outgoing; Wed, 27 May 1998 05:56:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.ftf.dk (root@mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23086 for ; Wed, 27 May 1998 05:56:33 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id QAA14815; Wed, 27 May 1998 16:57:50 +0200 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id OAA09713; Wed, 27 May 1998 14:56:23 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.7/8.8.5/prosa-1.1) id OAA27877; Wed, 27 May 1998 14:55:25 +0200 (CEST) Message-ID: <19980527145525.02573@deepo.prosa.dk> Date: Wed, 27 May 1998 14:55:25 +0200 From: Philippe Regnauld To: Brian Feldman Cc: freebsd-current@FreeBSD.ORG Subject: Re: current instabilities References: <19980527032329.16263.qmail@m2.findmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.88e In-Reply-To: <19980527032329.16263.qmail@m2.findmail.com>; from Brian Feldman on Wed, May 27, 1998 at 03:23:29AM -0000 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Please format 78 cols next time :-)] Brian Feldman writes: > 2) "options VM86" - EVIL EVIL EVIL! This really allows way too much > access to the memory by a mortal, and it's an effective DoS attack if a > user runs doscmd, say, and a certain executable (this time, I happened > to try ZSnes). Think there may be a way to make this safer? (I locked > myself up, and it didn't panic so I don't know what exact function > caused it). Also, could USER_LDT possibly be used as a DoS attack, like > it seems to me it could? It can: an old WINE binary lying around freezes my machine solid. Been doing so for 1~2 months (available on request) -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- «Pluto placed his bad dog at the entrance of Hades to keep the dead IN and the living OUT! The archetypical corporate firewall?» - S. Kelly Bootle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 06:06:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24605 for freebsd-current-outgoing; Wed, 27 May 1998 06:06:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24598 for ; Wed, 27 May 1998 06:06:50 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id NAA21594; Wed, 27 May 1998 13:06:46 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA02467; Wed, 27 May 1998 15:06:41 +0200 (MET DST) Message-ID: <19980527150641.40182@follo.net> Date: Wed, 27 May 1998 15:06:41 +0200 From: Eivind Eklund To: tarkhil@asteroid.svib.ru Cc: current@FreeBSD.ORG Subject: Re: TenDRA C++ References: <19980526194334.44185@follo.net> <199805270451.IAA02859@minas-tirith.pol.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805270451.IAA02859@minas-tirith.pol.ru>; from Alex Povolotsky on Wed, May 27, 1998 at 08:51:22AM +0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 27, 1998 at 08:51:22AM +0400, Alex Povolotsky wrote: > <19980526194334.44185@follo.net>Eivind Eklund writes: >> Personally I'd prefer to use TenDRA if at all possible. It seems to >> be much better than GCC when you look at error control etc. > > I've tried to compile Qt with TenDRA, and got more errors than I've got > earlier this year at all ;-) Looks like TenDRA has SOMETHING very different > from GCC inside it. It has an as full as possible verification against ISO C. This can be tuned; I'm not quite certain how easy it is to tune yet. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 06:45:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02035 for freebsd-current-outgoing; Wed, 27 May 1998 06:45:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02012 for ; Wed, 27 May 1998 06:45:33 -0700 (PDT) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id HAA01146; Wed, 27 May 1998 07:45:26 -0600 (MDT) (envelope-from brett@peloton.physics.montana.edu) Date: Wed, 27 May 1998 07:45:25 -0600 (MDT) From: Brett Taylor To: c5666305 cc: freebsd-current@FreeBSD.ORG Subject: Re: where can I find the fig2dev for xfig3.2 In-Reply-To: <199805270901.RAA04026@cssolar82.COMP.HKP.HK> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I need fig2dev 3.2 for xfig 3.2 and I cannot find it under ftp.FreeBSD.org. > Can anyone tell me where can I get it ? Thanks. cd /usr/ports/print/transfig && make install clean ********************************************************* Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ But Master, does not the fire need water too? Does not the mountain need the storm? - Beavis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 06:47:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02609 for freebsd-current-outgoing; Wed, 27 May 1998 06:47:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from serv.unibest.ru (serv.unibest.ru [194.87.33.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA02594 for ; Wed, 27 May 1998 06:47:41 -0700 (PDT) (envelope-from osa@unibest.ru) Received: (qmail 26775 invoked from network); 27 May 1998 13:47:29 -0000 Received: from unknown (HELO hole.etrust.ru) (192.168.30.2) by serv.unibest.ru with SMTP; 27 May 1998 13:47:29 -0000 Date: Wed, 27 May 1998 17:50:33 +0400 (MSD) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: FreeBSD-current mail-list Subject: 3.0-980520-SNAP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Today I upgrade my 3.0-SNAP to 3.0-980520-SNAP... After reboot: # uname -a FreeBSD ..... 3.0-980520-SNAP FreeBSD 3.0-980520-SNAP #0: Wed May 27 17:16:05 MSD 1998 osa@........:/usr/src/sys/compile/SECOND i386 # named -b /etc/namedb/named.boot May 27 ......... named[349]: /etc/namedb/named.boot:1: syntax error near; May 27 ......... named[350]: Ready to answer queries. My named.boot is following : ; $Id: named.boot,v 1.6 1997/05/08 15:23:28 joerg Exp $ ; From: @(#)named.boot 5.1 (Berkeley) 6/30/90 ; ; Refer to the named(8) man page for details. If you are ever going ; to setup a primary server, make sure you've understood the hairy ; details of how DNS is working. Even with simple mistakes, you can ; break connectivity for affected parties, or cause huge amount of ; useless Internet traffic. ; ; Setting up secondaries is way easier and the rough picture for this ; is explained below. ; ; If you enable a local name server, don't forget to enter 127.0.0.1 ; into your /etc/resolv.conf so this server will be queried first. ; Also, make sure to enable it in /etc/rc.conf. ; example sortlist config: ; sortlist 127.0.0.0 directory /etc/namedb ; type domain source host/file backup file cache . named.root primary 0.0.127.IN-ADDR.ARPA named.127.rev secondary etrust.ru 192.168.30.5 named.etrust.ru secondary 30.168.192.IN-ADDR.ARPA 192.168.30.5 named.192.168.30.rev forwarders 194.87.33.5 Whats strange ?? Rgdz, oZZ, osa@unibest.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 06:55:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04290 for freebsd-current-outgoing; Wed, 27 May 1998 06:55:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04273 for ; Wed, 27 May 1998 06:54:57 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id NAA24848 for ; Wed, 27 May 1998 13:54:54 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA02779; Wed, 27 May 1998 15:54:49 +0200 (MET DST) Message-ID: <19980527155446.50625@follo.net> Date: Wed, 27 May 1998 15:54:46 +0200 From: Eivind Eklund To: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <19980526194334.44185@follo.net> <199805261836.LAA00466@dingo.cdrom.com> <19980527001230.50907@follo.net> <19980527081540.A19950@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980527081540.A19950@keltia.freenix.fr>; from Ollivier Robert on Wed, May 27, 1998 at 08:15:40AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 27, 1998 at 08:15:40AM +0200, Ollivier Robert wrote: > According to Eivind Eklund: > > I think making it support e.g. 'long long' would need modifications of > > the frontend. > > lcc, now at 4.0, still has the same problem I think. That's basically because "long long" is in total violation of the ISO standard, IIRC. I've sent off a mail to the contact person for the TenDRA team; I'll wait and see that they say about the feasibility of using TenDRA as an OS compiler. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 07:22:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09233 for freebsd-current-outgoing; Wed, 27 May 1998 07:22:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09202 for ; Wed, 27 May 1998 07:22:11 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.0.Beta5/8.9.0.Beta5) id QAA07706; Wed, 27 May 1998 16:21:05 +0200 (SAT) From: John Hay Message-Id: <199805271421.QAA07706@zibbi.mikom.csir.co.za> Subject: Re: select: protocol failure in circuit setup In-Reply-To: <19980527214200.O24133@freebie.lemis.com> from Greg Lehey at "May 27, 98 09:42:00 pm" To: grog@lemis.com (Greg Lehey) Date: Wed, 27 May 1998 16:21:05 +0200 (SAT) Cc: FreeBSD-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anybody seen this message? > > select: protocol failure in circuit setup > > Since the last build (about 2 days ago), it happens when I do a > > $ rsh localhost echo foo > Do you have ipfw or something similar in use? John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 07:22:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09363 for freebsd-current-outgoing; Wed, 27 May 1998 07:22:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09346 for ; Wed, 27 May 1998 07:22:55 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from gjallarhorn.ifi.uio.no (2602@gjallarhorn.ifi.uio.no [129.240.65.40]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id QAA00488; Wed, 27 May 1998 16:22:49 +0200 (MET DST) Received: (from dag-erli@localhost) by gjallarhorn.ifi.uio.no ; Wed, 27 May 1998 16:22:49 +0200 (MET DST) Mime-Version: 1.0 To: Jared Mauch Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel panics.. References: <19980527002414.A3954@puck.nether.net> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 27 May 1998 16:22:48 +0200 In-Reply-To: Jared Mauch's message of "Wed, 27 May 1998 00:24:14 -0400" Message-ID: Lines: 7 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jared Mauch writes: > Anyone want the source for my program that nukes the system? :) Yes, please, thankyouverymuch :) -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 07:49:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12322 for freebsd-current-outgoing; Wed, 27 May 1998 07:49:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA12299; Wed, 27 May 1998 07:49:28 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0yehW4-0003B3-00; Wed, 27 May 1998 08:49:20 -0600 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id IAA20191; Wed, 27 May 1998 08:48:38 -0600 (MDT) Message-Id: <199805271448.IAA20191@harmony.village.org> To: Amancio Hasty Subject: Re: ELF preparation step 2 done Cc: sos@FreeBSD.ORG, karpen@ocean.campus.luth.se (Mikael Karpberg), current@FreeBSD.ORG In-reply-to: Your message of "Wed, 27 May 1998 02:20:06 PDT." <199805270920.CAA01664@rah.star-gate.com> References: <199805270920.CAA01664@rah.star-gate.com> Date: Wed, 27 May 1998 08:48:38 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199805270920.CAA01664@rah.star-gate.com> Amancio Hasty writes: : Any way of converting a a.out library to elf? If you are lucky: objcopy will do it. However, I fear that you may not be lucky. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 08:56:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26961 for freebsd-current-outgoing; Wed, 27 May 1998 08:56:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-100.joh.za.ibm.net [139.92.122.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26956 for ; Wed, 27 May 1998 08:56:22 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id RAA11565; Wed, 27 May 1998 17:51:14 +0200 (SAT) From: Robert Nordier Message-Id: <199805271551.RAA11565@ceia.nordier.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <19980527155446.50625@follo.net> from Eivind Eklund at "May 27, 98 03:54:46 pm" To: eivind@yes.no (Eivind Eklund) Date: Wed, 27 May 1998 17:51:11 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > On Wed, May 27, 1998 at 08:15:40AM +0200, Ollivier Robert wrote: > > According to Eivind Eklund: > > > I think making it support e.g. 'long long' would need modifications of > > > the frontend. > > > > lcc, now at 4.0, still has the same problem I think. > > That's basically because "long long" is in total violation of the ISO > standard, IIRC. A type long long int is part of the ISO standard presently under consideration (C9X). It is also not a "total violation" of the current ISO (C89/C94) standard in any meaningful sense. TenDRA can and already does support type long long int. > > I've sent off a mail to the contact person for the TenDRA team; I'll > wait and see that they say about the feasibility of using TenDRA as an > OS compiler. This was the subject of an Open Group research study (involving UnixWare and Linux) around 1995. (Fairly obviously, it is feasible.) The critical issue, however, is really whether it is feasible to compile *FreeBSD* with a non-GCC compiler. Any real problems will be due to FreeBSD (GCC quirks in the code) not to the compiler. (There are no fundamental difficulties inherent in compiling UNIX-like systems). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 09:12:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29795 for freebsd-current-outgoing; Wed, 27 May 1998 09:12:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29760 for ; Wed, 27 May 1998 09:11:56 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id LAA21904; Wed, 27 May 1998 11:11:39 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <00d201bd898a$239c9b40$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: "Ozz!!!" , "FreeBSD-current mail-list" Subject: Re: 3.0-980520-SNAP Date: Wed, 27 May 1998 11:11:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Ozz!!! > >Hi! >Today I upgrade my 3.0-SNAP to 3.0-980520-SNAP... >After reboot: > ># uname -a >FreeBSD ..... 3.0-980520-SNAP FreeBSD 3.0-980520-SNAP #0: Wed May 27 >17:16:05 MSD 1998 osa@........:/usr/src/sys/compile/SECOND i386 ># named -b /etc/namedb/named.boot >May 27 ......... named[349]: /etc/namedb/named.boot:1: syntax error near; >May 27 ......... named[350]: Ready to answer queries. > > >Whats strange ?? > 3.0-Current now uses BIND 8.x instead of BIND 4.x, you need to convert your named.boot file to a named.conf file that is compatible with BIND 8. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 09:19:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01415 for freebsd-current-outgoing; Wed, 27 May 1998 09:19:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA01397 for ; Wed, 27 May 1998 09:19:40 -0700 (PDT) (envelope-from trost@cloud.rain.com) Received: (qmail 14154 invoked by uid 4); 27 May 1998 16:18:57 -0000 Received: (qmail 9707 invoked from network); 27 May 1998 15:21:49 -0000 Received: from localhost.cloud.rain.com (HELO cloud.rain.com) (127.0.0.1) by localhost.cloud.rain.com with SMTP; 27 May 1998 15:21:49 -0000 To: current@FreeBSD.ORG Subject: Re: current instabilities References: <19980527145525.02573@deepo.prosa.dk> <19980527032329.16263.qmail@m2.findmail.com> In-reply-to: Your message of Wed, 27 May 1998 14:55:25 +0200. <19980527145525.02573@deepo.prosa.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <9703.896282507.1@cloud.rain.com> Date: Wed, 27 May 1998 08:21:48 -0700 Message-ID: <9704.896282508@cloud.rain.com> From: Bill Trost Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Philippe Regnauld writes: Brian Feldman writes: > Also, could USER_LDT possibly be used as a DoS attack, like it > seems to me it could? It can: an old WINE binary lying around freezes my machine solid. Been doing so for 1~2 months (available on request) I had been noticing that for a while, too, but have recently discovered that this problem can be avoided if I keep my paws off the mouse until the Windows program finished its startup. I don't understand the relationship, but there it is. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 09:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02173 for freebsd-current-outgoing; Wed, 27 May 1998 09:22:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from puck.nether.net (jared@puck.nether.net [204.42.254.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02167 for ; Wed, 27 May 1998 09:22:51 -0700 (PDT) (envelope-from jared@puck.nether.net) Received: (from jared@localhost) by puck.nether.net (8.9.0/8.7.3) id MAA14243; Wed, 27 May 1998 12:22:45 -0400 Message-ID: <19980527122245.A14180@puck.nether.net> Date: Wed, 27 May 1998 12:22:45 -0400 From: Jared Mauch To: =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel panics.. References: <19980527002414.A3954@puck.nether.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=mP3DRpeJDSE+ciuQ X-Mailer: Mutt 0.91.1i In-Reply-To: =?iso-8859-1?Q?=3Cxzp3edvkd3b=2Efsf=40gjallarhorn=2Eifi=2Euio=2Eno=3E=3B?= =?iso-8859-1?Q?_from_Dag-Erling_Coidan_Sm=F8rgrav__on_Wed=2C_May_27=2C_1?= =?iso-8859-1?Q?998_at_04:22:48PM_+0200?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Here's the url to the source: ftp://puck.nether.net/pub/jared/sysmon-0.78.4.12-fbsd.tar.gz It's a network monitoring tool. not a lot of docs out there for it. I'm also including my config file that causes the problems, feel free to use it for testing. I suspect that this is a mbuf issue when it gets so many raw icmp sockets going at once for doing pings... - jared --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sysmon.conf" config numfailures 2 config pageinterval 30 config logging local6 ; write a html file with the network status in it config statusfile html /home/httpd/html/netstat.html ; ITI Router: border1.arb.qual.net ping border1.arb.qual.net { blackrose-gw.arb ping blackrose-gw.arb photosystems-gw.arb ping photosystems-gw.arb.qual.net branch-1-gw.arb ping branch-1-gw.aa.qual.net branch-2-gw.arb ping branch-2-gw.aa.qual.net icnet-1-gw.arb ping icnet-1-gw.aa.qual.net icnet-2-gw.arb ping icnet-2-gw.aa.qual.net bizserve-gw.arb ping bizserve-gw.arb glfc.qual.net ping glfc milr.qual.net ping milr nnn-gw.arb.qual.net ping nnn-2514 { irc.cic.net ping irc.cic.net { irc.cic.net smtp smtp irc.cic.net tcp 4400 ircd } puck.nether.net ping puck.nether.net { puck.nether.net smtp smtp puck.nether.net tcp 21 ftpd puck.nether.net tcp 80 www } nether.net ping nether.net { nether.net tcp 21 ftpd nether.net smtp smtp } } ; UM: oasis-gw.arb.qual.net ping oasis-gw.dtw.qual.net michnet1.mich.net ping michnet1.mich.net michnet5.mich.net ping michnet5.mich.net border1.detroit.iagnet.net ping border1.detroit.iagnet.net { ; detroit customers: cisco1.detroit.usabestnet.net ping wwnet ; obm1.dtw.qual.net ping obm1.dtw provide-net-gw.dtw ping provide-net-gw.dtw mpro-gw.dtw ping mpro-gw.dtw altair-gw.dtw ping altair-gw.dtw.qual.net gateway-comm-gw.dtw ping gateway-comm-gw.dtw.qual.net eaglequest-gw.dtw ping eaglequest-gw.dtw detlegalnews-gw.dtw ping detlegalnews-gw.dtw asc-gw.dtw.qual.net ping asc-gw.dtw advdatanet-1-gw.dtw ping advdatanet-1-gw.dtw.qual.net advdatanet-2-gw.dtw ping advdatanet-2-gw.dtw.qual.net valassis-gw.dtw ping valassis-gw.dtw ; ds3 to bc1.cle bordercore1-ser12-1-0.cle.qual.net ping cle-dtw-ckt { border1.pittsburgh.iagnet.net ping border1.pbh.iagnet.net { buchanon-gw.pit ping pittsburgh-ser3-1 bandwidthcoop-gw.pit ping pittsburgh-ser3-2 meyer-unkovic-scott-gw.pit ping pittsburgh-ser3-3 acacia-gw.pit ping pittsburgh-ser3-4 natbus-1-gw.pit ping pittsburgh-ser3-5 natbus-2-gw.pit ping pittsburgh-ser3-6 natbus-3-gw.pit ping pittsburgh-ser3-7 } border1.akron.iagnet.net ping border1.akron.iagnet.net { anderson-gw.cak ping akron-ser8-0-0-5 tusconet-gw.cak ping akron-ser8-0-0-7 goodyear-1-gw.cak ping akron-ser8-0-0-6 pubsolu-gw.cak ping akron-ser8-0-0-8 acc-gw.cak ping akron-ser8-0-0-9 ; compulinx-gw.cak ping akron-ser3-0 chmca-gw.cak ping akron-ser8-0-0-2 multiverse-akron-gw.cak ping akron-eth5-1 rpm-gw.cak ping akron-ser8-0-0-12 bockclark-gw.cak ping akron-ser8-0-0-13 our-lady-of-the-elms-gw.cak ping akron-ser8-0-0-14 digitalclrimaging-gw.cak ping akron-ser8-0-0-15 hitchcock-gw.cak ping akron-ser3-1 wilkshire-gw.cak ping akron-ser8-0-0-16 aablueprint-gw.cak ping akron-ser8-0-0-18 ; cantoncompserv-gw.cak ping akron-ser8-0-0-19 goodyear-2-gw.cak ping akron-ser8-0-0-20 tusco-gw.cak ping akron-ser8-0-0-21 } border1.columbus.iagnet.net ping border1.columbus.iagnet.net { cottsys-gw.cmh ping columbus-ser4-0 bobevans-gw.cmh ping columbus-ser4-1 infinet-gw.cmh ping columbus-fasteth5-0-0 dominion-gw.cmh ping columbus-ser8-0-0-1 mc2-gw.cmh ping columbus-ser8-0-0-4 jade-gw.cmh ping columbus-ser8-0-0-5 thelimited-gw.cmh ping columbus-ser8-0-0-6 berwanger-gw.cmh ping columbus-ser8-0-0-7 milisornobil-gw.cmh ping columbus-ser8-0-0-8 morpc-gw.cmh ping columbus-ser8-0-0-9 eureka-gw.cmh ping columbus-ser8-0-0-10 mricolum-gw.cmh ping columbus-ser8-0-0-11 cruxnet-gw.cmh ping columbus-ser8-0-0-18 comnet-gw.cmh ping columbus-hssi9-0 siscom-gw.cmh ping columbus-eth10-0 } border1.toledo.iagnet.net ping border1.toledo.iagnet.net core1.cleveland.iagnet.net ping core1.cleveland.iagnet.net { bordercore1-atm1-0-0.cle.qual.net ping core1-atm border3.cleveland.iagnet.net ping border3.cle border4.cleveland.iagnet.net ping border4.cle border5.cleveland.iagnet.net ping border5.cle hq-gw.hq.qual.net ping hq-gw.hq.qual.net { nic ping nic { nic smtp nic-smtp } } ; dgx bordercore2.ord.qual.net ping bordercore2.ord { sl-gw12-chi-9-0.sprintlink.net ping sprint-upstream { verio.sprintnap.net ping verio.sprintnap.net genuity.sprintnap.net ping genuity.sprintnap.net digex.sprintnap.net ping digex.sprintnap.net Agis.sprintnap.net ping Agis.sprintnap.net cwix.sprintnap.net ping cwix.sprintnap.net netcom.sprintnap.net ping netcom.sprintnap.net nysernet.sprintnap.net ping nysernet.sprintnap.net geonet.sprintnap.net ping geonet.sprintnap.net idt.sprintnap.net ping idt.sprintnap.net athome.sprintnap.net ping athome.sprintnap.net exodus.sprintnap.net ping exodus.sprintnap.net esnet.sprintnap.net ping esnet.sprintnap.net dren.sprintnap.net ping dren.sprintnap.net iij.sprintnap.net ping iij.sprintnap.net EUNet.sprintnap.net ping EUNet.sprintnap.net attworldnet.sprintnap.net ping attworldnet.sprintnap.net vbns.sprintnap.net ping vbns.sprintnap.net } ; dgx interfaces news1.chicago.cic.net ping news1.chicago.cic.net { news1.chicago.cic.net nntp nntp } ns.chicago.cic.net ping ns.chicago.cic.net { ns.chicago.cic.net smtp smtp ns.chicago.cic.net udp 53 named } news2.chicago.cic.net ping feeder.chicago.cic.net { news2.chicago.cic.net nntp nntp } ; peo peo.cic.net ping peo.cic.net { bradley-gw.peo ping peo-int cyberdesic-gw.peo ping peo-int multiad-gw.peo ping peo-int eurora-gw.peo ping peo-int illinoiscentral-gw.peo ping peo-int mtco-1-gw.peo ping peo-int mtco-2-gw.peo ping peo-int } ; dgb border1.ord.qual.net ping border1.ord { wood-county-gw.ord ping dgb-int elmhurst-gw.ord ping dgb-int knox-gw.ord ping dgb-int aads-ldip-gw.ord ping dgb-int ala-gw.ord ping dgb-int lemont-high-school-gw.ord ping dgb-int kcl-gw.ord ping dgb-int devry-gw.ord ping dgb-int llcc-gw.ord ping dgb-int tric-gw.ord ping dgb-int stxavier-gw.ord ping dgb-int lakeforest-gw.ord ping dgb-int ncrel-gw.ord ping dgb-int kndl-gw.ord ping dgb-int d219-gw.ord ping dgb-int suba-gw.ord ping dgb-int wrhc-gw.ord ping dgb-int baxter-gw.ord ping dgb-int chicagopubsch-gw.ord ping dgb-int trinity-gw.ord ping dgb-int hinsdale-gw.ord ping dgb-int svcc-gw.ord ping dgb-int rockfordcollege-gw.ord ping dgb-int smithbucklin-1-gw.ord ping dgb-int depaul-2-gw.ord ping dgb-int mcmc-gw.ord ping dgb-int thinklink-gw.ord ping dgb-int luc-2-gw.ord ping dgb-int ilc-gw.ord ping dgb-int tsa-gw.ord ping dgb-int config numfailures 5 whis-gw.ord ping dgb-int config numfailures 2 trth-gw.ord ping dgb-int gisc-gw.ord ping dgb-int ides-gw.ord ping dgb-int lstc-gw.ord ping dgb-int stac-gw.ord ping dgb-int tcc-gw.ord ping dgb-int solitair-gw.ord ping dgb-int mchenry-gw.ord ping dgb-int knowledgesys-gw.ord ping dgb-int harv-gw.ord ping dgb-int davea-gw.ord ping dgb-int mrtc-gw.ord ping dgb-int uis-gw.ord ping dgb-int nlu-gw.ord ping dgb-int fedres-gw.ord ping dgb-int commonwealthed-gw.ord ping dgb-int abn-gw.ord ping dgb-int clc-gw.ord ping dgb-int d97-gw.ord ping dgb-int oohs-gw.ord ping dgb-int d146-gw.ord ping dgb-int scpm-gw.ord ping dgb-int psc-gw.ord ping dgb-int gem-gw.ord ping dgb-int onu-gw.ord ping dgb-int eis-gw.ord ping dgb-int northcentral-gw.ord ping dgb-int wcc-gw.ord ping dgb-int uofchicago-gw.ord ping dgb-int ibc-gw.ord ping dgb-int niu-gw.ord ping dgb-int colc-gw.ord ping dgb-int iit-gw.ord ping dgb-int htls-gw.ord ping dgb-int techadvisors-gw.ord ping dgb-int sd15-gw.ord ping dgb-int } ; dgc border2.ord.qual.net ping border2.ord { eths-gw.ord ping dgc-ser0-0 kish-gw.ord ping dgc-ser0-1 arq-gw.ord ping dgc-ser0-3 mvc-gw.ord ping dgc-ser0-4 jjc-gw.ord ping dgc-ser0-5 midwestern-gw.ord ping dgc-int ivcc-gw.ord ping dgc-ser1-1 lsoc-gw.ord ping dgc-ser1-2 dvic-gw.ord ping dgc-ser1-5 gri-gw.ord ping dgc-ser1-6 smithbucklin-2-gw.ord ping dgc-ser1-7 kcc-gw.ord ping dgc-ser2-1 dshs-gw.ord ping dgc-ser2-2 cod-gw.ord ping dgc-ser2-3 aurora-gw.ord ping dgc-ser2-4 ecn-gw.ord ping dgc-ser2-5 occ-gw.ord ping dgc-ser2-6 jmls-gw.ord ping dgc-ser2-7 aic-gw.ord ping dgc-ser3-0 sd59-gw.ord ping dgc-ser3-2 wc-gw.ord ping dgc-ser3-3 nsi-gw.ord ping dgc-ser3-4 depaul-1-gw.ord ping dgc-ser3-5 gln-gw.ord ping dgc-ser3-6 luc-1-gw.ord ping dgc-ser3-7 chm-gw.ord ping dgc-ser8-0 elm-gw.ord ping dgc-ser8-1 d108-gw.ord ping dgc-ser8-2 theramp-2-gw.ord ping dgc-ser8-3 qcr1-gw.ord ping dgc-ser8-4 niu-gw.ord ping dgc-ser8-6 elg-gw.ord ping dgc-ser8-7 ; ros-gw.ord ping dgc-ser9-0 ; msi-gw.ord ping dgc-ser9-1 uhc-gw.ord ping dgc-ser9-3 mbi-gw.ord ping dgc-ser9-5 dls-gw.ord ping dgc-ser9-6 ico-gw.ord ping dgc-ser9-7 ccc-gw.ord ping dgc-ser10-0 den-gw.ord ping dgc-ser10-2 npc-gw.ord ping dgc-ser10-3 mspy-gw.ord ping dgc-ser10-4 } ; dgf bordercore1.ord.qual.net ping bordercore1.ord { bordercore3-hssi0-0.WillowSprings.mci.net ping mci-upstream dgts1.cic.net ping dgts1.cic.net dgts2.cic.net ping dgts2.cic.net dgts3.cic.net ping dgts3.cic.net 6bone.cic.net ping 6bone.cic.net cmi.cic.net ping cmi.cic.net { cmihub-gw.cmi.qual.net ping cmihub charlie.ncsa.uiuc.edu ping charlie.ncsa.uiuc.edu dmz.gw.uiuc.edu ping dmz.gw.uiuc.edu net66-gw.cmi.qual.net ping net66-gw.cmi uci-ser0.cmi.qual.net ping uci-ser0.cmi servercom-gw.cmi.qual.net ping servercom-gw.cmi parkland-gw.cmi.qual.net ping parkland-gw.cmi wolfram-gw.cmi.qual.net ping wolfram-gw.cmi dacc-gw.cmi.qual.net ping dacc-gw.cmi.qual.net cci-ser0.cci.qual.net ping cci-ser0.cci.qual.net } } ; end of dgx } ; end of core1.cle } core2.cleveland.iagnet.net ping core2.cleveland.iagnet.net { h4-1-0.c40-14.Cleveland.t3.ans.net ping ans-upstream weasel ping weasel { weasel tcp 21 weasel-ftp weasel tcp 23 weasel-telnet weasel tcp 80 weasel-www weasel tcp 443 www-shttp ; virtual hosts: lti.cic.net tcp 80 lti.cic.net pharm.cic.net tcp 80 pharm.cic.net www.macfdn.org tcp 80 www.macfdn.org www.glfc.org tcp 80 www.glfc.org www.ncrel.org tcp 80 www.ncrel.org www.pixelquest.com tcp 80 www.pixelquest.com www.social.com tcp 80 www.social.com www.casappa.com tcp 80 www.casappa.com www.miec.org tcp 80 www.miec.org www.ncrtec.org tcp 80 www.ncrtec.org } ; main dialup machine cedar ping cedar { cedar smtp smtp cedar udp 49 xtacacs cedar udp 53 named cedar tcp 80 www www@qual.net } reader1.cleveland.iagnet.net ping reader1.cleveland.iagnet.net { reader1.cleveland.iagnet.net nntp nntp } } } } } --mP3DRpeJDSE+ciuQ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 09:24:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02377 for freebsd-current-outgoing; Wed, 27 May 1998 09:24:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02348 for ; Wed, 27 May 1998 09:23:57 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA01013; Wed, 27 May 1998 16:23:43 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA03746; Wed, 27 May 1998 18:23:37 +0200 (MET DST) Message-ID: <19980527182337.47243@follo.net> Date: Wed, 27 May 1998 18:23:37 +0200 From: Eivind Eklund To: Robert Nordier Cc: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <19980527155446.50625@follo.net> <199805271551.RAA11565@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805271551.RAA11565@ceia.nordier.com>; from Robert Nordier on Wed, May 27, 1998 at 05:51:11PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 27, 1998 at 05:51:11PM +0200, Robert Nordier wrote: > Eivind Eklund wrote: > > > On Wed, May 27, 1998 at 08:15:40AM +0200, Ollivier Robert wrote: > > > According to Eivind Eklund: > > > > I think making it support e.g. 'long long' would need modifications of > > > > the frontend. > > > > > > lcc, now at 4.0, still has the same problem I think. > > > > That's basically because "long long" is in total violation of the ISO > > standard, IIRC. > > A type long long int is part of the ISO standard presently under > consideration (C9X). I know - I reviewed this as part of the review team for Norway :-) > It is also not a "total violation" of the current ISO (C89/C94) > standard in any meaningful sense. It invokes undefined behaviour, and requires a diagnostic, and I believe it require a (minor) re-definition of some other parts of the grammar, and it break the semantics for 'long'. It is about as total a violation as you can get. The only reason it was allowed it into C9X was that it already was used too many places to be reasonably deniable :-( > TenDRA can and already does support type long long int. How do you set it up to allow this? I tried to find some way of doing it, but didn't. > > I've sent off a mail to the contact person for the TenDRA team; I'll > > wait and see that they say about the feasibility of using TenDRA as an > > OS compiler. > > This was the subject of an Open Group research study (involving UnixWare > and Linux) around 1995. (Fairly obviously, it is feasible.) I was thinking more of compiler speed and how much support is planned in the future. I know of the above studies (though I've not read them yet). > The critical issue, however, is really whether it is feasible to > compile *FreeBSD* with a non-GCC compiler. Whether it can be made feasible :-) It isn't doable at the moment, at least. > Any real problems will be due to FreeBSD (GCC quirks in the code) > not to the compiler. (There are no fundamental difficulties > inherent in compiling UNIX-like systems). It think the difficult issues here are linker sets and assembly. There are a few places where the code use GCC extensions to the preprocessor, but removing this has been on my TODO list for some time. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 09:30:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03755 for freebsd-current-outgoing; Wed, 27 May 1998 09:30:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03749 for ; Wed, 27 May 1998 09:30:49 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id LAA26315; Wed, 27 May 1998 11:30:45 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id LAA26883; Wed, 27 May 1998 11:30:14 -0500 Message-ID: <19980527113013.57367@right.PCS> Date: Wed, 27 May 1998 11:30:13 -0500 From: Jonathan Lemon To: Brian Feldman Cc: freebsd-current@FreeBSD.ORG Subject: Re: current instabilities References: <19980527032329.16263.qmail@m2.findmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <19980527032329.16263.qmail@m2.findmail.com>; from Brian Feldman on May 05, 1998 at 03:23:29AM -0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On May 05, 1998 at 03:23:29AM -0000, Brian Feldman wrote: > 2) "options VM86" - EVIL EVIL EVIL! This really allows way too much > access to the memory by a mortal, and it's an effective DoS attack if a > user runs doscmd, say, and a certain executable (this time, I happened > to try ZSnes). Think there may be a way to make this safer? (I locked > myself up, and it didn't panic so I don't know what exact function > caused it). Also, could USER_LDT possibly be used as a DoS attack, like > it seems to me it could? Uh. I've tried really hard to make sure that VM86 won't lock the system up. Are you sure that it is VM86, and not USER_LDT? If there is something in doscmd that can freeze the system, I'd like to know about it so I can get it fixed. :-) -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 10:11:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11090 for freebsd-current-outgoing; Wed, 27 May 1998 10:11:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11073 for ; Wed, 27 May 1998 10:11:19 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id BAA03536; Thu, 28 May 1998 01:09:45 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805271709.BAA03536@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: John Hay cc: grog@lemis.com (Greg Lehey), FreeBSD-current@FreeBSD.ORG Subject: Re: select: protocol failure in circuit setup In-reply-to: Your message of "Sat, 27 May 1998 16:21:05 +0200." <199805271421.QAA07706@zibbi.mikom.csir.co.za> Date: Thu, 28 May 1998 01:09:44 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > > Anybody seen this message? > > > > select: protocol failure in circuit setup > > > > Since the last build (about 2 days ago), it happens when I do a > > > > $ rsh localhost echo foo > > > > Do you have ipfw or something similar in use? It's a setup failure for rcmd(3) in libc. Basically what happens is that the outbound connection (from rsh to rshd) causes a reverse direction connection from rshd back to rsh for the control and stderr backchannel. All these are supposed to be checked for privileged ports, etc etc. I don't remember all that well, but it's something like that. ipfw is a likely suspect if it's filtering incoming connections to reserved ports etc. > John > -- > John Hay -- John.Hay@mikom.csir.co.za Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 10:15:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11810 for freebsd-current-outgoing; Wed, 27 May 1998 10:15:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11783 for ; Wed, 27 May 1998 10:15:19 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id BAA03576; Thu, 28 May 1998 01:14:14 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805271714.BAA03576@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Eivind Eklund cc: Nate Williams , "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Tue, 26 May 1998 20:15:49 +0200." <19980526201549.35268@follo.net> Date: Thu, 28 May 1998 01:14:13 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > On Tue, May 26, 1998 at 11:50:53AM -0600, Nate Williams wrote: > > > > I really don't think that we would want to also get into compiler > > > > support issues. Tool support issues are complex enough. I can imagine > > > > that egcs (could) be stable enough for our c++ compiler, but am much > > > > less confident of it being our default c compiler. > > > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > > be much better than GCC when you look at error control etc. > > > > Can it do shlibs? > > I don't know - is there much special it would have to do? Yes, it would need to be able to generate position independent code (PIC) to avoid relocation hits for data references. This is a big problem for the i386 family, there's no pc-relative addressing mode for data accesses (like there is on most other cpus), so one of the precious general purpose registers has to be stolen for it. (%ebx in this case). > It create assembly files (as the third stage) and use the system > assembler and linker, so I don't think it should be a problem, but I > don't really know. If it can make GOT and PLT references, it probably can do it. I'd be suprised though, it's a PITA to get it right. All the .size and function declarations would be needed as well. > Eivind. Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 11:40:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28996 for freebsd-current-outgoing; Wed, 27 May 1998 11:40:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28930 for ; Wed, 27 May 1998 11:40:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA00856; Wed, 27 May 1998 10:34:38 -0700 (PDT) Message-Id: <199805271734.KAA00856@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: FreeBSD current users Subject: Re: select: protocol failure in circuit setup In-reply-to: Your message of "Wed, 27 May 1998 21:42:00 +0930." <19980527214200.O24133@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 10:34:38 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anybody seen this message? > > select: protocol failure in circuit setup > > Since the last build (about 2 days ago), it happens when I do a > > $ rsh localhost echo foo If you telnet to localhost, are you getting the "realloc" message from inetd? This screws up a lot of protocols because it spills into the stream (eg. POP). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 11:42:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29452 for freebsd-current-outgoing; Wed, 27 May 1998 11:42:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29408; Wed, 27 May 1998 11:42:32 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA17779; Wed, 27 May 1998 19:40:36 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199805271840.TAA17779@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: sos@FreeBSD.ORG cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG Subject: Re: cvs commit: src Makefile src/etc rc src/etc/mtree BSD.usr.dist In-reply-to: Your message of "Tue, 26 May 1998 23:06:40 +0200." <199805262106.XAA27629@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 27 May 1998 19:40:36 +0100 From: Brian Somers Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA29430 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In reply to Garrett Wollman who wrote: > > < said: > > > > > This will after a make world & reboot give a system that no > > > longer uses /usr/lib/*, infact one could remove all the old > > > libraries there, they are not used anymore. > > > > Except for all the inconvenient third-party software... > > Well, there is no real solution for that I'm afraid.. > > At runtime shared libs wil be resolved via rtld which knows > where to look for libs. > > Systems that rely on libs being in /usr/lib via hard path will > fail, ie Makefiles with a wired in hard path, we can then argue > to death who is broken... > > Another story is what we are going to do with /usr/local/lib :( Any ideas for /usr/src/usr.sbin/ppp/loadalias.c ? It dlopen()s and dlsym()s with a fixed path prefix. Cheers. > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team > Even more code to hack -- will it ever end > .. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 11:44:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29711 for freebsd-current-outgoing; Wed, 27 May 1998 11:44:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29674 for ; Wed, 27 May 1998 11:43:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id KAA00888; Wed, 27 May 1998 10:39:28 -0700 (PDT) Message-Id: <199805271739.KAA00888@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Brian Feldman" cc: freebsd-current@FreeBSD.ORG Subject: Re: current instabilities In-reply-to: Your message of "27 May 1998 03:23:29 -0000." <19980527032329.16263.qmail@m2.findmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 10:39:28 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 2) "options VM86" - EVIL EVIL EVIL! This really allows way too much > access to the memory by a mortal I'm curious as to what you mean by this. What "memory" does it allow access to? >, and it's an effective DoS attack if a > user runs doscmd, say, and a certain executable (this time, I happened > to try ZSnes). There may still be bugs in the vm86 handling, and we'd like to know if you find them. What you were running sounds like a graphical program, and there is no support for graphics in doscmd. You wouldn't happen to have run with the '-r' flag now would you? > Think there may be a way to make this safer? (I locked > myself up, and it didn't panic so I don't know what exact function > caused it). Also, could USER_LDT possibly be used as a DoS attack, like > it seems to me it could? Again, it shouldn't, no. What services do you plan to deny? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 12:27:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09307 for freebsd-current-outgoing; Wed, 27 May 1998 12:27:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09292 for ; Wed, 27 May 1998 12:27:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA01163; Wed, 27 May 1998 11:23:12 -0700 (PDT) Message-Id: <199805271823.LAA01163@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Brian Feldman" cc: current@FreeBSD.ORG Subject: Re: current instabilities In-reply-to: Your message of "Wed, 27 May 1998 12:20:50 PDT." <19980527192053.7361.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 11:23:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Restored cc: to -current) > Yes it was a graphical program, DOS so it was trying to manipulate the > memory regions of the graphics card. As I gather about vm86, supposedly > it allows low-level access to specific memory regions, does it not? No. Doscmd uses the standard FreeBSD mechanisms for low-level hardware access. > And > this does seem to be a Denial of Service at the moment, considering a > valid MS-DOS program and a world-usable doscmd can currently be used to > lock the system completely. Doscmd is setgid kmem. Arguably it shouldn't be. To be really dangerous though, it has to be run as root. > As of USER_LDT I want to know more too, so I > can understand concerns about it. Coincidentally, X was running, and > doscmd -b were my args. I'll see what -r is when I get home... I would suggest learning more before rushing into print. However, please don't take that to mean that we aren't interested in hearing about these problems. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 12:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10180 for freebsd-current-outgoing; Wed, 27 May 1998 12:32:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10173 for ; Wed, 27 May 1998 12:32:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA01196 for ; Wed, 27 May 1998 11:27:46 -0700 (PDT) Message-Id: <199805271827.LAA01196@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.ORG Subject: Argh! errno spam! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 11:27:46 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a grumble; the 'new' errno macro is a real pain for non-libc consumers, as well as anything that has a structure member called 'errno'. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 13:11:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17303 for freebsd-current-outgoing; Wed, 27 May 1998 13:11:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-91.joh.za.ibm.net [139.92.122.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17281 for ; Wed, 27 May 1998 13:11:40 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id WAA13789; Wed, 27 May 1998 22:04:12 +0200 (SAT) From: Robert Nordier Message-Id: <199805272004.WAA13789@ceia.nordier.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <19980527182337.47243@follo.net> from Eivind Eklund at "May 27, 98 06:23:37 pm" To: eivind@yes.no (Eivind Eklund) Date: Wed, 27 May 1998 22:04:11 +0200 (SAT) Cc: rnordier@nordier.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > On Wed, May 27, 1998 at 05:51:11PM +0200, Robert Nordier wrote: > > TenDRA can and already does support type long long int. > > How do you set it up to allow this? I tried to find some way of doing > it, but didn't. #pragma TenDRA longlong type allow In the case of the FreeBSD port, you can also simply specify the system environment. You may need -ltdf during linking. There is currently an unresolved bug in i386 long long support: avoid casting to long long. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 13:16:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18530 for freebsd-current-outgoing; Wed, 27 May 1998 13:16:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18406 for ; Wed, 27 May 1998 13:16:00 -0700 (PDT) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <3066-8368> convert rfc822-to-8bit; Wed, 27 May 1998 22:15:45 +0200 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.8.8/8.8.8) with UUCP id VAA00757 for freebsd-current@freebsd.org; Wed, 27 May 1998 21:59:41 +0200 (MET DST) (envelope-from paulz@trantor.stuyts.nl) Received: from trantor.stuyts.nl (localhost [127.0.0.1]) by trantor.stuyts.nl (8.8.8/8.8.5) with ESMTP id QAA00517 for ; Wed, 27 May 1998 16:25:34 +0200 (MET DST) Message-Id: <199805271425.QAA00517@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: cdrecord trouble on currnet Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Date: Wed, 27 May 1998 16:25:34 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am getting write errors on my Philips 2600 CD-R using cd-write and burncd.sh (from /usr/share/examples/worm/ ) so I thought , I'l compile cdrecord and try that. But I get the following error when truying to do a dummy burn: $ sudo cdrecord -dev=0,4,0 -data -dummy /scratch/img/psnl Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler Bus error (core dumped) This is a freshly compiled port on a current cvsupped today. I suspect I am missing something in my kernel config, so here is my config file : # # # $Id: trantor,v 1.18 1998/05/27 14:19:06 paulz Exp paulz $ # machine "i386" cpu "I586_CPU" ident trantor maxusers 10 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES options MFS #Memory File System options NFS #Network File System options PROCFS #Process filesystem options "CD9660" #ISO 9660 filesystem options "COMPAT_43" #Compatible with BSD 4.3 options "SCSI_DELAY=5" #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options SCSIDEBUG options DDB options INCLUDE_CONFIG_FILE # Include thist file in /kernel options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on sd0 controller isa0 controller pci0 #controller pnp0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller ahc0 options AHC_ALLOW_MEMIO #options AHC_TAGENABLE #options AHC_SCBPAGING_ENABLE controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows device worm0 at scbus? # SCSI worm # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 10 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr # psm: PS/2 mouse port [note: conflicts with sc0/vt0, thus "conflicts" keywd] device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device de0 pseudo-device loop pseudo-device ether pseudo-device tun 2 pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device pty 31 pseudo-device bpfilter 4 #Berkeley packet filter # Audio drivers: `snd', `sb', `pas', `gus', `pca' controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? port? irq? drq 5 device sbmidi0 at isa? port 0x330 irq? device opl0 at isa? port 0x388 #device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x15 vector pcmintr # KTRACE enables the system-call tracing facility ktrace(2). options KTRACE #kernel tracing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about -- Paul van der Zwan paulz @ trantor.stuyts.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 13:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19277 for freebsd-current-outgoing; Wed, 27 May 1998 13:19:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from colossus.dyn.ml.org (dburr@206-18-112-222.la.inreach.net [206.18.112.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19248 for ; Wed, 27 May 1998 13:19:10 -0700 (PDT) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.8/8.8.7) id NAA28817; Wed, 27 May 1998 13:18:48 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 27 May 1998 13:18:47 -0700 (PDT) Organization: Computer Help From: Donald Burr To: Ozz!!! Subject: RE: 3.0-980520-SNAP Cc: FreeBSD-current mail-list Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 27-May-98, Ozz!!! wrote: > My named.boot is following : > ; $Id: named.boot,v 1.6 1997/05/08 15:23:28 joerg Exp $ > ; From: @(#)named.boot 5.1 (Berkeley) 6/30/90 The BIND (named) in current is the latest version. It uses a very different style of configuration file. You will need to convert your named.boot into the new syntax (it's not too difficult). Read the man page for named(8) to findout about the new format. - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNWx1JvjpixuAwagxAQGQ0gP6AtkcieGH9n3ey6UphqXJRsx9crqus3Gj eaa1pDXOHTYHZUh3iV5GJan+P7Wlviez0oh7Xnfj7pwVIIusKyps6fezwyAGvCFT CsgU7p6Mrlc6b/VuE2a0Bk/z3XlfTdoMM8iYCTA2WjYV9xVzTGlxyH+7Q0vpPfNP qc/zwKAY4QU= =nGxj -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 13:53:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27193 for freebsd-current-outgoing; Wed, 27 May 1998 13:53:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27175 for ; Wed, 27 May 1998 13:52:49 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id UAA10070; Wed, 27 May 1998 20:52:36 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id WAA06585; Wed, 27 May 1998 22:52:29 +0200 (MET DST) Message-ID: <19980527225223.43868@follo.net> Date: Wed, 27 May 1998 22:52:23 +0200 From: Eivind Eklund To: Amancio Hasty Cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <19980526225254.45152@follo.net> <199805270007.RAA06110@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805270007.RAA06110@rah.star-gate.com>; from Amancio Hasty on Tue, May 26, 1998 at 05:07:56PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 26, 1998 at 05:07:56PM -0700, Amancio Hasty wrote: > Since, most of the time over here all I do is compile this or compile that > makes me interested on the speed of the compiler . for instance, if it > can speed up make world that would be great and it the compiler generates > decent code all the much better. For selected applications I am very > interested on the code generation . I'm interested in code generation more than compile speed everywhere. Anyway; here are the results: gcc -O2 -pipe: 11.41s (average over 3 runs) tcc -Ysystem: 8.35s (average over 3 runs) tcc -Ysystem, -Wt,-X: 8.21s (average over 3 runs) gcc -pipe: 6.94s (average over 3 runs) tcc defaults to all optimizations on; I'd guess that's about equal to -O2. -Wt,-X disables "all" optimizations - this seems to only disable high-level optimizations, and not peepholes, which probably take the largest amount of time. Before each set of test runs I did a 'get-everything-into-the-cache' run with the same options, to avoid that penalty. The runs were done from a DTP RAID-1 array with a 16MB cache in front, so disk access times should not be a significant part. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 13:57:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28058 for freebsd-current-outgoing; Wed, 27 May 1998 13:57:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28024 for ; Wed, 27 May 1998 13:56:59 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id UAA10172; Wed, 27 May 1998 20:56:55 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id WAA06599; Wed, 27 May 1998 22:56:47 +0200 (MET DST) Message-ID: <19980527225647.36082@follo.net> Date: Wed, 27 May 1998 22:56:47 +0200 From: Eivind Eklund To: Robert Nordier Cc: current@FreeBSD.ORG Subject: Replacing gcc as the system compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) References: <19980527182337.47243@follo.net> <199805272004.WAA13789@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805272004.WAA13789@ceia.nordier.com>; from Robert Nordier on Wed, May 27, 1998 at 10:04:11PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 27, 1998 at 10:04:11PM +0200, Robert Nordier wrote: > You may need -ltdf during linking. What does this contain? Have you looked closely at XANDF? I'm seeing two real hurdles (beyond inertia) in using this as our main compiler: The use of asm() for some macros in the kernel, and the use of linker sets. What do you think our chance of working around these are? > There is currently an unresolved bug in i386 long long support: avoid > casting to long long. There is also what looks like a bug in handling of NULL - it doesn't allow the use of ((void *)0) as NULL for function pointers. I may remember the C standard incorrectly (I haven't looked it up), but I think it is required to. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 14:09:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01112 for freebsd-current-outgoing; Wed, 27 May 1998 14:09:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01097 for ; Wed, 27 May 1998 14:09:17 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id OAA03993; Wed, 27 May 1998 14:07:55 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805272107.OAA03993@rah.star-gate.com> To: Eivind Eklund cc: Amancio Hasty , "John S. Dyson" , current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Wed, 27 May 1998 22:52:23 +0200." <19980527225223.43868@follo.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3990.896303275.1@rah.star-gate.com> Date: Wed, 27 May 1998 14:07:55 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Next, is can you come up with a simple benchmark to test the floating point optimization for Pentium classes or higher? Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 14:18:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03279 for freebsd-current-outgoing; Wed, 27 May 1998 14:18:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03224 for ; Wed, 27 May 1998 14:18:32 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id VAA11019; Wed, 27 May 1998 21:18:15 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id XAA06676; Wed, 27 May 1998 23:18:04 +0200 (MET DST) Message-ID: <19980527231803.18654@follo.net> Date: Wed, 27 May 1998 23:18:03 +0200 From: Eivind Eklund To: Amancio Hasty Cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <19980527225223.43868@follo.net> <199805272107.OAA03993@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805272107.OAA03993@rah.star-gate.com>; from Amancio Hasty on Wed, May 27, 1998 at 02:07:55PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, May 27, 1998 at 02:07:55PM -0700, Amancio Hasty wrote: > Next, is can you come up with a simple benchmark to test the floating > point optimization for Pentium classes or higher? Not easily, no. Robert Nordier had som FP code he was compiling with it. I have no floating point intensive code, and I run on an atypical platform (the Pentium Pro, which has a quite different profile than the Pentium. The P-II is supposedly like the Pentium). >From looking at the optimizations passes I can say that it should be at least as fast as gcc for 386, 486, and Pentium Pros, faster for Pentiums, and I don't know for P-IIs - I have never really experimented to find the performance profile for the P-IIs. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 14:19:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03406 for freebsd-current-outgoing; Wed, 27 May 1998 14:19:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03358; Wed, 27 May 1998 14:19:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA01620; Wed, 27 May 1998 13:13:13 -0700 (PDT) Message-Id: <199805272013.NAA01620@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Somers cc: sos@FreeBSD.ORG, wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG Subject: Re: cvs commit: src Makefile src/etc rc src/etc/mtree BSD.usr.dist In-reply-to: Your message of "Wed, 27 May 1998 19:40:36 BST." <199805271840.TAA17779@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Wed, 27 May 1998 13:13:13 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA03364 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Well, there is no real solution for that I'm afraid.. > > > > At runtime shared libs wil be resolved via rtld which knows > > where to look for libs. > > > > Systems that rely on libs being in /usr/lib via hard path will > > fail, ie Makefiles with a wired in hard path, we can then argue > > to death who is broken... > > > > Another story is what we are going to do with /usr/local/lib :( > > Any ideas for /usr/src/usr.sbin/ppp/loadalias.c ? It dlopen()s and > dlsym()s with a fixed path prefix. Ideally you should be able to pass a library name to dlopen() and have it do the search for you based on the current search path. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 14:30:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06391 for freebsd-current-outgoing; Wed, 27 May 1998 14:30:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06316 for ; Wed, 27 May 1998 14:30:10 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id RAA00108; Wed, 27 May 1998 17:29:53 -0400 (EDT) (envelope-from wollman) Date: Wed, 27 May 1998 17:29:53 -0400 (EDT) From: Garrett Wollman Message-Id: <199805272129.RAA00108@khavrinen.lcs.mit.edu> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Argh! errno spam! In-Reply-To: <199805271827.LAA01196@dingo.cdrom.com> References: <199805271827.LAA01196@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Just a grumble; the 'new' errno macro is a real pain for non-libc > consumers, as well as anything that has a structure member called > 'errno'. 8( Any C program which has a structure member called `errno' is erroneous. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 14:34:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07002 for freebsd-current-outgoing; Wed, 27 May 1998 14:34:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06830 for ; Wed, 27 May 1998 14:33:09 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0/frmug-2.3/nospam) with UUCP id XAA01789 for current@FreeBSD.ORG; Wed, 27 May 1998 23:32:45 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id XAA23552 for current@FreeBSD.ORG; Wed, 27 May 1998 23:04:43 +0200 (CEST) (envelope-from roberto) Message-ID: <19980527230443.A23502@keltia.freenix.fr> Date: Wed, 27 May 1998 23:04:43 +0200 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: ELF preparation step 2 done Mail-Followup-To: current@FreeBSD.ORG References: <199805270920.CAA01664@rah.star-gate.com> <199805270939.LAA17351@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.92.3i In-Reply-To: =?iso-8859-1?Q?=3C199805270939=2ELAA17351=40sos=2Efreebsd=2Edk=3E=3B_fro?= =?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Wed=2C_May_27=2C_1998_at_11:39:12AM_?= =?iso-8859-1?Q?+0200?= X-Operating-System: FreeBSD 3.0-CURRENT ctm#4311 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Søren Schmidt: > Not yet I belive, but I know John Polstra /has been/is/is going to/ > work on such a beast... BTW, if anyone wants patches to compile XFree86 3.3.2 in ELF, just ask. There are several assumptions in the code/Imakefiles to correct but it works : ICE/libICE.so.6.3: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped PEX5/libPEX5.so.6.0: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped SM/libSM.so.6.0: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped X11/libX11.so.6.1: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped XIE/libXIE.so.6.0: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped Xaw/libXaw.so.6.1: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped Xext/libXext.so.6.3: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped Xi/libXi.so.6.0: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped Xmu/libXmu.so.6.0: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped Xp/libXp.so.6.2: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped Xt/libXt.so.6.0: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped Xtst/libXtst.so.6.1: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped oldX/liboldX.so.6.0: ELF 32-bit LSB shared object, Intel 80386, version 1, not stripped -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #60: Fri May 15 21:04:22 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 14:40:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08314 for freebsd-current-outgoing; Wed, 27 May 1998 14:40:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08183 for ; Wed, 27 May 1998 14:39:51 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA01753; Wed, 27 May 1998 13:34:17 -0700 (PDT) Message-Id: <199805272034.NAA01753@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Garrett Wollman cc: Mike Smith , current@FreeBSD.ORG Subject: Re: Argh! errno spam! In-reply-to: Your message of "Wed, 27 May 1998 17:29:53 EDT." <199805272129.RAA00108@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 May 1998 13:34:17 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > Just a grumble; the 'new' errno macro is a real pain for non-libc > > consumers, as well as anything that has a structure member called > > 'errno'. 8( > > Any C program which has a structure member called `errno' is > erroneous. How so? Structure members have been allowed to be non-unique for a while now; I don't recall there being constraints on globals vs. structure members at all. There are a few perfectly good reasons to call a structure member errno, but regardless of the good reasons, I fear for the code in the ports collection. 8( I was bitten by this with the NetBSD-derived bootcode I'm working on, which doesn't use libc and thus needs its own errno in order to be a reasonable facsimile therof. (Yes, I have a workaround.) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 14:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10070 for freebsd-current-outgoing; Wed, 27 May 1998 14:49:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09982 for ; Wed, 27 May 1998 14:48:53 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id RAA00168; Wed, 27 May 1998 17:48:38 -0400 (EDT) (envelope-from wollman) Date: Wed, 27 May 1998 17:48:38 -0400 (EDT) From: Garrett Wollman Message-Id: <199805272148.RAA00168@khavrinen.lcs.mit.edu> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: Argh! errno spam! In-Reply-To: <199805272034.NAA01753@dingo.cdrom.com> References: <199805272129.RAA00108@khavrinen.lcs.mit.edu> <199805272034.NAA01753@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> Any C program which has a structure member called `errno' is >> erroneous. > How so? The ISO C standard explicitly allows errno to be defined as a macro. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 15:48:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24031 for freebsd-current-outgoing; Wed, 27 May 1998 15:48:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23899 for ; Wed, 27 May 1998 15:47:47 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA14198; Wed, 27 May 1998 22:47:22 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA07742; Thu, 28 May 1998 00:47:15 +0200 (MET DST) Message-ID: <19980528004714.19214@follo.net> Date: Thu, 28 May 1998 00:47:14 +0200 From: Eivind Eklund To: Mike Smith Cc: "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <19980526194334.44185@follo.net> <199805261836.LAA00466@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805261836.LAA00466@dingo.cdrom.com>; from Mike Smith on Tue, May 26, 1998 at 11:36:54AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, May 26, 1998 at 11:36:54AM -0700, Mike Smith wrote: > > On Tue, May 26, 1998 at 11:59:52AM -0500, John S. Dyson wrote: > > > I really don't think that we would want to also get into compiler > > > support issues. Tool support issues are complex enough. I can imagine > > > that egcs (could) be stable enough for our c++ compiler, but am much > > > less confident of it being our default c compiler. > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > be much better than GCC when you look at error control etc. > > How much of the world will build with it? Too little at the moment, I'd guess - but I don't know. I'm trying to find out if getting the kernel compiled is possible first. That's what's been the hurdle for compiling other Unixen with TenDRA. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 16:07:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28335 for freebsd-current-outgoing; Wed, 27 May 1998 16:07:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28294 for ; Wed, 27 May 1998 16:07:25 -0700 (PDT) (envelope-from kpielorz@caladan.tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.8.8/8.8.8) with SMTP id AAA00681 for ; Thu, 28 May 1998 00:07:15 +0100 (BST) (envelope-from kpielorz@caladan.tdx.co.uk) Date: Thu, 28 May 1998 00:07:15 +0100 (BST) From: Karl Pielorz To: current@FreeBSD.ORG Subject: aha1542 - again... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I read a while ago there were problems with the existing AHA1542 support on -current... I also read that someone (I can't remember now who it was) said they'd been through the code and fixed up a few things... As I remember it was a problem to do with bounce buffers... I've just had to add a 1542CF to my machine (as I'm out PCI slots and it was 'hanging around'), and I've run into problems with it - but I'm not sure there to do with bounce buffers etc. I know CAM is looking almost 'immanent' - but can anyone confirm whether the 1542 driver is in any useable state in -current at the moment? I have 2 x Double-Speed CD-ROM drives hooked up to it, I wouldn't have thought they were particularly 'stressy' for the driver ;-) Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 16:14:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29391 for freebsd-current-outgoing; Wed, 27 May 1998 16:14:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fanfic.org (fanfic.org [205.150.35.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29280 for ; Wed, 27 May 1998 16:13:06 -0700 (PDT) (envelope-from dstenn@fanfic.org) Received: from fanfic.org (fanfic.org [205.150.35.145]) by fanfic.org (8.8.8/8.8.8) with SMTP id TAA28760; Wed, 27 May 1998 19:12:46 -0400 (EDT) (envelope-from dstenn@fanfic.org) Posted-Date: Wed, 27 May 1998 19:12:46 -0400 (EDT) Date: Wed, 27 May 1998 19:12:46 -0400 (EDT) From: Dennis Tenn Reply-To: Dennis Tenn To: Ozz!!! cc: FreeBSD-current mail-list Subject: Re: 3.0-980520-SNAP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 May 1998, Ozz!!! wrote: | Hi! | Today I upgrade my 3.0-SNAP to 3.0-980520-SNAP... | After reboot: | | # uname -a | FreeBSD ..... 3.0-980520-SNAP FreeBSD 3.0-980520-SNAP #0: Wed May 27 | 17:16:05 MSD 1998 osa@........:/usr/src/sys/compile/SECOND i386 | # named -b /etc/namedb/named.boot | May 27 ......... named[349]: /etc/namedb/named.boot:1: syntax error near; | May 27 ......... named[350]: Ready to answer queries. | | Whats strange ?? I'm willing to bet you were using bind 4.9.x before and now you have bind 8.1.2. If this is the case check out. http://g68.ryd.student.liu.se/doc/bind/manual/?894538148 There is a program you can run to convert your old named.boot to named.conf and this program should be on your system. To convert the file do this. In your /etc/named dir: /usr/local/bin/named-bootconf.pl named.boot > named.conf Make sure you're loading named.conf now instead of named.boot. Check your rc.conf to see what it is loading and make any necessary changes. With this done you can reboot and it should be fine. Either that or run as root: named -b /etc/namedb/named.conf -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Dennis Tenn * There will always come a time dstenn@fanfic.org * When your love will be tested ICQ# 1457509 * Stand tall and rise to the occasion * For only then will you grow strong. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 16:16:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29711 for freebsd-current-outgoing; Wed, 27 May 1998 16:16:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hotmail.com (f47.hotmail.com [207.82.250.58]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA29586 for ; Wed, 27 May 1998 16:15:05 -0700 (PDT) (envelope-from brianfeldman@hotmail.com) Received: (qmail 17329 invoked by uid 0); 27 May 1998 23:14:22 -0000 Message-ID: <19980527231422.17328.qmail@hotmail.com> Received: from 166.55.240.72 by www.hotmail.com with HTTP; Wed, 27 May 1998 16:14:21 PDT X-Originating-IP: [166.55.240.72] From: "Brian Feldman" To: jlemon@americantv.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: current instabilities Content-Type: text/plain Date: Wed, 27 May 1998 16:14:21 PDT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's the entire scenario: FreeBSD 3.0-VERYVERYCURRENT doscmd -b booted on a 10m dos image drive ZSNES 0.4 for DOS X11 running I ran doscmd -b, then tried to run ZSNES, and it locked the system. Is this really X's fault then? If so, would I only have to have the computer in X to have this lock it up? Seeing as all activity stopped on the computer, not just consoles locking, I tend to believe that either the kernel froze itself, or doscmd somehow let the clock irq get turned off (hope not ;). Perhaps you should try out ZSnes? Brian Feldman >From jlemon@americantv.com Wed May 27 14:12:35 1998 >Received: from right.PCS (right.PCS [148.105.10.31]) > by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id QAA27018 > for ; Wed, 27 May 1998 16:01:52 -0500 (CDT) >Received: (from jlemon@localhost) > by right.PCS (8.6.13/8.6.4) id QAA08873; > Wed, 27 May 1998 16:01:21 -0500 >Message-ID: <19980527160121.09643@right.PCS> >Date: Wed, 27 May 1998 16:01:21 -0500 >From: Jonathan Lemon >To: Brian Feldman >Subject: Re: current instabilities >References: <19980527191549.17187.qmail@hotmail.com> >Mime-Version: 1.0 >Content-Type: text/plain; charset=us-ascii >X-Mailer: Mutt 0.61.1 >In-Reply-To: <19980527191549.17187.qmail@hotmail.com>; from Brian Feldman on May 05, 1998 at 12:15:42PM -0800 > >On May 05, 1998 at 12:15:42PM -0800, Brian Feldman wrote: >> Well, yes, I am pretty sure it was VM86. Doscmd doesn't use user_ldt, >> I'm pretty sure, does it? I was using doscmd, not Wine, and making world >> at the same time (-j4, no softupdates, no biggie) and wasn't expecting >> for it to lock up my computer. What I was trying to run was ZSnes for >> DOS, a SNES emulator, and immediately the system froze. I suppose yes, >> this could be an attempt to access video hardware, but is it really a >> good idea to allow any access of that (and other) memory regions to a >> user, if it can be so easily exploited? You should be able to get a copy >> of zsnes at http://zsnes.home.ml.org to try it out, but you seem to >> already be on top of the problem. BTW, I didn't try and see if it only >> locked up the console and keyboard because I don't have a serial console >> to break to, just a monitor. And if you wouldn't mind to take the time >> to explain the working of vm86/user_ldt to me, I'd appreciate it; like, >> what's a "local descriptor table", and is the danger in vm86 caused by >> direct memory access, through /dev/{k}mem, or something else? Maybe if I >> understood the concept I might be able to help make it safer than it is >> now, but I'd need to understand the concepts first... > >doscmd executes everything in a "vm86 penalty box", which is a special >mode of operation that causes the Intel chip to act like an 8088. > >The biggest difficulty is in making sure that none of the privileged >instructions leak out and affect the machine; DOS programs like to turn >off interrupts, which would cause a lockup of the system, since all >keyboard activity is interrupt driven. This is achieved by a kernel >module that emulates the interrupt handling, and tells doscmd that >the interrupts are on or off, but should never actually turn interrupts >off. > >IIRC, doscmd does not have direct access to any hardware, video or >otherwise. The hooks are in there, but are not enabled by default. > >If it managed to lock up the system, it would be because there is a bug >somewhere in the kernel handling of interrupts. > >Were you running doscmd under X or on a raw terminal? >-- >Jonathan > ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 17:07:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10532 for freebsd-current-outgoing; Wed, 27 May 1998 17:07:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-94.joh.za.ibm.net [139.92.122.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10267 for ; Wed, 27 May 1998 17:05:40 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id BAA16858; Thu, 28 May 1998 01:57:07 +0200 (SAT) From: Robert Nordier Message-Id: <199805272357.BAA16858@ceia.nordier.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <19980527231803.18654@follo.net> from Eivind Eklund at "May 27, 98 11:18:03 pm" To: eivind@yes.no (Eivind Eklund) Date: Thu, 28 May 1998 01:57:06 +0200 (SAT) Cc: hasty@rah.star-gate.com, toor@dyson.iquest.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > On Wed, May 27, 1998 at 02:07:55PM -0700, Amancio Hasty wrote: > > Next, is can you come up with a simple benchmark to test the floating > > point optimization for Pentium classes or higher? > > Not easily, no. Robert Nordier had som FP code he was compiling with > it. I have no floating point intensive code, and I run on an atypical > platform (the Pentium Pro, which has a quite different profile than > the Pentium. The P-II is supposedly like the Pentium). > > >From looking at the optimizations passes I can say that it should be > at least as fast as gcc for 386, 486, and Pentium Pros, faster for > Pentiums, and I don't know for P-IIs - I have never really > experimented to find the performance profile for the P-IIs. Just as an experiment, I compiled an old grep utility using both GCC and TenDRA. The results were really disappointing. :-( The TenDRA-compiled utility runs around twice as slowly: gcc 5.74 real 5.69 user 0.04 sys tcc 10.64 real 10.48 user 0.07 sys >From a 233 MHz PII running -current searching on /usr/share/dict/web2. The files are at http://www.icon.co.za/~nordier/re.tar.gz -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 17:20:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13541 for freebsd-current-outgoing; Wed, 27 May 1998 17:20:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.video-collage.com (www.video-collage.com [206.15.171.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13426 for ; Wed, 27 May 1998 17:20:17 -0700 (PDT) (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (xxx.video-collage.com [199.232.254.68]) by www.video-collage.com (8.8.5/8.8.5) with ESMTP id UAA01110 for ; Wed, 27 May 1998 20:19:11 -0400 (EDT) Received: (from mi@localhost) by xxx.video-collage.com (8.8.8/8.8.7) id UAA29608 for current@freebsd.org; Wed, 27 May 1998 20:20:06 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <199805280020.UAA29608@xxx.video-collage.com> Subject: Re: TenDRA C++ In-Reply-To: <199805270451.IAA02859@minas-tirith.pol.ru> from Alex Povolotsky at "May 27, 98 08:51:22 am" To: current@FreeBSD.ORG Date: Wed, 27 May 1998 20:20:06 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15856 for freebsd-current-outgoing; Wed, 27 May 1998 17:30:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from m2.findmail.com (m2.findmail.com [209.185.96.135]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA15808 for ; Wed, 27 May 1998 17:30:38 -0700 (PDT) (envelope-from brianfeldman@hotmail.com) Received: (qmail 19834 invoked by uid 505); 28 May 1998 00:29:28 -0000 Date: 28 May 1998 00:29:28 -0000 Message-ID: <19980528002928.19833.qmail@m2.findmail.com> From: "Brian Feldman" Subject: Replacing gcc as the system compiler (was Re: Fix In-Reply-To: <19980527225647.36082@follo.net> To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yep, being able to use NULL casted to void * is part of the C standard. Brian Feldman > On Wed, May 27, 1998 at 10:04:11PM +0200, Robert Nordier wrote: > > You may need -ltdf during linking. > > What does this contain? > > Have you looked closely at XANDF? I'm seeing two real hurdles (beyond > inertia) in using this as our main compiler: The use of asm() for some > macros in the kernel, and the use of linker sets. What do you think > our chance of working around these are? > > > There is currently an unresolved bug in i386 long long support: avoid > > casting to long long. > > There is also what looks like a bug in handling of NULL - it doesn't > allow the use of ((void *)0) as NULL for function pointers. > > I may remember the C standard incorrectly (I haven't looked it up), > but I think it is required to. > > Eivind. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 17:35:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16657 for freebsd-current-outgoing; Wed, 27 May 1998 17:35:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16531 for ; Wed, 27 May 1998 17:34:41 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (sleet.dstc.edu.au [130.102.176.45]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id KAA14168; Thu, 28 May 1998 10:34:12 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: Eivind Eklund cc: Mike Smith , "John S. Dyson" , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Thu, 28 May 1998 00:47:14 +0200." <19980528004714.19214@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 28 May 1998 10:34:11 +1000 Message-ID: <2133.896315651@dstc.edu.au> From: George Michaelson Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA16551 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is this useful? -George ------------------------- http://www.gr.opengroup.org/andf/linux_re.htm Abstract: ========= Validation of TenDRA Capability to Implement a Set of Commands for the Linux Operating System François de Ferrière Fred Roy Open Software Foundation Research Institute This report describes work done under contract to the Defence Research Agency (DRA) of the U.K. It is an extension of an earlier contract to assess the capability of the DRA TenDRA technology to express a fully portable operating system implementation. -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 17:41:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17800 for freebsd-current-outgoing; Wed, 27 May 1998 17:41:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-74.joh.za.ibm.net [139.92.122.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17673 for ; Wed, 27 May 1998 17:40:50 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id CAA17560; Thu, 28 May 1998 02:34:37 +0200 (SAT) From: Robert Nordier Message-Id: <199805280034.CAA17560@ceia.nordier.com> Subject: Re: Replacing gcc as the system compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) In-Reply-To: <19980527225647.36082@follo.net> from Eivind Eklund at "May 27, 98 10:56:47 pm" To: eivind@yes.no (Eivind Eklund) Date: Thu, 28 May 1998 02:34:36 +0200 (SAT) Cc: rnordier@nordier.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > On Wed, May 27, 1998 at 10:04:11PM +0200, Robert Nordier wrote: > > You may need -ltdf during linking. > > What does this contain? Pretty much just 64-bit integer support. > > Have you looked closely at XANDF? I'm seeing two real hurdles (beyond > inertia) in using this as our main compiler: The use of asm() for some > macros in the kernel, and the use of linker sets. What do you think > our chance of working around these are? I think we can find reasonable ways over the technical hurdles. Possibly, though, we need to commit to supporting TenDRA as a secondary compiler initially, with a change 6-12 months down the line, if things work out. >From a few tests here, it is starting to look as though the trans386 optimization needs additional work. I know that some of the code I haved looked at was highly-optimized, so the slow times may be fairly readily correctable. > > > There is currently an unresolved bug in i386 long long support: avoid > > casting to long long. > > There is also what looks like a bug in handling of NULL - it doesn't > allow the use of ((void *)0) as NULL for function pointers. > > I may remember the C standard incorrectly (I haven't looked it up), > but I think it is required to. There is something strange there (even the error message looks wrong): Can't convert function pointer 'void *' to non-function pointer 'int ( * ) ( void )'. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 17:44:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18274 for freebsd-current-outgoing; Wed, 27 May 1998 17:44:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18187 for ; Wed, 27 May 1998 17:44:00 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id KAA29573; Thu, 28 May 1998 10:43:49 +1000 Date: Thu, 28 May 1998 10:43:49 +1000 From: Bruce Evans Message-Id: <199805280043.KAA29573@godzilla.zeta.org.au> To: current@FreeBSD.ORG, eivind@yes.no Subject: Re: Fix for undefined "__error" and discussion of shared object versioning Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > I think making it support e.g. 'long long' would need modifications of >> > the frontend. >> >> lcc, now at 4.0, still has the same problem I think. > >That's basically because "long long" is in total violation of the ISO >standard, IIRC. It will be standard in the next version of the standard :-(. >I've sent off a mail to the contact person for the TenDRA team; I'll >wait and see that they say about the feasibility of using TenDRA as an >OS compiler. I use __attribute__(()) to avoid warnings for `long long' so that LINT can be compiled by `gcc -ansi -pedantic' with no errors and only about 3000 lines of warnings. E.g., in . #ifdef __GNUC__ /* XXX scope */ typedef int __attribute__((__mode__(__DI__))) int64_t; typedef unsigned int __attribute__((__mode__(__DI__))) u_int64_t; #else typedef long int64_t; /* XXX WRONG */ typedef unsigned long u_int64_t; /* XXX WRONG */ #endif Does TENDRA support __attribute__(())? I thought not :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 18:05:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22227 for freebsd-current-outgoing; Wed, 27 May 1998 18:05:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22128 for ; Wed, 27 May 1998 18:05:15 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id BAA19466; Thu, 28 May 1998 01:05:06 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id DAA09180; Thu, 28 May 1998 03:04:59 +0200 (MET DST) Message-ID: <19980528030458.00490@follo.net> Date: Thu, 28 May 1998 03:04:58 +0200 From: Eivind Eklund To: Robert Nordier Cc: current@FreeBSD.ORG Subject: Re: Replacing gcc as the system compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) References: <19980527225647.36082@follo.net> <199805280034.CAA17560@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805280034.CAA17560@ceia.nordier.com>; from Robert Nordier on Thu, May 28, 1998 at 02:34:36AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 02:34:36AM +0200, Robert Nordier wrote: > Eivind Eklund wrote: > > Have you looked closely at XANDF? I'm seeing two real hurdles (beyond > > inertia) in using this as our main compiler: The use of asm() for some > > macros in the kernel, and the use of linker sets. What do you think > > our chance of working around these are? > > I think we can find reasonable ways over the technical hurdles. > Possibly, though, we need to commit to supporting TenDRA as a secondary > compiler initially, with a change 6-12 months down the line, if things > work out. We have to support it for a while before switching, at least. The first step is getting the entire tree to build. > >From a few tests here, it is starting to look as though the trans386 > optimization needs additional work. I know that some of the code I > haved looked at was highly-optimized, so the slow times may be fairly > readily correctable. What kind of optimizations are you missing? I think there might be additional ANDF->ANDF optimizations we might be able to grab hold of from the old OSF projects; they're marked as 'freely available'. If what you're missing is high-level optimizations, this might be a good way to go. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 18:14:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23717 for freebsd-current-outgoing; Wed, 27 May 1998 18:14:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23660 for ; Wed, 27 May 1998 18:13:57 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA02022; Thu, 28 May 1998 10:43:42 +0930 (CST) (envelope-from grog) Message-ID: <19980528104341.G342@freebie.lemis.com> Date: Thu, 28 May 1998 10:43:41 +0930 From: Greg Lehey To: Mike Smith Cc: FreeBSD current users Subject: Re: select: protocol failure in circuit setup References: <19980527214200.O24133@freebie.lemis.com> <199805271734.KAA00856@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805271734.KAA00856@dingo.cdrom.com>; from Mike Smith on Wed, May 27, 1998 at 10:34:38AM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 27 May 1998 at 10:34:38 -0700, Mike Smith wrote: >> Anybody seen this message? >> >> select: protocol failure in circuit setup >> >> Since the last build (about 2 days ago), it happens when I do a >> >> $ rsh localhost echo foo > > If you telnet to localhost, are you getting the "realloc" message from > inetd? This screws up a lot of protocols because it spills into the > stream (eg. POP). That's the one. It's also the reason why a lot of my mail has been bouncing recently. I'm not running ipfw, but I have noticed a number of problems in the last few days. Apart from installing the newest version of -CURRENT about 3 days ago, I also mounted /tmp and /var/tmp as mfs file systems. This morning I came in and the system was just able to croak "/kernel: out of swap" before it haung up completely. This machine has 250 MB swap, and I seldom use more than 100 MB. I also don't use much /tmp or /var/tmp. Any ideas? Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 18:35:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26925 for freebsd-current-outgoing; Wed, 27 May 1998 18:35:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26902 for ; Wed, 27 May 1998 18:35:26 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id VAA00687; Wed, 27 May 1998 21:35:19 -0400 (EDT) (envelope-from wollman) Date: Wed, 27 May 1998 21:35:19 -0400 (EDT) From: Garrett Wollman Message-Id: <199805280135.VAA00687@khavrinen.lcs.mit.edu> To: Eivind Eklund Cc: current@FreeBSD.ORG Subject: Replacing gcc as the system compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) In-Reply-To: <19980527225647.36082@follo.net> References: <19980527182337.47243@follo.net> <199805272004.WAA13789@ceia.nordier.com> <19980527225647.36082@follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > There is also what looks like a bug in handling of NULL - it doesn't > allow the use of ((void *)0) as NULL for function pointers. > I may remember the C standard incorrectly (I haven't looked it up), > but I think it is required to. As originally written, X3.159-1989 appeared to prohibit the behavior you want. I believe that this was the subject of an interpretation ruling (since you ought to be able to use NULL in the context of a function pointer regardless of its definition). I don't remember what the precise semantic result was, other than to allow the behavior you want. This is but one of the reasons I detest NULL.... -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 18:35:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26961 for freebsd-current-outgoing; Wed, 27 May 1998 18:35:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26948 for ; Wed, 27 May 1998 18:35:35 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA00604; Thu, 28 May 1998 11:35:33 +1000 Date: Thu, 28 May 1998 11:35:33 +1000 From: Bruce Evans Message-Id: <199805280135.LAA00604@godzilla.zeta.org.au> To: mike@smith.net.au, wollman@khavrinen.lcs.mit.edu Subject: Re: Argh! errno spam! Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Any C program which has a structure member called `errno' is >> erroneous. Actually, only ones that declare or reference such a struct member after including . >How so? Structure members have been allowed to be non-unique for a >while now; I don't recall there being constraints on globals vs. >structure members at all. Macro scope is different from global scope. >There are a few perfectly good reasons to call a structure member errno, >but regardless of the good reasons, I fear for the code in the ports >collection. 8( I'd like the ports collection to be compiled routinely under -current. Even if it doesn't compile, the breakage list would be interesting. >I was bitten by this with the NetBSD-derived bootcode I'm working on, >which doesn't use libc and thus needs its own errno in order to be a >reasonable facsimile therof. (Yes, I have a workaround.) errno shouldn't be defined for non-libc interfaces. You probably got bitten by namespace pollution. KERNEL must be defined to stop errno being defined in our errno.h. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 20:05:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13085 for freebsd-current-outgoing; Wed, 27 May 1998 20:05:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (lee@st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13047 for ; Wed, 27 May 1998 20:05:18 -0700 (PDT) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.8.7/8.8.7) id XAA19095; Wed, 27 May 1998 23:04:51 -0400 (EDT) (envelope-from lee) Message-ID: <19980527230451.04171@st-lcremean.tidalwave.net> Date: Wed, 27 May 1998 23:04:51 -0400 From: Lee Cremeans To: current@FreeBSD.ORG Subject: Re: ELF preparation step 2 done Reply-To: lcremean@tidalwave.net References: <199805270920.CAA01664@rah.star-gate.com> <199805270939.LAA17351@sos.freebsd.dk> <19980527230443.A23502@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <19980527230443.A23502@keltia.freenix.fr>; from Ollivier Robert on Wed, May 27, 1998 at 11:04:43PM +0200 X-OS: FreeBSD 2.2.5-STABLE (soon to be 3.0-CURRENT) X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know the magic incantation to get an ELF buildworld working on a -stable system? when I do make buildworld BINFORMAT=elf, it dies with an assembler error during the gcc build. -- Lee C. -- Manassas, VA, USA (WakkyMouse on DALnet #watertower) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | lcremean@tidalwave.net FreeBSD/Linux/Unix hacker...Win95 and M$ evil! (go see www.freebsd.org) My home page: http://st-lcremean.tidalwave.net/~lee | finger me for geek code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 20:07:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13527 for freebsd-current-outgoing; Wed, 27 May 1998 20:07:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13487 for ; Wed, 27 May 1998 20:07:21 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id MAA10845; Thu, 28 May 1998 12:37:12 +0930 (CST) (envelope-from grog) Message-ID: <19980528123712.H4179@freebie.lemis.com> Date: Thu, 28 May 1998 12:37:12 +0930 From: Greg Lehey To: Karl Pielorz , current@FreeBSD.ORG Subject: Re: aha1542 - again... References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Karl Pielorz on Thu, May 28, 1998 at 12:07:15AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 May 1998 at 0:07:15 +0100, Karl Pielorz wrote: > > Hi, > > I read a while ago there were problems with the existing AHA1542 support > on -current... I also read that someone (I can't remember now who it was) > said they'd been through the code and fixed up a few things... > > As I remember it was a problem to do with bounce buffers... > > I've just had to add a 1542CF to my machine (as I'm out PCI slots and it > was 'hanging around'), and I've run into problems with it - but I'm not > sure there to do with bounce buffers etc. > > I know CAM is looking almost 'immanent' - but can anyone confirm whether > the 1542 driver is in any useable state in -current at the moment? I'm developing vinum on a -CURRENT machine with a 1542B. I had trouble with a 1542A, which appears to be a known problem (a number 0f 0xff bytes strewn at regular intervals, usually 32K), but the 1542B is working fine. > I have 2 x Double-Speed CD-ROM drives hooked up to it, I wouldn't have > thought they were particularly 'stressy' for the driver ;-) Do you have problems? You'll need bounce buffers for any ISA DMA device if you have more than 16 MB memory. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 20:20:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16040 for freebsd-current-outgoing; Wed, 27 May 1998 20:20:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from atlantis.nconnect.net (root@atlantis.nconnect.net [207.227.50.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15986 for ; Wed, 27 May 1998 20:20:03 -0700 (PDT) (envelope-from randyd@nconnect.net) Received: from nconnect.net (birddog-mke-x2-45.nconnect.net [207.227.61.45]) by atlantis.nconnect.net (8.8.5/8.8.5) with ESMTP id WAA23913 for ; Wed, 27 May 1998 22:15:51 -0500 (CDT) Message-ID: <356CD7D8.AB477F42@nconnect.net> Date: Wed, 27 May 1998 22:19:52 -0500 From: Randy DuCharme Organization: Astrolab Development X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: /usr/lib changes to current??? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, I think I've missed some important messages from the lists during the past week or so.. :-( I just cvsupped -current for the first time in about 2 weeks. Make world stops with.... -- usr/src/tmp/usr/include -c /usr/src/usr.bin/compile_et/compile_et.c lex -t -l /usr/src/usr.bin/compile_et/et_lex.lex.l > et_lex.lex.c yacc -o error_table.c /usr/src/usr.bin/compile_et/error_table.y cc -O -pipe -I. -I/usr/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/usr/src/tmp/usr/include -c error_table.c cc -O -pipe -I. -I/usr/src/usr.bin/compile_et/../../lib/libcom_err -I/usr/obj/usr/src/tmp/usr/include -static -o compile_et compile_et.o error_table.o -ll ld: -ll: no match *** Error code 1 Stop. *** Error code 1 Stop. I noticed that after a restart, ldconfig complaind about being unable to use /usr/lib on boot-up. I've updated the /etc/rc file from /usr/src/etc ( and the other rc. files that were new ) but I'm not too sure what's supposed to be happening here. Can someone please point me in the right direction? -- Randall D DuCharme Systems Engineer Novell, Microsoft, and UNIX Networking Support Computer Specialists Free Your Machine.... FreeBSD 414-253-9998 414-253-9919 (fax) The Power To Serve! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 20:21:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16182 for freebsd-current-outgoing; Wed, 27 May 1998 20:21:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bleep.ishiboo.com (user9488@bleep.ishiboo.com [199.79.133.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA16154 for ; Wed, 27 May 1998 20:21:12 -0700 (PDT) (envelope-from nirva@ishiboo.com) Received: (qmail 15836 invoked by uid 1000); 28 May 1998 04:23:42 -0000 Message-ID: <19980527232341.65268@bleep.ishiboo.com> Date: Wed, 27 May 1998 23:23:41 -0500 From: Danny Dulai To: "Daniel O'Connor" Cc: freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Fastvid.. References: <199805250838.SAA07894@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199805250838.SAA07894@cain.gsoft.com.au>; from Daniel O'Connor on Mon, May 25, 1998 at 06:08:20PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Daniel O'Connor (doconnor@gsoft.com.au): > Mmm.. speedy :) > xengine goes from 148rpm to 280rpm when fastvid is installed. > This is on a PII/266 in a SuperMicro P6SLS (LX chipset). The graphics card is > a Matrox Millenium II (PCI) with 4Mb of RAM. > The display is 8-bit depth at 1280x1024, the xengine size is 1152x900. > > The speedup factor is 1.89, mmm :) cvsup'd -current yesterday, can't get fastvid to build :( [blookitty|~/fastvid]% uname -a FreeBSD blookitty.ishiboo.com 3.0-CURRENT FreeBSD 3.0-CURRENT #16: Wed May 27 01:22:55 EDT 1998 nirva@blookitty.ishiboo.com:/fs/src/freebsd-current/sys/compile/blookitty i386 [blookitty+~/fastvid]% make Warning: Object directory not changed from original /u/nirva/fastvid cc -O -pipe -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -ansi -nostdinc -I- -I/u/nirva/fastvid -I/u/nirva/fastvid/@ -c fastvid.c /u/nirva/fastvid/@/vm/vm_map.h: In function `_vm_map_lock_upgrade': In file included from fastvid.c:86: /u/nirva/fastvid/@/vm/vm_map.h:249: warning: implicit declaration of function `lockmgr' /u/nirva/fastvid/@/vm/vm_map.h:249: `LK_EXCLUPGRADE' undeclared (first use this function) /u/nirva/fastvid/@/vm/vm_map.h:249: (Each undeclared identifier is reported only once /u/nirva/fastvid/@/vm/vm_map.h:249: for each function it appears in.) fastvid.c: At top level: fastvid.c:101: warning: initialization from incompatible pointer type fastvid.c:103: parse error before string constant fastvid.c: In function `fastvid_mod': fastvid.c:234: `fastvid_mod_mod_struct' undeclared (first use this function) *** Error code 1 Stop. The vm_map.h problems are solved by #including , but the MOD_SYSCALL on line 103 and the problem at line 234 I do not understand. Does anyone have copy of this module for -current? -- ___________________________________________________________________________ Danny Dulai Feet. Pumice. Lotion. http://www.ishiboo.com/~nirva/ nirva@ishiboo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 20:48:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19189 for freebsd-current-outgoing; Wed, 27 May 1998 20:48:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19184 for ; Wed, 27 May 1998 20:48:08 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA09679; Thu, 28 May 1998 13:48:06 +1000 Date: Thu, 28 May 1998 13:48:06 +1000 From: Bruce Evans Message-Id: <199805280348.NAA09679@godzilla.zeta.org.au> To: eivind@yes.no, rnordier@nordier.com Subject: Re: Replacing gcc as the system compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Have you looked closely at XANDF? I'm seeing two real hurdles (beyond >inertia) in using this as our main compiler: The use of asm() for some >macros in the kernel, and the use of linker sets. What do you think >our chance of working around these are? Linker sets are just asm(). Too bad - I'd like another excuse to kill them. asm() is not sue much in macros, but is used a lot in inline functions. I see inline functions as the main hurdle. Chances of replacing them at reasonable cost are low. >There is also what looks like a bug in handling of NULL - it doesn't >allow the use of ((void *)0) as NULL for function pointers. gcc used to have this bug too. Apparently, the C standard can easily be read as not allowing conversion from (void *)0 to a function pointer. The standard doesn't allow conversion from an object pointer to a function pointer, but (void *)0 is is a null pointer constant and null pointer constants are special. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 23:02:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07583 for freebsd-current-outgoing; Wed, 27 May 1998 23:02:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bleep.ishiboo.com (user329@bleep.ishiboo.com [199.79.133.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA07569 for ; Wed, 27 May 1998 23:02:11 -0700 (PDT) (envelope-from nirva@ishiboo.com) Received: (qmail 17884 invoked by uid 1000); 28 May 1998 07:04:41 -0000 Message-ID: <19980528020441.63901@bleep.ishiboo.com> Date: Thu, 28 May 1998 02:04:41 -0500 From: Danny Dulai To: Mikhail Teterin Cc: current@FreeBSD.ORG Subject: Re: TenDRA C++ References: <199805270451.IAA02859@minas-tirith.pol.ru> <199805280020.UAA29608@xxx.video-collage.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199805280020.UAA29608@xxx.video-collage.com>; from Mikhail Teterin on Wed, May 27, 1998 at 08:20:06PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Mikhail Teterin (mi@video-collage.com): > Alex Povolotsky once stated: > > =I've tried to compile Qt with TenDRA, and got more errors than I've > =got earlier this year at all ;-) Looks like TenDRA has SOMETHING very > =different from GCC inside it. > > gcc-2.8.1 does not compile Qt either. Or, rather, it compiles, but the > resulting object files can not be linked together. Same with KDE stuff. I couldn't get it to work wtih 2.7.2.1 either, unless, when I linked, I specified -lqt -lqt -lqt. -- ___________________________________________________________________________ Danny Dulai Feet. Pumice. Lotion. http://www.ishiboo.com/~nirva/ nirva@ishiboo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 23:15:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09053 for freebsd-current-outgoing; Wed, 27 May 1998 23:15:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09046 for ; Wed, 27 May 1998 23:15:11 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (root@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id IAA20438; Thu, 28 May 1998 08:14:32 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (mark@localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id IAA06571; Thu, 28 May 1998 08:14:31 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199805280614.IAA06571@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 To: Ollivier Robert cc: current@FreeBSD.ORG Subject: Re: ELF preparation step 2 done Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 28 May 1998 08:14:29 +0200 From: Mark Murray Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA09049 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert wrote: > BTW, if anyone wants patches to compile XFree86 3.3.2 in ELF, just > ask. There are several assumptions in the code/Imakefiles to correct but it > works : Yes, please! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 23:18:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09674 for freebsd-current-outgoing; Wed, 27 May 1998 23:18:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09650 for ; Wed, 27 May 1998 23:18:38 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id PAA16531; Thu, 28 May 1998 15:48:34 +0930 (CST) (envelope-from grog) Message-ID: <19980528154833.A16496@freebie.lemis.com> Date: Thu, 28 May 1998 15:48:33 +0930 From: Greg Lehey To: FreeBSD current users Subject: First observations after /usr/lib restructure Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just built a new world and kernel, and they work. That's the good news. The not-quite-so-good news is that I had a fair amount of difficulty to find the libraries I needed. 1. I have a number of old libraries in /usr/lib which I need for old software (such as the XI Graphics X server, which uses libc.so.2.2). Today's version of ldconfig refuses to even look in /usr/lib. I had to link them into /usr/lib/aout in order to get them to work. 2. Something else (fvwm2? Don't know, it didn't say its name) kept complaining about a missing libgnumalloc, which is in /usr/lib/compat. According to my /etc/sysconfig (yes, still haven't upgraded it :-), ldconfig should look in this directory, but ldconfig -r said it hadn't done so. I couldn't find the messages from the startup ldconfig, of course, so I currently don't know why it didn't include /usr/lib/compat in its path from the beginning. In any case, I think it's rather strange of ldconfig to refuse to scan /usr/lib. Is this because it's afraid of elves? I wouldn't have thought they would do it any harm. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 23:56:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14353 for freebsd-current-outgoing; Wed, 27 May 1998 23:56:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from serv.unibest.ru (serv.unibest.ru [194.87.33.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA14334 for ; Wed, 27 May 1998 23:55:53 -0700 (PDT) (envelope-from osa@unibest.ru) Received: (qmail 28087 invoked from network); 28 May 1998 06:55:50 -0000 Received: from unknown (HELO hole.etrust.ru) (192.168.30.2) by serv.unibest.ru with SMTP; 28 May 1998 06:55:50 -0000 Date: Thu, 28 May 1998 10:59:04 +0400 (MSD) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: Dennis Tenn cc: FreeBSD-current mail-list Subject: Re: 3.0-980520-SNAP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > | # named -b /etc/namedb/named.boot > | May 27 ......... named[349]: /etc/namedb/named.boot:1: syntax error near; > | May 27 ......... named[350]: Ready to answer queries. > > http://g68.ryd.student.liu.se/doc/bind/manual/?894538148 > > There is a program you can run to convert your old named.boot to > named.conf and this program should be on your system. To convert the file > do this. > > In your /etc/named dir: > > /usr/local/bin/named-bootconf.pl named.boot > named.conf Where can i get this script ? Rgdz, oZZ, osa@unibest.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 23:58:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14765 for freebsd-current-outgoing; Wed, 27 May 1998 23:58:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fanfic.org (fanfic.org [205.150.35.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14760 for ; Wed, 27 May 1998 23:58:16 -0700 (PDT) (envelope-from dstenn@fanfic.org) Received: from fanfic.org (fanfic.org [205.150.35.145]) by fanfic.org (8.8.8/8.8.8) with SMTP id CAA15560; Thu, 28 May 1998 02:58:02 -0400 (EDT) (envelope-from dstenn@fanfic.org) Posted-Date: Thu, 28 May 1998 02:58:02 -0400 (EDT) Date: Thu, 28 May 1998 02:58:02 -0400 (EDT) From: Dennis Tenn To: Ozz!!! cc: FreeBSD-current mail-list Subject: Re: 3.0-980520-SNAP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 May 1998, Ozz!!! wrote: | | > | # named -b /etc/namedb/named.boot | > | May 27 ......... named[349]: /etc/namedb/named.boot:1: syntax error near; | > | May 27 ......... named[350]: Ready to answer queries. | > | > http://g68.ryd.student.liu.se/doc/bind/manual/?894538148 | > | > There is a program you can run to convert your old named.boot to | > named.conf and this program should be on your system. To convert the file | > do this. | > | > In your /etc/named dir: | > | > /usr/local/bin/named-bootconf.pl named.boot > named.conf | | Where can i get this script ? Check /usr/local/bin -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Dennis Tenn * There will always come a time dstenn@fanfic.org * When your love will be tested ICQ# 1457509 * Stand tall and rise to the occasion * For only then will you grow strong. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed May 27 23:59:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15082 for freebsd-current-outgoing; Wed, 27 May 1998 23:59:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14979 for ; Wed, 27 May 1998 23:59:10 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id KAA19164 for ; Thu, 28 May 1998 10:58:48 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Thu, 28 May 1998 10:58:47 +0400 (MSD) From: Hostas Red To: current@FreeBSD.ORG Subject: -current breakage Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! cvsup'ed just few minutes ago, make world fail on 10th minute of building: cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 net/*.h /usr/obj/usr/src/tmp/usr/include/net install: net/*.h: No such file or directory *** Error code 71 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 00:19:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18087 for freebsd-current-outgoing; Thu, 28 May 1998 00:19:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18074 for ; Thu, 28 May 1998 00:19:49 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA23859; Thu, 28 May 1998 17:19:47 +1000 Date: Thu, 28 May 1998 17:19:47 +1000 From: Bruce Evans Message-Id: <199805280719.RAA23859@godzilla.zeta.org.au> To: current@FreeBSD.ORG, Pierre.Dampure@barclayscapital.com Subject: Re: ELF Stage 2: results Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >- The links created for the crypt libraries under /usr/lib/aout do not >necessarily match what was present in /usr/lib; in effect, I was suddenly >switched from DES to MD5 (which of course caused some problems when trying >to log in...). Of course, this is just a one off, so it doesn't matter that >much. I understand this now. At least the non-secure src/lib/libcrypt/Makefile doesn't install the links if they already exist, so switching the version is difficult even if it is to recover from a build bug. Also, src/lib/Makefile used to traverse the libcrypt directories in an order that ensured that the wrong version was always installed first in the clean /usr/lib/aout directory. The change in rev.1.69 of src/lib/Makefile won't make any difference until you delete the bogus links. src/Makefile still has related bogons: - the libraries target traverses the libcrypt directories in the old order. Oops, I don't understand this now. Installing src/lib/libcrypt first here should make the change in rev.1.69 of src/lib/Makefile a full no-op. - the bootstrap-libraries target only builds src/lib/libcrypt. This is probably harmless, since the bootstrap libcrypt is only used by the bootstrap perl which is only used to create one file in perl/usub. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 00:22:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18692 for freebsd-current-outgoing; Thu, 28 May 1998 00:22:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18687 for ; Thu, 28 May 1998 00:22:16 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id AAA20557 for ; Thu, 28 May 1998 00:16:38 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id JAA06249 for freebsd-current@freefall.cdrom.com; Thu, 28 May 1998 09:22:03 +0200 (MEST) (envelope-from kuku) Date: Thu, 28 May 1998 09:22:03 +0200 (MEST) From: Christoph Kukulies Message-Id: <199805280722.JAA06249@gilberto.physik.RWTH-Aachen.DE> To: freebsd-current@freefall.cdrom.com Subject: help! - nodes.h where is it? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cannot build -current world because something seems to be screwed in my src tree and I cannot figure out. Could soneone help me: e -c /a/src/bin/sh/alias.c yacc -d /a/src/bin/sh/arith.y cp y.tab.c arith.c cc -O2 -m486 -pipe -DSHELL -I. -I/a/src/bin/sh -I/usr/obj/a/src/tmp/usr/include -c arith.c lex -t -8 /a/src/bin/sh/arith_lex.l > arith_lex.c cc -O2 -m486 -pipe -DSHELL -I. -I/a/src/bin/sh -I/usr/obj/a/src/tmp/usr/include -c arith_lex.c cc -O2 -m486 -pipe -DSHELL -I. -I/a/src/bin/sh -I/usr/obj/a/src/tmp/usr/include -c /a/src/bin/sh/cd.c /a/src/bin/sh/cd.c:58: nodes.h: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. I looked into cd.c and there is nodes.h included but I can't find it anywhere in the system. Is it produced by some step in the make phase? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 00:40:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA20709 for freebsd-current-outgoing; Thu, 28 May 1998 00:40:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myrddin.demon.co.uk (exim@myrddin.demon.co.uk [158.152.54.180]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA20700; Thu, 28 May 1998 00:40:12 -0700 (PDT) (envelope-from dom@myrddin.demon.co.uk) Received: from dom by myrddin.demon.co.uk with local (Exim 1.80 #1) id 0yex5W-0000Cw-00; Thu, 28 May 1998 08:26:58 +0100 To: Peter Wemm Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 References: <199805270424.MAA00317@spinner.netplex.com.au> From: Dom Mitchell In-Reply-To: Peter Wemm's message of "Wed, 27 May 1998 12:24:04 +0800" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Thu, 28 May 1998 08:26:58 +0100 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm writes: > Before everybody jumps up and says "use xyzmail[er] instead" or "just > don't ship anything in the base", I'm not sure that we can do that as > parts of the base *assume* that sendmail (or a workalike) is present. VMailer, exim and smail all go to quite strong lengths to be sendmail compatible. In particular, I've been using exim for some time (over a year) as a sendmail replacement and found no faults. It's still GPL'd though. And there's still the massive body of sysadmin inertia that *knows* sendmail... Wouldn't it be easier to just stick with 8.8.8 until the licensing issues of this latest sendmail can be clarified? > Maybe it's time to bring back a basic local-only mail transport that gets > blown away when a real sendmail or comparable (qmail, smail, vmailer, > exim, etc etc) gets installed from a port. Sigh. That's certainly one solution; was one of these things used before? If so, where can I get a look at it? P.S. You left out MMDF. :-) -- "Every minute there's a UNIX system crashing somewhere." -- DJB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 00:49:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22056 for freebsd-current-outgoing; Thu, 28 May 1998 00:49:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22036 for ; Thu, 28 May 1998 00:49:01 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id PAA06808; Thu, 28 May 1998 15:48:35 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805280748.PAA06808@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: current@FreeBSD.ORG, Pierre.Dampure@barclayscapital.com Subject: Re: ELF Stage 2: results In-reply-to: Your message of "Thu, 28 May 1998 17:19:47 +1000." <199805280719.RAA23859@godzilla.zeta.org.au> Date: Thu, 28 May 1998 15:48:34 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >- The links created for the crypt libraries under /usr/lib/aout do not > >necessarily match what was present in /usr/lib; in effect, I was suddenly > >switched from DES to MD5 (which of course caused some problems when trying > >to log in...). Of course, this is just a one off, so it doesn't matter that > >much. > > I understand this now. At least the non-secure src/lib/libcrypt/Makefile > doesn't install the links if they already exist, so switching the > version is difficult even if it is to recover from a build bug. Also, > src/lib/Makefile used to traverse the libcrypt directories in an order > that ensured that the wrong version was always installed first in the > clean /usr/lib/aout directory. The change in rev.1.69 of src/lib/Makefile > won't make any difference until you delete the bogus links. > > src/Makefile still has related bogons: > - the libraries target traverses the libcrypt directories in the old > order. Oops, I don't understand this now. Installing src/lib/libcrypt > first here should make the change in rev.1.69 of src/lib/Makefile a > full no-op. Yes, but here it's installing into usr/obj/tmp/usr/lib/aout and irrelevant which one is used. The src/lib/Makefile determines what is installed into /usr/lib/aout for real.. At least, that's what I think happens. :-) I've blown too many make worlds in the last 24 hours and am fried with all the variations... > Bruce Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 01:06:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25099 for freebsd-current-outgoing; Thu, 28 May 1998 01:06:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25085 for ; Thu, 28 May 1998 01:06:17 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA27023; Thu, 28 May 1998 18:06:14 +1000 Date: Thu, 28 May 1998 18:06:14 +1000 From: Bruce Evans Message-Id: <199805280806.SAA27023@godzilla.zeta.org.au> To: bde@zeta.org.au, peter@netplex.com.au Subject: Re: ELF Stage 2: results Cc: current@FreeBSD.ORG, Pierre.Dampure@barclayscapital.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> src/Makefile still has related bogons: >> - the libraries target traverses the libcrypt directories in the old >> order. Oops, I don't understand this now. Installing src/lib/libcrypt >> first here should make the change in rev.1.69 of src/lib/Makefile a >> full no-op. > >Yes, but here it's installing into usr/obj/tmp/usr/lib/aout and irrelevant >which one is used. The src/lib/Makefile determines what is installed into >/usr/lib/aout for real.. Everything gets liked to it there. Linking to the wrong version is probably harmless for shared linkage but fatal for static linkage. This seems to only break init for the default settings of NOSHARED. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 01:12:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26538 for freebsd-current-outgoing; Thu, 28 May 1998 01:12:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26529 for ; Thu, 28 May 1998 01:12:23 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id BAA20832 for ; Thu, 28 May 1998 01:06:41 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA27314; Thu, 28 May 1998 18:12:15 +1000 Date: Thu, 28 May 1998 18:12:15 +1000 From: Bruce Evans Message-Id: <199805280812.SAA27314@godzilla.zeta.org.au> To: freebsd-current@freefall.cdrom.com, kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: help! - nodes.h where is it? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I cannot build -current world because something seems to be >screwed in my src tree and I cannot figure out. >... >I looked into cd.c and there is nodes.h included but I can't >find it anywhere in the system. Is it produced by some step in the make >phase? nodes.h is build from notdetypes and nodes.c.pat by mknodes. It looks like your src/share/mk/bsd.prog.mk is broken. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 02:07:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05155 for freebsd-current-outgoing; Thu, 28 May 1998 02:07:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05137 for ; Thu, 28 May 1998 02:07:34 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id CAA21077 for ; Thu, 28 May 1998 02:01:50 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id LAA06574; Thu, 28 May 1998 11:07:15 +0200 (MEST) (envelope-from kuku) Message-ID: <19980528110715.50696@gil.physik.rwth-aachen.de> Date: Thu, 28 May 1998 11:07:15 +0200 From: Christoph Kukulies To: Bruce Evans Cc: freebsd-current@freefall.cdrom.com, kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: help! - nodes.h where is it? References: <199805280812.SAA27314@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199805280812.SAA27314@godzilla.zeta.org.au>; from Bruce Evans on Thu, May 28, 1998 at 06:12:15PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 06:12:15PM +1000, Bruce Evans wrote: > >I cannot build -current world because something seems to be > >screwed in my src tree and I cannot figure out. > >... > >I looked into cd.c and there is nodes.h included but I can't > >find it anywhere in the system. Is it produced by some step in the make > >phase? > > nodes.h is build from notdetypes and nodes.c.pat by mknodes. > > It looks like your src/share/mk/bsd.prog.mk is broken. make mk doesn't work anymore, btw. OK, I overwrote all my /usr/share/mk files with the new ones, went into /usr/src/bin/sh # make clean rm -f mkinit mkinit.o mknodes mknodes.o mksyntax mksyntax.o builtins.c init.c nodes.c syntax.c builtins.h nodes.h syntax.h token.h y.tab.h sh alias.o arith.o arith_lex.o cd.o echo.o error.o eval.o exec.o expand.o histedit.o input.o jobs.o mail.o main.o memalloc.o miscbltin.o mystring.o options.o output.o parser.o printf.o redir.o show.o trap.o var.o builtins.o init.o nodes.o syntax.o sh.1.gz sh.1.cat.gz arith_lex.c arith.c y.tab.c y.tab.h # make cc -O2 -m486 -pipe -DSHELL -I. -I/a/src/bin/sh -c /a/src/bin/sh/alias.c yacc -d /a/src/bin/sh/arith.y cp y.tab.c arith.c cc -O2 -m486 -pipe -DSHELL -I. -I/a/src/bin/sh -c arith.c lex -t -8 /a/src/bin/sh/arith_lex.l > arith_lex.c cc -O2 -m486 -pipe -DSHELL -I. -I/a/src/bin/sh -c arith_lex.c cc -O2 -m486 -pipe -DSHELL -I. -I/a/src/bin/sh -c /a/src/bin/sh/cd.c /a/src/bin/sh/cd.c:58: nodes.h: No such file or directory *** Error code 1 Stop. FWIW, /usr/src/bin/sh is a link to /a/src/bin/sh. > > Bruce -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 02:20:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07287 for freebsd-current-outgoing; Thu, 28 May 1998 02:20:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07094 for ; Thu, 28 May 1998 02:20:03 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id RAA07165; Thu, 28 May 1998 17:16:52 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805280916.RAA07165@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Ozz!!! cc: Dennis Tenn , FreeBSD-current mail-list Subject: Re: 3.0-980520-SNAP In-reply-to: Your message of "Thu, 28 May 1998 10:59:04 +0400." Date: Thu, 28 May 1998 17:16:51 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ozz!!! wrote: > > > | # named -b /etc/namedb/named.boot > > | May 27 ......... named[349]: /etc/namedb/named.boot:1: syntax error near; > > | May 27 ......... named[350]: Ready to answer queries. > > > > http://g68.ryd.student.liu.se/doc/bind/manual/?894538148 > > > > There is a program you can run to convert your old named.boot to > > named.conf and this program should be on your system. To convert the file > > do this. > > > > In your /etc/named dir: > > > > /usr/local/bin/named-bootconf.pl named.boot > named.conf > Where can i get this script ? Hmm... /usr/src/contrib/bind/bin/named/named-bootconf.pl But I would have sworn that I'd made this get installed into /etc/namedb though... > Rgdz, > oZZ, > osa@unibest.ru > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 02:34:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09512 for freebsd-current-outgoing; Thu, 28 May 1998 02:34:18 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09507 for ; Thu, 28 May 1998 02:34:14 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id CAA12130 for ; Thu, 28 May 1998 02:33:27 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd012127; Thu May 28 09:33:26 1998 Date: Thu, 28 May 1998 02:33:24 -0700 (PDT) From: Julian Elischer To: current@FreeBSD.ORG Subject: /sys/sys rm'd? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What the F***? I typed "make world" and 2 minutes later it stopped with "cannot find ../../sys/sys/param.h" sure enough every .h file in the kernel tree has been removed.. luckily I just resolved a bunch of diffs I had in there. "where do you want the pointy hat to go today?" I guess I'll be updating my home sources today.. hope it gets me a fixed makefile while it's about it.... julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 02:41:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA10765 for freebsd-current-outgoing; Thu, 28 May 1998 02:41:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA10757 for ; Thu, 28 May 1998 02:41:35 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id CAA21376 for ; Thu, 28 May 1998 02:35:56 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA31697; Thu, 28 May 1998 19:41:26 +1000 Date: Thu, 28 May 1998 19:41:26 +1000 From: Bruce Evans Message-Id: <199805280941.TAA31697@godzilla.zeta.org.au> To: bde@zeta.org.au, kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: help! - nodes.h where is it? Cc: eivind@FreeBSD.ORG, freebsd-current@freefall.cdrom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> It looks like your src/share/mk/bsd.prog.mk is broken. > >make mk doesn't work anymore, btw. It went away about a year ago. >OK, I overwrote all my /usr/share/mk files with the >new ones, >went into /usr/src/bin/sh ># make clean >rm -f mkinit mkinit.o mknodes mknodes.o mksyntax mksyntax.o builtins.c init.c nodes.c syntax.c builtins.h nodes.h syntax.h token.h y.tab.h sh alias.o arith.o arith_lex.o cd.o echo.o error.o eval.o exec.o expand.o histedit.o input.o jobs.o mail.o main.o memalloc.o miscbltin.o mystring.o options.o output.o parser.o printf.o redir.o show.o trap.o var.o builtins.o init.o nodes.o syntax.o sh.1.gz sh.1.cat.gz arith_lex.c arith.c y.tab.c y.tab.h ># make >cc -O2 -m486 -pipe -DSHELL -I. -I/a/src/bin/sh -c /a/src/bin/sh/alias.c >yacc -d /a/src/bin/sh/arith.y >cp y.tab.c arith.c >... With the current `mk' files and Makefiles, `make' should begin with: cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -c /usr/src/bin/sh/mknodes.c cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -static mknodes.o -o mknodes ./mknodes /usr/src/bin/sh/nodetypes /usr/src/bin/sh/nodes.c.pat cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -c /usr/src/bin/sh/mksyntax.c cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -static mksyntax.o -o mksyntax ./mksyntax sh /usr/src/bin/sh/mktokens yacc -d /usr/src/bin/sh/arith.y cp y.tab.c arith.c ... It builds all the headers first, as it must to satisfy the following rule in bsd.prog.mk: .if defined(PROG) && !exists(${DEPENDFILE}) ${OBJS}: ${SRCS:M*.h} .endif I think understand this now. This rule doesn't apply if .depend already exists, and if .depend already exists then it must have full dependencies on nodes.h to work properly. You probably have a stale .depend file in the source directory. A stale .depend file in the obj directory would be always be deleted by `make world'. A stale .depend file in the source directory would only sometimes be deleted by `make world'. This is another bug in `make world', like the libgmp/mp* one. Even if the current directory is readonly, `make world' will only attempt to change it if there is certain garbage in it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 02:45:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11421 for freebsd-current-outgoing; Thu, 28 May 1998 02:45:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay1.kar.net (relay1.kar.net [195.5.17.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11401 for ; Thu, 28 May 1998 02:45:13 -0700 (PDT) (envelope-from kushn@mail.kar.net) Received: from olinet.isf.kiev.ua by relay1.kar.net with ESMTP id MAA01748; (8.8.last/vAk3/1.9) Thu, 28 May 1998 12:34:51 +0300 (EEST) Received: from kushnir.kiev.ua by olinet.isf.kiev.ua with SMTP id MAA13444; (8.8.last/vAk3/1.9) Thu, 28 May 1998 12:26:10 +0300 (EET DST) Date: Thu, 28 May 1998 12:33:56 +0300 (EEST) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua Reply-To: Vladimir Kushnir To: current@FreeBSD.ORG Subject: Re: -current breakage In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 May 1998, Hostas Red wrote: > Hi! > > cvsup'ed just few minutes ago, make world fail on 10th minute of building: > > cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 net/*.h > /usr/obj/usr/src/tmp/usr/include/net > install: net/*.h: No such file or directory > *** Error code 71 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > Adios, > /KONG Same here, and even worse: somehow buildworld wiped all of sys/sys/*.h, sys/net/*.h probably something else as well. Regards, Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 03:22:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16832 for freebsd-current-outgoing; Thu, 28 May 1998 03:22:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16790 for ; Thu, 28 May 1998 03:22:02 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id KAA10607; Thu, 28 May 1998 10:21:56 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA12848; Thu, 28 May 1998 12:21:47 +0200 (MET DST) Message-ID: <19980528122147.44793@follo.net> Date: Thu, 28 May 1998 12:21:47 +0200 From: Eivind Eklund To: Bruce Evans , rnordier@nordier.com Cc: current@FreeBSD.ORG Subject: Re: Replacing gcc as the system compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) References: <199805280348.NAA09679@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805280348.NAA09679@godzilla.zeta.org.au>; from Bruce Evans on Thu, May 28, 1998 at 01:48:06PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 01:48:06PM +1000, Bruce Evans wrote: > >Have you looked closely at XANDF? I'm seeing two real hurdles (beyond > >inertia) in using this as our main compiler: The use of asm() for some > >macros in the kernel, and the use of linker sets. What do you think > >our chance of working around these are? > > Linker sets are just asm(). Too bad - I'd like another excuse to kill > them. asm() is not sue much in macros, but is used a lot in inline > functions. I see inline functions as the main hurdle. Chances of > replacing them at reasonable cost are low. inline functions should not be a problem. There is a keyword for defining inline functions in standard C: "static". 'inline' is semantically null. I think it will be possible to handle __asm(), but I haven't really attempted to implement my ideas yet. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 04:03:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21777 for freebsd-current-outgoing; Thu, 28 May 1998 04:03:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21761 for ; Thu, 28 May 1998 04:02:53 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id TAA07561; Thu, 28 May 1998 19:01:29 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805281101.TAA07561@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Vladimir Kushnir cc: current@FreeBSD.ORG Subject: Re: -current breakage In-reply-to: Your message of "Thu, 28 May 1998 12:33:56 +0300." Date: Thu, 28 May 1998 19:01:28 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vladimir Kushnir wrote: > > > > On Thu, 28 May 1998, Hostas Red wrote: > > > Hi! > > > > cvsup'ed just few minutes ago, make world fail on 10th minute of building: > > > > cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 net/*.h > > /usr/obj/usr/src/tmp/usr/include/net > > install: net/*.h: No such file or directory > > *** Error code 71 > > 1 error > > *** Error code 2 > > 1 error > > *** Error code 2 > > 1 error > > *** Error code 2 > > 1 error > > > > Adios, > > /KONG > > Same here, and even worse: somehow buildworld wiped all of sys/sys/*.h, > sys/net/*.h probably something else as well. > > Regards, > Vladimir > Do you have CLOBBER defined by any chance? I'm suspicious of the following section of src/Makefile: includes: .if defined(CLOBBER) rm -rf ${DESTDIR}/usr/include/* mtree -deU -f ${.CURDIR}/etc/mtree/BSD.include.dist \ -p ${DESTDIR}/usr/include .endif There are some rm -rf's in src/include/Makefile as well. However, neither of these should really be a problem unless rm has started following symlinks or there's something odd going on. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 04:58:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28346 for freebsd-current-outgoing; Thu, 28 May 1998 04:58:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28326 for ; Thu, 28 May 1998 04:58:42 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA20418; Thu, 28 May 1998 07:34:51 -0400 (EDT) From: Peter Dufault Message-Id: <199805281134.HAA20418@hda.hda.com> Subject: Re: cdrecord trouble on currnet In-Reply-To: <199805271425.QAA00517@trantor.stuyts.nl> from Paul van der Zwan at "May 27, 98 04:25:34 pm" To: paulz@trantor.stuyts.nl (Paul van der Zwan) Date: Thu, 28 May 1998 07:34:50 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I am getting write errors on my Philips 2600 CD-R using cd-write and burncd.sh > (from /usr/share/examples/worm/ ) so I thought , I'l compile cdrecord and try > that. But I get the following error when truying to do a dummy burn: > > $ sudo cdrecord -dev=0,4,0 -data -dummy /scratch/img/psnl > Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler > Bus error (core dumped) > > > This is a freshly compiled port on a current cvsupped today. (I wonder why he is trying to use the round robin scheduler - I expect he wants the FIFO one). Cdrecord has autoconf'd in the P1003.1B scheduler interface. I'm probably going to have to change how I did things, but the program may need fixing also. By default, with nothing defined, the new system calls are setup to be LKM'd in for development and will fail at run time with ENOSYS or if you check for their presense with sysconf(). You can add build time support with the _KPOSIX_PRIORITY_SCHEDULING option in the kernel. See how cdrecord is deciding to use priority scheduling. If it decides that a program that links OK without checking any compile time feature test macros means that priority scheduling is supported, then that should be changed. I've been told some programs are doing this (not specifically cdrecord). If you set _POSIX_C_SOURCE to 199009L with a -D in the makefile and cderecord still tries to use the round robin scheduler then someone has screwed up - either us or cdrecord - so try that too. I wasn't as naive as it might seem by setting this up the way I have (configured for an LKM). These (POSIX required) run time options are a pain to figure out how to support, and eventually there will be a mixture of systems supporting different options. Either everything becomes required, adding to kernel bloat, or programs will fail this way when there is a mixture of systems out there. You will build on one system with all support configured in and then run on another system and the programs won't handle ENOSYS properly. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 05:15:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00633 for freebsd-current-outgoing; Thu, 28 May 1998 05:15:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA00624 for ; Thu, 28 May 1998 05:15:06 -0700 (PDT) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id IAA11740 for ; Thu, 28 May 1998 08:09:27 -0400 (EDT) Date: Thu, 28 May 1998 08:15:05 -0400 (EDT) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: freebsd-current@FreeBSD.ORG Subject: Latest context switch mods and smp commit Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cant remember who just commited some SMP mods for PRE P5 and SMP boxes with some context switch mods but I just wanted to mention that on my dual P-200 things appear alot faster. Especially on bootup when squid goes and fires up, it used to grind for 30 seconds or so now its quiet and smooth. I'd time a make world but current seems to be quite broke right now from all the mail goin back and forth. But I just wanted to say whoever authored the code for the commit with the SMP, context switches and pre-P5 boxes GOOD WORK! Just hope its not quietly trashing my FS or similar quietly in the background :) Chris -- "I don't do favors, I accumulate debts" ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.6 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 05:17:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01063 for freebsd-current-outgoing; Thu, 28 May 1998 05:17:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mexcom.net (ver2-92.uninet.net.mx [200.38.135.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01058 for ; Thu, 28 May 1998 05:17:10 -0700 (PDT) (envelope-from eculp@ver1.telmex.net.mx) Received: from mc.mexcom.net (telmex@ppp-4.mexcom.net [206.103.65.196]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id HAA20713; Thu, 28 May 1998 07:13:09 -0500 (CDT) Message-ID: <356D5663.2955B8A3@ver1.telmex.net.mx> Date: Thu, 28 May 1998 07:19:47 -0500 From: Edwin Culp Organization: Mexico Communicates, S.A. de C.V. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.18 i586) MIME-Version: 1.0 To: Paul van der Zwan CC: freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet References: <199805271425.QAA00517@trantor.stuyts.nl> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul van der Zwan wrote: > > I am getting write errors on my Philips 2600 CD-R using cd-write and burncd.sh > (from /usr/share/examples/worm/ ) so I thought , I'l compile cdrecord and try > that. But I get the following error when truying to do a dummy burn: > > $ sudo cdrecord -dev=0,4,0 -data -dummy /scratch/img/psnl > Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler > Bus error (core dumped) > > This is a freshly compiled port on a current cvsupped today. > I had problems with 1.6 and am using the older 1.6b12 I think it is. ed P.D. I'm using it on current but compiled on 2.2.6. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 05:19:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01654 for freebsd-current-outgoing; Thu, 28 May 1998 05:19:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01631 for ; Thu, 28 May 1998 05:19:43 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id UAA07769; Thu, 28 May 1998 20:19:26 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805281219.UAA07769@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: /sys/sys rm'd? In-reply-to: Your message of "Thu, 28 May 1998 02:33:24 MST." Date: Thu, 28 May 1998 20:19:26 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > What the F***? > > I typed "make world" > and 2 minutes later it stopped with > "cannot find ../../sys/sys/param.h" > sure enough > every .h file in the kernel tree has been removed.. > luckily I just resolved a bunch of diffs I had in there. > > "where do you want the pointy hat to go today?" I think I know what's happening: [8:14pm]/tmp/xx-117# find -dx . -print ./1 ./2 ./3 ./4 . [8:14pm]/tmp/xx-118# find -dx . -print | cpio -dump /tmp/xx cpio: ./1: No such file or directory cpio: ./2: No such file or directory cpio: ./3: No such file or directory cpio: ./4: No such file or directory 0 blocks [8:15pm]/tmp/xx-119# l total 2 1 drwxr-xr-x 2 root wheel 512 May 28 20:15 ./ 1 drwxrwxrwt 6 root wheel 512 May 28 20:14 ../ [8:15pm]/tmp/xx-120# The 'bootstrap' target is probably the culprit, it can't be removing the symlinks and the cpio must be trying to copy the files over themselves (and unlinking them first). Are you using -DNOCLEAN by any chance? Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 05:25:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02342 for freebsd-current-outgoing; Thu, 28 May 1998 05:25:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-88.joh.za.ibm.net [139.92.122.88]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02332 for ; Thu, 28 May 1998 05:25:08 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id OAA21736; Thu, 28 May 1998 14:15:35 +0200 (SAT) From: Robert Nordier Message-Id: <199805281215.OAA21736@ceia.nordier.com> Subject: Re: Replacing gcc as the system compiler (was Re: Fix for undefined "__error" and discussion of shared object versioning) In-Reply-To: <199805280348.NAA09679@godzilla.zeta.org.au> from Bruce Evans at "May 28, 98 01:48:06 pm" To: bde@zeta.org.au (Bruce Evans), eivind@yes.no (Eivind Eklund) Date: Thu, 28 May 1998 14:15:34 +0200 (SAT) Cc: current@FreeBSD.ORG, rnordier@nordier.com X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > >Have you looked closely at XANDF? I'm seeing two real hurdles (beyond > >inertia) in using this as our main compiler: The use of asm() for some > >macros in the kernel, and the use of linker sets. What do you think > >our chance of working around these are? > > Linker sets are just asm(). Too bad - I'd like another excuse to kill > them. asm() is not sue much in macros, but is used a lot in inline > functions. I see inline functions as the main hurdle. Chances of > replacing them at reasonable cost are low. TenDRA also lacks direct support for __attribute__((packed)) However, there are no padding bits for bit-fields and it is possible to specify -Zp[12] for unaligned packing at a file level. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 05:25:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02410 for freebsd-current-outgoing; Thu, 28 May 1998 05:25:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mexcom.net (ver2-92.uninet.net.mx [200.38.135.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02400 for ; Thu, 28 May 1998 05:25:34 -0700 (PDT) (envelope-from eculp@ver1.telmex.net.mx) Received: from mc.mexcom.net (telmex@ppp-4.mexcom.net [206.103.65.196]) by ns.mexcom.net (8.8.8/8.8.7) with SMTP id HAA20810; Thu, 28 May 1998 07:21:47 -0500 (CDT) Message-ID: <356D5869.3BA31F1B@ver1.telmex.net.mx> Date: Thu, 28 May 1998 07:28:25 -0500 From: Edwin Culp Organization: Mexico Communicates, S.A. de C.V. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.18 i586) MIME-Version: 1.0 To: Paul van der Zwan , freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet References: <199805271425.QAA00517@trantor.stuyts.nl> <356D5663.2955B8A3@ver1.telmex.net.mx> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Edwin Culp wrote: > > Paul van der Zwan wrote: > > > > I am getting write errors on my Philips 2600 CD-R using cd-write and burncd.sh > > (from /usr/share/examples/worm/ ) so I thought , I'l compile cdrecord and try > > that. But I get the following error when truying to do a dummy burn: > > > > $ sudo cdrecord -dev=0,4,0 -data -dummy /scratch/img/psnl > > Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling > > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler > > Bus error (core dumped) > > > > This is a freshly compiled port on a current cvsupped today. > > > I had problems with 1.6 and am using the older 1.6b12 I think it is. > > ed > > P.D. I'm using it on current but compiled on 2.2.6. I forgot, be sure to look at http://www.best.com/~spadger/CDR-cdrecord.html It is an excellent source of information. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 05:30:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03322 for freebsd-current-outgoing; Thu, 28 May 1998 05:30:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03314 for ; Thu, 28 May 1998 05:30:53 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id FAA21862 for ; Thu, 28 May 1998 05:25:14 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id OAA07124; Thu, 28 May 1998 14:30:32 +0200 (MEST) (envelope-from kuku) Message-ID: <19980528143032.44069@gil.physik.rwth-aachen.de> Date: Thu, 28 May 1998 14:30:32 +0200 From: Christoph Kukulies To: Bruce Evans Cc: kuku@gilberto.physik.RWTH-Aachen.DE, eivind@FreeBSD.ORG, freebsd-current@freefall.cdrom.com Subject: Re: help! - nodes.h where is it? References: <199805280941.TAA31697@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199805280941.TAA31697@godzilla.zeta.org.au>; from Bruce Evans on Thu, May 28, 1998 at 07:41:26PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 07:41:26PM +1000, Bruce Evans wrote: > >> It looks like your src/share/mk/bsd.prog.mk is broken. > > > >make mk doesn't work anymore, btw. > > It went away about a year ago. > > >OK, I overwrote all my /usr/share/mk files with the > >new ones, > >went into /usr/src/bin/sh > ># make clean > >rm -f mkinit mkinit.o mknodes mknodes.o mksyntax mksyntax.o builtins.c init.c nodes.c syntax.c builtins.h nodes.h syntax.h token.h y.tab.h sh alias.o arith.o arith_lex.o cd.o echo.o error.o eval.o exec.o expand.o histedit.o input.o jobs.o mail.o main.o memalloc.o miscbltin.o mystring.o options.o output.o parser.o printf.o redir.o show.o trap.o var.o builtins.o init.o nodes.o syntax.o sh.1.gz sh.1.cat.gz arith_lex.c arith.c y.tab.c y.tab.h > ># make > >cc -O2 -m486 -pipe -DSHELL -I. -I/a/src/bin/sh -c /a/src/bin/sh/alias.c > >yacc -d /a/src/bin/sh/arith.y > >cp y.tab.c arith.c > >... > > With the current `mk' files and Makefiles, `make' should begin with: > > cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -c /usr/src/bin/sh/mknodes.c > cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -static mknodes.o -o mknodes > ./mknodes /usr/src/bin/sh/nodetypes /usr/src/bin/sh/nodes.c.pat > cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -c /usr/src/bin/sh/mksyntax.c > cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -static mksyntax.o -o mksyntax > ./mksyntax > sh /usr/src/bin/sh/mktokens > yacc -d /usr/src/bin/sh/arith.y > cp y.tab.c arith.c > ... > > It builds all the headers first, as it must to satisfy the following rule > in bsd.prog.mk: > > .if defined(PROG) && !exists(${DEPENDFILE}) > ${OBJS}: ${SRCS:M*.h} > .endif > > I think understand this now. This rule doesn't apply if .depend already > exists, and if .depend already exists then it must have full dependencies > on nodes.h to work properly. You probably have a stale .depend file in > the source directory. A stale .depend file in the obj directory would > be always be deleted by `make world'. > > A stale .depend file in the source directory would only sometimes be > deleted by `make world'. This is another bug in `make world', like > the libgmp/mp* one. Even if the current directory is readonly, > `make world' will only attempt to change it if there is certain > garbage in it. I removed my /a/obj tree also. There were no .depend files left in either src nor obj tree. I copied all mk files in place: $Id: bsd.dep.mk,v 1.24 1998/05/15 09:34:48 bde Exp $ $Id: bsd.doc.mk,v 1.44 1998/05/06 18:44:00 bde Exp $ $Id: bsd.info.mk,v 1.50 1998/05/06 18:44:01 bde Exp $ $Id: bsd.kern.mk,v 1.9 1998/05/01 18:13:37 bde Exp $ $Id: bsd.kmod.mk,v 1.48 1998/03/19 13:22:46 bde Exp $ $Id: bsd.lib.mk,v 1.72 1998/05/15 09:34:48 bde Exp $ $Id: bsd.libnames.mk,v 1.12 1998/05/15 09:34:48 bde Exp $ $Id: bsd.man.mk,v 1.27 1998/04/27 15:08:07 bde Exp $ $Id: bsd.obj.mk,v 1.24 1998/05/06 18:44:03 bde Exp $ $Id: bsd.own.mk,v 1.13 1998/03/19 13:32:43 bde Exp $ $Id: bsd.port.mk,v 1.276 1998/05/20 22:27:18 jkh Exp $ $Id: bsd.port.subdir.mk,v 1.23 1997/11/20 05:31:44 asami Exp $ $Id: bsd.prog.mk,v 1.74 1998/05/15 09:34:48 bde Exp $ $Id: bsd.sgml.mk,v 1.25 1998/05/18 16:57:10 wosch Exp $ $Id: bsd.subdir.mk,v 1.24 1998/05/06 16:53:53 wosch Exp $ $Id: sys.mk,v 1.33 1998/05/15 09:34:48 bde Exp $ I rebuilt and installed make, I copied make.conf in place. cd /a/src/bin/sh make clean make yields: Warning: Object directory not changed from original /a/src/bin/sh cc -O -pipe -DSHELL -I. -I/a/src/bin/sh -c alias.c yacc -d arith.y cp y.tab.c arith.c cc -O -pipe -DSHELL -I. -I/a/src/bin/sh -c arith.c lex -t -8 arith_lex.l > arith_lex.c cc -O -pipe -DSHELL -I. -I/a/src/bin/sh -c arith_lex.c cc -O -pipe -DSHELL -I. -I/a/src/bin/sh -c cd.c cd.c:58: nodes.h: No such file or directory *** Error code 1 Stop. Doing a make depend first then helped. Sorry, maybe it's just that I forgot make depend. But should make do it anyway when no .depend file exists? > > Bruce -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 05:56:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07629 for freebsd-current-outgoing; Thu, 28 May 1998 05:56:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07620 for ; Thu, 28 May 1998 05:56:46 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.0.Beta5/8.9.0.Beta5) id OAA27444; Thu, 28 May 1998 14:43:04 +0200 (SAT) From: John Hay Message-Id: <199805281243.OAA27444@zibbi.mikom.csir.co.za> Subject: Re: 3.0-980520-SNAP In-Reply-To: <199805280916.RAA07165@spinner.netplex.com.au> from Peter Wemm at "May 28, 98 05:16:51 pm" To: peter@netplex.com.au (Peter Wemm) Date: Thu, 28 May 1998 14:43:04 +0200 (SAT) Cc: osa@unibest.ru, dstenn@fanfic.org, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ozz!!! wrote: > > > > > | # named -b /etc/namedb/named.boot > > > | May 27 ......... named[349]: /etc/namedb/named.boot:1: syntax error near; > > > | May 27 ......... named[350]: Ready to answer queries. > > > > > > http://g68.ryd.student.liu.se/doc/bind/manual/?894538148 > > > > > > There is a program you can run to convert your old named.boot to > > > named.conf and this program should be on your system. To convert the file > > > do this. > > > > > > In your /etc/named dir: > > > > > > /usr/local/bin/named-bootconf.pl named.boot > named.conf > > Where can i get this script ? > > Hmm... > > /usr/src/contrib/bind/bin/named/named-bootconf.pl > > But I would have sworn that I'd made this get installed into /etc/namedb > though... > Well on the -current systems here it is in /usr/sbin installed as named-bootconf John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 06:29:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12897 for freebsd-current-outgoing; Thu, 28 May 1998 06:29:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12867 for ; Thu, 28 May 1998 06:29:34 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id VAA08050; Thu, 28 May 1998 21:28:53 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805281328.VAA08050@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Open Systems Networking cc: freebsd-current@FreeBSD.ORG Subject: Re: Latest context switch mods and smp commit In-reply-to: Your message of "Thu, 28 May 1998 08:15:05 -0400." Date: Thu, 28 May 1998 21:28:53 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Open Systems Networking wrote: > Just hope its not quietly trashing my FS or similar quietly in the > background :) > > Chris We don't call it "trashing" the filesystem, we call it "destroying the evidence".. :-) Cheers, -Peter (ps: I just _know_ this comment is going to get me into trouble...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 06:37:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14576 for freebsd-current-outgoing; Thu, 28 May 1998 06:37:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14568 for ; Thu, 28 May 1998 06:37:28 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id VAA08096 for ; Thu, 28 May 1998 21:37:23 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805281337.VAA08096@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: BEWARE - problem with make world can wipe out .h files in src/sys! Date: Thu, 28 May 1998 21:37:23 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Watch out, there is a condition in 'make world' that can cause all your src/sys/{net,sys,vm,netinet,etc..}/*.h files to get deleted. I'm think this only happens with 'make -DNOCLEAN world', and only if there are symlinks in the /usr/obj/tmp/usr/include tree at the point that the world is built. I have committed a fix, but this is a heads up for people building not-quite-current sources with -DNOCLEAN. So, if you have got important changes to src/sys/*/*.h, take a backup copy of them to be sure. Make sure you DO NOT do a 'make -DNOCLEAN world' with rev 1.185 of src/ Makefile. Everything else should be fine (at least, it shouldn't delete your source files....). Looks like I get the pointy hat for this one. Sorry folks... :-( Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 06:43:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA15913 for freebsd-current-outgoing; Thu, 28 May 1998 06:43:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA15608; Thu, 28 May 1998 06:42:04 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id VAA08110; Thu, 28 May 1998 21:41:27 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805281341.VAA08110@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Dom Mitchell cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 In-reply-to: Your message of "Thu, 28 May 1998 08:26:58 +0100." Date: Thu, 28 May 1998 21:41:27 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dom Mitchell wrote: > Peter Wemm writes: > > Before everybody jumps up and says "use xyzmail[er] instead" or "just > > don't ship anything in the base", I'm not sure that we can do that as > > parts of the base *assume* that sendmail (or a workalike) is present. > > VMailer, exim and smail all go to quite strong lengths to be sendmail > compatible. In particular, I've been using exim for some time (over a > year) as a sendmail replacement and found no faults. It's still GPL'd > though. > > And there's still the massive body of sysadmin inertia that *knows* > sendmail... Yes... Sendmail, for all it's warts, is pretty much a known quantity. > Wouldn't it be easier to just stick with 8.8.8 until the licensing > issues of this latest sendmail can be clarified? Yes, that's pretty much what is happening by default. I have asked the sendmail people twice now about this and still have got no response. I might try sending by fax next. I find it quite ironic that people setting up to sell sendmail don't have a handle on email. > > Maybe it's time to bring back a basic local-only mail transport that gets > > blown away when a real sendmail or comparable (qmail, smail, vmailer, > > exim, etc etc) gets installed from a port. Sigh. > > That's certainly one solution; was one of these things used before? > If so, where can I get a look at it? > > P.S. You left out MMDF. :-) MMDF can go away and die. I've wasted too much of my life fighting MMDF (and often loosing).. Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 07:08:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19581 for freebsd-current-outgoing; Thu, 28 May 1998 07:08:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19576 for ; Thu, 28 May 1998 07:08:33 -0700 (PDT) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.8.8/8.8.8) with SMTP id KAA08450 for ; Thu, 28 May 1998 10:08:02 -0400 (EDT) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 28 May 1998 10:08:02 -0400 (EDT) From: "Alok K. Dhir" To: current@FreeBSD.ORG Subject: fastvid? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I saw a note go by about a fastvid LKM for FreeBSD. Sadly, I didn't save it. A search on "freebsd fastvid" on Altavista yielded a tar.gz file for it which was apparently written by John Dyson and modified by Lars Koeller. There was no version information. I was unable to get it to compile - output follows... Several questions: 1. How can I get it to compile? 2. Do I have the latest version? 3. The README makes some mention of SMP, but it is not clear (to me). Will the fastvid LKM work on SMP systems? Thanks! Make output: [shadow:~/fastvid] make Warning: Object directory not changed from original /home/adhir/fastvid cc -O -pipe -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I/home/adhir/fastvid -I/home/adhir/fastvid/@ -c fastvid.c fastvid.c:81: vm/lock.h: No such file or directory In file included from fastvid.c:86: /home/adhir/fastvid/@/vm/vm_map.h:129: field `lock' has incomplete type /home/adhir/fastvid/@/vm/vm_map.h: In function `_vm_map_lock_upgrade': /home/adhir/fastvid/@/vm/vm_map.h:249: warning: implicit declaration of function `lockmgr' /home/adhir/fastvid/@/vm/vm_map.h:249: `LK_EXCLUPGRADE' undeclared (first use this function) /home/adhir/fastvid/@/vm/vm_map.h:249: (Each undeclared identifier is reported only once /home/adhir/fastvid/@/vm/vm_map.h:249: for each function it appears in.) fastvid.c: At top level: fastvid.c:101: warning: initialization from incompatible pointer type fastvid.c:103: parse error before string constant fastvid.c: In function `fastvid_mod': fastvid.c:234: `fastvid_mod_mod_struct' undeclared (first use this function) *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 07:25:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21507 for freebsd-current-outgoing; Thu, 28 May 1998 07:25:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21464; Thu, 28 May 1998 07:25:17 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id WAA08282; Thu, 28 May 1998 22:23:26 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805281423.WAA08282@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm cc: Dom Mitchell , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Sendmail 8.9 In-reply-to: Your message of "Thu, 28 May 1998 21:41:27 +0800." <199805281341.VAA08110@spinner.netplex.com.au> Date: Thu, 28 May 1998 22:23:26 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > Dom Mitchell wrote: > > Wouldn't it be easier to just stick with 8.8.8 until the licensing > > issues of this latest sendmail can be clarified? > > Yes, that's pretty much what is happening by default. I have asked the > sendmail people twice now about this and still have got no response. I > might try sending by fax next. I find it quite ironic that people setting > up to sell sendmail don't have a handle on email. Argh, I take that back, I shouldn't have uttered such crap, especially when I had a reply in my mailbox that I had not yet seen. (And even if it wasn't, this still wasn't appropriate). My big mouth is really going to get me in trouble sooner or later. So, my apologies, especially to the sendmail folks. (I have had a Really Bad Day, not that it's any excuse). -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 08:04:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25703 for freebsd-current-outgoing; Thu, 28 May 1998 08:04:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25690 for ; Thu, 28 May 1998 08:04:05 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from gjallarhorn.ifi.uio.no (2602@gjallarhorn.ifi.uio.no [129.240.65.40]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id RAA19783; Thu, 28 May 1998 17:03:39 +0200 (MET DST) Received: (from dag-erli@localhost) by gjallarhorn.ifi.uio.no ; Thu, 28 May 1998 17:03:39 +0200 (MET DST) Mime-Version: 1.0 To: Bruce Evans Cc: eivind@yes.no, rnordier@nordier.com, current@FreeBSD.ORG Subject: Re: Replacing gcc as the system compiler References: <199805280348.NAA09679@godzilla.zeta.org.au> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 28 May 1998 17:03:38 +0200 In-Reply-To: Bruce Evans's message of "Thu, 28 May 1998 13:48:06 +1000" Message-ID: Lines: 25 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > > There is also what looks like a bug in handling of NULL - it doesn't > > allow the use of ((void *)0) as NULL for function pointers. > gcc used to have this bug too. Apparently, the C standard can easily > be read as not allowing conversion from (void *)0 to a function pointer. > The standard doesn't allow conversion from an object pointer to a > function pointer, but (void *)0 is is a null pointer constant and > null pointer constants are special. The C null pointer constant is 0. No cast is needed. Converting 0 to a function pointer might work better than converting ((void *)0). The only situation in which it is advantageous to define NULL as ((void*)0) instead of just (0) is when passing NULL to a vararg function which lacks a prototype; but you shouldn't do that anyway, because it will break on more than just NULL (float->double conversion for instance) With the correct prototypes, it is perfectly legal and semantically correct to write e.g. execl("/bin/sh", "-sh", 0); -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 08:59:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA02610 for freebsd-current-outgoing; Thu, 28 May 1998 08:59:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from serv.unibest.ru (serv.unibest.ru [194.87.33.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA02584 for ; Thu, 28 May 1998 08:59:50 -0700 (PDT) (envelope-from osa@unibest.ru) Received: (qmail 1743 invoked from network); 28 May 1998 15:59:35 -0000 Received: from unknown (HELO hole.etrust.ru) (192.168.30.2) by serv.unibest.ru with SMTP; 28 May 1998 15:59:35 -0000 Date: Thu, 28 May 1998 20:02:55 +0400 (MSD) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: FreeBSD-current mail-list Subject: strange with who command... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! In my 3.0-980520-SNAP i say ( in xterm ): $ who osa ttyv0 28 May 19:57 osa ttyv1 28 May 19:57 (:0.0) ... ... ... then I down X-server & say: $ who osa ttyv0 28 May 19:57 osa ttyv1 28 May 19:57 (:0.0) ... ... ... I logoff from system, then logon & say: $ who osa ttyv0 28 May 19:59 osa ttyv1 28 May 19:57 (:0.0) Strange ?? Rgdz, oZZ, osa@unibest.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 09:20:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05036 for freebsd-current-outgoing; Thu, 28 May 1998 09:20:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05008 for ; Thu, 28 May 1998 09:19:58 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA01183; Thu, 28 May 1998 16:19:51 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA21845; Thu, 28 May 1998 18:19:39 +0200 (MET DST) Message-ID: <19980528181930.06204@follo.net> Date: Thu, 28 May 1998 18:19:30 +0200 From: Eivind Eklund To: =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= Cc: current@FreeBSD.ORG Subject: Re: Replacing gcc as the system compiler References: <199805280348.NAA09679@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.89.1i In-Reply-To: =?iso-8859-1?Q?=3Cxzpra1ecu9h=2Efsf=40gjallarhorn=2Eifi=2Euio=2Eno=3E=3B?= =?iso-8859-1?Q?_from_Dag-Erling_Coidan_Sm=F8rgrav__on_Thu=2C_May_28=2C_1?= =?iso-8859-1?Q?998_at_05=3A03=3A38PM_+0200?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 05:03:38PM +0200, Dag-Erling Coidan Smørgrav wrote: > Bruce Evans writes: > > > There is also what looks like a bug in handling of NULL - it doesn't > > > allow the use of ((void *)0) as NULL for function pointers. > > gcc used to have this bug too. Apparently, the C standard can easily > > be read as not allowing conversion from (void *)0 to a function pointer. > > The standard doesn't allow conversion from an object pointer to a > > function pointer, but (void *)0 is is a null pointer constant and > > null pointer constants are special. > > The C null pointer constant is 0. No cast is needed. Converting 0 to a > function pointer might work better than converting ((void *)0). The C null pointer constant _can be_ 0. Chapter and verse is (from the working draft, which is what I have online): Section 6.2.2.3, item 3. 3. An integer constant expression with the value 0, or such an expression cast to type void *, is called a null pointer constant.[53] If a null pointer constant is assigned to or compared for equality to a pointer, the constant is converted to a pointer of that type. Such a pointer, called a null pointer, is guaranteed to compare unequal to a pointer to any object or function. If you read this carefully, you will see this carefully allow the use of ((void*)0). It also allow expressions like ((void*)(14L-2L*7U)), but they are of somewhat dubious use - possibly useful for testing that the constant elimination in your compiler is done as early as it is required to. > The only situation in which it is advantageous to define NULL as > ((void*)0) instead of just (0) is when passing NULL to a vararg > function which lacks a prototype; but you shouldn't do that anyway, > because it will break on more than just NULL (float->double conversion > for instance) It is of advantage when some retarded pseudo-programmer have left int i = NULL; and other similar statements everywhere in the code and I want that to break. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 09:35:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06755 for freebsd-current-outgoing; Thu, 28 May 1998 09:35:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06750 for ; Thu, 28 May 1998 09:35:47 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id JAA21689; Thu, 28 May 1998 09:33:08 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd021685; Thu May 28 16:33:04 1998 Date: Thu, 28 May 1998 09:32:58 -0700 (PDT) From: Julian Elischer To: Peter Wemm cc: current@FreeBSD.ORG Subject: Re: BEWARE - problem with make world can wipe out .h files in src/sys! In-Reply-To: <199805281337.VAA08096@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's not only make -DNOCLEAN I don't have that set, however I think you got it anyhow as t survived a bit longer this time before falling over the fact that /usr/obj/usr/src/tmp (a separate filesysytem here) filled up Its probably due to all the files in usr/lib being duplicated in usr/lib/aout instead of being just installed there to start with. There's a 10 minute difference in thetimestamps between them. Unfortunatly I sized /usr/obj/usr/src/tmp pretty close thinking "this isn't going to grow THAT much". julian On Thu, 28 May 1998, Peter Wemm wrote: > Watch out, there is a condition in 'make world' that can cause all your > src/sys/{net,sys,vm,netinet,etc..}/*.h files to get deleted. I'm think > this only happens with 'make -DNOCLEAN world', and only if there are > symlinks in the /usr/obj/tmp/usr/include tree at the point that the world > is built. > > I have committed a fix, but this is a heads up for people building > not-quite-current sources with -DNOCLEAN. > > So, if you have got important changes to src/sys/*/*.h, take a backup copy > of them to be sure. > > Make sure you DO NOT do a 'make -DNOCLEAN world' with rev 1.185 of src/ > Makefile. Everything else should be fine (at least, it shouldn't delete > your source files....). > > Looks like I get the pointy hat for this one. Sorry folks... :-( > > Cheers, > -Peter > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 10:55:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17533 for freebsd-current-outgoing; Thu, 28 May 1998 10:55:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA17527 for ; Thu, 28 May 1998 10:55:02 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 28030 invoked from network); 28 May 1998 17:54:57 -0000 Received: from usera900.uk.uudial.com (HELO jfsebastian) (193.149.69.138) by smtp.dial.pipex.com with SMTP; 28 May 1998 17:54:57 -0000 Message-ID: <000101bd8a61$18e60330$0242000a@jfsebastian.k2c.co.uk> From: "Pierre Y. Dampure" To: Subject: Problems with ps on -current Date: Thu, 28 May 1998 18:50:26 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Output of ps ax on -current cvsupped 28/05/1998 16:00 BST : PID TT STAT TIME COMMAND 0 ?? DLs 78383:09.19 (swapper) 1 ?? Is 2935109:04.04 /sbin/init -- 2 ?? DL 73658:41.35 (pagedaemon) 3 ?? DL 572:39.74 (vmdaemon) 4 ?? DL 1338240:13.60 (syncer) 28 ?? Ss 31544959:58.07 mfs /dev/sd0s1b /tmp (mount_mfs) 47 ?? Is 328278:40.02 adjkerntz -i 106 ?? Ss 5990548:48.10 syslogd 116 ?? Is 580894:19.61 portmap 140 ?? Is 2881064:03.73 inetd 143 ?? Is 1673247:40.54 cron 147 ?? Is 830217:10.70 lpd 150 ?? Ss 1218052:43.51 sendmail: accepting connections on port 25 (sendmail) 183 ?? Is 449396:44.68 moused -p /dev/psm0 -t auto 203 v0 Ss 27825017:12.60 -bash (bash) 251 v0 R+ 226058:26.72 ps -ax 204 v1 Is+ 2079766:19.82 /usr/libexec/getty Pc ttyv1 205 v2 Is+ 1556639:18.82 /usr/libexec/getty Pc ttyv2 206 v3 Is+ 1363222:37.19 /usr/libexec/getty Pc ttyv3 207 v4 Is+ 1762869:19.60 /usr/libexec/getty Pc ttyv4 208 v5 Is+ 1658859:32.12 /usr/libexec/getty Pc ttyv5 209 v6 Is+ 1536023:28.24 /usr/libexec/getty Pc ttyv6 210 v7 Is+ 1666375:43.68 /usr/libexec/getty Pc ttyv7 211 v8 Is+ 1433015:50.30 /usr/libexec/getty Pc ttyv8 212 v9 Is+ 1505099:42.37 /usr/libexec/getty Pc ttyv9 213 va Is+ 1418556:06.90 /usr/libexec/getty Pc ttyva 214 vb Is+ 1506459:46.74 /usr/libexec/getty Pc ttyvb Given that I just rebootd my box, me thinks we might have a small issue there.... Best Regards, Pierre Y. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 11:08:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20603 for freebsd-current-outgoing; Thu, 28 May 1998 11:08:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from monsoon.dial.pipex.net (monsoon.dial.pipex.net [158.43.128.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA20583 for ; Thu, 28 May 1998 11:08:04 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: (qmail 1870 invoked from network); 28 May 1998 18:08:02 -0000 Received: from usera753.uk.uudial.com (HELO jfsebastian) (193.149.68.245) by smtp.dial.pipex.com with SMTP; 28 May 1998 18:08:02 -0000 Message-ID: <002801bd8a62$eccb3390$0242000a@jfsebastian.k2c.co.uk> From: "Pierre Y. Dampure" To: Subject: Re: Problems with ps on -current Date: Thu, 28 May 1998 19:03:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ooops... my mistake, the kernel didn't get rebuilt, everything's och aye now, flames on me... Best Regards, Pierre Y. -----Original Message----- From: Pierre Y. Dampure To: current@freebsd.org Date: 28 May 1998 18:50 Subject: Problems with ps on -current >Output of ps ax on -current cvsupped 28/05/1998 16:00 BST : > > PID TT STAT TIME COMMAND > 0 ?? DLs 78383:09.19 (swapper) > 1 ?? Is 2935109:04.04 /sbin/init -- > 2 ?? DL 73658:41.35 (pagedaemon) > 3 ?? DL 572:39.74 (vmdaemon) > 4 ?? DL 1338240:13.60 (syncer) > 28 ?? Ss 31544959:58.07 mfs /dev/sd0s1b /tmp (mount_mfs) > 47 ?? Is 328278:40.02 adjkerntz -i > 106 ?? Ss 5990548:48.10 syslogd > 116 ?? Is 580894:19.61 portmap > 140 ?? Is 2881064:03.73 inetd > 143 ?? Is 1673247:40.54 cron > 147 ?? Is 830217:10.70 lpd > 150 ?? Ss 1218052:43.51 sendmail: accepting connections on port 25 >(sendmail) > 183 ?? Is 449396:44.68 moused -p /dev/psm0 -t auto > 203 v0 Ss 27825017:12.60 -bash (bash) > 251 v0 R+ 226058:26.72 ps -ax > 204 v1 Is+ 2079766:19.82 /usr/libexec/getty Pc ttyv1 > 205 v2 Is+ 1556639:18.82 /usr/libexec/getty Pc ttyv2 > 206 v3 Is+ 1363222:37.19 /usr/libexec/getty Pc ttyv3 > 207 v4 Is+ 1762869:19.60 /usr/libexec/getty Pc ttyv4 > 208 v5 Is+ 1658859:32.12 /usr/libexec/getty Pc ttyv5 > 209 v6 Is+ 1536023:28.24 /usr/libexec/getty Pc ttyv6 > 210 v7 Is+ 1666375:43.68 /usr/libexec/getty Pc ttyv7 > 211 v8 Is+ 1433015:50.30 /usr/libexec/getty Pc ttyv8 > 212 v9 Is+ 1505099:42.37 /usr/libexec/getty Pc ttyv9 > 213 va Is+ 1418556:06.90 /usr/libexec/getty Pc ttyva > 214 vb Is+ 1506459:46.74 /usr/libexec/getty Pc ttyvb > >Given that I just rebootd my box, me thinks we might have a small issue >there.... > > >Best Regards, > > >Pierre Y. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 11:12:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21576 for freebsd-current-outgoing; Thu, 28 May 1998 11:12:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21571 for ; Thu, 28 May 1998 11:12:53 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id NAA11462; Thu, 28 May 1998 13:11:00 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id NAA01183; Thu, 28 May 1998 13:12:16 -0500 (CDT) (envelope-from joelh) Date: Thu, 28 May 1998 13:12:16 -0500 (CDT) Message-Id: <199805281812.NAA01183@detlev.UUCP> To: freebsd-current@FreeBSD.ORG Subject: sio0 flag 0x20000 From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is sio0 flag 0x20000 (enable 16550A features) in proper functioning order? I enabled it on a whim, and got strange effects in ppp (ie, login works fine, but during LQR negotiations, the other side doesn't see config-req or config-ack). Disabled it in bootconfig, and all is well. The probe reports the chip as a 16550A... is that reliable? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 11:21:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22694 for freebsd-current-outgoing; Thu, 28 May 1998 11:21:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22686 for ; Thu, 28 May 1998 11:21:09 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id NAA11908; Thu, 28 May 1998 13:19:50 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id NAA01231; Thu, 28 May 1998 13:21:06 -0500 (CDT) (envelope-from joelh) Date: Thu, 28 May 1998 13:21:06 -0500 (CDT) Message-Id: <199805281821.NAA01231@detlev.UUCP> To: kpielorz@caladan.tdx.co.uk CC: current@FreeBSD.ORG In-reply-to: (message from Karl Pielorz on Thu, 28 May 1998 00:07:15 +0100 (BST)) Subject: Re: aha1542 - again... From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I read a while ago there were problems with the existing AHA1542 support > on -current... I also read that someone (I can't remember now who it was) > said they'd been through the code and fixed up a few things... [snip] > I know CAM is looking almost 'immanent' - but can anyone confirm whether > the 1542 driver is in any useable state in -current at the moment? Well, I can tell you at least that I'm using one on a week-old -current, with no worries. The box is a ISA/EISA/VLB 486, AHA1542CF presently with two HDDs, a CD-ROM, and a CD-R. Note that my box only has 16 MB, which means anything bounce buffer-related will not hit me. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 11:30:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23824 for freebsd-current-outgoing; Thu, 28 May 1998 11:30:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23797 for ; Thu, 28 May 1998 11:30:03 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id NAA12458; Thu, 28 May 1998 13:28:20 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id NAA01253; Thu, 28 May 1998 13:29:34 -0500 (CDT) (envelope-from joelh) Date: Thu, 28 May 1998 13:29:34 -0500 (CDT) Message-Id: <199805281829.NAA01253@detlev.UUCP> To: rnordier@nordier.com CC: eivind@yes.no, current@FreeBSD.ORG In-reply-to: <199805271551.RAA11565@ceia.nordier.com> (message from Robert Nordier on Wed, 27 May 1998 17:51:11 +0200 (SAT)) Subject: Re: Fix for undefined "__error" and discussion of shared object versioning From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199805271551.RAA11565@ceia.nordier.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I've sent off a mail to the contact person for the TenDRA team; I'll >> wait and see that they say about the feasibility of using TenDRA as an >> OS compiler. > This was the subject of an Open Group research study (involving UnixWare > and Linux) around 1995. (Fairly obviously, it is feasible.) > The critical issue, however, is really whether it is feasible to > compile *FreeBSD* with a non-GCC compiler. Any real problems will > be due to FreeBSD (GCC quirks in the code) not to the compiler. > (There are no fundamental difficulties inherent in compiling > UNIX-like systems). My own concern would be the amount of code in third-party programs that uses gccisms. I guess I don't see why we're looking to change. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 11:41:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25381 for freebsd-current-outgoing; Thu, 28 May 1998 11:41:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-120.joh.za.ibm.net [139.92.122.120]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25359 for ; Thu, 28 May 1998 11:41:06 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id UAA26210; Thu, 28 May 1998 20:35:10 +0200 (SAT) From: Robert Nordier Message-Id: <199805281835.UAA26210@ceia.nordier.com> Subject: Re: Replacing gcc as the system compiler In-Reply-To: from =?ISO-8859-1?Q?Dag=2DErling_Coidan_Sm=F8rgrav?= at "May 28, 98 05:03:38 pm" To: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Thu, 28 May 1998 20:35:07 +0200 (SAT) Cc: bde@zeta.org.au, eivind@yes.no, rnordier@nordier.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Coidan Smørgrav wrote: > Bruce Evans writes: > > > There is also what looks like a bug in handling of NULL - it doesn't > > > allow the use of ((void *)0) as NULL for function pointers. > > gcc used to have this bug too. Apparently, the C standard can easily > > be read as not allowing conversion from (void *)0 to a function pointer. > > The standard doesn't allow conversion from an object pointer to a > > function pointer, but (void *)0 is is a null pointer constant and > > null pointer constants are special. > > The C null pointer constant is 0. No cast is needed. Converting 0 to a > function pointer might work better than converting ((void *)0). Bruce is talking about null pointer constants as referred to in the C standard. Both 0 and (void *)0 are equally "null pointer constants" and must work equally well in relevant contexts. > The only situation in which it is advantageous to define NULL as > ((void*)0) instead of just (0) is when passing NULL to a vararg > function which lacks a prototype; but you shouldn't do that anyway, > because it will break on more than just NULL (float->double conversion > for instance) > > With the correct prototypes, it is perfectly legal and semantically > correct to write e.g. > > execl("/bin/sh", "-sh", 0); I'm not sure why you feel the correct prototype int execl(const char *, const char *, ...); has a significant effect in this case. The ellipsis doesn't mean "more of the same", it means "no information as to number and type of parameters is available". Your example may actually fail in environments that have, for example, 16-bit ints and 32-bit pointers (which are, of course, extremely common :-). (That was a troll, wasn't it?) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 11:55:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27718 for freebsd-current-outgoing; Thu, 28 May 1998 11:55:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27698 for ; Thu, 28 May 1998 11:55:39 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id LAA26385; Thu, 28 May 1998 11:55:28 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd026285; Thu May 28 11:55:24 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id LAA22268; Thu, 28 May 1998 11:55:17 -0700 (MST) From: Terry Lambert Message-Id: <199805281855.LAA22268@usr09.primenet.com> Subject: Re: Fix for undefined "__error" and discussion of shared object To: smp@csn.net (Steve Passe) Date: Thu, 28 May 1998 18:55:17 +0000 (GMT) Cc: jdp@polstra.com, jb@cimlogic.com.au, tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199805261531.JAA22406@Ilsa.StevesCafe.com> from "Steve Passe" at May 26, 98 09:31:11 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > BTW, what's you opinion of egcs? > > > > It seems to have frequent ups and downs. We have been using the > > Feb. 21 snapshot for a fairly large C++ project that I'm involved > > with, and we haven't had any show-stopper problems. But I believe > > some of the other team members tried a later snapshot and ran into all > > sorts of bugs. > > > > One thing I can say is that the template support is immeasurably > > better than what was in gcc-2.7.2. I haven't tried gcc-2.8.1, but > > I've heard that its C++ support is much improved over 2.7.2 as well. > > We're doing a complex c++/pthreads project and found that neither 2.7.2 or > 2.8.1 worked for us, but an egcs snap from several months ago works well. The egcs code *requires* that all your code be either threaded or unthreaded. You must make this decision at the time you compile the compiler. The gcc 2.8.1 code *requires* the patches Jeremey Allison did (and which are in the FreeBSD port now, AFAIK) to support per thread exception stacks. The STL needs a number of changes to allow you to successfully use the STL threading capable functions, since it tries to statically initialize mutexes, and you can't do that with POSIX Draft 4 pthreads mutexes. We were doing a complex C++/threads project, and were only able to make it work with g++ 2.8.1. Basically, we ported the ACAP server to FreeBSD. AFAIK, this is the first time ACAP has been successfully run on a g++/egcs based platform, ever. There are a number ofvalid semantic constructs that both g++ and egcs tend to barf on. The egcs code tends to piss me off, both because it sometimes makes optimizations that are invalid (c.v.: the "octave" port), and the need to eat the overhead of threads in all programs if you want to use threads and exceptions in any one program. I guess the theory is that we should all buy faster processors. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 12:12:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01378 for freebsd-current-outgoing; Thu, 28 May 1998 12:12:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (slip139-92-122-118.joh.za.ibm.net [139.92.122.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01215 for ; Thu, 28 May 1998 12:12:05 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.8/8.6.12) id VAA26880; Thu, 28 May 1998 21:05:44 +0200 (SAT) From: Robert Nordier Message-Id: <199805281905.VAA26880@ceia.nordier.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805281829.NAA01253@detlev.UUCP> from Joel Ray Holveck at "May 28, 98 01:29:34 pm" To: joelh@gnu.org Date: Thu, 28 May 1998 21:05:42 +0200 (SAT) Cc: rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joel Ray Holveck wrote: > > The critical issue, however, is really whether it is feasible to > > compile *FreeBSD* with a non-GCC compiler. Any real problems will > > be due to FreeBSD (GCC quirks in the code) not to the compiler. > > (There are no fundamental difficulties inherent in compiling > > UNIX-like systems). > > My own concern would be the amount of code in third-party programs > that uses gccisms. I guess I don't see why we're looking to change. A reasonable point. TenDRA does have a more relaxed mode, but there are various things it can't handle. For instance, using cast expressions as lvalues (perhaps that's a pc-ism). I only want to be *able* to change: If you love gcc, let it go. If it stays, it is suitable If not, it never was. 8-) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 12:27:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04001 for freebsd-current-outgoing; Thu, 28 May 1998 12:27:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03991 for ; Thu, 28 May 1998 12:27:35 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id TAA07560; Thu, 28 May 1998 19:27:29 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA22773; Thu, 28 May 1998 21:27:14 +0200 (MET DST) Message-ID: <19980528212713.63593@follo.net> Date: Thu, 28 May 1998 21:27:13 +0200 From: Eivind Eklund To: joelh@gnu.org, rnordier@nordier.com Cc: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <199805271551.RAA11565@ceia.nordier.com> <199805281829.NAA01253@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805281829.NAA01253@detlev.UUCP>; from Joel Ray Holveck on Thu, May 28, 1998 at 01:29:34PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 01:29:34PM -0500, Joel Ray Holveck wrote: > My own concern would be the amount of code in third-party programs > that uses gccisms. I guess I don't see why we're looking to change. Well, here are a couple of points: * License * General quality of system (GCC is written under the paradigm 'learn writing compilers as we go') * Possibilities for exploiting the cross-CPU nature of XANDF * Better error checking/control * Choice (by being able to be compiled with more than one compiler) They might not be enough to be persuative, but they are at least in favour. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 12:35:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05241 for freebsd-current-outgoing; Thu, 28 May 1998 12:35:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay1.kar.net (relay1.kar.net [195.5.17.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05232 for ; Thu, 28 May 1998 12:35:06 -0700 (PDT) (envelope-from kushn@mail.kar.net) Received: from olinet.isf.kiev.ua by relay1.kar.net with ESMTP id WAA15549; (8.8.last/vAk3/1.9) Thu, 28 May 1998 22:21:18 +0300 (EEST) Received: from kushnir.kiev.ua by olinet.isf.kiev.ua with SMTP id WAA16787; (8.8.last/vAk3/1.9) Thu, 28 May 1998 22:11:05 +0300 (EET DST) Date: Thu, 28 May 1998 22:18:56 +0300 (EEST) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: Peter Wemm cc: current@FreeBSD.ORG Subject: Re: -current breakage In-Reply-To: <199805281101.TAA07561@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 May 1998, Peter Wemm wrote: > Vladimir Kushnir wrote: > > > > > > > > On Thu, 28 May 1998, Hostas Red wrote: > > > > > Hi! > > > > > > cvsup'ed just few minutes ago, make world fail on 10th minute of building: > > > > > > cd /usr/src/include/../sys; install -C -o bin -g bin -m 444 net/*.h > > > /usr/obj/usr/src/tmp/usr/include/net > > > install: net/*.h: No such file or directory > > > *** Error code 71 > > > 1 error > > > *** Error code 2 > > > 1 error > > > *** Error code 2 > > > 1 error > > > *** Error code 2 > > > 1 error > > > > > > Adios, > > > /KONG > > > > Same here, and even worse: somehow buildworld wiped all of sys/sys/*.h, > > sys/net/*.h probably something else as well. > > > > Regards, > > Vladimir > > > > Do you have CLOBBER defined by any chance? I'm suspicious of the > following section of src/Makefile: > > includes: > .if defined(CLOBBER) > rm -rf ${DESTDIR}/usr/include/* > mtree -deU -f ${.CURDIR}/etc/mtree/BSD.include.dist \ > -p ${DESTDIR}/usr/include > .endif > > There are some rm -rf's in src/include/Makefile as well. However, neither > of these should really be a problem unless rm has started following > symlinks or there's something odd going on. > > > Cheers, > -Peter > -- > Peter Wemm Netplex Consulting > No, I just did "make -DNOCLEAN buildworld" (there was some interrupted buildworld by then). Besides, it didn't rm /usr/src/include - some other directories were wiped away (like /usr/src/sys/sys and so on - sorry, can't say more exactly, I've already restored /usr/src). BTW, that was CTM src-cur.3398 (the last one.. err.. one before the last already). Regards, Vladimir To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 12:41:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06493 for freebsd-current-outgoing; Thu, 28 May 1998 12:41:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06475 for ; Thu, 28 May 1998 12:41:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00744; Thu, 28 May 1998 11:36:37 -0700 (PDT) Message-Id: <199805281836.LAA00744@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Eivind Eklund cc: Robert Nordier , current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Wed, 27 May 1998 18:23:37 +0200." <19980527182337.47243@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 11:36:37 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It think the difficult issues here are linker sets and assembly. > There are a few places where the code use GCC extensions to the > preprocessor, but removing this has been on my TODO list for some > time. Actually, a better idea would be to fix the preprocessor to handle these things. Partly because many of these extensions are really useful, and partly because otherwise we'll be stuck with having to have two compilers just so we can compile ports and the like that insist on gcc. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 12:42:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA06785 for freebsd-current-outgoing; Thu, 28 May 1998 12:42:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA06745 for ; Thu, 28 May 1998 12:42:23 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA11422; Thu, 28 May 1998 13:41:51 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA20236; Thu, 28 May 1998 13:41:48 -0600 Date: Thu, 28 May 1998 13:41:48 -0600 Message-Id: <199805281941.NAA20236@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: joelh@gnu.org Cc: rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805281829.NAA01253@detlev.UUCP> References: <199805271551.RAA11565@ceia.nordier.com> <199805281829.NAA01253@detlev.UUCP> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Replacing GCC with TenDra ] > My own concern would be the amount of code in third-party programs > that uses gccisms. Very few programs *should* use gccisms. If they do, they are broke since they won't build on other OS's compilers. > I guess I don't see why we're looking to change. Better/faster/less buggy compiler with a much less restrictive Copyright seems like a win overall to me. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 12:45:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07690 for freebsd-current-outgoing; Thu, 28 May 1998 12:45:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07682 for ; Thu, 28 May 1998 12:45:48 -0700 (PDT) (envelope-from paulz@trantor.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <4108-9473> convert rfc822-to-8bit; Thu, 28 May 1998 21:45:28 +0200 Received: from trantor.stuyts.nl (uucp@localhost) by terminus.stuyts.nl (8.8.8/8.8.8) with UUCP id VAA24603; Thu, 28 May 1998 21:39:37 +0200 (MET DST) (envelope-from paulz@trantor.stuyts.nl) Received: from trantor.stuyts.nl (localhost [127.0.0.1]) by trantor.stuyts.nl (8.8.8/8.8.5) with ESMTP id UAA15963; Thu, 28 May 1998 20:45:52 +0200 (MET DST) Message-Id: <199805281845.UAA15963@trantor.stuyts.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Dufault Subject: Re: cdrecord trouble on currnet In-reply-to: Your message of "Thu, 28 May 1998 07:34:50 EDT." <199805281134.HAA20418@hda.hda.com> cc: freebsd-current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Date: Thu, 28 May 1998 20:45:51 +0200 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > I am getting write errors on my Philips 2600 CD-R using cd-write and burncd.sh > > (from /usr/share/examples/worm/ ) so I thought , I'l compile cdrecord and try > > that. But I get the following error when truying to do a dummy burn: > > > > $ sudo cdrecord -dev=0,4,0 -data -dummy /scratch/img/psnl > > Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling > > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler > > Bus error (core dumped) > > > > > > This is a freshly compiled port on a current cvsupped today. > > (I wonder why he is trying to use the round robin scheduler - I > expect he wants the FIFO one). > > Cdrecord has autoconf'd in the P1003.1B scheduler interface. > > I'm probably going to have to change how I did things, but the > program may need fixing also. By default, with nothing defined, > the new system calls are setup to be LKM'd in for development and > will fail at run time with ENOSYS or if you check for their presense > with sysconf(). > You can add build time support with the _KPOSIX_PRIORITY_SCHEDULING > option in the kernel. > > See how cdrecord is deciding to use priority scheduling. If it > decides that a program that links OK without checking any compile > time feature test macros means that priority scheduling is supported, > then that should be changed. I've been told some programs are > doing this (not specifically cdrecord). I looked at the cdrecord source and the code calling sched_scheduler is in an #ifdef _POSIX_PRIORITY_SCHEDULING block. Apperently that gets defined in /usr/include/sys/unistd.h because _posix.h defines _P1003_1B_VISIBLE > > If you set _POSIX_C_SOURCE to 199009L with a -D in the makefile > and cderecord still tries to use the round robin scheduler then > someone has screwed up - either us or cdrecord - so try that too. > I recompile it uing the define and it seems to be working. No crash and it is now performing a dummy burn. Paul -- Paul van der Zwan paulz @ trantor.stuyts.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 12:53:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09904 for freebsd-current-outgoing; Thu, 28 May 1998 12:53:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09899 for ; Thu, 28 May 1998 12:53:35 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00873; Thu, 28 May 1998 11:48:54 -0700 (PDT) Message-Id: <199805281848.LAA00873@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Paul van der Zwan cc: freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet In-reply-to: Your message of "Wed, 27 May 1998 16:25:34 +0200." <199805271425.QAA00517@trantor.stuyts.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 28 May 1998 11:48:54 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA09900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I am getting write errors on my Philips 2600 CD-R using cd-write and burncd.sh > (from /usr/share/examples/worm/ ) so I thought , I'l compile cdrecord and try > that. But I get the following error when truying to do a dummy burn: > > $ sudo cdrecord -dev=0,4,0 -data -dummy /scratch/img/psnl > Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler > Bus error (core dumped) This is an arguable bug in cdrecord. Use the 2.2.6 package instead. I'm working on a CAM port of cdrecord, but the code quality is hampering my efforts. 8( -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 13:02:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11928 for freebsd-current-outgoing; Thu, 28 May 1998 13:02:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11910 for ; Thu, 28 May 1998 13:02:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA00920; Thu, 28 May 1998 11:56:54 -0700 (PDT) Message-Id: <199805281856.LAA00920@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: mike@smith.net.au, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: Argh! errno spam! In-reply-to: Your message of "Thu, 28 May 1998 11:35:33 +1000." <199805280135.LAA00604@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 11:56:54 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >There are a few perfectly good reasons to call a structure member errno, > >but regardless of the good reasons, I fear for the code in the ports > >collection. 8( > > I'd like the ports collection to be compiled routinely under -current. > Even if it doesn't compile, the breakage list would be interesting. You can either do this yourself, or request that a volunteer do it for you. Bento is equipped to build ports under -current, and you should have no access problems. > >I was bitten by this with the NetBSD-derived bootcode I'm working on, > >which doesn't use libc and thus needs its own errno in order to be a > >reasonable facsimile therof. (Yes, I have a workaround.) > > errno shouldn't be defined for non-libc interfaces. You probably got > bitten by namespace pollution. KERNEL must be defined to stop errno > being defined in our errno.h. Actually, the NetBSD code was written to think it was "like" the kernel, so it includes . We define the errno macro there, not in . Defining KERNEL resolves the issue for this application at least. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 13:04:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12307 for freebsd-current-outgoing; Thu, 28 May 1998 13:04:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12186 for ; Thu, 28 May 1998 13:04:10 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id WAA00597; Thu, 28 May 1998 22:02:09 +0200 (CEST) To: "Pierre Y. Dampure" cc: current@FreeBSD.ORG Subject: Re: Problems with ps on -current In-reply-to: Your message of "Thu, 28 May 1998 18:50:26 BST." <000101bd8a61$18e60330$0242000a@jfsebastian.k2c.co.uk> Date: Thu, 28 May 1998 22:02:09 +0200 Message-ID: <595.896385729@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Given that I just rebootd my box, me thinks we might have a small issue >there.... Absolutely a small issue. Just recompile ps & top. And read cvs commit messages in the future. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 13:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13014 for freebsd-current-outgoing; Thu, 28 May 1998 13:06:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12970 for ; Thu, 28 May 1998 13:06:27 -0700 (PDT) (envelope-from dmaddox@scsn.net) Received: from rhiannon.scsn.net ([208.133.153.96]) by mail.scsn.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-41950U6000L1100S0) with ESMTP id AAA315; Thu, 28 May 1998 16:00:41 -0400 Received: (from root@localhost) by rhiannon.scsn.net (8.8.8/8.8.8) id QAA00764; Thu, 28 May 1998 16:06:40 GMT (envelope-from root) Message-ID: <19980528160640.A747@scsn.net> Date: Thu, 28 May 1998 16:06:40 +0000 From: dmaddox@scsn.net (Donald J. Maddox) To: joelh@gnu.org, freebsd-current@FreeBSD.ORG Subject: Re: sio0 flag 0x20000 Reply-To: dmaddox@scsn.net Mail-Followup-To: joelh@gnu.org, freebsd-current@FreeBSD.ORG References: <199805281812.NAA01183@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805281812.NAA01183@detlev.UUCP>; from Joel Ray Holveck on Thu, May 28, 1998 at 01:12:16PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 01:12:16PM -0500, Joel Ray Holveck wrote: > Is sio0 flag 0x20000 (enable 16550A features) in proper functioning > order? I enabled it on a whim, and got strange effects in ppp (ie, > login works fine, but during LQR negotiations, the other side doesn't > see config-req or config-ack). Disabled it in bootconfig, and all is > well. > > The probe reports the chip as a 16550A... is that reliable? The 0x20000 flag is for use with 16>6<50s, not 16550s... ^ During the brief time when it was enabled by default, it caused problems with my 16550A-clone serial ports, but it works fine for the 16650-based LavaPort I have... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 13:15:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15332 for freebsd-current-outgoing; Thu, 28 May 1998 13:15:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15240 for ; Thu, 28 May 1998 13:15:04 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA04296; Thu, 28 May 1998 15:08:40 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id PAA01643; Thu, 28 May 1998 15:09:40 -0500 (CDT) (envelope-from joelh) Date: Thu, 28 May 1998 15:09:40 -0500 (CDT) Message-Id: <199805282009.PAA01643@detlev.UUCP> To: rnordier@nordier.com CC: eivind@yes.no, current@FreeBSD.ORG In-reply-to: <199805281905.VAA26880@ceia.nordier.com> (message from Robert Nordier on Thu, 28 May 1998 21:05:42 +0200 (SAT)) Subject: Re: Fix for undefined "__error" and discussion of shared object versioning From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199805281905.VAA26880@ceia.nordier.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> The critical issue, however, is really whether it is feasible to >>> compile *FreeBSD* with a non-GCC compiler. Any real problems will >>> be due to FreeBSD (GCC quirks in the code) not to the compiler. >>> (There are no fundamental difficulties inherent in compiling >>> UNIX-like systems). >> My own concern would be the amount of code in third-party programs >> that uses gccisms. I guess I don't see why we're looking to change. > A reasonable point. TenDRA does have a more relaxed mode, but > there are various things it can't handle. For instance, using cast > expressions as lvalues (perhaps that's a pc-ism). No, you're right, casts as lvalues is a gccism (along with ?: and , in lvalues). My main concerns are inline, long long, typeof, nested functions, and extensions to asm. Now, I'll grant you that the last three we most frequently get in through software from the GNU/Linux camps, but I still like the software and want to be able to use it. A question: Who knows how we are on gccisms in our assembly routines? > I only want to be *able* to change: > If you love gcc, let it go. > If it stays, it is suitable > If not, it never was. > 8-) Cute. :-) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 13:21:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17116 for freebsd-current-outgoing; Thu, 28 May 1998 13:21:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17085 for ; Thu, 28 May 1998 13:21:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA01071; Thu, 28 May 1998 12:15:11 -0700 (PDT) Message-Id: <199805281915.MAA01071@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Danny Dulai cc: Mikhail Teterin , current@FreeBSD.ORG Subject: Re: TenDRA C++ In-reply-to: Your message of "Thu, 28 May 1998 02:04:41 CDT." <19980528020441.63901@bleep.ishiboo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 12:15:11 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Quoting Mikhail Teterin (mi@video-collage.com): > > Alex Povolotsky once stated: > > > > =I've tried to compile Qt with TenDRA, and got more errors than I've > > =got earlier this year at all ;-) Looks like TenDRA has SOMETHING very > > =different from GCC inside it. > > > > gcc-2.8.1 does not compile Qt either. Or, rather, it compiles, but the > > resulting object files can not be linked together. Same with KDE stuff. > > I couldn't get it to work wtih 2.7.2.1 either, unless, when I linked, I > specified -lqt -lqt -lqt. Did you remember to feed the library to ranlib? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 13:23:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17662 for freebsd-current-outgoing; Thu, 28 May 1998 13:23:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17570 for ; Thu, 28 May 1998 13:23:18 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id WAA29600; Thu, 28 May 1998 22:24:20 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 28 May 1998 22:24:19 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: Cory Kempf , freebsd-current@FreeBSD.ORG Subject: Re: sio and dk440lx In-Reply-To: <199805260701.AAA00753@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 26 May 1998, Mike Smith wrote: > > Hi again, > > my serial ports don't seem to want to work. > > > > According to the intel docs, com1&2 should be at 0x3f8 and 0x2f8 respectively. > > Dmesg says sio0 not found at 0x3f8, sio1 not found at 0x2f8. > > The DK440LX ('Atlanta') board is believed to work just fine. > > > Anyone have an idea why not? > > You may have disabled the ports in the BIOS setup. As an owner (or rather: admin) of Dakota-based machine, I can confirm that the ports work ok, and that BIOS allows for some extreme tweaking of their settings.. Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 13:38:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21071 for freebsd-current-outgoing; Thu, 28 May 1998 13:38:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21046 for ; Thu, 28 May 1998 13:38:26 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA05293; Thu, 28 May 1998 15:23:35 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id PAA01692; Thu, 28 May 1998 15:24:32 -0500 (CDT) (envelope-from joelh) Date: Thu, 28 May 1998 15:24:32 -0500 (CDT) Message-Id: <199805282024.PAA01692@detlev.UUCP> To: nate@mt.sri.com CC: rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG In-reply-to: <199805281941.NAA20236@mt.sri.com> (message from Nate Williams on Thu, 28 May 1998 13:41:48 -0600) Subject: Re: Fix for undefined "__error" and discussion of shared object versioning From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199805271551.RAA11565@ceia.nordier.com> <199805281829.NAA01253@detlev.UUCP> <199805281941.NAA20236@mt.sri.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> My own concern would be the amount of code in third-party programs >> that uses gccisms. > Very few programs *should* use gccisms. If they do, they are broke > since they won't build on other OS's compilers. Not necessarily; ifdef's are common: #ifndef __GCC__ #define inline #endif I'm not discussing what should be, I'm discussing what is. We have a good percentage of software from the Linux camps, and many of their software authors wouldn't know a non-portable construct if it walked up and introduced itself in assembly code. >> I guess I don't see why we're looking to change. > Better/faster/less buggy compiler with a much less restrictive Copyright > seems like a win overall to me. I've seen two compile speed tests and one emitted-code benchmark. So far, they indicate that while TenDRA normally compiles faster, its generated code is slower than gcc. I don't know of any bugs in C for gcc 2.7.2.1, and it has a larger user base to find bugs than TenDRA or XANDF. In what ways are these other compilers superior to gcc? (Don't interpret this as belligerence or blind support of gcc; I'm actually asking for information here.) -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 13:47:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22698 for freebsd-current-outgoing; Thu, 28 May 1998 13:47:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22693 for ; Thu, 28 May 1998 13:47:21 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA11840; Thu, 28 May 1998 14:47:04 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA20525; Thu, 28 May 1998 14:47:02 -0600 Date: Thu, 28 May 1998 14:47:02 -0600 Message-Id: <199805282047.OAA20525@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: joelh@gnu.org Cc: nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805282024.PAA01692@detlev.UUCP> References: <199805271551.RAA11565@ceia.nordier.com> <199805281829.NAA01253@detlev.UUCP> <199805281941.NAA20236@mt.sri.com> <199805282024.PAA01692@detlev.UUCP> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> My own concern would be the amount of code in third-party programs > >> that uses gccisms. > > Very few programs *should* use gccisms. If they do, they are broke > > since they won't build on other OS's compilers. > > Not necessarily; ifdef's are common: > > #ifndef __GCC__ > #define inline > #endif So it's a non-issue. > I'm not discussing what should be, I'm discussing what is. We have a > good percentage of software from the Linux camps, and many of their > software authors wouldn't know a non-portable construct if it walked > up and introduced itself in assembly code. Fine, very little of that code is in our tree, including the ports tree. Most of the stuff that matters is commercial and we don't get access to the source and run it under emulation. > >> I guess I don't see why we're looking to change. > > Better/faster/less buggy compiler with a much less restrictive Copyright > > seems like a win overall to me. > > I've seen two compile speed tests and one emitted-code benchmark. So > far, they indicate that while TenDRA normally compiles faster, its > generated code is slower than gcc. The only benchmark was about FPU, and it might not be a problem with the compiler. > I don't know of any bugs in C for gcc 2.7.2.1, and it has a larger > user base to find bugs than TenDRA or XANDF. Finding bugs has never been a problem in GCC. Getting them fixed is the problem. Fixed in the next release was the answer for almost 3 years. :( > In what ways are these other compilers superior to gcc? Faster, smaller, easier to maintain, and re-written. Any software engineer knows that things re-written using the knowledge from previous projects are almost always better than old software that evolves into what it is. The new software is built with the featureset in mind, so it can be better designed into of 'kludged' to support the newer features. This isn't always the case, but it *is* the case when the people doing the work are talented/experienced enough to do things correctly. It appears that the LCC/TenDRa folks are both. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 13:51:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23365 for freebsd-current-outgoing; Thu, 28 May 1998 13:51:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23352 for ; Thu, 28 May 1998 13:51:41 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA06485; Thu, 28 May 1998 15:43:21 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id PAA02201; Thu, 28 May 1998 15:44:22 -0500 (CDT) (envelope-from joelh) Date: Thu, 28 May 1998 15:44:22 -0500 (CDT) Message-Id: <199805282044.PAA02201@detlev.UUCP> To: dmaddox@scsn.net CC: freebsd-current@FreeBSD.ORG In-reply-to: <19980528160640.A747@scsn.net> (dmaddox@scsn.net) Subject: Re: sio0 flag 0x20000 From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199805281812.NAA01183@detlev.UUCP> <19980528160640.A747@scsn.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Is sio0 flag 0x20000 (enable 16550A features) in proper functioning >> order? I enabled it on a whim, and got strange effects in ppp (ie, >> login works fine, but during LQR negotiations, the other side doesn't >> see config-req or config-ack). Disabled it in bootconfig, and all is >> well. >> The probe reports the chip as a 16550A... is that reliable? > The 0x20000 flag is for use with 16>6<50s, not 16550s... > During the brief time when it was enabled by default, it caused problems > with my 16550A-clone serial ports, but it works fine for the 16650-based > LavaPort I have... Memo to myself: check into treatment for dyslexia. Thanks! Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 13:54:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24144 for freebsd-current-outgoing; Thu, 28 May 1998 13:54:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24129 for ; Thu, 28 May 1998 13:54:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA01246; Thu, 28 May 1998 12:48:57 -0700 (PDT) Message-Id: <199805281948.MAA01246@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Peter Dufault cc: paulz@trantor.stuyts.nl (Paul van der Zwan), freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet In-reply-to: Your message of "Thu, 28 May 1998 07:34:50 EDT." <199805281134.HAA20418@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 28 May 1998 12:48:57 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA24135 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > $ sudo cdrecord -dev=0,4,0 -data -dummy /scratch/img/psnl > > Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling > > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler > > Bus error (core dumped) > > > > This is a freshly compiled port on a current cvsupped today. > > (I wonder why he is trying to use the round robin scheduler - I > expect he wants the FIFO one). > > Cdrecord has autoconf'd in the P1003.1B scheduler interface. Autoconf? cdrecord? You haven't seen this mess. 8) > I'm probably going to have to change how I did things, but the > program may need fixing also. By default, with nothing defined, > the new system calls are setup to be LKM'd in for development and > will fail at run time with ENOSYS or if you check for their presense > with sysconf(). > > You can add build time support with the _KPOSIX_PRIORITY_SCHEDULING > option in the kernel. > > See how cdrecord is deciding to use priority scheduling. If it > decides that a program that links OK without checking any compile > time feature test macros means that priority scheduling is supported, > then that should be changed. I've been told some programs are > doing this (not specifically cdrecord). It checks _POSIX_PRIORITY_SCHEDULING at build time. Can you give an example of the correct mechanism for using sysconf() to determine the availability of the scheduler? I'll fix it in the updates I'm working on. Thanks for the comprehensive explanations. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 14:34:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00913 for freebsd-current-outgoing; Thu, 28 May 1998 14:34:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00896 for ; Thu, 28 May 1998 14:34:35 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-135.camalott.com [208.229.74.135] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA04721; Thu, 28 May 1998 15:14:54 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id PAA01671; Thu, 28 May 1998 15:15:44 -0500 (CDT) (envelope-from joelh) Date: Thu, 28 May 1998 15:15:44 -0500 (CDT) Message-Id: <199805282015.PAA01671@detlev.UUCP> To: eivind@yes.no CC: rnordier@nordier.com, current@FreeBSD.ORG In-reply-to: <19980528212713.63593@follo.net> (message from Eivind Eklund on Thu, 28 May 1998 21:27:13 +0200) Subject: Re: Fix for undefined "__error" and discussion of shared object versioning From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199805271551.RAA11565@ceia.nordier.com> <199805281829.NAA01253@detlev.UUCP> <19980528212713.63593@follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> My own concern would be the amount of code in third-party programs >> that uses gccisms. I guess I don't see why we're looking to change. > Well, here are a couple of points: > * License I'll assume that TenDRA and XANDF are both BSD-license? > * General quality of system (GCC is written under the paradigm 'learn > writing compilers as we go') I can't comment on that one, not having examined the source code to the various compilers. But are the others written by professional compiler writers? > * Possibilities for exploiting the cross-CPU nature of XANDF How are XANDF's cross-cpu capabilities more powerful than gcc's? > * Better error checking/control How do you mean? > * Choice (by being able to be compiled with more than one compiler) I'm definately in agreement on this point. I don't like to be boxed in to *any* software, be it M$, GNU, or BSD. Is the OS compilable with pcc? > They might not be enough to be persuative, but they are at least in > favour. Okay. I'm not familiar enough with the compilers' specs, features, and limitations to make a judgement. So for now I'll gather information before I cast a vote. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 14:39:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01744 for freebsd-current-outgoing; Thu, 28 May 1998 14:39:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01731 for ; Thu, 28 May 1998 14:39:48 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id HAA27277; Fri, 29 May 1998 07:09:31 +0930 (CST) (envelope-from grog) Message-ID: <19980529070931.S25469@freebie.lemis.com> Date: Fri, 29 May 1998 07:09:31 +0930 From: Greg Lehey To: "Pierre Y. Dampure" , current@FreeBSD.ORG Subject: Re: Problems with ps on -current References: <000101bd8a61$18e60330$0242000a@jfsebastian.k2c.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <000101bd8a61$18e60330$0242000a@jfsebastian.k2c.co.uk>; from Pierre Y. Dampure on Thu, May 28, 1998 at 06:50:26PM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 X-Mutt-References: <000101bd8a61$18e60330$0242000a@jfsebastian.k2c.co.uk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 May 1998 at 18:50:26 +0100, Pierre Y. Dampure wrote: > Output of ps ax on -current cvsupped 28/05/1998 16:00 BST : > > PID TT STAT TIME COMMAND > 0 ?? DLs 78383:09.19 (swapper) Did you make the world and a new kernel? Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 14:43:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02516 for freebsd-current-outgoing; Thu, 28 May 1998 14:43:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dragon.axil.com (dragon.axil.com [206.33.98.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02496 for ; Thu, 28 May 1998 14:43:00 -0700 (PDT) (envelope-from richard@axil.com) From: richard@axil.com Received: from mint.axil.com by dragon.axil.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1458.49) id JYSKK4VQ; Thu, 28 May 1998 17:42:33 -0400 Received: (from richard@localhost) by mint.axil.com (8.7.1/8.7.1) id RAA02782 for current@freebsd.org; Thu, 28 May 1998 17:42:06 -0400 (EDT) Date: Thu, 28 May 1998 17:42:06 -0400 (EDT) Message-Id: <199805282142.RAA02782@mint.axil.com> To: current@FreeBSD.ORG Subject: FreeBSD on 8-way SMP PPro Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a hacked version of FreeBSD 3.0-980426-SNAP running on an Axil NX801 (8-way SMP PentiumPro 200MHz, 2 IOAPICs, 4 PCI buses, 7 NCR 53c875 scsi, up to 8GB DRAM and 24*9GB disk, see http://www.axil.com for details). Is this a record for the biggest machine running FreeBSD ? At the moment the hacks are not clean or safe for other hardware, so I won't submit patches yet, but here is a brief description of the changes: 1) i386/pmap.c - pmap_bootstrap() This erroneously uses the physical address io_apic_address[0] instead of io_apic_address[i] for each IOAPIC, so all accesses to the second IOAPIC get mapped to the first, causing considerable confusion ... 2) i386/mp_machdep.c - ap_init() Fixed a race condition - the first cpu to do ap_init(), i.e. the second cpu, would set invltlb_ok = 1; smp_started = 1; But this is not safe until *all* APs have completed ap_init(). This is potentially bad if you have more than 2 CPUs, in practice it seemed to work with 4 CPUs, but usually panic'ed with 6 or 8 CPUs (I didn't try odd numbers). My fix was to remove the "smp_cpus++" at start of ap_init(), and instead put this at the end of ap_init(): asm("lock ; incl _smp_cpus"); /* we're ready to go */ /* * The last cpu to get here enables IPIs etc */ if (smp_cpus >= mp_ncpus) { invltlb_ok = 1; smp_started = 1;/* enable IPI's, tlb shootdown, freezes etc */ smp_active = 1; /* historic */ } With this change it seems to work reliably with 8 CPUs (though I haven't done any stress tests). 3) i386/mpapic.c Various changes to cope with multiple IOAPICs, but my current solution is a kludge so I won't give details here. 4) i386/mp_machdep.c Change INTPIN() to return a hardware interrupt number [0..23] instead of just the IOAPIC pin number, i.e. #if (NAPIC < 2) #define INTPIN(I) (io_apic_ints[(I)].dst_apic_int) #else /* * Fix for multiple IOAPICs Tich 29Apr98 */ int INTPIN(int i) { io_int *ip = &io_apic_ints[i]; int apic, pin; apic = ID_TO_IO(ip->dst_apic_id); pin = ip->dst_apic_int; /* printf("mp_machdep: INTPIN(%d) apic_id %d apic_int %d apic%d.pin%d\n", i, ip->dst_apic_id, ip->dst_apic_int, apic, pin); */ if (apic > 0) pin += NPIN_APIC0; return(pin); } #endif 5) isa/apic_vector.s, isa/apic_ipl.s Various unsatisfactory kludges. I understand changes are afoot in the SMP/IOAPIC code; are there plans to support multiple IOAPICs ? My current solution only supports 16 pins on IOAPIC0 and 8 pins on IOAPIC1 - it looks as though there is code which packs 24 hardware interrupt bits and 7 swi bits into a word, so to support the full 16+24 apic pins requires mapping more than one {ioapic,pin} to each irqNum, which would need changes to INTREN() and INTRDIS(). Let me know if I can be any help. Thanks for the great OS Richard Cownie email: Richard.Cownie@pobox.com DISCLAIMER: I speak for myself, not for Axil Computer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 14:51:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03947 for freebsd-current-outgoing; Thu, 28 May 1998 14:51:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03931 for ; Thu, 28 May 1998 14:51:38 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id RAA21367; Thu, 28 May 1998 17:27:33 -0400 (EDT) From: Peter Dufault Message-Id: <199805282127.RAA21367@hda.hda.com> Subject: Re: cdrecord trouble on currnet In-Reply-To: <199805281948.MAA01246@dingo.cdrom.com> from Mike Smith at "May 28, 98 12:48:57 pm" To: mike@smith.net.au (Mike Smith) Date: Thu, 28 May 1998 17:27:31 -0400 (EDT) Cc: 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-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It checks _POSIX_PRIORITY_SCHEDULING at build time. That's understandable, then. > Can you give an example of the correct mechanism for using sysconf() to > determine the availability of the scheduler? I'll fix it in the > updates I'm working on. if (sysconf(_SC_PRIORITY_SCHEDULING) == -1) { if (errno != 0) { /* This isn't valid: */ err(EX_OSERR, "sysconf(_SC_PRIORITY_SCHEDULING)"); } else { errx(EX_UNAVAILABLE, "No run-time support for POSIX priority scheduling"); } } Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 15:01:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06214 for freebsd-current-outgoing; Thu, 28 May 1998 15:01:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06202 for ; Thu, 28 May 1998 15:01:36 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-146.camalott.com [208.229.74.146] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id QAA11176; Thu, 28 May 1998 16:59:59 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id RAA00542; Thu, 28 May 1998 17:01:00 -0500 (CDT) (envelope-from joelh) Date: Thu, 28 May 1998 17:01:00 -0500 (CDT) Message-Id: <199805282201.RAA00542@detlev.UUCP> To: nate@mt.sri.com CC: nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG In-reply-to: <199805282047.OAA20525@mt.sri.com> (message from Nate Williams on Thu, 28 May 1998 14:47:02 -0600) Subject: Re: Fix for undefined "__error" and discussion of shared object versioning From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199805271551.RAA11565@ceia.nordier.com> <199805281829.NAA01253@detlev.UUCP> <199805281941.NAA20236@mt.sri.com> <199805282024.PAA01692@detlev.UUCP> <199805282047.OAA20525@mt.sri.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> My own concern would be the amount of code in third-party programs >>>> that uses gccisms. >>> Very few programs *should* use gccisms. If they do, they are broke >>> since they won't build on other OS's compilers. >> Not necessarily; ifdef's are common: > #ifndef __GCC__ > #define inline > #endif > So it's a non-issue. Not if I want inline code. >> I'm not discussing what should be, I'm discussing what is. We have a >> good percentage of software from the Linux camps, and many of their >> software authors wouldn't know a non-portable construct if it walked >> up and introduced itself in assembly code. > Fine, very little of that code is in our tree, including the ports > tree. Most of the stuff that matters is commercial and we don't get > access to the source and run it under emulation. Matters? Matters to whom? The only commercial app I myself run is Allegro. >>>> I guess I don't see why we're looking to change. >>> Better/faster/less buggy compiler with a much less restrictive Copyright >>> seems like a win overall to me. >> I've seen two compile speed tests and one emitted-code benchmark. So >> far, they indicate that while TenDRA normally compiles faster, its >> generated code is slower than gcc. > The only benchmark was about FPU, and it might not be a problem with the > compiler. I was actually thinking of the grep that ran twice as slow. I will agree that we have few data points to go on. Unless somebody has some *data* for me, I think I'll go off and make some data points. I'm setting up a simple benchmark. Admittedly, benchmarks aren't that terrific, but it's what I've got availible. I'd like to get information from everybody... What compilers do you want me to test? And where can I get their sources? Email me privately, and I'll try to benchmark your favourite compiler. >> I don't know of any bugs in C for gcc 2.7.2.1, and it has a larger >> user base to find bugs than TenDRA or XANDF. > Finding bugs has never been a problem in GCC. Getting them fixed is the > problem. Fixed in the next release was the answer for almost 3 > years. :( I'm aware of the hassles with gcc under AIX, but I haven't run into any with 2.7.2.1 under FreeBSD. Admittedly, I haven't looked for bugs, but I haven't had problems. Again, I am presently referring to C, not C++ or Objective C. >> In what ways are these other compilers superior to gcc? > Faster, No data yet. Point me at data, or point me at sources so I can make some. > smaller, Nice, but with today's hardware, smaller for the sake of being smaller is less and less of a factor. I'm all for reducing bloat, but not at the expense of performance. > easier to maintain, Can't speak to that, haven't tried. > and re-written. > Any software engineer knows that things re-written using the knowledge > from previous projects are almost always better than old software that > evolves into what it is. The new software is built with the feature > set in mind, so it can be better designed into of 'kludged' to > support the newer features. I totally agree. But I'd like to see feature set, and the speed. > This isn't always the case, but it *is* the case when the people doing > the work are talented/experienced enough to do things correctly. It > appears that the LCC/TenDRa folks are both. Okay. I'll take your word for it. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 15:21:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10005 for freebsd-current-outgoing; Thu, 28 May 1998 15:21:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09982 for ; Thu, 28 May 1998 15:21:23 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA06688; Fri, 29 May 1998 08:21:15 +1000 Date: Fri, 29 May 1998 08:21:15 +1000 From: Bruce Evans Message-Id: <199805282221.IAA06688@godzilla.zeta.org.au> To: bde@zeta.org.au, dag-erli@ifi.uio.no Subject: Re: Replacing gcc as the system compiler Cc: current@FreeBSD.ORG, eivind@yes.no, rnordier@nordier.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The standard doesn't allow conversion from an object pointer to a >> function pointer, but (void *)0 is is a null pointer constant and >> null pointer constants are special. > >The C null pointer constant is 0. No cast is needed. Converting 0 to a Not quite. 0 is one of many C null pointer consants. >function pointer might work better than converting ((void *)0). Only in not-quite-C. In C, they work identically when correctly used, and break differently when incorrectly used. >The only situation in which it is advantageous to define NULL as >((void*)0) instead of just (0) is when passing NULL to a vararg >function which lacks a prototype; but you shouldn't do that anyway, >because it will break on more than just NULL (float->double conversion >for instance) This is actully the main disadvantage defining NULL as ((void *) 0) :-) - it helps broken program work. >With the correct prototypes, it is perfectly legal and semantically >correct to write e.g. > > execl("/bin/sh", "-sh", 0); Read what you wrote in the previous paragraph. execl() is varargs, so its varadic parameters must not be uncast 0s or NULLs. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 15:39:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13749 for freebsd-current-outgoing; Thu, 28 May 1998 15:39:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13741 for ; Thu, 28 May 1998 15:39:10 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id PAA19723 for ; Thu, 28 May 1998 15:33:27 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id IAA07718; Fri, 29 May 1998 08:38:56 +1000 Date: Fri, 29 May 1998 08:38:56 +1000 From: Bruce Evans Message-Id: <199805282238.IAA07718@godzilla.zeta.org.au> To: bde@zeta.org.au, kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: help! - nodes.h where is it? Cc: eivind@FreeBSD.ORG, freebsd-current@freefall.cdrom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >> It looks like your src/share/mk/bsd.prog.mk is broken. >... >Doing a make depend first then helped. Sorry, maybe it's just that I >forgot make depend. But should make do it anyway when no .depend >file exists? `make depend' used to be necessary in some cases, but I fixed that using general methods in bsd.prog.mk and removed special hacks for it in places like sh/Makefile. It still looks like your bsd.prog.mk is broken or you have a stale .depend file :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 15:46:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15497 for freebsd-current-outgoing; Thu, 28 May 1998 15:46:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15474 for ; Thu, 28 May 1998 15:46:37 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA12920; Thu, 28 May 1998 16:46:27 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA21766; Thu, 28 May 1998 16:46:24 -0600 Date: Thu, 28 May 1998 16:46:24 -0600 Message-Id: <199805282246.QAA21766@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: joelh@gnu.org Cc: nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805282201.RAA00542@detlev.UUCP> References: <199805271551.RAA11565@ceia.nordier.com> <199805281829.NAA01253@detlev.UUCP> <199805281941.NAA20236@mt.sri.com> <199805282024.PAA01692@detlev.UUCP> <199805282047.OAA20525@mt.sri.com> <199805282201.RAA00542@detlev.UUCP> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>>> My own concern would be the amount of code in third-party programs > >>>> that uses gccisms. > >>> Very few programs *should* use gccisms. If they do, they are broke > >>> since they won't build on other OS's compilers. > >> Not necessarily; ifdef's are common: > > #ifndef __GCC__ > > #define inline > > #endif > > So it's a non-issue. > > Not if I want inline code. Your program will work 'the same' if the code isn't inlined. It'll just run faster, since most of the time inlining busts the cache. :) > >> I'm not discussing what should be, I'm discussing what is. We have a > >> good percentage of software from the Linux camps, and many of their > >> software authors wouldn't know a non-portable construct if it walked > >> up and introduced itself in assembly code. > > Fine, very little of that code is in our tree, including the ports > > tree. Most of the stuff that matters is commercial and we don't get > > access to the source and run it under emulation. > > Matters? Matters to whom? The only commercial app I myself run is > Allegro. Which Linux programs do you run under FreeBSD that will only compile with GCC? > > smaller, > > Nice, but with today's hardware, smaller for the sake of being smaller > is less and less of a factor. Smaller == easier to fix bugs/maintain. Bloat because we can is still bloat, and it means the program is un-necessarily complex for no *real* good. > > easier to maintain, > > Can't speak to that, haven't tried. Have tried, gave up. Too much investment is required for little gain. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 15:48:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15764 for freebsd-current-outgoing; Thu, 28 May 1998 15:48:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pobox.com ([208.141.230.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15741; Thu, 28 May 1998 15:48:04 -0700 (PDT) (envelope-from alk@pobox.com) Received: (from alk@localhost) by pobox.com (8.8.8/8.7.3) id RAA03682; Thu, 28 May 1998 17:49:19 -0500 (CDT) Date: Thu, 28 May 1998 17:49:19 -0500 (CDT) Message-Id: <199805282249.RAA03682@pobox.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: chat@FreeBSD.ORG Cc: nate@mt.sri.com Subject: Re: Fix for undefined "__error" and discussion of shared object versioning X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Nate Williams : > > My own concern would be the amount of code in third-party programs > > that uses gccisms. > > Very few programs *should* use gccisms. If they do, they are broke > since they won't build on other OS's compilers. [ note redirect to chat ] Various points: 1 Non-portable != broken. 2 I'm amazed to see this coming from Nate "Java" Williams! Gcc is the *platform*. Gcc is what makes code portable, not ANSI, which is merely an idea, and not a platform. 3 People use gccisms because then they don't have to write asm, which is much *less* portable. 4 Are you planning on fixing them? Egad, the number of ports! > Better/faster/less buggy compiler with a much less restrictive Copyright > seems like a win overall to me. Remains to be seen, as far as I am concerned. Various points: 1 TenDRA should be compared to GCC 2.8.1, not 2.7.2.1. 2 GPL should not be a restriction in practice for anyone except someone who wants to retain source for a commercialization of added-value back-end code generation under FreeBSD, since there are plenty of source-to-source compilers suitable as front-ends to GCC. Since the amount of money to be made doing this is a negative number, it's not a restriction in practice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 16:07:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19492 for freebsd-current-outgoing; Thu, 28 May 1998 16:07:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19482 for ; Thu, 28 May 1998 16:07:06 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id XAA14692; Thu, 28 May 1998 23:06:52 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id BAA23613; Fri, 29 May 1998 01:06:40 +0200 (MET DST) Message-ID: <19980529010639.54255@follo.net> Date: Fri, 29 May 1998 01:06:39 +0200 From: Eivind Eklund To: joelh@gnu.org Cc: rnordier@nordier.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <199805271551.RAA11565@ceia.nordier.com> <199805281829.NAA01253@detlev.UUCP> <19980528212713.63593@follo.net> <199805282015.PAA01671@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805282015.PAA01671@detlev.UUCP>; from Joel Ray Holveck on Thu, May 28, 1998 at 03:15:44PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 03:15:44PM -0500, Joel Ray Holveck wrote: > >> My own concern would be the amount of code in third-party programs > >> that uses gccisms. I guess I don't see why we're looking to change. > > Well, here are a couple of points: > > * License > > I'll assume that TenDRA and XANDF are both BSD-license? BSD-style, yes. Not an exact BSD license. > > * General quality of system (GCC is written under the paradigm 'learn > > writing compilers as we go') > > I can't comment on that one, not having examined the source code to > the various compilers. But are the others written by professional > compiler writers? As far as I know: Yes. They've been contracted for the development, and I've seen there come a lot of papers from their research. > > * Possibilities for exploiting the cross-CPU nature of XANDF > > How are XANDF's cross-cpu capabilities more powerful than gcc's? XANDF is an intermediate format designed for being compiled to different processors at install-time. This means that we can do only the last phase of a cross-compilation, instead of doing the entire compilation, which we'd have to if we used gcc. > > * Better error checking/control > > How do you mean? Look at the TenDRA docs. It let you work with the defintion of APIs, instead of with whatever gunk ends up in the header files. It also can do a lot of checking against the ANSI/ISO standard. > > * Choice (by being able to be compiled with more than one compiler) > > I'm definately in agreement on this point. I don't like to be boxed > in to *any* software, be it M$, GNU, or BSD. > > Is the OS compilable with pcc? Not AFAIK. > > They might not be enough to be persuative, but they are at least in > > favour. > > Okay. I'm not familiar enough with the compilers' specs, features, and > limitations to make a judgement. So for now I'll gather information > before I cast a vote. So am I. I don't know if we should switch - but the only thing I really see in favour of GCC on a long-term basis is the size of the userbase. The actual design is OK, and the license (for FreeBSD purposes) suck. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 16:14:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20398 for freebsd-current-outgoing; Thu, 28 May 1998 16:14:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20329 for ; Thu, 28 May 1998 16:13:54 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA10039; Fri, 29 May 1998 09:13:37 +1000 Date: Fri, 29 May 1998 09:13:37 +1000 From: Bruce Evans Message-Id: <199805282313.JAA10039@godzilla.zeta.org.au> To: dmaddox@scsn.net, freebsd-current@FreeBSD.ORG, joelh@gnu.org Subject: Re: sio0 flag 0x20000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The probe reports the chip as a 16550A... is that reliable? > >The 0x20000 flag is for use with 16>6<50s, not 16550s... > ^ >During the brief time when it was enabled by default, it caused problems >with my 16550A-clone serial ports, Yes, it should completely break 16550s. >but it works fine for the 16650-based >LavaPort I have... On Startech16650s, it should improve CTS flow control and unimprove RTS flow control (hardware RTS flow control is broken as designed on at least ST16550s). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 16:19:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21421 for freebsd-current-outgoing; Thu, 28 May 1998 16:19:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21416 for ; Thu, 28 May 1998 16:19:52 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id QAA12779; Thu, 28 May 1998 16:19:49 -0700 (PDT) (envelope-from jdp) Message-Id: <199805282319.QAA12779@austin.polstra.com> To: lcremean@tidalwave.net Subject: Re: ELF preparation step 2 done In-Reply-To: <19980527230451.04171@st-lcremean.tidalwave.net> References: <199805270920.CAA01664@rah.star-gate.com> <199805270939.LAA17351@sos.freebsd.dk> <19980527230443.A23502@keltia.freenix.fr> <19980527230451.04171@st-lcremean.tidalwave.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 28 May 1998 16:19:49 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980527230451.04171@st-lcremean.tidalwave.net>, Lee Cremeans wrote: > Does anyone know the magic incantation to get an ELF buildworld working on a > -stable system? Sure: 1. Change your -stable system into a -current system. 2. Proceed to build an ELF world. We don't intend to switch the -2.2 branch to ELF ever. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 16:30:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23627 for freebsd-current-outgoing; Thu, 28 May 1998 16:30:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23622 for ; Thu, 28 May 1998 16:30:39 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id QAA12878; Thu, 28 May 1998 16:30:30 -0700 (PDT) (envelope-from jdp) Message-Id: <199805282330.QAA12878@austin.polstra.com> To: Pierre.Dampure@barclayscapital.com Subject: Re: ELF Stage 2: results In-Reply-To: <711DCB8FB391D111B9DD00805F8BDDBA7262FB@exips0019.itops.ldn.bzwint.com> References: <711DCB8FB391D111B9DD00805F8BDDBA7262FB@exips0019.itops.ldn.bzwint.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 28 May 1998 16:30:30 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - I tried to recompile modula-3 (still willing to see if John Dyson's SMP > mods sort the problem we have currently -- the port does not build under > SMP) but apparently ld is still looking for /usr/lib/crt0 (see below). Ooh, nasty! I will try to come up with a reasonable fix for the port. Meanwhile, you can edit "ports/lang/modula-3-lib/patches/patch-ah" and change the path appropriately. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 17:22:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02764 for freebsd-current-outgoing; Thu, 28 May 1998 17:22:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02674 for ; Thu, 28 May 1998 17:22:03 -0700 (PDT) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id IAA11734; Fri, 29 May 1998 08:44:18 +0930 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id LW7YQ0FK; Fri, 29 May 1998 08:46:42 +0930 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id IAA31244; Fri, 29 May 1998 08:46:43 +0930 (CST) Received: from dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with ESMTP id IAA01182; Fri, 29 May 1998 08:46:43 +0930 (CST) Message-ID: <356DF05A.E4B3AE09@dsto.defence.gov.au> Date: Fri, 29 May 1998 08:46:42 +0930 From: Matthew Thyer Organization: Defence Science Technology Organisation X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Greg Lehey CC: Karl Pielorz , current@FreeBSD.ORG Subject: Re: aha1542 - again... References: <19980528123712.H4179@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am about to add a 1542B to my current system and want to know about the bounce buffer issue. How do I tell whether the device I'm adding does DMA ? Do the probe messages tell me ? It's an ISA card and its an Adaptec 1542B so I assume being a SCSI card it will do DMA so I suppose I should include BOUNCE_BUFFERS since I have 32MB RAM on this P100. Greg Lehey wrote: > > On Thu, 28 May 1998 at 0:07:15 +0100, Karl Pielorz wrote: > > > > Hi, > > > > I read a while ago there were problems with the existing AHA1542 support > > on -current... I also read that someone (I can't remember now who it was) > > said they'd been through the code and fixed up a few things... > > > > As I remember it was a problem to do with bounce buffers... > > > > I've just had to add a 1542CF to my machine (as I'm out PCI slots and it > > was 'hanging around'), and I've run into problems with it - but I'm not > > sure there to do with bounce buffers etc. > > > > I know CAM is looking almost 'immanent' - but can anyone confirm whether > > the 1542 driver is in any useable state in -current at the moment? > > I'm developing vinum on a -CURRENT machine with a 1542B. I had > trouble with a 1542A, which appears to be a known problem (a number 0f > 0xff bytes strewn at regular intervals, usually 32K), but the 1542B is > working fine. > > > I have 2 x Double-Speed CD-ROM drives hooked up to it, I wouldn't have > > thought they were particularly 'stressy' for the driver ;-) > > Do you have problems? You'll need bounce buffers for any ISA DMA > device if you have more than 16 MB memory. > > Greg > -- > See complete headers for address and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 17:25:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03381 for freebsd-current-outgoing; Thu, 28 May 1998 17:25:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03267 for ; Thu, 28 May 1998 17:24:51 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id JAA07740; Fri, 29 May 1998 09:54:20 +0930 (CST) (envelope-from grog) Message-ID: <19980529095419.G25469@freebie.lemis.com> Date: Fri, 29 May 1998 09:54:19 +0930 From: Greg Lehey To: Matthew Thyer Cc: Karl Pielorz , current@FreeBSD.ORG Subject: Re: aha1542 - again... References: <19980528123712.H4179@freebie.lemis.com> <356DF05A.E4B3AE09@dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <356DF05A.E4B3AE09@dsto.defence.gov.au>; from Matthew Thyer on Fri, May 29, 1998 at 08:46:42AM +0930 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 May 1998 at 8:46:42 +0930, Matthew Thyer wrote: > Greg Lehey wrote: >> >> On Thu, 28 May 1998 at 0:07:15 +0100, Karl Pielorz wrote: >>> >>> I read a while ago there were problems with the existing AHA1542 support >>> on -current... I also read that someone (I can't remember now who it was) >>> said they'd been through the code and fixed up a few things... >>> >>> As I remember it was a problem to do with bounce buffers... >>> >>> I've just had to add a 1542CF to my machine (as I'm out PCI slots and it >>> was 'hanging around'), and I've run into problems with it - but I'm not >>> sure there to do with bounce buffers etc. >>> >>> I know CAM is looking almost 'immanent' - but can anyone confirm whether >>> the 1542 driver is in any useable state in -current at the moment? >> >> I'm developing vinum on a -CURRENT machine with a 1542B. I had >> trouble with a 1542A, which appears to be a known problem (a number 0f >> 0xff bytes strewn at regular intervals, usually 32K), but the 1542B is >> working fine. >> >>> I have 2 x Double-Speed CD-ROM drives hooked up to it, I wouldn't have >>> thought they were particularly 'stressy' for the driver ;-) >> >> Do you have problems? You'll need bounce buffers for any ISA DMA >> device if you have more than 16 MB memory. > > I am about to add a 1542B to my current system and want to know about > the bounce buffer issue. > > How do I tell whether the device I'm adding does DMA ? I suppose the safest way is to read the technical documentation. Failing that, the driver documentation may tell you. > Do the probe messages tell me ? Sometimes. Don't rely on it. > It's an ISA card and its an Adaptec 1542B so I assume being a SCSI card > it will do DMA Just because it's a SCSI board doesn't mean it does DMA. The fact that it's a 1542 does mean it'll do DMA, however. The 1520 doesn't, as far as I can recall. > so I suppose I should include BOUNCE_BUFFERS since I have 32MB RAM > on this P100. Correct. I think the system complains if you don't. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 17:38:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06521 for freebsd-current-outgoing; Thu, 28 May 1998 17:38:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06413; Thu, 28 May 1998 17:37:46 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Thu, 28 May 1998 19:49:05 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FABC@freya.circle.net> From: tcobb To: "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Cc: "'simon@simon-shapiro.org'" Subject: DPT driver fails and panics with Degraded Array Date: Thu, 28 May 1998 19:49:04 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a DPT3344UW/2 running an external 24GB array. OS is FreeBSD CURRENT circa 5/18/98. I'm running the latest available firmware flash for the card, all on a P5-233MMX with 128MB RAM. Recently I lost a harddrive in my 24GB RAID5 array. The array was configured with a HOT SPARE which should have allowed it to rebuild completely online, with no interruption in service (except some minor slowdowns, perhaps). While the HARDWARE worked well, the DPT DRIVER failed miserably. When my array went into degraded mode, the DPT DRIVER froze access to the partitions. Upon reboot, during device probe, the DPT DRIVER returned a 1 SECTOR (0 MB) sense for the array, despite the fact that the array was operating properly (though degraded). After this, the kernel panic'd before completing the boot process with a "Page Fault in Supervisor Mode" error, and continued to panic this way until the DPT Array was COMPLETELY REBUILT OFFLINE (requiring me to boot into DOS and do it - doing the rebuild of that size RAID5 array takes more than an hour). After a complete rebuild, the DPT DRIVER showed the array sizes correctly. During this process, booting into DOS revealed the array to be fine, even while the array was degraded -- it also wasn't confused by degraded mode and showed correct partition information. I believe that the DPT DRIVER is not correctly sensing that the array is okay, even though it is in degraded mode, and incorrectly returns sector/MB values which panic the kernel. I don't recommend depending on the proper operation of this driver for your High-Availability needs. HISTORY I've used DPT in FreeBSD since last November, first with the hacked 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that was crashing me about once per week. As 2.2.6, the MBUF leak disappeared and was replaced with a once every 2-3 day panic which it appeared was not going to get fixed by anyone (bidone: buffer not busy). So, I bit the bullet and upgraded recently to 3.0, which seemed to fix both of these prior panics only to reveal that the supposedly "high availability" software driver for my HA hardware is miserable during the most critical times. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 18:20:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14111 for freebsd-current-outgoing; Thu, 28 May 1998 18:20:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14098 for ; Thu, 28 May 1998 18:20:04 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id LAA20313; Fri, 29 May 1998 11:19:43 +1000 Date: Fri, 29 May 1998 11:19:43 +1000 From: Bruce Evans Message-Id: <199805290119.LAA20313@godzilla.zeta.org.au> To: dufault@hda.com, mike@smith.net.au Subject: Re: cdrecord trouble on currnet Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Can you give an example of the correct mechanism for using sysconf() to >> determine the availability of the scheduler? I'll fix it in the >> updates I'm working on. > > if (sysconf(_SC_PRIORITY_SCHEDULING) == -1) { > if (errno != 0) { > /* This isn't valid: > */ > err(EX_OSERR, "sysconf(_SC_PRIORITY_SCHEDULING)"); > } > else { > errx(EX_UNAVAILABLE, > "No run-time support for POSIX priority scheduling"); > } > } The "This isn't valid" case isn't valid, since sysconf() doesn't change errno if there is no error. errno must be set before calling sysconf(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 18:24:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15014 for freebsd-current-outgoing; Thu, 28 May 1998 18:24:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from limbo.rtfm.net (nathan@rtfm.net [204.141.125.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14602 for ; Thu, 28 May 1998 18:22:37 -0700 (PDT) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.8.8/8.8.8) id VAA10564; Thu, 28 May 1998 21:20:34 -0400 (EDT) (envelope-from nathan) Message-ID: <19980528211849.A10559@rtfm.net> Date: Thu, 28 May 1998 21:18:49 -0400 From: Nathan Dorfman To: current@FreeBSD.ORG Subject: top -osize Mail-Followup-To: current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's been confirmed, it's not just me: nathan: -osize doesn't work here. Anyway, top -osize is supposed to sort by size instead of cpu usage. Instead it prints a "this platform doesn't support arbitrary ordering, sorry" message and ignores the option. Is there a real reason for it not being able to do this or is something just mildly broken? -- ________________ ______________________________ / Nathan Dorfman \ / "Nietzsche is dead." - God \ / nathan@rtfm.net \/ http://www.FreeBSD.org/ \ / finger for PGP key \ FreeBSD 2.2.6 is now out! \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 19:11:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22723 for freebsd-current-outgoing; Thu, 28 May 1998 19:11:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22604 for ; Thu, 28 May 1998 19:10:36 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.8.8/8.8.5) with SMTP id WAA00409; Thu, 28 May 1998 22:09:55 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG, joelh@gnu.org Subject: Re: sio0 flag 0x20000 Date: Fri, 29 May 1998 02:12:03 GMT Message-ID: <357118f9.479511008@mail.cetlink.net> References: <199805282313.JAA10039@godzilla.zeta.org.au> In-Reply-To: <199805282313.JAA10039@godzilla.zeta.org.au> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id TAA22630 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 May 1998 09:13:37 +1000, Bruce Evans wrote: >On Startech16650s, it should improve CTS flow control and unimprove RTS >flow control (hardware RTS flow control is broken as designed on at >least ST16550s). "Broken," or unoptimized? (rhetorical question) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 19:15:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23431 for freebsd-current-outgoing; Thu, 28 May 1998 19:15:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23397 for ; Thu, 28 May 1998 19:14:49 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.8.8/8.8.5) with SMTP id WAA00926; Thu, 28 May 1998 22:14:43 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: richard@axil.com Cc: current@FreeBSD.ORG Subject: Re: FreeBSD on 8-way SMP PPro Date: Fri, 29 May 1998 02:16:52 GMT Message-ID: <35721a34.479825792@mail.cetlink.net> References: <199805282142.RAA02782@mint.axil.com> In-Reply-To: <199805282142.RAA02782@mint.axil.com> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id TAA23408 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 May 1998 17:42:06 -0400 (EDT), richard@axil.com wrote: >I have a hacked version of FreeBSD 3.0-980426-SNAP running >on an Axil NX801 (8-way SMP PentiumPro 200MHz, 2 IOAPICs, >4 PCI buses, 7 NCR 53c875 scsi, up to 8GB DRAM and 24*9GB disk, >see http://www.axil.com for details). >Is this a record for the biggest machine running FreeBSD ? Your home page advocates NT. How does performance compare? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 19:20:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24503 for freebsd-current-outgoing; Thu, 28 May 1998 19:20:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24377 for ; Thu, 28 May 1998 19:20:04 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.8/8.8.8) id VAA11598 for current@FreeBSD.org; Thu, 28 May 1998 21:20:02 -0500 (CDT) (envelope-from dan) Message-ID: <19980528212002.A11468@emsphone.com> Date: Thu, 28 May 1998 21:20:02 -0500 From: Dan Nelson To: current@FreeBSD.ORG Subject: Re: top -osize References: <19980528211849.A10559@rtfm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.4i In-Reply-To: <19980528211849.A10559@rtfm.net>; from "Nathan Dorfman" on Thu May 28 21:18:49 GMT 1998 X-OS: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (May 28), Nathan Dorfman said: > It's been confirmed, it's not just me: > > nathan: -osize doesn't work here. > > Anyway, top -osize is supposed to sort by size instead of cpu usage. > Instead it prints a "this platform doesn't support arbitrary > ordering, sorry" message and ignores the option. > > Is there a real reason for it not being able to do this or is > something just mildly broken? The only reason is that no one's wanted to write the sort routines. Out of the 40 platforms supported by top 3.5b7, only 5 (aix32, aix41, sunos4, sunos5, and untrix4) even implemented -o. If I need a process list sorted by something, I usually pipe ps through sort myself. And you're in the wrong channel :) -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 19:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29577 for freebsd-current-outgoing; Thu, 28 May 1998 19:44:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29558 for ; Thu, 28 May 1998 19:44:14 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA26085; Fri, 29 May 1998 12:44:07 +1000 Date: Fri, 29 May 1998 12:44:07 +1000 From: Bruce Evans Message-Id: <199805290244.MAA26085@godzilla.zeta.org.au> To: bde@zeta.org.au, jak@cetlink.net Subject: Re: sio0 flag 0x20000 Cc: freebsd-current@FreeBSD.ORG, joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>On Startech16650s, it should improve CTS flow control and unimprove RTS >>flow control (hardware RTS flow control is broken as designed on at >>least ST16550s). > >"Broken," or unoptimized? (rhetorical question) Pessimized by design. IIRC, it invokes flow control when the fifo trigger level is reached. The fifo trigger level will always be reached while input is streaming in. Sometimes, the external device will notice the flow control and stop sending for a microsecond or two that it takes to begin servicing the interrupt and read a byte or two from the fifo. Every time, the external device will have to do extra work to notice the flow control changes (typically, 2 extra interrupts per change). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 19:50:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00908 for freebsd-current-outgoing; Thu, 28 May 1998 19:50:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00852; Thu, 28 May 1998 19:49:59 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Thu, 28 May 1998 22:49:23 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAC2@freya.circle.net> From: tcobb To: "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: DPT driver fails and panics with Degraded Array Date: Thu, 28 May 1998 22:49:23 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a DPT3344UW/2 running an external 24GB array. OS is FreeBSD CURRENT circa 5/18/98. I'm running the latest available firmware flash for the card, all on a P5-233MMX with 128MB RAM. Recently I lost a harddrive in my 24GB RAID5 array. The array was configured with a HOT SPARE which should have allowed it to rebuild completely online, with no interruption in service (except some minor slowdowns, perhaps). While the HARDWARE worked well, the DPT DRIVER failed miserably. When my array went into degraded mode, the DPT DRIVER froze access to the partitions. Upon reboot, during device probe, the DPT DRIVER returned a 1 SECTOR (0 MB) sense for the array, despite the fact that the array was operating properly (though degraded). After this, the kernel panic'd before completing the boot process with a "Page Fault in Supervisor Mode" error, and continued to panic this way until the DPT Array was COMPLETELY REBUILT OFFLINE (requiring me to boot into DOS and do it - doing the rebuild of that size RAID5 array takes more than an hour). After a complete rebuild, the DPT DRIVER showed the array sizes correctly. During this process, booting into DOS revealed the array to be fine, even while the array was degraded -- it also wasn't confused by degraded mode and showed correct partition information. I believe that the DPT DRIVER is not correctly sensing that the array is okay, even though it is in degraded mode, and incorrectly returns sector/MB values which panic the kernel. I don't recommend depending on the proper operation of this driver for your High-Availability needs. HISTORY I've used DPT in FreeBSD since last November, first with the hacked 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that was crashing me about once per week. As 2.2.6, the MBUF leak disappeared and was replaced with a once every 2-3 day panic which it appeared was not going to get fixed by anyone (bidone: buffer not busy). So, I bit the bullet and upgraded recently to 3.0, which seemed to fix both of these prior panics only to reveal that the supposedly "high availability" software driver for my HA hardware is miserable during the most critical times. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 20:08:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03819 for freebsd-current-outgoing; Thu, 28 May 1998 20:08:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03805; Thu, 28 May 1998 20:08:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA02883; Thu, 28 May 1998 19:03:46 -0700 (PDT) Message-Id: <199805290203.TAA02883@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: tcobb cc: "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" , "'simon@simon-shapiro.org'" Subject: Re: DPT driver fails and panics with Degraded Array In-reply-to: Your message of "Thu, 28 May 1998 19:49:04 EDT." <509A2986E5C5D111B7DD0060082F32A402FABC@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 19:03:46 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > HISTORY > I've used DPT in FreeBSD since last November, first with the hacked > 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that was crashing > me about once per week. As 2.2.6, the MBUF leak disappeared and was > replaced with a once every 2-3 day panic which it appeared was not going > to get fixed by anyone (bidone: buffer not busy). So, I bit the bullet > and upgraded recently to 3.0, which seemed to fix both of these prior > panics only to reveal that the supposedly "high availability" software > driver for my HA hardware is miserable during the most critical times. Given that biodone is only called from disk drivers, and I guess you're probably only using the DPT driver, it sounds like your two problems are one. Certainly, given that 3.0 upgrade was taken against the indicators, it's hard to feel that many of your accusations are terribly justifiable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 20:55:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10343 for freebsd-current-outgoing; Thu, 28 May 1998 20:55:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10313; Thu, 28 May 1998 20:55:29 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Thu, 28 May 1998 23:54:50 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAC3@freya.circle.net> From: tcobb To: "'Mike Smith'" Cc: "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: RE: DPT driver fails and panics with Degraded Array Date: Thu, 28 May 1998 23:54:49 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > Sent: Thursday, May 28, 1998 10:04 PM > To: tcobb > Cc: 'freebsd-current@freebsd.org'; 'freebsd-scsi@freebsd.org'; > 'simon@simon-shapiro.org' > Subject: Re: DPT driver fails and panics with Degraded Array > > > > HISTORY > > I've used DPT in FreeBSD since last November, first with the hacked > > 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that > was crashing > > me about once per week. As 2.2.6, the MBUF leak disappeared and was > > replaced with a once every 2-3 day panic which it appeared > was not going > > to get fixed by anyone (bidone: buffer not busy). So, I > bit the bullet > > and upgraded recently to 3.0, which seemed to fix both of > these prior > > panics only to reveal that the supposedly "high > availability" software > > driver for my HA hardware is miserable during the most > critical times. > > Given that biodone is only called from disk drivers, and I > guess you're > probably only using the DPT driver, it sounds like your two problems > are one. > > Certainly, given that 3.0 upgrade was taken against the > indicators, it's > hard to feel that many of your accusations are terribly justifiable. Excuse me? Could you please explain what you mean by "taken against the indicators"? It was clear from talking to more than one person on the core team that the biodone issues were unlikely to get resolved in -stable. This, plus deficiencies in the -stable NFS code (and other -stable instabilities) caused me to have to upgrade this machine to -current in order to keep using FreeBSD for it. I was quite reluctant to do this, believe me. But it was the best recommendation I was given. My problem report (most of which you snipped) pointed out a deficiency in the DPT driver code which renders it useless in HA applications. I believe that this deficiency is likely to be present in ALL VERSIONS of this code, unless suddenly, people are putting the newest code in the oldest versions of the OS. "Indicators" are that I shouldn't be using FreeBSD for any High Availability or critical operations -- I AM using FreeBSD for > 15 live servers. Now, what was your point? -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 21:31:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16565 for freebsd-current-outgoing; Thu, 28 May 1998 21:31:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16551 for ; Thu, 28 May 1998 21:31:26 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA22025; Thu, 28 May 1998 21:31:25 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Nate Williams cc: joelh@gnu.org, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Thu, 28 May 1998 13:41:48 MDT." <199805281941.NAA20236@mt.sri.com> Date: Thu, 28 May 1998 21:31:25 -0700 Message-ID: <22020.896416285@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [ Replacing GCC with TenDra ] > > > My own concern would be the amount of code in third-party programs > > that uses gccisms. > > Very few programs *should* use gccisms. If they do, they are broke > since they won't build on other OS's compilers. Ah, the old "should" argument. Unix should be beating NT in the server market. Microsoft should not be the number one software company right now. Programmers should write better code. C++ is evil and should die. All things which *should* be true but don't make one hairy tootsie-pop's worth of difference in determining how things are in the real world. I don't expect to find gcc-isms hiding behind every bush, but I do think they will prove to be more common in actual use than anyone had suspected. And no, to answer the next question, it would not be the best possible use of our time to go chasing down all such instances when there are so many more urgent non-compiler related issues to be chasing in FreeBSD. Geeze, if you've got *that* much extra energy, Nate, then how about implementing 32-bit Cardbus support for PAO? I can think of a lot of laptop owners, both present and future, who could sure use that a lot more than they could use a 2nd compiler option. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 22:22:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28130 for freebsd-current-outgoing; Thu, 28 May 1998 22:22:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28081 for ; Thu, 28 May 1998 22:22:22 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id OAA27082; Fri, 29 May 1998 14:51:44 +0930 (CST) (envelope-from grog) Message-ID: <19980529145143.B20360@freebie.lemis.com> Date: Fri, 29 May 1998 14:51:43 +0930 From: Greg Lehey To: tcobb , "'Mike Smith'" Cc: "'freebsd-current@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FAC3@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAC3@freya.circle.net>; from tcobb on Thu, May 28, 1998 at 11:54:49PM -0400 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (removing -scsi; it's not *that* interesting) On Thu, 28 May 1998 at 23:54:49 -0400, tcobb wrote: >> From: Mike Smith [mailto:mike@smith.net.au] >> Sent: Thursday, May 28, 1998 10:04 PM >> >>> HISTORY >>> >>> I've used DPT in FreeBSD since last November, first with the >>> hacked 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that >>> was crashing me about once per week. As 2.2.6, the MBUF leak >>> disappeared and was replaced with a once every 2-3 day panic which >>> it appeared was not going to get fixed by anyone (bidone: buffer >>> not busy). So, I bit the bullet and upgraded recently to 3.0, >>> which seemed to fix both of these prior panics only to reveal that >>> the supposedly "high availability" software driver for my HA >>> hardware is miserable during the most critical times. >> >> Given that biodone is only called from disk drivers, and I guess >> you're probably only using the DPT driver, it sounds like your two >> problems are one. >> >> Certainly, given that 3.0 upgrade was taken against the >> indicators, it's >> hard to feel that many of your accusations are terribly justifiable. > > Excuse me? Could you please explain what you mean by "taken against the > indicators"? Good question. I suspect that the tone of your message rubbed Mike up the wrong way. He may have been over-reacting, but I can understand where he's coming from. You have apparently decided to use -CURRENT and the DPT driver on a live system, and are upset that it doesn't perform as well as production software. We are also often upset about the quality of the -CURRENT software, but most of us either try to fix it or report things in a more neutral manner. We see rather too many messages just plain complaining. > My problem report (most of which you snipped) pointed out a deficiency > in the DPT driver code which renders it useless in HA applications. I > believe that this deficiency is likely to be present in ALL VERSIONS of > this code, unless suddenly, people are putting the newest code in the > oldest versions of the OS. If you just want to report a bug, use send-pr. That will reach the person responsible for it as quickly as possible (consider that a lot of us just drop some of the mailing lists when the combined volume gets too high). The purpose of sending the message to -CURRRENT would be to draw the problem to the attention of other people using the software. > "Indicators" are that I shouldn't be using FreeBSD for any High > Availability or critical operations -- I AM using FreeBSD for > 15 live > servers. > > Now, what was your point? Well, Mike's probably asleep, but how about this for starters: People occasionally have other reasons for wanting to use FreeBSD-CURRENT. The following are not good reasons: o They see it as a way to be the first on the block with great new FreeBSD features. This is not a good reason, because there's no reason to believe that the features will stay, and there is good reason to believe that they will be unstable. o They see it as a quick way of getting bug fixes. In fact, it's a way of testing bug fixes. Bug fixes will be retrofitted into the -STABLE branch as soon as they have been properly tested. o They see it as the newest officially supported release of FreeBSD. This is incorrect: FreeBSD-CURRENT is not officially supported. The support is provided by the users. Basically, I'd guess Mike is saying "don't use FreeBSD-CURRENT in production environments". Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 22:32:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA00703 for freebsd-current-outgoing; Thu, 28 May 1998 22:32:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA00698 for ; Thu, 28 May 1998 22:32:26 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Fri, 29 May 1998 01:31:50 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAC7@freya.circle.net> From: tcobb To: "'Greg Lehey'" , "'Mike Smith'" Cc: "'freebsd-current@freebsd.org'" Subject: RE: DPT driver fails and panics with Degraded Array Date: Fri, 29 May 1998 01:31:49 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Greg Lehey [mailto:grog@lemis.com] > If you just want to report a bug, use send-pr. That will reach the > person responsible for it as quickly as possible (consider that a lot > of us just drop some of the mailing lists when the combined volume > gets too high). The purpose of sending the message to -CURRRENT > would be to draw the problem to the attention of other people using > the software. Indeed. And that was the point of sending to freebsd-current. I wanted anyone using the DPT driver and expecting it to perform appropriately in critical circumstances to know that it will not do so. I perhaps should have sent the email to -hackers instead? Or, maybe -scsi, like I did -- it is a scsi driver problem I'm talking about. I chose HA hardware for the particular reason that the server needs to be *available*. I settled on FreeBSD for all the servers I manage 2.5 years ago because it was the highest quality OS for Intel architectures. > > "Indicators" are that I shouldn't be using FreeBSD for any High > > Availability or critical operations -- I AM using FreeBSD > for > 15 live > > servers. > > > > Now, what was your point? > > > Basically, I'd guess Mike is saying "don't use FreeBSD-CURRENT in > production environments". I agree. I wouldn't have done so without provocation. My counterpoint is that FreeBSD-STABLE is NOT stable, either. Regardless, due to show-stopper bugs in -stable... My choices were: 1. Discard FreeBSD completely for this server. 2. Switch to a -current snapshot. I didn't want to do #1, so I spent two weeks rolling a -current snapshot release for my in-house use, I tested it, and tested it. It works well. My posting was really to point to the fact that it appears that the DPT driver is deficient across ALL releases, not just -current. Believe me, I understand the uncharted waters I've entered with my -current snapshot. The DPT driver failure was the unexpected thing. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 23:02:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA06729 for freebsd-current-outgoing; Thu, 28 May 1998 23:02:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA06713 for ; Thu, 28 May 1998 23:01:52 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA00310; Thu, 28 May 1998 21:56:40 -0700 (PDT) Message-Id: <199805290456.VAA00310@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nate Williams cc: joelh@gnu.org, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Thu, 28 May 1998 13:41:48 MDT." <199805281941.NAA20236@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 21:56:39 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [ Replacing GCC with TenDra ] > > > My own concern would be the amount of code in third-party programs > > that uses gccisms. > > Very few programs *should* use gccisms. If they do, they are broke > since they won't build on other OS's compilers. Given that gcc builds and runs just about everywhere, many people would argue that this isn't something they care about. > > I guess I don't see why we're looking to change. > > Better/faster/less buggy compiler with a much less restrictive Copyright > seems like a win overall to me. So far all we've seen is "less restrictive copyright". I'd certainly be happy to see more of the rest, but it has to be understood that we will have to support gcc in one form or another for the foreseeable future. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 23:20:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09915 for freebsd-current-outgoing; Thu, 28 May 1998 23:20:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09900 for ; Thu, 28 May 1998 23:20:08 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA00405; Thu, 28 May 1998 22:16:01 -0700 (PDT) Message-Id: <199805290516.WAA00405@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: tcobb cc: "'freebsd-current@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array In-reply-to: Your message of "Thu, 28 May 1998 23:54:49 EDT." <509A2986E5C5D111B7DD0060082F32A402FAC3@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 22:16:01 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > HISTORY > > > I've used DPT in FreeBSD since last November, first with the hacked > > > 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that > > was crashing > > > me about once per week. As 2.2.6, the MBUF leak disappeared and was > > > replaced with a once every 2-3 day panic which it appeared > > was not going > > > to get fixed by anyone (bidone: buffer not busy). So, I > > bit the bullet > > > and upgraded recently to 3.0, which seemed to fix both of > > these prior > > > panics only to reveal that the supposedly "high > > availability" software > > > driver for my HA hardware is miserable during the most > > critical times. > > > > Given that biodone is only called from disk drivers, and I > > guess you're > > probably only using the DPT driver, it sounds like your two problems > > are one. > > > > Certainly, given that 3.0 upgrade was taken against the > > indicators, it's > > hard to feel that many of your accusations are terribly justifiable. > > Excuse me? Could you please explain what you mean by "taken against the > indicators"? In your message, the only problems that you describe are ones that are not likely to be remedied in any significant fashion. On the other hand, the risks involved in moving to a bleeding-edge development release are very substantial, as you have discovered. > It was clear from talking to more than one person on the core team that > the biodone issues were unlikely to get resolved in -stable. It would have been useful to make this discussion public. -stable is meant to be our "production quality" release, and if these problems are not isolated to a particular driver (in your case they may), then I would imagine that many people would like some accountability attached to the decision not to resolve them. > This, plus > deficiencies in the -stable NFS code (and other > -stable instabilities) caused me to have to upgrade this machine to > -current in order to keep using FreeBSD for it. I was quite reluctant > to do this, believe me. But it was the best recommendation I was given. NFS is being addressed in both -current and -stable. You could probably obtain the services of a FreeBSD-savvy consultant to bring any remedies back from -current to -stable for significantly less than the cost of the downtime and aggravation you are currently experiencing. > My problem report (most of which you snipped) pointed out a deficiency > in the DPT driver code which renders it useless in HA applications. I > believe that this deficiency is likely to be present in ALL VERSIONS of > this code, unless suddenly, people are putting the newest code in the > oldest versions of the OS. I understood this entirely. I had assumed that you would be pursuing the matter with the driver author and maintainers, and merely added that your biodone problem was quite possibly related as an additional datapoint. Neither I nor FreeBSD Test Labs nor anyone that I can manipulate have access to any DPT hardware in order to attempt to resolve your problem, so I have nothing further constructive to offer, sorry. > "Indicators" are that I shouldn't be using FreeBSD for any High > Availability or critical operations -- I AM using FreeBSD for > 15 live > servers. It does sound like you've found some serious problems, yes. Are all 15 systems exploding on a daily basis? > Now, what was your point? Rushing to the "latest and greatest" is a stupid idea, particularly when it is plastered with black and yellow striped signs. Resolving the problems that you are specifically encountering in a generally stable (and static) branch limits your risk exposure, and greatly raises your chances of success. Any investment in such a resolution will have a far longer life insofar as it is less likely to be obsoleted or defeated by other substantial changes. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 23:22:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10376 for freebsd-current-outgoing; Thu, 28 May 1998 23:22:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10347 for ; Thu, 28 May 1998 23:22:41 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA00425; Thu, 28 May 1998 22:18:33 -0700 (PDT) Message-Id: <199805290518.WAA00425@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: tcobb cc: "'freebsd-current@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array In-reply-to: Your message of "Fri, 29 May 1998 01:31:49 EDT." <509A2986E5C5D111B7DD0060082F32A402FAC7@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 22:18:33 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Indeed. And that was the point of sending to freebsd-current. I wanted > anyone using the DPT driver and expecting it to perform appropriately in > critical circumstances to know that it will not do so. I perhaps should > have sent the email to -hackers instead? Or, maybe -scsi, like I did -- > it is a scsi driver problem I'm talking about. The heads-up was fine. Some indication that you were working with the author to resolve the issue would have been somewhat more encouraging, or at least that you had discussed the matter with same. > Believe me, I understand the uncharted waters I've entered with my > -current snapshot. The DPT driver failure was the unexpected thing. Gotcha. I didn't get this impression from your previous postings. Have you heard from Simon inre: the DPT issues? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 23:31:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11874 for freebsd-current-outgoing; Thu, 28 May 1998 23:31:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11851 for ; Thu, 28 May 1998 23:31:01 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA00502; Thu, 28 May 1998 22:26:48 -0700 (PDT) Message-Id: <199805290526.WAA00502@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: jak@cetlink.net (John Kelly) cc: richard@axil.com, current@FreeBSD.ORG Subject: Re: FreeBSD on 8-way SMP PPro In-reply-to: Your message of "Fri, 29 May 1998 02:16:52 GMT." <35721a34.479825792@mail.cetlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 May 1998 22:26:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 28 May 1998 17:42:06 -0400 (EDT), richard@axil.com wrote: > > >I have a hacked version of FreeBSD 3.0-980426-SNAP running > >on an Axil NX801 (8-way SMP PentiumPro 200MHz, 2 IOAPICs, > >4 PCI buses, 7 NCR 53c875 scsi, up to 8GB DRAM and 24*9GB disk, > >see http://www.axil.com for details). > >Is this a record for the biggest machine running FreeBSD ? > > Your home page advocates NT. How does performance compare? Axil's homepage advocates NT. I haven't seen Richard's. BTW, Richard, if Axil wanted to donate one of these systems (or even an 803) to the FreeBSD project, we would make sure that FreeBSD *always* ran properly on it. 8) More seriously, would you like some "Powered by FreeBSD" stickers to put on the system? Perhaps a stuffed Daemon to sit on top? Thanks for sharing your results; it's very encouraging to hear these sort of results! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 23:33:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12242 for freebsd-current-outgoing; Thu, 28 May 1998 23:33:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12203 for ; Thu, 28 May 1998 23:33:37 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Fri, 29 May 1998 02:32:53 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAC9@freya.circle.net> From: tcobb To: "'Mike Smith'" Cc: "'freebsd-current@freebsd.org'" Subject: RE: DPT driver fails and panics with Degraded Array Date: Fri, 29 May 1998 02:32:52 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > It would have been useful to make this discussion public. -stable is > meant to be our "production quality" release, and if these > problems are > not isolated to a particular driver (in your case they may), then I > would imagine that many people would like some accountability > attached > to the decision not to resolve them. I did, on -hackers. See: http://www.freebsd.org/cgi/getmsg.cgi?fetch=344895+347871+/usr/local/www /db/text/1998/freebsd-hackers/19980510.freebsd-hackers Interestingly enough, I got 10 or so PRIVATE posts as a result of the above email, and no public ones. There is a still-open pr on the biodone panics in -stable and -release. Apparently, CAM was tendered as a solution to this, but with no DPT support in CAM (yet) and no surety that CAM would solve it, I had to test and implement a -current implementation. These biodone panics appear to be NOT hardware specific. > > This, plus > > deficiencies in the -stable NFS code (and other > > -stable instabilities) caused me to have to upgrade this machine to > > -current in order to keep using FreeBSD for it. I was > quite reluctant > > to do this, believe me. But it was the best recommendation > I was given. > > NFS is being addressed in both -current and -stable. You could > probably obtain the services of a FreeBSD-savvy consultant to > bring any > remedies back from -current to -stable for significantly less > than the > cost of the downtime and aggravation you are currently experiencing. The determination was that a carefully tested -current snapshot was going to be more stable than -stable in the situations I use FreeBSD. I carefully tested it, the -current snapshot I'm using IS working well, the exception is the DPT software driver. > It does sound like you've found some serious problems, yes. Are all 15 > systems exploding on a daily basis? No. They are not. My busiest NFS server is the one having the problems, and the only one with DPT hardware, too. My posting was regarding DPT hardware, my reason for moving to a -current snapshot was NOT due to DPT hardware but rather due to -stable instabilities. > Rushing to the "latest and greatest" is a stupid idea, particularly > when it is plastered with black and yellow striped signs. > > Resolving the problems that you are specifically encountering in a > generally stable (and static) branch limits your risk exposure, and > greatly raises your chances of success. Any investment in such a > resolution will have a far longer life insofar as it is less > likely to > be obsoleted or defeated by other substantial changes. A valid point and one I agree with. I believe that my remarks would've incited less anger had I not posted them to -current. I perhaps erred in posting to -current as well as -scsi. My point was that the DPT driver is not ready for prime time, NOT that -current is such. I've found that my own self-rolled -current snapshot release to be faster and more stable than the -stable branch, actually. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 23:34:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12479 for freebsd-current-outgoing; Thu, 28 May 1998 23:34:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12442 for ; Thu, 28 May 1998 23:34:48 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA19425; Thu, 28 May 1998 23:33:11 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd019422; Fri May 29 06:33:07 1998 Date: Thu, 28 May 1998 23:33:04 -0700 (PDT) From: Julian Elischer To: tcobb cc: "'Greg Lehey'" , "'Mike Smith'" , "'freebsd-current@freebsd.org'" Subject: RE: DPT driver fails and panics with Degraded Array In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAC7@freya.circle.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I guess this is really something you want to discuss with simon. I'm sure he will contact you soon He's just finished moving houes and has been out-of-touch fro a few weeks julian On Fri, 29 May 1998, tcobb wrote: > > -----Original Message----- > > From: Greg Lehey [mailto:grog@lemis.com] > > > If you just want to report a bug, use send-pr. That will reach the > > person responsible for it as quickly as possible (consider that a lot > > of us just drop some of the mailing lists when the combined volume > > gets too high). The purpose of sending the message to -CURRRENT > > would be to draw the problem to the attention of other people using > > the software. > > Indeed. And that was the point of sending to freebsd-current. I wanted > anyone using the DPT driver and expecting it to perform appropriately in > critical circumstances to know that it will not do so. I perhaps should > have sent the email to -hackers instead? Or, maybe -scsi, like I did -- > it is a scsi driver problem I'm talking about. > > I chose HA hardware for the particular reason that the server needs to > be *available*. I settled on FreeBSD for all the servers I manage 2.5 > years ago because it was the highest quality OS for Intel architectures. > > > > "Indicators" are that I shouldn't be using FreeBSD for any High > > > Availability or critical operations -- I AM using FreeBSD > > for > 15 live > > > servers. > > > > > > Now, what was your point? > > > > > > Basically, I'd guess Mike is saying "don't use FreeBSD-CURRENT in > > production environments". > > I agree. I wouldn't have done so without provocation. My counterpoint > is that FreeBSD-STABLE is NOT stable, either. Regardless, due to > show-stopper bugs in -stable... > > My choices were: > > 1. Discard FreeBSD completely for this server. > 2. Switch to a -current snapshot. > > I didn't want to do #1, so I spent two weeks rolling a -current snapshot > release for my in-house use, I tested it, and tested it. It works well. > > My posting was really to point to the fact that it appears that the DPT > driver is deficient across ALL releases, not just -current. > > Believe me, I understand the uncharted waters I've entered with my > -current snapshot. The DPT driver failure was the unexpected thing. > > > -Troy Cobb > Circle Net, Inc. > http://www.circle.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu May 28 23:40:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13810 for freebsd-current-outgoing; Thu, 28 May 1998 23:40:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13759; Thu, 28 May 1998 23:40:24 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id HAA00434; Fri, 29 May 1998 07:40:08 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199805290640.HAA00434@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Mike Smith cc: Brian Somers , sos@FreeBSD.ORG, wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG Subject: Re: cvs commit: src Makefile src/etc rc src/etc/mtree BSD.usr.dist In-reply-to: Your message of "Wed, 27 May 1998 13:13:13 PDT." <199805272013.NAA01620@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 07:40:08 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So is dlopen() now capable ? This was discussed a while ago and dropped IIRC. Now, I guess it's pretty mandatory cos there's no other reliable way for ppp to find things.... We also need to bump __FreeBSD_version before any snaps get released, otherwise it's gonna create problems for me. Has anyone any objections ? Cheers. > > > Well, there is no real solution for that I'm afraid.. > > > > > > At runtime shared libs wil be resolved via rtld which knows > > > where to look for libs. > > > > > > Systems that rely on libs being in /usr/lib via hard path will > > > fail, ie Makefiles with a wired in hard path, we can then argue > > > to death who is broken... > > > > > > Another story is what we are going to do with /usr/local/lib :( > > > > Any ideas for /usr/src/usr.sbin/ppp/loadalias.c ? It dlopen()s and > > dlsym()s with a fixed path prefix. > > Ideally you should be able to pass a library name to dlopen() and have > it do the search for you based on the current search path. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 00:07:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18777 for freebsd-current-outgoing; Fri, 29 May 1998 00:07:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18746 for ; Fri, 29 May 1998 00:06:41 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.48.34]) by mailman.cs.ucla.edu (8.8.8/UCLACS-4.0) with ESMTP id AAA27332; Fri, 29 May 1998 00:05:53 -0700 (PDT) Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id AAA25365; Fri, 29 May 1998 00:05:52 -0700 (PDT) (envelope-from scottm) Date: Fri, 29 May 1998 00:05:52 -0700 (PDT) From: Scott Michel Message-Id: <199805290705.AAA25365@mordred.cs.ucla.edu> To: mike@smith.net.au Subject: Re: TenDRA C++ Cc: current@FreeBSD.ORG In-Reply-To: <199805281915.MAA01071@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of TenDRA and C++, is there any reasonable implementation of iostream (or compilation hacks to get iostream to work?) I spent a number of hours on it, but then abandoned it due to shear frustration at fixing various pieces of code (i.e. stdio.h isn't included, but BUFSIZ is used in an obscure #define ...) ! > Quoting Mikhail Teterin (mi@video-collage.com): ! > > Alex Povolotsky once stated: ! > > ! > > =I've tried to compile Qt with TenDRA, and got more errors than I've ! > > =got earlier this year at all ;-) Looks like TenDRA has SOMETHING very ! > > =different from GCC inside it. ! > > ! > > gcc-2.8.1 does not compile Qt either. Or, rather, it compiles, but the ! > > resulting object files can not be linked together. Same with KDE stuff. ! > ! > I couldn't get it to work wtih 2.7.2.1 either, unless, when I linked, I ! > specified -lqt -lqt -lqt. ! ! Did you remember to feed the library to ranlib? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 00:13:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19953 for freebsd-current-outgoing; Fri, 29 May 1998 00:13:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19922 for ; Fri, 29 May 1998 00:13:15 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id JAA10787; Fri, 29 May 1998 09:13:13 +0200 (MEST) (envelope-from kuku) Message-ID: <19980529091313.42603@gil.physik.rwth-aachen.de> Date: Fri, 29 May 1998 09:13:13 +0200 From: Christoph Kukulies To: Daniel Ortmann Cc: freebsd-current@FreeBSD.ORG Subject: Re: help! - nodes.h where is it? References: <199805280722.JAA06249@gilberto.physik.RWTH-Aachen.DE> <199805281631.LAA09351@pyrl.eye> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199805281631.LAA09351@pyrl.eye>; from Daniel Ortmann on Thu, May 28, 1998 at 11:31:16AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 11:31:16AM -0500, Daniel Ortmann wrote: > > I cannot build -current world because something seems to be screwed > > in my src tree and I cannot figure out. > > Are you doing a "cvs update -d" or just "cvs update"? > > Without "-d" cvs won't checkout new stuff in directories. I think > that any time I've been bit it has been for this reason. I'm using cvsup. (REL_15_1 as I just found out - thought I have 15_4 also laying around - maybe I'd better upgrade). > > -- > Daniel Ortmann 507.288.7732 (h) ortmann@isl.net > 2414 30 av NW, #D 507.253.6795 (w) ortmann@vnet.ibm.com > Rochester, MN 55901 "PERL: The Swiss Army Chainsaw" > "The answers are so simple and we all know where to look, > but it's easier just to avoid the question." -- Kansas -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 00:18:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21041 for freebsd-current-outgoing; Fri, 29 May 1998 00:18:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA20991 for ; Fri, 29 May 1998 00:18:37 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id AAA11535 for ; Fri, 29 May 1998 00:12:51 -0700 (PDT) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id JAA10798; Fri, 29 May 1998 09:17:53 +0200 (MEST) (envelope-from kuku) Message-ID: <19980529091752.13151@gil.physik.rwth-aachen.de> Date: Fri, 29 May 1998 09:17:52 +0200 From: Christoph Kukulies To: Bruce Evans Cc: kuku@gilberto.physik.RWTH-Aachen.DE, eivind@FreeBSD.ORG, freebsd-current@freefall.cdrom.com Subject: Re: help! - nodes.h where is it? References: <199805282238.IAA07718@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199805282238.IAA07718@godzilla.zeta.org.au>; from Bruce Evans on Fri, May 29, 1998 at 08:38:56AM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 29, 1998 at 08:38:56AM +1000, Bruce Evans wrote: > >> >> It looks like your src/share/mk/bsd.prog.mk is broken. > >... > >Doing a make depend first then helped. Sorry, maybe it's just that I > >forgot make depend. But should make do it anyway when no .depend > >file exists? > > `make depend' used to be necessary in some cases, but I fixed that > using general methods in bsd.prog.mk and removed special hacks for it > in places like sh/Makefile. It still looks like your bsd.prog.mk is > broken or you have a stale .depend file :-). I definitely copied over /usr/src/share/mk/* to /usr/share/mk and I deleted my obj tree. There wasn't definitely no .depend in /usr/src/bin/sh nor in the corresponding obj path (prior to deleting it anyway). Hmm, maybe just a woodoo day :-) I'm starting a new make world right now and see what it gives. > > Bruce -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 00:27:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22808 for freebsd-current-outgoing; Fri, 29 May 1998 00:27:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22778 for ; Fri, 29 May 1998 00:27:34 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Fri, 29 May 1998 03:26:57 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FACA@freya.circle.net> From: tcobb To: "'Julian Elischer'" Cc: "'Greg Lehey'" , "'Mike Smith'" , "'freebsd-current@freebsd.org'" Subject: RE: DPT driver fails and panics with Degraded Array Date: Fri, 29 May 1998 03:26:56 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I guess this is really something you want to discuss with simon. > I'm sure he will contact you soon > He's just finished moving houes and has been out-of-touch fro > a few weeks > > julian Yes. I am going to contact DPT tomorrow about obtaining the NDA-bound specs for the board. We have some development talent in-house to commit to stabilizing this driver. Our choices are either: a) wait for Simon to stabilize the driver b) try to stabilize the driver ourselves, release code back to FreeBSD c) scrap FreeBSD on this HA server (Solaris,Linux,NT all have native support for DPT) d) scrap DPT and use a SCSI-to-SCSI based RAID solution Given our current committment to DPT and FreeBSD so far, I'd prefer a or b above. I'm not confident of a) happening quickly, as Simon appears to be either busy with other projects or relatively unavailable. As for b) we're mostly application hackers, not driver hackers, so it may be a stretch. -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Julian Elischer [mailto:julian@whistle.com] > Sent: Friday, May 29, 1998 2:33 AM > To: tcobb > Cc: 'Greg Lehey'; 'Mike Smith'; 'freebsd-current@freebsd.org' > Subject: RE: DPT driver fails and panics with Degraded Array > > > I guess this is really something you want to discuss with simon. > I'm sure he will contact you soon > He's just finished moving houes and has been out-of-touch fro > a few weeks > > julian > > > On Fri, 29 May 1998, tcobb wrote: > > > > -----Original Message----- > > > From: Greg Lehey [mailto:grog@lemis.com] > > > > > If you just want to report a bug, use send-pr. That will > reach the > > > person responsible for it as quickly as possible > (consider that a lot > > > of us just drop some of the mailing lists when the combined volume > > > gets too high). The purpose of sending the message to -CURRRENT > > > would be to draw the problem to the attention of other > people using > > > the software. > > > > Indeed. And that was the point of sending to > freebsd-current. I wanted > > anyone using the DPT driver and expecting it to perform > appropriately in > > critical circumstances to know that it will not do so. I > perhaps should > > have sent the email to -hackers instead? Or, maybe -scsi, > like I did -- > > it is a scsi driver problem I'm talking about. > > > > I chose HA hardware for the particular reason that the > server needs to > > be *available*. I settled on FreeBSD for all the servers I > manage 2.5 > > years ago because it was the highest quality OS for Intel > architectures. > > > > > > "Indicators" are that I shouldn't be using FreeBSD for any High > > > > Availability or critical operations -- I AM using FreeBSD > > > for > 15 live > > > > servers. > > > > > > > > Now, what was your point? > > > > > > > > > Basically, I'd guess Mike is saying "don't use FreeBSD-CURRENT in > > > production environments". > > > > I agree. I wouldn't have done so without provocation. My > counterpoint > > is that FreeBSD-STABLE is NOT stable, either. Regardless, due to > > show-stopper bugs in -stable... > > > > My choices were: > > > > 1. Discard FreeBSD completely for this server. > > 2. Switch to a -current snapshot. > > > > I didn't want to do #1, so I spent two weeks rolling a > -current snapshot > > release for my in-house use, I tested it, and tested it. > It works well. > > > > My posting was really to point to the fact that it appears > that the DPT > > driver is deficient across ALL releases, not just -current. > > > > Believe me, I understand the uncharted waters I've entered with my > > -current snapshot. The DPT driver failure was the unexpected thing. > > > > > > -Troy Cobb > > Circle Net, Inc. > > http://www.circle.net > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 00:31:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23587 for freebsd-current-outgoing; Fri, 29 May 1998 00:31:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23562; Fri, 29 May 1998 00:31:22 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA22858; Fri, 29 May 1998 00:31:08 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Brian Somers cc: Mike Smith , sos@FreeBSD.ORG, wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG Subject: Re: cvs commit: src Makefile src/etc rc src/etc/mtree BSD.usr.dist In-reply-to: Your message of "Fri, 29 May 1998 07:40:08 BST." <199805290640.HAA00434@awfulhak.org> Date: Fri, 29 May 1998 00:31:08 -0700 Message-ID: <22854.896427068@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We also need to bump __FreeBSD_version before any snaps get released, > otherwise it's gonna create problems for me. Has anyone any > objections ? Only that the snap was released 5 days ago. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 00:40:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25359 for freebsd-current-outgoing; Fri, 29 May 1998 00:40:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from serv.unibest.ru (serv.unibest.ru [194.87.33.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA25275 for ; Fri, 29 May 1998 00:40:02 -0700 (PDT) (envelope-from osa@unibest.ru) Received: (qmail 2841 invoked from network); 29 May 1998 07:39:59 -0000 Received: from softdnserror (HELO hole.etrust.ru) (192.168.30.2) by serv.unibest.ru with SMTP; 29 May 1998 07:39:59 -0000 Date: Fri, 29 May 1998 11:42:12 +0400 (MSD) From: Ozz!!! X-Sender: osa@hole.etrust.ru To: FreeBSD-current mail-list Subject: options NFS_NOSERVER ???? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Does NFS_NOSERVER enable in 3.0-980520 ??? In my new kernel i say : options NFS_NOSERVER # config MYKERNEL MYKERNEL:30: unknown option "NFS_NOSERVER" .... What can I do ? Rgdz, oZZ, osa@unibest.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 01:03:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28445 for freebsd-current-outgoing; Fri, 29 May 1998 01:03:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28432 for ; Fri, 29 May 1998 01:03:50 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id JAA25222; Fri, 29 May 1998 09:03:45 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <356E6BE1.50B8AEC1@tdx.co.uk> Date: Fri, 29 May 1998 09:03:45 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: tcobb CC: "'freebsd-current@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FAC2@freya.circle.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tcobb wrote: > > I have a DPT3344UW/2 running an external 24GB array. OS is FreeBSD > CURRENT circa 5/18/98. I'm running the latest available firmware flash > for the card, all on a P5-233MMX with 128MB RAM. > > Recently I lost a harddrive in my 24GB RAID5 array. The array was > configured with a HOT SPARE which should have allowed it to rebuild > completely online, with no interruption in service (except some minor > slowdowns, perhaps). While the HARDWARE worked well, the DPT DRIVER > failed miserably. One comment (and it's not a flame!) - honestly... ;-) With an array of that size, on a machine that important - did you not test to see what would happen with a failed drive? The only system we have running with RAID at the moment is an NT box on an HP Netserver - but even with that, we pulled a drive to 'see what happened' - and a) make sure it works, and b) note down any important steps to recovering it... We did this before we certified the machines as 24/7 & 'mission critical' (It also shows that even with NT & 'expensive' hardware, theres always stuff they leave out the manual, or have changed on screen, but not in the manual ;-) Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 01:12:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29686 for freebsd-current-outgoing; Fri, 29 May 1998 01:12:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29661 for ; Fri, 29 May 1998 01:12:37 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Fri, 29 May 1998 04:12:01 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FACD@freya.circle.net> From: tcobb To: "'Karl Pielorz'" Cc: "'freebsd-current@freebsd.org'" Subject: RE: DPT driver fails and panics with Degraded Array Date: Fri, 29 May 1998 04:12:00 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Karl Pielorz [mailto:kpielorz@tdx.co.uk] > Sent: Friday, May 29, 1998 4:04 AM > To: tcobb > Cc: 'freebsd-current@freebsd.org' > Subject: Re: DPT driver fails and panics with Degraded Array > > > tcobb wrote: > > > > I have a DPT3344UW/2 running an external 24GB array. OS is FreeBSD > > CURRENT circa 5/18/98. I'm running the latest available > firmware flash > > for the card, all on a P5-233MMX with 128MB RAM. > > > > Recently I lost a harddrive in my 24GB RAID5 array. The array was > > configured with a HOT SPARE which should have allowed it to rebuild > > completely online, with no interruption in service (except > some minor > > slowdowns, perhaps). While the HARDWARE worked well, the DPT DRIVER > > failed miserably. > > One comment (and it's not a flame!) - honestly... ;-) No flame taken ;) > With an array of that size, on a machine that important - did > you not test > to see what would happen with a failed drive? Actually, we did that when we first implemented this array last November. Yanked a drive. The hardware screamed (beeped like a banshee), the system kept operating then but wasn't under any real load. Despite pre-certification testing, something will be different when you have a failure in production. The difference in our case, I'm guessing, was that the array is now 60-75% full, and the OS version is different, and the system was under heavy access load, too. The original driver was an over-hacked version stuffed into 2.2.2, the newest driver IS better integrated, and actually faster, but obviously unable to handle the under-load failure situation in exactly the way we had it happen. -Troy Cobb Circle Net, Inc. http://www.circle.net > The only system we have running with RAID at the moment is an > NT box on an > HP Netserver - but even with that, we pulled a drive to 'see > what happened' > - and a) make sure it works, and b) note down any important steps to > recovering it... > > We did this before we certified the machines as 24/7 & > 'mission critical' > (It also shows that even with NT & 'expensive' hardware, > theres always stuff > they leave out the manual, or have changed on screen, but not > in the manual > ;-) > > Regards, > > Karl Pielorz > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 01:24:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01477 for freebsd-current-outgoing; Fri, 29 May 1998 01:24:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01470 for ; Fri, 29 May 1998 01:24:34 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id IAA05068; Fri, 29 May 1998 08:22:56 GMT Date: Fri, 29 May 1998 17:22:56 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: Eivind Eklund cc: joelh@gnu.org, rnordier@nordier.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <19980528212713.63593@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 May 1998, Eivind Eklund wrote: > On Thu, May 28, 1998 at 01:29:34PM -0500, Joel Ray Holveck wrote: > > My own concern would be the amount of code in third-party programs > > that uses gccisms. I guess I don't see why we're looking to change. This is an interesting point. I talked Carl Rigney at Livingston recently and their position is that only gcc is supported for their radius distribution. So I submitted patches using __FreeBSD__ consistent with how it was done with other platforms so that radius2.1 will build for FreeBSD out the box using ... make EXT=FreeBSD build Regards, Mike P.S. The Lucent PM3 is a pretty cool box. No more Ascends for me. > Well, here are a couple of points: > * License > * General quality of system (GCC is written under the paradigm 'learn > writing compilers as we go') > * Possibilities for exploiting the cross-CPU nature of XANDF > * Better error checking/control > * Choice (by being able to be compiled with more than one compiler) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 01:27:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01926 for freebsd-current-outgoing; Fri, 29 May 1998 01:27:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01921 for ; Fri, 29 May 1998 01:27:17 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id JAA26011; Fri, 29 May 1998 09:27:14 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <356E7162.91E85509@tdx.co.uk> Date: Fri, 29 May 1998 09:27:14 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: tcobb CC: current@FreeBSD.ORG Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FACD@freya.circle.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tcobb wrote: > > With an array of that size, on a machine that important - did > > you not test > > to see what would happen with a failed drive? > > Despite pre-certification testing, something will be different when you > have a failure in production. The difference in our case, I'm guessing, > was that the array is now 60-75% full, and the OS version is different, > and the system was under heavy access load, too. The original driver > was an over-hacked version stuffed into 2.2.2, the newest driver IS > better integrated, and actually faster, but obviously unable to handle > the under-load failure situation in exactly the way we had it happen. We did our tests under load, but not with a 'full' array (it was at about 20-30%)... We've never changed the operating system 'under' it, I know that it would be checked again if the driver was ever changed (and to be honest it would have to be a pretty dire problem to change the driver while the machines 'online' - it would normally be made off-line or taken out the loop first). I'll also admit that we were looking at the DPT solution for our next FreeBSD box... I think we'll either wait a while now (or I'll just keep quiet and add a few extra weeks to the testing phase for the machine - I'd prefer the latter for obvious reasons... ;-) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 01:32:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02639 for freebsd-current-outgoing; Fri, 29 May 1998 01:32:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02630 for ; Fri, 29 May 1998 01:32:54 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id BAA01622 for ; Fri, 29 May 1998 01:32:52 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805290832.BAA01622@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: ACE is for Elves! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 01:32:52 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Previously, it was very difficult to build the ACE's network service program netsvc with a.out format . At any rate , things are moving along very nicely in elf land 8) {root} pwd /usr/home/hasty/ace/ACE_wrappers/netsvcs/servers {root} file main main: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked, not stripped {root} ./main starting up daemon ./main opening dynamic service Logger did dynamic on Logger, error = 0 opening dynamic service Time_Service starting up Time Server at port 20222 on handle 9 did dynamic on Time_Service, error = 0 opening dynamic service Name_Server starting up Name Server at port 20012 on handle 10 did dynamic on Name_Server, erro Enjoy, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 01:36:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03539 for freebsd-current-outgoing; Fri, 29 May 1998 01:36:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03510 for ; Fri, 29 May 1998 01:36:44 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Fri, 29 May 1998 04:36:07 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FACE@freya.circle.net> From: tcobb To: "'Karl Pielorz'" Cc: current@FreeBSD.ORG Subject: RE: DPT driver fails and panics with Degraded Array Date: Fri, 29 May 1998 04:36:04 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Karl Pielorz [mailto:kpielorz@tdx.co.uk] > Sent: Friday, May 29, 1998 4:27 AM > To: tcobb > Cc: current@freebsd.org > Subject: Re: DPT driver fails and panics with Degraded Array > > > tcobb wrote: > > > > With an array of that size, on a machine that important - did > > > you not test > > > to see what would happen with a failed drive? > > > > Despite pre-certification testing, something will be > different when you > > have a failure in production. The difference in our case, > I'm guessing, > > was that the array is now 60-75% full, and the OS version > is different, > > and the system was under heavy access load, too. The > original driver > > was an over-hacked version stuffed into 2.2.2, the newest driver IS > > better integrated, and actually faster, but obviously > unable to handle > > the under-load failure situation in exactly the way we had > it happen. > > We did our tests under load, but not with a 'full' array (it > was at about > 20-30%)... We've never changed the operating system 'under' > it, I know that > it would be checked again if the driver was ever changed (and > to be honest > it would have to be a pretty dire problem to change the > driver while the > machines 'online' - it would normally be made off-line or > taken out the loop > first). Undoubtably our testing of the most recent upgrades was less adequate than I'd realized. We were under some pressure to resolve the unpredictable (every 2 days or so) "biodone" panics that had appeared 2 weeks after upgrading to 2.2.6. The annoying thing was that these panics did not occur during the 2.2.6 testing phase that we DID do, but that just means we didn't run it long enough, I suppose. > I'll also admit that we were looking at the DPT solution for our next > FreeBSD box... I think we'll either wait a while now (or I'll > just keep > quiet and add a few extra weeks to the testing phase for the > machine - I'd > prefer the latter for obvious reasons... ;-) Smart move :) I'll certainly release whatever improvements to the driver we come up with. I'm currently under some pressure to implement a complete alternative (SCSI-to-SCSI or another OS entirely) but I'm pushing for finding a way to stabilize our current solution. I respect the DPT HARDWARE, and have high hopes that some positive changes can be made to the driver. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 01:37:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03691 for freebsd-current-outgoing; Fri, 29 May 1998 01:37:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03652 for ; Fri, 29 May 1998 01:37:37 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id IAA05161; Fri, 29 May 1998 08:36:31 GMT Date: Fri, 29 May 1998 17:36:30 +0900 (JST) From: Michael Hancock To: Karl Pielorz cc: tcobb , "'freebsd-current@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array In-Reply-To: <356E6BE1.50B8AEC1@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 May 1998, Karl Pielorz wrote: > One comment (and it's not a flame!) - honestly... ;-) > > With an array of that size, on a machine that important - did you not test > to see what would happen with a failed drive? > I recently got a DPT too for a production system but my needs were not as critical. I use a SYM53C875 for the system disk and the DPT with 2 mirrored drives for data. I can do some experimentation during off hours with this system. I would like to see the DPT stabilize such that large arrays could be used reliably so I'll try and test patches against 2.2.6, after I work out a budget to get more drives. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 01:42:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04773 for freebsd-current-outgoing; Fri, 29 May 1998 01:42:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04710 for ; Fri, 29 May 1998 01:42:46 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id IAA05230; Fri, 29 May 1998 08:41:48 GMT Date: Fri, 29 May 1998 17:41:48 +0900 (JST) From: Michael Hancock To: richard@axil.com cc: current@FreeBSD.ORG Subject: Re: FreeBSD on 8-way SMP PPro In-Reply-To: <199805282142.RAA02782@mint.axil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 28 May 1998 richard@axil.com wrote: > I have a hacked version of FreeBSD 3.0-980426-SNAP running > on an Axil NX801 (8-way SMP PentiumPro 200MHz, 2 IOAPICs, > 4 PCI buses, 7 NCR 53c875 scsi, up to 8GB DRAM and 24*9GB disk, > see http://www.axil.com for details). > Is this a record for the biggest machine running FreeBSD ? For CPU and RAM, I think it is. > At the moment the hacks are not clean or safe for other > hardware, so I won't submit patches yet, but here is a brief > description of the changes: This kind of stuff is very much appreciated. Thanks! Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 02:44:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29477 for freebsd-current-outgoing; Fri, 29 May 1998 02:44:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29402; Fri, 29 May 1998 02:44:39 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id JAA07262; Fri, 29 May 1998 09:44:35 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA25768; Fri, 29 May 1998 11:44:21 +0200 (MET DST) Message-ID: <19980529114301.44319@follo.net> Date: Fri, 29 May 1998 11:43:01 +0200 From: Eivind Eklund To: tcobb , "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FAC2@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAC2@freya.circle.net>; from tcobb on Thu, May 28, 1998 at 10:49:23PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 28, 1998 at 10:49:23PM -0400, tcobb wrote: > I believe that the DPT DRIVER is not correctly sensing that the array is > okay, even though it is in degraded mode, and incorrectly returns > sector/MB values which panic the kernel. I don't recommend depending on > the proper operation of this driver for your High-Availability needs. I have an older DPT, but I still want to add my experiences to the above: (1) I've had my array (a 2GB RAID1 - personal RAID :-) run in degraded mode. This has worked just fine with the driver in -current, with the RAID full (of partitions, not data. I can't understand that the amount of data should make a difference - the controller shouldn't know about this anyway). (2) The DPT controller on this has reported alternating wrong sense of the disk setup to the BIOS. This is obviously NOT a driver problem. As for your problems, I'm sorry to hear about them, but have no idea how to fix it. I've had none of the problems you have :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 02:50:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01081 for freebsd-current-outgoing; Fri, 29 May 1998 02:50:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01022; Fri, 29 May 1998 02:50:09 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Fri, 29 May 1998 05:49:31 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net> From: tcobb To: "'Eivind Eklund'" , "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: RE: DPT driver fails and panics with Degraded Array Date: Fri, 29 May 1998 05:49:30 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Eivind Eklund [mailto:eivind@yes.no] > Sent: Friday, May 29, 1998 5:43 AM > To: tcobb; 'freebsd-current@freebsd.org'; 'freebsd-scsi@freebsd.org' > Subject: Re: DPT driver fails and panics with Degraded Array > > > On Thu, May 28, 1998 at 10:49:23PM -0400, tcobb wrote: > > I believe that the DPT DRIVER is not correctly sensing that > the array is > > okay, even though it is in degraded mode, and incorrectly returns > > sector/MB values which panic the kernel. I don't recommend > depending on > > the proper operation of this driver for your > High-Availability needs. > > I have an older DPT, but I still want to add my experiences to the > above: > > (1) I've had my array (a 2GB RAID1 - personal RAID :-) run in degraded > mode. This has worked just fine with the driver in -current, with > the RAID full (of partitions, not data. I can't understand that > the amount of data should make a difference - the controller > shouldn't know about this anyway). Perhaps the difference is RAID-1 versus RAID-5. > (2) The DPT controller on this has reported alternating wrong sense of > the disk setup to the BIOS. This is obviously NOT a driver > problem. True. Interestingly enough, I've never had a problem with the wrong BIOS info from my DPT card. Only with the incorrect sensed info when using the DPT driver on a RAID-5 array when that array is in degraded mode. The fact that it panics trying to boot is amazing to me. It is NOT trying to boot from the RAID-5 by the way. > As for your problems, I'm sorry to hear about them, but have no idea > how to fix it. I've had none of the problems you have :-( Lucky for you, less so for me. ;) -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 02:53:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02123 for freebsd-current-outgoing; Fri, 29 May 1998 02:53:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA02054 for ; Fri, 29 May 1998 02:53:22 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id CAA01821; Fri, 29 May 1998 02:03:22 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805290903.CAA01821@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 to: richard@axil.com, current@FreeBSD.ORG Subject: Re: FreeBSD on 8-way SMP PPro In-reply-to: Your message of "Fri, 29 May 1998 17:41:48 +0900." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 02:03:21 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, What was the maximum amount of memory that you tested? > 4 PCI buses, 7 NCR 53c875 scsi, up to 8GB DRAM and 24*9GB disk, Tnks! Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 03:27:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16594 for freebsd-current-outgoing; Fri, 29 May 1998 03:27:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16463; Fri, 29 May 1998 03:27:30 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id KAA09157; Fri, 29 May 1998 10:27:25 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA25887; Fri, 29 May 1998 12:27:11 +0200 (MET DST) Message-ID: <19980529122551.16212@follo.net> Date: Fri, 29 May 1998 12:25:51 +0200 From: Eivind Eklund To: tcobb , "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net>; from tcobb on Fri, May 29, 1998 at 05:49:30AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 29, 1998 at 05:49:30AM -0400, tcobb wrote: > > (1) I've had my array (a 2GB RAID1 - personal RAID :-) run in degraded > > mode. This has worked just fine with the driver in -current, with > > the RAID full (of partitions, not data. I can't understand that > > the amount of data should make a difference - the controller > > shouldn't know about this anyway). > > Perhaps the difference is RAID-1 versus RAID-5. This might be so, or there might (I'm probably blaspheming by saying this) be a difference or bug in the handling of degradation from DPT to DPT. What is obvious is only that you're having problems with a particular controller/driver/kernel combination, and that a part of the driver has problems coping with failure somewhere else. I don't think it would be wise to consider the problem to be narrowed down more than that. Now, to be able to debug this as effectively as possible I suggest you/we try to create a list of test-cases that we believe would lock down the problem: Hypothesis 1: The problem occur when using your type of controller, RAID5+HotSpare, "large" amounts of capacity used, your kernel, and a disk fail. Verification: Create above setup, try to fail a disk on it. Now, which parameters to vary depend on whether we can get the above to crash. It might be dependent on having exactly equal disks, too :-( Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 03:32:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18724 for freebsd-current-outgoing; Fri, 29 May 1998 03:32:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18656; Fri, 29 May 1998 03:32:07 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id KAA09421; Fri, 29 May 1998 10:32:03 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id MAA25905; Fri, 29 May 1998 12:31:49 +0200 (MET DST) Message-ID: <19980529123029.12289@follo.net> Date: Fri, 29 May 1998 12:30:29 +0200 From: Eivind Eklund To: tcobb , "'freebsd-current@freebsd.org'" , "'freebsd-scsi@freebsd.org'" Subject: Re: DPT driver fails and panics with Degraded Array References: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net> <19980529122551.16212@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980529122551.16212@follo.net>; from Eivind Eklund on Fri, May 29, 1998 at 12:25:51PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 29, 1998 at 12:25:51PM +0200, Eivind Eklund wrote: > Hypothesis 1: The problem occur when using your type of controller, > RAID5+HotSpare, "large" amounts of capacity used, your kernel, and > a disk fail. > Verification: Create above setup, try to fail a disk on it. > > Now, which parameters to vary depend on whether we can get the above > to crash. It might be dependent on having exactly equal disks, too > :-( This was a pretty dumb way of saying this. What I meant was that forming further hypotheses/verifiction pairs in any effective manner seems pretty difficult without knowing the results of the above test. If you have more data, or more hypotheses/verification pairs, then come with 'em. If you want to be 100% certain of coming to a conclusion, this is usually the way to do it (but it can be expensive in terms of the number of tests you have to do). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 03:36:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20565 for freebsd-current-outgoing; Fri, 29 May 1998 03:36:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20525 for ; Fri, 29 May 1998 03:36:10 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id OAA00708 for ; Fri, 29 May 1998 14:36:05 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Fri, 29 May 1998 14:36:05 +0400 (MSD) From: Hostas Red To: current@FreeBSD.ORG Subject: Strange things happening... :( Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! After rebooting 1 hour ago i've found, that I COMPLETELY CANNOT LOGIN into my system. ;( It doesn't understands any passwords - mine, root and a couple of accounts. After rebooting in single-user mode and passwd'ing some passwords I can login under these accounts, but - still can't login under others. So, noone of my users can't login here, and I can't change passwords for them because I can't contact them fast, and they can't get any mail from my system because of wrong passwords... :( infinite loop. Did we have changed algorythm of encoding passwords in master.passwd? Or this happens because of ELF|usr/lib things? Can't get it... Adios, /KONG PS: cvsup'ed and compiled kernel/world just yesterday night, ~10 hours ago. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 04:08:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08383 for freebsd-current-outgoing; Fri, 29 May 1998 04:08:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from door.bzw.com (www.barclayscapital.com [194.205.158.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08324 for ; Fri, 29 May 1998 04:08:17 -0700 (PDT) (envelope-from Pierre.Dampure@barclayscapital.com) Received: (from mailman@localhost) by door.bzw.com (8.8.8/8.8.7) id MAA14657 for ; Fri, 29 May 1998 12:07:12 +0100 (BST) Received: from gate.bzw.com(194.205.158.68) by door.bzw.com via smap (V2.0) id xma014611; Fri, 29 May 98 12:06:55 +0100 Received: (from nobody@localhost) by gate.bzw.com (8.8.7/8.8.7) id MAA24136 for ; Fri, 29 May 1998 12:07:57 +0100 (BST) Received: from fwgw01-dmz(194.205.158.129) by gate.bzw.com via smap (V2.0) id xma024100; Fri, 29 May 98 12:07:51 +0100 Received: (from nobody@localhost) by fwgw01.ldn.bzwint.com (8.8.7/8.8.7) id MAA29348 for ; Fri, 29 May 1998 12:07:49 +0100 (BST) Received: from oplss0001.itops.ldn.bzwint.com(30.75.1.4) by fwgw01.ldn.bzwint.com via smap (V2.0) id xma029110; Fri, 29 May 98 12:07:12 +0100 Received: from nmb01gw01 (smtphost.ldn.bzwint.com [30.10.1.10]) by oplss0001.itops.ldn.bzwint.com (8.8.7/8.8.6) with SMTP id MAA01585 for ; Fri, 29 May 1998 12:06:38 +0100 (BST) Received: from exintgw03.itops.ldn.bzwint.com (exintgw03.itops.ldn.bzwint.com [30.45.1.86]) by nmb01gw01 (NTMail 3.02.13) with ESMTP id ha778161 for ; Fri, 29 May 1998 11:54:38 +0100 Received: by exintgw03.itops.ldn.bzwint.com with Internet Mail Service (5.0.1460.8) id ; Fri, 29 May 1998 12:02:59 +0100 Message-ID: <711DCB8FB391D111B9DD00805F8BDDBA726306@exips0019.itops.ldn.bzwint.com> From: "Dampure, Pierre-Yves: IT (LDN)" To: "'Hostas Red'" , current@FreeBSD.ORG Subject: RE: Strange things happening... :( Date: Fri, 29 May 1998 12:07:46 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check the previous postings... the *crypt* symlinks in /usr/lib/aout seem to be pointing to the MD5 libraries, not to the DES ones. I think this has been corrected since, but you will need to boot single-user and modify the symlinks + re-passwd the accounts you modified (the MD5 password strings are much longer, that should be easy to recognise). Best Regards, Pierre Y. > -----Original Message----- > From: Hostas Red [SMTP:kong@kong.spb.ru] > Sent: 29 May 1998 11:36 > To: current@freebsd.org > Subject: Strange things happening... :( > > Hi! > > After rebooting 1 hour ago i've found, that I COMPLETELY CANNOT LOGIN into > my system. ;( It doesn't understands any passwords - mine, root and a > couple of accounts. > > After rebooting in single-user mode and passwd'ing some passwords I can > login under these accounts, but - still can't login under others. So, > noone of my users can't login here, and I can't change passwords for them > because I can't contact them fast, and they can't get any mail from my > system because of wrong passwords... :( infinite loop. > > Did we have changed algorythm of encoding passwords in master.passwd? Or > this happens because of ELF|usr/lib things? Can't get it... > > Adios, > /KONG > > PS: cvsup'ed and compiled kernel/world just yesterday night, ~10 hours > ago. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 04:10:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10421 for freebsd-current-outgoing; Fri, 29 May 1998 04:10:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from colossus.dyn.ml.org (dburr@206-18-115-156.la.inreach.net [206.18.115.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10214 for ; Fri, 29 May 1998 04:10:43 -0700 (PDT) (envelope-from dburr@colossus.dyn.ml.org) Received: (from dburr@localhost) by colossus.dyn.ml.org (8.8.8/8.8.7) id EAA20121; Fri, 29 May 1998 04:09:18 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 29 May 1998 04:09:16 -0700 (PDT) Organization: Computer Help From: Donald Burr To: Hostas Red Subject: RE: Strange things happening... :( Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 29-May-98, Hostas Red wrote: > Hi! > > After rebooting 1 hour ago i've found, that I COMPLETELY CANNOT LOGIN > into > my system. ;( It doesn't understands any passwords - mine, root and a > couple of accounts. This happened to someone else on -current a few days ago. Basically, the symlinks for the "crypt" libaries got wiped -- they were using md5 crypt, not des crypt. this (or something similar) is probably what happened to you. check the links and try again. - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNW6XXPjpixuAwagxAQGCIwQAo27fywqssTH3vVFPhSXwVPcvwFcM9Hen KMY92l2MUubqOauwOMozpWNKkMsBZ3rivo4c5fuDp/KSq4yxYiONOkvScWHryOwH jGhVu/y+nxUKh4qwXWPUNt+xKRbf9e8kD0YM01WojZtPG+jGNTU57DWEP7bx8ZRg 22w1fTGVl0Y= =3aTi -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 04:10:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10464 for freebsd-current-outgoing; Fri, 29 May 1998 04:10:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10327 for ; Fri, 29 May 1998 04:10:50 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id NAA27198; Fri, 29 May 1998 13:10:45 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 29 May 1998 13:10:45 +0200 (MET DST) Mime-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG, eivind@yes.no, rnordier@nordier.com Subject: Re: Replacing gcc as the system compiler References: <199805282221.IAA06688@godzilla.zeta.org.au> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 29 May 1998 13:10:44 +0200 In-Reply-To: Bruce Evans's message of "Fri, 29 May 1998 08:21:15 +1000" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > > execl("/bin/sh", "-sh", 0); > Read what you wrote in the previous paragraph. execl() is varargs, so > its varadic parameters must not be uncast 0s or NULLs. I saw the mistake after posting. Sorry. -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 04:16:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14152 for freebsd-current-outgoing; Fri, 29 May 1998 04:16:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14079 for ; Fri, 29 May 1998 04:16:11 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id NAA27950; Fri, 29 May 1998 13:15:56 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 29 May 1998 13:15:55 +0200 (MET DST) Mime-Version: 1.0 To: Robert Nordier Cc: bde@zeta.org.au, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Replacing gcc as the system compiler References: <199805281835.UAA26210@ceia.nordier.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 29 May 1998 13:15:54 +0200 In-Reply-To: Robert Nordier's message of "Thu, 28 May 1998 20:35:07 +0200 (SAT)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier writes: > I'm not sure why you feel the correct prototype > > int execl(const char *, const char *, ...); > > has a significant effect in this case. The ellipsis doesn't mean I meant one thing and wrote the other. I think I'll just shut up until after I have read the draft proposal. -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 04:33:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19455 for freebsd-current-outgoing; Fri, 29 May 1998 04:33:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19348 for ; Fri, 29 May 1998 04:33:44 -0700 (PDT) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA23356; Fri, 29 May 1998 07:09:31 -0400 (EDT) From: Peter Dufault Message-Id: <199805291109.HAA23356@hda.hda.com> Subject: Re: cdrecord trouble on currnet In-Reply-To: <199805290119.LAA20313@godzilla.zeta.org.au> from Bruce Evans at "May 29, 98 11:19:43 am" To: bde@zeta.org.au (Bruce Evans) Date: Fri, 29 May 1998 07:09:30 -0400 (EDT) Cc: dufault@hda.com, mike@smith.net.au, 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-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > if (sysconf(_SC_PRIORITY_SCHEDULING) == -1) { > > if (errno != 0) { > > /* This isn't valid: > > */ (...) > The "This isn't valid" case isn't valid, since sysconf() doesn't change > errno if there is no error. errno must be set before calling sysconf(). I needed to cut a few more lines: > /* Is priority scheduling configured? > */ > errno = 0; > if (sysconf(_SC_PRIORITY_SCHEDULING) == -1) { Remember: Bruce is watching. Measure twice, cut once. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 05:34:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17834 for freebsd-current-outgoing; Fri, 29 May 1998 05:34:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17793 for ; Fri, 29 May 1998 05:33:57 -0700 (PDT) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id OAA09148; Fri, 29 May 1998 14:33:52 +0200 (MET DST) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 29 May 1998 14:33:51 +0200 (MET DST) Mime-Version: 1.0 To: Hostas Red Cc: current@FreeBSD.ORG Subject: Re: Strange things happening... :( References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-Stop-Spam: http://www.cauce.org From: dag-erli@ifi.uio.no (Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 29 May 1998 14:33:51 +0200 In-Reply-To: Hostas Red's message of "Fri, 29 May 1998 14:36:05 +0400 (MSD)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hostas Red writes: > After rebooting 1 hour ago i've found, that I COMPLETELY CANNOT LOGIN into > my system. ;( It doesn't understands any passwords - mine, root and a > couple of accounts. Search for "MD5" in the freebsd-current archive. What has happened is that your system has mistakenly switched to using MD5 passwords instead of DES passwords. This problem was identified (and solved?) a few days ago. -- Noone else has a .sig like this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 05:59:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27870 for freebsd-current-outgoing; Fri, 29 May 1998 05:59:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27673 for ; Fri, 29 May 1998 05:58:38 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id QAA23361; Fri, 29 May 1998 16:58:04 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Fri, 29 May 1998 16:58:03 +0400 (MSD) From: Hostas Red To: "Dampure, Pierre-Yves: IT (LDN)" cc: current@FreeBSD.ORG Subject: RE: Strange things happening... :( In-Reply-To: <711DCB8FB391D111B9DD00805F8BDDBA726306@exips0019.itops.ldn.bzwint.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Fri, 29 May 1998, Dampure, Pierre-Yves: IT (LDN) wrote: > Check the previous postings... the *crypt* symlinks in /usr/lib/aout seem to > be pointing to the MD5 libraries, not to the DES ones. I think this has been > corrected since, but you will need to boot single-user and modify the > symlinks + re-passwd the accounts you modified (the MD5 password strings are > much longer, that should be easy to recognise). Thank You, and all, who answered my Q. I've changed links of libcrypt* from libscrypt* to libdescrypt*. Thank You and all once more. :) Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 06:50:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27354 for freebsd-current-outgoing; Fri, 29 May 1998 06:50:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27233 for ; Fri, 29 May 1998 06:50:37 -0700 (PDT) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.8/8.8.8) id PAA25118; Fri, 29 May 1998 15:45:59 +0200 (CEST) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199805291345.PAA25118@ocean.campus.luth.se> Subject: Re: cvs commit: src Makefile src/etc rc src/etc/mtree BSD.usr.dist In-Reply-To: <22854.896427068@time.cdrom.com> from "Jordan K. Hubbard" at "May 29, 98 00:31:08 am" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Fri, 29 May 1998 15:45:58 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > > We also need to bump __FreeBSD_version before any snaps get released, > > otherwise it's gonna create problems for me. Has anyone any > > objections ? > > Only that the snap was released 5 days ago. :-) Well, that was before the the ELF commits which causes the problem, no? /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 07:17:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10915 for freebsd-current-outgoing; Fri, 29 May 1998 07:17:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.175.134.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10824 for ; Fri, 29 May 1998 07:17:10 -0700 (PDT) (envelope-from schilling@fokus.gmd.de) Received: from sherwood.gmd.de (sherwood [193.175.133.102]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id QAA07375; Fri, 29 May 1998 16:14:34 +0200 (MET DST) Received: (from jes@localhost) by sherwood.gmd.de (8.8.8+Sun/8.8.8) id QAA12750; Fri, 29 May 1998 16:14:14 +0200 (MET DST) Date: Fri, 29 May 1998 16:14:14 +0200 (MET DST) From: Joerg Schilling Message-Id: <199805291414.QAA12750@sherwood.gmd.de> To: freebsd-current@FreeBSD.ORG, schilling@fokus.gmd.de Subject: Re: cdrecord trouble on currnet Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First some notes. You are discussing things related to cdrecord. If you like to see your effort back in the main stream cdrecord, this is definitely the wring mailing list. cdwrite@lists.debian.org is the list for discussions related to cdrecord. I got your mail only by accident from dejanews. >> > I am getting write errors on my Philips 2600 CD-R using cd-write and burncd.sh >> > (from /usr/share/examples/worm/ ) so I thought , I'l compile cdrecord and try >> > that. But I get the following error when truying to do a dummy burn: >> > >> > $ sudo cdrecord -dev=0,4,0 -data -dummy /scratch/img/psnl >> > Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling >> > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler This seems to be a problem in FreeBSD & the Posix standard. All other operating systems that define _POSIX_PRIORITY_SCHEDULING have it functional. >> > Bus error (core dumped) If you are not able to analyze the core with adb and send a usable bug description, I cannot help.. >> > This is a freshly compiled port on a current cvsupped today. >> >> (I wonder why he is trying to use the round robin scheduler - I >> expect he wants the FIFO one). >> >> Cdrecord has autoconf'd in the P1003.1B scheduler interface. >> >> I'm probably going to have to change how I did things, but the >> program may need fixing also. By default, with nothing defined, >> the new system calls are setup to be LKM'd in for development and >> will fail at run time with ENOSYS or if you check for their presense >> with sysconf(). >> You can add build time support with the _KPOSIX_PRIORITY_SCHEDULING >> >> See how cdrecord is deciding to use priority scheduling. If it >> decides that a program that links OK without checking any compile >> time feature test macros means that priority scheduling is supported, >> then that should be changed. I've been told some programs are >> doing this (not specifically cdrecord). >I looked at the cdrecord source and the code calling sched_scheduler is in >an #ifdef _POSIX_PRIORITY_SCHEDULING block. >Apperently that gets defined in /usr/include/sys/unistd.h because _posix.h >defines _P1003_1B_VISIBLE Do you have any newer pointers to on-line versions of the POSIX standard? >> If you set _POSIX_C_SOURCE to 199009L with a -D in the makefile >> and cderecord still tries to use the round robin scheduler then >> someone has screwed up - either us or cdrecord - so try that too. Is is not as easy as you think!!!!! Cdrecord is not a FreeBSD program. It is highly portable and for that reason cannoot adopt to any rubbish added to a specific operating system. On SVr4 systems the _POSIX_PRIORITY_SCHEDULING is definitely worse than the RT priocntl() interface and proicntl with RR scheduling is even available since the early days of SVr4. I cannot change the source in a way that only makes sure that nothing works after the change. >> It checks _POSIX_PRIORITY_SCHEDULING at build time. > >That's understandable, then. >> Can you give an example of the correct mechanism for using sysconf() to >> determine the availability of the scheduler? I'll fix it in the >> updates I'm working on. > if (sysconf(_SC_PRIORITY_SCHEDULING) == -1) { > if (errno != 0) { > /* This isn't valid: > */ > err(EX_OSERR, "sysconf(_SC_PRIORITY_SCHEDULING)"); > } > else { > errx(EX_UNAVAILABLE, > "No run-time support for POSIX priority scheduling"); > } > } This code is highly non-portable as it uses non-standard interfaces (err & errx) This is a common problem on *BSD. Programs written for *BSD tend to get more and more non-portable. Again: It is not as easy as you expect. If you like to co-operate with me, you should discuss this on the right forum and not in a private play ground. A note to CAM: CAM seems to be very similar in general (but diffrerent in spcific) to an interface called SCSA documented and developped by Sun in 1987-1988. The SCSA API is very similar to the earlier Sun architecture used since 1986. The scg drvier which I wrote in 1986 is based on this interface and itself is the base for my portable SCSI user-level command transport system. It should be faily easy to make a CAM adoption layer for scg. I am currently still working on DVD-R support for cdrecord with is the first UNIX program that supports DVD-R. The new ESO (www.eso.org) supertelescope data will be archived using cdrecord and a DVD-R writer. If this project is finished, I am planning to create a "real" SCSI library from the stuff originally written for 'sformat' and cdrecord. I am also planning an ABI checker for this library which should make it easy to check if a transport adaption layer is written the right way. Jörg EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) If you don't have iso-8859-1 schilling@fokus.gmd.de (work) chars I am J"org Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 07:55:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27010 for freebsd-current-outgoing; Fri, 29 May 1998 07:55:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from enigami.com (enigami.com [208.140.182.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26998 for ; Fri, 29 May 1998 07:54:58 -0700 (PDT) (envelope-from ckempf@enigami.com) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by enigami.com (8.8.7/8.8.7) with ESMTP id KAA24934 for ; Fri, 29 May 1998 10:54:41 -0400 (EDT) Received: (from ckempf@localhost) by singularity.enigami.com (8.8.8/8.8.8) id KAA07335; Fri, 29 May 1998 10:52:00 -0400 (EDT) (envelope-from ckempf@enigami.com) To: freebsd-current@FreeBSD.ORG Subject: MD5 v. DES? From: Cory Kempf Date: 29 May 1998 10:52:00 -0400 In-Reply-To: dag-erli@ifi.uio.no's message of "29 May 1998 14:33:51 +0200" Message-ID: Lines: 20 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav ) writes: >Hostas Red writes: >Search for "MD5" in the freebsd-current archive. What has happened is >that your system has mistakenly switched to using MD5 passwords >instead of DES passwords. This problem was identified (and solved?) a >few days ago. Is there a discussion somewhere about the merits of MD5 v. DES? E.g. what advantages one has over the other? Thanks, +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 08:45:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22395 for freebsd-current-outgoing; Fri, 29 May 1998 08:45:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (omega.Xerox.COM [13.1.64.95]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA22333 for ; Fri, 29 May 1998 08:45:31 -0700 (PDT) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <32627(2)>; Fri, 29 May 1998 08:44:48 PDT Received: from mango.parc.xerox.com (localhost [127.0.0.1]) by mango.parc.xerox.com (8.8.8/8.8.8) with ESMTP id IAA22065; Fri, 29 May 1998 08:44:38 -0700 (PDT) (envelope-from fenner@mango.parc.xerox.com) Message-Id: <199805291544.IAA22065@mango.parc.xerox.com> To: Garrett Wollman cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: and again on forwarding... In-reply-to: Your message of "Tue, 19 May 1998 15:11:45 PDT." <199805192211.SAA22187@khavrinen.lcs.mit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <22062.896456677.1@mango.parc.xerox.com> Date: Fri, 29 May 1998 08:44:37 PDT From: Bill Fenner Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199805192211.SAA22187@khavrinen.lcs.mit.edu>you write: >< .unipi.it> said: >> isn't that also because the output routine (not the input one) will >> free the mbuf once done ? > >Well, sure, but that's easy -- just take a reference. That's what m_copy() does. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 08:52:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24467 for freebsd-current-outgoing; Fri, 29 May 1998 08:52:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dragon.axil.com (dragon.axil.com [206.33.98.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24397 for ; Fri, 29 May 1998 08:52:21 -0700 (PDT) (envelope-from richard.cownie@axil.com) Received: by dragon.axil.com with Internet Mail Service (5.0.1458.49) id ; Fri, 29 May 1998 11:51:50 -0400 Message-ID: From: Richard Cownie To: Mike Smith , jak@cetlink.net Cc: Richard Cownie , current@FreeBSD.ORG Subject: RE: FreeBSD on 8-way SMP PPro Date: Fri, 29 May 1998 11:51:47 -0400 X-Priority: 3 X-Mailer: Internet Mail Service (5.0.1458.49) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That thought had occurred to me ... the surest way to make it happen would be for lots of people to express serious interest in buying NX801/NX803 machines to run FreeBSD. Richard Cownie DISCLAIMER: speaking for myself as usual, not for Axil Computer Inc > -----Original Message----- > From: Mike Smith [SMTP:mike@smith.net.au] > Sent: Friday, May 29, 1998 1:27 AM > To: jak@cetlink.net > Cc: richard@axil.com; current@FreeBSD.ORG > Subject: Re: FreeBSD on 8-way SMP PPro > > BTW, Richard, if Axil wanted to donate one of these systems (or even > an > 803) to the FreeBSD project, we would make sure that FreeBSD *always* > ran properly on it. 8) > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 08:59:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26968 for freebsd-current-outgoing; Fri, 29 May 1998 08:59:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dragon.axil.com (dragon.axil.com [206.33.98.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26938 for ; Fri, 29 May 1998 08:59:47 -0700 (PDT) (envelope-from richard.cownie@axil.com) Received: by dragon.axil.com with Internet Mail Service (5.0.1458.49) id ; Fri, 29 May 1998 11:59:23 -0400 Message-ID: From: Richard Cownie To: Amancio Hasty , Richard Cownie , current@FreeBSD.ORG Subject: RE: FreeBSD on 8-way SMP PPro Date: Fri, 29 May 1998 11:59:19 -0400 X-Priority: 3 X-Mailer: Internet Mail Service (5.0.1458.49) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I only have 256K of DRAM so far - I could borrow a board with 4GB, but it probably wouldn't be interesting until I have a good way of stressing the system (maybe "make -j32 world") ? Richard Cownie > -----Original Message----- > From: Amancio Hasty [SMTP:hasty@rah.star-gate.com] > Sent: Friday, May 29, 1998 5:03 AM > To: richard@axil.com; current@FreeBSD.ORG > Subject: Re: FreeBSD on 8-way SMP PPro > > > Hi, > > What was the maximum amount of memory that you tested? > > > 4 PCI buses, 7 NCR 53c875 scsi, up to 8GB DRAM and 24*9GB disk, > > > Tnks! > Amancio > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 09:04:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29102 for freebsd-current-outgoing; Fri, 29 May 1998 09:04:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28914 for ; Fri, 29 May 1998 09:04:17 -0700 (PDT) (envelope-from mike@seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id MAA21390; Fri, 29 May 1998 12:03:39 -0400 (EDT) Date: Fri, 29 May 1998 12:03:39 -0400 (EDT) From: Mike To: Hostas Red cc: current@FreeBSD.ORG Subject: Re: Strange things happening... :( In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 May 1998, Hostas Red wrote: > After rebooting 1 hour ago i've found, that I COMPLETELY CANNOT LOGIN into > my system. ;( It doesn't understands any passwords - mine, root and a > couple of accounts. What happens if you 'boot: -s' and then vipw, write/quit, reboot. Don't make any changes to master.passwd, just rebuild the database. It's happened here a couple times. --- Mike Hoskins Email: mike@seidata.com SEI Data Network Services, Inc. WWW: http://www.seidata.com P.O. Box 7, 14005 U.S. 50 (BLD2) Voice: 800.925.6746 ex. 251 Dillsboro, IN 47018 Fax: 812.744.8000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 09:05:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29515 for freebsd-current-outgoing; Fri, 29 May 1998 09:05:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles328.castles.com [208.214.167.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29456 for ; Fri, 29 May 1998 09:05:38 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA02770; Fri, 29 May 1998 08:01:11 -0700 (PDT) Message-Id: <199805291501.IAA02770@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Richard Cownie cc: Mike Smith , jak@cetlink.net, current@FreeBSD.ORG Subject: Re: FreeBSD on 8-way SMP PPro In-reply-to: Your message of "Fri, 29 May 1998 11:51:47 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 08:01:11 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That thought had occurred to me ... the surest way to make it happen > would be for lots of people to express serious interest in buying > NX801/NX803 machines to run FreeBSD. Indeed, although the sort of people in that market are probably going to want some sort of indication that it *will* run properly before they are likely to commit to it. The chicken-and-egg problem is always a tough one, but your work is definitely the first step. Now, one more question (*). Do you folks have a loaner system that we could take to Usenix? Heck, can we get that sort of power on the floor there? > Richard Cownie > > DISCLAIMER: speaking for myself as usual, not for Axil Computer Inc Do Axil have an opinion at all about non-NT operating systems and their hardware? There's quite a lot of "wow" power in saying to someone "this guy at Axil has FreeBSD running on one of *these* (points to picture)", and it really does lend some serious credibility to the project. However, it's not the sort of thing that you want to do if Axil corporate have a dim view of other operating systems, so I'd prefer to be a little careful about it. (*) "Ha Ha only serious". -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 09:12:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01853 for freebsd-current-outgoing; Fri, 29 May 1998 09:12:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01788 for ; Fri, 29 May 1998 09:12:04 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-36.camalott.com [208.229.74.36] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA28004; Fri, 29 May 1998 11:10:50 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA06149; Fri, 29 May 1998 11:11:52 -0500 (CDT) (envelope-from joelh) Date: Fri, 29 May 1998 11:11:52 -0500 (CDT) Message-Id: <199805291611.LAA06149@detlev.UUCP> To: ckempf@enigami.com CC: freebsd-current@FreeBSD.ORG In-reply-to: (message from Cory Kempf on 29 May 1998 10:52:00 -0400) Subject: Re: MD5 v. DES? From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there a discussion somewhere about the merits of MD5 v. DES? > E.g. what advantages one has over the other? In the handbook (http://www.freebsd.org/handbook/handbook55.html). But the Reader's Digest version is, MD5 is more secure and is exportable from the US. DES is the algorithm used on other Unix machines (to allow password sharing and NIS). Are there any issues with using the international version of DES in France? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 09:16:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03350 for freebsd-current-outgoing; Fri, 29 May 1998 09:16:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03308 for ; Fri, 29 May 1998 09:16:44 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-36.camalott.com [208.229.74.36] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA28295; Fri, 29 May 1998 11:15:41 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA06189; Fri, 29 May 1998 11:16:42 -0500 (CDT) (envelope-from joelh) Date: Fri, 29 May 1998 11:16:42 -0500 (CDT) Message-Id: <199805291616.LAA06189@detlev.UUCP> To: schilling@fokus.gmd.de CC: freebsd-current@FreeBSD.ORG, schilling@fokus.gmd.de In-reply-to: <199805291414.QAA12750@sherwood.gmd.de> (message from Joerg Schilling on Fri, 29 May 1998 16:14:14 +0200 (MET DST)) Subject: Re: cdrecord trouble on currnet From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199805291414.QAA12750@sherwood.gmd.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > First some notes. You are discussing things related to cdrecord. > If you like to see your effort back in the main stream cdrecord, this > is definitely the wring mailing list. > cdwrite@lists.debian.org > is the list for discussions related to cdrecord. I got your mail only > by accident from dejanews. Could we add this address to the man page? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 09:25:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06836 for freebsd-current-outgoing; Fri, 29 May 1998 09:25:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06796 for ; Fri, 29 May 1998 09:25:41 -0700 (PDT) (envelope-from piquan@wcc.net) Received: from detlev.UUCP (tex-36.camalott.com [208.229.74.36] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id LAA28764; Fri, 29 May 1998 11:24:37 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id LAA06227; Fri, 29 May 1998 11:25:38 -0500 (CDT) (envelope-from joelh) Date: Fri, 29 May 1998 11:25:38 -0500 (CDT) Message-Id: <199805291625.LAA06227@detlev.UUCP> To: freebsd-current@FreeBSD.ORG Subject: SLICE From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does somebody have a pointer to SLICE info (FAQ, whatever)? Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 09:26:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07125 for freebsd-current-outgoing; Fri, 29 May 1998 09:26:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles328.castles.com [208.214.167.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07031 for ; Fri, 29 May 1998 09:26:07 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA02861; Fri, 29 May 1998 08:21:44 -0700 (PDT) Message-Id: <199805291521.IAA02861@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Joerg Schilling cc: freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet In-reply-to: Your message of "Fri, 29 May 1998 16:14:14 +0200." <199805291414.QAA12750@sherwood.gmd.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 29 May 1998 08:21:43 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id JAA07078 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > First some notes. You are discussing things related to cdrecord. > If you like to see your effort back in the main stream cdrecord, this > is definitely the wring mailing list. It's a good place to deal with the specifics of making cdrecord work on FreeBSD though. It's certainly unlikely that Peter would have been listening on the cdrecord list. > >> > $ sudo cdrecord -dev=0,4,0 -data -dummy /scratch/img/psnl > >> > Cdrecord release 1.6 Copyright (C) 1995-1998 Jörg Schilling > >> > cdrecord: Function not implemented. WARNING: Cannot set RR-scheduler > > This seems to be a problem in FreeBSD & the Posix standard. > All other operating systems that define _POSIX_PRIORITY_SCHEDULING > have it functional. The FreeBSD Posix implementation is still under development, and the scheduler module is an optional addition (as allowed for under the spec.). Cdrecord doesn't make the required runtime check for the presence of the desired functionality. > >> > Bus error (core dumped) > > If you are not able to analyze the core with adb and send a usable > bug description, I cannot help.. The bus error is (in my case at any rate) due to a buffer overrun elsewhere. I haven't been able to ascertain the cause of this yet, but there are indications that winding back the visible Posix interface resolves the issue. > >> If you set _POSIX_C_SOURCE to 199009L with a -D in the makefile > >> and cderecord still tries to use the round robin scheduler then > >> someone has screwed up - either us or cdrecord - so try that too. > > Is is not as easy as you think!!!!! > > Cdrecord is not a FreeBSD program. It is highly portable and for that reason > cannoot adopt to any rubbish added to a specific operating system. We're not talking about "rubbish". We're talking about an in-development implementation of the Posix environment. > On SVr4 systems the _POSIX_PRIORITY_SCHEDULING is definitely worse > than the RT priocntl() interface and proicntl with RR scheduling is even > available since the early days of SVr4. I cannot change the source in a way > that only makes sure that nothing works after the change. This sounds like "rubbish" in SysV. > >> It checks _POSIX_PRIORITY_SCHEDULING at build time. > > > >That's understandable, then. > > >> Can you give an example of the correct mechanism for using sysconf() to > >> determine the availability of the scheduler? I'll fix it in the > >> updates I'm working on. > > > if (sysconf(_SC_PRIORITY_SCHEDULING) == -1) { > > if (errno != 0) { > > /* This isn't valid: > > */ > > err(EX_OSERR, "sysconf(_SC_PRIORITY_SCHEDULING)"); > > } > > else { > > errx(EX_UNAVAILABLE, > > "No run-time support for POSIX priority scheduling"); > > } > > } > > This code is highly non-portable as it uses non-standard interfaces (err & errx) > This is a common problem on *BSD. Programs written for *BSD tend to get more and more > non-portable. It's a trivial example intended to give me an idea of what to do about the situation, not a patch to cdrecord (note the absence of patch items). When I have something that works like it "should", I'll certainly be sending you patches. Until then, and while we're pursing the definition of "should" in this context, I see no need to drag you into this unnecessarily. > The scg drvier which I wrote in 1986 is based on this interface and > itself is the base for my portable SCSI user-level command transport > system. It should be faily easy to make a CAM adoption layer for scg. It was. The real problems with scg have to do with the lack of visible documentation. It is unclear how to do any sort of meaningful error handling, or whether this should be managed at a lower level. Again, this is an issue I was postponing until I had established that everything else was going to behave and the interface had stabilised. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 09:27:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07839 for freebsd-current-outgoing; Fri, 29 May 1998 09:27:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.175.134.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07768 for ; Fri, 29 May 1998 09:27:38 -0700 (PDT) (envelope-from schilling@fokus.gmd.de) Received: from sherwood.gmd.de (sherwood [193.175.133.102]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id SAA18411; Fri, 29 May 1998 18:27:12 +0200 (MET DST) Received: (from jes@localhost) by sherwood.gmd.de (8.8.8+Sun/8.8.8) id SAA14763; Fri, 29 May 1998 18:26:46 +0200 (MET DST) Date: Fri, 29 May 1998 18:26:46 +0200 (MET DST) From: Joerg Schilling Message-Id: <199805291626.SAA14763@sherwood.gmd.de> To: joelh@gnu.org, schilling@fokus.gmd.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From piquan@wcc.net Fri May 29 18:16:55 1998 >> First some notes. You are discussing things related to cdrecord. >> If you like to see your effort back in the main stream cdrecord, this >> is definitely the wring mailing list. >> cdwrite@lists.debian.org >> is the list for discussions related to cdrecord. I got your mail only >> by accident from dejanews. >Could we add this address to the man page? OK, I added the following: .SH "MAILING LISTS If you want to actively take part on the development of cdrecord, you may join the cdwriting maling list by sending mail to: .nf .sp cdwrite-request@lists.debian.org .sp .fi and include the word .I subscribe in the body. The mail address of the list is: .nf .sp cdwrite@lists.debian.org .fi .SH AUTHOR .nf J\*org Schilling Seestr. 110 D-13353 Berlin Germany To the cdrecord man page. It will appear in cdrecord-1.8 Jörg EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) If you don't have iso-8859-1 schilling@fokus.gmd.de (work) chars I am J"org Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 09:32:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09466 for freebsd-current-outgoing; Fri, 29 May 1998 09:32:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kong.dorms.spbu.ru (kong@kong.dorms.spbu.ru [195.19.252.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09411 for ; Fri, 29 May 1998 09:31:49 -0700 (PDT) (envelope-from kong@kong.dorms.spbu.ru) Received: from localhost (kong@localhost) by kong.dorms.spbu.ru (8.8.8/kong/0.01) with SMTP id UAA01207; Fri, 29 May 1998 20:31:34 +0400 (MSD) (envelope-from kong@kong.dorms.spbu.ru) Date: Fri, 29 May 1998 20:31:34 +0400 (MSD) From: Hostas Red To: Mike cc: current@FreeBSD.ORG Subject: Re: Strange things happening... :( In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! On Fri, 29 May 1998, Mike wrote: > > After rebooting 1 hour ago i've found, that I COMPLETELY CANNOT LOGIN into > > my system. ;( It doesn't understands any passwords - mine, root and a > > couple of accounts. > > What happens if you 'boot: -s' and then vipw, write/quit, reboot. Don't > make any changes to master.passwd, just rebuild the database. It's > happened here a couple times. It doesn't worked, relinking libcrypt* helps. ;) Adios, /KONG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 10:04:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17170 for freebsd-current-outgoing; Fri, 29 May 1998 10:04:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.175.134.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17161 for ; Fri, 29 May 1998 10:04:48 -0700 (PDT) (envelope-from schilling@fokus.gmd.de) Received: from sherwood.gmd.de (sherwood [193.175.133.102]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id TAA21109; Fri, 29 May 1998 19:03:43 +0200 (MET DST) Received: (from jes@localhost) by sherwood.gmd.de (8.8.8+Sun/8.8.8) id TAA14897; Fri, 29 May 1998 19:03:23 +0200 (MET DST) Date: Fri, 29 May 1998 19:03:23 +0200 (MET DST) From: Joerg Schilling Message-Id: <199805291703.TAA14897@sherwood.gmd.de> To: mike@smith.net.au, schilling@fokus.gmd.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From mike@antipodes.cdrom.com Fri May 29 18:26:05 1998 >> First some notes. You are discussing things related to cdrecord. >> If you like to see your effort back in the main stream cdrecord, this >> is definitely the wring mailing list. >It's a good place to deal with the specifics of making cdrecord work on = >FreeBSD though. It's certainly unlikely that Peter would have been = I see that this should be discussed on the FreeBSD list too, but if you like to get help from me, you could not get it from freebsd-current, I am not subscribed. >The FreeBSD Posix implementation is still under development, and the = >scheduler module is an optional addition (as allowed for under the = >spec.). Cdrecord doesn't make the required runtime check for the = >presence of the desired functionality. OK, but this is a new issue. It never has been nessecary before. If other operating systems will start to behave similar, it would make autoconfiguration a lot more complex. >> >> > Bus error (core dumped) >> = >> If you are not able to analyze the core with adb and send a usable >> bug description, I cannot help.. >The bus error is (in my case at any rate) due to a buffer overrun = >elsewhere. I haven't been able to ascertain the cause of this yet, but = >there are indications that winding back the visible Posix interface = >resolves the issue. I am interested to find the reason for this core dump as it should not happen. Some versions of HP-UX have the definition for POSIX RR and do not implement it. On such HP_UX versions you usually get a warning about the non existence of RR scheduling and cdrecord then uses nice(2). I even may remove the warning if I an sure that no-one cares about the non existing RR class. I am testing cdrecord on all systems I can get hold of in a way that allows testing to me (root access). As the SCSI implementations usually are not sufficient, development and testing is mainly done on Solaris. >We're not talking about "rubbish". We're talking about an >in-development implementation of the Posix environment. OK, I understand. BTW: I would be happy if the user interface of the new SCSI user transport calls would be easier to access and to understand. In other words: I like to have the device files be present by default so that programs like cdrecord onlu have to open the right file to get access to the device. >> On SVr4 systems the _POSIX_PRIORITY_SCHEDULING is definitely worse >> than the RT priocntl() interface and proicntl with RR scheduling is eve= >n >> available since the early days of SVr4. I cannot change the source in a= > way >> that only makes sure that nothing works after the change. >This sounds like "rubbish" in SysV. I I would not call this rubbish, it is available since 1988/1989 - years before POSIX realtime enhanceements have beendefined and it grants you to be able to run a process at a higher priority than you pager. >> The scg drvier which I wrote in 1986 is based on this interface and >> itself is the base for my portable SCSI user-level command transport >> system. It should be faily easy to make a CAM adoption layer for scg. >It was. The real problems with scg have to do with the lack of visible >documentation. It is unclear how to do any sort of meaningful error >handling, or whether this should be managed at a lower level. Again, >this is an issue I was postponing until I had established that >everything else was going to behave and the interface had stabilised. OK, here is what I send to Sun some weeks ago: If you like to do a quick hack: - scsi_open() is currenltly not able to use anything but busno,target,lun You would get into trouble if you like to open /dev/rdsk/* - The interface funkctions are (currently): scsi_open() prepare a handle for later use with scsi_send() scsi_maxdma() return the max. amount of contiguous DMA on the current architecture scsi_getbuf(amt) allocate a (currently global - later open-specific) buffer of size 'amt' but not grater than scsi_maxdma() scsi_havebuf(busno) return TRUE/FALSE on whether the current machine includes a SCSI bus 'busno' scsi_fileno(bus, tgt, lun) return a filedescriptor to be used for the SCSI send ioctl. The filedesscriptor mus be the right one for bus/tgt/lun scsieset() as it says, need not to be implemented. scsi_send(f, struct scg_cmd *) Simulate the scg SCSI send command ioctl. returns: -1 usage error(e.g. EINVAL ....) 0 All other see scgio.h for a description of the fields in the struct. cmd->resid is set to the DMA residual count cmd-error is set to one of: SCG_NO_ERROR SCSI transport without error this is true for most failed commands too !!!! SCG_FATAL could not select target SCG_TIMEOUT a SCSI timeout occured SCG_RETRYABLE any other case cmd->ux_errno is set to the UNIX errno for a failed command (note: parameter error are covered above) cmd->scb is set to the SCSI Status byte for the command note there is currently no sense status cmd->sense must be filled with auto-sense data if the comand fails. cmd->sense_count must be set to the # of valid sense bytes /*--------------------------------------------------------------------------*/ I decided to make the SCSI ABI testuite available before I start to create a separate SCSI library. Jörg EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) If you don't have iso-8859-1 schilling@fokus.gmd.de (work) chars I am J"org Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 10:09:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17861 for freebsd-current-outgoing; Fri, 29 May 1998 10:09:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17850 for ; Fri, 29 May 1998 10:09:03 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-65.camalott.com [208.229.74.65] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id MAA30928; Fri, 29 May 1998 12:07:41 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id MAA27037; Fri, 29 May 1998 12:08:36 -0500 (CDT) (envelope-from joelh) Date: Fri, 29 May 1998 12:08:36 -0500 (CDT) Message-Id: <199805291708.MAA27037@detlev.UUCP> To: richard.cownie@axil.com CC: hasty@rah.star-gate.com, richard.cownie@axil.com, current@FreeBSD.ORG In-reply-to: (message from Richard Cownie on Fri, 29 May 1998 11:59:19 -0400) Subject: Re: FreeBSD on 8-way SMP PPro From: Joel Ray Holveck Reply-to: joelh@gnu.org References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> 4 PCI buses, 7 NCR 53c875 scsi, up to 8GB DRAM and 24*9GB disk, >> What was the maximum amount of memory that you tested? > I only have 256K of DRAM so far - I could borrow a board with 4GB, > but it probably wouldn't be interesting until I have a good way of > stressing the system (maybe "make -j32 world") ? Tell me I'm misreading this... I haven't had a system with 256k DRAM in over a decade. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 10:11:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18229 for freebsd-current-outgoing; Fri, 29 May 1998 10:11:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18221 for ; Fri, 29 May 1998 10:11:33 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id KAA20783; Fri, 29 May 1998 10:11:31 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd020594; Fri May 29 10:11:18 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id KAA27106; Fri, 29 May 1998 10:11:15 -0700 (MST) From: Terry Lambert Message-Id: <199805291711.KAA27106@usr08.primenet.com> Subject: Re: TenDRA compiler To: nate@mt.sri.com (Nate Williams) Date: Fri, 29 May 1998 17:11:14 +0000 (GMT) Cc: eivind@yes.no, nate@mt.sri.com, current@FreeBSD.ORG In-Reply-To: <199805261840.MAA07456@mt.sri.com> from "Nate Williams" at May 26, 98 12:40:15 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > > > be much better than GCC when you look at error control etc. > > > > > > Can it do shlibs? > > > > I don't know - is there much special it would have to do? > > Generating PIC code is a big prerequisite, so the assembly it generates > must be capable of being relocated. I'm not 100% sure if this is a > function of the compiler, but given that GCC1 couldn't do it and GCC2 > could, I suspect it's a function of the compiler. Someone should talk to Jeffrey Hsu, since he's the guy who did the original GCC PIC modifications (back when I was first working on LKM's and BSD style shared libraries in early 1994(?)). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 10:12:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18402 for freebsd-current-outgoing; Fri, 29 May 1998 10:12:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dragon.axil.com (dragon.axil.com [206.33.98.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18368 for ; Fri, 29 May 1998 10:12:31 -0700 (PDT) (envelope-from richard.cownie@axil.com) Received: by dragon.axil.com with Internet Mail Service (5.0.1458.49) id ; Fri, 29 May 1998 13:12:06 -0400 Message-ID: From: Richard Cownie To: joelh@gnu.org, richard.cownie@axil.com Cc: hasty@rah.star-gate.com, current@FreeBSD.ORG Subject: RE: FreeBSD on 8-way SMP PPro Date: Fri, 29 May 1998 13:11:57 -0400 X-Priority: 3 X-Mailer: Internet Mail Service (5.0.1458.49) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My apologies, I meant 256M > -----Original Message----- > From: Joel Ray Holveck [SMTP:joelh@gnu.org] > Sent: Friday, May 29, 1998 1:09 PM > To: richard.cownie@axil.com > Cc: hasty@rah.star-gate.com; richard.cownie@axil.com; > current@FreeBSD.ORG > Subject: Re: FreeBSD on 8-way SMP PPro > > >>> 4 PCI buses, 7 NCR 53c875 scsi, up to 8GB DRAM and 24*9GB disk, > >> What was the maximum amount of memory that you tested? > > I only have 256K of DRAM so far - I could borrow a board with 4GB, > > but it probably wouldn't be interesting until I have a good way of > > stressing the system (maybe "make -j32 world") ? > > Tell me I'm misreading this... I haven't had a system with 256k DRAM > in over a decade. > > Happy hacking, > joelh > > -- > Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 10:20:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19657 for freebsd-current-outgoing; Fri, 29 May 1998 10:20:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.175.134.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19648 for ; Fri, 29 May 1998 10:20:44 -0700 (PDT) (envelope-from schilling@fokus.gmd.de) Received: from sherwood.gmd.de (sherwood [193.175.133.102]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id TAA21518; Fri, 29 May 1998 19:20:34 +0200 (MET DST) Received: (from jes@localhost) by sherwood.gmd.de (8.8.8+Sun/8.8.8) id TAA15036; Fri, 29 May 1998 19:20:10 +0200 (MET DST) Date: Fri, 29 May 1998 19:20:10 +0200 (MET DST) From: Joerg Schilling Message-Id: <199805291720.TAA15036@sherwood.gmd.de> To: mike@smith.net.au, schilling@fokus.gmd.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet / SCSI ABI test Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The scg drvier which I wrote in 1986 is based on this interface and >> itself is the base for my portable SCSI user-level command transport >> system. It should be faily easy to make a CAM adoption layer for scg. >It was. The real problems with scg have to do with the lack of visible >documentation. It is unclear how to do any sort of meaningful error >handling, or whether this should be managed at a lower level. Again, >this is an issue I was postponing until I had established that >everything else was going to behave and the interface had stabilised. The main problem with this documentation is that a hacker who wants to contribute code must have thorough knowledge on the SCSI protocol to understand what to do from reading simply a API doc. For this reason, I prefer to have some ABI checker software. The main problem with this checker software is that I must be able to create certain error situations like: - drive not selectable - timeout - SCSI status code on error - correct sense data content - correct sense data length - return code of scsisend() - check for working DMA residual count .... I am tending to do the necessarily tests with CD-ROM drive as most people seem to have one. But for timeout tests not every CD-ROM drive is usable because the only idea I currently have to force a SCSI timeout is to do one very big SCSi-VERIFY on a disk with > 400MB data on it. This is because not all timeout implementations catch timeouts fast (< 1 minute). Jörg EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) If you don't have iso-8859-1 schilling@fokus.gmd.de (work) chars I am J"org Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 10:31:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20890 for freebsd-current-outgoing; Fri, 29 May 1998 10:31:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dragon.axil.com (dragon.axil.com [206.33.98.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20879 for ; Fri, 29 May 1998 10:31:18 -0700 (PDT) (envelope-from richard.cownie@axil.com) Received: by dragon.axil.com with Internet Mail Service (5.0.1458.49) id ; Fri, 29 May 1998 13:30:51 -0400 Message-ID: From: Richard Cownie To: Mike Smith , Richard Cownie Cc: jak@cetlink.net, current@FreeBSD.ORG Subject: RE: FreeBSD on 8-way SMP PPro Date: Fri, 29 May 1998 13:30:49 -0400 X-Priority: 3 X-Mailer: Internet Mail Service (5.0.1458.49) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, I probably have to tread carefully here and repeat my disclaimer that these are my personal views rather than Axil corporate policy. 1) Axil's main focus is building and selling high-end NT servers. As you'll see from the website http://www.axil.com, all our marketing is focused on NT 2) In the design of the hardware and Bios, we have adhered closely to the Intel MPS spec and other standards - so *in theory* any and all well-behaved OS's should work. However, as a relatively small company we don't have enough technical people to do extensive testing or active support of many different OS's. Ans as you know, if you haven't tested it, it doesn't work (usually). 3)Unixware on NX801 definitely does work, and several customers are running this. So there is a precedent for selling non-NT systems. If anyone wanted to buy a box to run any other OS (FreeBSD, Linux, DOS :-), then we'll probably sell the box, while making it clear that Axil won't provide support for the OS. 4) Until recently Axil also built SPARC boxes, and much of our internal development enviornment is still based on SPARC/Solaris/NFS; so we don't have any ideological objections to Unix. So I think it's probably ok to say "some guy at Axil has FreeBSD running", which is nothing more or less than the strict truth,as long as you don't raise any expectation that corporate Axil is putting big resources into this. Cheers Richard Cownie [] [] From: Mike Smith [SMTP:mike@smith.net.au] > Sent: Friday, May 29, 1998 11:01 AM > To: Richard Cownie > Cc: Mike Smith; jak@cetlink.net; current@FreeBSD.ORG > Subject: Re: FreeBSD on 8-way SMP PPro > > Do Axil have an opinion at all about non-NT operating systems and > their > hardware? There's quite a lot of "wow" power in saying to someone > "this > guy at Axil has FreeBSD running on one of *these* (points to > picture)", > and it really does lend some serious credibility to the project. > However, it's not the sort of thing that you want to do if Axil > corporate have a dim view of other operating systems, so I'd prefer to > be a little careful about it. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 10:56:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25964 for freebsd-current-outgoing; Fri, 29 May 1998 10:56:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (root@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25871 for ; Fri, 29 May 1998 10:56:03 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id KAA17753; Fri, 29 May 1998 10:07:35 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp03.primenet.com, id smtpd012826; Fri May 29 09:58:52 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id JAA26569; Fri, 29 May 1998 09:58:49 -0700 (MST) From: Terry Lambert Message-Id: <199805291658.JAA26569@usr08.primenet.com> Subject: Re: buildworld from read-only filesystem To: eivind@yes.no (Eivind Eklund) Date: Fri, 29 May 1998 16:58:48 +0000 (GMT) Cc: syssgm@dtir.qld.gov.au, freebsd-current@FreeBSD.ORG In-Reply-To: <19980525153245.29293@follo.net> from "Eivind Eklund" at May 25, 98 03:32:45 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just had many people complain that 'buildworld' from a RO FS > didn't work, with the last being Terry Lambert a few weeks ago. I don't think so... I haven't tried to do this in quite a while, so have had no reason to complain. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 11:13:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29208 for freebsd-current-outgoing; Fri, 29 May 1998 11:13:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA29186 for ; Fri, 29 May 1998 11:13:21 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 417 invoked by uid 1000); 29 May 1998 19:14:42 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FABC@freya.circle.net> Date: Fri, 29 May 1998 15:14:42 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: tcobb Subject: RE: DPT driver fails and panics with Degraded Array Cc: "simon@simon-shapiro.org" , "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-May-98 tcobb wrote: > I have a DPT3344UW/2 running an external 24GB array. OS is FreeBSD > CURRENT circa 5/18/98. I'm running the latest available firmware flash > for the card, all on a P5-233MMX with 128MB RAM. What version is ``latest''? I have several ``latest'' here. > Recently I lost a harddrive in my 24GB RAID5 array. The array was > configured with a HOT SPARE which should have allowed it to rebuild > completely online, with no interruption in service (except some minor > slowdowns, perhaps). While the HARDWARE worked well, the DPT DRIVER > failed miserably. the DPT driver HAS NOTHING TO DO with the RAID array. It is seen strinctly as a disk. > When my array went into degraded mode, the DPT DRIVER froze access to > the partitions. Upon reboot, during device probe, the DPT DRIVER > returned a 1 SECTOR (0 MB) sense for the array, despite the fact that > the array was operating properly (though degraded). After this, the > kernel panic'd before completing the boot process with a "Page Fault in > Supervisor Mode" error, and continued to panic this way until the DPT > Array was COMPLETELY REBUILT OFFLINE (requiring me to boot into DOS and > do it - doing the rebuild of that size RAID5 array takes more than an > hour). After a complete rebuild, the DPT DRIVER showed the array sizes > correctly. This is strange. I routinely (although rarely coluntarily) run into degraded mode. The size reported by the DPT driver, is the size rerported to the driver by the DPT firmware. If it shows as ZERO, it is either ZERO, or the array is more than degraded (dead). > During this process, booting into DOS revealed the array to be fine, > even while the array was degraded -- it also wasn't confused by degraded > mode and showed correct partition information. So, was it fine, or was it degraded? > I believe that the DPT DRIVER is not correctly sensing that the array is > okay, even though it is in degraded mode, and incorrectly returns > sector/MB values which panic the kernel. I don't recommend depending on > the proper operation of this driver for your High-Availability needs. I beg to differ. The DPT driver does not do any sensing at all. The SCSI layer calls for SENSE commands. The DPT driver is simply a protocol translator. I do not even look at the commands, nor their results/contents. Extending your recommendation, I'll repeat what was said here endlessly; Do NOT use 3.0-CURRENT for any mission critical software. Extending it further, do no use any computer software for mission critical under any conditions. All systems fail, except those with the power off. > HISTORY > I've used DPT in FreeBSD since last November, first with the hacked > 2.2.2 driver. I upgraded to 2.2.6 to fix a MBUF leak that was crashing > me about once per week. As 2.2.6, the MBUF leak disappeared and was > replaced with a once every 2-3 day panic which it appeared was not going > to get fixed by anyone (bidone: buffer not busy). So, I bit the bullet > and upgraded recently to 3.0, which seemed to fix both of these prior > panics only to reveal that the supposedly "high availability" software > driver for my HA hardware is miserable during the most critical times. It may help, in the future, if you contact me for help. >From your description, you have a marginal disk subsystem. Either bad cabling, bad power, bad controller. None of your symptoms is relevant to the DPT driver. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 11:20:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01060 for freebsd-current-outgoing; Fri, 29 May 1998 11:20:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA00849 for ; Fri, 29 May 1998 11:19:56 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 492 invoked by uid 1000); 29 May 1998 19:21:17 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 29 May 1998 15:21:17 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Michael Hancock Subject: Re: DPT driver fails and panics with Degraded Array Cc: "freebsd-current@freebsd.org" , tcobb , Karl Pielorz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-May-98 Michael Hancock wrote: > On Fri, 29 May 1998, Karl Pielorz wrote: > >> One comment (and it's not a flame!) - honestly... ;-) >> >> With an array of that size, on a machine that important - did you not >> test >> to see what would happen with a failed drive? >> > > I recently got a DPT too for a production system but my needs were not as > critical. I use a SYM53C875 for the system disk and the DPT with 2 > mirrored drives for data. I can do some experimentation during off hours > with this system. > > I would like to see the DPT stabilize such that large arrays could be > used > reliably so I'll try and test patches against 2.2.6, after I work out a > budget to get more drives. I am routinely running a Dual DPT with 38 drives on 6 busses. On 3.0-CURRENT SMP. The system did lose disk drives, either intentionally, or by accident. I cannot confirm any of Mr. Cobb's finding. I have not been funished with any data, including the panic point, which I suspect is not in the DPT code. I am still waiting for such data. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 11:44:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07666 for freebsd-current-outgoing; Fri, 29 May 1998 11:44:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk ([195.8.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07615 for ; Fri, 29 May 1998 11:44:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id UAA00401; Fri, 29 May 1998 20:42:25 +0200 (CEST) To: Cory Kempf cc: freebsd-current@FreeBSD.ORG Subject: Re: MD5 v. DES? In-reply-to: Your message of "29 May 1998 10:52:00 EDT." Date: Fri, 29 May 1998 20:42:24 +0200 Message-ID: <399.896467344@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Cory Kempf writes: >dag-erli@ifi.uio.no (Dag-Erling Coidan Smørgrav ) writes: >>Hostas Red writes: >>Search for "MD5" in the freebsd-current archive. What has happened is >>that your system has mistakenly switched to using MD5 passwords >>instead of DES passwords. This problem was identified (and solved?) a >>few days ago. > >Is there a discussion somewhere about the merits of MD5 v. DES? >E.g. what advantages one has over the other? MD5 is more resilient against dictionary based brute force cracking attempts. MD5 can be exported. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 11:46:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08307 for freebsd-current-outgoing; Fri, 29 May 1998 11:46:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (root@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08284 for ; Fri, 29 May 1998 11:46:43 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id LAA00162; Fri, 29 May 1998 11:14:27 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd021685; Fri May 29 10:47:11 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id KAA28662; Fri, 29 May 1998 10:47:04 -0700 (MST) From: Terry Lambert Message-Id: <199805291747.KAA28662@usr08.primenet.com> Subject: Re: ELF Step 2 To: bde@zeta.org.au (Bruce Evans) Date: Fri, 29 May 1998 17:47:04 +0000 (GMT) Cc: current@FreeBSD.ORG, pierre.dampure@k2c.co.uk In-Reply-To: <199805271111.VAA17050@godzilla.zeta.org.au> from "Bruce Evans" at May 27, 98 09:11:41 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /usr/src/Makefile has the md5 libcrypt hard-coded in one place. I'm > not sure why it doesn't get replaced by the correct ${_libcrypt} later. > NOCLEAN? The wrong version should only be used to build perl. Why should the wrong version be used to build perl? Is it so perl can be wrong? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 12:15:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15491 for freebsd-current-outgoing; Fri, 29 May 1998 12:15:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA15421 for ; Fri, 29 May 1998 12:14:58 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1256 invoked by uid 1000); 29 May 1998 20:16:18 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAC3@freya.circle.net> Date: Fri, 29 May 1998 16:16:18 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: tcobb Subject: RE: DPT driver fails and panics with Degraded Array Cc: "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" , Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-May-98 tcobb wrote: ... > My problem report (most of which you snipped) pointed out a deficiency > in the DPT driver code which renders it useless in HA applications. I > believe that this deficiency is likely to be present in ALL VERSIONS of > this code, unless suddenly, people are putting the newest code in the > oldest versions of the OS. We all trust that you use FreeBSD 3.0-current and a DPT controller in said system. What you have failed to demonstrate is that the FreeBSD DRIVER is at fault. I am very anxious to discover and repair ANY bug in this driver as many people use this setup for mission critical work. Since I read the driver code few times and am somewhat familiar with it, I cannot find support to your claim that the failure you report (and we trust there is a failure) is induced in the driver. I am very interested in helping you solve your problem, but going into the driver and tearing up the code, searching for unknown and unlikely breakage is not an efficient use of my time and will most likely not advance our common goal of getting your system up and running and the problem eradicated. As you can observe elsewhere, a FreeBSD SCSI HBA driver in general (and the DPT driver in particular) is not involving itself with the contents of the SCSI commands passed to it from the kernel. Nor does it concern itself with the results of these commands. In the FreeBSD driver, similar to other DPT drivers (but not identical), I perfrom certain checks with the DPT hardware. These happen at boot time, BEFORE any of the kernel boot prompts you see. None of these has anything to do with what devices are attached to the bus, but strictly with the controller; Who are you? How are you doing?, etc. But never anything to do with attached devices. Reporting an array size zero (or one) is most likely caused by the array being DEAD, not degraded. Have you run the dptmgr verify function against the entire array? DOS does not perform much analysis and can be misleading. Unless you explicitly instruct the DPTMGR software to access data on a disk (or array), only the first sector is being accessed. Thus, it is entirely possible that the array is inaccessible beyond one sector, if that. Your symptoms can be caused by many causes, all of them within the realm of DPT hardware and attached devices. I really do not know the purpose of your messages on this subject. You really have not asked for help fixing the problem. Neither did you offer any diagnistics data to me, or the group as a whole. If your purpose is to create an acusation, it is well written, with the minor flow of it being inaccurate and quite wrong in its conclusion. If your purpose is to solve the problem, please send me the following (with a copy to the group, if you care) a. Exact Configuration; What CPU, what memory, DPT card model, type of cache memory, amount of cache, exact firmware version, exact BIOS version (NOT the same thing!) What disks are in which array, etc. I'll also need to know how the disks are programmed into the array, their bus and target IDs, etc. I need this information from both the hardware configuration and the logical view screens. b. Exact Setup; These disks, what brand and model? What firmware version on each disk? How are these disks mounted and in what? The type of cables you use, the type of terminators you use, etc. c. Is the system bootable now? Is it on the net? Can I have a root login on it for a while? d. Are you going to be available to run dptmgr for me and be my eyes and fingers, while in DOS or SU mode? e. Have you run all the DPT diagnostics to assure that the arrays are really healthy and accessible? Have you wiggled the wires to every device, while the tests are running? Have you printed out the DPT error log for the controller (from DPTMGR)? Have you run the statistics, to see the error counts and rates? Please provide me with this data, so I can try and help you. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 12:20:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16705 for freebsd-current-outgoing; Fri, 29 May 1998 12:20:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16700 for ; Fri, 29 May 1998 12:20:35 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id UAA26575 for ; Fri, 29 May 1998 20:22:31 +0100 (BST) Date: Fri, 29 May 1998 20:22:31 +0100 (BST) From: Doug Rabson To: current@FreeBSD.ORG Subject: FreeBSD/alpha status report (2) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I reached a significant milestone today. I exec'ed '/sbin/init' (binary from NetBSD) and it successfully managed a few syscalls and even a page fault or two before it choked deep inside __sysctl. It won't be long before I get a single-user shell working. Along the way, I have successfully probed for simulated devices on a simulated PCI bus and attached simulated SCSI disks :-). I am *not* currently using NetBSD's bus_space stuff to handle accesses to device i/o ports and memory. Given that 99% of the machines that the port will work on don't need the complexity of bus_space, I have taken the Linux route and each chipset will supply versions of inb etc which perform the relavent contortions. Next week, I will probably commit some of this code. I have made a lot of 64bit fixes to generic kernel code which I need to test on i386. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 12:24:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17294 for freebsd-current-outgoing; Fri, 29 May 1998 12:24:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA17265 for ; Fri, 29 May 1998 12:24:39 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1323 invoked by uid 1000); 29 May 1998 20:26:01 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAC7@freya.circle.net> Date: Fri, 29 May 1998 16:26:01 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: tcobb Subject: RE: DPT driver fails and panics with Degraded Array Cc: "freebsd-current@freebsd.org" , Mike Smith , Greg Lehey Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-May-98 tcobb wrote: ... > Indeed. And that was the point of sending to freebsd-current. I wanted > anyone using the DPT driver and expecting it to perform appropriately in > critical circumstances to know that it will not do so. I perhaps should > have sent the email to -hackers instead? Or, maybe -scsi, like I did -- > it is a scsi driver problem I'm talking about. I am steadily losing patience here :-( You have NOT provided me with any information indicating that the driver is at fault. My understanding of the DPT subsystem and of the driver for FreeBSD indicate it is NOT a driver fault. Before jumping into a conclusion as to what caused the problem, you shuld have at least sent me a note about it. Your desire to ``warn others'' is suspect. Not only is is suspect, but it may deter others from using FreeBSD and/or the DPT drivers for no good reason. ... > I agree. I wouldn't have done so without provocation. My counterpoint > is that FreeBSD-STABLE is NOT stable, either. Regardless, due to > show-stopper bugs in -stable... Again, you have yet to demonstrate any bug in any software here. > My choices were: > > 1. Discard FreeBSD completely for this server. > 2. Switch to a -current snapshot. > > I didn't want to do #1, so I spent two weeks rolling a -current snapshot > release for my in-house use, I tested it, and tested it. It works well. > > My posting was really to point to the fact that it appears that the DPT > driver is deficient across ALL releases, not just -current. Yet again, what exactly supports this opinion? Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 12:26:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17511 for freebsd-current-outgoing; Fri, 29 May 1998 12:26:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA17462 for ; Fri, 29 May 1998 12:25:53 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1333 invoked by uid 1000); 29 May 1998 20:27:09 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199805290518.WAA00425@antipodes.cdrom.com> Date: Fri, 29 May 1998 16:27:09 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mike Smith Subject: Re: DPT driver fails and panics with Degraded Array Cc: "freebsd-current@freebsd.org" , tcobb Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-May-98 Mike Smith wrote: >> >> Indeed. And that was the point of sending to freebsd-current. I wanted >> anyone using the DPT driver and expecting it to perform appropriately in >> critical circumstances to know that it will not do so. I perhaps should >> have sent the email to -hackers instead? Or, maybe -scsi, like I did -- >> it is a scsi driver problem I'm talking about. > > The heads-up was fine. Some indication that you were working with the > author to resolve the issue would have been somewhat more encouraging, > or at least that you had discussed the matter with same. Wrong, Mike. I have not heard anything from him at all. Not as of this moment :-( Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 12:30:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18224 for freebsd-current-outgoing; Fri, 29 May 1998 12:30:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA18193 for ; Fri, 29 May 1998 12:30:38 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1364 invoked by uid 1000); 29 May 1998 20:32:00 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FACA@freya.circle.net> Date: Fri, 29 May 1998 16:32:00 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: tcobb Subject: RE: DPT driver fails and panics with Degraded Array Cc: "freebsd-current@freebsd.org" , Mike Smith , Greg Lehey , Julian Elischer Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-May-98 tcobb wrote: >> I guess this is really something you want to discuss with simon. >> I'm sure he will contact you soon >> He's just finished moving houes and has been out-of-touch fro >> a few weeks >> >> julian > > Yes. > > I am going to contact DPT tomorrow about obtaining the NDA-bound specs > for the board. We have some development talent in-house to commit to > stabilizing this driver. > > Our choices are either: > a) wait for Simon to stabilize the driver > b) try to stabilize the driver ourselves, release code back to FreeBSD > c) scrap FreeBSD on this HA server (Solaris,Linux,NT all have native > support for DPT) > d) scrap DPT and use a SCSI-to-SCSI based RAID solution > > Given our current committment to DPT and FreeBSD so far, I'd prefer a or > b above. > > I'm not confident of a) happening quickly, as Simon appears to be either > busy with other projects or relatively unavailable. Nonsense! You have not contacted me. Your earliest posting was dated yesterday. You continue to voice opinions and provide no data. If I tried to aggrqavate someone purposely, I would hardly find a better way. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 12:40:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20256 for freebsd-current-outgoing; Fri, 29 May 1998 12:40:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20224; Fri, 29 May 1998 12:40:15 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id PAA03125; Fri, 29 May 1998 15:40:12 -0400 (EDT) Date: Fri, 29 May 1998 15:40:12 -0400 (EDT) From: The Hermit Hacker To: freebsd-scsi@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: May20th CAM drivers with today's (May29th) sources ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having a panic problems on my server, and want to upgrade, but am using CAM...does anyone know of any problems with using May20th drivers with May29th sources? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 12:44:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21290 for freebsd-current-outgoing; Fri, 29 May 1998 12:44:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (daemon@smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21217 for ; Fri, 29 May 1998 12:43:51 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id MAA09349; Fri, 29 May 1998 12:43:24 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp03.primenet.com, id smtpd009285; Fri May 29 12:43:20 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id MAA29478; Fri, 29 May 1998 12:43:07 -0700 (MST) From: Terry Lambert Message-Id: <199805291943.MAA29478@usr07.primenet.com> Subject: Re: TenDRA... To: eivind@yes.no (Eivind Eklund) Date: Fri, 29 May 1998 19:43:07 +0000 (GMT) Cc: mike@smith.net.au, toor@dyson.iquest.net, current@FreeBSD.ORG In-Reply-To: <19980528004714.19214@follo.net> from "Eivind Eklund" at May 28, 98 00:47:14 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Personally I'd prefer to use TenDRA if at all possible. It seems to > > > be much better than GCC when you look at error control etc. > > > > How much of the world will build with it? > > Too little at the moment, I'd guess - but I don't know. I'm trying to > find out if getting the kernel compiled is possible first. That's > what's been the hurdle for compiling other Unixen with TenDRA. This may be of interest: http://www.gr.opengroup.org/andf/tendra.htm Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 12:48:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22781 for freebsd-current-outgoing; Fri, 29 May 1998 12:48:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA22762 for ; Fri, 29 May 1998 12:48:37 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1563 invoked by uid 1000); 29 May 1998 20:49:56 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FACD@freya.circle.net> Date: Fri, 29 May 1998 16:49:56 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: tcobb Subject: RE: DPT driver fails and panics with Degraded Array Cc: "freebsd-current@freebsd.org" , Karl Pielorz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-May-98 tcobb wrote: [ To the rest of the crowd : Is it OK for me NOT to help this guy? :-(( ] > Despite pre-certification testing, something will be different when you > have a failure in production. The difference in our case, I'm guessing, > was that the array is now 60-75% full, and the OS version is different, > and the system was under heavy access load, too. The original driver > was an over-hacked version stuffed into 2.2.2, the newest driver IS > better integrated, and actually faster, but obviously unable to handle > the under-load failure situation in exactly the way we had it happen. Your comments demonstrate ignorance in addition to lack of manners. I wrote this driver, every line of it, with help from others, but I wrote it. As such, it may help you realize that it was actually written on 2.2-CURRENT, migrated to 2.2-BETA, 2.2-STABle, and finally to 3.0-CURRENT. Anyone who has written a FreeBSD (or virtually any Unix) SCSI HBA driver knows that the initial size reporting is a BIOS or firmware reply to a call from the kernel SCSI layer, not the HBA driver. How full is the disk has nothing to do with what the controller firmware reports to the kernel as to the configuration. Before releasing a driver, my procedure is as follows: a. Create a 26GB partition b. Spawn 256 processes, each doing random read/write operation on a 2GB area of the 26GB partition. At this point, the load on the system will reach 140-400 (we run the tests against RAID-0 and RAID-1, the performance differs) c. NFS-mount a large partition from another system, also running DPT and RAID arrays. d. Spawn 16-64 processes, each doing: find /NFS | cpio -H newc -ov -O /dev/null At this point LA will climb to 800-900. We run this test for 24 hours on UP, then 24 hours on SMP We then do make release, cut a CD, scrap the test machines and install from the CD. One test machine installs to an IDE drive, and uses the DPT array for some of the filesystems. The other system boots off the DPT. We then repeat the test above. Following that, I install the driver on my various on-line machines. About a week later, the code is released to a FreeBSD committer for inclusion in FreeBSD. If you snatch a patch from my ftp server, it may vary from useless to excellent. No way to tell by looking at it. These patches are not solicited to anyone, but any legitimate user, intending to use the code in a legal an moral way is welcome to it. So your statement about over-hacked back port is abusive rude and patently not the truth. As I said, I am using the DPT drivers in a production environment and so are many others. I am very anxious to help any FreeBSD user fix any problem I can help with, be it DPT related or otherwise. Being abused is outside the scope of what I consider helping others. Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 12:51:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23456 for freebsd-current-outgoing; Fri, 29 May 1998 12:51:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA23388 for ; Fri, 29 May 1998 12:51:31 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 1584 invoked by uid 1000); 29 May 1998 20:52:49 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <509A2986E5C5D111B7DD0060082F32A402FAD1@freya.circle.net> Date: Fri, 29 May 1998 16:52:49 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: tcobb Subject: RE: DPT driver fails and panics with Degraded Array Cc: "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" , Eivind Eklund Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-May-98 tcobb wrote: >> (1) I've had my array (a 2GB RAID1 - personal RAID :-) run in degraded >> mode. This has worked just fine with the driver in -current, with >> the RAID full (of partitions, not data. I can't understand that >> the amount of data should make a difference - the controller >> shouldn't know about this anyway). > > Perhaps the difference is RAID-1 versus RAID-5. What has that got to do with the over-hacked driver, again? Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 13:19:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29199 for freebsd-current-outgoing; Fri, 29 May 1998 13:19:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29186 for ; Fri, 29 May 1998 13:19:43 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00482; Fri, 29 May 1998 12:13:13 -0700 (PDT) Message-Id: <199805291913.MAA00482@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Peter Dufault cc: bde@zeta.org.au (Bruce Evans), mike@smith.net.au, current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet In-reply-to: Your message of "Fri, 29 May 1998 07:09:30 EDT." <199805291109.HAA23356@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 12:13:12 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > if (sysconf(_SC_PRIORITY_SCHEDULING) == -1) { > > > if (errno != 0) { > > > /* This isn't valid: > > > */ > > (...) > > > The "This isn't valid" case isn't valid, since sysconf() doesn't change > > errno if there is no error. errno must be set before calling sysconf(). > > I needed to cut a few more lines: > > > /* Is priority scheduling configured? > > */ > > errno = 0; > > if (sysconf(_SC_PRIORITY_SCHEDULING) == -1) { > > Remember: Bruce is watching. Measure twice, cut once. 8) Thanks again. In reality, I can just check the return from sysconf; if _SC_PRIORITY_SCHEDULING can't be queried, then it's not a goer anyway. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 13:21:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29797 for freebsd-current-outgoing; Fri, 29 May 1998 13:21:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29784 for ; Fri, 29 May 1998 13:21:46 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00509; Fri, 29 May 1998 12:15:53 -0700 (PDT) Message-Id: <199805291915.MAA00509@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Joerg Schilling cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet / SCSI ABI test In-reply-to: Your message of "Fri, 29 May 1998 19:20:10 +0200." <199805291720.TAA15036@sherwood.gmd.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 29 May 1998 12:15:53 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA29787 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> The scg drvier which I wrote in 1986 is based on this interface and > >> itself is the base for my portable SCSI user-level command transport > >> system. It should be faily easy to make a CAM adoption layer for scg. > > >It was. The real problems with scg have to do with the lack of visible > >documentation. It is unclear how to do any sort of meaningful error > >handling, or whether this should be managed at a lower level. Again, > >this is an issue I was postponing until I had established that > >everything else was going to behave and the interface had stabilised. > > The main problem with this documentation is that a hacker who wants to > contribute code must have thorough knowledge on the SCSI protocol to > understand what to do from reading simply a API doc. Actually, they shouldn't. Your scg stack passes SCSI commands down, and expects them to be handled according to a set of rules. The interface shim has to provide a translation between those rules and the rules that the host system advertises. > For this reason, I prefer to have some ABI checker software. Alan Turing. > But for timeout tests not every CD-ROM drive is usable because the only > idea I currently have to force a SCSI timeout is to do one very big > SCSi-VERIFY on a disk with > 400MB data on it. This is because not all > timeout implementations catch timeouts fast (< 1 minute). Build a small board containing a 5380 and a microcontroller. Write some minimal SCSI target software, and put a console on it. You could probably sell 5-10 of these to SCSI driver authors. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 13:42:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06012 for freebsd-current-outgoing; Fri, 29 May 1998 13:42:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05957 for ; Fri, 29 May 1998 13:42:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00596; Fri, 29 May 1998 12:36:46 -0700 (PDT) Message-Id: <199805291936.MAA00596@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Joerg Schilling cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet In-reply-to: Your message of "Fri, 29 May 1998 19:03:23 +0200." <199805291703.TAA14897@sherwood.gmd.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 29 May 1998 12:36:46 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA05971 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >From mike@antipodes.cdrom.com Fri May 29 18:26:05 1998 > > >> First some notes. You are discussing things related to cdrecord. > >> If you like to see your effort back in the main stream cdrecord, this > >> is definitely the wring mailing list. > > >It's a good place to deal with the specifics of making cdrecord work on = > > >FreeBSD though. It's certainly unlikely that Peter would have been = > > I see that this should be discussed on the FreeBSD list too, but if you like > to get help from me, you could not get it from freebsd-current, I am not > subscribed. I understand that. > >The FreeBSD Posix implementation is still under development, and the = > >scheduler module is an optional addition (as allowed for under the = > >spec.). Cdrecord doesn't make the required runtime check for the = > >presence of the desired functionality. > > OK, but this is a new issue. It never has been nessecary before. > If other operating systems will start to behave similar, it would make > autoconfiguration a lot more complex. I suggest you study IEEE Std1003.1-1988 and the definition of sysconf(). It certainly appears to me (and the FreeBSD Posix implementors) that it's legitimate to define the various _SC_ constants without providing the backing functionality. If you have a differing interpretation, and some time to discuss it, I'm quite certain that we would appreciate your input. I take your point that the current state is somewhat unique, and likely to surprise an implementor that's not expecting it. This is somewhat normal for -current, which changes on a day-to-day basis. > >> >> > Bus error (core dumped) > >> = > >> If you are not able to analyze the core with adb and send a usable > >> bug description, I cannot help.. > > >The bus error is (in my case at any rate) due to a buffer overrun = > >elsewhere. I haven't been able to ascertain the cause of this yet, but = > >there are indications that winding back the visible Posix interface = > >resolves the issue. > > I am interested to find the reason for this core dump as it should not > happen. Some versions of HP-UX have the definition for POSIX RR and do not > implement it. On such HP_UX versions you usually get a warning about > the non existence of RR scheduling and cdrecord then uses nice(2). It's due to not checking the return value from the sysconf(_SC_PAGESIZE) in fifo.c. Once you get past that, there's a timing failure between the writer and reader processes due to a similar omission a little further down the file. Having dealt with these, I seem to be dummy-burning quite happily. I'll cut a disc for real to be sure, and then send you my patches for discussion. > I am testing cdrecord on all systems I can get hold of in a way that allows > testing to me (root access). As the SCSI implementations usually are not > sufficient, development and testing is mainly done on Solaris. We can almost certainly arrange that sort of access for you to a CAM system, if you're interested. > >We're not talking about "rubbish". We're talking about an > >in-development implementation of the Posix environment. > > OK, I understand. BTW: I would be happy if the user interface of the new > SCSI user transport calls would be easier to access and to understand. > In other words: > > I like to have the device files be present by default so that > programs like cdrecord onlu have to open the right file to get > access to the device. The CAM interface works like that: sprintf(name, "cd%d", unit); dev = cam_open_device(name, O_RDWR); specifically, it takes care of working out where the device nodes are and how to connect to the device. What you get back is a cam_device structure referring to the device. If you want to search on SCSI ID, that's a little trickier: for (passno = 0; ; passno++) { sprintf(name, "pass%d", passno); if ((dev = cam_open_device(name, O_RDWR)) == NULL) break; if ((dev->path_id == bus) && (dev->target_id == target) && (dev->target_lun == lun)) break; cam_close_device(dev); } The "pass" device attaches to everything, so you can use it if you want to work this way around (ie. as cdrecord currently does). > >It was. The real problems with scg have to do with the lack of visible > >documentation. It is unclear how to do any sort of meaningful error > >handling, or whether this should be managed at a lower level. Again, > >this is an issue I was postponing until I had established that > >everything else was going to behave and the interface had stabilised. > > OK, here is what I send to Sun some weeks ago: Thanks for this. I will verify that I (believe I) am compliant with this before I send you the changes. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 13:58:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAB00943 for freebsd-current-outgoing; Fri, 29 May 1998 13:58:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00919 for ; Fri, 29 May 1998 13:57:58 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id GAA19082; Sat, 30 May 1998 06:57:50 +1000 Date: Sat, 30 May 1998 06:57:50 +1000 From: Bruce Evans Message-Id: <199805292057.GAA19082@godzilla.zeta.org.au> To: bde@zeta.org.au, tlambert@primenet.com Subject: Re: ELF Step 2 Cc: current@FreeBSD.ORG, pierre.dampure@k2c.co.uk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> /usr/src/Makefile has the md5 libcrypt hard-coded in one place. I'm >> not sure why it doesn't get replaced by the correct ${_libcrypt} later. >> NOCLEAN? The wrong version should only be used to build perl. > >Why should the wrong version be used to build perl? Is it so perl can >be wrong? The md5 version is (was) certainly used to build the build-tools version of perl, but I think that is (was) the limit of the wrongness. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 14:01:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01531 for freebsd-current-outgoing; Fri, 29 May 1998 14:01:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01516 for ; Fri, 29 May 1998 14:01:44 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA17680; Fri, 29 May 1998 14:01:33 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd017644; Fri May 29 14:01:26 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA13484; Fri, 29 May 1998 14:01:21 -0700 (MST) From: Terry Lambert Message-Id: <199805292101.OAA13484@usr04.primenet.com> Subject: Re: TenDRA C++ To: nirva@ishiboo.com (Danny Dulai) Date: Fri, 29 May 1998 21:01:21 +0000 (GMT) Cc: mi@video-collage.com, current@FreeBSD.ORG In-Reply-To: <19980528020441.63901@bleep.ishiboo.com> from "Danny Dulai" at May 28, 98 02:04:41 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > gcc-2.8.1 does not compile Qt either. Or, rather, it compiles, but the > > resulting object files can not be linked together. Same with KDE stuff. > > I couldn't get it to work wtih 2.7.2.1 either, unless, when I linked, I > specified -lqt -lqt -lqt. ranlib(1) is your friend. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 14:15:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04018 for freebsd-current-outgoing; Fri, 29 May 1998 14:15:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03978 for ; Fri, 29 May 1998 14:15:22 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA23451; Fri, 29 May 1998 14:15:15 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd023410; Fri May 29 14:15:11 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA14543; Fri, 29 May 1998 14:15:01 -0700 (MST) From: Terry Lambert Message-Id: <199805292115.OAA14543@usr04.primenet.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning To: nate@mt.sri.com (Nate Williams) Date: Fri, 29 May 1998 21:15:01 +0000 (GMT) Cc: joelh@gnu.org, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG In-Reply-To: <199805281941.NAA20236@mt.sri.com> from "Nate Williams" at May 28, 98 01:41:48 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I guess I don't see why we're looking to change. > > Better/faster/less buggy compiler with a much less restrictive Copyright > seems like a win overall to me. License is a good enough reason. Not to mention an architecturally neutral ports distribution... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 14:23:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05549 for freebsd-current-outgoing; Fri, 29 May 1998 14:23:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05528 for ; Fri, 29 May 1998 14:22:54 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA26605; Fri, 29 May 1998 14:22:50 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd026576; Fri May 29 14:22:48 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA15162; Fri, 29 May 1998 14:22:43 -0700 (MST) From: Terry Lambert Message-Id: <199805292122.OAA15162@usr04.primenet.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning To: joelh@gnu.org Date: Fri, 29 May 1998 21:22:43 +0000 (GMT) Cc: nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG In-Reply-To: <199805282024.PAA01692@detlev.UUCP> from "Joel Ray Holveck" at May 28, 98 03:24:32 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm not discussing what should be, I'm discussing what is. We have a > good percentage of software from the Linux camps, and many of their > software authors wouldn't know a non-portable construct if it walked > up and introduced itself in assembly code. If the plan is to "make it work anyway", how do you propose the common Linux programming error where they fail to zero sockarr_in contents before partially filling in values and using them? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 14:50:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10957 for freebsd-current-outgoing; Fri, 29 May 1998 14:50:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (root@mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10938 for ; Fri, 29 May 1998 14:50:45 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-146.camalott.com [208.229.74.146] (may be forged)) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id QAA13725; Fri, 29 May 1998 16:48:26 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id QAA07938; Fri, 29 May 1998 16:49:19 -0500 (CDT) (envelope-from joelh) Date: Fri, 29 May 1998 16:49:19 -0500 (CDT) Message-Id: <199805292149.QAA07938@detlev.UUCP> To: tlambert@primenet.com CC: nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG In-reply-to: <199805292115.OAA14543@usr04.primenet.com> (message from Terry Lambert on Fri, 29 May 1998 21:15:01 +0000 (GMT)) Subject: Re: Fix for undefined "__error" and discussion of shared object versioning From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199805292115.OAA14543@usr04.primenet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> I guess I don't see why we're looking to change. >> Better/faster/less buggy compiler with a much less restrictive >> Copyright seems like a win overall to me. > License is a good enough reason. At what price? I still want numbers. (I've got a primitive test suite here, but I'm presently in a make world, and want to run it on an idle machine. Numbers will be posted RSN.) > Not to mention an architecturally neutral ports distribution... I don't see this as a big win for FreeBSD. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 15:09:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06012 for freebsd-current-outgoing; Fri, 29 May 1998 13:42:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05957 for ; Fri, 29 May 1998 13:42:34 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA00596; Fri, 29 May 1998 12:36:46 -0700 (PDT) Message-Id: <199805291936.MAA00596@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Joerg Schilling cc: mike@smith.net.au, freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet In-reply-to: Your message of "Fri, 29 May 1998 19:03:23 +0200." <199805291703.TAA14897@sherwood.gmd.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 29 May 1998 12:36:46 -0700 From: Mike Smith Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id NAA05971 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >From mike@antipodes.cdrom.com Fri May 29 18:26:05 1998 > > >> First some notes. You are discussing things related to cdrecord. > >> If you like to see your effort back in the main stream cdrecord, this > >> is definitely the wring mailing list. > > >It's a good place to deal with the specifics of making cdrecord work on = > > >FreeBSD though. It's certainly unlikely that Peter would have been = > > I see that this should be discussed on the FreeBSD list too, but if you like > to get help from me, you could not get it from freebsd-current, I am not > subscribed. I understand that. > >The FreeBSD Posix implementation is still under development, and the = > >scheduler module is an optional addition (as allowed for under the = > >spec.). Cdrecord doesn't make the required runtime check for the = > >presence of the desired functionality. > > OK, but this is a new issue. It never has been nessecary before. > If other operating systems will start to behave similar, it would make > autoconfiguration a lot more complex. I suggest you study IEEE Std1003.1-1988 and the definition of sysconf(). It certainly appears to me (and the FreeBSD Posix implementors) that it's legitimate to define the various _SC_ constants without providing the backing functionality. If you have a differing interpretation, and some time to discuss it, I'm quite certain that we would appreciate your input. I take your point that the current state is somewhat unique, and likely to surprise an implementor that's not expecting it. This is somewhat normal for -current, which changes on a day-to-day basis. > >> >> > Bus error (core dumped) > >> = > >> If you are not able to analyze the core with adb and send a usable > >> bug description, I cannot help.. > > >The bus error is (in my case at any rate) due to a buffer overrun = > >elsewhere. I haven't been able to ascertain the cause of this yet, but = > >there are indications that winding back the visible Posix interface = > >resolves the issue. > > I am interested to find the reason for this core dump as it should not > happen. Some versions of HP-UX have the definition for POSIX RR and do not > implement it. On such HP_UX versions you usually get a warning about > the non existence of RR scheduling and cdrecord then uses nice(2). It's due to not checking the return value from the sysconf(_SC_PAGESIZE) in fifo.c. Once you get past that, there's a timing failure between the writer and reader processes due to a similar omission a little further down the file. Having dealt with these, I seem to be dummy-burning quite happily. I'll cut a disc for real to be sure, and then send you my patches for discussion. > I am testing cdrecord on all systems I can get hold of in a way that allows > testing to me (root access). As the SCSI implementations usually are not > sufficient, development and testing is mainly done on Solaris. We can almost certainly arrange that sort of access for you to a CAM system, if you're interested. > >We're not talking about "rubbish". We're talking about an > >in-development implementation of the Posix environment. > > OK, I understand. BTW: I would be happy if the user interface of the new > SCSI user transport calls would be easier to access and to understand. > In other words: > > I like to have the device files be present by default so that > programs like cdrecord onlu have to open the right file to get > access to the device. The CAM interface works like that: sprintf(name, "cd%d", unit); dev = cam_open_device(name, O_RDWR); specifically, it takes care of working out where the device nodes are and how to connect to the device. What you get back is a cam_device structure referring to the device. If you want to search on SCSI ID, that's a little trickier: for (passno = 0; ; passno++) { sprintf(name, "pass%d", passno); if ((dev = cam_open_device(name, O_RDWR)) == NULL) break; if ((dev->path_id == bus) && (dev->target_id == target) && (dev->target_lun == lun)) break; cam_close_device(dev); } The "pass" device attaches to everything, so you can use it if you want to work this way around (ie. as cdrecord currently does). > >It was. The real problems with scg have to do with the lack of visible > >documentation. It is unclear how to do any sort of meaningful error > >handling, or whether this should be managed at a lower level. Again, > >this is an issue I was postponing until I had established that > >everything else was going to behave and the interface had stabilised. > > OK, here is what I send to Sun some weeks ago: Thanks for this. I will verify that I (believe I) am compliant with this before I send you the changes. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 16:03:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25356 for freebsd-current-outgoing; Fri, 29 May 1998 16:03:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25351 for ; Fri, 29 May 1998 16:03:24 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA01107; Fri, 29 May 1998 14:57:04 -0700 (PDT) Message-Id: <199805292157.OAA01107@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: joelh@gnu.org, nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Fri, 29 May 1998 21:22:43 -0000." <199805292122.OAA15162@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 14:57:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm not discussing what should be, I'm discussing what is. We have a > > good percentage of software from the Linux camps, and many of their > > software authors wouldn't know a non-portable construct if it walked > > up and introduced itself in assembly code. > > If the plan is to "make it work anyway", how do you propose the common > Linux programming error where they fail to zero sockarr_in contents > before partially filling in values and using them? Fix the (broken) code in the kernel that depends on zero terminators in "magic" locations. Ask Julian what he thinks about this. If he's noncommittal, remind him of the experience we had last year... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 16:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26866 for freebsd-current-outgoing; Fri, 29 May 1998 16:14:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26841 for ; Fri, 29 May 1998 16:14:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA01191; Fri, 29 May 1998 15:08:25 -0700 (PDT) Message-Id: <199805292208.PAA01191@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: shimon@simon-shapiro.org cc: Michael Hancock , "freebsd-current@freebsd.org" , tcobb , Karl Pielorz Subject: Re: DPT driver fails and panics with Degraded Array In-reply-to: Your message of "Fri, 29 May 1998 15:21:17 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 15:08:25 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am routinely running a Dual DPT with 38 drives on 6 busses. On > 3.0-CURRENT SMP. The system did lose disk drives, either intentionally, or > by accident. I cannot confirm any of Mr. Cobb's finding. I have not been > funished with any data, including the panic point, which I suspect is not > in the DPT code. I am still waiting for such data. I'd just like to point out that the "biodone: buffer not busy" panic doesn't come from the DPT driver, but may be caused by it calling biodone() on a buffer that the system does not believe is busy. These situations are worth analysing, and I hope to see you and Troy resolving this one, even if it means that you point the finger elsewhere. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 16:16:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27129 for freebsd-current-outgoing; Fri, 29 May 1998 16:16:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27043 for ; Fri, 29 May 1998 16:15:54 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA08374; Fri, 29 May 1998 16:15:44 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd006071; Fri May 29 16:08:33 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA22868; Fri, 29 May 1998 16:08:21 -0700 (MST) From: Terry Lambert Message-Id: <199805292308.QAA22868@usr05.primenet.com> Subject: Re: library symlinks To: kong@kong.spb.ru (Hostas Red) Date: Fri, 29 May 1998 23:08:21 +0000 (GMT) Cc: Pierre.Dampure@barclayscapital.com, current@FreeBSD.ORG In-Reply-To: from "Hostas Red" at May 29, 98 04:58:03 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thank You, and all, who answered my Q. I've changed links of libcrypt* > from libscrypt* to libdescrypt*. These symlinks should be relatively pathed instead of absolutely pathed so that they can be moved around without damaging their referential integrity. This should be fixed by someone with commit privs as soon as possible to avoid future fiascos. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 16:31:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29745 for freebsd-current-outgoing; Fri, 29 May 1998 16:31:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29722 for ; Fri, 29 May 1998 16:31:22 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA22721; Fri, 29 May 1998 16:31:10 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd022646; Fri May 29 16:31:04 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA23999; Fri, 29 May 1998 16:30:56 -0700 (MST) From: Terry Lambert Message-Id: <199805292330.QAA23999@usr05.primenet.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning To: mike@smith.net.au (Mike Smith) Date: Fri, 29 May 1998 23:30:55 +0000 (GMT) Cc: tlambert@primenet.com, joelh@gnu.org, nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG In-Reply-To: <199805292157.OAA01107@dingo.cdrom.com> from "Mike Smith" at May 29, 98 02:57:04 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If the plan is to "make it work anyway", how do you propose the common > > Linux programming error where they fail to zero sockarr_in contents > > before partially filling in values and using them? > > Fix the (broken) code in the kernel that depends on zero terminators in > "magic" locations. I think that Linux works not because these "magic" places are handled "correctly", but because it zeros stack page allocations for "security reasons", and simply lucks out that the call graph doesn't descend then ascend leaving crap behind. >From my reading of the use of the structure contents, it's perfectly valid to fill out other pieces of teh structure with non-zero values and then expect the kernel to interpret the non-zero values as significant. The problem is in the default value of zero being significant, AND in the default value from the stack being non-zero, but not ALSO significant. When I ported the sample implementation of the Service Location Protocol code from Sun Microsystems, I had to de-Linux the type type declarations, then memset( &x, 0, sizeof(struct sockaddr_in)); all over the place. While we are on the subject of portability problems, doesn't anyone else find it annoying that memcpy() is not guaranteed to work on overlapping memory ranges, yet we are migrating bcopy() to memcpy() as time goes on? Grrrr... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 16:42:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01978 for freebsd-current-outgoing; Fri, 29 May 1998 16:42:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from m2.findmail.com (m2.findmail.com [209.185.96.135]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA01920 for ; Fri, 29 May 1998 16:42:00 -0700 (PDT) (envelope-from brianfeldman@hotmail.com) Received: (qmail 14426 invoked by uid 505); 29 May 1998 23:40:22 -0000 Date: 29 May 1998 23:40:22 -0000 Message-ID: <19980529234022.14425.qmail@m2.findmail.com> From: "Brian Feldman" Subject: fd + SoftUpdates = crash To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ouch, here's the bt: (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:281 #1 0xf0118fc7 in panic (fmt=0xf01f1f56 "isa_dmastart: bad bounce buffer") at ../../kern/kern_shutdown.c:421 #2 0xf01f1fcf in isa_dmastart (flags=587333684, addr=0xf2d4d014 "ð\004", nbytes=4096, chan=2) at ../../i386/isa/isa.c:767 #3 0xf01ec1fd in fdstate (fdcu=0, fdc=0xf02622d4) at ../../i386/isa/fd.c:1640 #4 0xf01ebcb3 in fdintr (fdcu=0) at ../../i386/isa/fd.c:1445 #5 0xf01ebc75 in fd_pseudointr (arg1=0x0) at ../../i386/isa/fd.c:1425 #6 0xf011d203 in softclock () at ../../kern/kern_timeout.c:124 #7 0xf01d6cc7 in doreti_swi () Cannot access memory at address 0x274e35f8. (kgdb) Cheers, Brian Feldman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 16:43:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02146 for freebsd-current-outgoing; Fri, 29 May 1998 16:43:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02128 for ; Fri, 29 May 1998 16:43:12 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id XAA09398; Fri, 29 May 1998 23:42:39 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id BAA29342; Sat, 30 May 1998 01:42:19 +0200 (MET DST) Message-ID: <19980530014218.62162@follo.net> Date: Sat, 30 May 1998 01:42:19 +0200 From: Eivind Eklund To: Terry Lambert , Mike Smith Cc: joelh@gnu.org, nate@mt.sri.com, rnordier@nordier.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <199805292157.OAA01107@dingo.cdrom.com> <199805292330.QAA23999@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805292330.QAA23999@usr05.primenet.com>; from Terry Lambert on Fri, May 29, 1998 at 11:30:55PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 29, 1998 at 11:30:55PM +0000, Terry Lambert wrote: > While we are on the subject of portability problems, doesn't anyone > else find it annoying that memcpy() is not guaranteed to work on > overlapping memory ranges, yet we are migrating bcopy() to memcpy() > as time goes on? Grrrr... memmove() is for the cases where you're not guaranteed to be non-overlapping, exctly like bcopy(). memcpy() is for those cases where you know that you don't have overlaps. I don't find this problematic, no. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 17:29:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09903 for freebsd-current-outgoing; Fri, 29 May 1998 17:29:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09895 for ; Fri, 29 May 1998 17:29:46 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA16521; Fri, 29 May 1998 17:29:18 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Terry Lambert cc: mike@smith.net.au (Mike Smith), joelh@gnu.org, nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Fri, 29 May 1998 23:30:55 -0000." <199805292330.QAA23999@usr05.primenet.com> Date: Fri, 29 May 1998 17:29:18 -0700 Message-ID: <16517.896488158@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While we are on the subject of portability problems, doesn't anyone > else find it annoying that memcpy() is not guaranteed to work on > overlapping memory ranges, yet we are migrating bcopy() to memcpy() > as time goes on? Grrrr... Who's "we", white man? :-) ... STANDARDS The memcpy() function conforms to ISO 9899: 1990 (``ISO C''). BUGS In this implementation memcpy() is implemented using bcopy(3), and therefore the strings may overlap. On other systems, copying overlapping strings may produce surprises. A simpler solution is to not use memcpy(). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 17:55:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15068 for freebsd-current-outgoing; Fri, 29 May 1998 17:55:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15060 for ; Fri, 29 May 1998 17:55:18 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id RAA24471; Fri, 29 May 1998 17:55:07 -0700 (PDT) (envelope-from jdp) Message-Id: <199805300055.RAA24471@austin.polstra.com> To: kuku@gilberto.physik.RWTH-Aachen.DE Subject: Re: help! - nodes.h where is it? In-Reply-To: <19980529091313.42603@gil.physik.rwth-aachen.de> References: <199805280722.JAA06249@gilberto.physik.RWTH-Aachen.DE> <199805281631.LAA09351@pyrl.eye> <19980529091313.42603@gil.physik.rwth-aachen.de> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Fri, 29 May 1998 17:55:07 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19980529091313.42603@gil.physik.rwth-aachen.de>, Christoph Kukulies wrote: > I'm using cvsup. (REL_15_1 as I just found out - thought I have 15_4 > also laying around - maybe I'd better upgrade). Yes, you should upgrade, but I don't think that will solve your problem. I haven't fixed (or heard of) any bugs causing the wrong files to be sent for ages -- revision 13.something at the latest. But everybody should upgrade to 15.4 because it will deal properly with the new version of CVS when we upgrade to that on freefall (soon). You'll get a zillion "fixups" otherwise. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 18:07:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16964 for freebsd-current-outgoing; Fri, 29 May 1998 18:07:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16918 for ; Fri, 29 May 1998 18:06:44 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id VAA23704; Fri, 29 May 1998 21:04:09 -0400 (EDT) Date: Fri, 29 May 1998 21:04:09 -0400 (EDT) From: "Larry S. Lile" To: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805292115.OAA14543@usr04.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So how do I get make world to run to completion? I have been trying to build for 2 days now. Help, help :( Larry Lile lile@stdio.com On Fri, 29 May 1998, Terry Lambert wrote: > > > I guess I don't see why we're looking to change. > > > > Better/faster/less buggy compiler with a much less restrictive Copyright > > seems like a win overall to me. > > > License is a good enough reason. > > Not to mention an architecturally neutral ports distribution... > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 18:07:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17089 for freebsd-current-outgoing; Fri, 29 May 1998 18:07:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (jkh@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17071 for ; Fri, 29 May 1998 18:07:54 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: (from jkh@localhost) by time.cdrom.com (8.8.8/8.8.8) id SAA16711 for current@freebsd.org; Fri, 29 May 1998 18:08:16 -0700 (PDT) (envelope-from jkh) Date: Fri, 29 May 1998 18:08:16 -0700 (PDT) From: "Jordan K. Hubbard" Message-Id: <199805300108.SAA16711@time.cdrom.com> To: current@FreeBSD.ORG Subject: I see one major problem with DEVFS... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bash# ls -l bpf* crw------- 1 root wheel 23, 0 May 29 08:03 bpf0 crw------- 1 root wheel 23, 1 May 29 08:03 bpf1 crw------- 1 root wheel 23, 2 May 29 08:03 bpf2 crw------- 1 root wheel 23, 3 May 29 08:03 bpf4 bash# rm bpf4 bash# ls -l bpf* crw------- 1 root wheel 23, 0 May 29 08:03 bpf0 crw------- 1 root wheel 23, 1 May 29 08:03 bpf1 crw------- 1 root wheel 23, 2 May 29 08:03 bpf2 bash# mknod bpf4 c 23 3 E.g. I can shoot my foot off, but I can't sew it back on. :-) Also, while I'm on this topic, what is the purpose served by DEVFS auto-mounting itself on "dummy_mount"? I'm only going to mount it as /dev later, so I don't really get the idea behind the first instance of it. Is it for "cloning" purposes or something? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 18:35:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21025 for freebsd-current-outgoing; Fri, 29 May 1998 18:35:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (root@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21010 for ; Fri, 29 May 1998 18:34:59 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id PAA09325; Fri, 29 May 1998 15:02:45 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd019857; Fri May 29 14:20:48 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA14978; Fri, 29 May 1998 14:20:43 -0700 (MST) From: Terry Lambert Message-Id: <199805292120.OAA14978@usr04.primenet.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning To: joelh@gnu.org Date: Fri, 29 May 1998 21:20:43 +0000 (GMT) Cc: eivind@yes.no, rnordier@nordier.com, current@FreeBSD.ORG In-Reply-To: <199805282015.PAA01671@detlev.UUCP> from "Joel Ray Holveck" at May 28, 98 03:15:44 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Well, here are a couple of points: > > * License > > I'll assume that TenDRA and XANDF are both BSD-license? Yes. > > * General quality of system (GCC is written under the paradigm 'learn > > writing compilers as we go') > > I can't comment on that one, not having examined the source code to > the various compilers. But are the others written by professional > compiler writers? Yes. Under denfense contract. > > * Possibilities for exploiting the cross-CPU nature of XANDF > > How are XANDF's cross-cpu capabilities more powerful than gcc's? You can distribute "binaries" and localize them to an architecture at install time. This means you can distribute commercial code that will run on x86, Alpha, MIPS, PPC, 68k, VAX, SPARC, etc., etc.. For FreeBSD, this means one "ports" CDROM will work for all future architectures. It also means that one "ports" CDROM will work for FreeBSD 3.x and FreeBSD 235.x. > > * Better error checking/control > > How do you mean? Full mapping of the error checking and warning space. GCC only maps the parts that they thought were important, and then it's done pretty haphazardly. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 19:07:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26283 for freebsd-current-outgoing; Fri, 29 May 1998 19:07:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (root@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26276 for ; Fri, 29 May 1998 19:07:24 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id OAA09010; Fri, 29 May 1998 14:00:12 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp04.primenet.com, id smtpda29416; Fri May 29 12:47:23 1998 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id MAA29647; Fri, 29 May 1998 12:47:15 -0700 (MST) From: Terry Lambert Message-Id: <199805291947.MAA29647@usr07.primenet.com> Subject: Re: Argh! errno spam! To: mike@smith.net.au (Mike Smith) Date: Fri, 29 May 1998 19:47:14 +0000 (GMT) Cc: wollman@khavrinen.lcs.mit.edu, mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: <199805272034.NAA01753@dingo.cdrom.com> from "Mike Smith" at May 27, 98 01:34:17 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Any C program which has a structure member called `errno' is > > erroneous. > > How so? Structure members have been allowed to be non-unique for a > while now; I don't recall there being constraints on globals vs. > structure members at all. > > There are a few perfectly good reasons to call a structure member errno, > but regardless of the good reasons, I fear for the code in the ports > collection. 8( > > I was bitten by this with the NetBSD-derived bootcode I'm working on, > which doesn't use libc and thus needs its own errno in order to be a > reasonable facsimile therof. (Yes, I have a workaround.) Any code which does not use libc, has a structure member called `errno', and still includes errno.h... is erroneous. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 19:38:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29565 for freebsd-current-outgoing; Fri, 29 May 1998 19:38:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pobox.com ([208.141.230.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29554 for ; Fri, 29 May 1998 19:38:28 -0700 (PDT) (envelope-from alk@pobox.com) Received: (from alk@localhost) by pobox.com (8.8.8/8.7.3) id VAA27971; Fri, 29 May 1998 21:38:21 -0500 (CDT) Date: Fri, 29 May 1998 21:38:21 -0500 (CDT) Message-Id: <199805300238.VAA27971@pobox.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Reply-To: alk@pobox.com To: current@FreeBSD.ORG Subject: buildworld stops in strip X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... cp strip maybe_stripped strip maybe_stripped strip: maybe_stripped: File format not recognized *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Presumably this is a well-understood elf-ification glitch. What's the *right* way to get over this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 20:05:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03125 for freebsd-current-outgoing; Fri, 29 May 1998 20:05:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03102 for ; Fri, 29 May 1998 20:05:00 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA23777; Fri, 29 May 1998 19:58:21 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd023771; Sat May 30 02:58:14 1998 Message-ID: <356F75C2.7566F4CF@whistle.com> Date: Fri, 29 May 1998 19:58:10 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <199805300108.SAA16711@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > bash# ls -l bpf* > crw------- 1 root wheel 23, 0 May 29 08:03 bpf0 > crw------- 1 root wheel 23, 1 May 29 08:03 bpf1 > crw------- 1 root wheel 23, 2 May 29 08:03 bpf2 > crw------- 1 root wheel 23, 3 May 29 08:03 bpf4 > bash# rm bpf4 > bash# ls -l bpf* > crw------- 1 root wheel 23, 0 May 29 08:03 bpf0 > crw------- 1 root wheel 23, 1 May 29 08:03 bpf1 > crw------- 1 root wheel 23, 2 May 29 08:03 bpf2 > bash# mknod bpf4 c 23 3 > > E.g. I can shoot my foot off, but I can't sew it back on. :-) > > Also, while I'm on this topic, what is the purpose served by > DEVFS auto-mounting itself on "dummy_mount"? I'm only going to > mount it as /dev later, so I don't really get the idea behind > the first instance of it. Is it for "cloning" purposes or > something? > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message dummy_mount is a hack the trouble is that the root fs is mounted before /dev so the device has to come out of the kernel's internel /de blueprint (from which it makes the user alterable versions that people mount) trouble with this is that SYNC only writes back superblocks on devices that are mounted from filesysytems in the mount list, which the internal copy is not (or it was not). to ge tthe root superblock SYNC'd I needed to add that internal copy to the mount list.. I've since decided that in the DEVFS/SLICE case, a better answer would be to special-case that and just do it and the mount list as well julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 20:05:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03146 for freebsd-current-outgoing; Fri, 29 May 1998 20:05:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03124 for ; Fri, 29 May 1998 20:05:04 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id XAA09419; Fri, 29 May 1998 23:04:54 -0400 (EDT) (envelope-from wollman) Date: Fri, 29 May 1998 23:04:54 -0400 (EDT) From: Garrett Wollman Message-Id: <199805300304.XAA09419@khavrinen.lcs.mit.edu> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-Reply-To: <199805292157.OAA01107@dingo.cdrom.com> References: <199805292122.OAA15162@usr04.primenet.com> <199805292157.OAA01107@dingo.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Fix the (broken) code in the kernel that depends on zero terminators in > "magic" locations. Um, no. It's not broken. The API is very clear: You Shall Zero The Structure First. There is a very good reason for this -- the routing code doesn't know a damn thing about where the holes are in fifteen random address families' sockaddrs are, and shouldn't need to. Otherwise, comparison of two sockaddrs would require an outcall to a family-specific function -- and all of my researcher friends would laugh at me and tell me what an idiot the implementor of that idea was. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 20:09:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04310 for freebsd-current-outgoing; Fri, 29 May 1998 20:09:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04275; Fri, 29 May 1998 20:09:32 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA05164; Fri, 29 May 1998 22:09:08 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199805300309.WAA05164@dyson.iquest.net> Subject: Re: Fastvid.. In-Reply-To: <19980527232341.65268@bleep.ishiboo.com> from Danny Dulai at "May 27, 98 11:23:41 pm" To: nirva@ishiboo.com (Danny Dulai) Date: Fri, 29 May 1998 22:09:08 -0500 (EST) Cc: doconnor@gsoft.com.au, freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Quoting Daniel O'Connor (doconnor@gsoft.com.au): > > > > The speedup factor is 1.89, mmm :) > > > The vm_map.h problems are solved by #including , but the > MOD_SYSCALL on line 103 and the problem at line 234 I do not understand. > > Does anyone have copy of this module for -current? > This is a copy of the original code that I submitted to someone who cleaned it up (I am sorry that I forgot who actually took ownership.) This code works on my display adaptor, and compiles under -current. #include #include #include #include #include #include #include #include #include #include #include #include #include #define I586_CPU /* XXX for i586_ctr_freq */ #include static int load(struct lkm_table *lkmtp, int cmd); static int mycall(struct proc *p, void *uap, int *retval); extern int newsyscall_mod(struct lkm_table *lkmtp, int cmd, int ver); static int unload(struct lkm_table *lkmtp, int cmd); vm_offset_t contigaddr; struct proc *curproc; static struct sysent newent = { 0, mycall /* # of args, function pointer*/ }; MOD_SYSCALL(newsyscall_mod, -1, &newent); static struct { int address; char *name; } ranges[] = { {0x250, "MTRRfix64K_00000"}, {0x258, "MTRRfix16K_80000"}, {0x259, "MTRRfix16K_A0000"}, {0x268, "MTRRfix4K_C0000"}, {0x269, "MTRRfix4K_C8000"}, {0x26a, "MTRRfix4K_D0000"}, {0x26b, "MTRRfix4K_D8000"}, {0x26c, "MTRRfix4K_E0000"}, {0x26d, "MTRRfix4K_E8000"}, {0x26e, "MTRRfix4K_F0000"}, {0x26f, "MTRRfix4K_F8000"}, {0x0, NULL} }; static int load(struct lkm_table *lkmtp, int cmd) { int i; long long base; long long mask; vm_offset_t kernaddr; struct proc *otherp; int tbase, tmask, type; unsigned long long newval; pmap_t pmap; base = rdmsr(0x2ff); tbase = base & 0xfff; printf("default: type: 0x%x\n", tbase); wrmsr(0x259, 0x0101010101010101ULL); /* * Add in an Memory type register entry here, after * reviewing the output of your X server. * My video ram is at phys addr 0xfe000000, size 8MB */ #define VIDPHYSADDR (0xfe000000) #define VIDPHYSSIZE (0x800000) #define MSRINDEX 5 base = VIDPHYSADDR | 0x1; mask = (long long) (0xfffffffffLL - ((long) VIDPHYSSIZE - 1)) | (long long) 0x800; wrmsr(0x200 + MSRINDEX * 2, base); wrmsr(0x201 + MSRINDEX * 2, mask); for(i=0;i<8;i++) { int basehi, baselo; int maskhi, masklo; base = rdmsr(0x200 + i * 2); basehi = (unsigned long long) base >> 32; baselo = (unsigned long long) base & 0xffffffffL; type = base & 0xff; base >>= 12; tbase = base; mask = rdmsr(0x201 + i * 2); if ((mask & 0x800) == 0) continue; maskhi = (unsigned long long) mask >> 32; masklo = (unsigned long long) mask & 0xffffffffL; mask >>= 12; tmask = mask; printf("%d: type: %d, addr: 0x%x000, mask: 0x%x000\n basehi: 0x%8.8x, baselo: 0x%8.8x\n maskhi: 0x%8.8x, masklo: 0x%8.8x\n", i, type, tbase, tmask, basehi, baselo, maskhi, masklo); } for(i=0;ranges[i].address;i++) { int maskhi, masklo; mask = rdmsr(ranges[i].address); maskhi = (unsigned long long) mask >> 32; masklo = (unsigned long long) mask & 0xffffffffL; printf("%s: 0x%8.8x 0x%8.8x\n", ranges[i].name, maskhi, masklo); } tbase = rdmsr(0x1e0); printf("BKUPTMPDR6: %x\n", tbase); tbase = rdmsr(0x2a); printf("BKUPTMPDR6: %x\n", tbase); pmap = &curproc->p_vmspace->vm_pmap; for(i=0;i<1024;i++) { unsigned entry; entry = (unsigned) curproc->p_vmspace->vm_pmap.pm_pdir[i]; if (entry & PG_PS) { printf("4MB page: 0x%x(%x)\n", entry, i << 22); } } otherp = pfind(153); if (otherp) { for(i=0;i<1024;i++) { unsigned entry; entry = (unsigned) otherp->p_vmspace->vm_pmap.pm_pdir[i]; if (entry & PG_PS) { printf("4MB page: 0x%x(%x)\n", entry, i << 22); } } } return 0; } static int mycall(struct proc *p, void *uap, int *retval) { return ENODEV; } int newsyscall_mod(struct lkm_table *lkmtp, int cmd, int ver) { #if 0 DISPATCH(lkmtp, cmd, ver, load, unload, lkm_nullcmd) #endif MOD_DISPATCH(newsyscall_mod, lkmtp, cmd, ver, load, unload, lkm_nullcmd) #if 0 MOD_DISPATCH(newsyscall_mod, lkmtp, cmd, ver, newsyscall_load, lkm_nullcmd, lkm_nullcmd) #endif } static int unload(struct lkm_table *lkmtp, int cmd) { return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 20:12:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04954 for freebsd-current-outgoing; Fri, 29 May 1998 20:12:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (root@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04941 for ; Fri, 29 May 1998 20:12:18 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA04894; Fri, 29 May 1998 16:01:44 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd026044; Fri May 29 15:39:25 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id PAA21359; Fri, 29 May 1998 15:39:14 -0700 (MST) From: Terry Lambert Message-Id: <199805292239.PAA21359@usr05.primenet.com> Subject: Re: Fix for undefined "__error" and discussion of shared object versioning To: joelh@gnu.org Date: Fri, 29 May 1998 22:39:14 +0000 (GMT) Cc: tlambert@primenet.com, nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG In-Reply-To: <199805292149.QAA07938@detlev.UUCP> from "Joel Ray Holveck" at May 29, 98 04:49:19 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > License is a good enough reason. > > At what price? I still want numbers. (I've got a primitive test > suite here, but I'm presently in a make world, and want to run it on > an idle machine. Numbers will be posted RSN.) At nearly any price. The main reason most of us aren't hacking Linux is the GPL on Linux preventing us from using (not utilizing) the code and code fragments in commercial products. GPL'ed code is not suitable for embedded systems. I have this fantasy of someone using GPL'ed code for the executive in a missle system, and Sadam Hussein calling up and demanding source code, or that the US cease their "distribution" of the binary code to Iraq. > > Not to mention an architecturally neutral ports distribution... > > I don't see this as a big win for FreeBSD. NetBSD and OpenBSD use the FreeBSD ports distribution. FreeBSD is also in the process of being ported to multiple architectures. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 20:15:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05524 for freebsd-current-outgoing; Fri, 29 May 1998 20:15:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05480 for ; Fri, 29 May 1998 20:15:14 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id NAA08210; Sat, 30 May 1998 13:23:04 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805300323.NAA08210@cimlogic.com.au> Subject: Re: buildworld stops in strip In-Reply-To: <199805300238.VAA27971@pobox.com> from Tony Kimball at "May 29, 98 09:38:21 pm" To: alk@pobox.com Date: Sat, 30 May 1998 13:23:03 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Kimball wrote: > ... > cp strip maybe_stripped > strip maybe_stripped > strip: maybe_stripped: File format not recognized Which strip directory is this? My guess is that the ELF strip (from gnu/usr.bin/binutils/strip) is being executed instead of the aout version. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 20:35:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08770 for freebsd-current-outgoing; Fri, 29 May 1998 20:35:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08761 for ; Fri, 29 May 1998 20:35:43 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id UAA17272; Fri, 29 May 1998 20:35:39 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 19:58:10 PDT." <356F75C2.7566F4CF@whistle.com> Date: Fri, 29 May 1998 20:35:39 -0700 Message-ID: <17268.896499339@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > E.g. I can shoot my foot off, but I can't sew it back on. :-) OK, I understand the dummy_mount problem a little better now. Now what about the issue I raised of not being able to mknod back things which have been removed? :-) -Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 20:45:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09927 for freebsd-current-outgoing; Fri, 29 May 1998 20:45:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09921 for ; Fri, 29 May 1998 20:45:35 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id DAA16006; Sat, 30 May 1998 03:45:33 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id FAA03880; Sat, 30 May 1998 05:45:12 +0200 (MET DST) Message-ID: <19980530054511.13601@follo.net> Date: Sat, 30 May 1998 05:45:11 +0200 From: Eivind Eklund To: Mike Smith , Joerg Schilling Cc: freebsd-current@FreeBSD.ORG Subject: Re: cdrecord trouble on currnet / SCSI ABI test References: <199805291720.TAA15036@sherwood.gmd.de> <199805291915.MAA00509@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805291915.MAA00509@dingo.cdrom.com>; from Mike Smith on Fri, May 29, 1998 at 12:15:53PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 29, 1998 at 12:15:53PM -0700, Mike Smith wrote: > > But for timeout tests not every CD-ROM drive is usable because the only > > idea I currently have to force a SCSI timeout is to do one very big > > SCSi-VERIFY on a disk with > 400MB data on it. This is because not all > > timeout implementations catch timeouts fast (< 1 minute). > > Build a small board containing a 5380 and a microcontroller. Write > some minimal SCSI target software, and put a console on it. > > You could probably sell 5-10 of these to SCSI driver authors. What I'd do for this kind of testing is equip a FreeBSD machine with a well-known work SCSI-controller (probably an NCR), and emulate a target from that end :-) It is possible this is due to my lack of hardware building experience, but I still like FreeBSD better than microcontrollers :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 20:49:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10435 for freebsd-current-outgoing; Fri, 29 May 1998 20:49:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10427 for ; Fri, 29 May 1998 20:49:22 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id DAA16063; Sat, 30 May 1998 03:48:59 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id FAA03891; Sat, 30 May 1998 05:48:42 +0200 (MET DST) Message-ID: <19980530054842.51661@follo.net> Date: Sat, 30 May 1998 05:48:42 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <199805300108.SAA16711@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805300108.SAA16711@time.cdrom.com>; from Jordan K. Hubbard on Fri, May 29, 1998 at 06:08:16PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 29, 1998 at 06:08:16PM -0700, Jordan K. Hubbard wrote: > bash# ls -l bpf* > crw------- 1 root wheel 23, 0 May 29 08:03 bpf0 > crw------- 1 root wheel 23, 1 May 29 08:03 bpf1 > crw------- 1 root wheel 23, 2 May 29 08:03 bpf2 > crw------- 1 root wheel 23, 3 May 29 08:03 bpf4 > bash# rm bpf4 > bash# ls -l bpf* > crw------- 1 root wheel 23, 0 May 29 08:03 bpf0 > crw------- 1 root wheel 23, 1 May 29 08:03 bpf1 > crw------- 1 root wheel 23, 2 May 29 08:03 bpf2 > bash# mknod bpf4 c 23 3 > > E.g. I can shoot my foot off, but I can't sew it back on. :-) Yes, you can. You can mount another devfs and 'mv' a device from it (or at least that's the way the specs read - I don't have devfs enabled right now, so I can't test). > Also, while I'm on this topic, what is the purpose served by > DEVFS auto-mounting itself on "dummy_mount"? I'm only going to > mount it as /dev later, so I don't really get the idea behind > the first instance of it. Is it for "cloning" purposes or > something? I think this is only significant for bootstrap/internal kernel reasons, but I may well be wrong. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 20:51:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10920 for freebsd-current-outgoing; Fri, 29 May 1998 20:51:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10915 for ; Fri, 29 May 1998 20:51:45 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id UAA17378; Fri, 29 May 1998 20:52:02 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Eivind Eklund cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 05:48:42 +0200." <19980530054842.51661@follo.net> Date: Fri, 29 May 1998 20:52:01 -0700 Message-ID: <17374.896500321@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > E.g. I can shoot my foot off, but I can't sew it back on. :-) > > Yes, you can. You can mount another devfs and 'mv' a device from it > (or at least that's the way the specs read - I don't have devfs > enabled right now, so I can't test). That's utterly rude. :-) I hope you're not implying that this is going to be the accepted way for doing this in the future as well. Non-persistence is a big enough violation of POLA as it is, and not even being able to do mknod(2) operations on a devfs to replace missing entries would be a POLA catastrophe. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 21:00:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12233 for freebsd-current-outgoing; Fri, 29 May 1998 21:00:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12222 for ; Fri, 29 May 1998 21:00:31 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id EAA16310; Sat, 30 May 1998 04:00:26 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id GAA03950; Sat, 30 May 1998 06:00:09 +0200 (MET DST) Message-ID: <19980530060008.33353@follo.net> Date: Sat, 30 May 1998 06:00:08 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <19980530054842.51661@follo.net> <17374.896500321@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <17374.896500321@time.cdrom.com>; from Jordan K. Hubbard on Fri, May 29, 1998 at 08:52:01PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 29, 1998 at 08:52:01PM -0700, Jordan K. Hubbard wrote: > > > E.g. I can shoot my foot off, but I can't sew it back on. :-) > > > > Yes, you can. You can mount another devfs and 'mv' a device from it > > (or at least that's the way the specs read - I don't have devfs > > enabled right now, so I can't test). > > That's utterly rude. :-) > > I hope you're not implying that this is going to be the accepted way > for doing this in the future as well. Non-persistence is a big enough > violation of POLA as it is, and not even being able to do mknod(2) > operations on a devfs to replace missing entries would be a POLA > catastrophe. Allowing mknod on a devfs would be somewhat akin to pointing an Uzi at your foot and playing with how close to the actual trig limit you can pull the trigger without firing. Remember, at least major numbers don't exist when DEVFS is fully deployed. For disks, minor numbers don't exist either. Perhaps extend mknod to give a warning "you're attempting to do a 'mknod' on a devfs. This is not possible. However, you can achieve the effect you want by mounting another devfs and using 'mv' to transfer device nodes' when somebody attempt to run it against a devfs? I'm certain somebody can write a paragraph in actual english that let a child of five understand this (as compared to my pseudo-understandable technobabble above). We might run into a block in that very few children of five are FreeBSD admins, though... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 21:16:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14725 for freebsd-current-outgoing; Fri, 29 May 1998 21:16:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14718 for ; Fri, 29 May 1998 21:16:52 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id NAA26829; Sat, 30 May 1998 13:46:10 +0930 (CST) (envelope-from grog) Message-ID: <19980530134610.C20360@freebie.lemis.com> Date: Sat, 30 May 1998 13:46:10 +0930 From: Greg Lehey To: John Birrell , alk@pobox.com Cc: current@FreeBSD.ORG Subject: Re: buildworld stops in strip References: <199805300238.VAA27971@pobox.com> <199805300323.NAA08210@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805300323.NAA08210@cimlogic.com.au>; from John Birrell on Sat, May 30, 1998 at 01:23:03PM +1000 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 May 1998 at 13:23:03 +1000, John Birrell wrote: > Tony Kimball wrote: >> ... >> cp strip maybe_stripped >> strip maybe_stripped >> strip: maybe_stripped: File format not recognized > > Which strip directory is this? > My guess is that the ELF strip (from gnu/usr.bin/binutils/strip) is > being executed instead of the aout version. Almost correct. This happened to me. I had . in my path, and as you can see there's a strip in the current directory, so that's the one it executed. It doesn't understand a.out. I took out the . and all ran fine. I didn't mention this, because I know the number of people who would come and say "don't put . in your PATH", but I'm apparently not the only one :-) Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 21:17:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14777 for freebsd-current-outgoing; Fri, 29 May 1998 21:17:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14771 for ; Fri, 29 May 1998 21:17:15 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id MAA19723; Sat, 30 May 1998 12:16:50 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805300416.MAA19723@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: alk@pobox.com cc: current@FreeBSD.ORG Subject: Re: buildworld stops in strip In-reply-to: Your message of "Fri, 29 May 1998 21:38:21 EST." <199805300238.VAA27971@pobox.com> Date: Sat, 30 May 1998 12:16:49 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Kimball wrote: > ... > cp strip maybe_stripped > strip maybe_stripped > strip: maybe_stripped: File format not recognized > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > Presumably this is a well-understood elf-ification glitch. > What's the *right* way to get over this? Two questions.. Which strip is this? gnu/usr.bin/binutils/strip or usr.bin/strip? Second, do you have "." in front of your $PATH? Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 21:24:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15778 for freebsd-current-outgoing; Fri, 29 May 1998 21:24:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15738 for ; Fri, 29 May 1998 21:23:32 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id OAA10557; Sat, 30 May 1998 14:30:27 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805300430.OAA10557@cimlogic.com.au> Subject: Re: buildworld stops in strip In-Reply-To: <19980530134610.C20360@freebie.lemis.com> from Greg Lehey at "May 30, 98 01:46:10 pm" To: grog@lemis.com (Greg Lehey) Date: Sat, 30 May 1998 14:30:27 +1000 (EST) Cc: jb@cimlogic.com.au, alk@pobox.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > Almost correct. This happened to me. I had . in my path, and as you > can see there's a strip in the current directory, so that's the one it > executed. It doesn't understand a.out. I took out the . and all ran > fine. > > I didn't mention this, because I know the number of people who would > come and say "don't put . in your PATH", but I'm apparently not the > only one :-) I thought buildworld was supposed to set up it's own path with it's $WORLDTMP directories first. If so, it sounds like strip is being found in one of those. I'll defer to anyone who is actually building though. I decided I'd wait a bit longer before updating my -current machine. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 21:55:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17977 for freebsd-current-outgoing; Fri, 29 May 1998 21:55:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17970 for ; Fri, 29 May 1998 21:55:30 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id EAA17400; Sat, 30 May 1998 04:55:28 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id GAA04127; Sat, 30 May 1998 06:55:09 +0200 (MET DST) Message-ID: <19980530065508.30647@follo.net> Date: Sat, 30 May 1998 06:55:08 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <19980530054842.51661@follo.net> <17374.896500321@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <17374.896500321@time.cdrom.com>; from Jordan K. Hubbard on Fri, May 29, 1998 at 08:52:01PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 29, 1998 at 08:52:01PM -0700, Jordan K. Hubbard wrote: > > > E.g. I can shoot my foot off, but I can't sew it back on. :-) > > > > Yes, you can. You can mount another devfs and 'mv' a device from it > > (or at least that's the way the specs read - I don't have devfs > > enabled right now, so I can't test). > > That's utterly rude. :-) > > I hope you're not implying that this is going to be the accepted way > for doing this in the future as well. Non-persistence is a big enough > violation of POLA as it is, and not even being able to do mknod(2) > operations on a devfs to replace missing entries would be a POLA > catastrophe. OK, this can be solved in at least these three ways (neither of which are pretty): (1) Add an ioctl() to devfs that does all of this in-kernel, and make mknod use this. (2) Add another layer to devfs that let somebody request by major/minor (requires a lot of hoops for SLICE, and locks us to the present set of majors/minors until the compatibility mode goes away). Call this layer from mknod to get correct device names. (3) Put a table in mknod that tells what owns which majors, and how to parse the minors. Use that to parse majors and minors. For the two latter solutions, mknod would have to mount a temporary devfs somewhere, and hardlink over the correct device node to the name supplied. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 21:55:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18000 for freebsd-current-outgoing; Fri, 29 May 1998 21:55:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17995 for ; Fri, 29 May 1998 21:55:41 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA17591; Fri, 29 May 1998 21:55:55 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Eivind Eklund cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 06:00:08 +0200." <19980530060008.33353@follo.net> Date: Fri, 29 May 1998 21:55:55 -0700 Message-ID: <17587.896504155@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Allowing mknod on a devfs would be somewhat akin to pointing an Uzi at > your foot and playing with how close to the actual trig limit you can > pull the trigger without firing. Naw, nothing so dire. Backwards compatability doesn't always have to be asthetically pleasing, it just has to work and for a reasonable period of time until people have made the transition. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 22:00:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18644 for freebsd-current-outgoing; Fri, 29 May 1998 22:00:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18639 for ; Fri, 29 May 1998 22:00:22 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id FAA17493; Sat, 30 May 1998 05:00:18 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id HAA04155; Sat, 30 May 1998 07:00:01 +0200 (MET DST) Message-ID: <19980530070000.29794@follo.net> Date: Sat, 30 May 1998 07:00:00 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <19980530060008.33353@follo.net> <17587.896504155@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <17587.896504155@time.cdrom.com>; from Jordan K. Hubbard on Fri, May 29, 1998 at 09:55:55PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, May 29, 1998 at 09:55:55PM -0700, Jordan K. Hubbard wrote: > > Allowing mknod on a devfs would be somewhat akin to pointing an Uzi at > > your foot and playing with how close to the actual trig limit you can > > pull the trigger without firing. > > Naw, nothing so dire. Backwards compatability doesn't always have to > be asthetically pleasing, it just has to work and for a reasonable > period of time until people have made the transition. If we're talking a true mknod, I still stand by the comment. If we're talking a compatibility hack that look like mknod, that's another cup of tea, and one which I just sent three ways of 'solving'. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 22:01:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18727 for freebsd-current-outgoing; Fri, 29 May 1998 22:01:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ConSys.COM ([209.141.107.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18699 for ; Fri, 29 May 1998 22:01:15 -0700 (PDT) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (ip-17-235.prc.primenet.com [207.218.17.235]) by ConSys.COM (8.8.6/8.8.6) with ESMTP id WAA17779; Fri, 29 May 1998 22:01:07 -0700 (MST) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.8.8/8.8.7) with ESMTP id VAA01116; Fri, 29 May 1998 21:59:17 -0700 (MST) Message-Id: <199805300459.VAA01116@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: joelh@gnu.org, eivind@yes.no, rnordier@nordier.com, current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning In-reply-to: Your message of "Fri, 29 May 1998 21:20:43 GMT." <199805292120.OAA14978@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 21:59:17 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Well, here are a couple of points: > > > * License > > > > I'll assume that TenDRA and XANDF are both BSD-license? > > Yes. > > > > * General quality of system (GCC is written under the paradigm 'learn > > > writing compilers as we go') > > > > I can't comment on that one, not having examined the source code to > > the various compilers. But are the others written by professional > > compiler writers? > > Yes. Under denfense contract. As someone who is currently billing hours to the U.S. DoD by using ACE on FreeBSD, let me underscore the tenous nature of defense projects. I don't think this aspect has been sufficiently considered. TenDRA looks to be another of those interesting singularities that occur with modest frequency whenever sufficient funding&&complacency in oversight&&sufficient intellectual force is displayed by the P.I. Examples in the U.S. abound, two U.S. Gov (not DoD) projects perhaps familiar (to this list) are the current NASA NetBSD networking and storage projects, and Beowulf. I doubt seriously HMS "DoD" is any different. Easy come. Easy go. Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 22:03:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19204 for freebsd-current-outgoing; Fri, 29 May 1998 22:03:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19190 for ; Fri, 29 May 1998 22:03:22 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id WAA17658; Fri, 29 May 1998 22:03:41 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Eivind Eklund cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 07:00:00 +0200." <19980530070000.29794@follo.net> Date: Fri, 29 May 1998 22:03:41 -0700 Message-ID: <17654.896504621@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If we're talking a true mknod, I still stand by the comment. If we're > talking a compatibility hack that look like mknod, that's another cupe I don't see the difference in relation to devfs? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 22:12:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20230 for freebsd-current-outgoing; Fri, 29 May 1998 22:12:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20196 for ; Fri, 29 May 1998 22:12:01 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id NAA20017; Sat, 30 May 1998 13:11:30 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805300511.NAA20017@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 20:52:01 MST." <17374.896500321@time.cdrom.com> Date: Sat, 30 May 1998 13:11:29 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > E.g. I can shoot my foot off, but I can't sew it back on. :-) > > > > Yes, you can. You can mount another devfs and 'mv' a device from it > > (or at least that's the way the specs read - I don't have devfs > > enabled right now, so I can't test). > > That's utterly rude. :-) > > I hope you're not implying that this is going to be the accepted way > for doing this in the future as well. Non-persistence is a big enough > violation of POLA as it is, and not even being able to do mknod(2) > operations on a devfs to replace missing entries would be a POLA > catastrophe. Remember this is merely step 1. The Plan is to eventually replace minor/ major devices completely so that the filesystem interface will probably be through a 32 bit vnode pointer or something along those lines. Doing a mknod will be practically impossible. (This has some major benefits but will be a major change in the driver/kernel/fs interface. Drivers won't have a major/minor number anymore, they'll just have a unit number.. specfs will either be gone or won't resemble anything like it does now, and will probably hang off devfs instead. For the problem at hand though, I once suggested to Julian that we use undelete(2) to make files come back. "rm -W bpf4" could almost work as is, except that it wants to stat the file and look for whiteout flags first and 'rm' doesn't create a whiteout in devfs. (This might be an interesting approach to the problem if all unlinks caused a whiteout instead of the node disappearing entirely.) > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 22:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21082 for freebsd-current-outgoing; Fri, 29 May 1998 22:19:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles135.castles.com [208.214.165.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21076 for ; Fri, 29 May 1998 22:19:10 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA00432; Fri, 29 May 1998 21:14:32 -0700 (PDT) Message-Id: <199805300414.VAA00432@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 20:52:01 PDT." <17374.896500321@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 21:14:32 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > E.g. I can shoot my foot off, but I can't sew it back on. :-) > > > > Yes, you can. You can mount another devfs and 'mv' a device from it > > (or at least that's the way the specs read - I don't have devfs > > enabled right now, so I can't test). > > That's utterly rude. :-) > > I hope you're not implying that this is going to be the accepted way > for doing this in the future as well. Non-persistence is a big enough > violation of POLA as it is, and not even being able to do mknod(2) > operations on a devfs to replace missing entries would be a POLA > catastrophe. You could make a strong case for having mknod ignore the (dev) argument and just look the name up in the reference devfs copy, and then duplicate it at the path given (presuming that's inside a devfs). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 22:23:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21681 for freebsd-current-outgoing; Fri, 29 May 1998 22:23:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21676 for ; Fri, 29 May 1998 22:23:48 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id XAA02620; Fri, 29 May 1998 23:19:38 -0600 (MDT) Date: Fri, 29 May 1998 23:19:38 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199805300519.XAA02620@narnia.plutotech.com> To: Doug Rabson cc: current@FreeBSD.ORG Subject: Re: FreeBSD/alpha status report (2) User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Along the way, I have successfully probed for simulated devices on a > simulated PCI bus and attached simulated SCSI disks :-). I am *not* > currently using NetBSD's bus_space stuff to handle accesses to device i/o > ports and memory. Given that 99% of the machines that the port will work > on don't need the complexity of bus_space, I have taken the Linux route > and each chipset will supply versions of inb etc which perform the > relavent contortions. I suppose I don't understand the rational here. The i386 port doesn't have to go through any contortions in it's bus space implemenation and implementing bus space for FreeBSD x86 (look in i386/include/bus.h) was *trivial*. So why not use bus space? The CAM drivers already use it, you say that 99% of Alphas can use a "simple" implementation, and it buys us the ability to more easily port code from NetBSD? Just because you seem to believe that NetBSD's implementation of the bus space and bus DMA interfaces for Alpha are overly complex, doesn't mean that the interfaces themselves are a bad idea. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 22:25:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21983 for freebsd-current-outgoing; Fri, 29 May 1998 22:25:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21965 for ; Fri, 29 May 1998 22:25:37 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id WAA22013; Fri, 29 May 1998 22:25:45 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 21:14:32 PDT." <199805300414.VAA00432@antipodes.cdrom.com> Date: Fri, 29 May 1998 22:25:44 -0700 Message-ID: <21984.896505944@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You could make a strong case for having mknod ignore the (dev) argument > and just look the name up in the reference devfs copy, and then > duplicate it at the path given (presuming that's inside a devfs). Well, the way I figured it, devfs is going to have a mechanism for creating aliases anyway (for ln and friends), so an attempt to mknod something would result in devfs doing a reverse-lookup on the major/minor pair and creating an alias for the entry found. If none is found at all, you treat the mknod as a bogus operation and punt it. At last, a version of mknod which checks all of its arguments! :-) :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 22:39:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23898 for freebsd-current-outgoing; Fri, 29 May 1998 22:39:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23890 for ; Fri, 29 May 1998 22:39:17 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA09294; Fri, 29 May 1998 22:39:01 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805300539.WAA09294@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Richard Cownie cc: Mike Smith , jak@cetlink.net, current@FreeBSD.ORG Subject: Re: FreeBSD on 8-way SMP PPro In-reply-to: Your message of "Fri, 29 May 1998 11:51:47 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 22:39:01 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This sounds like a wonderful FreeBSD news update for http://www.freebsd.org We really need that a news sticker style or something up at www.freebsd.org Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 22:42:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24424 for freebsd-current-outgoing; Fri, 29 May 1998 22:42:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles135.castles.com [208.214.165.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24410 for ; Fri, 29 May 1998 22:42:42 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id VAA00666; Fri, 29 May 1998 21:38:19 -0700 (PDT) Message-Id: <199805300438.VAA00666@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Mike Smith , Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 22:25:44 PDT." <21984.896505944@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 21:38:19 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You could make a strong case for having mknod ignore the (dev) argument > > and just look the name up in the reference devfs copy, and then > > duplicate it at the path given (presuming that's inside a devfs). > > Well, the way I figured it, devfs is going to have a mechanism for > creating aliases anyway (for ln and friends), so an attempt to mknod > something would result in devfs doing a reverse-lookup on the > major/minor pair and creating an alias for the entry found. If none > is found at all, you treat the mknod as a bogus operation and punt it. Uh, doing a reverse lookup on the major/minor pair would be pretty unuseful. If you've just deleted the device, you have no idea what it's (dev) is, so you can't possibly supply them as arguments. If/When dev_t finally disappears, this won't even be feasible. The only useful way to do it is to recover something by its original name. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 23:01:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27298 for freebsd-current-outgoing; Fri, 29 May 1998 23:01:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27283 for ; Fri, 29 May 1998 23:01:09 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id PAA17644; Sat, 30 May 1998 15:30:46 +0930 (CST) (envelope-from grog) Message-ID: <19980530153046.E20360@freebie.lemis.com> Date: Sat, 30 May 1998 15:30:46 +0930 From: Greg Lehey To: Peter Wemm , "Jordan K. Hubbard" Cc: Eivind Eklund , current@FreeBSD.ORG Subject: Creating/deleting devfs nodes (was: I see one major problem with DEVFS...) References: <17374.896500321@time.cdrom.com> <199805300511.NAA20017@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805300511.NAA20017@spinner.netplex.com.au>; from Peter Wemm on Sat, May 30, 1998 at 01:11:29PM +0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 May 1998 at 13:11:29 +0800, Peter Wemm wrote: > For the problem at hand though, I once suggested to Julian that we use > undelete(2) to make files come back. "rm -W bpf4" could almost work as is, > except that it wants to stat the file and look for whiteout flags first and > 'rm' doesn't create a whiteout in devfs. (This might be an interesting > approach to the problem if all unlinks caused a whiteout instead of the > node disappearing entirely.) I don't really understand this. 1. Why should it be possible to delete a device node from devfs? It shouldn't be possible to remove individual nodes without removing their functionality. rm isn't the right tool to do that, and I'd consider it a bug to allow it. 2. If for some reason (including explicit disabling, or unloading of an LKM), a device node *does* disappear, the obvious tool for reconstruct it is the device driver. If you need to do this, something akin to camcontrol's rescan function is what you need. In the case of an LKM device driver, the driver should always create its nodes when it starts. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 23:25:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00311 for freebsd-current-outgoing; Fri, 29 May 1998 23:25:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00302 for ; Fri, 29 May 1998 23:25:53 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id XAA29540; Fri, 29 May 1998 23:26:02 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 21:38:19 PDT." <199805300438.VAA00666@antipodes.cdrom.com> Date: Fri, 29 May 1998 23:26:02 -0700 Message-ID: <29532.896509562@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Uh, doing a reverse lookup on the major/minor pair would be pretty > unuseful. If you've just deleted the device, you have no idea what > it's (dev) is, so you can't possibly supply them as arguments. Eh? You still have an instance in your "template" mount that you can match up. I also _know_ that majors and minors are going away - I'm not trying to argue for their long-term preservation, simply that they continue to have as much "meaning" as possible during the transition period (which I would expect to last as long as 1 maybe 2 years before people are entirely accustomed to the new model). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 23:35:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01419 for freebsd-current-outgoing; Fri, 29 May 1998 23:35:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles135.castles.com [208.214.165.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01398 for ; Fri, 29 May 1998 23:35:50 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA00926; Fri, 29 May 1998 22:31:22 -0700 (PDT) Message-Id: <199805300531.WAA00926@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Mike Smith , Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 23:26:02 PDT." <29532.896509562@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 22:31:21 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Uh, doing a reverse lookup on the major/minor pair would be pretty > > unuseful. If you've just deleted the device, you have no idea what > > it's (dev) is, so you can't possibly supply them as arguments. > > Eh? You still have an instance in your "template" mount that you can > match up. I also _know_ that majors and minors are going away - I'm > not trying to argue for their long-term preservation, simply that they > continue to have as much "meaning" as possible during the transition > period (which I would expect to last as long as 1 maybe 2 years before > people are entirely accustomed to the new model). Yes, but you can't *look*at* the template mount to find out what these numbers *are*. As a user, if I have just nuked /dev/foo0, what I am going to want to do is "mknod /dev/foo0 ". My suggestion was simply that the name /dev/foo0 contains everything that's required to reconstruct the node, providing you haven't done something smart like renaming it. ie. you could only mknod "original" devices. As an alternative, whiteout support might be better, although I don't think that many people are familiar with whiteouts. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 23:40:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01846 for freebsd-current-outgoing; Fri, 29 May 1998 23:40:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles135.castles.com [208.214.165.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01841 for ; Fri, 29 May 1998 23:40:03 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA00954; Fri, 29 May 1998 22:34:47 -0700 (PDT) Message-Id: <199805300534.WAA00954@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: Peter Wemm , "Jordan K. Hubbard" , Eivind Eklund , current@FreeBSD.ORG Subject: Re: Creating/deleting devfs nodes (was: I see one major problem with DEVFS...) In-reply-to: Your message of "Sat, 30 May 1998 15:30:46 +0930." <19980530153046.E20360@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 22:34:47 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 30 May 1998 at 13:11:29 +0800, Peter Wemm wrote: > > For the problem at hand though, I once suggested to Julian that we use > > undelete(2) to make files come back. "rm -W bpf4" could almost work as is, > > except that it wants to stat the file and look for whiteout flags first and > > 'rm' doesn't create a whiteout in devfs. (This might be an interesting > > approach to the problem if all unlinks caused a whiteout instead of the > > node disappearing entirely.) > > I don't really understand this. > > 1. Why should it be possible to delete a device node from devfs? It > shouldn't be possible to remove individual nodes without removing > their functionality. rm isn't the right tool to do that, and I'd > consider it a bug to allow it. There is an argument that suggests that this can be used to enhance security, eg. in chroot-jail duplicate devfs mounts. > 2. If for some reason (including explicit disabling, or unloading of > an LKM), a device node *does* disappear, the obvious tool for > reconstruct it is the device driver. If you need to do this, > something akin to camcontrol's rescan function is what you need. > In the case of an LKM device driver, the driver should always > create its nodes when it starts. If a node is removed from a mounted devfs, the driver is not impacted - it will have copies of this node in other devfs instances including the invisible "master" instance inside the kernel. The easiest way to "resurrect" a node is to simply duplicate the original from the "master". -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 23:44:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02433 for freebsd-current-outgoing; Fri, 29 May 1998 23:44:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02383 for ; Fri, 29 May 1998 23:44:24 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id QAA20273; Sat, 30 May 1998 16:13:49 +0930 (CST) (envelope-from grog) Message-ID: <19980530161349.F20360@freebie.lemis.com> Date: Sat, 30 May 1998 16:13:49 +0930 From: Greg Lehey To: Mike Smith Cc: Peter Wemm , "Jordan K. Hubbard" , Eivind Eklund , current@FreeBSD.ORG Subject: Re: Creating/deleting devfs nodes (was: I see one major problem with DEVFS...) References: <19980530153046.E20360@freebie.lemis.com> <199805300534.WAA00954@antipodes.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199805300534.WAA00954@antipodes.cdrom.com>; from Mike Smith on Fri, May 29, 1998 at 10:34:47PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 May 1998 at 22:34:47 -0700, Mike Smith wrote: >> On Sat, 30 May 1998 at 13:11:29 +0800, Peter Wemm wrote: >>> For the problem at hand though, I once suggested to Julian that we use >>> undelete(2) to make files come back. "rm -W bpf4" could almost work as is, >>> except that it wants to stat the file and look for whiteout flags first and >>> 'rm' doesn't create a whiteout in devfs. (This might be an interesting >>> approach to the problem if all unlinks caused a whiteout instead of the >>> node disappearing entirely.) >> >> I don't really understand this. >> >> 1. Why should it be possible to delete a device node from devfs? It >> shouldn't be possible to remove individual nodes without removing >> their functionality. rm isn't the right tool to do that, and I'd >> consider it a bug to allow it. > > There is an argument that suggests that this can be used to enhance > security, eg. in chroot-jail duplicate devfs mounts. I think you need to be more specific. I can see a number of things that you might mean here. What's wrong with setting the permissions of the nodes? That shouldn't be impacted by devfs. >> 2. If for some reason (including explicit disabling, or unloading of >> an LKM), a device node *does* disappear, the obvious tool for >> reconstruct it is the device driver. If you need to do this, >> something akin to camcontrol's rescan function is what you need. >> In the case of an LKM device driver, the driver should always >> create its nodes when it starts. > > If a node is removed from a mounted devfs, the driver is not impacted - > it will have copies of this node in other devfs instances including > the invisible "master" instance inside the kernel. That's an assumption. The way I stated it, it would be incorrect. > The easiest way to "resurrect" a node is to simply duplicate the > original from the "master". The real question is what the device nodes are for. If they're supposed to be an accurate reflection of the device driver's capabilities (my premise), this wouldn't make sense. If they're supposed to provide access to the device driver (your apparent premise), that's fine. But then we don't really need devfs, we can use the current method. BTW, vinum creates its own device nodes when it's started. Does anybody have any comments on this? Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 23:57:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04537 for freebsd-current-outgoing; Fri, 29 May 1998 23:57:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles135.castles.com [208.214.165.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04524 for ; Fri, 29 May 1998 23:57:43 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA01042; Fri, 29 May 1998 22:53:02 -0700 (PDT) Message-Id: <199805300553.WAA01042@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Greg Lehey cc: Mike Smith , Peter Wemm , "Jordan K. Hubbard" , Eivind Eklund , current@FreeBSD.ORG Subject: Re: Creating/deleting devfs nodes (was: I see one major problem with DEVFS...) In-reply-to: Your message of "Sat, 30 May 1998 16:13:49 +0930." <19980530161349.F20360@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 22:53:02 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> 1. Why should it be possible to delete a device node from devfs? It > >> shouldn't be possible to remove individual nodes without removing > >> their functionality. rm isn't the right tool to do that, and I'd > >> consider it a bug to allow it. > > > > There is an argument that suggests that this can be used to enhance > > security, eg. in chroot-jail duplicate devfs mounts. > > I think you need to be more specific. I can see a number of things > that you might mean here. What's wrong with setting the permissions > of the nodes? That shouldn't be impacted by devfs. It's impacted by devfs insofar as it's devfs that retains the nodes. As for why changing permissions isn't enough, you'll have to talk to someone else about that. I don't feel adequately passionate about how closely devfs has to cleave to "normal" file semantics. > >> 2. If for some reason (including explicit disabling, or unloading of > >> an LKM), a device node *does* disappear, the obvious tool for > >> reconstruct it is the device driver. If you need to do this, > >> something akin to camcontrol's rescan function is what you need. > >> In the case of an LKM device driver, the driver should always > >> create its nodes when it starts. > > > > If a node is removed from a mounted devfs, the driver is not impacted - > > it will have copies of this node in other devfs instances including > > the invisible "master" instance inside the kernel. > > That's an assumption. The way I stated it, it would be incorrect. It's a statement of fact based on the model to which DEVFS adheres and its implementation. There is no facility for reflexiveness in the node instantiation, and MHO is that it would be an extremely difficult path to follow. > > The easiest way to "resurrect" a node is to simply duplicate the > > original from the "master". > > The real question is what the device nodes are for. If they're > supposed to be an accurate reflection of the device driver's > capabilities (my premise), this wouldn't make sense. If they're > supposed to provide access to the device driver (your apparent > premise), that's fine. But then we don't really need devfs, we can > use the current method. I fear I have no idea what you mean by the device node "being an accurate reflection of the device driver's capabilities". A device node is an access method. The current (static) device node population process is less than adequate for this. > BTW, vinum creates its own device nodes when it's started. Does > anybody have any comments on this? Is this the driver doing the work, or an administrative program? How can you presume that / is read/write when vinum starts? How can you presume that the device nodes should be in /dev? What if someone wants the device nodes in a chrooted tree? What if someone doesn't want all the device nodes present? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri May 29 23:58:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04715 for freebsd-current-outgoing; Fri, 29 May 1998 23:58:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04710 for ; Fri, 29 May 1998 23:58:21 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id XAA02871; Fri, 29 May 1998 23:58:31 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 22:31:21 PDT." <199805300531.WAA00926@antipodes.cdrom.com> Date: Fri, 29 May 1998 23:58:30 -0700 Message-ID: <2867.896511510@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, but you can't *look*at* the template mount to find out what these > numbers *are*. Why *not*? :-) If the devfs subsystem gets a mount request to go instantiate cdev foo0 with 1/12, you still have a pointer to your "invisible master" containing its own list of devices, one of which, I'd hope, would have a major/minor of 1/12. What's to stop you from then cloning the entry back over? I'm also not *against* matching on names, that's fine, I'm simply arguing that we can never really know just what kinds of custom sysadmin tools are out there, and if we're handed a request through mknod(2) for something which used to work, we should probably try and make it continue to work so that this tool doesn't suddenly break the day we throw the switch to devfs. This isn't as rare a scenario as one might think, either, our very own dear sysinstall having *mucho* internal knowledge of major/minor values and the devices they represent. Sure, I'll change sysinstall or its replacement well before the time comes because I will be well warned, but not everyone keeps that closely up to date on our progress and I can well imagine other tools, some perhaps even derived from sysinstall, out there doing overly incestuous things with major/minor numbers which will need more time to make the transition. Implementing backwards-compatibility directly at the mknod(2) level means we don't have to even think about how people might be abusing things in system applications, they'll Just Work for whatever set of dev_t assignments we last had before devfs replaced it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 00:06:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05680 for freebsd-current-outgoing; Sat, 30 May 1998 00:06:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk ([195.8.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05655 for ; Sat, 30 May 1998 00:06:36 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id JAA15403; Sat, 30 May 1998 09:04:40 +0200 (CEST) To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 18:08:16 PDT." <199805300108.SAA16711@time.cdrom.com> Date: Sat, 30 May 1998 09:04:38 +0200 Message-ID: <15401.896511878@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199805300108.SAA16711@time.cdrom.com>, "Jordan K. Hubbard" writes: >bash# ls -l bpf* >crw------- 1 root wheel 23, 0 May 29 08:03 bpf0 >crw------- 1 root wheel 23, 1 May 29 08:03 bpf1 >crw------- 1 root wheel 23, 2 May 29 08:03 bpf2 >crw------- 1 root wheel 23, 3 May 29 08:03 bpf4 >bash# rm bpf4 >bash# ls -l bpf* >crw------- 1 root wheel 23, 0 May 29 08:03 bpf0 >crw------- 1 root wheel 23, 1 May 29 08:03 bpf1 >crw------- 1 root wheel 23, 2 May 29 08:03 bpf2 >bash# mknod bpf4 c 23 3 > >E.g. I can shoot my foot off, but I can't sew it back on. :-) The logical thing would be for "undelete" to work here... Have you tried that ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 00:10:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06328 for freebsd-current-outgoing; Sat, 30 May 1998 00:10:31 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05973; Sat, 30 May 1998 00:09:02 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Sat, 30 May 1998 03:08:26 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAE8@freya.circle.net> From: tcobb To: "'shimon@simon-shapiro.org'" Cc: "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" Subject: DPT Redux Date: Sat, 30 May 1998 03:08:21 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I won't respond to each of Simon's many emails over the past 24 hours, simply because most of them were out-of-context reactions to a thread that grew from my original DPT post yesterday. Instead, I think that the most productive thing is to provide a bit more of the information requested. The system is using a single PM3334UW/2 with drives configured in the following logical arrays: 2 1GB drives as RAID-1 (sd0) 7 4GB drives as RAID-5 (sd1) 1 4GB hot swap Event #1: 1 of the RAID-5 drives fails, DPT hardware begins to auto-rebuild with the hot swap drive DPT driver freezes access to sd1, system remains running but access to sd1 hangs I shutdown and rebooted machine (SYNC failed on shutdown) Allowed FreeBSD to boot, it returned the following for sd1 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 0MB (1 512 byte sectors) Then, system continued booting and finally panic'd with a "Page Fault in Supervisor Mode" error prior to mounting drives. I then booted the system with a DOS floppy, used DPTmgr to examine array. The array was complete, but in degraded mode. It had begun rebuilding itself, which specs say can happen in the background while other accesses are going on. I tested redundancy info on the array AND tested random reads on the array -- all succeeded. So, I exited DPTmgr, and tried booting back to FreeBSD, same problem as above occurred (0MB 1 sector, panic). Then, I rebooted into DOS and let the DPT card run its rebuild from there. It completed about 1.5 hours later, and showed the array optimal. I then rebooted into FreeBSD which showed the correct info again. Event #2: This was the next day. Hard drive fails in array (this was the ex-hot swap from above). This leaves the array with no hotswap to insert, but no data lost. The array is now again in degraded mode. The card screams bloody murder. HOWEVER, the DPT driver does NOT hang on access to the sd1 partition. I successfully shutdown the machine (SYNC succeeded this time). I insert a new harddrive into the array so that the DPT hardware will begin rebuilding with this new drive. On reboot, FreeBSD showed the same results as above (0MB, 1 sector, panic). Rebooting back to DOS and running DPTmgr showed that the array was in degraded mode, but that no data was lost and that redundancy information was all there. It automatically began rebuilding with the new drive. I tested rebooting into FreeBSD, same results (0/1/panic). Rebooted back to DOS, allowed the hardware to finish its rebuild (1.5 hours), rebooted to FreeBSD and it showed the correct results. So, here's the summary for those of you who've stayed with me. With RAID-5 and a HOT SWAP drive, a single drive failure caused the DPT driver in FreeBSD to hang on access to the partition. This appears to be because DPT was doing a background rebuild automatically. With RAID-5 and NO hot swap drive, a single drive failure does NOT cause the DPT driver in FreeBSD to hang on access to the partition. This appears to be because DPT was NOT doing a background rebuild -- there being no drives to rebuild into. With RAID-5 and a new drive to rebuild on, the DPT hardware begins automatic rebuilds of the array. However, in these conditions the DPT driver (or other FreeBSD component) does not correctly sense the size information and panics the kernel during bootup. This symptom goes away after the rebuild is complete. This symptom does not appear when in DOS under the same circumstances. DOS DPTmgr checks show the array of the correct size. BIOS bootup screen for DPT shows the array of the correct size. The super-summary is that it appears the the DPT driver or other FreeBSD code component is not correctly coordinating with the DPT hardware (or sensing status properly) when the DPT hardware is doing a background rebuild of the array. This array has been running non-stop since November 1997. Cabling is good. Active terminators and custom cables created by Granite are used. Seagate and Micropolis drives are used. The RAID-5 array is in an external rackmount case. -Troy Cobb Circle Net, Inc. http://www.circle.net Here's the dmesg ouput, trimmed to show relevant data. FreeBSD 3.0-CURRENT #0: Sun May 24 04:30:04 EDT 1998 root@kali.circle.net:/usr/src/sys/compile/BENZAITEN-4 CPU: Pentium (232.67-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 134217728 (131072K bytes) avail memory = 128147456 (125144K bytes) DEVFS: ready for devices DPT: RAID Manager driver, Version 1.0.5 Probing for devices on PCI bus 0: DPT: PCI SCSI HBA Driver, version 1.4.2 chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 dpt0: rev 0x02 int a irq 9 on pci0.20.0 dpt0: DPT type 3, model PM3334UW firmware 07M0, Protocol 0 on port 6310 with Write-Back cache. LED = 0000 0000 dpt0: Enabled Options: Recover Lost Interrupts Collect Metrics Optimize CPU Cache dpt0: waiting for scsi devices to settle scbus0 at dpt0 bus 0 dpt0: Initializing Lost IRQ Timer sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 1029MB (2109328 512 byte sectors) dpt0: waiting for scsi devices to settle scbus1 at dpt0 bus 1 sd1 at scbus1 target 2 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 20503MB (41990720 512 byte sectors) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 00:11:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06390 for freebsd-current-outgoing; Sat, 30 May 1998 00:11:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk ([195.8.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06383 for ; Sat, 30 May 1998 00:11:39 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id JAA15538; Sat, 30 May 1998 09:10:12 +0200 (CEST) To: Eivind Eklund cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 06:55:08 +0200." <19980530065508.30647@follo.net> Date: Sat, 30 May 1998 09:10:11 +0200 Message-ID: <15536.896512211@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19980530065508.30647@follo.net>, Eivind Eklund writes: >On Fri, May 29, 1998 at 08:52:01PM -0700, Jordan K. Hubbard wrote: >> > > E.g. I can shoot my foot off, but I can't sew it back on. :-) >> > >> > Yes, you can. You can mount another devfs and 'mv' a device from it >> > (or at least that's the way the specs read - I don't have devfs >> > enabled right now, so I can't test). >> >> That's utterly rude. :-) >> >> I hope you're not implying that this is going to be the accepted way >> for doing this in the future as well. Non-persistence is a big enough >> violation of POLA as it is, and not even being able to do mknod(2) >> operations on a devfs to replace missing entries would be a POLA >> catastrophe. > >OK, this can be solved in at least these three ways (neither of which >are pretty): The POLA way is: (4) use undelete(2) for what it is intended to do. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 00:13:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06587 for freebsd-current-outgoing; Sat, 30 May 1998 00:13:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06581 for ; Sat, 30 May 1998 00:13:18 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id IAA01776; Sat, 30 May 1998 08:16:02 +0100 (BST) Date: Sat, 30 May 1998 08:16:02 +0100 (BST) From: Doug Rabson To: "Justin T. Gibbs" cc: current@FreeBSD.ORG Subject: Re: FreeBSD/alpha status report (2) In-Reply-To: <199805300519.XAA02620@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 29 May 1998, Justin T. Gibbs wrote: > > Along the way, I have successfully probed for simulated devices on a > > simulated PCI bus and attached simulated SCSI disks :-). I am *not* > > currently using NetBSD's bus_space stuff to handle accesses to device i/o > > ports and memory. Given that 99% of the machines that the port will work > > on don't need the complexity of bus_space, I have taken the Linux route > > and each chipset will supply versions of inb etc which perform the > > relavent contortions. > > I suppose I don't understand the rational here. The i386 port > doesn't have to go through any contortions in it's bus space > implemenation and implementing bus space for FreeBSD x86 (look in > i386/include/bus.h) was *trivial*. So why not use bus space? The > CAM drivers already use it, you say that 99% of Alphas can use a > "simple" implementation, and it buys us the ability to more easily > port code from NetBSD? Just because you seem to believe that NetBSD's > implementation of the bus space and bus DMA interfaces for Alpha are > overly complex, doesn't mean that the interfaces themselves are a > bad idea. I am not saying that there won't be a . I am saying that I don't think that all the chipset implementations need to implement it. If I do a bus_space interface, I expect that it will be something like i386/include/bus.h. It is possible that TurboChannel and TurboLaser boxes with multiple PCI busses might provide their own implementation rather than the generic one. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 00:17:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07554 for freebsd-current-outgoing; Sat, 30 May 1998 00:17:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07498; Sat, 30 May 1998 00:16:23 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Sat, 30 May 1998 03:15:46 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAE9@freya.circle.net> From: tcobb To: "'shimon@simon-shapiro.org'" , "'freebsd-scsi@freebsd.org'" Cc: "freebsd-current@freebsd.org" , Karl Pielorz Subject: RE: DPT driver fails and panics with Degraded Array Date: Sat, 30 May 1998 03:15:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Simon Shapiro [mailto:shimon@simon-shapiro.org] [SNIP] > At this point, the load on > the system will > reach 140-400 (we run the tests against RAID-0 and RAID-1, the > performance differs) >From my quick review of the replies of FreeBSD DPT RAID users, all of them appear to be using their arrays in RAID-0 or RAID-1 configurations. According to Simon's test procedure for his releases (portion copied above), he too only uses the DPT RAID-0 and RAID-1 features. In my setup, I'm using both RAID-5 and RAID-1. I have yet to have a drive failure on the RAID-1 array (*knock on wood*), the problems I saw were with the RAID-5 array and rebuilds. *PERHAPS* the key point is that the driver developer hasn't tested the FreeBSD DPT driver with a RAID-5 array. Perhaps not. What is clear from my prior post (the really long one) is that in my configuration the DPT driver or some other FreeBSD software component does not correctly deal with the DPT hardware doing a background rebuild. I'm going to try to obtain another DPT card and setup another small array for further testing. -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 00:26:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09015 for freebsd-current-outgoing; Sat, 30 May 1998 00:26:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09004 for ; Sat, 30 May 1998 00:26:09 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA15994; Sat, 30 May 1998 00:23:40 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 09:04:38 +0200." <15401.896511878@critter.freebsd.dk> Date: Sat, 30 May 1998 00:23:40 -0700 Message-ID: <15986.896513020@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The logical thing would be for "undelete" to work here... Assuming removals became whiteouts, yes. The only fs I know which currently does that is unionfs, however. > Have you tried that ? See above - what good would that do? :) I even tried it with unionfs, just for grins, and it wouldn't allow me to change anything at all. :) Oh yeah, Eivind: I also tried the mv trick, mounting the 2nd instance and then moving a file over? Works great, but with an unforseen side-effect: You can't unmount the 2nd filesystem instance after that. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 00:31:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09853 for freebsd-current-outgoing; Sat, 30 May 1998 00:31:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles135.castles.com [208.214.165.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09848 for ; Sat, 30 May 1998 00:31:13 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA01190; Fri, 29 May 1998 23:26:48 -0700 (PDT) Message-Id: <199805300626.XAA01190@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Mike Smith , Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 23:58:30 PDT." <2867.896511510@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 May 1998 23:26:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Yes, but you can't *look*at* the template mount to find out what these > > numbers *are*. > > Why *not*? :-) Because it ain't mounted anyhere. Think: user says: # rm /dev/foo0 # mknod /dev/foo0 c ??? What are they going to supply for the dev_t? The numbers are dynamic, so there's no possible reference to them. Even if they weren't, there's no guarantee they'd be able to guess them anyway. > I'm also not *against* matching on names, that's fine, I'm simply > arguing that we can never really know just what kinds of custom > sysadmin tools are out there, and if we're handed a request through > mknod(2) for something which used to work, we should probably try and > make it continue to work so that this tool doesn't suddenly break the > day we throw the switch to devfs. Sure. But it's not useful to try to do anything with the major/minor pairs. They don't have any constant meaning; it's the name that's relevant. If in the "transition period" you want to verify that the name and dev match, that's fair enough, but I don't think it's worth encouraging. Yes, if you're the sort of person that renames all their devices as a matter of course, this is going to catch you out. I can't say that's such a bad thing. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 00:51:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13010 for freebsd-current-outgoing; Sat, 30 May 1998 00:51:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13001 for ; Sat, 30 May 1998 00:51:13 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id AAA29816; Sat, 30 May 1998 00:50:29 -0700 (PDT) Message-Id: <199805300750.AAA29816@implode.root.com> To: Greg Lehey cc: Peter Wemm , "Jordan K. Hubbard" , Eivind Eklund , current@FreeBSD.ORG Subject: Re: Creating/deleting devfs nodes (was: I see one major problem with DEVFS...) In-reply-to: Your message of "Sat, 30 May 1998 15:30:46 +0930." <19980530153046.E20360@freebie.lemis.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 30 May 1998 00:50:29 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Sat, 30 May 1998 at 13:11:29 +0800, Peter Wemm wrote: >> For the problem at hand though, I once suggested to Julian that we use >> undelete(2) to make files come back. "rm -W bpf4" could almost work as is, >> except that it wants to stat the file and look for whiteout flags first and >> 'rm' doesn't create a whiteout in devfs. (This might be an interesting >> approach to the problem if all unlinks caused a whiteout instead of the >> node disappearing entirely.) > >I don't really understand this. > >1. Why should it be possible to delete a device node from devfs? It > shouldn't be possible to remove individual nodes without removing > their functionality. rm isn't the right tool to do that, and I'd > consider it a bug to allow it. Yeah, people should use the file permissions to deny access to a device, not rm. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 00:54:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA13581 for freebsd-current-outgoing; Sat, 30 May 1998 00:54:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13564 for ; Sat, 30 May 1998 00:54:18 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id AAA04009; Sat, 30 May 1998 00:54:25 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Fri, 29 May 1998 23:26:48 PDT." <199805300626.XAA01190@antipodes.cdrom.com> Date: Sat, 30 May 1998 00:54:25 -0700 Message-ID: <4005.896514865@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Because it ain't mounted anyhere. Think: user says: > > # rm /dev/foo0 > > # mknod /dev/foo0 c ??? > > What are they going to supply for the dev_t? The numbers are dynamic, > so there's no possible reference to them. Even if they weren't, > there's no guarantee they'd be able to guess them anyway. 1. Of course the numbers aren't dynamic - for backwards-compatibility to even begin to work at the mknod-level, you'd have to preserve the old assignments. 2. The mknod operation may be done by something like sysinstall or even the old MAKEDEV script - the user doesn't necessarily have to know, it just needs to work even if the script is creating some custom set of aliases, like "/dev/floppy" or "/dev/cdrom", etc. That's why I'm sticking so stubbornly to the idea of preserving any residual meaning for major/minors at all. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 03:49:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28224 for freebsd-current-outgoing; Sat, 30 May 1998 03:49:49 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA28217 for ; Sat, 30 May 1998 03:49:46 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 26619 invoked by uid 100); 30 May 1998 10:50:37 -0000 Message-ID: <19980530035034.A26571@top.worldcontrol.com> Date: Sat, 30 May 1998 03:50:34 -0700 To: freebsd-current@FreeBSD.ORG Cc: toor@dyson.iquest.net Subject: Panic: SMP, CAM, Dyson SMP patches Mail-Followup-To: freebsd-current@freebsd.org, toor@dyson.iquest.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 3.0-CURRENT #2: Fri May 29 12:45:20 PDT 1998 with CAM, and Dyson's 26.may SMP patches. It panic'ed during a 'make -j 8 buildworld' pretty near the end. It did not panic during two 'make -j 4 buildworld's. I'm also quite suspicious of these silo overflow messages. They only occur with a kernel running the Dyson SMP patches. ... May 30 02:11:18 bls2 /kernel: sio1: 1 more silo overflow (total 33) May 30 02:32:16 bls2 /kernel: sio1: 1 more silo overflow (total 34) May 30 03:08:43 bls2 /kernel: sio1: 1 more silo overflow (total 35) Fatal trap 12: page fault while in kernel mode mp_lock = 01000003; cpuid = 1; lapic.id = 00000000 fault virtual address = 0xffffff8e fault code = supervisor write, page not present instruction pointer = 0x8:0xf4c53c5b stack pointer = 0x10:0xf4c53c2c frame pointer = 0x10:0xf4c53c48 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 9871 (make) interrupt mask = <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000003; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... regretably I had the kernel in DDB_UNATTENDED, rather than DDB and the system froze after syncing disks... Why am I not getting kernel crashdumps? I've set: savecore_enable="YES" # Save kernel crashdumps for debugging (or NO). dumpdev="/dev/da0s2b" # Device name to crashdump to (if enabled). in /etc/rc.conf. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 03:53:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28690 for freebsd-current-outgoing; Sat, 30 May 1998 03:53:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tecumseh.altavista-software.com (tecumseh.altavista-software.com [205.181.164.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28683 for ; Sat, 30 May 1998 03:53:13 -0700 (PDT) (envelope-from matt@3am-software.com) Received: from nowin (1Cust221.tnt12.bos2.da.uu.net [208.254.158.221]) by tecumseh.altavista-software.com (8.8.5/8.8.5) with SMTP id GAA05668; Sat, 30 May 1998 06:53:02 -0400 (EDT) Message-Id: <199805301053.GAA05668@tecumseh.altavista-software.com> X-Sender: 3ampop@ranier.altavista-software.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Sat, 30 May 1998 06:51:37 -0400 To: Doug Rabson From: Matt Thomas Subject: Re: FreeBSD/alpha status report (2) Cc: current@FreeBSD.ORG In-Reply-To: References: <199805300519.XAA02620@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:16 AM 5/30/98 , Doug Rabson wrote: >I am not saying that there won't be a . I am saying that I >don't think that all the chipset implementations need to implement it. If >I do a bus_space interface, I expect that it will be something like >i386/include/bus.h. It is possible that TurboChannel and TurboLaser boxes >with multiple PCI busses might provide their own implementation rather >than the generic one. That's misguided. The point of the bus_space and bus_dma is to hide the mechanics of the underlying bus from the driver. Even if the bus is simple, the point is to abstract it (so you would have a simple abstraction). As an example, I recently moved the DEC FDDI driver to bus_dma (it already used in bus_space) which allowed me to get it running under NetBSD/pmax but only fixing coherency bugs. This means this drivers is known to work on 3 difference architectures and 3 different buses. This would be almost impossible without bus_space and bus_dma. In a week or two, I should be able to confirm it works under NetBSD/arm32. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt/ Nashua, NH Disclaimer: I disavow all knowledge of this message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 03:57:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA29014 for freebsd-current-outgoing; Sat, 30 May 1998 03:57:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA29009 for ; Sat, 30 May 1998 03:57:33 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.8/8.8.5) with SMTP id MAA03028; Sat, 30 May 1998 12:00:16 +0100 (BST) Date: Sat, 30 May 1998 12:00:16 +0100 (BST) From: Doug Rabson To: Matt Thomas cc: current@FreeBSD.ORG Subject: Re: FreeBSD/alpha status report (2) In-Reply-To: <199805301053.GAA05668@tecumseh.altavista-software.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 May 1998, Matt Thomas wrote: > At 03:16 AM 5/30/98 , Doug Rabson wrote: > > >I am not saying that there won't be a . I am saying that I > >don't think that all the chipset implementations need to implement it. If > >I do a bus_space interface, I expect that it will be something like > >i386/include/bus.h. It is possible that TurboChannel and TurboLaser boxes > >with multiple PCI busses might provide their own implementation rather > >than the generic one. > > That's misguided. The point of the bus_space and bus_dma is to hide > the mechanics of the underlying bus from the driver. Even if the bus > is simple, the point is to abstract it (so you would have a simple > abstraction). As an example, I recently moved the DEC FDDI driver > to bus_dma (it already used in bus_space) which allowed me to get it > running under NetBSD/pmax but only fixing coherency bugs. This means > this drivers is known to work on 3 difference architectures and 3 > different buses. This would be almost impossible without bus_space > and bus_dma. In a week or two, I should be able to confirm it works > under NetBSD/arm32. Why is it misguided? Drivers which use bus_space will see the same set of functions. Alpha chipsets for modern cpus with dense i/o space will use the trivial implementation of bus_space. Legacy drivers which use inb etc (we have quite a few) will work. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 04:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA05692 for freebsd-current-outgoing; Sat, 30 May 1998 04:46:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk ([195.8.133.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA05663 for ; Sat, 30 May 1998 04:46:30 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id LAA17378; Sat, 30 May 1998 11:37:46 +0200 (CEST) To: "Jordan K. Hubbard" cc: Mike Smith , Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 00:54:25 PDT." <4005.896514865@time.cdrom.com> Date: Sat, 30 May 1998 11:37:46 +0200 Message-ID: <17376.896521066@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4005.896514865@time.cdrom.com>, "Jordan K. Hubbard" writes: >> Because it ain't mounted anyhere. Think: user says: >> >> # rm /dev/foo0 >> >> # mknod /dev/foo0 c ??? >> >> What are they going to supply for the dev_t? The numbers are dynamic, >> so there's no possible reference to them. Even if they weren't, >> there's no guarantee they'd be able to guess them anyway. > >1. Of course the numbers aren't dynamic - for backwards-compatibility > to even begin to work at the mknod-level, you'd have to preserve > the old assignments. No, the medium to long term goal is to kill dev_t and mknod entirely, they are a hideous kludge and they are scheduled for demolition. (The process will take slightly longer than 2 minutes, thank you!) Think for a moment about this parallel: rm -rf /proc/125 ???? Right ? Removing /dev/lpt0 doesn't make sense, it doesn't remove the driver, it doesn't attach from the hardware, it merely removes the namesticker from the mailbox. Devfs is synthetic and maybe we shouldn't even allow removes in the first place but a whiteout/undelete solution is the "POLA" choice. Alternatively devfs could allow mknod, but ignore the major/minor numbers given and just "DTRT", that would work also after we have killed dev_t. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 05:25:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08087 for freebsd-current-outgoing; Sat, 30 May 1998 05:25:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from d183-205.uoregon.edu (d183-205.uoregon.edu [128.223.183.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08081 for ; Sat, 30 May 1998 05:25:18 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by d183-205.uoregon.edu (8.8.8/8.8.7) id FAA12313; Sat, 30 May 1998 05:25:07 -0700 (PDT) Message-ID: <19980530052506.09390@hydrogen.nike.efn.org> Date: Sat, 30 May 1998 05:25:06 -0700 From: John-Mark Gurney To: Ozz!!! Cc: FreeBSD-current mail-list Subject: Re: options NFS_NOSERVER ???? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Ozz!!! on Fri, May 29, 1998 at 11:42:12AM +0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.6-STABLE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ozz!!! scribbled this message on May 29: > > Hi! > Does NFS_NOSERVER enable in 3.0-980520 ??? > > In my new kernel i say : > options NFS_NOSERVER > > # config MYKERNEL > > MYKERNEL:30: unknown option "NFS_NOSERVER" > .... > > What can I do ? I should be fixing this in a few days... I have a number of new options to document and make new-style options... -- John-Mark Gurney Modem Rev/FAX: +1 541 346 9237 Cu Networking P.O. Box 5693, 97405 Live in Peace, destroy Micro$oft, support free software, run FreeBSD Don't trust anyone you don't have the source for To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 07:52:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18799 for freebsd-current-outgoing; Sat, 30 May 1998 07:52:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA18792 for ; Sat, 30 May 1998 07:52:41 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id OAA05353; Sat, 30 May 1998 14:52:38 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA05279; Sat, 30 May 1998 16:52:17 +0200 (MET DST) Message-ID: <19980530165217.17203@follo.net> Date: Sat, 30 May 1998 16:52:17 +0200 From: Eivind Eklund To: "Jordan K. Hubbard" , julian@whistle.com Cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <15401.896511878@critter.freebsd.dk> <15986.896513020@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <15986.896513020@time.cdrom.com>; from Jordan K. Hubbard on Sat, May 30, 1998 at 12:23:40AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 30, 1998 at 12:23:40AM -0700, Jordan K. Hubbard wrote: > Oh yeah, Eivind: I also tried the mv trick, mounting the 2nd instance > and then moving a file over? Works great, but with an unforseen > side-effect: You can't unmount the 2nd filesystem instance after > that. :-) Whooa - not good. It's supposed to be ln, not mv, but your datapoint should still be interesting to Julian. I agree that we have to do something to make 'mknod' work for re-creation. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 08:06:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20135 for freebsd-current-outgoing; Sat, 30 May 1998 08:06:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20129 for ; Sat, 30 May 1998 08:06:06 -0700 (PDT) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.4) with UUCP id QAA24890; Sat, 30 May 1998 16:05:14 +0100 (BST) Received: from [194.32.164.2] by seagoon.gid.co.uk; Sat, 30 May 1998 15:57:39 +0100 (BST) X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199805292330.QAA23999@usr05.primenet.com> References: <199805292157.OAA01107@dingo.cdrom.com> from "Mike Smith" at May 29, 98 02:57:04 pm Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 30 May 1998 16:03:34 +0100 To: Terry Lambert From: Bob Bishop Subject: Re: Fix for undefined "__error" and discussion of shared object versioning Cc: mike@smith.net.au (Mike Smith), tlambert@primenet.com, joelh@gnu.org, nate@mt.sri.com, rnordier@nordier.com, eivind@yes.no, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:30 pm +0000 29/5/98, Terry Lambert wrote: >[..] >While we are on the subject of portability problems, doesn't anyone >else find it annoying that memcpy() is not guaranteed to work on >overlapping memory ranges, yet we are migrating bcopy() to memcpy() >as time goes on? Grrrr... Yes. TABP -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 08:26:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21893 for freebsd-current-outgoing; Sat, 30 May 1998 08:26:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA21823 for ; Sat, 30 May 1998 08:26:00 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id PAA29505; Sat, 30 May 1998 15:46:04 +0200 From: Luigi Rizzo Message-Id: <199805301346.PAA29505@labinfo.iet.unipi.it> Subject: How about /usr/ports/kernel ? To: current@FreeBSD.ORG Date: Sat, 30 May 1998 15:46:04 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just looking backward, i realize that i am doing a lot of work on the kernel, and so are others. So, how about adding a new port category, /usr/ports/kernel, where one can find various kernel enhancements etc which for any reason did not find their way in the main source tree ? That would accommodate the following things: * work in progress before inclusion in the kernel (e.g. CDDA patches, IDE CDWriter support, vfat, ntfs,...). * special drivers that very few people uses. E.g. transputer, qcam, perhaps x10. * special kernel patches/subsystem (e.g. ALTQ, dummynet, PAO, ...) * backport of features from 3.0 (use at your own risk :) e.g. IDE busmastering or whatever Comments ? This section would be highly dynamic, but in my opinion very useful. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 08:26:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21932 for freebsd-current-outgoing; Sat, 30 May 1998 08:26:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21923 for ; Sat, 30 May 1998 08:26:13 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id XAA22197; Sat, 30 May 1998 23:24:08 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805301524.XAA22197@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 00:23:40 MST." <15986.896513020@time.cdrom.com> Date: Sat, 30 May 1998 23:24:07 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > The logical thing would be for "undelete" to work here... > > Assuming removals became whiteouts, yes. The only fs I know which > currently does that is unionfs, however. > > > Have you tried that ? > > See above - what good would that do? :) I even tried it with > unionfs, just for grins, and it wouldn't allow me to change > anything at all. :) > > Oh yeah, Eivind: I also tried the mv trick, mounting the 2nd instance > and then moving a file over? Works great, but with an unforseen > side-effect: You can't unmount the 2nd filesystem instance after > that. :-) Well, that'll teach you for shooting your foot off in the first place. :-) Seriously though, 'ln' was what Julian told me to use. It might make a difference since it's not making a change to the source instance. On the other hand, it also sounds like some reference counting/locking problem. > - Jordan Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 08:39:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23504 for freebsd-current-outgoing; Sat, 30 May 1998 08:39:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA23485 for ; Sat, 30 May 1998 08:39:19 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id XAA22245; Sat, 30 May 1998 23:37:01 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805301537.XAA22245@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: "Jordan K. Hubbard" , Mike Smith , Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 11:37:46 +0200." <17376.896521066@critter.freebsd.dk> Date: Sat, 30 May 1998 23:37:00 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <4005.896514865@time.cdrom.com>, "Jordan K. Hubbard" writes: > >> Because it ain't mounted anyhere. Think: user says: > >> > >> # rm /dev/foo0 > >> > >> # mknod /dev/foo0 c ??? > >> > >> What are they going to supply for the dev_t? The numbers are dynamic, > >> so there's no possible reference to them. Even if they weren't, > >> there's no guarantee they'd be able to guess them anyway. > > > >1. Of course the numbers aren't dynamic - for backwards-compatibility > > to even begin to work at the mknod-level, you'd have to preserve > > the old assignments. > > No, the medium to long term goal is to kill dev_t and mknod entirely, > they are a hideous kludge and they are scheduled for demolition. > (The process will take slightly longer than 2 minutes, thank you!) > > Think for a moment about this parallel: > > rm -rf /proc/125 > > ???? > > Right ? > > Removing /dev/lpt0 doesn't make sense, it doesn't remove the driver, > it doesn't attach from the hardware, it merely removes the namesticker > from the mailbox. > > Devfs is synthetic and maybe we shouldn't even allow removes in the > first place but a whiteout/undelete solution is the "POLA" choice. > > Alternatively devfs could allow mknod, but ignore the major/minor > numbers given and just "DTRT", that would work also after we have > killed dev_t. Exactly.. mknod() can be made to do something useful, even after there are no dev_t's left. Also, /dev/floppy, /dev/mouse and /dev/cdrom really shouldn't be done with mknod on any system, they are best done with ln or ln -s. I think a nowhiteout mount option would be nice, since 'ls -W' etc can show all the devices that are *really* present. However, I could imagine circumstances where it might be preferable to disable whiteouts, eg: the jail scenario where the mounted node would be overloaded with whiteouts and it would allow a cracker something to gather info about since they could see the whiteouts to find out what hardware/drivers are present. Cheers, -Peter -- Peter Wemm Netplex Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 09:29:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27794 for freebsd-current-outgoing; Sat, 30 May 1998 09:29:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27788 for ; Sat, 30 May 1998 09:29:44 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id QAA08034; Sat, 30 May 1998 16:29:36 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA05460; Sat, 30 May 1998 18:29:14 +0200 (MET DST) Message-ID: <19980530182913.04478@follo.net> Date: Sat, 30 May 1998 18:29:13 +0200 From: Eivind Eklund To: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: How about /usr/ports/kernel ? References: <199805301346.PAA29505@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805301346.PAA29505@labinfo.iet.unipi.it>; from Luigi Rizzo on Sat, May 30, 1998 at 03:46:04PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 30, 1998 at 03:46:04PM +0200, Luigi Rizzo wrote: > Just looking backward, i realize that i am doing a lot of work > on the kernel, and so are others. So, how about adding a new port > category, /usr/ports/kernel, where one can find various kernel > enhancements etc which for any reason did not find their way in the > main source tree ? > > That would accommodate the following things: > [...] > > Comments ? I think it might be a good idea, but this would require us to find a good way to add things to the kernel. My own view of this is that config(8) should scan for ../../*/conf/files.FreeBSD ../../*/conf/options.FreeBSD ../../*/conf/files.FreeBSD. ../../*/conf/options.FreeBSD. add concatenate this with the appropriate files. This would allow us to add a new subsystem (like i4b) by just adding a new subdir to the kernel. For some ports we would of course need to add extra kernel hooks, but this at least solve the easy cases. What do people think? Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 10:12:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03089 for freebsd-current-outgoing; Sat, 30 May 1998 10:12:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03062 for ; Sat, 30 May 1998 10:11:58 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.0/frmug-2.3/nospam) with UUCP id TAA07568 for freebsd-current@FreeBSD.ORG; Sat, 30 May 1998 19:11:52 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.9.0.Beta4/keltia-2.14/nospam) id IAA23220 for freebsd-current@FreeBSD.ORG; Sat, 30 May 1998 08:23:56 +0200 (CEST) (envelope-from roberto) Message-ID: <19980530082355.A23195@keltia.freenix.fr> Date: Sat, 30 May 1998 08:23:55 +0200 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: MD5 v. DES? Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199805291611.LAA06149@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.92.3i In-Reply-To: <199805291611.LAA06149@detlev.UUCP>; from Joel Ray Holveck on Fri, May 29, 1998 at 11:11:52AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4311 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Joel Ray Holveck: > Are there any issues with using the international version of DES in > France? The new law regarding cryptography enables anyone to use authentication products without problem. Encryption is limited to 40 bits or less if you use a product without key escrow. There is some talk about permitting 56 bits systems but that's still not allowed. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #60: Fri May 15 21:04:22 CEST 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 10:37:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05825 for freebsd-current-outgoing; Sat, 30 May 1998 10:37:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05784; Sat, 30 May 1998 10:36:52 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id BAA24556; Sun, 31 May 1998 01:36:32 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805301736.BAA24556@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: committers@FreeBSD.ORG Subject: elf vs. bsd.*.mk Date: Sun, 31 May 1998 01:36:32 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been having a good fight trying to get the world and all the permutations of the binary formats doing something sensible. Along the way I've found some things in the *.mk files which scare the hell out of me. For starters, sys.mk is automatically pulled in at make(1) startup time to setup the base, posix and generally widely accepted default rules and variables. However, at the end, it's now pulling in bsd.own.mk and /etc/make.conf (!). This is polluting the default make environment up with all sorts of crap. Sure, it means more when the .include stuff is activated at the end, but there's no reason for it to be there when using non-bmake Makefiles. The reason I ran into this was because there are certain things in the tree that *must* be compiled with a given object format and cannot use the system default - eg: the a.out ld.so must be a.out, libgcc.a needs to be compiled twice, once in a.out and once in elf format etc. Ideally, this could be fixed by overriding things in the Makefile, eg: sticking in a BINFORMAT=elf or BINFORMAT=aout as needed.. But at that point, it's too late as certain .ifs have already been "done" in bsd.own.mk (LIBDIR in particular). The other *BSD's don't have this problem. They pull in make.conf in bsd.own.mk, and all the public bsd.{prog,lib,doc,..etc..}.mk files are responsible for pulling in bsd.own.mk (instead of sys.mk). This means that STRIP, BINOWN etc are not defined until the bsd.prog.mk (or whatever) pulls it in. This is actually not much of a problem, except for a few cases where things like usr.bin/strip/Makefile do conditional rules based on variables that are not yet defined and hence don't work. A simple reordering of rules fixes it. Anyway, I manged to get it (pretty much) working although it nearly cost me my remaining sanity. I've now got the world building again, although I know of a handful of minor problems still. However, I've just realized another way of doing it that doesn't cause such a dramatic disturbance to the *.mk files, and hence is less likely to badly break things.... and is much simpler (damn!!!!!). So, I thought I'd see what general feelings were on the subject. Do we really want things like ${LIBDIR} defined for *all* makefiles, including non bsd.prog.mk etc Makefiles. Also, make.conf is also globally visible as well. I'm sure this can't be good for posix compliance etc. Since I've finished 95% of the work so far, should I press on and clean up the loose ends, or should I put it in the 'too hard' basket for the time being and try the simple way out :-). Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 10:47:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07509 for freebsd-current-outgoing; Sat, 30 May 1998 10:47:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles195.castles.com [208.214.165.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07467; Sat, 30 May 1998 10:47:32 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA06203; Sat, 30 May 1998 09:42:47 -0700 (PDT) Message-Id: <199805301642.JAA06203@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Peter Wemm cc: current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: elf vs. bsd.*.mk In-reply-to: Your message of "Sun, 31 May 1998 01:36:32 +0800." <199805301736.BAA24556@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 09:42:46 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First, a big cheer for the work you've been doing on all this! > So, I thought I'd see what general feelings were on the subject. Do we > really want things like ${LIBDIR} defined for *all* makefiles, including > non bsd.prog.mk etc Makefiles. Also, make.conf is also globally visible > as well. I'm sure this can't be good for posix compliance etc. Since > I've finished 95% of the work so far, should I press on and clean up the > loose ends, or should I put it in the 'too hard' basket for the time being > and try the simple way out :-). That depends on whether the simple way out will work. 8) If it's the "right" way, then of course it's worth doing. How about some more details on it? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 10:57:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09162 for freebsd-current-outgoing; Sat, 30 May 1998 10:57:17 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09154; Sat, 30 May 1998 10:57:14 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id RAA09821; Sat, 30 May 1998 17:57:12 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id TAA05688; Sat, 30 May 1998 19:56:51 +0200 (MET DST) Message-ID: <19980530195650.41062@follo.net> Date: Sat, 30 May 1998 19:56:50 +0200 From: Eivind Eklund To: Peter Wemm , current@FreeBSD.ORG Cc: committers@FreeBSD.ORG Subject: Re: elf vs. bsd.*.mk References: <199805301736.BAA24556@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199805301736.BAA24556@spinner.netplex.com.au>; from Peter Wemm on Sun, May 31, 1998 at 01:36:32AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, May 31, 1998 at 01:36:32AM +0800, Peter Wemm wrote: > So, I thought I'd see what general feelings were on the subject. Do we > really want things like ${LIBDIR} defined for *all* makefiles, including > non bsd.prog.mk etc Makefiles. Also, make.conf is also globally visible > as well. I'm sure this can't be good for posix compliance etc. Since > I've finished 95% of the work so far, should I press on and clean up the > loose ends, or should I put it in the 'too hard' basket for the time being > and try the simple way out :-). In my very strong opinion, bsd.own.mk should not be included from sys.mk If you have time to do it, do it, otherwise it'll stay on my mental todo-list (and will just keep being postponed until sometime in the very far future...) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 11:11:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10458 for freebsd-current-outgoing; Sat, 30 May 1998 11:11:40 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10423; Sat, 30 May 1998 11:11:27 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id CAA24860; Sun, 31 May 1998 02:10:43 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199805301810.CAA24860@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: elf vs. bsd.*.mk In-reply-to: Your message of "Sat, 30 May 1998 09:42:46 MST." <199805301642.JAA06203@antipodes.cdrom.com> Date: Sun, 31 May 1998 02:10:42 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > First, a big cheer for the work you've been doing on all this! > > > So, I thought I'd see what general feelings were on the subject. Do we > > really want things like ${LIBDIR} defined for *all* makefiles, including > > non bsd.prog.mk etc Makefiles. Also, make.conf is also globally visible > > as well. I'm sure this can't be good for posix compliance etc. Since > > I've finished 95% of the work so far, should I press on and clean up the > > loose ends, or should I put it in the 'too hard' basket for the time being > > and try the simple way out :-). > > That depends on whether the simple way out will work. 8) If it's the > "right" way, then of course it's worth doing. How about some more > details on it? Specifically, bsd.own.mk does this: .if ${BINFORMAT} == aout LIBDIR?= /usr/lib/aout .else LIBDIR?= /usr/lib .endif Which means... The condition is processed before the Makefile is read, so the makefile cannot "change" BINFORMAT and get a coherent set of changes. ie: everything except LIBDIR changes. So, the cheap hack way out is this: LIBDIR?= /usr/lib${LIBSUBDIR} and then define LIBSUBDIR later on in the bsd.*.mk files. ie: set it to "" for elf, or "/aout" for a.out, or even "/compat" if needed. This might make a few things easier in some other places too where we have gone to a lot of trouble with this particular variable. Yes, I was peeved when I realized this. :-) I started trying to get my dual-mode elf system to build world around 13 hours ago (and working on NFS stuff while waiting for the next compile to fail :-) The other way: peter@beast[2:04am]~src/share/mk-266> cvs diff -c | wc -l cvs diff: Diffing . 860 peter@beast[2:04am]~src/share/mk-267> cvs diff -u | wc -l cvs diff: Diffing . 700 Plus 20 other Makefile tweaks around the tree. Luckily, a number of the changes are applicable either way, so it's not a total loss. On one hand, the one-line change is simpler, but I think the reshuffle is more "right", although it has very little effect on how the bmakefiles see the world. It's more of a cleanliness win on non-BSD makefiles. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 11:17:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11025 for freebsd-current-outgoing; Sat, 30 May 1998 11:17:20 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11018 for ; Sat, 30 May 1998 11:17:16 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id OAA14649; Sat, 30 May 1998 14:17:08 -0400 (EDT) (envelope-from wollman) Date: Sat, 30 May 1998 14:17:08 -0400 (EDT) From: Garrett Wollman Message-Id: <199805301817.OAA14649@khavrinen.lcs.mit.edu> To: dg@root.com Cc: current@FreeBSD.ORG Subject: Re: Creating/deleting devfs nodes (was: I see one major problem with DEVFS...) In-Reply-To: <199805300750.AAA29816@implode.root.com> References: <19980530153046.E20360@freebie.lemis.com> <199805300750.AAA29816@implode.root.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Yeah, people should use the file permissions to deny access to a device, > not rm. Having the node EXIST at all leaks information -- particularly in the DEVFS model where drivers that aren't present don't have device nodes. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 12:06:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17037 for freebsd-current-outgoing; Sat, 30 May 1998 12:06:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles195.castles.com [208.214.165.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17001; Sat, 30 May 1998 12:06:15 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA06594; Sat, 30 May 1998 11:01:35 -0700 (PDT) Message-Id: <199805301801.LAA06594@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Peter Wemm cc: Mike Smith , current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: elf vs. bsd.*.mk In-reply-to: Your message of "Sun, 31 May 1998 02:10:42 +0800." <199805301810.CAA24860@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 11:01:35 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On one hand, the one-line change is simpler, but I think the reshuffle is > more "right", although it has very little effect on how the bmakefiles see > the world. It's more of a cleanliness win on non-BSD makefiles. I think the executive summary, plus your state of near-completion on the "more right" approach makes the course fairly self-evident from the point of view of expedience. Looking at the code and trying to follow your commentary, I realise that I don't know enough about the details to be able to decide on technical merits, so I'll leave that to people with opinions. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 12:09:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17846 for freebsd-current-outgoing; Sat, 30 May 1998 12:09:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17841 for ; Sat, 30 May 1998 12:09:39 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA10772; Sat, 30 May 1998 12:01:45 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd010703; Sat May 30 19:01:16 1998 Date: Sat, 30 May 1998 12:01:12 -0700 (PDT) From: Julian Elischer To: "Jordan K. Hubbard" cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-Reply-To: <15986.896513020@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 May 1998, Jordan K. Hubbard wrote: > > The logical thing would be for "undelete" to work here... > > Assuming removals became whiteouts, yes. The only fs I know which > currently does that is unionfs, however. > > > Have you tried that ? > > See above - what good would that do? :) I even tried it with > unionfs, just for grins, and it wouldn't allow me to change > anything at all. :) > > Oh yeah, Eivind: I also tried the mv trick, mounting the 2nd instance > and then moving a file over? Works great, but with an unforseen > side-effect: You can't unmount the 2nd filesystem instance after > that. :-) yeah, but I can fix that.. :-) > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 12:11:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18073 for freebsd-current-outgoing; Sat, 30 May 1998 12:11:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18068 for ; Sat, 30 May 1998 12:11:08 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA10479; Sat, 30 May 1998 11:59:10 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd010476; Sat May 30 18:59:00 1998 Date: Sat, 30 May 1998 11:58:58 -0700 (PDT) From: Julian Elischer To: Peter Wemm cc: "Jordan K. Hubbard" , Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-Reply-To: <199805300511.NAA20017@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you may also be able to do a mount -u to refresh deleted devices though I haven't figured out all the facets of that. On Sat, 30 May 1998, Peter Wemm wrote: > "Jordan K. Hubbard" wrote: > > > > E.g. I can shoot my foot off, but I can't sew it back on. :-) > > > > > > Yes, you can. You can mount another devfs and 'mv' a device from it > > > (or at least that's the way the specs read - I don't have devfs > > > enabled right now, so I can't test). > > > > That's utterly rude. :-) > > > > I hope you're not implying that this is going to be the accepted way > > for doing this in the future as well. Non-persistence is a big enough > > violation of POLA as it is, and not even being able to do mknod(2) > > operations on a devfs to replace missing entries would be a POLA > > catastrophe. > > Remember this is merely step 1. The Plan is to eventually replace minor/ > major devices completely so that the filesystem interface will probably be > through a 32 bit vnode pointer or something along those lines. Doing a > mknod will be practically impossible. (This has some major benefits but > will be a major change in the driver/kernel/fs interface. Drivers won't > have a major/minor number anymore, they'll just have a unit number.. > specfs will either be gone or won't resemble anything like it does now, > and will probably hang off devfs instead. > > For the problem at hand though, I once suggested to Julian that we use > undelete(2) to make files come back. "rm -W bpf4" could almost work as is, > except that it wants to stat the file and look for whiteout flags first and > 'rm' doesn't create a whiteout in devfs. (This might be an interesting > approach to the problem if all unlinks caused a whiteout instead of the > node disappearing entirely.) > > > - Jordan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Cheers, > -Peter > -- > Peter Wemm Netplex Consulting > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 12:14:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18852 for freebsd-current-outgoing; Sat, 30 May 1998 12:14:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18847 for ; Sat, 30 May 1998 12:14:51 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id MAA11174; Sat, 30 May 1998 12:10:00 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd011172; Sat May 30 19:09:54 1998 Date: Sat, 30 May 1998 12:09:51 -0700 (PDT) From: Julian Elischer To: Mike Smith cc: "Jordan K. Hubbard" , Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-Reply-To: <199805300414.VAA00432@antipodes.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes, and the easiest way of achieving that is to get the device from a temporarily mounted new copy of devfs. do a lookup in there for the device you want mv it to /dev wherever you want ans unmount the temp devfs. I know that at present you can't do that and unmount the 2nd devfs, but that's easily fixable in the code. This lets the kernel do the lookup and the housekeeping. there are a few other things I'm looking at, one of which is a being able to mount a 'blank devfs (useful in some cases) and a mount -u which refreshes deleted devices julian On Fri, 29 May 1998, Mike Smith wrote: > > > > E.g. I can shoot my foot off, but I can't sew it back on. :-) > > > > > > Yes, you can. You can mount another devfs and 'mv' a device from it > > > (or at least that's the way the specs read - I don't have devfs > > > enabled right now, so I can't test). > > > > That's utterly rude. :-) > > > > I hope you're not implying that this is going to be the accepted way > > for doing this in the future as well. Non-persistence is a big enough > > violation of POLA as it is, and not even being able to do mknod(2) > > operations on a devfs to replace missing entries would be a POLA > > catastrophe. > > You could make a strong case for having mknod ignore the (dev) argument > and just look the name up in the reference devfs copy, and then > duplicate it at the path given (presuming that's inside a devfs). > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 13:09:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA26026 for freebsd-current-outgoing; Sat, 30 May 1998 13:09:39 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles195.castles.com [208.214.165.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA26020; Sat, 30 May 1998 13:09:36 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA07077; Sat, 30 May 1998 12:04:45 -0700 (PDT) Message-Id: <199805301904.MAA07077@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Somers cc: Mike Smith , sos@FreeBSD.ORG, wollman@khavrinen.lcs.mit.edu (Garrett Wollman), current@FreeBSD.ORG Subject: Re: cvs commit: src Makefile src/etc rc src/etc/mtree BSD.usr.dist In-reply-to: Your message of "Fri, 29 May 1998 07:40:08 BST." <199805290640.HAA00434@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 12:04:44 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So is dlopen() now capable ? Not AFAIK. Adding it should not be too difficult; in the a.out loader you could steal the fragment from the LD_PRELOAD handler that says: path = (strchr(name, '/') == NULL) ? strdup(name) : rtfindfile(name); ... free(path); Note that the LD_LIBRARY_PATH handling code will only add directories to the standard search path if it's "safe" to do so, so you don't have to worry about the security implications of this search; the path is as secure as it would otherwise be. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 13:31:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28800 for freebsd-current-outgoing; Sat, 30 May 1998 13:31:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28794 for ; Sat, 30 May 1998 13:31:08 -0700 (PDT) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <6690-8368>; Sat, 30 May 1998 22:30:49 +0200 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.8.8/8.8.8) with ESMTP id WAA01418; Sat, 30 May 1998 22:27:06 +0200 (MET DST) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id WAA09104; Sat, 30 May 1998 22:27:01 +0200 (MET DST) Message-Id: <199805302027.WAA09104@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Sat, 30 May 98 22:26:59 +0200 To: current@FreeBSD.ORG, brian@awfulhak.org Subject: ppp -background sets wrong pid in /var/run/tun0.pid Reply-To: ben@stuyts.nl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have just done a make world of -current, and I noticed the following problem with the new ppp: [terminus.stuyts.nl var/run]16: ppp -background nlnet Working in background mode Using interface: tun0 PPP enabled. [terminus.stuyts.nl var/run]17: ps -aguxww | grep ppp benst 1389 0.0 1.5 1276 956 ?? Ss 10:24PM 0:00.05 ppp -background nlnet [terminus.stuyts.nl var/run]18: cat /var/run/tun0.pid 1388 It seems the value in tun0.pid is one off. This is quite a problem in scripts such as: /usr/sbin/ppp -background nlnet > /dev/console 2>&1 ... /bin/kill -TERM `cat /var/run/tun0.pid` > /dev/console Any ideas? Best regards, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 13:42:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29782 for freebsd-current-outgoing; Sat, 30 May 1998 13:42:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29772; Sat, 30 May 1998 13:42:09 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id GAA13569; Sun, 31 May 1998 06:42:06 +1000 Date: Sun, 31 May 1998 06:42:06 +1000 From: Bruce Evans Message-Id: <199805302042.GAA13569@godzilla.zeta.org.au> To: current@FreeBSD.ORG, peter@netplex.com.au Subject: Re: elf vs. bsd.*.mk Cc: committers@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >For starters, sys.mk is automatically pulled in at make(1) startup time to >setup the base, posix and generally widely accepted default rules and >variables. > >However, at the end, it's now pulling in bsd.own.mk and /etc/make.conf (!). It's done that for years, and I've been compaining about it for years. rgrimes added the bsd.own.mk hack and phk added the /etc/make.conf hack. >This is polluting the default make environment up with all sorts of crap. >Sure, it means more when the .include stuff is activated at the >end, but there's no reason for it to be there when using non-bmake >Makefiles. However, there seems to be no better place than /etc/make.conf to set some variables. Some have to be set early, and it's too hard to set them on the command line or in a few thousand Makefiles. >The other *BSD's don't have this problem. They pull in make.conf in >bsd.own.mk, and all the public bsd.{prog,lib,doc,..etc..}.mk files are >responsible for pulling in bsd.own.mk (instead of sys.mk). This means >that STRIP, BINOWN etc are not defined until the bsd.prog.mk (or whatever) >pulls it in. Another interesting point is that despite moving repetitive code to bsd.own.mk etc., we have 5 times as much code in *.mk as Lite2 (not counting ports). Just the comments in bsd.own.mk are larger than most Lite2 mk files. bsd.own.mk can probably be moved to the end easily enough. I was planning to merge it with bsd.obj.mk and rename the result to something like bsd.misc.mk. This file would contain everything that applies to all types of bsd.*mk files and can be specified last. >However, I've just realized another way of doing it that doesn't cause >such a dramatic disturbance to the *.mk files, and hence is less likely to >badly break things.... and is much simpler (damn!!!!!). > >So, I thought I'd see what general feelings were on the subject. Do we >really want things like ${LIBDIR} defined for *all* makefiles, including >non bsd.prog.mk etc Makefiles. Also, make.conf is also globally visible We want them defined for all bsd.*.mk files if they are "constant". BINDIR can not be defaulted because it varies within a single world, and LIBDIR is variable if you want it to put {aout,elf} in it. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 13:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00715 for freebsd-current-outgoing; Sat, 30 May 1998 13:49:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00707 for ; Sat, 30 May 1998 13:49:23 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id PAA29795; Sat, 30 May 1998 15:45:31 -0500 (CDT) Date: Sat, 30 May 1998 15:45:31 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <19980530182913.04478@follo.net> References: <199805301346.PAA29505@labinfo.iet.unipi.it>; from Luigi Rizzo on Sat, May 30, 1998 at 03:46:04PM +0200 <199805301346.PAA29505@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Eivind Eklund From: Richard Wackerbarth Subject: Re: How about /usr/ports/kernel ? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:29 PM -0000 5/30/98, Eivind Eklund wrote: >My own view of this is that config(8) should scan for > ../../*/conf/files.FreeBSD > ../../*/conf/options.FreeBSD > ../../*/conf/files.FreeBSD. > ../../*/conf/options.FreeBSD. >add concatenate this with the appropriate files. > >This would allow us to add a new subsystem (like i4b) by just adding a >new subdir to the kernel. > >For some ports we would of course need to add extra kernel hooks, but >this at least solve the easy cases. > >What do people think? My first observation is that, other than being more dynamic, and a higher desire for individual customization, the binary file generated for "/kernel" is not fundamentally different from the one created for "/bin/cat" or "/usr/sbin/ctm". Each of them has its own variances on the theme of source -> itermediate -> result translation. For example, they use different linker stratgies. If we rearrange our viewpoint a bit, "config" is similar to "yacc" and is a tool (which needs to be up-to-date) which converts a source file (eg., "GENERIC") into some "C" files. These files are subsequently transformed, under the direction of "make", into intermediate object files and finally a loadable result. A single "user" may wish to have a number of different kernels built. He could do this by adding an appropriate (trivial) directory, Makefile, and additional/overriding files to describe his variation. Particular subprojects could, to a large extent, co-exist in the same (master) source tree. They would simply be invoked as needed by the kernel configuration and/or Makefiles. Unused sections would simply be ignored. A user would add appropriate directories to src/sys/compile.1386 for the kernels that he wishes to build. He would not explicitly run "config" because that would be an automatic part of the "make" structure. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 13:56:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01853 for freebsd-current-outgoing; Sat, 30 May 1998 13:56:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01846 for ; Sat, 30 May 1998 13:56:48 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.7/8.6.12) id UAA08572; Sat, 30 May 1998 20:56:36 GMT Message-ID: <19980530135635.A8548@nuxi.com> Date: Sat, 30 May 1998 13:56:35 -0700 From: "David O'Brien" To: Karl Pielorz , current@FreeBSD.ORG Subject: Re: problems with SCSI drives over sd9? Reply-To: obrien@NUXI.com References: <35654168.F0F30C3@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <35654168.F0F30C3@tdx.co.uk>; from Karl Pielorz on Fri, May 22, 1998 at 10:12:08AM +0100 X-Operating-System: FreeBSD 2.2.5-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Basically the same procedure which has worked for sd0 through sd9 doesn't > appear to work for sd10... This sounds slightly related to a fix I made in libdisk in which Disk_Names() woulnd't probe any disk greater than sd9. I only experieneced a problem with sysinstall, so I don't think this is your problem... but just to make sure, see if you have the most current src/lib/libdisk/disk.c. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 14:00:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02446 for freebsd-current-outgoing; Sat, 30 May 1998 14:00:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp154.0.mmtl.videotron.net [207.253.0.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02434 for ; Sat, 30 May 1998 14:00:25 -0700 (PDT) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost [127.0.0.1]) by azimov.videotron.ca (8.8.8/8.8.8) with ESMTP id RAA00236 for ; Sat, 30 May 1998 17:02:14 -0400 (EDT) (envelope-from sepotvin@videotron.ca) Message-ID: <357073D6.64199B09@videotron.ca> Date: Sat, 30 May 1998 17:02:14 -0400 From: "Stephane E. Potvin" Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <199805301537.XAA22245@spinner.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Maybe this will seems a stupid question but why in the first place would someone want to delete a device from a devfs /dev? Or put differently why is not devfs append-only so someone would be able to make new links but not able to delete existing devices? Stephane E. Potvin POS and Industry Helpdesk IBM Canada Ltd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 14:09:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03673 for freebsd-current-outgoing; Sat, 30 May 1998 14:09:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03639 for ; Sat, 30 May 1998 14:09:15 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.8.8/8.8.8) with ESMTP id WAA04964; Sat, 30 May 1998 22:09:05 +0100 (BST) (envelope-from kpielorz@tdx.co.uk) Message-ID: <35707571.68F99E96@tdx.co.uk> Date: Sat, 30 May 1998 22:09:05 +0100 From: Karl Pielorz Organization: TDX X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: obrien@NUXI.com CC: current@FreeBSD.ORG Subject: Re: problems with SCSI drives over sd9? References: <35654168.F0F30C3@tdx.co.uk> <19980530135635.A8548@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > Basically the same procedure which has worked for sd0 through sd9 doesn't > > appear to work for sd10... > > This sounds slightly related to a fix I made in libdisk in which > Disk_Names() woulnd't probe any disk greater than sd9. I only > experieneced a problem with sysinstall, so I don't think this is your > problem... but just to make sure, see if you have the most current > src/lib/libdisk/disk.c. Hi, Jordan got involved with this for a bit, then it got kinda dropped... As far as I can tell - the system won't write disklabels to drives over sd9... If I forcibly re-wire the drives down into the sd0-8 range I can label, partition etc. fine... newfs works regardless of the sdX, it's just labels I'm having problems with... If I try to disklabel say sd12 - it 'seems' to work, but when you read the label back you get disk label's 'worst' guess for the label, not what you'd just told it to write... I'm running 3.0-CURRENT, made as of about 2 weeks ago... I've seen the change in sysinstall, before it would only list up to sd9, now it correctly lists up to sd14... Labelling etc. from sysinstall still fails though... All of this is with no error messages :-( Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 14:15:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04429 for freebsd-current-outgoing; Sat, 30 May 1998 14:15:48 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04422 for ; Sat, 30 May 1998 14:15:45 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id QAA29897; Sat, 30 May 1998 16:15:39 -0500 (CDT) Date: Sat, 30 May 1998 16:15:39 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199805302042.GAA13569@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Bruce Evans From: Richard Wackerbarth Subject: Re: elf vs. bsd.*.mk Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:42 PM -0000 5/30/98, Bruce Evans wrote: >We want them defined for all bsd.*.mk files if they are "constant". >BINDIR can not be defaulted because it varies within a single world, >and LIBDIR is variable if you want it to put {aout,elf} in it. Virtually NOTHING is constant. Quite often if may be desirable for it to take on a default value because we have not specified any overriding value. For example, the source is likely, but should not be required, to be in /usr/src; the target machine architecture is generally, but not always, the same as that of the machine on which it is running; etc. I SHOULD be able to simultaneously compile, from the same source tree, systems for two different machine architectures and/or variations of compile parameters. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 14:15:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04471 for freebsd-current-outgoing; Sat, 30 May 1998 14:15:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04461 for ; Sat, 30 May 1998 14:15:52 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id QAA29900; Sat, 30 May 1998 16:15:40 -0500 (CDT) Date: Sat, 30 May 1998 16:15:40 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199805292120.OAA14978@usr04.primenet.com> References: <199805282015.PAA01671@detlev.UUCP> from "Joel Ray Holveck" at May 28, 98 03:15:44 pm Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Terry Lambert From: Richard Wackerbarth Subject: Re: Fix for undefined "__error" and discussion of shared object versioning Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:20 PM -0000 5/29/98, Terry Lambert wrote: >It also means that one "ports" CDROM will work for FreeBSD 3.x and >FreeBSD 235.x. How can you make this claim? The individual ports may well rely on some feature of FreeBSD 235.x that was not present in FreeBSD 3.x. Similarly, a port for 3.x may rely on a feature that was removed before 5.0. As much as we might like to think otherwise, assumptions about the structure of the underlying OS and "hardcoded" into the source of the program. :-( Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 14:31:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06900 for freebsd-current-outgoing; Sat, 30 May 1998 14:31:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06895 for ; Sat, 30 May 1998 14:31:57 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.7/8.6.12) id VAA08715; Sat, 30 May 1998 21:31:48 GMT Message-ID: <19980530143148.E3610@nuxi.com> Date: Sat, 30 May 1998 14:31:48 -0700 From: "David O'Brien" To: Karl Pielorz Cc: current@FreeBSD.ORG Subject: Re: problems with SCSI drives over sd9? Reply-To: obrien@NUXI.com References: <35654168.F0F30C3@tdx.co.uk> <19980530135635.A8548@nuxi.com> <35707571.68F99E96@tdx.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <35707571.68F99E96@tdx.co.uk>; from Karl Pielorz on Sat, May 30, 1998 at 10:09:05PM +0100 X-Operating-System: FreeBSD 2.2.5-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Jordan got involved with this for a bit, then it got kinda dropped... As far > as I can tell - the system won't write disklabels to drives over sd9... If I > forcibly re-wire the drives down into the sd0-8 range I can label, partition > etc. fine... I know that 22-stable's disklabel will work on sd18 :) But my drives are NOT continuiously numbered. Currently I've got sd0,sd1,sd2,sd3 on one controler, and sd10,sd11,sd12,sd13,sd14,sd15,sd18 on another one. (the last digit matches the SCSI id). All of sd1X was done with ``disklabel -Brw sd1X auto'' and all use the "c" partition. Although, last month most of the sd1X used the "e" partition (if any of this helps). What is your setup? -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 14:33:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07196 for freebsd-current-outgoing; Sat, 30 May 1998 14:33:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bleep.ishiboo.com (user19346@bleep.ishiboo.com [199.79.133.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA07163 for ; Sat, 30 May 1998 14:32:54 -0700 (PDT) (envelope-from nirva@ishiboo.com) Received: (qmail 5061 invoked by uid 1000); 30 May 1998 22:35:29 -0000 Message-ID: <19980530173528.55676@bleep.ishiboo.com> Date: Sat, 30 May 1998 17:35:28 -0500 From: Danny Dulai To: "John S. Dyson" Cc: freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Fastvid: no speed increase :( References: <19980527232341.65268@bleep.ishiboo.com> <199805300309.WAA05164@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199805300309.WAA05164@dyson.iquest.net>; from John S. Dyson on Fri, May 29, 1998 at 10:09:08PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting John S. Dyson (toor@dyson.iquest.net): > > Quoting Daniel O'Connor (doconnor@gsoft.com.au): > > > > > > The speedup factor is 1.89, mmm :) > > This is a copy of the original code that I submitted to someone who > cleaned it up (I am sorry that I forgot who actually took ownership.) I used this code, set the VIDPHYSADDR to 0xe1800000 and VIDPHYSSIZE to 0x800000, and MSRINDEX is set to 5 (??) and experienced NO speed increase at all when using xengine. this is my X server output: PCI (#1/1, 8000000c) MATROX,28: 2064W,TVP3026 (8192k @e1800000) MATROX,28: 2164WA,TVP3026 (4096k @e3000000) Xaccel 4.1 (build 4100,MX) Accelerated-X (tm) Display Server Copyright (c) 1993-97 by Xi Graphics, Inc. All Rights Reserved Unpublished -- Rights reserved under the Copyright Laws of the United States This is my dmesg output when I load it: default: type: 0xc00 0: type: 6, addr: 0x0000, mask: 0xff8000000 basehi: 0x 0, baselo: 0x 6 maskhi: 0x f, masklo: 0xf8000800 5: type: 1, addr: 0xe1800000, mask: 0xfff800000 basehi: 0x 0, baselo: 0xe1800001 maskhi: 0x f, masklo: 0xff800800 MTRRfix64K_00000: 0x 6060606 0x 6060606 MTRRfix16K_80000: 0x 6060606 0x 6060606 MTRRfix16K_A0000: 0x 1010101 0x 1010101 MTRRfix4K_C0000: 0x 5050505 0x 5050505 MTRRfix4K_C8000: 0x 0 0x 0 MTRRfix4K_D0000: 0x 0 0x 0 MTRRfix4K_D8000: 0x 0 0x 0 MTRRfix4K_E0000: 0x 0 0x 0 MTRRfix4K_E8000: 0x 0 0x 0 MTRRfix4K_F0000: 0x 0 0x 0 MTRRfix4K_F8000: 0x 5 0x 5050505 BKUPTMPDR6: ff0 BKUPTMPDR6: c5900000 4MB page: 0xe7(f0000000) Any ideas? Might Xinside already be setting this for me and I'm already getting as fast as it gets? -- ___________________________________________________________________________ Danny Dulai Feet. Pumice. Lotion. http://www.ishiboo.com/~nirva/ nirva@ishiboo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 14:48:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09740 for freebsd-current-outgoing; Sat, 30 May 1998 14:48:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09729 for ; Sat, 30 May 1998 14:48:26 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id HAA15922; Sun, 31 May 1998 07:48:24 +1000 Date: Sun, 31 May 1998 07:48:24 +1000 From: Bruce Evans Message-Id: <199805302148.HAA15922@godzilla.zeta.org.au> To: bde@zeta.org.au, rkw@dataplex.net Subject: Re: elf vs. bsd.*.mk Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>We want them defined for all bsd.*.mk files if they are "constant". >>BINDIR can not be defaulted because it varies within a single world, >>and LIBDIR is variable if you want it to put {aout,elf} in it. > >Virtually NOTHING is constant. Quite often if may be desirable for >it to take on a default value because we have not specified any >overriding value. Virtually everything is "constant", i.e. has the same values for all sub-makes. >I SHOULD be able to simultaneously compile, from the same source tree, >systems for two different machine architectures and/or variations >of compile parameters. Not in a single invocation of make. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 14:52:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10521 for freebsd-current-outgoing; Sat, 30 May 1998 14:52:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10511 for ; Sat, 30 May 1998 14:52:28 -0700 (PDT) (envelope-from mi@rtfm.ziplink.net) Received: from rtfm.ziplink.net (rtfm [199.232.255.52]) by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id VAA16638 for ; Sat, 30 May 1998 21:52:13 GMT (envelope-from mi@rtfm.ziplink.net) Received: (from mi@localhost) by rtfm.ziplink.net (8.8.8/8.8.5) id RAA17435 for current@freebsd.org; Sat, 30 May 1998 17:52:15 -0400 (EDT) From: Mikhail Teterin Message-Id: <199805302152.RAA17435@rtfm.ziplink.net> Subject: Re: I see one major problem with DEVFS... In-Reply-To: <17376.896521066@critter.freebsd.dk> from "Poul-Henning Kamp" at "May 30, 98 11:37:46 am" To: current@FreeBSD.ORG Date: Sat, 30 May 1998 17:52:15 -0400 (EDT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12347 for freebsd-current-outgoing; Sat, 30 May 1998 15:07:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12335 for ; Sat, 30 May 1998 15:07:00 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id RAA00172; Sat, 30 May 1998 17:06:50 -0500 (CDT) Date: Sat, 30 May 1998 17:06:50 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199805302148.HAA15922@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Bruce Evans From: Richard Wackerbarth Subject: Re: elf vs. bsd.*.mk Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:48 PM -0000 5/30/98, Bruce Evans wrote: >>>We want them defined for all bsd.*.mk files if they are "constant". >>>BINDIR can not be defaulted because it varies within a single world, >>>and LIBDIR is variable if you want it to put {aout,elf} in it. >> >>Virtually NOTHING is constant. Quite often if may be desirable for >>it to take on a default value because we have not specified any >>overriding value. > >Virtually everything is "constant", i.e. has the same values for all >sub-makes. > >>I SHOULD be able to simultaneously compile, from the same source tree, >>systems for two different machine architectures and/or variations >>of compile parameters. > >Not in a single invocation of make. I agree. However, my concern is that the prior tendancy has been to expand the "invariant within a tree of sub-makes" into "globally constant across all uses". For example, there have been numerous assumptions that the source tree is ALWAYS in /usr/src. Here are still places that effectively assume that /x/y/z/../../y/z is the same as /x/y/z. In the presence of symbolic links, this may well be false. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 15:18:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14374 for freebsd-current-outgoing; Sat, 30 May 1998 15:18:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14110 for ; Sat, 30 May 1998 15:17:09 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id WAA15079 for ; Sat, 30 May 1998 22:17:08 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id AAA06365; Sun, 31 May 1998 00:15:26 +0200 (MET DST) Message-ID: <19980531001525.36883@follo.net> Date: Sun, 31 May 1998 00:15:25 +0200 From: Eivind Eklund To: "Stephane E. Potvin" , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <199805301537.XAA22245@spinner.netplex.com.au> <357073D6.64199B09@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <357073D6.64199B09@videotron.ca>; from Stephane E. Potvin on Sat, May 30, 1998 at 05:02:14PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 30, 1998 at 05:02:14PM -0400, Stephane E. Potvin wrote: > Maybe this will seems a stupid question but why in the first place would > someone want to delete a device from a devfs /dev? Or put differently why is > not devfs append-only so someone would be able to make new links but not able > to delete existing devices? For use in a chroot()'ed environment. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 15:49:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA18606 for freebsd-current-outgoing; Sat, 30 May 1998 15:49:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA18555; Sat, 30 May 1998 15:48:53 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id PAA00442; Sat, 30 May 1998 15:48:04 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Peter Wemm cc: current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: elf vs. bsd.*.mk In-reply-to: Your message of "Sun, 31 May 1998 01:36:32 +0800." <199805301736.BAA24556@spinner.netplex.com.au> Date: Sat, 30 May 1998 15:48:04 -0700 Message-ID: <438.896568484@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I suggest you leverage the work you've done so far and simply finish it. We know our build system is full of warts, we've just not had anyone dedicated (with $$ incentive :) to go after them until now(?). - Jordan > I've been having a good fight trying to get the world and all the > permutations of the binary formats doing something sensible. > > Along the way I've found some things in the *.mk files which scare the > hell out of me. > > For starters, sys.mk is automatically pulled in at make(1) startup time to > setup the base, posix and generally widely accepted default rules and > variables. > > However, at the end, it's now pulling in bsd.own.mk and /etc/make.conf (!). > This is polluting the default make environment up with all sorts of crap. > Sure, it means more when the .include stuff is activated at the > end, but there's no reason for it to be there when using non-bmake > Makefiles. > > The reason I ran into this was because there are certain things in the > tree that *must* be compiled with a given object format and cannot use the > system default - eg: the a.out ld.so must be a.out, libgcc.a needs to be > compiled twice, once in a.out and once in elf format etc. > > Ideally, this could be fixed by overriding things in the Makefile, eg: > sticking in a BINFORMAT=elf or BINFORMAT=aout as needed.. But at that > point, it's too late as certain .ifs have already been "done" in > bsd.own.mk (LIBDIR in particular). > > The other *BSD's don't have this problem. They pull in make.conf in > bsd.own.mk, and all the public bsd.{prog,lib,doc,..etc..}.mk files are > responsible for pulling in bsd.own.mk (instead of sys.mk). This means > that STRIP, BINOWN etc are not defined until the bsd.prog.mk (or whatever) > pulls it in. > > This is actually not much of a problem, except for a few cases where > things like usr.bin/strip/Makefile do conditional rules based on variables > that are not yet defined and hence don't work. A simple reordering of > rules fixes it. > > Anyway, I manged to get it (pretty much) working although it nearly cost > me my remaining sanity. I've now got the world building again, although I > know of a handful of minor problems still. > > However, I've just realized another way of doing it that doesn't cause > such a dramatic disturbance to the *.mk files, and hence is less likely to > badly break things.... and is much simpler (damn!!!!!). > > So, I thought I'd see what general feelings were on the subject. Do we > really want things like ${LIBDIR} defined for *all* makefiles, including > non bsd.prog.mk etc Makefiles. Also, make.conf is also globally visible > as well. I'm sure this can't be good for posix compliance etc. Since > I've finished 95% of the work so far, should I press on and clean up the > loose ends, or should I put it in the 'too hard' basket for the time being > and try the simple way out :-). > > Cheers, > -Peter > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 15:59:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20035 for freebsd-current-outgoing; Sat, 30 May 1998 15:59:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20030 for ; Sat, 30 May 1998 15:59:55 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA15718; Sat, 30 May 1998 15:53:15 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd015716; Sat May 30 22:53:13 1998 Date: Sat, 30 May 1998 15:53:10 -0700 (PDT) From: Julian Elischer Reply-To: Julian Elischer To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-Reply-To: <1416.896556860@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I agree with this it's not a bad idea If the device being made does not exist then the master directory corresponding with that the mknod is in is scanned for that name. if it exists, it's made. Now, here are some implementatioan details.. If it already exists there but was just renamed, should I make it a link? I think yes (I can do this quite easily). If the entire directory has been renamed? with On Sat, 30 May 1998, Poul-Henning Kamp wrote: > > Julian, > > Just to get peace over the land again, I think you should implement > it so that one can mknod a device again, but discard the dev_t, > and use whatever DEVFS knows (better). > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 16:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21159 for freebsd-current-outgoing; Sat, 30 May 1998 16:07:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21030 for ; Sat, 30 May 1998 16:06:29 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id XAA16012; Sat, 30 May 1998 23:06:12 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id BAA06568; Sun, 31 May 1998 01:04:25 +0200 (MET DST) Message-ID: <19980531010424.07998@follo.net> Date: Sun, 31 May 1998 01:04:24 +0200 From: Eivind Eklund To: Richard Wackerbarth , Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: elf vs. bsd.*.mk References: <199805302042.GAA13569@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Richard Wackerbarth on Sat, May 30, 1998 at 04:15:39PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 30, 1998 at 04:15:39PM -0500, Richard Wackerbarth wrote: > At 8:42 PM -0000 5/30/98, Bruce Evans wrote: > I SHOULD be able to simultaneously compile, from the same source tree, > systems for two different machine architectures and/or variations > of compile parameters. Hmmm. There are two things missing to be able to do this: o Automated generation of kernels o Reading of make.conf from ${MAKE_CONF} if it exists, instead of using /etc/make.conf always. The latter is a trivial patch to sys.mk (or possibly to the bsd.*.mk after Peter has fixed the use of bsd.own.mk). Apart from the above, we already have control of the various variants through the use of SUBDIR_CHANGE (which I haven't yet tested if works through the buildworld target - I suspect it doesn't. Ah, silly me) and OBJDIR. And, of course, we're missing the ability to actually do a compile for more than one architecture _at all_, given our lack of alternate architectures. Of course, the present way of specifying all of this isn't the best imaginable, but it _is_ possible. I'm imagining SUBDIR_CHANGE to be used mostly through a higher-level interface in the future. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 16:09:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21408 for freebsd-current-outgoing; Sat, 30 May 1998 16:09:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21393 for ; Sat, 30 May 1998 16:09:09 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA15630; Sat, 30 May 1998 15:48:14 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd015612; Sat May 30 22:48:04 1998 Date: Sat, 30 May 1998 15:47:59 -0700 (PDT) From: Julian Elischer To: Eivind Eklund cc: Luigi Rizzo , current@FreeBSD.ORG Subject: Re: How about /usr/ports/kernel ? In-Reply-To: <19980530182913.04478@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you know, I was thinking very similar things.. As you know I've been adding stuff but some of it gets added a little earlier than it should because there is no real alternative. On Sat, 30 May 1998, Eivind Eklund wrote: > On Sat, May 30, 1998 at 03:46:04PM +0200, Luigi Rizzo wrote: > > Just looking backward, i realize that i am doing a lot of work > > on the kernel, and so are others. So, how about adding a new port > > category, /usr/ports/kernel, where one can find various kernel > > enhancements etc which for any reason did not find their way in the > > main source tree ? > > > > That would accommodate the following things: > > > [...] > > > > Comments ? > > I think it might be a good idea, but this would require us to find a > good way to add things to the kernel. > > My own view of this is that config(8) should scan for > ../../*/conf/files.FreeBSD > ../../*/conf/options.FreeBSD > ../../*/conf/files.FreeBSD. > ../../*/conf/options.FreeBSD. > add concatenate this with the appropriate files. > > This would allow us to add a new subsystem (like i4b) by just adding a > new subdir to the kernel. > > For some ports we would of course need to add extra kernel hooks, but > this at least solve the easy cases. > > What do people think? > > Eivind. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 16:14:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22772 for freebsd-current-outgoing; Sat, 30 May 1998 16:14:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22501 for ; Sat, 30 May 1998 16:13:42 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id XAA16141 for ; Sat, 30 May 1998 23:13:40 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id BAA06594; Sun, 31 May 1998 01:11:59 +0200 (MET DST) Message-ID: <19980531011158.16813@follo.net> Date: Sun, 31 May 1998 01:11:58 +0200 From: Eivind Eklund To: Richard Wackerbarth Cc: current@FreeBSD.ORG Subject: Re: Fix for undefined "__error" and discussion of shared object versioning References: <199805282015.PAA01671@detlev.UUCP> <199805292120.OAA14978@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Richard Wackerbarth on Sat, May 30, 1998 at 04:15:40PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 30, 1998 at 04:15:40PM -0500, Richard Wackerbarth wrote: > At 9:20 PM -0000 5/29/98, Terry Lambert wrote: > > >It also means that one "ports" CDROM will work for FreeBSD 3.x and > >FreeBSD 235.x. > > How can you make this claim? The individual ports may well rely on > some feature of FreeBSD 235.x that was not present in FreeBSD > 3.x. Similarly, a port for 3.x may rely on a feature that was > removed before 5.0. > > As much as we might like to think otherwise, assumptions about the > structure of the underlying OS and "hardcoded" into the source of > the program. :-( Have you looked at the XANDF structure? It actually does address this point (by doing the final stages of compilation as the program is installed, and being able to take care of that kind of dependencies at that point). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 16:22:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23635 for freebsd-current-outgoing; Sat, 30 May 1998 16:22:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23618 for ; Sat, 30 May 1998 16:21:56 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id XAA03982; Sat, 30 May 1998 23:14:10 GMT Date: Sun, 31 May 1998 08:14:10 +0900 (JST) From: Michael Hancock To: Poul-Henning Kamp cc: "Jordan K. Hubbard" , Mike Smith , Eivind Eklund , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-Reply-To: <17376.896521066@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 30 May 1998, Poul-Henning Kamp wrote: > Devfs is synthetic and maybe we shouldn't even allow removes in the > first place but a whiteout/undelete solution is the "POLA" choice. > > Alternatively devfs could allow mknod, but ignore the major/minor > numbers given and just "DTRT", that would work also after we have > killed dev_t. I agree with either of these options. The whiteout solution would mean a lot of hacking on a devfs_lookup(). Being able to refresh the node using mknod without the major/minor arguments or ignoring the arguments and just DTRT sounds good to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 16:53:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27328 for freebsd-current-outgoing; Sat, 30 May 1998 16:53:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27306 for ; Sat, 30 May 1998 16:53:44 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id XAA16855; Sat, 30 May 1998 23:53:40 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id BAA06729; Sun, 31 May 1998 01:53:19 +0200 (MET DST) Message-ID: <19980531015319.33329@follo.net> Date: Sun, 31 May 1998 01:53:19 +0200 From: Eivind Eklund To: Julian Elischer , Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... References: <1416.896556860@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Julian Elischer on Sat, May 30, 1998 at 03:53:10PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 30, 1998 at 03:53:10PM -0700, Julian Elischer wrote: > > Julian, > > > > Just to get peace over the land again, I think you should implement > > it so that one can mknod a device again, but discard the dev_t, > > and use whatever DEVFS knows (better). > > I agree with this > it's not a bad idea > > If the device being made does not exist then the master directory > corresponding with that the mknod is in is scanned for that name. If you want to be really nice, I'd say implement a reverse mapping from the major/minor numbers for the time being. We will (of course) get rid of this later, but it would allow an almost completely smooth transition to DEVFS. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 16:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27491 for freebsd-current-outgoing; Sat, 30 May 1998 16:54:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27483; Sat, 30 May 1998 16:54:26 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id SAA00461; Sat, 30 May 1998 18:54:20 -0500 (EST) (envelope-from toor) Message-Id: <199805302354.SAA00461@dyson.iquest.net> Subject: Re: Fastvid: no speed increase :( In-Reply-To: <19980530173528.55676@bleep.ishiboo.com> from Danny Dulai at "May 30, 98 05:35:28 pm" To: nirva@ishiboo.com (Danny Dulai) Date: Sat, 30 May 1998 18:54:20 -0500 (EST) Cc: freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Danny Dulai said: > Quoting John S. Dyson (toor@dyson.iquest.net): > > > Quoting Daniel O'Connor (doconnor@gsoft.com.au): > > > > > > > > The speedup factor is 1.89, mmm :) > > > > This is a copy of the original code that I submitted to someone who > > cleaned it up (I am sorry that I forgot who actually took ownership.) > > I used this code, set the VIDPHYSADDR to 0xe1800000 and VIDPHYSSIZE to > 0x800000, and MSRINDEX is set to 5 (??) and experienced NO speed increase > at all when using xengine. > If the (VGA/System)bios works right, then fastvid isn't needed. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 17:17:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00327 for freebsd-current-outgoing; Sat, 30 May 1998 17:17:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00322 for ; Sat, 30 May 1998 17:17:11 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA00922; Sat, 30 May 1998 17:12:41 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Eivind Eklund cc: Julian Elischer , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sun, 31 May 1998 01:53:19 +0200." <19980531015319.33329@follo.net> Date: Sat, 30 May 1998 17:12:41 -0700 Message-ID: <919.896573561@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you want to be really nice, I'd say implement a reverse mapping > from the major/minor numbers for the time being. We will (of course) > get rid of this later, but it would allow an almost completely smooth > transition to DEVFS. Thanks, I couldn't have said it better myself. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 18:07:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06807 for freebsd-current-outgoing; Sat, 30 May 1998 18:07:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06796 for ; Sat, 30 May 1998 18:07:11 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id SAA18476 for ; Sat, 30 May 1998 18:07:06 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805310107.SAA18476@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: pthreads and thread-specific? In-reply-to: Your message of "Sun, 31 May 1998 10:25:00 +1000." <199805310025.KAA12864@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 18:07:06 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to get ACE up and running on -current/elf and it appears that the ACE's tests are not able to exit properly. Anyone got any clues or thread-specific tests to verify the behavior of threads? Tnks, Amancio {hasty} gdb-elf ./Barrier_Test GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... (gdb) run Starting program: /usr/home/hasty/ace/ACE_wrappers/tests/./Barrier_Test ^C Program received signal SIGINT, Interrupt. 0x2818d5f0 in gettimeofday () (gdb) bt #0 0x2818d5f0 in gettimeofday () #1 0x2819afe7 in _thread_kern_set_timeout (timeout=0x0) at /usr/src/lib/libc_r/uthread/uthread_kern.c:680 #2 0x28199f25 in pthread_yield () at /usr/src/lib/libc_r/uthread/uthread_yield.c:48 #3 0x2819a0ad in _spinlock (lck=0x281d5c04) at /usr/src/lib/libc_r/uthread/uthread_spinlock.c:65 #4 0x2819a221 in _thread_cleanupspecific () at /usr/src/lib/libc_r/uthread/uthread_spec.c:178 #5 0x2819c7de in pthread_exit () at /usr/src/lib/libc_r/uthread/uthread_exit.c:180 #6 0x2816de50 in _thread_start () at /usr/src/lib/libc_r/uthread/uthread_create.c:205 ============= ACTIVE THREADS -------------------- Thread 0x8050a00 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthr ead_cond.c:331] -------------------- Thread 0x8050800 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthr ead_cond.c:331] This is the running thread -------------------- Thread 0x8050400 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthr ead_cond.c:331] -------------------- Thread 0x8050200 () prio 64 state Waiting on a condition variable [/usr/src /lib/libc_r/uthread/uthread_cond.c:163] This is the initial thread DEAD THREADS Thread 0x8050600 prio 64 [/usr/src/lib/libc_r/uthread/uthread_exit.c:176] ============= FILE DESCRIPTOR TABLE fd[ 5] read owner 0x0 count 0 [/usr/src/lib/libc_r/uthread/uthread_fstat.c: 49] write owner 0x0 count 0 [/usr/src/lib/libc_r/uthread/uthread_write.c :55] ~ ~ ~ ~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 18:21:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08393 for freebsd-current-outgoing; Sat, 30 May 1998 18:21:47 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gorillanet.gorilla.net (gorillanet.gorilla.net [208.128.8.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA08386 for ; Sat, 30 May 1998 18:21:45 -0700 (PDT) (envelope-from tom@gorilla.net) Received: from [208.143.84.103] by gorillanet.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id qa151674 for ; Sat, 30 May 1998 20:21:03 -0500 Received: (from tom@localhost) by gorilla.net (8.8.8/8.8.8) id UAA00317; Sat, 30 May 1998 20:21:36 -0500 (CDT) (envelope-from tom) Message-ID: <19980530202106.26856@TOJ.org> Date: Sat, 30 May 1998 20:21:06 -0500 From: Tom Jackson To: FreeBSD Current Subject: devfs/slice disk problem Mail-Followup-To: FreeBSD Current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After shooting myself a few times in the foot, was wondering if anybody knows how to remedy this without disk remake: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #22: Thu May 28 22:52:50 CDT 1998 root@peeper.TOJ.org:/usr/src/sys/compile/TWO-PEEP Timecounter "i8254" frequency 1193182 Hz cost 3244 ns CPU: Pentium II (686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80fbff real memory = 134217728 (131072K bytes) avail memory = 127574016 (124584K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 DEVFS: ready for devices [snipped] yep sd0s1: type 6. Leaving sd0s2: attaching disklabel.. part 0, start=0, size=102400 part 1, start=102400, size=524288 part 4, start=626688, size=1677336 part 5, start=2304024, size=843764 part 6, start=3147788, size=843764 sd0s3: attaching disklabel.. part 4, start=0, size=537109 part 5, start=537109, size=1074218 part 6, start=1611327, size=1332000 part 7, start=2943327, size=1050273 sd1: probing for MBR.. rejected.. multiple active nope ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sd1: probing for disklabel.. nope ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ sd2: probing for MBR.. yep sd2s1: attaching disklabel.. part 4, start=0, size=488254 part 5, start=488254, size=567264 part 6, start=1055518, size=1076418 sd3: probing for MBR.. yep [snipped] Tried rebuilding mbr, that didn't work. Stumped, any ideas? -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 18:25:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08827 for freebsd-current-outgoing; Sat, 30 May 1998 18:25:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08819 for ; Sat, 30 May 1998 18:24:59 -0700 (PDT) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id BAA04321; Sun, 31 May 1998 01:17:36 GMT Date: Sun, 31 May 1998 10:17:36 +0900 (JST) From: Michael Hancock To: Eivind Eklund cc: Julian Elischer , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-Reply-To: <19980531015319.33329@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 31 May 1998, Eivind Eklund wrote: > If you want to be really nice, I'd say implement a reverse mapping > from the major/minor numbers for the time being. We will (of course) > get rid of this later, but it would allow an almost completely smooth > transition to DEVFS. Ok, but would you care to elaborate on some of the dirty details and creating a coherent outline that Julian can follow? Be sure to include things like handling aliases and how to keep the vnode, name cache, and major/minor reverse mapping in sync. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 18:29:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09275 for freebsd-current-outgoing; Sat, 30 May 1998 18:29:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09265 for ; Sat, 30 May 1998 18:29:28 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA00927 for current@freebsd.org; Sat, 30 May 1998 20:29:23 -0500 (EST) (envelope-from toor) Message-Id: <199805310129.UAA00927@dyson.iquest.net> Subject: Generic suggestion about -current problem messages To: current@FreeBSD.ORG Date: Sat, 30 May 1998 20:29:23 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wanted to remind people who talk about bugs in -current. Please state the date of the -current that you downloaded/checked out. Current has so many changes and improvements, it is very difficult to tell if the problem that is being reported has already been fixed. Geesh, it is even possible to talk about -current not supporting Ultra/DMA. (Of course, that would be 2.2-current :-)). -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 18:31:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09484 for freebsd-current-outgoing; Sat, 30 May 1998 18:31:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09459 for ; Sat, 30 May 1998 18:31:12 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id LAA13018; Sun, 31 May 1998 11:39:35 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805310139.LAA13018@cimlogic.com.au> Subject: Re: pthreads and thread-specific? In-Reply-To: <199805310107.SAA18476@rah.star-gate.com> from Amancio Hasty at "May 30, 98 06:07:06 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 31 May 1998 11:39:35 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > I am trying to get ACE up and running on -current/elf and it appears > that the ACE's tests are not able to exit properly. Anyone got any > clues or thread-specific tests to verify the behavior of threads? [...] > #1 0x2819afe7 in _thread_kern_set_timeout (timeout=0x0) > at /usr/src/lib/libc_r/uthread/uthread_kern.c:680 > #2 0x28199f25 in pthread_yield () > at /usr/src/lib/libc_r/uthread/uthread_yield.c:48 > #3 0x2819a0ad in _spinlock (lck=0x281d5c04) > at /usr/src/lib/libc_r/uthread/uthread_spinlock.c:65 > #4 0x2819a221 in _thread_cleanupspecific () > at /usr/src/lib/libc_r/uthread/uthread_spec.c:178 You didn't answer my question (from private mail). What is the value in key_table[key].access_lock in this function? Is it valid (i.e. one of the threads below), or is it bogus? I have test applications that use this stuff and those tests pass, so there must either be a race condition, a corruption or another path thought the code that I haven't tested. You need to answer my question before I can answer yours! > #5 0x2819c7de in pthread_exit () > at /usr/src/lib/libc_r/uthread/uthread_exit.c:180 > #6 0x2816de50 in _thread_start () > at /usr/src/lib/libc_r/uthread/uthread_create.c:205 > > > ============= > ACTIVE THREADS > > -------------------- > Thread 0x8050a00 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthr > ead_cond.c:331] > -------------------- > Thread 0x8050800 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthr > ead_cond.c:331] > This is the running thread > -------------------- > Thread 0x8050400 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthr > ead_cond.c:331] > -------------------- > Thread 0x8050200 () prio 64 state Waiting on a condition variable [/usr/src > /lib/libc_r/uthread/uthread_cond.c:163] > This is the initial thread > > > DEAD THREADS > > Thread 0x8050600 prio 64 [/usr/src/lib/libc_r/uthread/uthread_exit.c:176] > > > ============= > FILE DESCRIPTOR TABLE > > fd[ 5] read owner 0x0 count 0 [/usr/src/lib/libc_r/uthread/uthread_fstat.c: > 49] > write owner 0x0 count 0 [/usr/src/lib/libc_r/uthread/uthread_write.c > :55] > ~ > ~ > ~ > ~ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 18:39:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10290 for freebsd-current-outgoing; Sat, 30 May 1998 18:39:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10285 for ; Sat, 30 May 1998 18:39:13 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id SAA18592; Sat, 30 May 1998 18:39:04 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805310139.SAA18592@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: pthreads and thread-specific? In-reply-to: Your message of "Sun, 31 May 1998 11:39:35 +1000." <199805310139.LAA13018@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 18:39:04 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Just give me a few more minutes to try to answer your question. kill -INFO 8862 {hasty} gdb-elf ./Task_Test GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... (gdb) run Starting program: /usr/home/hasty/ace/ACE_wrappers/tests/./Task_Test Program received signal ?, Unknown signal. 0x2819c3b8 in _thread_kern_set_timeout (timeout=0x0) at /usr/src/lib/libc_r/uthread/uthread_kern.c:680 680 } Current language: auto; currently c ------------------------ However if I issue the signal without running the program under gdb the SIGINFO is interpreted correctly. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 19:00:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12202 for freebsd-current-outgoing; Sat, 30 May 1998 19:00:44 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from heathers2.stdio.com (lile@heathers2.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12197 for ; Sat, 30 May 1998 19:00:42 -0700 (PDT) (envelope-from lile@stdio.com) Received: (from lile@localhost) by heathers2.stdio.com (8.8.8/8.8.8) id VAA04396; Sat, 30 May 1998 21:58:08 -0400 (EDT) Date: Sat, 30 May 1998 21:58:07 -0400 (EDT) From: "Larry S. Lile" To: current@FreeBSD.ORG Subject: Need help with make world on 3.0-current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just cvsup'd 3.0-current (5/30) and I cannot get make world to finish. I keep getting "undefined symbol `___error` referenced from text segment" when the build fails. Also most of the ports I have tried to compile die with the same error. Is there any way to get current to build or is the tree just broken for now? Larry Lile lile@stdio.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 19:04:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12748 for freebsd-current-outgoing; Sat, 30 May 1998 19:04:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gorillanet.gorilla.net (gorillanet.gorilla.net [208.128.8.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA12743 for ; Sat, 30 May 1998 19:04:19 -0700 (PDT) (envelope-from tom@gorilla.net) Received: from [208.143.84.8] by gorillanet.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id ca151712 for ; Sat, 30 May 1998 21:03:27 -0500 Received: (from tom@localhost) by gorilla.net (8.8.8/8.8.8) id VAA00712; Sat, 30 May 1998 21:04:00 -0500 (CDT) (envelope-from tom) Message-ID: <19980530210320.35350@TOJ.org> Date: Sat, 30 May 1998 21:03:20 -0500 From: Tom Jackson To: FreeBSD Current Subject: IP Packet Aliasing Broke? Mail-Followup-To: FreeBSD Current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On May 28 packet forwarding was working, on the 29 it was *not*. Any ideas or did I miss something? All I have done is make world and kernel rebuid. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 19:04:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12843 for freebsd-current-outgoing; Sat, 30 May 1998 19:04:56 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isua1.iastate.edu (isua1.iastate.edu [129.186.1.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12836 for ; Sat, 30 May 1998 19:04:54 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: (from graphix@localhost) by isua1.iastate.edu (8.8.5/8.8.5) id VAA03255 for current@freebsd.org; Sat, 30 May 1998 21:04:53 -0500 (CDT) Date: Sat, 30 May 1998 21:04:53 -0500 (CDT) From: Kent A Vander Velden Message-Id: <199805310204.VAA03255@isua1.iastate.edu> To: current@FreeBSD.ORG Subject: Undefined symbols referenced Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While compiling xdelta and gimp-devel on a semi-current system I started to notice many of applications failing to link. The messages that ld generated were of the form: 2 -pipe -Wall -o .libs/xd xd.o -R/usr/X11R6/lib -lgimpui -L/usr/local/lib -R/usr /X11R6/lib -lgimp -L/usr/local/lib -L/usr/X11R6/lib -L/usr/X11R6/lib -lgtk -lgdk -lglib -lXext -lX11 -lm -lxdelta -lglib -lgdbm -lc -L/usr/local/lib xd.o: Undefined symbol `_unlink' referenced (use -lc ?) xd.o: Undefined symbol `_stat' referenced (use -lc ?) /usr/local/lib/libgdbm.a(gdbmstore.o): Undefined symbol `_write' referenced (use -lc ?) /usr/local/lib/libgdbm.a(bucket.o): Undefined symbol `_read' referenced (use -lc ?) /usr/local/lib/libgdbm.a(bucket.o): Undefined symbol `_write' referenced (use -l c ?) I noticed a message in the current-digest about __error being undefined but got in on the end of the thread. What must I change inorder to have these applications link properly? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 19:23:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14566 for freebsd-current-outgoing; Sat, 30 May 1998 19:23:12 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14558 for ; Sat, 30 May 1998 19:23:11 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id WAA14906 for ; Sat, 30 May 1998 22:23:09 -0400 (EDT) Received: by mozart (5.65c/SAS/Domains/5-6-90) id AA23531; Sat, 30 May 1998 22:23:03 -0400 From: "John W. DeBoskey" Message-Id: <199805310223.AA23531@mozart> Subject: cdrecord & core dumps To: freebsd-current@FreeBSD.ORG Date: Sat, 30 May 1998 22:23:03 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have cdrecord working just fine under 3.0-CURRENT. If this information is out-of-date, my apologies. I posted a note a few months ago concerning sysconf() and getpagesize()... I was promptly and impolitely told I was doing it 'wrong'. Oh well... First of all, the following code is incorrect for FreeBSD. _SC_PAGESIZE is defined in the header files, but it is not supported via sysconf(), hence pagesize gets set to -1. In init_fifo() (fifo.c) #ifdef _SC_PAGESIZE pagesize = sysconf(_SC_PAGESIZE); #else pagesize = getpagesize(); #endif At this point, the code in init_fifo() makes some very bad calculations, among others, a bad buffer size. A simple change: (not portable) #ifdef _SC_PAGESIZE pagesize = sysconf(_SC_PAGESIZE); EDEBUG(("_SC_pagesize: %d\n", pagesize)); if (pagesize == -1) pagesize = getpagesize(); EDEBUG(("_SC_pagesize: %d\n", pagesize)); #else As far as posix is concerned, the following change to my kernel took care of it: # # Enable Posix priority scheduling # options "_KPOSIX_PRIORITY_SCHEDULING" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 19:24:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14689 for freebsd-current-outgoing; Sat, 30 May 1998 19:24:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14682 for ; Sat, 30 May 1998 19:24:23 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id TAA19643; Sat, 30 May 1998 19:20:48 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd019641; Sun May 31 02:20:46 1998 Date: Sat, 30 May 1998 19:20:42 -0700 (PDT) From: Julian Elischer To: Tom Jackson cc: FreeBSD Current Subject: Re: devfs/slice disk problem In-Reply-To: <19980530202106.26856@TOJ.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG using fdisk -u /dev/rsd1 remove the flags=80 for all but one of the slices.. theoretically having more than one being the boot partition doesn't make sense. I have taken that as a sign of an corrupted or nonsinsical bootblock but apparantly the sysinstall can do this.. (grumble) julian On Sat, 30 May 1998, Tom Jackson wrote: > After shooting myself a few times in the foot, was wondering > if anybody knows how to remedy this without disk remake: > > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-CURRENT #22: Thu May 28 22:52:50 CDT 1998 > root@peeper.TOJ.org:/usr/src/sys/compile/TWO-PEEP > Timecounter "i8254" frequency 1193182 Hz cost 3244 ns > CPU: Pentium II (686-class CPU) > Origin = "GenuineIntel" Id = 0x634 Stepping=4 > Features=0x80fbff > real memory = 134217728 (131072K bytes) > avail memory = 127574016 (124584K bytes) > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > DEVFS: ready for devices > [snipped] > yep > sd0s1: type 6. Leaving > sd0s2: attaching disklabel.. > part 0, start=0, size=102400 > part 1, start=102400, size=524288 > part 4, start=626688, size=1677336 > part 5, start=2304024, size=843764 > part 6, start=3147788, size=843764 > sd0s3: attaching disklabel.. > part 4, start=0, size=537109 > part 5, start=537109, size=1074218 > part 6, start=1611327, size=1332000 > part 7, start=2943327, size=1050273 > sd1: probing for MBR.. rejected.. multiple active nope > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > sd1: probing for disklabel.. nope > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > sd2: probing for MBR.. yep > sd2s1: attaching disklabel.. > part 4, start=0, size=488254 > part 5, start=488254, size=567264 > part 6, start=1055518, size=1076418 > sd3: probing for MBR.. yep > [snipped] > > Tried rebuilding mbr, that didn't work. Stumped, any > ideas? > > -- > Tom > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 19:50:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17006 for freebsd-current-outgoing; Sat, 30 May 1998 19:50:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c243.moon.jic.com [206.156.18.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16999 for ; Sat, 30 May 1998 19:50:51 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id WAA25867; Sat, 30 May 1998 22:50:42 -0400 (EDT) (envelope-from gjp@gjp.erols.com) To: Richard Cownie cc: Amancio Hasty , current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: FreeBSD on 8-way SMP PPro In-reply-to: Your message of "Fri, 29 May 1998 11:59:19 EDT." Date: Sat, 30 May 1998 22:50:42 -0400 Message-ID: <25863.896583042@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Richard Cownie wrote in message ID : > I only have 256K of DRAM so far - I could borrow a board with 4GB, but > it probably wouldn't be interesting until I have a good way of stressing > the > system (maybe "make -j32 world") ? A couple of 512Mb RAM disks, one holding /usr/src and one holding /usr/obj, and cranking make world up to see how fast you can go? :) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 19:54:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17478 for freebsd-current-outgoing; Sat, 30 May 1998 19:54:50 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17472 for ; Sat, 30 May 1998 19:54:47 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id TAA18874; Sat, 30 May 1998 19:54:35 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805310254.TAA18874@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: pthreads and thread-specific? In-reply-to: Your message of "Sun, 31 May 1998 11:39:35 +1000." <199805310139.LAA13018@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 19:54:35 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi John, It looks like the threads are waiting on a dead thread... I stuck this in uthread_info: for (pthread = _thread_link_list; pthread != NULL; pthread = pthread->nxt) { /* Find the state: */ for (j = 0; j < (sizeof(thread_info) / sizeof(struct s_thread_info)) - 1; j++) if (thread_info[j].state == pthread->state) break; /* Output a record for the current thread: */ sprintf(s, "--------------------\nThread %p (%s) prio %3d state %s [%s:%d]\n", pthread, (pthread->name == NULL) ? "":pthread->name, pthread-> pthread_priority, thread_info[j].name,pthread->fname,pthread->lineno); _thread_sys_write(fd, s, strlen(s)); ------------------------ for (itr = 0; itr < PTHREAD_DESTRUCTOR_ITERATIONS; itr++) { for (key = 0; key < PTHREAD_KEYS_MAX; key++) { if (_thread_run->specific_data_count ) { if (_thread_run->specific_data[key]) { sprintf(s, " key %d lock %x \n", key, key_table[key].access_lock); _thread_sys_write(fd, s, strlen(s)); } } } } ------------------------ ============= ACTIVE THREADS -------------------- Thread 0x8050a00 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread _cond.c:331] key 2 lock 8050800 key 2 lock 8050800 key 2 lock 8050800 key 2 lock 8050800 -------------------- Thread 0x8050600 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread _cond.c:331] key 2 lock 8050800 key 2 lock 8050800 key 2 lock 8050800 key 2 lock 8050800 This is the running thread -------------------- Thread 0x8050400 () prio 64 state Running [/usr/src/lib/libc_r/uthread/uthread _cond.c:331] key 2 lock 8050800 key 2 lock 8050800 key 2 lock 8050800 key 2 lock 8050800 -------------------- Thread 0x8050200 () prio 64 state Waiting on a condition variable [/usr/src/lib/libc_r/uthread/uthread_cond.c:163] key 2 lock 8050800 key 2 lock 8050800 key 2 lock 8050800 key 2 lock 8050800 This is the initial thread DEAD THREADS Thread 0x8050800 prio 64 [/usr/src/lib/libc_r/uthread/uthread_exit.c:176] ============= FILE DESCRIPTOR TABLE fd[ 5] read owner 0x0 count 0 [/usr/src/lib/libc_r/uthread/uthread_fstat.c:49] write owner 0x0 count 0 [/usr/src/lib/libc_r/uthread/uthread_write.c:55 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 19:59:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18088 for freebsd-current-outgoing; Sat, 30 May 1998 19:59:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles307.castles.com [208.214.167.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18068 for ; Sat, 30 May 1998 19:59:00 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA08633; Sat, 30 May 1998 18:54:47 -0700 (PDT) Message-Id: <199805310154.SAA08633@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Mikhail Teterin cc: current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... In-reply-to: Your message of "Sat, 30 May 1998 17:52:15 EDT." <199805302152.RAA17435@rtfm.ziplink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 18:54:47 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Poul-Henning Kamp once stated: > > =Removing /dev/lpt0 doesn't make sense, it doesn't remove the driver, > =it doesn't attach from the hardware, it merely removes the namesticker > =from the mailbox. > > May be this should be the semantics of `rm' on the DEVFS? Removal > of the driver, or telling it to stop driving a particular device? > (If possible, otherwise, rm fails?) mknod (or, `touch'!!) can then > be used to load the driver back (if possible). > > Too far off? Not useful. You want to poke a single entity (the driver) and have it remove all it's nodes, rather than have to guess at all the nodes everywhere that it might own and run around deleting them all. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 20:21:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20535 for freebsd-current-outgoing; Sat, 30 May 1998 20:21:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20526 for ; Sat, 30 May 1998 20:21:49 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id DAA20817; Sun, 31 May 1998 03:21:43 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id FAA10187; Sun, 31 May 1998 05:21:21 +0200 (MET DST) Message-ID: <19980531052120.41610@follo.net> Date: Sun, 31 May 1998 05:21:20 +0200 From: Eivind Eklund To: Richard Wackerbarth Cc: current@FreeBSD.ORG Subject: Re: How about /usr/ports/kernel ? References: <199805301346.PAA29505@labinfo.iet.unipi.it>; <199805301346.PAA29505@labinfo.iet.unipi.it> <19980530182913.04478@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Richard Wackerbarth on Sat, May 30, 1998 at 03:45:31PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 30, 1998 at 03:45:31PM -0500, Richard Wackerbarth wrote: > At 4:29 PM -0000 5/30/98, Eivind Eklund wrote: > > >My own view of this is that config(8) should scan for > > ../../*/conf/files.FreeBSD > > ../../*/conf/options.FreeBSD > > ../../*/conf/files.FreeBSD. > > ../../*/conf/options.FreeBSD. > >add concatenate this with the appropriate files. > > > >This would allow us to add a new subsystem (like i4b) by just adding a > >new subdir to the kernel. > > > >For some ports we would of course need to add extra kernel hooks, but > >this at least solve the easy cases. > > > >What do people think? > [...on having kernels made as a part of a normal build...] We've discussed this before (off the list), and I tend to agree to some of it. However, how is this related to the proposal above (except for both being part of the kernel build structure)? Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 20:23:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20732 for freebsd-current-outgoing; Sat, 30 May 1998 20:23:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from moon.jic.com ([206.156.0.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA20679 for ; Sat, 30 May 1998 20:23:07 -0700 (PDT) (envelope-from mbriggs@switchboard.net) Received: from switchboard.net (alex-va-n013c109.moon.jic.com [208.135.210.119]) by moon.jic.com (8.8.8/8.8.8) with ESMTP id XAA29387 for ; Sat, 30 May 1998 23:21:32 -0400 (EDT) Message-ID: <3570CD13.87BEDFA9@switchboard.net> Date: Sat, 30 May 1998 23:22:59 -0400 From: "Matthew R. Briggs" X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.1.103 i686) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: General SMP Instability SNAP-0523 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm new to FreeBSD, having come from the Debian GNU/Linux camp. I'm very impressed with what I have seen while working with the CURRENT snapshot from 0523, but stability has been an issue. I know that the CURRENT-3.0 branch is under heavy development, but I only run SMP boxen and to try FreeBSD out I had to go to CURRENT. Here is the issue: I am able to wedge the system fairly consistently (and often) with parallel makes of various pieces of software. Not the kernel, but "make world -j4" will crash it, as will compilation of FileRunner from the ports collection (along with a few other things). The system will lock hard and drop me to the kernel debugger. Since I'm new to this, what I'm asking for is a description of what information I should send to the right people to fix any bugs or to expose my own ignorance. Here is the hardware I am using to test things out: Tyan Tiger II w/2xPII-333 128MB SDRAM UDMA IDE disk (flags set to b0ffb0ff) Matrox Millenium II AGP PS/2 mouse (though I used an adapter for serial, trying to resolve conflict with the console...no improvement) Kingston KNE40T NIC (21040-based) Thanks for any and all help...I'd really like to get this to work! Matt Briggs mbriggs-at-switchboard.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 20:25:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21414 for freebsd-current-outgoing; Sat, 30 May 1998 20:25:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gorillanet.gorilla.net (gorillanet.gorilla.net [208.128.8.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA21404 for ; Sat, 30 May 1998 20:25:43 -0700 (PDT) (envelope-from tom@gorilla.net) Received: from [208.143.84.97] by gorillanet.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id aa151788 for ; Sat, 30 May 1998 22:24:55 -0500 Received: (from tom@localhost) by gorilla.net (8.8.8/8.8.8) id WAA00318; Sat, 30 May 1998 22:25:28 -0500 (CDT) (envelope-from tom) Message-ID: <19980530222458.54036@TOJ.org> Date: Sat, 30 May 1998 22:24:58 -0500 From: Tom Jackson To: FreeBSD Current Subject: Re: devfs/slice disk problem Mail-Followup-To: FreeBSD Current References: <19980530202106.26856@TOJ.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <19980530202106.26856@TOJ.org>; from Tom Jackson on Sat, May 30, 1998 at 08:21:06PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, May 30, 1998 at 08:21:06PM -0500, Tom Jackson wrote: > After shooting myself a few times in the foot, was wondering > if anybody knows how to remedy this without disk remake: > > > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-CURRENT #22: Thu May 28 22:52:50 CDT 1998 > root@peeper.TOJ.org:/usr/src/sys/compile/TWO-PEEP > Timecounter "i8254" frequency 1193182 Hz cost 3244 ns > CPU: Pentium II (686-class CPU) > Origin = "GenuineIntel" Id = 0x634 Stepping=4 > Features=0x80fbff > real memory = 134217728 (131072K bytes) > avail memory = 127574016 (124584K bytes) > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > DEVFS: ready for devices > [snipped] > yep > sd0s1: type 6. Leaving > sd0s2: attaching disklabel.. > part 0, start=0, size=102400 > part 1, start=102400, size=524288 > part 4, start=626688, size=1677336 > part 5, start=2304024, size=843764 > part 6, start=3147788, size=843764 > sd0s3: attaching disklabel.. > part 4, start=0, size=537109 > part 5, start=537109, size=1074218 > part 6, start=1611327, size=1332000 > part 7, start=2943327, size=1050273 > sd1: probing for MBR.. rejected.. multiple active nope > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > sd1: probing for disklabel.. nope > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > sd2: probing for MBR.. yep > sd2s1: attaching disklabel.. > part 4, start=0, size=488254 > part 5, start=488254, size=567264 > part 6, start=1055518, size=1076418 > sd3: probing for MBR.. yep > [snipped] > > Tried rebuilding mbr, that didn't work. Stumped, any > ideas? > Argh!! One of these days I'll learn to read error messages. Both slices, both FreeBSD were set active! Set first one active and wallah, devfs/slice started working. Now if I can just get packet forwarding working again :( -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 20:51:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24402 for freebsd-current-outgoing; Sat, 30 May 1998 20:51:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles307.castles.com [208.214.167.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24392; Sat, 30 May 1998 20:51:16 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA08863; Sat, 30 May 1998 19:47:05 -0700 (PDT) Message-Id: <199805310247.TAA08863@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: dyson@FreeBSD.ORG cc: nirva@ishiboo.com (Danny Dulai), freebsd-multimedia@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Fastvid: no speed increase :( In-reply-to: Your message of "Sat, 30 May 1998 18:54:20 CDT." <199805302354.SAA00461@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 19:47:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Danny Dulai said: > > Quoting John S. Dyson (toor@dyson.iquest.net): > > > > Quoting Daniel O'Connor (doconnor@gsoft.com.au): > > > > > > > > > > The speedup factor is 1.89, mmm :) > > > > > > This is a copy of the original code that I submitted to someone who > > > cleaned it up (I am sorry that I forgot who actually took ownership.) > > > > I used this code, set the VIDPHYSADDR to 0xe1800000 and VIDPHYSSIZE to > > 0x800000, and MSRINDEX is set to 5 (??) and experienced NO speed increase > > at all when using xengine. > > > If the (VGA/System)bios works right, then fastvid isn't needed. Many system BIOS setup programs have a "VGA buffer UC/USWC" option. The UC option is "just uncached", while the "USWC" option enables write combining. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 20:56:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25467 for freebsd-current-outgoing; Sat, 30 May 1998 20:56:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles307.castles.com [208.214.167.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25461 for ; Sat, 30 May 1998 20:56:55 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA08893; Sat, 30 May 1998 19:52:37 -0700 (PDT) Message-Id: <199805310252.TAA08893@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: cdrecord & core dumps In-reply-to: Your message of "Sat, 30 May 1998 22:23:03 EDT." <199805310223.AA23531@mozart> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 19:52:37 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > First of all, the following code is incorrect for FreeBSD. > _SC_PAGESIZE is defined in the header files, but it is not supported > via sysconf(), hence pagesize gets set to -1. > > In init_fifo() (fifo.c) > > #ifdef _SC_PAGESIZE > pagesize = sysconf(_SC_PAGESIZE); > #else > pagesize = getpagesize(); > #endif I've actually patched this to: int pagesize = -1; #ifdef _SC_PAGESIZE pagesize = sysconf(_SC_PAGESIZE); #endif if (pagesize == -1) pagesize = getpagesize(); Which is about as readable as is reasonable. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 21:14:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27252 for freebsd-current-outgoing; Sat, 30 May 1998 21:14:27 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles307.castles.com [208.214.167.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27246; Sat, 30 May 1998 21:14:16 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id UAA09016; Sat, 30 May 1998 20:09:41 -0700 (PDT) Message-Id: <199805310309.UAA09016@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: tcobb cc: "'shimon@simon-shapiro.org'" , "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: DPT Redux In-reply-to: Your message of "Sat, 30 May 1998 03:08:21 EDT." <509A2986E5C5D111B7DD0060082F32A402FAE8@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 20:09:41 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I shutdown and rebooted machine (SYNC failed on shutdown) > Allowed FreeBSD to boot, it returned the following for sd1 > sd1: type 0 fixed SCSI 2 > sd1: Direct-Access 0MB (1 512 byte sectors) > > Then, system continued booting and finally panic'd with a "Page Fault in > Supervisor Mode" error prior to mounting drives. Did you happen to write down the details from this message? In conjunction with your kernel image, these are required in order to determine what happened. It's possible that something doesn't like being asked to boot from a zero-sized disk. It's also possible that something else later got upset - it's not clear where in the chain of events the panic occurred (see above). Thanks for the extra info. Are you able to simulate the failure by eg. disconnecting one of the 'active' drives? If you can't do this on a regular basis, I believe we are able to arrange temporary access to a similar but idle system where this can be simulate. Simon may also be able to offer some suggestions inre. possible poor interaction between the dpt driver and some firmware revisions. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 21:24:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28396 for freebsd-current-outgoing; Sat, 30 May 1998 21:24:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from m2.findmail.com (m2.findmail.com [209.185.96.135]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA28391 for ; Sat, 30 May 1998 21:24:37 -0700 (PDT) (envelope-from brianfeldman@hotmail.com) Received: (qmail 16102 invoked by uid 505); 31 May 1998 04:24:32 -0000 Date: 31 May 1998 04:24:32 -0000 Message-ID: <19980531042432.16101.qmail@m2.findmail.com> From: "Brian Feldman" Subject: fd crash (in isa_dmastart) To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, out of curiousity, I wanted to try SoftUpdates on a floppy. Let's just say that SoftUpdates on a floppy is a Bad Thing, causing Too Much Disk Access and A Bad Panic. (out out evil capitals!) Here's the bt, for those interested, and I'll delete this huge vmcore tomorrow if noone tells me not to and we don't want to try to get any more info out of it: (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:281 #1 0xf0118fc7 in panic (fmt=0xf01f1f56 "isa_dmastart: bad bounce buffer") at ../../kern/kern_shutdown.c:421 #2 0xf01f1fcf in isa_dmastart (flags=587333684, addr=0xf2d4d014 "ð\004", nbytes=4096, chan=2) at ../../i386/isa/isa.c:767 #3 0xf01ec1fd in fdstate (fdcu=0, fdc=0xf02622d4) at ../../i386/isa/fd.c:1640 #4 0xf01ebcb3 in fdintr (fdcu=0) at ../../i386/isa/fd.c:1445 #5 0xf01ebc75 in fd_pseudointr (arg1=0x0) at ../../i386/isa/fd.c:1425 #6 0xf011d203 in softclock () at ../../kern/kern_timeout.c:124 #7 0xf01d6cc7 in doreti_swi () Cannot access memory at address 0x274e35f8. Now I'm relatively certain that this was specifically caused by way to much disk access on SoftUpdates' part; any idea how we should fix this? Cheers, Brian Feldman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 21:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28809 for freebsd-current-outgoing; Sat, 30 May 1998 21:26:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28793; Sat, 30 May 1998 21:26:51 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Sun, 31 May 1998 00:26:12 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAF6@freya.circle.net> From: tcobb To: "'Mike Smith'" Cc: "'shimon@simon-shapiro.org'" , "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" Subject: RE: DPT Redux Date: Sun, 31 May 1998 00:26:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Mike Smith [mailto:mike@smith.net.au] > > I shutdown and rebooted machine (SYNC failed on shutdown) > > Allowed FreeBSD to boot, it returned the following for sd1 > > sd1: type 0 fixed SCSI 2 > > sd1: Direct-Access 0MB (1 512 byte sectors) > > > > Then, system continued booting and finally panic'd with a > "Page Fault in > > Supervisor Mode" error prior to mounting drives. > > Did you happen to write down the details from this message? In > conjunction with your kernel image, these are required in order to > determine what happened. This is the one thing I neglected to do, unfortunately - I just got the error name, not the rest of the info. The situation was a surprise and had become an emergency at the point it was clear that FreeBSD wasn't going to reboot. The kernel file I can certainly supply. > It's possible that something doesn't like being asked to boot from a > zero-sized disk. It's also possible that something else later got > upset - it's not clear where in the chain of events the panic > occurred > (see above). Actually, it wasn't booting from the "zero-sized" disk. From my earlier email, I noted that I have two arrays configured, the first sd0, is the boot disk and RAID-1 and contains all relevant system directories, the second sd1, is simply an NFS export partition and is RAID-5. It was the second disk (sd1) which showed the "0 MB/1 sector" problem. > Thanks for the extra info. Are you able to simulate the > failure by eg. > disconnecting one of the 'active' drives? If you can't do this on a > regular basis, I believe we are able to arrange temporary access to a > similar but idle system where this can be simulate. Simon > may also be > able to offer some suggestions inre. possible poor > interaction between > the dpt driver and some firmware revisions. I'm hoping to be able to create a duplicate array to this one for testing, also. I'm getting resistance to budgeting additional funds for DPT/FreeBSD at the moment :( The machine in question is currently (and still) a live NFS server. I'm working on scheduling some downtime for it in the next few days get a hotswap drive back in there. I expect that I'll have to keep it down (1.5hrs) for a complete array rebuild on the RAID-5 given the interactions I've seen recently. My instinct is that, assuming someone could setup a RAID-5 array with HOT SWAP disk, and then yanked a live drive, that they'd see the same symptoms that I did. Or, even simpler would be to tell the array to rebuild, then try to boot FreeBSD... -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 21:28:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29128 for freebsd-current-outgoing; Sat, 30 May 1998 21:28:09 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29110 for ; Sat, 30 May 1998 21:28:05 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id OAA13342; Sun, 31 May 1998 14:36:29 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805310436.OAA13342@cimlogic.com.au> Subject: Re: Need help with make world on 3.0-current In-Reply-To: from "Larry S. Lile" at "May 30, 98 09:58:07 pm" To: lile@stdio.com (Larry S. Lile) Date: Sun, 31 May 1998 14:36:29 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Larry S. Lile wrote: > > I just cvsup'd 3.0-current (5/30) and I cannot get make world > to finish. I keep getting "undefined symbol `___error` referenced > from text segment" when the build fails. Also most of the ports > I have tried to compile die with the same error. > > Is there any way to get current to build or is the tree just broken > for now? make world should build and install libc and headers together, without trying to link any programs in between. If you've installed includes manually, then you have to build and install libc manually. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 21:37:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00162 for freebsd-current-outgoing; Sat, 30 May 1998 21:37:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00156 for ; Sat, 30 May 1998 21:37:25 -0700 (PDT) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id XAA00448; Sat, 30 May 1998 23:37:20 -0500 (EST) (envelope-from toor) Message-Id: <199805310437.XAA00448@dyson.iquest.net> Subject: Re: General SMP Instability SNAP-0523 In-Reply-To: <3570CD13.87BEDFA9@switchboard.net> from "Matthew R. Briggs" at "May 30, 98 11:22:59 pm" To: mbriggs@switchboard.net (Matthew R. Briggs) Date: Sat, 30 May 1998 23:37:20 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew R. Briggs said: > Hello, > I'm new to FreeBSD, having come from the Debian GNU/Linux camp. I'm > very impressed with what I have seen while working with the CURRENT > snapshot from 0523, but stability has been an issue. I know that the > CURRENT-3.0 branch is under heavy development, but I only run SMP boxen > and to try FreeBSD out I had to go to CURRENT. > Here is the issue: I am able to wedge the system fairly consistently > (and often) with parallel makes of various pieces of software. Not the > kernel, but "make world -j4" will crash it, as will compilation of > FileRunner from the ports collection (along with a few other things). > The system will lock hard and drop me to the kernel debugger. > Since I'm new to this, what I'm asking for is a description of what > information I should send to the right people to fix any bugs or to > expose my own ignorance. Here is the hardware I am using to test things > out: > I am working like a mad-man on the SMP context switching and other like code. I will have a new SMP upgrade snapshot in my www.freebsd.org:~dyson directory at the end of the weekend. Alot of our diagnostic info is pretty rough, but feel free to send me/post any info that you feel will be useful. Useful kernel debugger commands are "ps" and "trace". Those will sometimes give a useful pointer to some troubles. However, with SMP, the system sometimes gets into a state where the traceback is useless (in my private working sources, and soon to be committed, or at least in my SMP update(s), stack tracebacks will work better, due to maintaining frame pointer.) One warning is that softupdates tends to make the system less stable also. SMP and softupdates can be challenging :-). > > Thanks for any and all help...I'd really like to get this to work! > I would like to be able to help, others will likely also try to chip in. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 21:39:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00416 for freebsd-current-outgoing; Sat, 30 May 1998 21:39:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00404 for ; Sat, 30 May 1998 21:39:06 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id OAA13356; Sun, 31 May 1998 14:47:20 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805310447.OAA13356@cimlogic.com.au> Subject: Re: Undefined symbols referenced In-Reply-To: <199805310204.VAA03255@isua1.iastate.edu> from Kent A Vander Velden at "May 30, 98 09:04:53 pm" To: graphix@iastate.edu (Kent A Vander Velden) Date: Sun, 31 May 1998 14:47:20 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent A Vander Velden wrote: > > While compiling xdelta and gimp-devel on a semi-current system I started > to notice many of applications failing to link. The messages that ld What is a "semi-current system" ?? It looks to me as though you've updated to a -current libc (with weak symbols for the syscalls), but your linker doesn't know about weak symbols. Is that possible? It's surprising. If you run "nm -W /usr/lib/libc.a | grep _read", do you see: 00000008 T __read 00000008 TW _read (plus many other references)? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 22:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA02726 for freebsd-current-outgoing; Sat, 30 May 1998 22:01:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA02713 for ; Sat, 30 May 1998 22:01:38 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id PAA13433; Sun, 31 May 1998 15:09:57 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805310509.PAA13433@cimlogic.com.au> Subject: Re: pthreads and thread-specific? In-Reply-To: <199805310254.TAA18874@rah.star-gate.com> from Amancio Hasty at "May 30, 98 07:54:35 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 31 May 1998 15:09:57 +1000 (EST) Cc: jb@cimlogic.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > Hi John, > > It looks like the threads are waiting on a dead thread... > > I stuck this in uthread_info: [...] I don't think you needed the outer loop. Chuckle. > for (itr = 0; itr < PTHREAD_DESTRUCTOR_ITERATIONS; itr++) { [...] > > DEAD THREADS > > Thread 0x8050800 prio 64 [/usr/src/lib/libc_r/uthread/uthread_exit.c:176] Hmmm, so Elvis really isn't dead. He's just deadlocked waiting on a spinlock. 8-) For the thread to be dead, it must have completed the cleanup. There is only one place where it sets it's state to PS_DEAD and that is after all exit processing has been completed and it has removed itself from the list of active threads. As far as I can see, the _spinlock/_atomic_unlock calls are correctly paired in src/lib/libc_r/uthread/uthread_spec.c, so it looks like the _atomic_unlock call hasn't done it's job. Is the _atomic_unlock linked into the process from libc_r, or has another function of the same name been linked in first? You are linking with gcc -pthread on a -current system, aren't you? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 22:07:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03383 for freebsd-current-outgoing; Sat, 30 May 1998 22:07:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isua3.iastate.edu (isua3.iastate.edu [129.186.1.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03378 for ; Sat, 30 May 1998 22:07:42 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua3.iastate.edu (8.8.5/8.8.5) with SMTP id AAA09076; Sun, 31 May 1998 00:07:30 -0500 (CDT) Message-Id: <199805310507.AAA09076@isua3.iastate.edu> To: John Birrell Cc: current@FreeBSD.ORG Subject: Re: Undefined symbols referenced In-reply-to: Your message of "Sun, 31 May 1998 14:47:20 +1000." <199805310447.OAA13356@cimlogic.com.au> Date: Sun, 31 May 1998 00:07:28 CDT From: "Kent Vander Velden" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199805310447.OAA13356@cimlogic.com.au>, John Birrell writes: >It looks to me as though you've updated to a -current libc (with weak >symbols for the syscalls), but your linker doesn't know about weak >symbols. Is that possible? It's surprising. Here are the dates on the linker and the libraries: namedb|Sun12:04am} file /usr/lib/libc.so.3.1 /usr/lib/libc.so.3.1: FreeBSD/i386 compact demand paged shared library not stripped namedb|Sun12:04am} file /usr/lib/libc.a /usr/lib/libc.a: current ar archive random library namedb|Sun12:05am} ls -l /usr/bin/ld -r-xr-xr-x 1 bin bin 122880 May 14 03:41 /usr/bin/ld* namedb|Sun12:05am} ls -l /usr/lib/libc* -r--r--r-- 1 bin bin 600382 May 14 03:37 /usr/lib/libc.a -r--r--r-- 1 bin bin 435727 Jun 28 1996 /usr/lib/libc.so.2.2 -r--r--r-- 1 bin bin 458179 Dec 18 22:42 /usr/lib/libc.so.3.0 -r--r--r-- 1 bin bin 475277 May 14 03:37 /usr/lib/libc.so.3.1 >If you run "nm -W /usr/lib/libc.a | grep _read", do you see: > >00000008 T __read >00000008 TW _read > >(plus many other references)? Yes and several others. Here is the complete output: namedb|Sat11:59pm} nm -W /usr/lib/libc.a | grep _read nm: U _readlink utf2.o: no name list U _read U _read nm: U _read mskanji.o: no name list U _read nm: euc.o: no name list nm: U _readdir U _readdir 0000035c T _fts_read U _readdir bt_debug.o: no name list aio_read.o: 00000008 T __aio_read 00000008 TW _aio_read U _read U _read U _readdir U _read U _read U _readv U _read 00000008 T __readv 00000008 TW _readv U _read U _read U _readdir U _readdir 00000000 T _readdir U _read U _read U _read U _read U _read U _readlink U _read 00000008 T __readlink 00000008 TW _readlink 00000008 T __read 00000008 TW _read Thanks. --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 22:15:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04123 for freebsd-current-outgoing; Sat, 30 May 1998 22:15:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04111 for ; Sat, 30 May 1998 22:15:49 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id PAA13470; Sun, 31 May 1998 15:24:18 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805310524.PAA13470@cimlogic.com.au> Subject: Re: Undefined symbols referenced In-Reply-To: <199805310507.AAA09076@isua3.iastate.edu> from Kent Vander Velden at "May 31, 98 00:07:28 am" To: graphix@iastate.edu (Kent Vander Velden) Date: Sun, 31 May 1998 15:24:18 +1000 (EST) Cc: jb@cimlogic.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Vander Velden wrote: [..] > 00000008 T __read > 00000008 TW _read Hmm, both libc and ld should be OK. Does a simple program (without all the -L paths) link correctly? Does a make buildworld with your sources succeed in linking `make'? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 22:21:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04600 for freebsd-current-outgoing; Sat, 30 May 1998 22:21:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04595 for ; Sat, 30 May 1998 22:21:12 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA19570; Sat, 30 May 1998 22:21:00 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805310521.WAA19570@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: pthreads and thread-specific? In-reply-to: Your message of "Sun, 31 May 1998 15:09:57 +1000." <199805310509.PAA13433@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 22:21:00 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG {hasty} ldd Barrier_Test Barrier_Test: libACE.so => /usr/lib/libACE.so (0x28052000) libc_r.so.3 => /usr/lib/libc_r.so.3 (0x2815b000) libstdc++.so.2 => /usr/lib/libstdc++.so.2 (0x281e3000) libg++.so.4 => /usr/lib/libg++.so.4 (0x2821a000) libm.so.2 => /usr/lib/libm.so.2 (0x28257000) libc.so.3 => /usr/lib/libc.so.3 (0x28271000) libc_r.so.3 => /usr/lib/libc_r.so.3 (0x2815b000) libstdc++.so.2 => /usr/lib/libstdc++.so.2 (0x281e3000) libg++.so.4 => /usr/lib/libg++.so.4 (0x2821a000) libm.so.2 => /usr/lib/libm.so.2 (0x28257000) Looks like I am pulling the right libraries. I will browse at the code a little bit more. Tnks, amancio > Amancio Hasty wrote: > > Hi John, > > > > It looks like the threads are waiting on a dead thread... > > > > I stuck this in uthread_info: > [...] > > I don't think you needed the outer loop. Chuckle. > > > for (itr = 0; itr < PTHREAD_DESTRUCTOR_ITERATIONS; itr++) { > [...] > > > > DEAD THREADS > > > > Thread 0x8050800 prio 64 [/usr/src/lib/libc_r/uthread/uthread_exit.c:176] > > Hmmm, so Elvis really isn't dead. He's just deadlocked waiting on a > spinlock. 8-) > > For the thread to be dead, it must have completed the cleanup. There is > only one place where it sets it's state to PS_DEAD and that is after all > exit processing has been completed and it has removed itself from the > list of active threads. As far as I can see, the _spinlock/_atomic_unlock > calls are correctly paired in src/lib/libc_r/uthread/uthread_spec.c, > so it looks like the _atomic_unlock call hasn't done it's job. Is the > _atomic_unlock linked into the process from libc_r, or has another > function of the same name been linked in first? You are linking with > gcc -pthread on a -current system, aren't you? > > -- > John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ > CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 22:22:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04796 for freebsd-current-outgoing; Sat, 30 May 1998 22:22:04 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isua3.iastate.edu (isua3.iastate.edu [129.186.1.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04791 for ; Sat, 30 May 1998 22:22:03 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua3.iastate.edu (8.8.5/8.8.5) with SMTP id AAA08254; Sun, 31 May 1998 00:21:40 -0500 (CDT) Message-Id: <199805310521.AAA08254@isua3.iastate.edu> To: John Birrell Cc: current@FreeBSD.ORG Subject: Re: Undefined symbols referenced In-reply-to: Your message of "Sun, 31 May 1998 15:24:18 +1000." <199805310524.PAA13470@cimlogic.com.au> Date: Sun, 31 May 1998 00:21:39 CDT From: "Kent Vander Velden" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199805310524.PAA13470@cimlogic.com.au>, John Birrell writes: >Kent Vander Velden wrote: >[..] >> 00000008 T __read >> 00000008 TW _read > >Hmm, both libc and ld should be OK. Does a simple program (without all >the -L paths) link correctly? Does a make buildworld with your sources >succeed in linking `make'? Other applications simple and complex have built without a problem. A "make world" has been running for the past couple of hours without problem. not sure why the problem only shows up with some applications. Thanks. --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 22:30:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05774 for freebsd-current-outgoing; Sat, 30 May 1998 22:30:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05759 for ; Sat, 30 May 1998 22:30:31 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id PAA13512; Sun, 31 May 1998 15:38:56 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805310538.PAA13512@cimlogic.com.au> Subject: Re: pthreads and thread-specific? In-Reply-To: <199805310521.WAA19570@rah.star-gate.com> from Amancio Hasty at "May 30, 98 10:21:00 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 31 May 1998 15:38:56 +1000 (EST) Cc: jb@cimlogic.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > {hasty} ldd Barrier_Test > Barrier_Test: > libACE.so => /usr/lib/libACE.so (0x28052000) > libc_r.so.3 => /usr/lib/libc_r.so.3 (0x2815b000) > libstdc++.so.2 => /usr/lib/libstdc++.so.2 (0x281e3000) > libg++.so.4 => /usr/lib/libg++.so.4 (0x2821a000) > libm.so.2 => /usr/lib/libm.so.2 (0x28257000) > libc.so.3 => /usr/lib/libc.so.3 (0x28271000) > libc_r.so.3 => /usr/lib/libc_r.so.3 (0x2815b000) If you used gcc -pthread to link the program, libc shouldn't be there _at all_ and libc_r should be last. If this list is the order that the linker resolved symbols, then any libc/libc_r functions that libstdc++ and libg++ reference (that haven't already been referenced by libACE and directly by your application) will use those from libc, not libc_r. > libstdc++.so.2 => /usr/lib/libstdc++.so.2 (0x281e3000) > libg++.so.4 => /usr/lib/libg++.so.4 (0x2821a000) > libm.so.2 => /usr/lib/libm.so.2 (0x28257000) > > Looks like I am pulling the right libraries. I will browse at the > code a little bit more. I beg to differ. Please link your application properly using gcc -pthread and don't declare libc_r on the command line. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 22:33:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06138 for freebsd-current-outgoing; Sat, 30 May 1998 22:33:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06131 for ; Sat, 30 May 1998 22:33:55 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA19647; Sat, 30 May 1998 22:33:43 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199805310533.WAA19647@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: current@FreeBSD.ORG Subject: Re: pthreads and thread-specific? In-reply-to: Your message of "Sun, 31 May 1998 15:38:56 +1000." <199805310538.PAA13512@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 30 May 1998 22:33:43 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, Now I get this: {root} gmake Task_Test g++ -pthread -Wall -Wpointer-arith -pipe -D_THREAD_SAFE -O -pipe -g -g -fno-implicit-templates -I. -I/usr/home/hasty/ace/ACE_wrappers -o Task_Test .obj/Task_Test.o -L/usr/home/hasty/ace/ACE_wrappers/ace -L./ -lACE -lstdc++ -lcompat /usr/lib/libc_r.so: undefined reference to `fchdir' /usr/home/hasty/ace/ACE_wrappers/ace/libACE.so: undefined reference to `mkfifo' /usr/home/hasty/ace/ACE_wrappers/ace/libACE.so: undefined reference to `sendmsg' /usr/home/hasty/ace/ACE_wrappers/ace/libACE.so: undefined reference to `recvmsg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 22:35:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06403 for freebsd-current-outgoing; Sat, 30 May 1998 22:35:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06382 for ; Sat, 30 May 1998 22:35:15 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id PAA13538; Sun, 31 May 1998 15:43:45 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805310543.PAA13538@cimlogic.com.au> Subject: Re: Undefined symbols referenced In-Reply-To: <199805310521.AAA08254@isua3.iastate.edu> from Kent Vander Velden at "May 31, 98 00:21:39 am" To: graphix@iastate.edu (Kent Vander Velden) Date: Sun, 31 May 1998 15:43:45 +1000 (EST) Cc: jb@cimlogic.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Vander Velden wrote: > Other applications simple and complex have built without a problem. > A "make world" has been running for the past couple of hours without > problem. not sure why the problem only shows up with some applications. If it is a `make world' and it hasn't done the final install, it will be doing everything in the /usr/obj tree. You won't know if other applications have a problem until the make world completes and _then_ you try building the applications. While the `make world' is running, any application you build separately will use the previously installed tools, headers and libraries. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 22:42:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA07072 for freebsd-current-outgoing; Sat, 30 May 1998 22:42:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA07064 for ; Sat, 30 May 1998 22:42:51 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id PAA13565; Sun, 31 May 1998 15:51:11 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805310551.PAA13565@cimlogic.com.au> Subject: Re: pthreads and thread-specific? In-Reply-To: <199805310533.WAA19647@rah.star-gate.com> from Amancio Hasty at "May 30, 98 10:33:43 pm" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Sun, 31 May 1998 15:51:11 +1000 (EST) Cc: jb@cimlogic.com.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > Okay, > > Now I get this: > > {root} gmake Task_Test > g++ -pthread -Wall -Wpointer-arith -pipe -D_THREAD_SAFE -O -pipe -g -g > -fno-implicit-templates -I. -I/usr/home/hasty/ace/ACE_wrappers -o > Task_Test .obj/Task_Test.o -L/usr/home/hasty/ace/ACE_wrappers/ace -L./ -lACE > -lstdc++ -lcompat > /usr/lib/libc_r.so: undefined reference to `fchdir' > /usr/home/hasty/ace/ACE_wrappers/ace/libACE.so: undefined reference to `mkfifo' > /usr/home/hasty/ace/ACE_wrappers/ace/libACE.so: undefined reference to > `sendmsg' > /usr/home/hasty/ace/ACE_wrappers/ace/libACE.so: undefined reference to `recvmsg Looks like we might be missing some wrappers in libc_r. 8-( Must be time for you to sleep while I fill in the gaps (I have to go out for a few hours). -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat May 30 23:59:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14250 for freebsd-current-outgoing; Sat, 30 May 1998 23:59:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isua1.iastate.edu (isua1.iastate.edu [129.186.1.201]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14243 for ; Sat, 30 May 1998 23:59:55 -0700 (PDT) (envelope-from graphix@iastate.edu) Received: from localhost (graphix@localhost) by isua1.iastate.edu (8.8.5/8.8.5) with SMTP id BAA15247; Sun, 31 May 1998 01:59:42 -0500 (CDT) Message-Id: <199805310659.BAA15247@isua1.iastate.edu> To: John Birrell Cc: current@FreeBSD.ORG Subject: Re: Undefined symbols referenced In-reply-to: Your message of "Sun, 31 May 1998 15:43:45 +1000." <199805310543.PAA13538@cimlogic.com.au> Date: Sun, 31 May 1998 01:59:42 CDT From: "Kent Vander Velden" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199805310543.PAA13538@cimlogic.com.au>, John Birrell writes: >Kent Vander Velden wrote: >> Other applications simple and complex have built without a problem. >> A "make world" has been running for the past couple of hours without >> problem. not sure why the problem only shows up with some applications. > >If it is a `make world' and it hasn't done the final install, it will >be doing everything in the /usr/obj tree. You won't know if other >applications have a problem until the make world completes and _then_ >you try building the applications. While the `make world' is running, >any application you build separately will use the previously installed >tools, headers and libraries. The 'make world' was started only after I had reported the problem. My thinking is that an updated install might fix this problem. --- Kent Vander Velden kent@iastate.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message