From owner-freebsd-current Sun Dec 26 5:46:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4064714CA7; Sun, 26 Dec 1999 05:46:06 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 25EE81CA0; Sun, 26 Dec 1999 21:45:59 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: Andreas Klemm , current@FreeBSD.ORG Subject: Re: can't get vmware to run ( on -current ) In-Reply-To: Message from Mike Smith of "Sat, 25 Dec 1999 14:24:11 PST." <199912252224.OAA00513@mass.cdrom.com> Date: Sun, 26 Dec 1999 21:45:59 +0800 From: Peter Wemm Message-Id: <19991226134559.25EE81CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > b) could not open /usr/local/lib/vmware/lib/vmm (no such file or directory) . > > No idea about that one. That is because /proc/curproc/exe is missing. Under Linux it's a pointer to the executable file (like our "file" used to be before it was killed). A trivial patch to reactivate it in a form that is useable by vmware: Index: procfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/miscfs/procfs/procfs_vnops.c,v retrieving revision 1.76 diff -u -r1.76 procfs_vnops.c --- procfs_vnops.c 1999/12/15 23:02:08 1.76 +++ procfs_vnops.c 1999/12/26 13:43:49 @@ -91,6 +91,7 @@ /* name type validp */ { DT_DIR, N("."), Pproc, NULL }, { DT_DIR, N(".."), Proot, NULL }, + { DT_REG, N("exe"), Pfile, procfs_validfile }, { DT_REG, N("mem"), Pmem, NULL }, { DT_REG, N("regs"), Pregs, procfs_validregs }, { DT_REG, N("fpregs"), Pfpregs, procfs_validfpregs }, This works because the Pfile support code hasn't been removed. Or you can check out the linprocfs stuff, see the vmware pages for a pointer. It provides a linux-like /compat/linux/proc that provides the missing bits that linux programs expect. 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 Dec 26 5:52:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id 5B7C714C0A for ; Sun, 26 Dec 1999 05:52:08 -0800 (PST) (envelope-from lynch@bsd.unix.sh) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id IAA22554; Sun, 26 Dec 1999 08:52:01 -0500 (EST) Date: Sun, 26 Dec 1999 08:52:00 -0500 (EST) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: Ben Rosengart Cc: current@FreeBSD.ORG Subject: Re: Speaking of moving files (Re: make world broken building fortunes ) 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, 14 Dec 1999, Ben Rosengart wrote: > > vi -- which is in /usr. > > Good example of something else that would be great to have in /bin. > > *ducking* > > -- > Ben Rosengart and as a coworker, I'd have to tell you how to use cat ;) ROTFL. -Pat __ Pat Lynch lynch@rush.net lynch@bsdunix.net lynch@unix.sh lynch@blowfi.sh Systems Administrator Rush Networking To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 6: 7: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from bytor.rush.net (bytor.rush.net [209.45.245.145]) by hub.freebsd.org (Postfix) with ESMTP id 4321114D94; Sun, 26 Dec 1999 06:06:51 -0800 (PST) (envelope-from lynch@bsd.unix.sh) Received: from localhost (lynch@localhost) by bytor.rush.net (8.9.3/8.9.3) with ESMTP id JAA22608; Sun, 26 Dec 1999 09:06:36 -0500 (EST) Date: Sun, 26 Dec 1999 09:06:36 -0500 (EST) From: Pat Lynch X-Sender: lynch@bytor.rush.net To: "Rodney W. Grimes" Cc: freebsd-current@FreeBSD.ORG, chat@FreeBSD.ORG Subject: Re: Speaking of moving files In-Reply-To: <199912150029.QAA20326@gndrsh.dnsmgr.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 Cc:ed to -chat where this seems to belong now. Yes, everyone should be familiar with fsdb (you should have seen the fear on a coworker's face the other day when I said something about fixing a filesystem with fsdb in jest. It was straight unadulterated terror.) The mere mention of this tool makes Junior level administrators cower in fear. Just for that reason it makes it the best tool for intimidation. -Pat -- Pat Lynch lynch@rush.net lynch@bsdunix.net lynch@unix.sh lynch@blowfi.sh Systems Administrator Rush Networking On Tue, 14 Dec 1999, Rodney W. Grimes wrote: > [Charset ISO-8859-1 unsupported, filtering to ASCII...] > > Ben Rosengart wrote in list.freebsd-current: > > > On Tue, 14 Dec 1999, Matthew Dillon wrote: > > > > > > > I think at one time or another all of us have missed *something* in > > > > /usr that wasn't in /. For example, disklabel -e doesn't work without > > > > vi -- which is in /usr. > > > > > > Good example of something else that would be great to have in /bin. > > > > No, really bad example. > > > > # export EDITOR=ed > > # disklabel -e da0s1 > > 759 > > _ > > > > Works perfectly well. But for chown, there is no functional > > equivalent in /bin or /sbin that I'm aware of. > > A person who really knew fsdb could do it /bin/fsdb, infact it's > not really that hard... as fsdb has chown, chgrp, chmod, chtype chname and > all the others built in as native commands ;-) :-) :-) > > > -- > Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.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 Sun Dec 26 7:10:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id A836B14C20; Sun, 26 Dec 1999 07:10:27 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2ivea7h.dialup.mindspring.com [165.247.40.241]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id KAA04605; Sun, 26 Dec 1999 10:10:24 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id KAA00406; Sun, 26 Dec 1999 10:10:22 -0500 (EST) (envelope-from vsilyaev) Date: Sun, 26 Dec 1999 10:10:22 -0500 From: "Vladimir N. Silyaev" To: Andreas Klemm Cc: Mike Smith , vns@delta.odessa.ua, current@FreeBSD.ORG Subject: Re: can't get vmware to run ( on -current ) Message-ID: <19991226101022.A378@jupiter.delta.ny.us> References: <19991225220356.A40880@titan.klemm.gtn.com> <199912252111.NAA31680@mass.cdrom.com> <19991225231318.A44105@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991225231318.A44105@titan.klemm.gtn.com>; from andreas@klemm.gtn.com on Sat, Dec 25, 1999 at 11:13:19PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 25, 1999 at 11:13:19PM +0100, Andreas Klemm wrote: > > Well, I think I had an outdated vmware port. > I grabbed it new from the mindspring webserver. > Then I had to manually load the vmmon.ko module > from /usr/local/lib/vmware/lib/modules Don't required, this modules are loaded at the booting time, in the /usr/local/etc/rc.d/vmware.sh script. After installation you are can launch it manually. > > I created a new configuration and the only problem seems > to be the following error messages: > a) about missing /dev/rtc and Exactly, /dev/rtc doesn't supported. > b) could not open /usr/local/lib/vmware/lib/vmm (no such file or directory). This is a FAQ. When you are selected, that you are want to use linux proc filesystem emulator, you are _must_ mount it in /compat/linux/proc before launch vmware executable (the easiest way to do that, it's install the linuxprocfs port). At other case vmware port provide some hack and dirty way to emulate some facility of linux proc filesystem. -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 9:14:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 87F5F14F7A for ; Sun, 26 Dec 1999 09:14:51 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 24896 invoked from network); 26 Dec 1999 17:14:49 -0000 Received: from lca111.cvzoom.net (HELO cvzoom.net) (63.65.158.111) by ns.cvzoom.net with SMTP; 26 Dec 1999 17:14:48 -0000 Message-ID: <38664CC6.34DD3329@cvzoom.net> Date: Sun, 26 Dec 1999 12:13:42 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: gcc compile error References: <199912260717.XAA73116@rah.star-gate.com> Content-Type: multipart/mixed; boundary="------------816DC2C1C7498C7B8D7B6F27" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------816DC2C1C7498C7B8D7B6F27 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Amancio Hasty wrote: > > While trying to compile the latest version of XFree86 I found the following > compiler bug. > > {root} gcc -v > Using builtin specs. > gcc version 2.95.2 19991024 (release) > > I assume that this an old version of gcc... Actually, that's one of the newest versions of gcc. -snip- > xf86vmode.c: In function `ProcXF86VidModeGetMonitor': > xf86vmode.c:1320: Unable to generate reloads for: > (insn 300 298 302 (parallel[ > (set (reg:SI 0 %eax) > (fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0)))) > (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) > (const_int -34 [0xffffffde])) 0)) > (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) > (const_int -36 [0xffffffdc])) 0)) > (clobber (mem:SI (plus:SI (reg:SI 6 %ebp) > (const_int -40 [0xffffffd8])) 0)) > (clobber (scratch:HI)) > ] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil)) > (expr_list:REG_DEAD (reg:SI 0 %eax) > (expr_list:REG_UNUSED (scratch:HI) > (nil)))) > *** Error code 1 I get similar errors trying to compile aview from ports. I just updated my ports tree, so that can't be the problem. See the attached make.log. There's something about not allowing access to the cx register. - Donn --------------816DC2C1C7498C7B8D7B6F27 Content-Type: text/plain; charset=us-ascii; name="make.log" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="make.log" ===> Building for aview-1.2 cc -O -pipe -I/usr/X11R6/include -I/usr/local/include -c flip.c flip.c: In function `dcd_delta_flc': sstring.h:493: Invalid `asm' statement: sstring.h:493: fixed or forbidden register 2 (cx) was spilled for class CREG. flip.c: In function `dcd_delta_fli': sstring.h:493: Invalid `asm' statement: sstring.h:493: fixed or forbidden register 2 (cx) was spilled for class CREG. flip.c: In function `dcd_byte_run': sstring.h:493: Invalid `asm' statement: sstring.h:493: fixed or forbidden register 2 (cx) was spilled for class CREG. flip.c: In function `dcd_black': sstring.h:669: Invalid `asm' statement: sstring.h:669: fixed or forbidden register 2 (cx) was spilled for class CREG. flip.c: In function `dcd_literal': sstring.h:493: Invalid `asm' statement: sstring.h:493: fixed or forbidden register 2 (cx) was spilled for class CREG. *** Error code 1 Stop in /usr/ports/graphics/aview/work/aview-1.2. *** Error code 1 Stop in /usr/ports/graphics/aview. *** Error code 1 Stop in /usr/ports/graphics/aview. *** Error code 1 Stop in /usr/ports/graphics/aview. --------------816DC2C1C7498C7B8D7B6F27-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 9:34:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2660214C13 for ; Sun, 26 Dec 1999 09:34:24 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 122HYl-000BTb-00 for freebsd-current@freebsd.org; Sun, 26 Dec 1999 09:34:23 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: buildworld failure Message-Id: Date: Sun, 26 Dec 1999 09:34:23 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG trying an upgrade from 3.4-stable to -current.9912261321 did a full rm -rf of /usr/src and /usr/obj, then a full cvsup. buildworld dies: rm -f libfetch.a # llib-lfetch.ln rm -f fetch.po common.po ftp.po http.po file.po fetch_err.po fetch.po.tmp common.po.tmp ftp.po.tmp http.po.tmp file.po.tmp fetch_err.po.tmp libfetch_p.a rm -f fetch.So common.So ftp.So http.So file.So fetch_err.So fetch.so common.so ftp.so http.so file.so fetch_err.so fetch.So.tmp common.So.tmp ftp.So.tmp http.So.tmp file.So.tmp fetch_err.So.tmp libfetch.so.1 libfetch.so libfetch.so.* libfetch.so libfetch_pic.a rm -f .depend /usr/src/lib/libfetch/GPATH /usr/src/lib/libfetch/GRTAGS /usr/src/lib/libfetch/GSYMS /usr/src/lib/libfetch/GTAGS ===> lib/libform cd: can't cd to /usr/src/lib/libform *** Error code 2 Stop. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 9:51:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 0FB0915218 for ; Sun, 26 Dec 1999 09:51:24 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 122HpD-000GNn-00 for freebsd-current@freebsd.org; Sun, 26 Dec 1999 09:51:23 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: Re: buildworld failure Message-Id: Date: Sun, 26 Dec 1999 09:51:23 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> lib/libform cd: can't cd to /usr/src/lib/libform *** Error code 2 so i removed libform from the /usr/src/lib/Makefile, and am now blessed with ===> usr.bin/strip rm -f maybe_stripped strip strip.o strip.1aout.gz strip.1aout.cat.gz rm -f .depend /usr/src/usr.bin/strip/GPATH /usr/src/usr.bin/strip/GRTAGS /usr/src/usr.bin/strip/GSYMS /usr/src/usr.bin/strip/GTAGS 2 errors *** Error code 2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 9:56:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 32A791502D; Sun, 26 Dec 1999 09:55:46 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id CAA02958; Mon, 27 Dec 1999 02:55:43 +0900 (JST) To: FreeBSD-current@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG Subject: Re: indirection in bus space From: KATO Takenori In-Reply-To: Your message of "Sat, 25 Dec 1999 22:56:03 +0900" <19991225225603L.kato@gneiss.eps.nagoya-u.ac.jp> References: <19991225225603L.kato@gneiss.eps.nagoya-u.ac.jp> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991227025513Z.kato@gneiss.eps.nagoya-u.ac.jp> Date: Mon, 27 Dec 1999 02:55:13 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 27 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD-hackers list is added. KATO Takenori wrote: > I didn't realize the difference in type of bus_space_handle_t. So, > bus.h needs to be separated into bus_at386.h and bus_pc98.h. I revised bus space patch. This patch does: 1. copy bus.h to bus_at386.h. The bus_at386.h doesn't support indirection. 2. add bus_pc98.h. The bus_pc98.h supports indirection. 3. make new bus.h. The bus.h includes bus_at386.h or bus_pc98.h. 4. modify isa.c and nexus.c to support indirection. Indirection is enabled only when PC98 is defined. Because the pache is too large to attach on this mail, I put it as: http://www.freebsd.org/~kato/patches/busspace.diff.gz -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 10:15:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from afcon.net (afcon.afcon.net [209.26.60.2]) by hub.freebsd.org (Postfix) with ESMTP id 7946A14F85 for ; Sun, 26 Dec 1999 10:15:53 -0800 (PST) (envelope-from scorpio@sunline.net) Received: from jeff (afcon-dyn46.afcon.net [209.26.60.46]) by afcon.net (8.9.3/8.9.3) with SMTP id NAA31213; Sun, 26 Dec 1999 13:15:26 -0500 Message-ID: <005601bf4fcd$3e967140$2e3c1ad1@jeff> From: "Jeff Palmer" To: "Randy Bush" , "FreeBSD Current" Subject: Re: buildworld failure Date: Sun, 26 Dec 1999 13:15:51 -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.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randy, There are a few things you have to do when supping from 3.* to -CURRENT The Best Source of information I have found is at http://www.external.org/freebsd/current.html I hope this document helps you, I have tried it, it worked fine (however I didn't like -CURRENT so I reformatted and went -STABLE again) I'm no coder, so when little things would break, I was out of luck.. Jeff Palmer scorpio@sunline.net -----Original Message----- From: Randy Bush To: FreeBSD Current Date: Sunday, December 26, 1999 12:50 PM Subject: Re: buildworld failure >===> lib/libform >cd: can't cd to /usr/src/lib/libform >*** Error code 2 > >so i removed libform from the /usr/src/lib/Makefile, and am now blessed with > >===> usr.bin/strip >rm -f maybe_stripped strip strip.o strip.1aout.gz strip.1aout.cat.gz >rm -f .depend /usr/src/usr.bin/strip/GPATH /usr/src/usr.bin/strip/GRTAGS /usr/src/usr.bin/strip/GSYMS /usr/src/usr.bin/strip/GTAGS >2 errors >*** Error code 2 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 11:54:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles506.castles.com [208.214.165.70]) by hub.freebsd.org (Postfix) with ESMTP id 5F08414BE3 for ; Sun, 26 Dec 1999 11:54:11 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA03528; Sun, 26 Dec 1999 11:58:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912261958.LAA03528@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jerry Alexandratos Cc: freebsd-current@freebsd.org Subject: Re: OSS and -current In-reply-to: Your message of "Sat, 25 Dec 1999 21:07:21 EST." <19991225210721.A314@hellboy.aug.fusa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Dec 1999 11:58:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to get the latest version of OSS (3.9.3a) working under > -current and having very little success. > > When I try running soundconf, I get the following messages: > > kldload: can't load /usr/opt/oss/oss_mod: Exec format error > Cannot load OSS driver module. > > Dec 25 21:02:46 hellboy /kernel: link_elf: symbol register_intr undefined > > This is with a kernel and world built 1999-12-24 and sources cvsup'ed > prior to that. > > Any ideas one what could be wrong here? This is something I cautioned the OSS folks about a while back. Because they maintain their code for a large number of platforms, they use their own probe/attach infrastructure rather than the host operating system's bus support. Because of that, and in the FreeBSD case because they've been supporting 2.2.x and 3.x for a long time, they've been using the old compatibility interfaces (this is just simple expediency, and not something to chastise them for). In this case, register_intr() was one of those interfaces, and it's gone away. I'm expecting that we're going to have to spend some time very soon helping the OSS folks get their code up to speed for 4.x. In the meantime, however, people on the 4.x branch are going to have to live without OSS. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 12: 6:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id D70FA14ED5 for ; Sun, 26 Dec 1999 12:06:18 -0800 (PST) (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.9.3/8.9.3) with ESMTP id MAA77437; Sun, 26 Dec 1999 12:02:58 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912262002.MAA77437@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: gcc compile error In-reply-to: Your message of "Sun, 26 Dec 1999 12:13:42 EST." <38664CC6.34DD3329@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Dec 1999 12:02:58 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Actually, that's one of the newest versions of gcc. Perhaps a later snapshot of gcc will work . >attached make.log. There's something about not allowing access >to the cx register. I am not into hacking gcc's register allocator 8) -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 12:23:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id DA0FE1502D for ; Sun, 26 Dec 1999 12:23:43 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 122KCc-0007UZ-00 for freebsd-current@freebsd.org; Sun, 26 Dec 1999 12:23:42 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: base64 To: FreeBSD Current Subject: Re: buildworld failure References: Message-Id: Date: Sun, 26 Dec 1999 12:23:42 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PiA9PT0+IGxpYi9saWJmb3JtDQo+IGNkOiBjYW4ndCBjZCB0byAvdXNyL3NyYy9saWIvbGli Zm9ybQ0KPiAqKiogRXJyb3IgY29kZSAyDQo+IA0KPiBzbyBpIHJlbW92ZWQgbGliZm9ybSBm cm9tIHRoZSAvdXNyL3NyYy9saWIvTWFrZWZpbGUsIGFuZCBhbSBub3cgYmxlc3NlZCB3aXRo DQo+IA0KPiA9PT0+IHVzci5iaW4vc3RyaXANCj4gcm0gLWYgbWF5YmVfc3RyaXBwZWQgc3Ry aXAgc3RyaXAubyBzdHJpcC4xYW91dC5neiBzdHJpcC4xYW91dC5jYXQuZ3oNCj4gcm0gLWYg LmRlcGVuZCAvdXNyL3NyYy91c3IuYmluL3N0cmlwL0dQQVRIIC91c3Ivc3JjL3Vzci5iaW4v c3RyaXAvR1JUQUdTICAvdXNyL3NyYy91c3IuYmluL3N0cmlwL0dTWU1TIC91c3Ivc3JjL3Vz ci5iaW4vc3RyaXAvR1RBR1MNCj4gMiBlcnJvcnMNCj4gKioqIEVycm9yIGNvZGUgMg0KDQo8 ZG9oPg0KDQp0aGlzIGlzIGFsbCBiZWNhdXNlIGkgYmxldyBhd2F5IC91c3Ivc3JjLyogYW5k IC91c3Ivb2JqLyogYW5kIHRoZW4gcmFuIA0KY3ZzdXAgLXMuICB0b29rIG9mZiB0aGF0IC1z LCBhbmQgdGhpcyBraW5kIG9mIGdyb3NzIG5vbnNlbnNlIHN0b3BwZWQuDQoNCm5vdyBpIGhh dmUgbW9yZSAnbm9ybWFsJyBjdXJyZW50IG5vbnNlbnNlLg0KDQpta2RlcCAtZiAuZGVwZW5k IC1hICAgIC1JL3Vzci9zcmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi8uLi9jcnlw dG8va2VyYmVyb3NJVi9pbmNsdWRlIC1JL3Vzci9vYmovdXNyL3NyYy9rZXJiZXJvc0lWL2xp Yi9saWJrYWRtLy4uLy4uL2luY2x1ZGUgLUkvdXNyL3NyYy9rZXJiZXJvc0lWL2xpYi9saWJr YWRtLy4uLy4uLy4uL2NyeXB0by9rZXJiZXJvc0lWL2xpYi9rcmIgLUkvdXNyL3NyYy9rZXJi ZXJvc0lWL2xpYi9saWJrYWRtLy4uLy4uLy4uL2NyeXB0by9rZXJiZXJvc0lWL2xpYi9rZGIg LUkvdXNyL3NyYy9rZXJiZXJvc0lWL2xpYi9saWJrYWRtLy4uLy4uLy4uL2NyeXB0by9rZXJi ZXJvc0lWL2xpYi9rYWRtIC1JL3Vzci9zcmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8u Li8uLi9jcnlwdG8va2VyYmVyb3NJVi9saWIvcm9rZW4gLUkvdXNyL29iai91c3Ivc3JjL2tl cmJlcm9zSVYvbGliL2xpYmthZG0vLi4vLi4vbGliL2xpYmtyYiAtSS91c3Ivb2JqL3Vzci9z cmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi9saWIvbGlia2FkbSAtSS91c3Ivb2Jq L3Vzci9zcmMva2VyYmVyb3NJVi9saWIvbGlia2FkbSAtSS91c3Ivc3JjL2tlcmJlcm9zSVYv bGliL2xpYmthZG0vLi4vLi4vaW5jbHVkZSAtREhBVkVfQ09ORklHX0ggLUkvdXNyL29iai91 c3Ivc3JjL2tlcmJlcm9zSVYvbGliL2xpYmthZG0vLi4vLi4vaW5jbHVkZSAtREJJTkRJUj1c Ii91c3IvYmluXCIgLURTQklORElSPVwiL3Vzci9zYmluXCIgLUkvdXNyL29iai91c3Ivc3Jj L2kzODYvdXNyL2luY2x1ZGUgIC91c3Ivc3JjL2tlcmJlcm9zSVYvbGliL2xpYmthZG0vLi4v Li4vLi4vY3J5cHRvL2tlcmJlcm9zSVYvbGliL2thZG0va2FkbV9jbGlfd3JhcC5jIC91c3Iv c3JjL2tlcmJlcm9zSVYvbGliL2xpYmthZG0vLi4vLi4vLi4vY3J5cHRvL2tlcmJlcm9zSVYv bGliL2thZG0va2FkbV9zdHJlYW0uYyAvdXNyL3NyYy9rZXJiZXJvc0lWL2xpYi9saWJrYWRt Ly4uLy4uLy4uL2NyeXB0by9rZXJiZXJvc0lWL2xpYi9rYWRtL2thZG1fc3VwcC5jIC91c3Iv b2JqL3Vzci9zcmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi9saWIvbGlia2FkbS9r YWRtX2Vyci5jIC91c3Ivc3JjL2tlcmJlcm9zSVYvbGliL2xpYmthZG0vLi4vLi4vLi4vY3J5 cHRvL2tlcmJlcm9zSVYvbGliL2thZG0vY2hlY2tfcGFzc3dvcmQuYw0KSW4gZmlsZSBpbmNs dWRlZCBmcm9tIC91c3Ivc3JjL2tlcmJlcm9zSVYvbGliL2xpYmthZG0vLi4vLi4vLi4vY3J5 cHRvL2tlcmJlcm9zSVYvbGliL2thZG0va2FkbV9sb2NsLmg6NzksDQogICAgICAgICAgICAg ICAgIGZyb20gL3Vzci9zcmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi8uLi9jcnlw dG8va2VyYmVyb3NJVi9saWIva2FkbS9rYWRtX2NsaV93cmFwLmM6MzA6DQovdXNyL29iai91 c3Ivc3JjL2tlcmJlcm9zSVYvbGliL2xpYmthZG0vLi4vLi4vbGliL2xpYmtyYi9rcmJfZXJy Lmg6MTc6IGludmFsaWQgbWFjcm8gbmFtZQ0KSW4gZmlsZSBpbmNsdWRlZCBmcm9tIC91c3Iv c3JjL2tlcmJlcm9zSVYvbGliL2xpYmthZG0vLi4vLi4vLi4vY3J5cHRvL2tlcmJlcm9zSVYv bGliL2thZG0va2FkbV9sb2NsLmg6ODIsDQogICAgICAgICAgICAgICAgIGZyb20gL3Vzci9z cmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi8uLi9jcnlwdG8va2VyYmVyb3NJVi9s aWIva2FkbS9rYWRtX2NsaV93cmFwLmM6MzA6DQovdXNyL29iai91c3Ivc3JjL2tlcmJlcm9z SVYvbGliL2xpYmthZG0vLi4vLi4vbGliL2xpYmthZG0va2FkbV9lcnIuaDoxMzogd2Fybmlu ZzogYEVSUk9SX1RBQkxFX0JBU0VfJyByZWRlZmluZWQNCi91c3Ivb2JqL3Vzci9zcmMva2Vy YmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi9saWIvbGlia3JiL2tyYl9lcnIuaDoxMzogd2Fy bmluZzogdGhpcyBpcyB0aGUgbG9jYXRpb24gb2YgdGhlIHByZXZpb3VzIGRlZmluaXRpb24N Ci91c3Ivb2JqL3Vzci9zcmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi9saWIvbGli a2FkbS9rYWRtX2Vyci5oOjE3OiBpbnZhbGlkIG1hY3JvIG5hbWUNCkluIGZpbGUgaW5jbHVk ZWQgZnJvbSAvdXNyL3NyYy9rZXJiZXJvc0lWL2xpYi9saWJrYWRtLy4uLy4uLy4uL2NyeXB0 by9rZXJiZXJvc0lWL2xpYi9rYWRtL2thZG1fbG9jbC5oOjc5LA0KICAgICAgICAgICAgICAg ICBmcm9tIC91c3Ivc3JjL2tlcmJlcm9zSVYvbGliL2xpYmthZG0vLi4vLi4vLi4vY3J5cHRv L2tlcmJlcm9zSVYvbGliL2thZG0va2FkbV9zdHJlYW0uYzozODoNCi91c3Ivb2JqL3Vzci9z cmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi9saWIvbGlia3JiL2tyYl9lcnIuaDox NzogaW52YWxpZCBtYWNybyBuYW1lDQpJbiBmaWxlIGluY2x1ZGVkIGZyb20gL3Vzci9zcmMv a2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi8uLi9jcnlwdG8va2VyYmVyb3NJVi9saWIv a2FkbS9rYWRtX2xvY2wuaDo4MiwNCiAgICAgICAgICAgICAgICAgZnJvbSAvdXNyL3NyYy9r ZXJiZXJvc0lWL2xpYi9saWJrYWRtLy4uLy4uLy4uL2NyeXB0by9rZXJiZXJvc0lWL2xpYi9r YWRtL2thZG1fc3RyZWFtLmM6Mzg6DQovdXNyL29iai91c3Ivc3JjL2tlcmJlcm9zSVYvbGli L2xpYmthZG0vLi4vLi4vbGliL2xpYmthZG0va2FkbV9lcnIuaDoxMzogd2FybmluZzogYEVS Uk9SX1RBQkxFX0JBU0VfJyByZWRlZmluZWQNCi91c3Ivb2JqL3Vzci9zcmMva2VyYmVyb3NJ Vi9saWIvbGlia2FkbS8uLi8uLi9saWIvbGlia3JiL2tyYl9lcnIuaDoxMzogd2FybmluZzog dGhpcyBpcyB0aGUgbG9jYXRpb24gb2YgdGhlIHByZXZpb3VzIGRlZmluaXRpb24NCi91c3Iv b2JqL3Vzci9zcmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi9saWIvbGlia2FkbS9r YWRtX2Vyci5oOjE3OiBpbnZhbGlkIG1hY3JvIG5hbWUNCkluIGZpbGUgaW5jbHVkZWQgZnJv bSAvdXNyL3NyYy9rZXJiZXJvc0lWL2xpYi9saWJrYWRtLy4uLy4uLy4uL2NyeXB0by9rZXJi ZXJvc0lWL2xpYi9rYWRtL2thZG1fbG9jbC5oOjc5LA0KICAgICAgICAgICAgICAgICBmcm9t IC91c3Ivc3JjL2tlcmJlcm9zSVYvbGliL2xpYmthZG0vLi4vLi4vLi4vY3J5cHRvL2tlcmJl cm9zSVYvbGliL2thZG0va2FkbV9zdXBwLmM6MzY6DQovdXNyL29iai91c3Ivc3JjL2tlcmJl cm9zSVYvbGliL2xpYmthZG0vLi4vLi4vbGliL2xpYmtyYi9rcmJfZXJyLmg6MTc6IGludmFs aWQgbWFjcm8gbmFtZQ0KSW4gZmlsZSBpbmNsdWRlZCBmcm9tIC91c3Ivc3JjL2tlcmJlcm9z SVYvbGliL2xpYmthZG0vLi4vLi4vLi4vY3J5cHRvL2tlcmJlcm9zSVYvbGliL2thZG0va2Fk bV9sb2NsLmg6ODIsDQogICAgICAgICAgICAgICAgIGZyb20gL3Vzci9zcmMva2VyYmVyb3NJ Vi9saWIvbGlia2FkbS8uLi8uLi8uLi9jcnlwdG8va2VyYmVyb3NJVi9saWIva2FkbS9rYWRt X3N1cHAuYzozNjoNCi91c3Ivb2JqL3Vzci9zcmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8u Li8uLi9saWIvbGlia2FkbS9rYWRtX2Vyci5oOjEzOiB3YXJuaW5nOiBgRVJST1JfVEFCTEVf QkFTRV8nIHJlZGVmaW5lZA0KL3Vzci9vYmovdXNyL3NyYy9rZXJiZXJvc0lWL2xpYi9saWJr YWRtLy4uLy4uL2xpYi9saWJrcmIva3JiX2Vyci5oOjEzOiB3YXJuaW5nOiB0aGlzIGlzIHRo ZSBsb2NhdGlvbiBvZiB0aGUgcHJldmlvdXMgZGVmaW5pdGlvbg0KL3Vzci9vYmovdXNyL3Ny Yy9rZXJiZXJvc0lWL2xpYi9saWJrYWRtLy4uLy4uL2xpYi9saWJrYWRtL2thZG1fZXJyLmg6 MTc6IGludmFsaWQgbWFjcm8gbmFtZQ0KSW4gZmlsZSBpbmNsdWRlZCBmcm9tIC91c3Ivc3Jj L2tlcmJlcm9zSVYvbGliL2xpYmthZG0vLi4vLi4vLi4vY3J5cHRvL2tlcmJlcm9zSVYvbGli L2thZG0va2FkbV9sb2NsLmg6NzksDQogICAgICAgICAgICAgICAgIGZyb20gL3Vzci9zcmMv a2VyYmVyb3NJVi9saWIvbGlia2FkbS8uLi8uLi8uLi9jcnlwdG8va2VyYmVyb3NJVi9saWIv a2FkbS9jaGVja19wYXNzd29yZC5jOjM5Og0KL3Vzci9vYmovdXNyL3NyYy9rZXJiZXJvc0lW L2xpYi9saWJrYWRtLy4uLy4uL2xpYi9saWJrcmIva3JiX2Vyci5oOjE3OiBpbnZhbGlkIG1h Y3JvIG5hbWUNCkluIGZpbGUgaW5jbHVkZWQgZnJvbSAvdXNyL3NyYy9rZXJiZXJvc0lWL2xp Yi9saWJrYWRtLy4uLy4uLy4uL2NyeXB0by9rZXJiZXJvc0lWL2xpYi9rYWRtL2thZG1fbG9j bC5oOjgyLA0KICAgICAgICAgICAgICAgICBmcm9tIC91c3Ivc3JjL2tlcmJlcm9zSVYvbGli L2xpYmthZG0vLi4vLi4vLi4vY3J5cHRvL2tlcmJlcm9zSVYvbGliL2thZG0vY2hlY2tfcGFz c3dvcmQuYzozOToNCi91c3Ivb2JqL3Vzci9zcmMva2VyYmVyb3NJVi9saWIvbGlia2FkbS8u Li8uLi9saWIvbGlia2FkbS9rYWRtX2Vyci5oOjEzOiB3YXJuaW5nOiBgRVJST1JfVEFCTEVf QkFTRV8nIHJlZGVmaW5lZA0KL3Vzci9vYmovdXNyL3NyYy9rZXJiZXJvc0lWL2xpYi9saWJr YWRtLy4uLy4uL2xpYi9saWJrcmIva3JiX2Vyci5oOjEzOiB3YXJuaW5nOiB0aGlzIGlzIHRo ZSBsb2NhdGlvbiBvZiB0aGUgcHJldmlvdXMgZGVmaW5pdGlvbg0KL3Vzci9vYmovdXNyL3Ny Yy9rZXJiZXJvc0lWL2xpYi9saWJrYWRtLy4uLy4uL2xpYi9saWJrYWRtL2thZG1fZXJyLmg6 MTc6IGludmFsaWQgbWFjcm8gbmFtZQ0KbWtkZXA6IGNvbXBpbGUgZmFpbGVkDQoqKiogRXJy b3IgY29kZSAxDQoNCg0Kbm90ZSB0aGF0IGkgYW0gcnVubmluZyB3aXRoIGEgaGFjay1idWls dCBjdXJyZW50IGtlcm5lbC4gIGZvciB0aGUgcmVjb3JkLA0KYSBoYWNrYnVpbHQgY3VycmVu dCBrZXJuZWwgcmVxdWlyZWQgcmVtb3ZpbmcgKDMuNC1zdGFibGUpIHBvc2l4L2xpbnV4DQpl bXVsYXRpb24uDQoNCnJhbmR5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 13:29:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 9D99214F25; Sun, 26 Dec 1999 13:29:05 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup1-55.iptelecom.net.ua [212.9.226.55]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id XAA11206; Sun, 26 Dec 1999 23:31:02 +0200 (EET) Message-ID: <38667DEB.309D1295@altavista.net> Date: Sun, 26 Dec 1999 22:43:23 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org, brian@freebsd.org Subject: PPP still has problems with config parsing Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As of today -current ppp is still incorrectly parsing dial string (yes, I know that Brian several days ago already submitted some patches to address similar problems, but it seems that it was not enough). Following is transcript of my session, using configuration which worked flawlessly on the previous -current built two weeks ago. As you can see phone number and configuration string are not being sent to modem and ppp doesn't wait for response string ("CONNECT") to proceed with negotiation. -Maxim Script started on Sun Dec 26 22:28:17 1999 bash-2.03# ppp ip-telecom Working in interactive mode Using interface: tun0 tun0: Command: ip-telecom: set device /dev/cuaa1 tun0: Command: ip-telecom: set speed 115200 tun0: Command: ip-telecom: set dial ABORT BUSY ABORT NO\sCARRIER ABORT NO\sDIAL\sTONE TIMEOUT 5 "" AT OK-AT-OK AT&F OK AT#F0$R1%E0S20=8&E2S48=16 OK \dATDP\T TIMEOUT 40 CONNECT tun0: Command: ip-telecom: set server ***** ******** tun0: Phase: Listening at port 3000. tun0: Command: ip-telecom: disable sroutes tun0: Command: ip-telecom: set phone 238-8888 tun0: Command: ip-telecom: set login tun0: Command: ip-telecom: set authname *** tun0: Command: ip-telecom: set authkey ******** tun0: Command: ip-telecom: set timeout 120 tun0: Command: ip-telecom: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 tun0: Command: ip-telecom: add default HISADDR tun0: Command: ip-telecom: enable dns tun0: Phase: PPP Started (interactive mode). ppp ON home> dia tun0: Command: /dev/tty: dia tun0: Phase: bundle: Establish tun0: Phase: deflink: closed -> opening tun0: Phase: deflink: Connected! tun0: Phase: deflink: opening -> dial tun0: Phase: Phone: 238-8888 tun0: Chat: deflink: Dial attempt 1 of 1 ppp ON home> tun0: Chat: Send: AT tun0: Chat: Expect(5): OK tun0: Chat: Received: AT tun0: Chat: Received: OK tun0: Chat: Send: AT&F tun0: Chat: Expect(5): OK tun0: Chat: Received: AT&F tun0: Chat: Received: OK tun0: Chat: Send: AT tun0: Phase: deflink: dial -> carrier tun0: Phase: deflink: /dev/cuaa1 doesn't support CD tun0: Phase: deflink: carrier -> login tun0: Phase: deflink: login -> lcp [...] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 16: 2:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id F101514BDB for ; Sun, 26 Dec 1999 16:02:53 -0800 (PST) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 122NdI-000AkP-00; Sun, 26 Dec 1999 19:03:28 -0500 To: grog@lemis.com Cc: current@freebsd.org From: "Gary Palmer" Subject: ``how to'' for Vinum and mirroring after the volume was created? Date: Sun, 26 Dec 1999 19:03:27 -0500 Message-ID: <41316.946253007@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Greg, I've got a question or two about vinum, and how to work it. I'm trying to upgrade the storage on my home computer, and while I was transitioning my old disks out, I only managed to get one of the new ones online to copy data onto it. Now I want to mirror that volume onto a 2nd plex. Attaching the plex to the volume and doing a vinum start seemed to start a mirroring process, but it seemed to be reading from both plexes in round robin to do the mirror! This obviously wasn't what I had hoped for. The second question concerns the flag fields. Is there any way to change flags on the fly? e.g. change the volume from being round robin to prefer plex? Lastly, what does vinum mean? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 16:20:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id E11CE14F5D; Sun, 26 Dec 1999 16:20:47 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id BFCE31CA0; Mon, 27 Dec 1999 08:20:41 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Vladimir N. Silyaev" Cc: Andreas Klemm , Mike Smith , vns@delta.odessa.ua, current@FreeBSD.ORG Subject: Re: can't get vmware to run ( on -current ) In-Reply-To: Message from "Vladimir N. Silyaev" of "Sun, 26 Dec 1999 10:10:22 EST." <19991226101022.A378@jupiter.delta.ny.us> Date: Mon, 27 Dec 1999 08:20:41 +0800 From: Peter Wemm Message-Id: <19991227002041.BFCE31CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Vladimir N. Silyaev" wrote: > > I created a new configuration and the only problem seems > > to be the following error messages: > > a) about missing /dev/rtc and > Exactly, /dev/rtc doesn't supported. .. and I'm not entirely sure that we can support it easily. Linux appears to allow user processes to program the RTC to run at an arbitary frequency and /dev/rtc is used to count the number of "ticks" since the last time it was read. The problem is that we use the RTC for other things and at specific frequencies (128hz or 1024hz), so I don't think we can easily emulate /dev/rtc with great precision. 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 Dec 26 16:30:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 1624815090 for ; Sun, 26 Dec 1999 16:30:36 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 122O3X-000AUN-00 for freebsd-current@freebsd.org; Sun, 26 Dec 1999 16:30:35 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: Re: buildworld failure References: Message-Id: Date: Sun, 26 Dec 1999 16:30:35 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG so i commented kerberos out of /etc/make.conf so i could keep chugging. an hour later (smp off and only a 300mhz chip), perl cores the build. cc -o /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX/auto/POSIX/POSIX.so -shared POSIX.o -lperl chmod 755 /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX/auto/POSIX/POSIX.so cp POSIX.bs /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX/auto/POSIX/POSIX.bs chmod 644 /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/POSIX/auto/POSIX/POSIX.bs Segmentation fault - core dumped Running '/usr/obj/usr/src/gnu/usr.bin/perl/perl/perl -I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp -v 2>&1' exits with status 139 at (eval 34) line 17. Segmentation fault - core dumped Running '/usr/obj/usr/src/gnu/usr.bin/perl/perl/perl /usr/obj/usr/src/gnu/usr.bin/perl/perl/lib/ExtUtils/xsubpp temp000 2>&1' exits with status 139 at (eval 34) line 43. Writing Makefile for sdbm Writing Makefile for SDBM_File mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/SDBM_File mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/SDBM_File/auto mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/SDBM_File/auto/SDBM_File cp SDBM_File.pm /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/SDBM_File/SDBM_File.pm cd sdbm && make all cc -c -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -DVERSION=\"0.10\" -DXS_VERSION=\"0.10\" -DPIC -fpic -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -DSDBM -DDUFF sdbm.c cc -c -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -DVERSION=\"0.10\" -DXS_VERSION=\"0.10\" -DPIC -fpic -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -DSDBM -DDUFF pair.c cc -c -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -DVERSION=\"0.10\" -DXS_VERSION=\"0.10\" -DPIC -fpic -I/usr/obj/usr/src/gnu/usr.bin/perl/perl -DSDBM -DDUFF hash.c Segmentation fault - core dumped *** Error code 139 on Tue, 23 Nov 1999, Doug Ambrisko sent mail to this list saying he was checking in a tentative fix, but ... randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 17:35: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 4241D150E6 for ; Sun, 26 Dec 1999 17:34:58 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA42234; Mon, 27 Dec 1999 12:04:45 +1030 (CST) Date: Mon, 27 Dec 1999 12:04:45 +1030 From: Greg Lehey To: Gary Palmer Cc: current@freebsd.org Subject: Re: ``how to'' for Vinum and mirroring after the volume was created? Message-ID: <19991227120444.S1316@freebie.lemis.com> References: <41316.946253007@noop.colo.erols.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <41316.946253007@noop.colo.erols.net> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Sunday, 26 December 1999 at 19:03:27 -0500, Gary Palmer wrote: > > Hi Greg, > > I've got a question or two about vinum, and how to work it. > > I'm trying to upgrade the storage on my home computer, and while I was > transitioning my old disks out, I only managed to get one of the new > ones online to copy data onto it. Did you forget the 'setupstate' keyword? > Now I want to mirror that volume onto a 2nd plex. Attaching the > plex to the volume and doing a vinum start seemed to start a > mirroring process, but it seemed to be reading from both plexes in > round robin to do the mirror! How do you determine that? > This obviously wasn't what I had hoped for. It certainly doesn't make sense? > The second question concerns the flag fields. Is there any way to > change flags on the fly? e.g. change the volume from being round > robin to prefer plex? That's one thing I haven't done yet. It's trivial, but I haven't thought of a syntax for the command. Suggestions? > Lastly, what does vinum mean? Wine (in Latin). If you search, you may find an amusing pun on a Latin saying. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 17:53:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 2AC4B14E05 for ; Sun, 26 Dec 1999 17:53:36 -0800 (PST) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 122PMY-000Arq-00; Sun, 26 Dec 1999 20:54:18 -0500 To: Greg Lehey Cc: current@freebsd.org From: Gary Palmer Subject: Re: ``how to'' for Vinum and mirroring after the volume was created? In-reply-to: Your message of "Mon, 27 Dec 1999 12:04:45 +1030." <19991227120444.S1316@freebie.lemis.com> Date: Sun, 26 Dec 1999 20:54:17 -0500 Message-ID: <41777.946259657@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote in message ID <19991227120444.S1316@freebie.lemis.com>: > Did you forget the 'setupstate' keyword? How would that apply? The 2nd disk was not consistant as it was added after the data was copied onto the first and the old disks removed. Or should I have dd'd the contents of the first disk onto the second? There was already a filesystem and data on the first disk which was not present on the 2nd as I couldn't physically power the disk without removing one of the old ones. > How do you determine that? Looking at the stats vinum provided. Unfortunately they're gone from my scrollback buffer, but the 2nd plex was being read from, which is not something I'd expect from what should have been a straight copy from the first to the second. Also, if I remember right, the read data from the first plex was going up more slowly than the written data to the 2nd plex, which indicates to me that it may indeed have been round-robining the reads, even though the 2nd plex wasn't consistant. I realise that the above is speculation, and not conclusive proof about what vinum was doing, but without hacking the module, I didn't see any easy way of tracking exactly what it was doing. > > The second question concerns the flag fields. Is there any way to > > change flags on the fly? e.g. change the volume from being round > > robin to prefer plex? > That's one thing I haven't done yet. It's trivial, but I haven't > thought of a syntax for the command. Suggestions? I think (at least to my mind) the best way to abstract it would be as readflags/setflags commands, and do it so that it would work for flags on the volume, plex, subdisk or disk level. I don't know how many flags you really want to expose to the end-user, but I can imagine as the product develops, more flags will be added. e.g. veritas has user-settable comments fields. e.g. vinum setflag vol01 readpol=prefer preferplex=plex01 (that is a tricky one, as you really are setting two flags I would imagine, not just one) Thanks Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 18: 1:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 5546014C8E for ; Sun, 26 Dec 1999 18:01:31 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA42498; Mon, 27 Dec 1999 12:31:24 +1030 (CST) Date: Mon, 27 Dec 1999 12:31:24 +1030 From: Greg Lehey To: Gary Palmer Cc: current@freebsd.org Subject: Re: ``how to'' for Vinum and mirroring after the volume was created? Message-ID: <19991227123124.U1316@freebie.lemis.com> References: <19991227120444.S1316@freebie.lemis.com> <41777.946259657@noop.colo.erols.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <41777.946259657@noop.colo.erols.net> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Sunday, 26 December 1999 at 20:54:17 -0500, Gary Palmer wrote: > Greg Lehey wrote in message ID > <19991227120444.S1316@freebie.lemis.com>: >> Did you forget the 'setupstate' keyword? > > How would that apply? The 2nd disk was not consistant as it was added > after the data was copied onto the first and the old disks removed. Ah. I misunderstood. Yes, in this case you have to revive. >> [reading from the plex being revived] >> How do you determine that? > > Looking at the stats vinum provided. Unfortunately they're gone from > my scrollback buffer, but the 2nd plex was being read from, which is > not something I'd expect from what should have been a straight copy > from the first to the second. Also, if I remember right, the read > data from the first plex was going up more slowly than the written > data to the 2nd plex, which indicates to me that it may indeed have > been round-robining the reads, even though the 2nd plex wasn't > consistant. It occurs to me that it is, in fact, correct to read from a volume being revived. The data is consistent up to the point where the revive has progressed, so the system can read from this area. Check the function checksdstate() in vinumstate.c: if (diskaddr > (sd->revived + sd->plexoffset + (sd->revive_blocksize >> DEV_BSHIFT))) /* we're beyond the end */ return REQUEST_DOWN; else if (diskend > (sd->revived + sd->plexoffset)) { /* we finish beyond the end */ if (writeop) { rq->flags |= XFR_REVIVECONFLICT; /* note a potential conflict */ rq->sdno = sd->sdno; /* and which sd last caused it */ } else return REQUEST_DOWN; } >>> The second question concerns the flag fields. Is there any way to >>> change flags on the fly? e.g. change the volume from being round >>> robin to prefer plex? > >> That's one thing I haven't done yet. It's trivial, but I haven't >> thought of a syntax for the command. Suggestions? > > I think (at least to my mind) the best way to abstract it would be as > readflags/setflags commands, and do it so that it would work for flags > on the volume, plex, subdisk or disk level. I don't know how many > flags you really want to expose to the end-user, but I can imagine as > the product develops, more flags will be added. e.g. veritas has > user-settable comments fields. > > e.g. > > vinum setflag vol01 readpol=prefer preferplex=plex01 > > (that is a tricky one, as you really are setting two flags I would > imagine, not just one) Hmm. This looks too VERITAS-like for my liking. In addition, this isn't a flag. Internally it's represented as a plex index, with -1 meaning "round robin". I've tried to keep away from this sort of stuff. I was thinking of something more like: vinum prefer volfoo plexbar or vinum prefer volfoo -1 The second example is supposed to set round robin. I don't like that syntax either. Maybe the second example should be just vinum prefer volfoo. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 18:23:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 5D6C014C3E for ; Sun, 26 Dec 1999 18:23:33 -0800 (PST) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 122PpX-000AuO-00; Sun, 26 Dec 1999 21:24:15 -0500 To: Greg Lehey Cc: current@freebsd.org From: Gary Palmer Subject: Re: ``how to'' for Vinum and mirroring after the volume was created? In-reply-to: Your message of "Mon, 27 Dec 1999 12:31:24 +1030." <19991227123124.U1316@freebie.lemis.com> Date: Sun, 26 Dec 1999 21:24:15 -0500 Message-ID: <41935.946261455@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote in message ID <19991227123124.U1316@freebie.lemis.com>: > It occurs to me that it is, in fact, correct to read from a volume > being revived. The data is consistent up to the point where the > revive has progressed, so the system can read from this area. Why would it be reading from the reviving plex? The volume wasn't mounted when I was watching the stats, so the only i/o should have been the revive. (Yes, I'm paranoid :) ) > Hmm. This looks too VERITAS-like for my liking. In addition, this > isn't a flag. Internally it's represented as a plex index, with -1 > meaning "round robin". Aaah. That makes sense. > I've tried to keep away from this sort of stuff. Unfortunately a beast as complicated as a LVM has to have the ability to change the way it works on the fly. > The second example is supposed to set round robin. I don't like that > syntax either. Maybe the second example should be just > > vinum prefer volfoo. vinum prefer volfoo none That runs into problems with people calling plexes `none', but in that case they get what they deserve ;) vinum prefer volfoo "" There is some precedent for the null string being used for stuff like this. I can't think of them offhand, but some unix programs take that sort of flag. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 19: 5:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 1429914F7C for ; Sun, 26 Dec 1999 19:05:43 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA42808; Mon, 27 Dec 1999 13:35:08 +1030 (CST) Date: Mon, 27 Dec 1999 13:35:07 +1030 From: Greg Lehey To: Gary Palmer Cc: current@freebsd.org Subject: Re: ``how to'' for Vinum and mirroring after the volume was created? Message-ID: <19991227133507.X1316@freebie.lemis.com> References: <19991227123124.U1316@freebie.lemis.com> <41935.946261455@noop.colo.erols.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <41935.946261455@noop.colo.erols.net> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Sunday, 26 December 1999 at 21:24:15 -0500, Gary Palmer wrote: > Greg Lehey wrote in message ID > <19991227123124.U1316@freebie.lemis.com>: >> It occurs to me that it is, in fact, correct to read from a volume >> being revived. The data is consistent up to the point where the >> revive has progressed, so the system can read from this area. > > Why would it be reading from the reviving plex? The volume wasn't > mounted when I was watching the stats, so the only i/o should have > been the revive. (Yes, I'm paranoid :) ) Again, news for me. You can stop a revive and restart it at a later time; the state information includes the revive pointer. But the only real answer to this one would be to see the statistics. >> Hmm. This looks too VERITAS-like for my liking. In addition, this >> isn't a flag. Internally it's represented as a plex index, with -1 >> meaning "round robin". > > Aaah. That makes sense. > >> I've tried to keep away from this sort of stuff. > > Unfortunately a beast as complicated as a LVM has to have the ability > to change the way it works on the fly. You misunderstand. I've tried to stay away from the complexity of the VERITAS syntax. Sure, I agree that being able to reconfigure on the fly is important. >> The second example is supposed to set round robin. I don't like that >> syntax either. Maybe the second example should be just >> >> vinum prefer volfoo. > > vinum prefer volfoo none > > That runs into problems with people calling plexes `none', but in that > case they get what they deserve ;) Right, that's the down side. I suppose we could include the alternative of a plex index in the syntax. > vinum prefer volfoo "" > > There is some precedent for the null string being used for stuff like > this. I can't think of them offhand, but some unix programs take that > sort of flag. Right, but it's confusing for people new to UNIX. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 20:18:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id B9CDE14D33 for ; Sun, 26 Dec 1999 20:18:23 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS1-p104.rlz.netvision.net.il [62.0.168.106]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id GAA27282; Mon, 27 Dec 1999 06:17:57 +0200 (IST) Message-ID: <3866E8B3.8DAAD96F@freenet.co.uk> Date: Mon, 27 Dec 1999 04:18:59 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: can't get vmware to run ( on -current ) References: <19991226134559.25EE81CA0@overcee.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 Peter Wemm wrote: > > > b) could not open /usr/local/lib/vmware/lib/vmm (no such file or directory) > > That is because /proc/curproc/exe is missing. Under Linux it's a pointer to > the executable file (like our "file" used to be before it was killed). A > trivial patch to reactivate it in a form that is useable by vmware: > > + { DT_REG, N("exe"), Pfile, procfs_validfile }, > > This works because the Pfile support code hasn't been removed. > > Or you can check out the linprocfs stuff, see the vmware pages for a pointer. > It provides a linux-like /compat/linux/proc that provides the missing bits > that linux programs expect. Peter, Since you seem to be fairly well acquainted with the code in question, perhaps you could review and commit the linprocfs stuff? The Pfile support code could then be included in the linprocfs emulator rather than completely removed. I don't think anyone would doubt the usefulness of Linux procfs support. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 20:31:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id BD02A14CF4 for ; Sun, 26 Dec 1999 20:31:35 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS1-p104.rlz.netvision.net.il [62.0.168.106]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id GAA28083; Mon, 27 Dec 1999 06:31:33 +0200 (IST) Message-ID: <3866EBE3.3997DA8B@freenet.co.uk> Date: Mon, 27 Dec 1999 04:32:35 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Cc: gandalf@vilnya.demon.co.uk Subject: pcm hangs in pcmwr Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The kernel dated Dec 6 works fine. The kernel compiled from yesterday's sources detects and attaches the card, but there is no sound. mpg123 (and other programs) hang in "pcmwr" (tsleep in pcm/channel.c). Both the new and old kernels report the card as: pcm0: at port 0x530-0x53f,0x310-0x311 irq 5 drq 1 flags 0xa210 on isa0 The card is non-PnP, so PnP-related fixes are not responsible. I suspect it has something to do with the recent DMA underrun/2nd buffer changes to pcm/channel.c. I'll try to investigate further. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 21:36:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id E93AA14DC0 for ; Sun, 26 Dec 1999 21:36:36 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 8004 invoked from network); 27 Dec 1999 05:36:29 -0000 Received: from lca111.cvzoom.net (63.65.158.111) by ns.cvzoom.net with SMTP; 27 Dec 1999 05:36:29 -0000 Date: Mon, 27 Dec 1999 00:35:25 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: ESS 1868, mpg123, heavy CPU usage 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 Something funny's going on with mpg123 and the pcm sound driver with the ESS 1868. Whenever a clip is playing with mpg123, the load average shoots up to around 2 (when running X). When the clip is "finished", my machine then feels sluggish as if the sound driver is somehow tying up the cpu. Then, the load average drops down to around 1 and stays there. When I start mpg123 again to play a clip, the load average shoots up to 3. Then, the cpu usage becomes unbearable. Of course, rebooting solves the problem. RealPlayer 5.0 and G2 at least don't exhibit this problem. RealPlayer has it's problems, but it doesn't tie up the cpu after RealPlayer has exited. I'm guessing the codec from mpg123 is still active, although the actual program has exited. Of course, sometimes mpg123 doesn't exit after the clip is finished, and I have to kill it manually. It would be nice if we had a special option to ps that showed the resource usage on drivers, because now ps only shows the resource usage on daemons and userland programs. I think newpcm should be a loadable kernel module, as it would make it easy to kill an "out of control" sound driver. Actually, on Linux, I had to unload and reload the sound driver for the ESS 1868 on one occasion. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 26 23: 8:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id D10B11521E for ; Sun, 26 Dec 1999 23:08:07 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: from rina.r.dl.itc.u-tokyo.ac.jp (localhost.r.dl.itc.u-tokyo.ac.jp [127.0.0.1]) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with ESMTP id QAA01035; Mon, 27 Dec 1999 16:08:02 +0900 (JST) Date: Mon, 27 Dec 1999 16:08:01 +0900 Message-ID: <14439.4177.642029.72159A@rina.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: current@freebsd.org Subject: Re: more patch for secondary buffer, polling and DMA emulation in pcm In-Reply-To: In your message of "Sat, 25 Dec 1999 12:06:28 +0900" <14436.13492.839612.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> References: <14429.46098.1195.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14433.63218.157116.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <386278C7.B748EEF5@cvzoom.net> <14434.52947.683451.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14436.13492.839612.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Digital Library Research Division, Information Techinology Centre, The University of Tokyo MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Another fix was made on feeding and sucking pcm data. Now chn_wrfeed() and the other functions do not attempt excessive feeding during DMA transfer to eat up the whole processor. The patch is at: http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227.diff.gz -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 0:40:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 7074B152EE for ; Mon, 27 Dec 1999 00:40:49 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 17932 invoked from network); 27 Dec 1999 08:40:43 -0000 Received: from lca111.cvzoom.net (HELO cvzoom.net) (63.65.158.111) by ns.cvzoom.net with SMTP; 27 Dec 1999 08:40:43 -0000 Message-ID: <386725DC.20B18CF4@cvzoom.net> Date: Mon, 27 Dec 1999 03:39:56 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Seigo Tanimura Cc: current@freebsd.org Subject: Re: more patch for secondary buffer, polling and DMA emulation in pcm References: <14429.46098.1195.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14433.63218.157116.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <386278C7.B748EEF5@cvzoom.net> <14434.52947.683451.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14436.13492.839612.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <14439.4177.642029.72159A@rina.r.dl.itc.u-tokyo.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seigo Tanimura wrote: > > Another fix was made on feeding and sucking pcm data. Now chn_wrfeed() > and the other functions do not attempt excessive feeding during DMA > transfer to eat up the whole processor. The patch is at: > > http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227.diff.gz Hmmm... this seems to have broken the probe at boot time. Here's a sample of my dmesg: unknown0: at port 0x800-0x807 on isa0 unknown1: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 unknown2: at port 0x201 on isa0 - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 3:38:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from gcs.hu (ns.gcs.hu [195.75.249.2]) by hub.freebsd.org (Postfix) with ESMTP id E30A514C9F for ; Mon, 27 Dec 1999 03:38:39 -0800 (PST) (envelope-from mmuller@gcs.hu) Received: from gcs.hu (mmuller@zohar.in.gcs.hu [192.168.1.15]) by gcs.hu (8.9.3/8.9.3/Debian 8.9.3-6) with ESMTP id MAA11025; Mon, 27 Dec 1999 12:41:47 +0100 X-Authentication-Warning: ns.gcs.hu: Host mmuller@zohar.in.gcs.hu [192.168.1.15] claimed to be gcs.hu Message-ID: <3867503C.542DF9BF@gcs.hu> Date: Mon, 27 Dec 1999 12:40:44 +0100 From: MULLER Miklos Organization: GCS Hungary Kft X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.10 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 3:46:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-96.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.224]) by hub.freebsd.org (Postfix) with ESMTP id CB64C1509B; Mon, 27 Dec 1999 03:46:00 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA34000; Mon, 27 Dec 1999 11:45:59 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id LAA82665; Mon, 27 Dec 1999 11:48:42 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912271148.LAA82665@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Maxim Sobolev Cc: current@freebsd.org, brian@freebsd.org, brian@hak.lan.Awfulhak.org Subject: Re: PPP still has problems with config parsing In-Reply-To: Message from Maxim Sobolev of "Sun, 26 Dec 1999 22:43:23 +0200." <38667DEB.309D1295@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Dec 1999 11:48:41 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > tun0: Command: ip-telecom: set dial ABORT BUSY ABORT NO\sCARRIER ABORT > NO\sDIAL\sTONE TIMEOUT 5 "" AT OK-AT-OK AT&F OK > AT#F0$R1%E0S20=8&E2S48=16 OK \dATDP\T TIMEOUT 40 CONNECT [.....] ppp was treating everything from the # to the end of line as a comment. It should be fixed 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 Mon Dec 27 4: 9:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 197F614D95 for ; Mon, 27 Dec 1999 04:09:41 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with UUCP id VAA07741; Mon, 27 Dec 1999 21:09:38 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id VAA32555; Mon, 27 Dec 1999 21:09:15 +0900 (JST) Date: Mon, 27 Dec 1999 21:09:15 +0900 Message-ID: <14439.22251.432880.29321F@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: dmmiller@cvzoom.net Cc: tanimura@r.dl.itc.u-tokyo.ac.jp, current@freebsd.org Subject: Re: more patch for secondary buffer, polling and DMA emulation in pcm In-Reply-To: In your message of "Mon, 27 Dec 1999 03:39:56 -0500" <386725DC.20B18CF4@cvzoom.net> References: <14429.46098.1195.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14433.63218.157116.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <386278C7.B748EEF5@cvzoom.net> <14434.52947.683451.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14436.13492.839612.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <14439.4177.642029.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <386725DC.20B18CF4@cvzoom.net> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Carrots MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Dec 1999 03:39:56 -0500, Donn Miller said: >> http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227.diff.gz Donn> Hmmm... this seems to have broken the probe at boot time. Donn> Here's a sample of my dmesg: (snip) Donn> unknown1: at port Donn> 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 That is odd... The patch does not even touch sbc.c. How does your pnpinfo(1) look like? -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 5:15:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id 828BF14FA2 for ; Mon, 27 Dec 1999 05:15:04 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with UUCP id WAA08361; Mon, 27 Dec 1999 22:15:01 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (localhost [127.0.0.1]) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id WAA02521; Mon, 27 Dec 1999 22:14:19 +0900 (JST) Date: Mon, 27 Dec 1999 22:14:19 +0900 Message-ID: <14439.26155.338725.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: current@freebsd.org Cc: tanimura@r.dl.itc.u-tokyo.ac.jp Subject: Re: more patch for secondary buffer, polling and DMA emulation in pcm In-Reply-To: In your message of "Mon, 27 Dec 1999 16:08:01 +0900" <14439.4177.642029.72159A@rina.r.dl.itc.u-tokyo.ac.jp> References: <14429.46098.1195.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14433.63218.157116.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <386278C7.B748EEF5@cvzoom.net> <14434.52947.683451.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14436.13492.839612.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <14439.4177.642029.72159A@rina.r.dl.itc.u-tokyo.ac.jp> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Carrots MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Dec 1999 16:08:01 +0900, Seigo Tanimura said: Seigo> Another fix was made on feeding and sucking pcm data. Now chn_wrfeed() Seigo> and the other functions do not attempt excessive feeding during DMA Seigo> transfer to eat up the whole processor. The patch is at: Ouch, the patch broke Rollemup, so I fixed just now. The URI is the same. Seigo> http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227.diff.gz -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 10:21:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id DDAAF14EC8 for ; Mon, 27 Dec 1999 10:21:40 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA88820; Mon, 27 Dec 1999 13:20:54 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Mon, 27 Dec 1999 13:20:53 -0500 To: Robert Watson From: Garance A Drosihn Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Cc: Alfred Perlstein , Andre Albsmeier , Warner Losh , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:55 AM -0500 12/24/99, Robert Watson wrote: >... keep in mind that this optimization does not produce behavior >behavior in some cases. For example, imagine that the user has a >number of hard links to the file in question. If the file is copied and >then deleted, then the link count is decremented by one, and the data used >to print is independent of the original file. However, if a single file >system rename is used, the link count remains the same until the end of >the print job, and if any of the other references to the same inode are >modified, the print job will see inconsistent versions of the file (i.e., >it being changed out from under it). Hmm. This was a very good point to bring up, even if people don't use it to modify the file (or do anything else nefarious). The real problem here is that lpr changes the ownership and permissions of the file after moving it. That means that if the user does give us a file with multiple hard links, lpr will repermit *all* copies of the file, not just the version it moved into the spool directory. Clearly we also need to check the inode count. Thanks for that observation! >I do not know whether the current >lpr waits until it finishes copying before returning, but assume so, >meaning that once lpr returns, normally, you are guaranteed that unless >using the symlink option, you can continue to modify the inode in question >with impunity. With this optimization makes that assumption not true. A >caveat is already present for the symlink, "-s", option to this effect. I >believe this also allows users to present files that start out being >within the maximum file size when that is checked, but later add more, >allowing users to avoid the file size limit on print jobs. This is >presumably already present with "-s", and it's possible that lpd checks >for this. Well, for some reason lpr is dumber than that. The spooled datafile ends up being owned by the user who sent the job, and thus the user can go in any time and make changes. That's already true, without this update or '-s' being used. Personally I think that is bad, because it does allow the user to circumvent any checks done at job-submission time. I think I'll write a separate update for that (maybe next year... :-). --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 11:15:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 6DAE1152D5 for ; Mon, 27 Dec 1999 11:15:09 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (boomer.navinet.net [216.67.12.90]) by forrie.net (8.10.0.Beta10/8.9.3) with ESMTP id dBRJF2g00667 for ; Mon, 27 Dec 1999 14:15:03 -0500 (EST) Message-Id: <4.2.2.19991227141115.00a98f00@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 27 Dec 1999 14:14:29 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Installation bug (4.0-19991227-CURRENT) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did a test install against the latest snapshot. The network configuration comes up with "dc0" (we have de0), this "works" in that we were able to perform the network install (so it must be a typo somewhere). However, it results in multiple entries in /etc/rc.conf (three, total), which have to be removed before the network will come up correctly after rebooting. NB, this was an install over a previous 4.0 instance, so there's the possibility that the rc.conf file was edited rather than written over -- though I would doubt that (?). FYI. _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 11:24: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 4FFCB152BA for ; Mon, 27 Dec 1999 11:24:02 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA00914; Mon, 27 Dec 1999 11:28:09 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912271928.LAA00914@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Forrest Aldrich Cc: freebsd-current@freebsd.org Subject: Re: Installation bug (4.0-19991227-CURRENT) In-reply-to: Your message of "Mon, 27 Dec 1999 14:14:29 EST." <4.2.2.19991227141115.00a98f00@216.67.12.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 Dec 1999 11:28:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The 'de' driver has been obsoleted for the 21143 part by the 'dc' driver. You should be using 'dc' for those devices that it supports. > Did a test install against the latest snapshot. > > The network configuration comes up with "dc0" (we have de0), this "works" in that we were able to perform the network install (so it must be a typo somewhere). > > However, it results in multiple entries in /etc/rc.conf (three, total), which have to be removed before the network will come up correctly after rebooting. > > NB, this was an install over a previous 4.0 instance, so there's the possibility that the rc.conf file was edited rather than written over -- though I would doubt that (?). > > FYI. > > > > _F > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 11:32:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id EBB8014E0D for ; Mon, 27 Dec 1999 11:32:48 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 03A1C3E37; Mon, 27 Dec 1999 20:32:47 +0100 (CET) Date: Mon, 27 Dec 1999 20:32:47 +0100 From: Jesper Skriver To: Forrest Aldrich Cc: freebsd-current@freebsd.org Subject: Re: Installation bug (4.0-19991227-CURRENT) Message-ID: <19991227203247.A9977@skriver.dk> References: <4.2.2.19991227141115.00a98f00@216.67.12.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <4.2.2.19991227141115.00a98f00@216.67.12.69>; from forrie@forrie.com on Mon, Dec 27, 1999 at 02:14:29PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 02:14:29PM -0500, Forrest Aldrich wrote: > Did a test install against the latest snapshot. > > The network configuration comes up with "dc0" (we have de0), > this "works" in that we were able to perform the network > install (so it must be a typo somewhere). If you had been following -current, you would know that Bill Paul has written the dc driver, that works with much of the same cards that the de driver does. If both the de and dc driver are available, the dc driver wins. > However, it results in multiple entries in /etc/rc.conf (three, > total), which have to be removed before the network will come > up correctly after rebooting. > > NB, this was an install over a previous 4.0 instance, so there's > the possibility that the rc.conf file was edited rather than written > over -- though I would doubt that (?). That is probably the case ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 11:34:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 71A12152C2 for ; Mon, 27 Dec 1999 11:34:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA05412; Mon, 27 Dec 1999 20:34:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installation bug (4.0-19991227-CURRENT) In-reply-to: Your message of "Mon, 27 Dec 1999 14:14:29 EST." <4.2.2.19991227141115.00a98f00@216.67.12.69> Date: Mon, 27 Dec 1999 20:34:27 +0100 Message-ID: <5410.946323267@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <4.2.2.19991227141115.00a98f00@216.67.12.69>, Forrest Aldrich writes : >Did a test install against the latest snapshot. > >The network configuration comes up with "dc0" (we have de0), this >"works" in that we were able to perform the network install (so it >must be a typo somewhere). No, dc0 is the new and improved driver for the newer tulip chips. >However, it results in multiple entries in /etc/rc.conf (three, >total), which have to be removed before the network will come up >correctly after rebooting. > >NB, this was an install over a previous 4.0 instance, so there's >the possibility that the rc.conf file was edited rather than written >over -- though I would doubt that (?). That is probably what happened here. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 12:50:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from iris.vsrc.uab.edu (iris.vsrc.uab.edu [138.26.156.231]) by hub.freebsd.org (Postfix) with ESMTP id 80F3515015 for ; Mon, 27 Dec 1999 12:50:39 -0800 (PST) (envelope-from emre@iris.vsrc.uab.edu) Received: by iris.vsrc.uab.edu (Postfix, from userid 1001) id D6FBA12509; Mon, 27 Dec 1999 14:52:03 +0000 (GMT) Date: Mon, 27 Dec 1999 14:52:03 +0000 From: Emre To: freebsd-current@freebsd.org Subject: IPFW Message-ID: <19991227145203.A29810@iris.vsrc.uab.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I apologize if this question is not appropriate for this list but... I just installed FreeBSD 4.0-CURRENT (19991226) on a box. I also recompiled the kernel so it would support SMP. All I basicly did is change two lines concerning SMP in the GENERIC kernel (I followed the handbook). The box is running just fine and I am very pleased with it. Here is the problem: I'm trying to firewall it using ipfw, when I issue the command ipfw add deny udp from any to any 1-2200 I get 00000 deny udp from any to any 1-2200 ipfw: setsockopt(IP_FW_ADD): Protocol not available I only changed two lines in the GENERIC kernel. Did I screw it up? I assumed packet filtering was enabled in the GENERIC kernel by default. Can anyone give me hints on how to fix this, or what this message means? I already RTFM and the stuff in the handbook (the man page looks very similar to the stuff that was in the handbook). Any help is greatly appreciated :) (PS: does the IPFILTER package work with FreeBSD? Because I'm used it and ipfw syntax is kinda anal. If so, has anyone tried it and successfully used it? Thanks.) -- Emre Yildirim Fingerprint = B16C EBA7 97FE EF2C 365F C4C4 54AA 3676 5E9E E10A DSS/DH 1024/4064: 0x5E9EE10A/0x2486FEBE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 13: 7: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from beach.silcom.com (beach.silcom.com [199.201.128.19]) by hub.freebsd.org (Postfix) with ESMTP id 0F55C15344 for ; Mon, 27 Dec 1999 13:06:56 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from smarter.than.nu (pm1-6.vpop1.avtel.net [207.71.237.56]) by beach.silcom.com (Postfix) with ESMTP id 67B07145273; Mon, 27 Dec 1999 13:06:53 -0800 (PST) Date: Mon, 27 Dec 1999 13:06:52 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Emre Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPFW In-Reply-To: <19991227145203.A29810@iris.vsrc.uab.edu> 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, 27 Dec 1999, Emre wrote: > Hi, > > I apologize if this question is not appropriate for this list but... > > I just installed FreeBSD 4.0-CURRENT (19991226) on a box. I also recompiled > the kernel so it would support SMP. All I basicly did is change two lines > concerning SMP in the GENERIC kernel (I followed the handbook). The box > is running just fine and I am very pleased with it. Here is the problem: > > I'm trying to firewall it using ipfw, when I issue the command > > ipfw add deny udp from any to any 1-2200 > > I get > > 00000 deny udp from any to any 1-2200 > ipfw: setsockopt(IP_FW_ADD): Protocol not available Add the line: options IPFIREWALL to your kernel config and recompile. See LINT for documentation and other options you may wish to consider. IP Firewalling is not enabled by default in GENERIC. -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 13:12:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from iris.vsrc.uab.edu (iris.vsrc.uab.edu [138.26.156.231]) by hub.freebsd.org (Postfix) with ESMTP id 418C914DA9 for ; Mon, 27 Dec 1999 13:12:39 -0800 (PST) (envelope-from emre@iris.vsrc.uab.edu) Received: by iris.vsrc.uab.edu (Postfix, from userid 1001) id D6E5F1250B; Mon, 27 Dec 1999 15:14:04 +0000 (GMT) Date: Mon, 27 Dec 1999 15:14:04 +0000 From: Emre To: "Brian W. Buchanan" Cc: freebsd-current@freebsd.org Subject: Re: IPFW Message-ID: <19991227151404.A24612@iris.vsrc.uab.edu> References: <19991227145203.A29810@iris.vsrc.uab.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 01:06:52PM -0800, Brian W. Buchanan wrote: > Add the line: > > options IPFIREWALL > > to your kernel config and recompile. See LINT for documentation and other > options you may wish to consider. IP Firewalling is not enabled by > default in GENERIC. Oh Thanks for the quick reply, I will try now :) -- Emre Yildirim Fingerprint = B16C EBA7 97FE EF2C 365F C4C4 54AA 3676 5E9E E10A DSS/DH 1024/4064: 0x5E9EE10A/0x2486FEBE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 13:13:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 3F41914CF1 for ; Mon, 27 Dec 1999 13:13:56 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 9BF99137F69 for ; Mon, 27 Dec 1999 16:13:54 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id QAA13084; Mon, 27 Dec 1999 16:13:48 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14439.54923.884773.393442@trooper.velocet.net> Date: Mon, 27 Dec 1999 16:13:47 -0500 (EST) To: freebsd-current@freebsd.org Subject: How to de-select DMA to ad0? X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had my share of problems with this drive's DMA abilities. I'm convinced that it has none... even though it probes as such. ad0: ATA-0 disk at ata0 as master ad0: ... ad0: 16 secs/int, 1 depth queue, DMA now... when I boot -v, I don't have a chance to write down what it says, but it will hang every time with the following output: ad0: ad-timeout: lost disk contact ata0: resetting drives -- mask=03 status0=50 status1=50 .. And that's it. It never prints out "done" which I see in many of the list messages. Is there a way of disabling DMA on a specific drive? I read a bit of the source, but didn't find any obvious documentation on the issue. (This is all on a kernel compiled from a cvsup this afternoon) Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 13:54:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 028D215437; Mon, 27 Dec 1999 13:54:33 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 122i63-0000GN-00; Mon, 27 Dec 1999 13:54:31 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Russell Cattelan Cc: freebsd-multimedia@freebsd.org, freebsd-current@freebsd.org Subject: Re: es1371 PCI128 Rev 7 patch References: <385F27BF.5CEF274@thebarn.com> Message-Id: Date: Mon, 27 Dec 1999 13:54:31 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem with the PCI128 rev 7 and ASUS boards seem to be solved > with a simple patch. > > Anybody with such a combination please try this patch > ftp://ftp.thebarn.com/FreeBSD/es1371/es1371-src4-PCI128rev7.patch > > Once it is verified to work, I'm sure somebody will want to commit it. dunno what's solved by what, but current is not blasting sound for me. reading the lists, suggestions for adding controller pnp0 seem out of date, as i get rip.psg.com:/sys/i386/conf# config RIP Don't forget to do a ``make depend'' Warning: controller "pnp" is unknown Kernel build directory is ../../compile/RIP the patch mentioned above does not take with current.9912270034, two rejects. so i expect a commit was done. dmesg whines pci0: Intel PIIX4 ATA controller (vendor=0x8086, dev=0x7111) at 4.1 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 4.2 irq 19 ... bktr0: irq 18 at device 10.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 bktr0: Hauppauge Model 61111 A M bktr0: Detected a MSP3430G-A1 at 0x80 Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo. pci0: unknown card (vendor=0x109e, dev=0x0878) at 10.1 irq 18 pcm0: irq 17 at device 11.0 on pci0 ac97: dac not ready ... kernel sez device pcm0 randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 14: 3: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id ACD56150E3 for ; Mon, 27 Dec 1999 14:02:57 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA26218; Mon, 27 Dec 1999 17:02:45 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Mon, 27 Dec 1999 17:02:45 -0500 To: Robert Watson From: Garance A Drosihn Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Cc: Alfred Perlstein , Andre Albsmeier , Warner Losh , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:55 AM -0500 12/24/99, Robert Watson wrote: >For example, imagine that the user has a >number of hard links to the file in question. Okay, here's my newer version of the code, which takes into account multiple hard links, and also makes it so the spooled data file is owned by daemon instead of the user. This works fine. At some later point I'll write an update so the spooled data file is owned by daemon in other cases, too. Further comments or observations welcome. If this looks okay I'll submit this as a new PR. Index: lpr/lpr.c =================================================================== RCS file: /Users/cvsdepot/lpr-fbsd/lpr/lpr.c,v retrieving revision 1.1.1.1 diff -U5 -r1.1.1.1 lpr.c --- lpr.c 1999/11/30 16:15:22 1.1.1.1 +++ lpr.c 1999/12/27 21:58:39 @@ -382,10 +382,69 @@ nact++; continue; } if (sflag) printf("%s: %s: not linked, copying instead\n", name, arg); + + if (f) { + /* + * The user wants the file removed after it is copied, + * so see if it can be mv'ed instead of copy/unlink'ed. + * This will be much faster and better than copying the + * file, especially for larger files. Can be very + * useful for services like samba, pcnfs, CAP, et al. + */ + int ret, didlink; + struct stat statb2; + seteuid(euid); + didlink = 0; + /* don't do this if the user's file is a symlink */ + if (lstat(arg, &statb) < 0) goto nohardlink; + if (S_ISLNK(statb.st_mode)) goto nohardlink; + /* if the attempt to link fails, abandon the move */ + if (link(arg, dfname) != 0) goto nohardlink; + didlink = 1; + /* make sure the user hasn't tried to trick us via + * any race conditions */ + if (lstat(dfname, &statb2) < 0) goto nohardlink; + if (statb.st_dev != statb2.st_dev) goto nohardlink; + if (statb.st_ino != statb2.st_ino) goto nohardlink; + /* skip if the file already had multiple hard links, + * because changing the owner and access-bits would + * change ALL versions of the file */ + if (statb2.st_nlink > 2) goto nohardlink; + + /* if we can access and remove the given file without + * special setuid-ness then this method is safe. */ + seteuid(uid); + ret = access(dfname, R_OK); + if (ret == 0) + ret = unlink(arg); + seteuid(euid); + /* the user does not have access to read or remove + * this file, so abandon the move and fall back to + * the usual (copy) methods. */ + if (ret != 0) goto nohardlink; + + /* unlink of user file was successful. fixup perms, + * add entries to control file, and skip copy step */ + chown(dfname, pp->daemon_user, getegid()); + chmod(dfname, S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP); + seteuid(uid); + if (format == 'p') + card('T', title ? title : arg); + for (i = 0; i < ncopies; i++) + card(format, &dfname[inchar-2]); + card('U', &dfname[inchar-2]); + card('N', arg); + nact++; + continue; +nohardlink: + if (didlink) unlink(dfname); + seteuid(uid); /* restore old uid */ + } /* end: if (f) */ + if ((i = open(arg, O_RDONLY)) < 0) { printf("%s: cannot open %s\n", name, arg); } else { copy(pp, i, arg); (void) close(i); =================================================================== --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 14: 3:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id C3B26152E1 for ; Mon, 27 Dec 1999 14:03:20 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA29831; Mon, 27 Dec 1999 22:59:57 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA03394; Mon, 27 Dec 1999 22:02:29 +0100 (CET) (envelope-from wilko) Date: Mon, 27 Dec 1999 22:02:29 +0100 From: Wilko Bulte To: Emre Cc: freebsd-current@FreeBSD.ORG Subject: Re: IPFW Message-ID: <19991227220229.A3327@yedi.iaf.nl> References: <19991227145203.A29810@iris.vsrc.uab.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991227145203.A29810@iris.vsrc.uab.edu>; from emre@iris.vsrc.uab.edu on Mon, Dec 27, 1999 at 02:52:03PM +0000 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 02:52:03PM +0000, Emre wrote: > I apologize if this question is not appropriate for this list but... It is not I'm afraid. > I'm trying to firewall it using ipfw, when I issue the command > > ipfw add deny udp from any to any 1-2200 > > I get > > 00000 deny udp from any to any 1-2200 > ipfw: setsockopt(IP_FW_ADD): Protocol not available > > I only changed two lines in the GENERIC kernel. Did I screw it up? > I assumed packet filtering was enabled in the GENERIC kernel by default. Wrong assumption. See /sys/i386/conf/LINT for the entries you need to enable the firewall code. > Can anyone give me hints on how to fix this, or what this message means? > I already RTFM and the stuff in the handbook (the man page looks very similar > to the stuff that was in the handbook). Is there any reason for you to run -current? Because if there isn't you'd be better off using a -stable version of FreeBSD. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 14:30:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.170.50]) by hub.freebsd.org (Postfix) with ESMTP id 500D114A00; Mon, 27 Dec 1999 14:30:07 -0800 (PST) (envelope-from cattelan@thebarn.com) Received: from thebarn.com (lupo.borg.umn.edu [160.94.170.114]) by lips.borg.umn.edu (8.9.3/8.9.1) with ESMTP id QAA88601; Mon, 27 Dec 1999 16:30:01 -0600 (CST) Message-ID: <3867E868.CDA0E794@thebarn.com> Date: Mon, 27 Dec 1999 16:30:00 -0600 From: Russell Cattelan X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Randy Bush Cc: freebsd-multimedia@freebsd.org, freebsd-current@freebsd.org Subject: Re: es1371 PCI128 Rev 7 patch References: <385F27BF.5CEF274@thebarn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randy Bush wrote: > > The problem with the PCI128 rev 7 and ASUS boards seem to be solved > > with a simple patch. > > > > Anybody with such a combination please try this patch > > ftp://ftp.thebarn.com/FreeBSD/es1371/es1371-src4-PCI128rev7.patch > > > > Once it is verified to work, I'm sure somebody will want to commit it. > > dunno what's solved by what, but current is not blasting sound for me. > reading the lists, suggestions for adding > > controller pnp0 The pnp stuff shouldn't have anything to do with this card, it's pi. Cameron did a bunch of code clean up, which is why the patch didn't apply. I generated a new patch that should apply to current -current. ftp://ftp.thebarn.com/FreeBSD/es1371/es1371-src4-PCI128rev7.2,patch > > > > seem out of date, as i get > > rip.psg.com:/sys/i386/conf# config RIP > Don't forget to do a ``make depend'' > Warning: controller "pnp" is unknown > Kernel build directory is ../../compile/RIP > > the patch mentioned above does not take with current.9912270034, two > rejects. so i expect a commit was done. > > dmesg whines > > pci0: Intel PIIX4 ATA controller (vendor=0x8086, dev=0x7111) at 4.1 > pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 4.2 irq 19 > ... > bktr0: irq 18 at device 10.0 on pci0 > iicbb0: on bti2c0 > iicbus0: on iicbb0 master-only > smbus0: on bti2c0 > bktr0: Hauppauge Model 61111 A M > bktr0: Detected a MSP3430G-A1 at 0x80 > Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo. > pci0: unknown card (vendor=0x109e, dev=0x0878) at 10.1 irq 18 > pcm0: irq 17 at device 11.0 on pci0 > ac97: dac not ready > ... > > kernel sez > > device pcm0 > > randy -- Russell Cattelan cattelan@thebarn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 15: 1:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from iris.vsrc.uab.edu (iris.vsrc.uab.edu [138.26.156.231]) by hub.freebsd.org (Postfix) with ESMTP id DB0A714BFE for ; Mon, 27 Dec 1999 15:01:37 -0800 (PST) (envelope-from emre@iris.vsrc.uab.edu) Received: by iris.vsrc.uab.edu (Postfix, from userid 1001) id 713921250B; Mon, 27 Dec 1999 17:02:58 +0000 (GMT) Date: Mon, 27 Dec 1999 17:02:58 +0000 From: Emre To: Wilko Bulte Cc: freebsd-current@freebsd.org Subject: Re: IPFW Message-ID: <19991227170258.A25978@iris.vsrc.uab.edu> References: <19991227145203.A29810@iris.vsrc.uab.edu> <19991227220229.A3327@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <19991227220229.A3327@yedi.iaf.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 10:02:29PM +0100, Wilko Bulte wrote: > Is there any reason for you to run -current? Because if there isn't you'd > be better off using a -stable version of FreeBSD. Not really. All my other boxes (NetBSD/OpenBSD) run -current so I'm used to be on the "bleeding edge" I figured it would be enabled by default, since FreeBSD promises to be _the_ Server O/S. Actually I haven't tried -release or -stable...I'm willing to take the chance. BTW, I fixed the firewalling stuff, ipfw still has a bit anal syntax but I think I got it working. Thanks for the help :) -- Emre Yildirim Fingerprint = B16C EBA7 97FE EF2C 365F C4C4 54AA 3676 5E9E E10A DSS/DH 1024/4064: 0x5E9EE10A/0x2486FEBE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 15:35:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 1236714A1F; Mon, 27 Dec 1999 15:35:24 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 122jfe-0000As-00; Mon, 27 Dec 1999 15:35:22 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Russell Cattelan Cc: freebsd-multimedia@freebsd.org, freebsd-current@freebsd.org Subject: Re: es1371 PCI128 Rev 7 patch References: <385F27BF.5CEF274@thebarn.com> <3867E868.CDA0E794@thebarn.com> Message-Id: Date: Mon, 27 Dec 1999 15:35:22 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> dunno what's solved by what, but current is not blasting sound for me. >> reading the lists, suggestions for adding >> controller pnp0 > The pnp stuff shouldn't have anything to do with this card, it's pi. ^c unnerstand. but there's stuff on the current list saying to use that with the pci128, so i thought i would debunk it. > ftp://ftp.thebarn.com/FreeBSD/es1371/es1371-src4-PCI128rev7.2,patch yes! works fine on my asus p2b-ds with current as of this morning. thank you. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 15:49:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id B0086152D1 for ; Mon, 27 Dec 1999 15:49:51 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 122jtf-0000fq-00 for freebsd-current@freebsd.org; Mon, 27 Dec 1999 15:49:51 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: unknown pci card Message-Id: Date: Mon, 27 Dec 1999 15:49:51 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG any clue how i can find out what this puppy is Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo. -> pci0: unknown card (vendor=0x109e, dev=0x0878) at 10.1 irq 18 pcm0: irq 17 at device 11.0 on pci0 i think everything in the box is working. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 15:58: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 85E4814D7D for ; Mon, 27 Dec 1999 15:58:00 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA02398; Mon, 27 Dec 1999 15:59:59 -0800 Date: Mon, 27 Dec 1999 15:59:59 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Randy Bush Cc: FreeBSD Current Subject: Re: unknown pci card In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Dec 1999, Randy Bush wrote: > any clue how i can find out what this puppy is > > Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo. > -> pci0: unknown card (vendor=0x109e, dev=0x0878) at 10.1 irq 18 Go to http://www.pcisig.com/membership/vendors/sorted.html to look up vendor ids (this one's a brooktree part) > pcm0: irq 17 at device 11.0 on pci0 > > i think everything in the box is working. > > randy > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 15:59: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 264BD152E3 for ; Mon, 27 Dec 1999 15:59:01 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id SAA26093 for ; Mon, 27 Dec 1999 18:59:00 -0500 (EST) (envelope-from efutch@nyct.net) Date: Mon, 27 Dec 1999 18:59:00 -0500 (EST) From: "Eric D. Futch" To: freebsd-current@freebsd.org Subject: if_fxp.c Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is from -current as of Wed Dec 22 01:48:17 EST 1999 ../../pci/if_fxp.c: In function `fxp_intr': ../../pci/if_fxp.c:1069: warning: label `getit' defined but not used ../../pci/if_fxp.c:1064: warning: label `dropit' defined but not used -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 16: 6:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id CDF9614DFC for ; Mon, 27 Dec 1999 16:06:34 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id TAA27195 for ; Mon, 27 Dec 1999 19:06:34 -0500 (EST) (envelope-from efutch@nyct.net) Date: Mon, 27 Dec 1999 19:06:33 -0500 (EST) From: "Eric D. Futch" To: freebsd-current@FreeBSD.ORG Subject: Re: if_fxp.c 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 hehe oops.. follow up to my own message this is for -stable :) -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Mon, 27 Dec 1999, Eric D. Futch wrote: This is from -current as of Wed Dec 22 01:48:17 EST 1999 ../../pci/if_fxp.c: In function `fxp_intr': ../../pci/if_fxp.c:1069: warning: label `getit' defined but not used ../../pci/if_fxp.c:1064: warning: label `dropit' defined but not used -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 16:12:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 43FE5152D5 for ; Mon, 27 Dec 1999 16:12:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA34430; Mon, 27 Dec 1999 16:12:16 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Dec 1999 16:12:16 -0800 (PST) From: Matthew Dillon Message-Id: <199912280012.QAA34430@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: Proposed patch to fix VN device (again) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sigh. Ok, I've fixed the VN device. Again. It looks like the removal of /dev/drum removed a little too much. We need the device infrastructure to support the VN device's use of swap backing store. This patch below is a commit candidate. It could use a review, then I'll commit it. -Matt Index: swap_pager.h =================================================================== RCS file: /home/ncvs/src/sys/vm/swap_pager.h,v retrieving revision 1.27 diff -u -r1.27 swap_pager.h --- swap_pager.h 1999/11/18 06:55:40 1.27 +++ swap_pager.h 1999/12/27 23:59:49 @@ -106,6 +106,7 @@ /* choose underlying swap device and queue up I/O */ struct buf; +struct vnode *vm_swap_makevnode __P((void)); void swstrategy __P((struct buf *bp)); /* probably needs to move elsewhere */ #endif Index: vm_swap.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_swap.c,v retrieving revision 1.93 diff -u -r1.93 vm_swap.c --- vm_swap.c 1999/12/15 23:02:35 1.93 +++ vm_swap.c 1999/12/28 00:05:55 @@ -68,6 +68,42 @@ static int nswdev = NSWAPDEV; int vm_swap_size; +#define CDEV_MAJOR 4 + +static struct cdevsw sw_cdevsw = { + /* open */ nullopen, + /* close */ nullclose, + /* read */ noread, + /* write */ nowrite, + /* ioctl */ noioctl, + /* poll */ nopoll, + /* mmap */ nommap, + /* strategy */ swstrategy, + /* name */ "sw", + /* maj */ CDEV_MAJOR, + /* dump */ nodump, + /* psize */ nopsize, + /* flags */ D_DISK, + /* bmaj */ -1 +}; + +struct vnode * +vm_swap_makevnode(void) +{ + struct vnode *vp = NULL; + + if (getnewvnode(VT_NON, NULL, spec_vnodeop_p, &vp)) { + panic("Cannot get vnode for swapdev"); + return(NULL); + } + vp->v_rdev = make_dev(&sw_cdevsw, 1, UID_ROOT, GID_KMEM, + 0640, "swapdev"); + vp->v_rdev->si_bsize_phys = PAGE_SIZE; + vp->v_rdev->si_bsize_best = PAGE_SIZE; + vp->v_type = VCHR; + return(vp); +} + /* * swstrategy: * Index: swap_pager.c =================================================================== RCS file: /home/ncvs/src/sys/vm/swap_pager.c,v retrieving revision 1.129 diff -u -r1.129 swap_pager.c --- swap_pager.c 1999/11/22 15:27:09 1.129 +++ swap_pager.c 1999/12/28 00:01:24 @@ -329,10 +329,7 @@ swhash_mask = n - 1; - n = getnewvnode(VT_NON, NULL, spec_vnodeop_p, &swapdev_vp); - if (n) - panic("Cannot get vnode for swapdev"); - swapdev_vp->v_type = VBLK; + swapdev_vp = vm_swap_makevnode(); } /* Index: /usr/src/sys/conf/majors =================================================================== RCS file: /home/ncvs/src/sys/conf/majors,v retrieving revision 1.94 diff -u -r1.94 majors --- majors 1999/12/17 19:56:39 1.94 +++ majors 1999/12/27 23:27:37 @@ -21,7 +21,7 @@ 1 ctty /dev/tty 2 mm /dev/mem,kmem,etc 3 wd ST506 disk controller (with IDE extensions) -4 was:swap /dev/drum +4 swap /dev/drum 5 pts pseudo tty "tty" half 6 ptc pseudo tty "master" half 7 log system log To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 16:14:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 7032E14C4E for ; Mon, 27 Dec 1999 16:14:36 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 122kHc-0002EZ-00 for freebsd-current@freebsd.org; Mon, 27 Dec 1999 16:14:36 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Current Subject: Re: buildworld failure Message-Id: Date: Mon, 27 Dec 1999 16:14:36 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG so, to go for 3.4 to -current i had to o comment kerberos4 and perl from /etc/make.conf o build o build and install perl right in the directory o the usual cruft it works. and it fixed o wl0 o my dlt free bus error still working on kerberos, but i have learned to care less and less about it. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 16:23:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 878541517F for ; Mon, 27 Dec 1999 16:23:30 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id BAA07429; Tue, 28 Dec 1999 01:23:16 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-reply-to: Your message of "Mon, 27 Dec 1999 16:12:16 PST." <199912280012.QAA34430@apollo.backplane.com> Date: Tue, 28 Dec 1999 01:23:16 +0100 Message-ID: <7427.946340596@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912280012.QAA34430@apollo.backplane.com>, Matthew Dillon writes: > Sigh. Ok, I've fixed the VN device. Again. It looks like the removal of > /dev/drum removed a little too much. We need the device infrastructure > to support the VN device's use of swap backing store. > > This patch below is a commit candidate. It could use a review, then I'll > commit it. Could you please explain why you need this ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 16:27: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D99201529C for ; Mon, 27 Dec 1999 16:27:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA34572; Mon, 27 Dec 1999 16:26:59 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Dec 1999 16:26:59 -0800 (PST) From: Matthew Dillon Message-Id: <199912280026.QAA34572@apollo.backplane.com> To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) References: <7427.946340596@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In message <199912280012.QAA34430@apollo.backplane.com>, Matthew Dillon writes: : :> Sigh. Ok, I've fixed the VN device. Again. It looks like the removal of :> /dev/drum removed a little too much. We need the device infrastructure :> to support the VN device's use of swap backing store. :> :> This patch below is a commit candidate. It could use a review, then I'll :> commit it. : :Could you please explain why you need this ? : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." :FreeBSD -- It will take a long time before progress goes too far! VN calls vm_pager_strategy() which collects I/O in filesystem buffers (bp)'s in order to cluster the I/O, and you cannot initiate I/O on filesystem buffers without a valid b_dev. So, the jist of the problem is that in order to get reasonable performance out of the thing (i.e. not issue 4K I/O's to the disk), we have to use filesystem buffers which means the bp must be properly initialized. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 16:28:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 7519915291 for ; Mon, 27 Dec 1999 16:28:03 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id SAA18539 for ; Mon, 27 Dec 1999 18:28:02 -0600 (CST) Date: Mon, 27 Dec 1999 18:28:02 -0600 (CST) From: Steve Price To: freebsd-current@FreeBSD.org Subject: troubles with X Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I just rebooted my -current box for the first time in a long time. Everything on this box is freshly compiled (including X) as of only a couple of hours ago. I even mergemaster'd for good measure. For some reason now I can't startx(1) as either myself or root. I type startx and the PAM auth routines loop forever printing out 'Password:'. I comment out the last two lines in /etc/pam.conf and I get an authentication failure (as I should). Anyone have any ideas what I'm doing wrong? What is the correct method to start X on -current nowadays? Thanks. -steve PS: I'd search the mailing lists but I can't get to my browser and I'm not so good with lynx. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 16:32:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from chain.freebsd.os.org.za (chain.freebsd.os.org.za [196.7.162.242]) by hub.freebsd.org (Postfix) with ESMTP id A0F6214F99 for ; Mon, 27 Dec 1999 16:30:34 -0800 (PST) (envelope-from khetan@freebsd.os.org.za) Received: by chain.freebsd.os.org.za (Postfix, from userid 1000) id EC2EA35627; Tue, 28 Dec 1999 02:30:27 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by chain.freebsd.os.org.za (Postfix) with ESMTP id B361631915 for ; Tue, 28 Dec 1999 02:30:27 +0200 (SAST) Date: Tue, 28 Dec 1999 02:30:27 +0200 (SAST) From: Khetan Gajjar To: current@freebsd.org Subject: newpcm and non-PnP SoundBlaster Vibra 16 4.13 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I have been following the thread(s) about getting the SoundBlaster Vibra 16 sound-cards working in -current, and it appears that if you have a PnP card, it seems to be working. I do not have a PnP version of this card, and the last time I was able to get the sound card recognised was October 2nd. A verbose boot of that kernel reveals sb_probe: no addr, trying (0x220, 0x240) pcm: 4c000 pcm: setmap 4d0000, ff00; 0xc80c500 -> 4d000 and /dev/sndstat reveals FreeBSD Audio Driver (newpcm) Oct 2 1999 14:30:27 Installed devices: pcm0: at io 0x220 irq 10 drq 3:7 (1/1 channels duplex) With subsequent kernels, including a -current kernel from 20 Dec, the sound card is not detected. The definitions I'm using in my kernel currently (no pun intended :) are #sound card device pcm0 device sbc0 at isa? port ? irq 10 drq 3 flags 0x17 as compared to what I had device pcm0 at isa? port ? irq 10 drq 3 flags 0x17 The card is probed if the machine is booted with a kernel of Oct 2, and not probed if the machine is botted with a kernel of Dec 20. The only other thing I can think of is that the old kernel had support for PnP, whereas the new ones doesn't. This shouldn't matter though if I'm supplying the parameters directly to the card. Khetan Gajjar. --- khetan@uunet.co.za * khetan@os.org.za * PGP Key, contact UUNET South Africa * FreeBSD enthusiast * details and other http://www.uunet.co.za/ * http://www.freebsd.org/ * information at System Administration * http://link.os.org.za/ * kg+details@os.org.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 16:44:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 5AAC514CE8 for ; Mon, 27 Dec 1999 16:44:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id BAA08504; Tue, 28 Dec 1999 01:44:15 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-reply-to: Your message of "Mon, 27 Dec 1999 16:26:59 PST." <199912280026.QAA34572@apollo.backplane.com> Date: Tue, 28 Dec 1999 01:44:15 +0100 Message-ID: <8502.946341855@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912280026.QAA34572@apollo.backplane.com>, Matthew Dillon writes: > VN calls vm_pager_strategy() which collects I/O in filesystem buffers > (bp)'s in order to cluster the I/O, and you cannot initiate I/O on > filesystem buffers without a valid b_dev. > > So, the jist of the problem is that in order to get reasonable performance > out of the thing (i.e. not issue 4K I/O's to the disk), we have to use > filesystem buffers which means the bp must be properly initialized. vm_pager_strategy() branches out based on the object type and ends up in swap_pager_strategy() which only uses b_dev after calling swstrategy() then only in a diagnostic printf which we had better never reach. swstrategy() which initializes bp->b_dev to the right physical device. I'm afraid I don't see why or where we would need the bogus /dev/drum dev_t. Furthermore, since we have already clustered above the VN device, I seriously doubt the utility of doing it again between VN and the swapdevice. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 17: 2: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id ADEA914E86 for ; Mon, 27 Dec 1999 17:01:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA34874; Mon, 27 Dec 1999 17:01:55 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Dec 1999 17:01:55 -0800 (PST) From: Matthew Dillon Message-Id: <199912280101.RAA34874@apollo.backplane.com> To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) References: <8502.946341855@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In message <199912280026.QAA34572@apollo.backplane.com>, Matthew Dillon writes: : :> VN calls vm_pager_strategy() which collects I/O in filesystem buffers :> (bp)'s in order to cluster the I/O, and you cannot initiate I/O on :> filesystem buffers without a valid b_dev. :> :> So, the jist of the problem is that in order to get reasonable performance :> out of the thing (i.e. not issue 4K I/O's to the disk), we have to use :> filesystem buffers which means the bp must be properly initialized. : :vm_pager_strategy() branches out based on the object type and ends up :in swap_pager_strategy() which only uses b_dev after calling swstrategy() :then only in a diagnostic printf which we had better never reach. : :swstrategy() which initializes bp->b_dev to the right physical device. : :I'm afraid I don't see why or where we would need the bogus /dev/drum dev_t. : :Furthermore, since we have already clustered above the VN device, :I seriously doubt the utility of doing it again between VN and the :swapdevice. : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." :FreeBSD -- It will take a long time before progress goes too far! Umm. Poul, I know you don't like the idea but you obviously do not understand the code in question. First, you are confusing the underlying swap devices that we swapon on with the parent swap device that controls them. The parent swap device needs to have a dev_t - it does not currently have one, and this is the entry point that the buffers are going into. The underlying swap devices *already* have a dev_t. My kernel crashes on a NULL bp->b_dev. In fact, it also crashes on a NULL vp->v_rdev. Without the patch. So if you are trying to say that b_dev is being magically set I gotta tell you that my kernel dumps say otherwise. Second, the clustering done above the VN device is done by the filesystem and has no understanding of whether the underlying media controlled by the VN device can itself be clustered in the same way. When using swap as backing store what may appear to be clusterable by the filesystem may actually *NOT* be clusterable when you get into the swap device due to potentially non-contiguous mappings as well as border-crossings between interleaved swap devices. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 17:10:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4750114E13 for ; Mon, 27 Dec 1999 17:10:34 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id CAA09893; Tue, 28 Dec 1999 02:10:24 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-reply-to: Your message of "Mon, 27 Dec 1999 17:01:55 PST." <199912280101.RAA34874@apollo.backplane.com> Date: Tue, 28 Dec 1999 02:10:23 +0100 Message-ID: <9890.946343423@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912280101.RAA34874@apollo.backplane.com>, Matthew Dillon writes: > First, you are confusing the underlying swap devices that we swapon on > with the parent swap device that controls them. The parent swap device > needs to have a dev_t - it does not currently have one, and this is > the entry point that the buffers are going into. The underlying swap > devices *already* have a dev_t. My kernel crashes on a NULL bp->b_dev. > In fact, it also crashes on a NULL vp->v_rdev. And where in the code does this crash happen ? > Second, the clustering done above the VN device is done by the > filesystem and has no understanding of whether the underlying media > controlled by the VN device can itself be clustered in the same way. > When using swap as backing store what may appear to be clusterable > by the filesystem may actually *NOT* be clusterable when you get into > the swap device due to potentially non-contiguous mappings as well > as border-crossings between interleaved swap devices. So you need to cluster all the way through the VN device ? Obviously clustering on just one side will not buy you anything. Tough luck... It sounds more and more like the mistake here is for VN to have a specfs VOP vector on top, I think it needs its own VOP vector so it can get hold of the VOP_BMAP function... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 17:21:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D5CEC15266 for ; Mon, 27 Dec 1999 17:21:39 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA35049; Mon, 27 Dec 1999 17:21:35 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Dec 1999 17:21:35 -0800 (PST) From: Matthew Dillon Message-Id: <199912280121.RAA35049@apollo.backplane.com> To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) References: <9890.946343423@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In message <199912280101.RAA34874@apollo.backplane.com>, Matthew Dillon writes: : :> First, you are confusing the underlying swap devices that we swapon on :> with the parent swap device that controls them. The parent swap device :> needs to have a dev_t - it does not currently have one, and this is :> the entry point that the buffers are going into. The underlying swap :> devices *already* have a dev_t. My kernel crashes on a NULL bp->b_dev. :> In fact, it also crashes on a NULL vp->v_rdev. : :And where in the code does this crash happen ? #9 0xc023c5b3 in trap () #10 0xc014b862 in devsw () #11 0xc017fa4a in vn_isdisk () #12 0xc018e1f3 in spec_strategy () #13 0xc020eb42 in flushchainbuf () #14 0xc0202e1e in swap_pager_strategy () #15 0xc020e675 in vm_pager_strategy () #9 0xc023c5e3 in trap () #10 0xc014b862 in devsw () #11 0xc018e26e in spec_strategy () #12 0xc020eb72 in flushchainbuf () #13 0xc0202e4e in swap_pager_strategy () #14 0xc020e6a5 in vm_pager_strategy () #9 0xc023c5c3 in trap () #10 0xc018e23f in spec_strategy () #11 0xc020eb52 in flushchainbuf () #12 0xc0202e2e in swap_pager_strategy () #13 0xc020e685 in vm_pager_strategy () :> Second, the clustering done above the VN device is done by the :> filesystem and has no understanding of whether the underlying media :> controlled by the VN device can itself be clustered in the same way. :> When using swap as backing store what may appear to be clusterable :> by the filesystem may actually *NOT* be clusterable when you get into :> the swap device due to potentially non-contiguous mappings as well :> as border-crossings between interleaved swap devices. : :So you need to cluster all the way through the VN device ? Obviously :clustering on just one side will not buy you anything. Tough luck... : :It sounds more and more like the mistake here is for VN to have a :specfs VOP vector on top, I think it needs its own VOP vector so :it can get hold of the VOP_BMAP function... : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." Ummm. The VN device is not a filesystem, it's a 'disk'. The UFS filesystem does not recursively VOP_BMAP down into the underlying media so implementing VOP_BMAP in VN would not help. We could implement our own set of device vectors but it would be rather pointless since specfs's device vectors do everything we want. And, in anycase, I am not going to spend hours putting together a long involved patch when a simple short patch suffices. If you want to spend the time to come up with your own patch (that doesn't screw the pooch in regards to cluster performance!), then I'm all ears, otherwise this patch is what is going to go in for the 4.0 release. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 17:40: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 6380214BCE for ; Mon, 27 Dec 1999 17:40:01 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id CAA11322; Tue, 28 Dec 1999 02:39:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-reply-to: Your message of "Mon, 27 Dec 1999 17:21:35 PST." <199912280121.RAA35049@apollo.backplane.com> Date: Tue, 28 Dec 1999 02:39:53 +0100 Message-ID: <11320.946345193@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ahh, I see the mistake. All you need to fix this is to add a new function: void flushswchainbuf(struct buf *nbp) { if (nbp->b_bcount) { nbp->b_bufsize = nbp->b_bcount; if ((nbp->b_flags & B_READ) == 0) nbp->b_dirtyend = nbp->b_bcount; BUF_KERNPROC(nbp); swstrategy(nbp); } else { biodone(nbp); } } And use this instead of flushchainbuf() in swap_pager_strategy(). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 17:43:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C90A514BCE for ; Mon, 27 Dec 1999 17:43:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA35278; Mon, 27 Dec 1999 17:43:19 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Dec 1999 17:43:19 -0800 (PST) From: Matthew Dillon Message-Id: <199912280143.RAA35278@apollo.backplane.com> To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) References: <11320.946345193@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : :Ahh, I see the mistake. : :All you need to fix this is to add a new function: : : void : flushswchainbuf(struct buf *nbp) : { : if (nbp->b_bcount) { : nbp->b_bufsize = nbp->b_bcount; : if ((nbp->b_flags & B_READ) == 0) : nbp->b_dirtyend = nbp->b_bcount; : BUF_KERNPROC(nbp); : swstrategy(nbp); : } else { : biodone(nbp); : } : } : :And use this instead of flushchainbuf() in swap_pager_strategy(). : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." Uh... no. The chain buffer routines are supposed to be generic. In fact, all the filesystem buffer cache I/O routines are supposed to be generic. There is no way I'm going to pollute them to special case swap. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 17:48:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4565F1530E for ; Mon, 27 Dec 1999 17:48:16 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id CAA11812; Tue, 28 Dec 1999 02:48:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-reply-to: Your message of "Mon, 27 Dec 1999 17:43:19 PST." <199912280143.RAA35278@apollo.backplane.com> Date: Tue, 28 Dec 1999 02:48:09 +0100 Message-ID: <11809.946345689@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912280143.RAA35278@apollo.backplane.com>, Matthew Dillon writes: >: >:Ahh, I see the mistake. >: >:All you need to fix this is to add a new function: >: >: void >: flushswchainbuf(struct buf *nbp) >: { >: if (nbp->b_bcount) { >: nbp->b_bufsize = nbp->b_bcount; >: if ((nbp->b_flags & B_READ) == 0) >: nbp->b_dirtyend = nbp->b_bcount; >: BUF_KERNPROC(nbp); >: swstrategy(nbp); >: } else { >: biodone(nbp); >: } >: } >: >:And use this instead of flushchainbuf() in swap_pager_strategy(). >: >:-- >:Poul-Henning Kamp FreeBSD coreteam member >:phk@FreeBSD.ORG "Real hackers run -current on their laptop." > > Uh... no. The chain buffer routines are supposed to be generic. In fact, > all the filesystem buffer cache I/O routines are supposed to be generic. > There is no way I'm going to pollute them to special case swap. Ok, fair enough: Then stop abusing struct buf for swap device access :-) If you want to abuse struct buf for swap device access, you will need to special case it as applicable. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 17:54: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1ADF115042 for ; Mon, 27 Dec 1999 17:54:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA35369; Mon, 27 Dec 1999 17:53:57 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Dec 1999 17:53:57 -0800 (PST) From: Matthew Dillon Message-Id: <199912280153.RAA35369@apollo.backplane.com> To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) References: <11809.946345689@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>:-- :>:Poul-Henning Kamp FreeBSD coreteam member :>:phk@FreeBSD.ORG "Real hackers run -current on their laptop." :> :> Uh... no. The chain buffer routines are supposed to be generic. In fact, :> all the filesystem buffer cache I/O routines are supposed to be generic. :> There is no way I'm going to pollute them to special case swap. : :Ok, fair enough: Then stop abusing struct buf for swap device access :-) : :If you want to abuse struct buf for swap device access, you will need :to special case it as applicable. : :-- :Poul-Henning Kamp FreeBSD coreteam member :phk@FreeBSD.ORG "Real hackers run -current on their laptop." Huh? Look Poul, I don't know what your problem is but I'm through playing around with you. You aren't making any sense and, frankly my dear sir, the buffer cache, vm_pager interface, VN device, and vm_pager_strategy subsystem is my ball of wax, not yours... I don't need your permission and I certainly don't need your help if this is all you can come up with. I'm not going to twist up all that wonderful clean code just to avoid making the swapper a real device. After all, making it a real device is only a few simple lines of code - simple and straightforward. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 18:11:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 99B8114DFB for ; Mon, 27 Dec 1999 18:11:45 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id DAA13071; Tue, 28 Dec 1999 03:11:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-reply-to: Your message of "Mon, 27 Dec 1999 17:53:57 PST." <199912280153.RAA35369@apollo.backplane.com> Date: Tue, 28 Dec 1999 03:11:38 +0100 Message-ID: <13069.946347098@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912280153.RAA35369@apollo.backplane.com>, Matthew Dillon writes: > Huh? Look Poul, I don't know what your problem is but I'm through > playing around with you. You aren't making any sense and, frankly my > dear sir, the buffer cache, vm_pager interface, VN device, and > vm_pager_strategy subsystem is my ball of wax, not yours... Sorry, not so (and you've been told plenty many times already). You should fix the swap-pager to remove this last smoldering assumption about the existence of /dev/drum, rather than obfuscate the rest of the system by adding it back. I know it means more work for you, but we're not here to cut corners, we're here to get a better system. We don't get a better system if you keep pushing the dirty bits into obscure corners of the kernel rather than fix them where they need fixed. > I don't need > your permission and I certainly don't need your help if this is all you > can come up with. I objected to your patch on the grounds that it would be a step backwards, that has nothing to do with getting my permission. > can come up with. I'm not going to twist up all that wonderful clean code > just to avoid making the swapper a real device. You can call that "wonderful clean code" all you like, it is most certainly not the term I would use for it, and either way the matter of the fact is that struct buf is being abused to do something which it isn't able to do in its current design, and the way to fix that is not to add a hacked up dev_t but to give it special handling where it needs that. And adding a bogus dev_t and a equally bogus devsw does by no means make the swapper "a real device". I still object to your patch. It is a step backwards and it would further obfuscate the swap_pagers code. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 18:27:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3140B15483 for ; Mon, 27 Dec 1999 18:27:07 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA35755; Mon, 27 Dec 1999 18:27:02 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Dec 1999 18:27:02 -0800 (PST) From: Matthew Dillon Message-Id: <199912280227.SAA35755@apollo.backplane.com> To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) References: <13069.946347098@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In message <199912280153.RAA35369@apollo.backplane.com>, Matthew Dillon writes: : :> Huh? Look Poul, I don't know what your problem is but I'm through :> playing around with you. You aren't making any sense and, frankly my :> dear sir, the buffer cache, vm_pager interface, VN device, and :> vm_pager_strategy subsystem is my ball of wax, not yours... : :Sorry, not so (and you've been told plenty many times already). : :You should fix the swap-pager to remove this last smoldering :assumption about the existence of /dev/drum, rather than obfuscate :the rest of the system by adding it back. : :I know it means more work for you, but we're not here to cut corners, :we're here to get a better system. We don't get a better system if :you keep pushing the dirty bits into obscure corners of the kernel :rather than fix them where they need fixed. Sorry Poul, but you have no authority in this matter. All the statements you have made in the last hour simply point out, in very clear terms, that you don't know what you are talking about. Instead of simply admiting a mistake or even spending some time to review the code more closely, your solution is instead to continue to make outrageous statements. Frankly, Poul, I strongly, *STRONGLY* recommend that you simply not reply to any of my postings. Not a single one, because I am wholely sick and tired of your superiority complex. This thread was not meant for you, and your presence in it is not welcome. And don't even think about doing an end-run around me and committing your frankly inappropriate 'solution' - I'm going through proper channels to get this in. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 18:43:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E75E31532F for ; Mon, 27 Dec 1999 18:43:34 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id DAA14408; Tue, 28 Dec 1999 03:43:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-reply-to: Your message of "Mon, 27 Dec 1999 18:27:02 PST." <199912280227.SAA35755@apollo.backplane.com> Date: Tue, 28 Dec 1999 03:43:25 +0100 Message-ID: <14406.946349005@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912280227.SAA35755@apollo.backplane.com>, Matthew Dillon writes: > Sorry Poul, but you have no authority in this matter. All the statements > you have made in the last hour simply point out, in very clear terms, > that you don't know what you are talking about. Instead of simply > admiting a mistake or even spending some time to review the code > more closely, your solution is instead to continue to make outrageous > statements. The fact that I think the hacks should be kept firmly inside the VM system, rather than spill out into the rest of the kernel is not something I count amongst my mistakes. I have actually spent quite some time looking at the code, both before and again tonight just because of your email. That is probably the best example of a review process which works. > Frankly, Poul, I strongly, *STRONGLY* recommend that you simply not > reply to any of my postings. This has been my general policy for a long time, but it gets overridden whenever you come up with something which is obviously wrong. (And I find the fact that so many people have adopted this policy disturbing, and sufficient grounds for me to relax my instance of it.) > Not a single one, because I am wholely > sick and tired of your superiority complex. This thread was not meant > for you, and your presence in it is not welcome. And don't even think > about doing an end-run around me and committing your frankly inappropriate > 'solution' - I'm going through proper channels to get this in. I have all rights I need to answer you when you send an email in public asking for a review. It is my obligation to answer you when I am one of the few people who are not intimidated by neither you nor the code in question and I can see that what you are proposing is plain wrong. So far you have one very experienced kernel programmer objecting to your patch, so yes: you will bloddy have to go through proper channels to resolve this issue. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 19: 3: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 1CBC214DD8 for ; Mon, 27 Dec 1999 19:03:03 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id SAA12518; Mon, 27 Dec 1999 18:58:41 -0800 (PST) Message-Id: <199912280258.SAA12518@implode.root.com> To: Poul-Henning Kamp Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-reply-to: Your message of "Tue, 28 Dec 1999 03:11:38 +0100." <13069.946347098@critter.freebsd.dk> From: David Greenman Reply-To: dg@root.com Date: Mon, 27 Dec 1999 18:58:41 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've heard from both of you that you think the other is wrong. This isn't very helpful, however, in finding the correct solution. What I'd like to hear from both of you is the reasons why swap is better as a device, or not. There seems to be some unstated architectural philosophy that needs to be stated before any informed decision can be made about what is the right direction to go in. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 19:14:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 83D1D14D3E for ; Mon, 27 Dec 1999 19:14:47 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id MAA14709; Tue, 28 Dec 1999 12:14:41 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id MAA16736; Tue, 28 Dec 1999 12:14:40 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id MAA12942; Tue, 28 Dec 1999 12:14:39 +0900 (JST) To: davidc@lodge.guild.ab.ca Cc: current@FreeBSD.ORG Subject: Re: INET6 userland tools In-Reply-To: <19991216125426X.shin@nd.net.fujitsu.co.jp> References: <19991216125426X.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991228121510C.shin@nd.net.fujitsu.co.jp> Date: Tue, 28 Dec 1999 12:15:10 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 35 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Very INET6 specific patches are already prepared and under the > review. getaddrinfo() and getaddrname() is not yet, but I'll > also prepare them. > > And after those libraries are prepared, porting KAME tools > onto current won't be difficult. Getaddrinfo(), getaddrname(), etc support is commited, and also several udp and raw socket apps are also committed. -gethostbyaddr(), gethostbyname(), etc support in libc/net (but DNS query over IPv6 transport is not yet) -several udp and raw socket apps ping6 rtsol(host address autoconfiguration tool. Actually the source code is shared with 'rtsold'. Though it needs 'rtadvd' daemon on a router, 'rtadvd' for current is not yet.) rtsold(host address autoconfiguration daemon for Note PC, which frequently change its subnet) gifconfig(v6/v4, v6/v4, v4/v4, v6/v6 tunneling configuration) ifmcstat(print out v6 multicast addr configuration info) prefix(assigne address prefix, e.g. subnet addr, just like ifconfig for full addr. it also support host internal prefix renumbering) route6d rip6query Anyone interested in them please try and enjoy. (Note that you need to build kernel with INET6 option.) If there is any problems, please let me know. Thanks, Yoshinobu Inoue KAME project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 19:14:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 8490C15304 for ; Mon, 27 Dec 1999 19:14:51 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 9393C1CA0; Tue, 28 Dec 1999 11:14:45 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-Reply-To: Message from Matthew Dillon of "Mon, 27 Dec 1999 17:21:35 PST." <199912280121.RAA35049@apollo.backplane.com> Date: Tue, 28 Dec 1999 11:14:45 +0800 From: Peter Wemm Message-Id: <19991228031445.9393C1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: [..] > And, in anycase, I am not going to spend hours putting together a long > involved patch when a simple short patch suffices. If you want to > spend the time to come up with your own patch (that doesn't screw the > pooch in regards to cluster performance!), then I'm all ears, otherwise > this patch is what is going to go in for the 4.0 release. Please hold fire for a bit longer. I have (what I think is) a much cleaner fix in mind. There is no urgency here, a couple of hours isn't going to make the slightest difference to the big picture. On a side note, as the original author of the changes that lead to this, I would have thought it would have been appropriate to ask ME directly first before going public. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 19:24:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 667D115304 for ; Mon, 27 Dec 1999 19:24:39 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 70DE41CA0; Tue, 28 Dec 1999 11:24:33 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: dg@root.com Cc: Poul-Henning Kamp , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-Reply-To: Message from David Greenman of "Mon, 27 Dec 1999 18:58:41 PST." <199912280258.SAA12518@implode.root.com> Date: Tue, 28 Dec 1999 11:24:33 +0800 From: Peter Wemm Message-Id: <19991228032433.70DE41CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Greenman wrote: > I've heard from both of you that you think the other is wrong. This isn't > very helpful, however, in finding the correct solution. What I'd like to hear > from both of you is the reasons why swap is better as a device, or not. There > seems to be some unstated architectural philosophy that needs to be stated > before any informed decision can be made about what is the right direction to > go in. The problem is that swapdev_vp needs to handle VOP_STRATEGY(), and swapdev_vp is incorrectly being pointed at spec_vnops. Here is a proposed (UNTESTED!) clean fix: Index: swap_pager.c =================================================================== RCS file: /home/ncvs/src/sys/vm/swap_pager.c,v retrieving revision 1.129 diff -u -r1.129 swap_pager.c --- swap_pager.c 1999/11/22 15:27:09 1.129 +++ swap_pager.c 1999/12/28 03:22:08 @@ -199,6 +199,32 @@ static daddr_t swp_pager_meta_ctl __P((vm_object_t, vm_pindex_t, int)); /* + * Handle a VOP_STRATEGY() on swapdev_vp + */ + +static int +swapdev_strategy(ap) + struct vop_strategy_args /* { + struct vnode *a_vp; + struct buf *a_bp; + } */ *ap; +{ + struct buf *bp; + + bp = ap->a_bp; + return swstrategy(bp); +} + +vop_t **swapdev_vnodeop_p; +static struct vnodeopv_entry_desc swapdev_vnodeop_entries[] = { + { &vop_strategy_desc, (vop_t *) swapdev_strategy }, + { NULL, NULL } +}; +static struct vnodeopv_desc swapdev_vnodeop_opv_desc = + { &swapdev_vnodeop_p, swapdev_vnodeop_entries }; +VNODEOP_SET(swapdev_vnodeop_opv_desc); + +/* * SWP_SIZECHECK() - update swap_pager_full indication * * update the swap_pager_almost_full indication and warn when we are @@ -329,7 +355,7 @@ swhash_mask = n - 1; - n = getnewvnode(VT_NON, NULL, spec_vnodeop_p, &swapdev_vp); + n = getnewvnode(VT_NON, NULL, swapdev_vnodeop_p, &swapdev_vp); if (n) panic("Cannot get vnode for swapdev"); swapdev_vp->v_type = VBLK; After this, flushchainbuf() on a bp that is bound to swapdev_vp should do the right thing. There is still no need at all to redirect this via a fake device. I'll be testing this shortly, but I wanted to get an alternative in before the arms race truely turned nuclear. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 19:28: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D719914DD6 for ; Mon, 27 Dec 1999 19:27:58 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA38006; Mon, 27 Dec 1999 20:27:57 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA58707; Mon, 27 Dec 1999 20:27:57 -0700 (MST) Message-Id: <199912280327.UAA58707@harmony.village.org> To: Peter Wemm Subject: Re: General ata grousing Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 23 Dec 1999 22:31:29 +0800." <19991223143129.14CD71CCE@overcee.netplex.com.au> References: <19991223143129.14CD71CCE@overcee.netplex.com.au> Date: Mon, 27 Dec 1999 20:27:57 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991223143129.14CD71CCE@overcee.netplex.com.au> Peter Wemm writes: : Just as a BTW, dfr and sos are exchanging patches right now (and have been : for quite a few days) that happen to fix the inthand_add() stuff. This may also help the pccard code cases which I have floating around. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 19:47:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E9EFE14F65 for ; Mon, 27 Dec 1999 19:47:24 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA36239; Mon, 27 Dec 1999 19:47:20 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Dec 1999 19:47:20 -0800 (PST) From: Matthew Dillon Message-Id: <199912280347.TAA36239@apollo.backplane.com> To: David Greenman Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) References: <199912280258.SAA12518@implode.root.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : I've heard from both of you that you think the other is wrong. This isn't :very helpful, however, in finding the correct solution. What I'd like to hear :from both of you is the reasons why swap is better as a device, or not. There :seems to be some unstated architectural philosophy that needs to be stated :before any informed decision can be made about what is the right direction to :go in. : :-DG : :David Greenman :Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Ok, I'll buy that. Though I will note that VN has been broken for over a month - I found that out about half a month ago and posted the fact, and if Poul is so interested in fixing it he could easily have done so then. I'm the one who has spent all the time tracking it down, patching, and testing it, and frankly that should count for a hellofalot more then nil. Poul frankly does not have a leg to stand on to demand that I work on a 'better' solution when I didn't cause the problem in the first place, nor does he have any right to pollute the VM code to end-run around the issue. It would be tragic if Poul's behavior were allowed to conclude the matter. That said, here is my position, split into a 'history' and my 'reasoning': Previously we had /dev/drum, which didn't work, and the SWAP device was layered around a device and swap I/O was vectored through the device subsystem. One month ago, after discussions, Peter Wemm removed the userland frontend for the swap device, /dev/drum, and at the same time thought it would be a good idea to collapse the VOP_STRATEGY routines (that ran through the SWAP dev_t) into direct calls to swstrategy(). At the time I was ambivalent but since the change seemed to clear out a bunch of cruft I went with it. However, this broke the VN device. I found this out about half a month later (around half a month ago) but at the time was hip deep in NFS work for the 3.4 release and could not address the issue. Now that the NFS work is finished I revisited the now broken VN device to determine what went wrong. It turns out that the VN device indirectly runs through the swap device using several generic filesystem buffer related subsystems. When the swap dev_t was removed, the result was a panic. - The VN device uses vm_pager_strategy() to implement swap backing store. vm_pager_strategy() is a generic mechanism that I introduced into the VM system a number of months ago for two reasons: (1) As a sounding board for giving the vm_pager_*() functions a strategy entry point, to see how well it would work. (2) To implement the swap backing store feature for the VN device. vm_pager_strategy() in turn looks at the pager ID and does a table lookup call through to the swap_pager_strategy() function. This function takes a VM object and a *generic* bp. While the function itself is swap-specific, the design of the code is supposed to be as generic as possible. vm_pager_strategy() may need to cut up the bp into subrequests to deal with clustering issues. It uses the generic 'chainbuf' routines to manage the asynchronous I/O. The 'chainbuf' routines are designed to be as generic as possible.. they take BP's. They do *NOT* and are not intended to be special cased in any way. This is my design for these routines, and even though they are currently used only by the swap_pager_strategy() code I believe the generic nature of the routines must be maintained. I/O sequencing for the swap-backed VN device is thus: VN->vm_pager_strategy->chainbuf->STRATEGY. I advocate that the best solution is to simply undo part of the original commit and restore SWAP's dev_t which was removed a month ago. Poul's solution is considerably more complicated (the patch he offered will not work in all cases, and I've already corrected all his other misstatements that I do not really feel it appropriate to continue to correct his misstatements when all he does with those corrections is use them as a poolboard to make his next set of incorrect statements!). I will tell you why Poul's patch will not work, but I am NOT going to tell Poul because, damn it, he has no right to spend 5 minutes working up a shoddy patch and then try to dictate to me that it should be used over my well tested 8-hours-of-work patch! Poul's patch will not work because flushchainbuf() is not the only chain routine that flushes the buffers. getchainbuf() and waitchainbuf() may *also* flush the buffers if there are already too many chain buffers built up in the linked list. Poul only addressed flushchainbuf(). He obviously didn't bother to read the code carefully and he just as obviously doesn't understand it. And not understanding it I can't imagine how he can possibly believes he understasnds the concepts behind it. Poul's patch also pollutes the chainbuf code which is supposed to be *GENERIC*. - Poul has demonstrated over and over again (if you read the thread) that he understands not a single issue regarding this whole chain of events. He advocates polluting my carefully designed and implemented VM code, both the vm_pager_strategy() design and the chainbuf design, in order to avoid creating a dev_t for the swap device. I strongly believe that the VN/PAGER/CHAINBUFIO code sequence must be maintained without such pollution. Since swap really is a device - it has a fully functional strategy entry point and has logical separation from the VM swap subsystem by taking on the responsibility for managing the block devices mounted as swap - I see no reason why we can't implement a simple dev_t for it. Giving it a dev_t allows us to use all the standard filesystem buffer cache I/O routines with it, and we've already demonstrated that it is useful to do so in the VN swap-backing device. There could easily be other situations that come up in the future that may also take advantage of this. I will also point out that only a month ago the SWAP device *WAS* a dev_t. It was removed. That removal was a mistake because nobody (including me) realized that we just blew up VN. It's as simple as that. Do we back out a small portion of the patch to make VN work again, or do we spend hours or days rewriting an unrelated subsystem to work around the loss of the dev_t? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 19:49: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 6A352153A6 for ; Mon, 27 Dec 1999 19:48:38 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id EAA17617; Tue, 28 Dec 1999 04:48:15 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: dg@root.com Cc: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-reply-to: Your message of "Mon, 27 Dec 1999 18:58:41 PST." <199912280258.SAA12518@implode.root.com> Date: Tue, 28 Dec 1999 04:48:15 +0100 Message-ID: <17615.946352895@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912280258.SAA12518@implode.root.com>, David Greenman writes: >There >seems to be some unstated architectural philosophy that needs to be stated >before any informed decision can be made about what is the right direction to >go in. The underlying problem is of course that struct buf is a conglomerate of "struct block_cache" and "struct io_request", and in the cases where you need only the latter functionality you still have to respect all the conventions of the former. This issue leads to complexity and hacks in all code that needs to splite a io operation: vinum, ccd, swap_pager and disk_slice/label. For this reason the swap-pager has a bogus vnode: (swapdev_vp) to hang buffers from. This vnode even more bogusly uses spec_vnodeop_p for its vop[], and at the far end of that vop[] it used to abuse /dev/drum to get things done. If we want to maintain the presently unused generality of the chainbuf routines (they are currently only used in the swap-pager), then the fix is to add a real vop[] to the bogus swapdev_vp so that VOP_STRATEGY correctly end up in swstrategy() for swap device buffers. If we accept that the chainbuf routines are of limited utility, we can simply s/VOP_STRATEGY/swstrategy/ in the flushchain procedure. The reason why /dev/drum should not be brought back is that it isn't a device and it shouldn't be made one. In particular it should not made one to paste over a bogus vnode, that would be a step backwards. If we want to *really* fix the problem, we should introduce a bop[] function vector on struct buf. Kirk already (almost) did this: struct bio_ops. This bop[] would be where code would find the strategy, bwrite* and other operations on the buffer without knowing if the buffer has a dev_t, a dev_t + a vnode, only a vnode or neither associated with it. This fix is out of scope for the present problem, and certainly not a 4.0 item. This fix will be needed before we can put a non-device backed storage layer under UFS. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 19:50:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3FA1315113 for ; Mon, 27 Dec 1999 19:50:57 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA64597; Mon, 27 Dec 1999 19:50:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Matthew Dillon Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-reply-to: Your message of "Mon, 27 Dec 1999 18:27:02 PST." <199912280227.SAA35755@apollo.backplane.com> Date: Mon, 27 Dec 1999 19:50:40 -0800 Message-ID: <64593.946353040@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Frankly, Poul, I strongly, *STRONGLY* recommend that you simply not > reply to any of my postings. Not a single one, because I am wholely > sick and tired of your superiority complex. This thread was not meant This is unwontedly personal and has no place in a public mailing list. Please keep your replies confined to technical content (or your concerns about the lack thereof) and keep always in mind that getting emotional serves only to generate heat when what's needed is light. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 19:55:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7ECF414C39 for ; Mon, 27 Dec 1999 19:55:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA36310; Mon, 27 Dec 1999 19:55:49 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Dec 1999 19:55:49 -0800 (PST) From: Matthew Dillon Message-Id: <199912280355.TAA36310@apollo.backplane.com> To: Poul-Henning Kamp Cc: dg@root.com, freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) References: <17615.946352895@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It makes no sense whatsoever to spend hours or days reworking a major subsystem *just* so the swap device can do without a dev_t. I don't really give a damn about /dev/drum -- I said before and I will say again that we can leave it out. But we need to give the swap device its's dev_t back to fix VN because no matter what you believe the *right* thing is to do, (A) nobody has time to rework a major subsystem at this time, and (B) VN was broken when the dev_t was removed, the dev_t should be added back in until someone comes up with a better overall solution. I also strongly believe that polluting *OTHER* subsystems (the buffer chaining code) just to avoid creating a dev_t for SWAP makes even less sense. I do not have the inclination to spend huge amounts of my time reworking the VOP or filesystem buffer subsystem because someone isn't willing to spend a tiny amount of code to partially back out a patch that broke something (VN) in the system, that someone also not themselves willing to spend the time required to rework the system properly. It's that simple. It makes no sense to impose such a requirement on someone else to fix a problem that they did not create. Now I would like to make a clarification: The commit we are talking about was actually one Peter did with the approval of everyone, including me. At the end of November. However, nobody including me realized that the second part of his commit, which was an optimization to remove the 'cruft' of the SWAP device, broke VN. If we had known then that this optimization would break VN it would *NOT* have gone in until the VN problem was fixed. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 19:57:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4092F14A1A for ; Mon, 27 Dec 1999 19:57:54 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 237CC1CA0; Tue, 28 Dec 1999 11:57:43 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: dg@root.com, Poul-Henning Kamp , Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-Reply-To: Message from Peter Wemm of "Tue, 28 Dec 1999 11:24:33 +0800." <19991228032433.70DE41CA0@overcee.netplex.com.au> Date: Tue, 28 Dec 1999 11:57:43 +0800 From: Peter Wemm Message-Id: <19991228035743.237CC1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > David Greenman wrote: > > I've heard from both of you that you think the other is wrong. This isn' t > > very helpful, however, in finding the correct solution. What I'd like to he ar > > from both of you is the reasons why swap is better as a device, or not. The re > > seems to be some unstated architectural philosophy that needs to be stated > > before any informed decision can be made about what is the right direction to > > go in. > > The problem is that swapdev_vp needs to handle VOP_STRATEGY(), and swapdev_vp > is incorrectly being pointed at spec_vnops. Here is a proposed (UNTESTED!) > clean fix: This is missing a vop_default entry, so it will panic. But as a proof of concept it still stands. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 20: 3: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 91C9214A1A for ; Mon, 27 Dec 1999 20:03:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA36381; Mon, 27 Dec 1999 20:01:56 -0800 (PST) (envelope-from dillon) Date: Mon, 27 Dec 1999 20:01:56 -0800 (PST) From: Matthew Dillon Message-Id: <199912280401.UAA36381@apollo.backplane.com> To: Peter Wemm Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) References: <19991228031445.9393C1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Matthew Dillon wrote: :[..] :> And, in anycase, I am not going to spend hours putting together a long :> involved patch when a simple short patch suffices. If you want to :> spend the time to come up with your own patch (that doesn't screw the :> pooch in regards to cluster performance!), then I'm all ears, otherwise :> this patch is what is going to go in for the 4.0 release. : :Please hold fire for a bit longer. I have (what I think is) a much cleaner :fix in mind. There is no urgency here, a couple of hours isn't going to :make the slightest difference to the big picture. : :On a side note, as the original author of the changes that lead to this, I :would have thought it would have been appropriate to ask ME directly first :before going public. : :Cheers, :-Peter Your fix looks pretty good, Peter. I'll run it in and test it. I only wish you had come up with it before Poul started going off the deep end. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 20:29:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id D4A2E152EE for ; Mon, 27 Dec 1999 20:29:42 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id UAA28932; Mon, 27 Dec 1999 20:29:05 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 27 Dec 1999 20:29:05 -0800 Date: Mon, 27 Dec 1999 20:29:05 -0800 (PST) From: Kip Macy To: "Jordan K. Hubbard" Cc: Matthew Dillon , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-Reply-To: <64593.946353040@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: jkh@zippy.cdrom.com,dillon@apollo.backplane.com,phk@critter.freebsd.dk,freebsd-current@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is unwontedly personal and has no place in a public mailing list. > Please keep your replies confined to technical content (or your > concerns about the lack thereof) and keep always in mind that getting > emotional serves only to generate heat when what's needed is light. > > - Jordan And it undermines even the strongest of technical arguments. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 20:55:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 79D30152EE; Mon, 27 Dec 1999 20:55:22 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA16558; Mon, 27 Dec 1999 23:55:17 -0500 (EST) Received: from rac2.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id XAA19712; Mon, 27 Dec 1999 23:55:19 -0500 (EST) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id XAA19708; Mon, 27 Dec 1999 23:55:19 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Mon, 27 Dec 1999 23:55:19 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-multimedia@freebsd.org Cc: freebsd-current@freebsd.org Subject: DVD driver 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 noticed recently (10 minutes ago) that FreeBSD will mount a DVD and I can even look around on it as if it were a regular CD (on -CURRENT). I was wondering if there was any mpeg2 decoder that would play DVD movies. I don't have a hardware decoder the software one looks fine but I'd like to know if anyone has tried to make a software decoder for FreeBSD. Thanks.. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 20:59:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (Postfix) with ESMTP id E066714EA7 for ; Mon, 27 Dec 1999 20:59:43 -0800 (PST) (envelope-from veldy@visi.com) Received: from barley (h-181-6.mn.mediaone.net [209.32.181.6]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id XAA08347 for ; Mon, 27 Dec 1999 23:59:37 -0500 (EST) Message-ID: <002d01bf50f0$a8491c40$0100a8c0@veldy.org> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: Problem with PAM-AUTH for XFree86? Date: Mon, 27 Dec 1999 23:01:50 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002A_01BF50BE.5BFBCC20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_002A_01BF50BE.5BFBCC20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I just got my box up and running Current 12-27. ATA works great for = both drives now. However, I compiled XFree86 from the port and I chose = the options for RPC, Wraphelp.c, PAM and threads. When I start x (using = startkde), I get many many password prompts. I can only assume that the = PAM module used for athentication by XFree86 is broken. Is the owner = aware of this? I recompiled without PAM support and everything works as expected. Tom Veldhouse veldy@visi.com ------=_NextPart_000_002A_01BF50BE.5BFBCC20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
    I just got my box up = and running=20 Current 12-27.  ATA works great for both drives now.  However, = I=20 compiled XFree86 from the port and I chose the options for RPC, = Wraphelp.c, PAM=20 and threads.  When I start x (using startkde), I get many many = password=20 prompts.  I can only assume that the PAM module used for = athentication by=20 XFree86 is broken.  Is the owner aware of this?
 
    I recompiled without = PAM support=20 and everything works as expected.
 
Tom Veldhouse
veldy@visi.com
------=_NextPart_000_002A_01BF50BE.5BFBCC20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 21: 0: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (Postfix) with ESMTP id C9BCD14CC1 for ; Mon, 27 Dec 1999 20:59:52 -0800 (PST) (envelope-from veldy@visi.com) Received: from barley (h-181-6.mn.mediaone.net [209.32.181.6]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id XAA08381 for ; Mon, 27 Dec 1999 23:59:48 -0500 (EST) Message-ID: <003401bf50f0$aebc1c80$0100a8c0@veldy.org> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: Problem with PAM-AUTH for XFree86? Date: Mon, 27 Dec 1999 23:02:02 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I just got my box up and running Current 12-27. ATA works great for both drives now. However, I compiled XFree86 from the port and I chose the options for RPC, Wraphelp.c, PAM and threads. When I start x (using startkde), I get many many password prompts. I can only assume that the PAM module used for athentication by XFree86 is broken. Is the owner aware of this? I recompiled without PAM support and everything works as expected. Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 21:23:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from green.excel.net (excel.net [156.46.156.2]) by hub.freebsd.org (Postfix) with ESMTP id 3FAEA14C2F for ; Mon, 27 Dec 1999 21:23:40 -0800 (PST) (envelope-from kevin@tarvalon.net) Received: from fdl0004.excel.net (kevin@fdl0004.excel.net [156.46.102.132]) by green.excel.net (8.9.3/8.9.3) with ESMTP id XAA11994 for ; Mon, 27 Dec 1999 23:23:26 -0600 (CST) Date: Mon, 27 Dec 1999 23:23:21 -0600 (CST) From: Kevin Entringer To: current@freebsd.org Subject: Make world documentation 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 Recently someone posted a url that provided a quick run through on some important extra steps to take while doing a make world from -STABLE to -CURRENT, unfortunatly I lost the URL. I was wondering if someone could post it again? I did check the archives, but I wasn't able to find it. Thanks. Regards, Kevin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 21:32:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 53F8314C37 for ; Mon, 27 Dec 1999 21:32:23 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id VAA07025; Mon, 27 Dec 1999 21:31:50 -0800 (PST) Date: Mon, 27 Dec 1999 21:31:50 -0800 From: Brooks Davis To: Kevin Entringer Cc: current@FreeBSD.ORG Subject: Re: Make world documentation Message-ID: <19991227213150.A6741@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from kevin@tarvalon.net on Mon, Dec 27, 1999 at 11:23:21PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 11:23:21PM -0600, Kevin Entringer wrote: > Recently someone posted a url that provided a quick run through on some > important extra steps to take while doing a make world from -STABLE to > -CURRENT, unfortunatly I lost the URL. I was wondering if someone could > post it again? I did check the archives, but I wasn't able to find it. http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html Though I though it was supposed to have been moved to the main site, but that's what http://www.freebsd.org/tutorials/ says. -- Brooks P.S. This belonged on -questions. -- "Those who desire to give up freedom in order to gain security, will not have, nor do they deserve, either one" --Thomas Jefferson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 21:33:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (p135.as1.naas1.eircom.net [159.134.254.135]) by hub.freebsd.org (Postfix) with ESMTP id 8D57B154E1 for ; Mon, 27 Dec 1999 21:33:08 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id FAA17220; Tue, 28 Dec 1999 05:33:11 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991227170258.A25978@iris.vsrc.uab.edu> Date: Tue, 28 Dec 1999 05:32:50 -0000 (GMT) From: "Steve O'Hara-Smith" To: Emre Subject: Re: IPFW Cc: freebsd-current@freebsd.org, Wilko Bulte Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Dec-99 Emre wrote: > Actually I haven't tried -release or -stable...I'm willing > to take the chance. I think you will find that you are taking much more of a chance with -current than with -stable. After all -current is allowed to break sometimes, -stable only does it by accident. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 21:36: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from host.cer.ntnu.edu.tw (cer.ntnu.edu.tw [140.122.119.9]) by hub.freebsd.org (Postfix) with ESMTP id 7F61D152F8 for ; Mon, 27 Dec 1999 21:35:58 -0800 (PST) (envelope-from clive@host.cer.ntnu.edu.tw) Received: (from clive@localhost) by host.cer.ntnu.edu.tw (8.9.3/8.9.3) id NAA50991; Tue, 28 Dec 1999 13:38:57 +0800 (CST) (envelope-from clive) Date: Tue, 28 Dec 1999 13:38:57 +0800 From: Clive Lin To: "Thomas T. Veldhouse" Cc: FreeBSD-Current Subject: Re: Problem with PAM-AUTH for XFree86? Message-ID: <19991228133857.A50959@host.cer.ntnu.edu.tw> Reply-To: Clive Lin References: <002d01bf50f0$a8491c40$0100a8c0@veldy.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <002d01bf50f0$a8491c40$0100a8c0@veldy.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 11:01:50PM -0600, Thomas T. Veldhouse wrote: > Hello, > > I just got my box up and running Current 12-27. ATA works great for both drives now. However, I compiled XFree86 from the port and I chose the options for RPC, Wraphelp.c, PAM and threads. When I start x (using startkde), I get many many password prompts. I can only assume that the PAM module used for athentication by XFree86 is broken. Is the owner aware of this? > > I recompiled without PAM support and everything works as expected. > Hi! I dunno if this is tooo tricky, but I added a single line to solved the same question as yours. the xserver line... X clive@cartier ~> tail -5 /etc/pam.conf # tricky tricky forgive me xserver auth sufficient pam_permit.so no_use # If we don't match anything else, default to using getpwnam(). other auth required pam_unix.so try_first_pass other account required pam_unix.so try_first_pass X clive@cartier ~> -- CirX Clive Lin FreeBSD - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 22:35: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id D6E6E14F18 for ; Mon, 27 Dec 1999 22:34:58 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBS6Yk341020; Tue, 28 Dec 1999 08:34:46 +0200 (SAST) Message-Id: <199912280634.dBS6Yk341020@gratis.grondar.za> To: "Thomas T. Veldhouse" Cc: "FreeBSD-Current" Subject: Re: Problem with PAM-AUTH for XFree86? References: <002d01bf50f0$a8491c40$0100a8c0@veldy.org> In-Reply-To: <002d01bf50f0$a8491c40$0100a8c0@veldy.org> ; from "Thomas T. Veldhouse" "Mon, 27 Dec 1999 23:01:50 CST." Date: Tue, 28 Dec 1999 08:34:45 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just got my box up and running Current 12-27. ATA works great for = > both drives now. However, I compiled XFree86 from the port and I chose = > the options for RPC, Wraphelp.c, PAM and threads. When I start x (using = > startkde), I get many many password prompts. I can only assume that the = > PAM module used for athentication by XFree86 is broken. Is the owner = > aware of this? > > I recompiled without PAM support and everything works as expected. Is your /etc/* up to date? Specifically /etc/pam.conf? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 27 23:58:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from poboxer.pobox.com (ferg5200-1-37.cpinternet.com [208.149.16.37]) by hub.freebsd.org (Postfix) with ESMTP id ACD5314E39; Mon, 27 Dec 1999 23:58:39 -0800 (PST) (envelope-from alk@poboxer.pobox.com) Received: (from alk@localhost) by poboxer.pobox.com (8.9.3/8.9.1) id BAA93378; Tue, 28 Dec 1999 01:57:19 -0600 (CST) (envelope-from alk) From: Anthony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 28 Dec 1999 01:57:13 -0600 (CST) X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO 5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed Reply-To: alk@pobox.com To: culverk@wam.umd.edu Cc: freebsd-multimedia@FreeBSD.ORG Subject: DVD driver References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14440.19576.535609.277984@avalon.east> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoth Kenneth Wayne Culver on Mon, 27 December: : I don't have a hardware decoder the software one looks fine but I'd like to : know if anyone has tried to make a software decoder for FreeBSD. Thanks.. (I'll redirect to multimedia.) I've been trying to build the nist mpeg2player on current lately. It was reported to be working in late October, but I'm not having any luck at the moment because of failures in static initializers in the Regex package -- probably something to do with pthreads, and very much non-trivial to debug, given my vanishingly small understanding of the ever-changing thread model on CURRENT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 1:23: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (Postfix) with ESMTP id 60362153EB for ; Tue, 28 Dec 1999 01:23:00 -0800 (PST) (envelope-from veldy@visi.com) Received: from visi.com (h-180-107.mn.mediaone.net [209.32.180.107]) by chmls11.mediaone.net (8.8.7/8.8.7) with ESMTP id EAA05588; Tue, 28 Dec 1999 04:22:42 -0500 (EST) Message-ID: <386881E9.F97C9B82@visi.com> Date: Tue, 28 Dec 1999 03:24:57 -0600 From: "Thomas T. Veldhouse" X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19991227-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Murray Cc: FreeBSD-Current Subject: Re: Problem with PAM-AUTH for XFree86? References: <002d01bf50f0$a8491c40$0100a8c0@veldy.org> <199912280634.dBS6Yk341020@gratis.grondar.za> 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 using yesterday's snapshot (12-27). /etc/pam.conf is dated 12/21. Tom Veldhouse veldy@visi.com Mark Murray wrote: > > > I just got my box up and running Current 12-27. ATA works great for = > > both drives now. However, I compiled XFree86 from the port and I chose = > > the options for RPC, Wraphelp.c, PAM and threads. When I start x (using = > > startkde), I get many many password prompts. I can only assume that the = > > PAM module used for athentication by XFree86 is broken. Is the owner = > > aware of this? > > > > I recompiled without PAM support and everything works as expected. > > Is your /etc/* up to date? Specifically /etc/pam.conf? > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 1:24:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (Postfix) with ESMTP id F28C515466 for ; Tue, 28 Dec 1999 01:24:56 -0800 (PST) (envelope-from veldy@visi.com) Received: from visi.com (h-180-107.mn.mediaone.net [209.32.180.107]) by chmls11.mediaone.net (8.8.7/8.8.7) with ESMTP id EAA05748; Tue, 28 Dec 1999 04:24:33 -0500 (EST) Message-ID: <38688258.83CA791C@visi.com> Date: Tue, 28 Dec 1999 03:26:48 -0600 From: "Thomas T. Veldhouse" X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19991227-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Clive Lin Cc: FreeBSD-Current Subject: Re: Problem with PAM-AUTH for XFree86? References: <002d01bf50f0$a8491c40$0100a8c0@veldy.org> <19991228133857.A50959@host.cer.ntnu.edu.tw> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nope! Not too tricky. Should this be added to the file permanantly, or perhaps as part of the port? Tom Veldhouse veldy@visi.com Clive Lin wrote: > > On Mon, Dec 27, 1999 at 11:01:50PM -0600, Thomas T. Veldhouse wrote: > > Hello, > > > > I just got my box up and running Current 12-27. ATA works great for both drives now. However, I compiled XFree86 from the port and I chose the options for RPC, Wraphelp.c, PAM and threads. When I start x (using startkde), I get many many password prompts. I can only assume that the PAM module used for athentication by XFree86 is broken. Is the owner aware of this? > > > > I recompiled without PAM support and everything works as expected. > > > Hi! > I dunno if this is tooo tricky, but I added a single line to solved the > same question as yours. the xserver line... > > X clive@cartier ~> tail -5 /etc/pam.conf > # tricky tricky forgive me > xserver auth sufficient pam_permit.so no_use > # If we don't match anything else, default to using getpwnam(). > other auth required pam_unix.so try_first_pass > other account required pam_unix.so try_first_pass > X clive@cartier ~> > > -- > CirX > Clive Lin > > FreeBSD - The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 1:54:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (Postfix) with ESMTP id CF6B615439 for ; Tue, 28 Dec 1999 01:54:18 -0800 (PST) (envelope-from veldy@visi.com) Received: from visi.com (h-180-107.mn.mediaone.net [209.32.180.107]) by chmls11.mediaone.net (8.8.7/8.8.7) with ESMTP id EAA07283 for ; Tue, 28 Dec 1999 04:54:15 -0500 (EST) Message-ID: <3868894D.4430B7CA@visi.com> Date: Tue, 28 Dec 1999 03:56:29 -0600 From: "Thomas T. Veldhouse" X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19991227-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: where did /etc/make.conf go? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have noticed that /etc/make.conf is missing from the current source tree and I can not find any mention of its removal anywhere. Where did it go? Tom Veldhouse veldy@visi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 2: 8:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from tohokugw.tohoku.iij.ad.jp (tohokugw.tohoku.iij.ad.jp [202.232.14.98]) by hub.freebsd.org (Postfix) with ESMTP id DF6F514CE8 for ; Tue, 28 Dec 1999 02:08:42 -0800 (PST) (envelope-from taguchi@tohoku.iij.ad.jp) Received: by tohokugw.tohoku.iij.ad.jp; id TAA13866; Tue, 28 Dec 1999 19:08:42 +0900 (JST) From: Received: from hirose.tohoku.iij.ad.jp(192.168.144.2) by tohokugw.tohoku.iij.ad.jp via smap (V4.2) id xma013864; Tue, 28 Dec 99 19:08:40 +0900 Received: from hirose.tohoku.iij.ad.jp (localhost [127.0.0.1]) by hirose.tohoku.iij.ad.jp (8.9.3/3.7W99113014) with ESMTP id TAA01447 for ; Tue, 28 Dec 1999 19:08:39 +0900 (JST) Date: Tue, 28 Dec 1999 19:08:38 +0900 Message-ID: To: freebsd-current@freebsd.org Subject: Re: where did /etc/make.conf go? In-Reply-To: In your message of "Tue, 28 Dec 1999 03:56:29 -0600" <3868894D.4430B7CA@visi.com> References: <3868894D.4430B7CA@visi.com> User-Agent: Wanderlust/2.2.12 (Joyride) EMIKO/1.13.9 (Euglena tripteris) FLIM/1.13.2 (Kasanui) Emacs/20.4 (i386--freebsd) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by EMIKO 1.13.9 - "Euglena tripteris") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > I have noticed that /etc/make.conf is missing from the current source > tree and I can not find any mention of its removal anywhere. Where did > it go? See /etc/defaults ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 2: 9: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 3F9F614F2F for ; Tue, 28 Dec 1999 02:09:05 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA73132; Tue, 28 Dec 1999 10:06:35 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 28 Dec 1999 10:06:35 +0000 (GMT) From: Doug Rabson To: Warner Losh Cc: Peter Wemm , current@freebsd.org Subject: Re: General ata grousing In-Reply-To: <199912280327.UAA58707@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Dec 1999, Warner Losh wrote: > In message <19991223143129.14CD71CCE@overcee.netplex.com.au> Peter Wemm writes: > : Just as a BTW, dfr and sos are exchanging patches right now (and have been > : for quite a few days) that happen to fix the inthand_add() stuff. > > This may also help the pccard code cases which I have floating around. I'm not doing anything special with this code btw., just calling bus_alloc_resource() carefully in the right place. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 4:12:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B517814E8F for ; Tue, 28 Dec 1999 04:12:53 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 99B541CCE; Tue, 28 Dec 1999 20:12:47 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-Reply-To: Message from Matthew Dillon of "Mon, 27 Dec 1999 20:01:56 PST." <199912280401.UAA36381@apollo.backplane.com> Date: Tue, 28 Dec 1999 20:12:47 +0800 From: Peter Wemm Message-Id: <19991228121247.99B541CCE@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI for the list; this has been fixed and committed now. Another problem in vn when backed with swap was found and fixed too. Matthew Dillon wrote: > > : > :Matthew Dillon wrote: > :[..] > :> And, in anycase, I am not going to spend hours putting together a long > :> involved patch when a simple short patch suffices. If you want to > :> spend the time to come up with your own patch (that doesn't screw the > :> pooch in regards to cluster performance!), then I'm all ears, otherwis e > :> this patch is what is going to go in for the 4.0 release. > : > :Please hold fire for a bit longer. I have (what I think is) a much cleaner > :fix in mind. There is no urgency here, a couple of hours isn't going to > :make the slightest difference to the big picture. > : > :On a side note, as the original author of the changes that lead to this, I > :would have thought it would have been appropriate to ask ME directly first > :before going public. > : > :Cheers, > :-Peter > > Your fix looks pretty good, Peter. I'll run it in and test it. I only > wish you had come up with it before Poul started going off the deep end. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 5: 5:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 86DFD14C49 for ; Tue, 28 Dec 1999 05:05:24 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id IAA20585 for ; Tue, 28 Dec 1999 08:05:18 -0500 (EST) Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id IAA03021 for ; Tue, 28 Dec 1999 08:05:20 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id IAA03017 for ; Tue, 28 Dec 1999 08:05:20 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Tue, 28 Dec 1999 08:05:20 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: the nist port 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 can't get the nist port to compile: c++ -g -O2 -Wall -DDO_NIST -DPACKAGE=\"ac3dec\" -DVERSION=\"0.5.5\" -I../../inc -c bitstream.c -o bitstream.o In file included from decode.h:24, from bitstream.c:27: ../../inc/athread.hh: In function `int athr_setschedparam(pthread *, int, sched_param *)': ../../inc/athread.hh:150: implicit declaration of function `int pthread_setschedparam(...)' ../../inc/athread.hh: In function `int athr_getschedparam(pthread *, int *, sched_param *)': ../../inc/athread.hh:151: implicit declaration of function `int pthread_getschedparam(...)' bitstream.c: In function `uint_32 bitstream_get(bitstream_t *, long unsigned int)': bitstream.c:47: warning: unused variable `uint_32 bits_to_go' bitstream.c:46: warning: unused variable `uint_32 bits_read' bitstream.c: At top level: bitstream.c:39: warning: `void bitstream_load(bitstream_t *)' declared `static' but never defined gmake[3]: *** [bitstream.o] Error 1 gmake[3]: Leaving directory `/usr/home/culverk/dl_temp/nist/src/ac3' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/home/culverk/dl_temp/nist/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/home/culverk/dl_temp/nist' gmake: *** [all-recursive-am] Error 2 Any help Soren? ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 5:41:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id BD5ED15174 for ; Tue, 28 Dec 1999 05:41:48 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id OAA07797; Tue, 28 Dec 1999 14:41:12 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <19991228121247.99B541CCE@overcee.netplex.com.au> References: <19991228121247.99B541CCE@overcee.netplex.com.au> Date: Tue, 28 Dec 1999 13:50:03 +0100 To: Peter Wemm , Matthew Dillon From: Brad Knowles Subject: Re: Proposed patch to fix VN device (again) Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:12 PM +0800 1999/12/28, Peter Wemm wrote: > FYI for the list; this has been fixed and committed now. Another problem > in vn when backed with swap was found and fixed too. Was the vn problem an issue for 3.x as well? If so, is there any chance of getting this mfc'ed any time soon? -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 6: 2:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 098A014EAA for ; Tue, 28 Dec 1999 06:02:30 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id BFFDF1CA0; Tue, 28 Dec 1999 22:02:22 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Brad Knowles Cc: Matthew Dillon , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: Proposed patch to fix VN device (again) In-Reply-To: Message from Brad Knowles of "Tue, 28 Dec 1999 13:50:03 +0100." Date: Tue, 28 Dec 1999 22:02:22 +0800 From: Peter Wemm Message-Id: <19991228140222.BFFDF1CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > At 8:12 PM +0800 1999/12/28, Peter Wemm wrote: > > > FYI for the list; this has been fixed and committed now. Another problem > > in vn when backed with swap was found and fixed too. > > Was the vn problem an issue for 3.x as well? If so, is there any > chance of getting this mfc'ed any time soon? No, 3.x doesn't support swap-backed vn devices. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 10: 5:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 2E7C4154C7 for ; Tue, 28 Dec 1999 10:05:39 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 18276 invoked from network); 28 Dec 1999 18:05:23 -0000 Received: from lca111.cvzoom.net (HELO cvzoom.net) (63.65.158.111) by ns.cvzoom.net with SMTP; 28 Dec 1999 18:05:23 -0000 Message-ID: <3868FBB9.D102D8DA@cvzoom.net> Date: Tue, 28 Dec 1999 13:04:41 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Seigo Tanimura Cc: current@freebsd.org Subject: Re: more patch for secondary buffer, polling and DMA emulation in pcm References: <14429.46098.1195.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14433.63218.157116.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <386278C7.B748EEF5@cvzoom.net> <14434.52947.683451.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14436.13492.839612.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <14439.4177.642029.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14439.26155.338725.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seigo Tanimura wrote: > > Ouch, the patch broke Rollemup, so I fixed just now. The URI is the same. > > Seigo> http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227.diff.gz Great, the sound drivers are working very nicely on my ESS 1868. Does pcm support SoundBlaster WavEffects? Hopefully, nobody will do anything to break the sound drivers (although it may happen). I think I'll make a backup of my /sys/dev source code tree just in case. ;-) - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 11: 7:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from main.avias.com (avias-gw.corbina.net [195.14.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 36F9314D5B for ; Tue, 28 Dec 1999 11:07:49 -0800 (PST) (envelope-from camel@avias.com) Received: from camel.avias.com (camel.avias.com [195.14.38.87]) by main.avias.com (8.9.3/8.9.3) with ESMTP id WAA22694; Tue, 28 Dec 1999 22:07:05 +0300 (MSK) (envelope-from camel@avias.com) Date: Tue, 28 Dec 1999 22:07:07 +0300 (MSK) From: Ilya Naumov To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: the nist port 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, 28 Dec 1999, Kenneth Wayne Culver wrote: > I can't get the nist port to compile: the same thing. css-auth builds fine. sincerely, ilya naumov (at work) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 11:51:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 6A769154E8 for ; Tue, 28 Dec 1999 11:51:21 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id NAA16394; Tue, 28 Dec 1999 13:28:14 GMT (envelope-from nik) Date: Tue, 28 Dec 1999 13:28:13 +0000 From: Nik Clayton To: Brooks Davis Cc: Kevin Entringer , current@FreeBSD.ORG Subject: Re: Make world documentation Message-ID: <19991228132813.A12000@catkin.nothing-going-on.org> References: <19991227213150.A6741@orion.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991227213150.A6741@orion.ac.hmc.edu>; from Brooks Davis on Mon, Dec 27, 1999 at 09:31:50PM -0800 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 09:31:50PM -0800, Brooks Davis wrote: > > Recently someone posted a url that provided a quick run through on some > > important extra steps to take while doing a make world from -STABLE to > > -CURRENT, unfortunatly I lost the URL. I was wondering if someone could > > post it again? I did check the archives, but I wasn't able to find it. > > http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html > > Though I though it was supposed to have been moved to the main site, but > that's what http://www.freebsd.org/tutorials/ says. Damn, I haven't updated the tutorial page. The contents of that URL have moved in to the Handbook. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 12:40:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 07E2D14F8B for ; Tue, 28 Dec 1999 12:40:31 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA45252; Tue, 28 Dec 1999 21:40:01 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912282040.VAA45252@freebsd.dk> Subject: Re: the nist port In-Reply-To: from Kenneth Wayne Culver at "Dec 28, 1999 08:05:20 am" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Tue, 28 Dec 1999 21:40:01 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kenneth Wayne Culver wrote: > I can't get the nist port to compile: > c++ -g -O2 -Wall -DDO_NIST -DPACKAGE=\"ac3dec\" -DVERSION=\"0.5.5\" > -I../../inc -c bitstream.c -o bitstream.o > In file included from decode.h:24, > from bitstream.c:27: > ../../inc/athread.hh: In function `int athr_setschedparam(pthread *, int, > sched_param *)': > ../../inc/athread.hh:150: implicit declaration of function `int > pthread_setschedparam(...)' > ../../inc/athread.hh: In function `int athr_getschedparam(pthread *, int > *, sched_param *)': > ../../inc/athread.hh:151: implicit declaration of function `int > pthread_getschedparam(...)' > bitstream.c: In function `uint_32 bitstream_get(bitstream_t *, long > unsigned int)': Uhm, seems like we need to define _POSIX_THREAD_PRIORITY_SCHEDULING now to get the prototypes for these, add: #ifdef __FreeBSD__ #define _POSIX_THREAD_PRIORITY_SCHEDULING #endif At line 80 in inc/athread.hh -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 12:47:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id A960215511 for ; Tue, 28 Dec 1999 12:46:55 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA46433; Tue, 28 Dec 1999 21:44:38 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912282044.VAA46433@freebsd.dk> Subject: Re: the nist port In-Reply-To: <199912282040.VAA45252@freebsd.dk> from Soren Schmidt at "Dec 28, 1999 09:40:01 pm" To: sos@freebsd.dk (Soren Schmidt) Date: Tue, 28 Dec 1999 21:44:38 +0100 (CET) Cc: culverk@wam.umd.edu (Kenneth Wayne Culver), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Soren Schmidt wrote: > Uhm, seems like we need to define _POSIX_THREAD_PRIORITY_SCHEDULING now > to get the prototypes for these, add: > > #ifdef __FreeBSD__ > #define _POSIX_THREAD_PRIORITY_SCHEDULING > #endif > > At line 80 in inc/athread.hh Just to follow up on my self, I've put up a new version that compiles here again at least... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 12:57:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3495B1551B for ; Tue, 28 Dec 1999 12:57:25 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA49015; Tue, 28 Dec 1999 21:55:41 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912282055.VAA49015@freebsd.dk> Subject: Re: How to de-select DMA to ad0? In-Reply-To: <14439.54923.884773.393442@trooper.velocet.net> from David Gilbert at "Dec 27, 1999 04:13:47 pm" To: dgilbert@velocet.ca (David Gilbert) Date: Tue, 28 Dec 1999 21:55:41 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David Gilbert wrote: > I've had my share of problems with this drive's DMA abilities. I'm > convinced that it has none... even though it probes as such. > > ad0: ATA-0 disk at ata0 as master > ad0: ... > ad0: 16 secs/int, 1 depth queue, DMA > > now... when I boot -v, I don't have a chance to write down what it > says, but it will hang every time with the following output: > > ad0: ad-timeout: lost disk contact > ata0: resetting drives -- mask=03 status0=50 status1=50 .. > > And that's it. It never prints out "done" which I see in many of the > list messages. Is there a way of disabling DMA on a specific drive? > I read a bit of the source, but didn't find any obvious documentation > on the issue. There is no way (yet) other than hacking the code, but I'm working on it... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 12:58: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6AC1814FDD for ; Tue, 28 Dec 1999 12:57:49 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA49015; Tue, 28 Dec 1999 21:55:41 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912282055.VAA49015@freebsd.dk> Subject: Re: How to de-select DMA to ad0? In-Reply-To: <14439.54923.884773.393442@trooper.velocet.net> from David Gilbert at "Dec 27, 1999 04:13:47 pm" To: dgilbert@velocet.ca (David Gilbert) Date: Tue, 28 Dec 1999 21:55:41 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems David Gilbert wrote: > I've had my share of problems with this drive's DMA abilities. I'm > convinced that it has none... even though it probes as such. > > ad0: ATA-0 disk at ata0 as master > ad0: ... > ad0: 16 secs/int, 1 depth queue, DMA > > now... when I boot -v, I don't have a chance to write down what it > says, but it will hang every time with the following output: > > ad0: ad-timeout: lost disk contact > ata0: resetting drives -- mask=03 status0=50 status1=50 .. > > And that's it. It never prints out "done" which I see in many of the > list messages. Is there a way of disabling DMA on a specific drive? > I read a bit of the source, but didn't find any obvious documentation > on the issue. There is no way (yet) other than hacking the code, but I'm working on it... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 14:27:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from cc158233-a.catv1.md.home.com (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (Postfix) with ESMTP id 9F5DB14C36 for ; Tue, 28 Dec 1999 14:27:29 -0800 (PST) (envelope-from sjr@home.net) Received: from istari.home.net (localhost.home.net [127.0.0.1]) by cc158233-a.catv1.md.home.com (8.9.3/8.9.3) with ESMTP id RAA02722 for ; Tue, 28 Dec 1999 17:24:42 -0500 (EST) (envelope-from sjr@cc158233-a.catv1.md.home.com) Message-Id: <199912282224.RAA02722@cc158233-a.catv1.md.home.com> Date: Tue, 28 Dec 1999 17:24:41 -0500 (EST) From: "Stephen J. Roznowski" Subject: Linux RealPlayer 5.0 working under current? To: freebsd-current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have the linux-realplayer-5.0 port working under -current? I'm running a -current that is a few days old, and have a "Creative ViBRA16C" sound chip. Playing a CDROM using xcdplayer works, but when I try to use realplayer, it just seems to hang. Here are the relevant lines from my boot: sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 9 drq 1,5 on isa0 sbc0: setting card to irq 9, drq 1, 5 pcm0: on sbc0 I can provide more info if necessary. Thanks, -- Stephen J. Roznowski (sjr@home.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 14:35:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id BBB391554C for ; Tue, 28 Dec 1999 14:35:11 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA10558; Tue, 28 Dec 1999 17:34:34 -0500 (EST) Date: Tue, 28 Dec 1999 17:34:34 -0500 (EST) From: Daniel Eischen To: Soren Schmidt Cc: Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG, jasone@canonware.com Subject: Re: the nist port In-Reply-To: <199912282040.VAA45252@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Dec 1999, Soren Schmidt wrote: > It seems Kenneth Wayne Culver wrote: > > I can't get the nist port to compile: > > c++ -g -O2 -Wall -DDO_NIST -DPACKAGE=\"ac3dec\" -DVERSION=\"0.5.5\" > > -I../../inc -c bitstream.c -o bitstream.o > > In file included from decode.h:24, > > from bitstream.c:27: > > ../../inc/athread.hh: In function `int athr_setschedparam(pthread *, int, > > sched_param *)': > > ../../inc/athread.hh:150: implicit declaration of function `int > > pthread_setschedparam(...)' > > ../../inc/athread.hh: In function `int athr_getschedparam(pthread *, int > > *, sched_param *)': > > ../../inc/athread.hh:151: implicit declaration of function `int > > pthread_getschedparam(...)' > > bitstream.c: In function `uint_32 bitstream_get(bitstream_t *, long > > unsigned int)': > > Uhm, seems like we need to define _POSIX_THREAD_PRIORITY_SCHEDULING now > to get the prototypes for these, add: > > #ifdef __FreeBSD__ > #define _POSIX_THREAD_PRIORITY_SCHEDULING > #endif > Hey, these _POSIX_THREAD_XXXX definitions used to be in pthread.h. It looks like they were removed from version 1.16 of pthread.h: revision 1.16 date: 1999/12/16 21:53:38; author: jasone; state: Exp; lines: +1 -18 Move POSIX feature constants from pthread.h to unistd.h, as required by 1003.1c-1995. Undefine _POSIX_THREAD_SAFE_FUNCTIONS, since we do not implement all of the necessary interfaces. At least getgrgid_r(), getrnam_r(), getpwuid_r(), getpwnam_r(), getc_unlocked(), getchar_unlocked(), putc_unlocked(), and putchar_unlocked() are missing. Due to a likely typo in 1003.1c-1995, we are not technically allowed to define _POSIX_THREADS without defining _POSIX_THREAD_SAFE_FUNCTIONS, but either way we're non-compliant, so I'm leaving _POSIX_THREADS defined. They're not in unistd.h either. This is a FreeBSD bug. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 14:41:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from watchtower.iad.dead-dog.com (ashford-113-40.tidalwave.net [208.206.113.40]) by hub.freebsd.org (Postfix) with ESMTP id 74C4814A2E for ; Tue, 28 Dec 1999 14:41:18 -0800 (PST) (envelope-from irving@iad.dead-dog.com) Received: from localhost (irving@localhost) by watchtower.iad.dead-dog.com (8.9.3/8.9.3) with ESMTP id RAA14722; Tue, 28 Dec 1999 17:41:09 -0500 (EST) (envelope-from irving@iad.dead-dog.com) Date: Tue, 28 Dec 1999 17:41:08 -0500 (EST) From: Irving Popovetsky To: "Stephen J. Roznowski" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Linux RealPlayer 5.0 working under current? In-Reply-To: <199912282224.RAA02722@cc158233-a.catv1.md.home.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 Why bother with 5.0? It cant play any modern streams anyway. http://proforma.real.com/real/player/linuxplayer.html I've been using the Linux G2 player on my -current box for a while now. Video can get a little choppy, and theres an occasional crash, but otherwise its fine. ( This is with both the old sb drivers and the newpcm driver. ) -Irving On Tue, 28 Dec 1999, Stephen J. Roznowski wrote: > Date: Tue, 28 Dec 1999 17:24:41 -0500 (EST) > From: Stephen J. Roznowski > To: freebsd-current@FreeBSD.ORG > Subject: Linux RealPlayer 5.0 working under current? > > Does anyone have the linux-realplayer-5.0 port working under -current? > > I'm running a -current that is a few days old, and have a "Creative > ViBRA16C" sound chip. Playing a CDROM using xcdplayer works, but when > I try to use realplayer, it just seems to hang. > > Here are the relevant lines from my boot: > > sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b > irq 9 drq 1,5 on isa0 > sbc0: setting card to irq 9, drq 1, 5 > pcm0: on sbc0 > > I can provide more info if necessary. > > Thanks, > -- > Stephen J. Roznowski (sjr@home.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 Tue Dec 28 15: 1:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 532FF150C1 for ; Tue, 28 Dec 1999 15:01:55 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id PAA99079 for ; Tue, 28 Dec 1999 15:01:54 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 28 Dec 1999 15:01:54 -0800 (PST) From: Doug White To: current@freebsd.org Subject: SUBMIT: compat.linux.pathmunge 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 fellow hackers, I've written up a short patch to add a sysctl to control the appending of /compat/linux/ to path requests in Linux mode. We had to get ADSM's Linux client working on FreeBSD so we could do backups of our systems. Luckily it comes statically linked so all was needed was this sysctl and some creative redirections (there's a bug in the termio ioctl() emulation still...) to get it working. Patch is attached. Alternately you can poke http://www.freebsd.org/~dwhite/linux.pathmunge.patch. These are against -current. I have a nasty #ifdef hack for 3.3 that requires Makefile changes to compile (you want to keep the fixed and unfixed kernel modules around on 3.3!). Please let me know if you have comments/suggestions/etc. If no one whines too badly I'll commit these later this week and finally break my declaration against making kernel changes. :) Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org Index: linux_mib.c =================================================================== RCS file: /usr/local/cvs/src/sys/i386/linux/linux_mib.c,v retrieving revision 1.2 diff -u -r1.2 linux_mib.c --- linux_mib.c 1999/08/28 02:16:31 1.2 +++ linux_mib.c 1999/12/07 06:33:35 @@ -43,6 +43,7 @@ char pr_osname[LINUX_MAX_UTSNAME]; char pr_osrelease[LINUX_MAX_UTSNAME]; int pr_oss_version; + int pr_pathmunge; }; SYSCTL_NODE(_compat, OID_AUTO, linux, CTLFLAG_RW, 0, @@ -111,6 +112,28 @@ 0, 0, linux_sysctl_oss_version, "I", "Linux OSS version"); +static int linux_pathmunge = 1; + +static int +linux_sysctl_pathmunge SYSCTL_HANDLER_ARGS +{ + int pathmunge; + int error; + + pathmunge = linux_get_pathmunge(req->p); + error = sysctl_handle_int(oidp, &pathmunge, 0, req); + if (error || req->newptr == NULL) + return (error); + error = linux_set_pathmunge(req->p, pathmunge); + return (error); +} + +SYSCTL_PROC(_compat_linux, OID_AUTO, pathmunge, + CTLTYPE_INT | CTLFLAG_RW | CTLFLAG_PRISON, + 0, 0, linux_sysctl_pathmunge, "I", + "Linux Path Munge"); + + static struct linux_prison * get_prison(struct proc *p) { @@ -226,6 +249,38 @@ lpr->pr_oss_version = oss_version; else linux_oss_version = oss_version; + + return (0); +} +int +linux_get_pathmunge(p) + struct proc *p; +{ + register struct prison *pr; + register struct linux_prison *lpr; + + pr = p->p_prison; + if (pr != NULL && pr->pr_linux != NULL) { + lpr = pr->pr_linux; + if (lpr->pr_pathmunge) + return (lpr->pr_pathmunge); + } + + return (linux_pathmunge); +} + +int +linux_set_pathmunge(p, pathmunge) + struct proc *p; + int pathmunge; +{ + register struct linux_prison *lpr; + + lpr = get_prison(p); + if (lpr != NULL) + lpr->pr_pathmunge = pathmunge; + else + linux_pathmunge = pathmunge; return (0); } Index: linux_mib.h =================================================================== RCS file: /usr/local/cvs/src/sys/i386/linux/linux_mib.h,v retrieving revision 1.2 diff -u -r1.2 linux_mib.h --- linux_mib.h 1999/08/28 02:16:32 1.2 +++ linux_mib.h 1999/12/07 05:22:18 @@ -1,3 +1,4 @@ + /*- * Copyright (c) 1999 Marcel Moolenaar * All rights reserved. @@ -39,5 +40,8 @@ int linux_get_oss_version __P((struct proc *p)); int linux_set_oss_version __P((struct proc *p, int oss_version)); + +int linux_get_pathmunge __P((struct proc *p)); +int linux_set_pathmunge __P((struct proc *p, int pathmunge)); #endif /* _LINUX_MIB_H_ */ Index: linux_util.c =================================================================== RCS file: /usr/local/cvs/src/sys/i386/linux/linux_util.c,v retrieving revision 1.8 diff -u -r1.8 linux_util.c --- linux_util.c 1999/08/28 00:45:25 1.8 +++ linux_util.c 1999/12/08 05:22:49 @@ -38,6 +38,7 @@ #include #include +#include const char linux_emul_path[] = "/compat/linux"; @@ -69,8 +70,22 @@ buf = (char *) malloc(MAXPATHLEN, M_TEMP, M_WAITOK); *pbuf = path; - for (ptr = buf; (*ptr = *prefix) != '\0'; ptr++, prefix++) - continue; + /* + * Look at the compat.linux.pathmunge sysctl to determine + * whether to add the linux_emul_path on the front of the + * requested file. Software that does tree walks, such + * as backup clients, get locked into the /compat/linux + * subtree if this is set. Setting the sysctl to 0 + * makes Linux apps access files like any other, but must + * be statically linked or they'll never find their libs. + */ + + if(linux_get_pathmunge(p)) { + for (ptr = buf; (*ptr = *prefix) != '\0'; ptr++, prefix++) + continue; + } else { + ptr = buf; + } sz = MAXPATHLEN - (ptr - buf); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 15:40:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id E836615522 for ; Tue, 28 Dec 1999 15:40:50 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 76301 invoked by uid 1001); 28 Dec 1999 23:38:06 -0000 Date: Tue, 28 Dec 1999 15:38:06 -0800 From: Jason Evans To: Daniel Eischen Cc: Soren Schmidt , Kenneth Wayne Culver , freebsd-current@FreeBSD.ORG Subject: Re: the nist port Message-ID: <19991228153806.R39990@sturm.canonware.com> References: <199912282040.VAA45252@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from eischen@vigrid.com on Tue, Dec 28, 1999 at 05:34:34PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 28, 1999 at 05:34:34PM -0500, Daniel Eischen wrote: > On Tue, 28 Dec 1999, Soren Schmidt wrote: > > It seems Kenneth Wayne Culver wrote: > > > I can't get the nist port to compile: > > > c++ -g -O2 -Wall -DDO_NIST -DPACKAGE=\"ac3dec\" -DVERSION=\"0.5.5\" > > > -I../../inc -c bitstream.c -o bitstream.o > > > In file included from decode.h:24, > > > from bitstream.c:27: > > > ../../inc/athread.hh: In function `int athr_setschedparam(pthread *, int, > > > sched_param *)': > > > ../../inc/athread.hh:150: implicit declaration of function `int > > > pthread_setschedparam(...)' > > > ../../inc/athread.hh: In function `int athr_getschedparam(pthread *, int > > > *, sched_param *)': > > > ../../inc/athread.hh:151: implicit declaration of function `int > > > pthread_getschedparam(...)' > > > bitstream.c: In function `uint_32 bitstream_get(bitstream_t *, long > > > unsigned int)': > > > > Uhm, seems like we need to define _POSIX_THREAD_PRIORITY_SCHEDULING now > > to get the prototypes for these, add: > > > > #ifdef __FreeBSD__ > > #define _POSIX_THREAD_PRIORITY_SCHEDULING > > #endif > > > > Hey, these _POSIX_THREAD_XXXX definitions used to be in pthread.h. > It looks like they were removed from version 1.16 of pthread.h: > > revision 1.16 > date: 1999/12/16 21:53:38; author: jasone; state: Exp; lines: +1 -18 > Move POSIX feature constants from pthread.h to unistd.h, as required by > 1003.1c-1995. > > Undefine _POSIX_THREAD_SAFE_FUNCTIONS, since we do not implement all of the > necessary interfaces. At least getgrgid_r(), getrnam_r(), getpwuid_r(), > getpwnam_r(), getc_unlocked(), getchar_unlocked(), putc_unlocked(), > and putchar_unlocked() are missing. Due to a likely typo in 1003.1c-1995, > we are not technically allowed to define _POSIX_THREADS without defining > _POSIX_THREAD_SAFE_FUNCTIONS, but either way we're non-compliant, so I'm > leaving _POSIX_THREADS defined. > > They're not in unistd.h either. This is a FreeBSD bug. They're in sys/unistd.h, which is included by unistd.h. That should be just fine, and that location appears to be consistent with our other POSIX macro definitions. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 16:18:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 2FBCC14D67 for ; Tue, 28 Dec 1999 16:18:15 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA22761; Tue, 28 Dec 1999 19:18:10 -0500 (EST) Date: Tue, 28 Dec 1999 19:18:10 -0500 (EST) From: Daniel Eischen Message-Id: <199912290018.TAA22761@pcnet1.pcnet.com> To: eischen@vigrid.com, jasone@canonware.com Subject: Re: the nist port Cc: culverk@wam.umd.edu, freebsd-current@FreeBSD.ORG, sos@freebsd.dk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > They're in sys/unistd.h, which is included by unistd.h. That should be > just fine, and that location appears to be consistent with our other POSIX > macro definitions. Ahh, good. I didn't have them because I wasn't up to date. So the question is now, why wasn't the nist port picking them up? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 17:14:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 97D9414C95 for ; Tue, 28 Dec 1999 17:14:16 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA09009; Tue, 28 Dec 1999 17:14:16 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA07636; Tue, 28 Dec 1999 17:14:16 -0800 (PST) (envelope-from obrien) Date: Tue, 28 Dec 1999 17:14:16 -0800 From: "David O'Brien" To: Amancio Hasty Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error Message-ID: <19991228171415.B7516@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <38664CC6.34DD3329@cvzoom.net> <199912262002.MAA77437@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912262002.MAA77437@rah.star-gate.com>; from hasty@rah.star-gate.com on Sun, Dec 26, 1999 at 12:02:58PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Actually, that's one of the newest versions of gcc. > > Perhaps a later snapshot of gcc will work . GCC 2.95.2 is a *RELEASED* version. We don't use snapshots as the base compiler. What every the problem is 4.0 will live with it unless someone narrows down the problem more. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 17:15:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6D69914FB8 for ; Tue, 28 Dec 1999 17:15:10 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA09020; Tue, 28 Dec 1999 17:15:10 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA07652; Tue, 28 Dec 1999 17:15:10 -0800 (PST) (envelope-from obrien) Date: Tue, 28 Dec 1999 17:15:10 -0800 From: "David O'Brien" To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: gcc compile error Message-ID: <19991228171510.C7516@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199912260717.XAA73116@rah.star-gate.com> <38664CC6.34DD3329@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38664CC6.34DD3329@cvzoom.net>; from dmmiller@cvzoom.net on Sun, Dec 26, 1999 at 12:13:42PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 26, 1999 at 12:13:42PM -0500, Donn Miller wrote: > I get similar errors trying to compile aview from ports. I just > updated my ports tree, so that can't be the problem. See the > attached make.log. There's something about not allowing access > to the cx register. ... > sstring.h:493: fixed or forbidden register 2 (cx) was spilled for class CREG. These are easy to fix. Please use `send-pr' to submit a PR and hopefully I can get to it. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 18: 9: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from svn.com.br (sv1.svn.com.br [200.223.74.33]) by hub.freebsd.org (Postfix) with ESMTP id 9FDC414DED; Tue, 28 Dec 1999 18:08:50 -0800 (PST) (envelope-from boozy@rabelo.eti.br) Received: from robusto (sp235.svn.com.br [200.223.82.25]) by svn.com.br (8.9.3/8.9.2) with SMTP id AAA00249; Wed, 29 Dec 1999 00:08:46 -0200 Message-Id: X-Sender: boozy%rabelo.eti.br@mickey.atarde.com.br (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Demo Date: Wed, 29 Dec 1999 00:01:30 -0200 To: freebsd-current@FreeBSD.org, freebsd-net@FreeBSD.org From: Boozy Subject: -current and IPv6 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Lists, How are the implementation of IPv6 in FreeBSD 4.0? Is it available? Is it stable? What is better: use FreeBSD 3.4 with Kame or FreeBSD 4.0? Thanks, Luciano Rabelo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 18:16:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id D6B1914E6F; Tue, 28 Dec 1999 18:16:12 -0800 (PST) (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.9.3/8.9.3) with ESMTP id SAA35503; Tue, 28 Dec 1999 18:15:59 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912290215.SAA35503@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@FreeBSD.ORG Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-reply-to: Your message of "Tue, 28 Dec 1999 17:14:16 PST." <19991228171415.B7516@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Dec 1999 18:15:59 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thats nice . Now we have a compiler which fails to build X. > > >Actually, that's one of the newest versions of gcc. > > > > Perhaps a later snapshot of gcc will work . > > GCC 2.95.2 is a *RELEASED* version. We don't use snapshots as the base > compiler. What every the problem is 4.0 will live with it unless someone > narrows down the problem more. > > -- > -- David (obrien@NUXI.com) -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 18:18:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id AB8E915498; Tue, 28 Dec 1999 18:18:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA10308; Tue, 28 Dec 1999 18:18:34 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Amancio Hasty Cc: obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-reply-to: Your message of "Tue, 28 Dec 1999 18:15:59 PST." <199912290215.SAA35503@rah.star-gate.com> Date: Tue, 28 Dec 1999 18:18:34 -0800 Message-ID: <10305.946433914@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thats nice . Now we have a compiler which fails to build X. This seems like hyperbole. I'm able to build X just fine with the -current compiler, so to directly imply that we can't do so flies in the face of common sense and experience. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 18:19:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 95F03155C1 for ; Tue, 28 Dec 1999 18:19:32 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id SAA04956; Tue, 28 Dec 1999 18:19:25 -0800 (PST) Date: Tue, 28 Dec 1999 18:19:25 -0800 (PST) From: Julian Elischer To: Doug White Cc: current@freebsd.org Subject: Re: SUBMIT: compat.linux.pathmunge 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, 28 Dec 1999, Doug White wrote: > Hello fellow hackers, > > I've written up a short patch to add a sysctl to control the appending of > /compat/linux/ to path requests in Linux mode. We had to get ADSM's Linux > client working on FreeBSD so we could do backups of our systems. Luckily > it comes statically linked so all was needed was this sysctl and some > creative redirections (there's a bug in the termio ioctl() emulation > still...) to get it working. > > Patch is attached. Alternately you can poke > http://www.freebsd.org/~dwhite/linux.pathmunge.patch. These are against > -current. I have a nasty #ifdef hack for 3.3 that requires Makefile > changes to compile (you want to keep the fixed and unfixed kernel modules > around on 3.3!). > > Please let me know if you have comments/suggestions/etc. If no one whines > too badly I'll commit these later this week and finally break my > declaration against making kernel changes. :) Good idea that... > > Doug White | FreeBSD: The Power to Serve > dwhite@resnet.uoregon.edu | www.FreeBSD.org > > Index: linux_mib.c > =================================================================== > RCS file: /usr/local/cvs/src/sys/i386/linux/linux_mib.c,v > retrieving revision 1.2 > diff -u -r1.2 linux_mib.c > --- linux_mib.c 1999/08/28 02:16:31 1.2 > +++ linux_mib.c 1999/12/07 06:33:35 > @@ -43,6 +43,7 @@ > char pr_osname[LINUX_MAX_UTSNAME]; > char pr_osrelease[LINUX_MAX_UTSNAME]; > int pr_oss_version; > + int pr_pathmunge; white space inconsistancy > }; > > SYSCTL_NODE(_compat, OID_AUTO, linux, CTLFLAG_RW, 0, > @@ -111,6 +112,28 @@ > 0, 0, linux_sysctl_oss_version, "I", > "Linux OSS version"); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 18:27:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 63536150F7; Tue, 28 Dec 1999 18:27:25 -0800 (PST) (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.9.3/8.9.3) with ESMTP id SAA35600; Tue, 28 Dec 1999 18:27:09 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912290227.SAA35600@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-reply-to: Your message of "Tue, 28 Dec 1999 18:18:34 PST." <10305.946433914@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Dec 1999 18:27:09 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I can rightfully claim that you cannot build XFree86 3.9 xxx dated December 24 with the default gcc compiler on FreeBSD -current. I am running FreeBSD -current and XFree86 3.9xxx current. > > Thats nice . Now we have a compiler which fails to build X. > > This seems like hyperbole. I'm able to build X just fine with the > -current compiler, so to directly imply that we can't do so flies in > the face of common sense and experience. > > - Jordan -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 18:51: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id AC08A156A9; Tue, 28 Dec 1999 18:51:05 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id EFB131C4D; Tue, 28 Dec 1999 21:50:14 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id E03163847; Tue, 28 Dec 1999 21:50:14 -0500 (EST) Date: Tue, 28 Dec 1999 21:50:14 -0500 (EST) From: Bill Fumerola To: Amancio Hasty Cc: "Jordan K. Hubbard" , obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-Reply-To: <199912290227.SAA35600@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Dec 1999, Amancio Hasty wrote: > Yes, I can rightfully claim that you cannot build XFree86 3.9 xxx dated > December 24 with the default gcc compiler on FreeBSD -current. > > I am running FreeBSD -current and XFree86 3.9xxx current. > > > > > > Typically this empty space would contain the output of the build failure, more details, or even a patch. You might want to find out why your mailer is thrashing it. > > > Thats nice . Now we have a compiler which fails to build X. > > > > This seems like hyperbole. I'm able to build X just fine with the > > -current compiler, so to directly imply that we can't do so flies in > > the face of common sense and experience. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 19:23:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B76F71500A for ; Tue, 28 Dec 1999 19:23:52 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id EAA40047; Wed, 29 Dec 1999 04:23:23 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912290323.EAA40047@freebsd.dk> Subject: Re: the nist port In-Reply-To: <199912290018.TAA22761@pcnet1.pcnet.com> from Daniel Eischen at "Dec 28, 1999 07:18:10 pm" To: eischen@vigrid.com (Daniel Eischen) Date: Wed, 29 Dec 1999 04:23:23 +0100 (CET) Cc: jasone@canonware.com, culverk@wam.umd.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Daniel Eischen wrote: > > They're in sys/unistd.h, which is included by unistd.h. That should be > > just fine, and that location appears to be consistent with our other POSIX > > macro definitions. > > Ahh, good. I didn't have them because I wasn't up to date. > > So the question is now, why wasn't the nist port picking them up? Because unistd.h is not included as linux/solaris/etc doesn't need that. I've put in yet another ifdef __FreeBSD__ to deal with it, sigh.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 21:57:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m5.columbus.rr.com [204.210.252.249]) by hub.freebsd.org (Postfix) with ESMTP id 78AC714DBE for ; Tue, 28 Dec 1999 21:57:17 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([24.95.60.151]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com for ; Wed, 29 Dec 1999 00:57:14 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id AAA81192; Wed, 29 Dec 1999 00:57:15 -0500 (EST) (envelope-from caa) Date: Wed, 29 Dec 1999 00:57:15 -0500 From: "Charles Anderson" To: multimedia@columbus.rr.com, FreeBSD Current Subject: mmaping /dev/dsp problems Message-ID: <19991229005714.C79763@midgard.dhs.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="ReaqsoxgOBHFXBhH" X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Hello, I'm trying to get the quake 1 source to compile and work under freebsd with glx. Most of the graphics parts work, and I can play, but I can't seem to get it to mmap the dsp dma buffer like it wants to. I have ripped out part of the code to demonstrate the problem. All I had to change to get it to compile this was to include machine/soundcard.h instead of linux/soundcard.h, but that doesn't seem to be enough to get it to work. I'm running -current with newpcm as of Dec 13, I know it's not the latest, but not much has changed in the dsp code lately. I'll build a new world tomorrow, and try it out. I have attached the files snd_linux.c & sound.h When I run snd_linux I get opening /dev/dsp audio_fd /dev/dsp=3 about to map 63488 bytes to /dev/dsp shm->buffer=280eb000 Segmentation fault (core dumped) bash-2.02$ gdb has this to say about shm->buffer (what mmap returns) $3 = ( unsigned char *) 0x280eb000 Thanks, for any help. -Charlie -- Charles Anderson caa@columbus.rr.com No quote, no nothin' --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="snd_linux.c" /* Copyright (C) 1996-1997 Id Software, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ #include #include #include #include #include #include #include #include #include #include #include "sound.h" int audio_fd; int snd_inited; static int tryrates[] = { 11025, 22051, 44100, 8000 }; #define Con_Printf printf dma_t *shm; qboolean SNDDMA_Init(void) { dma_t sn; int rc; int fmt; int tmp; int i; char *s; struct audio_buf_info info; int caps; snd_inited = 0; // open /dev/dsp, confirm capability to mmap, and get size of dma buffer Con_Printf("opening /dev/dsp\n"); audio_fd = open("/dev/dsp", O_RDWR); if (audio_fd < 0) { perror("/dev/dsp"); Con_Printf("Could not open /dev/dsp\n"); return 0; } Con_Printf("audio_fd /dev/dsp=%d\n", audio_fd); rc = ioctl(audio_fd, SNDCTL_DSP_RESET, 0); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not reset /dev/dsp\n"); close(audio_fd); return 0; } if (ioctl(audio_fd, SNDCTL_DSP_GETCAPS, &caps)==-1) { perror("/dev/dsp"); Con_Printf("Sound driver too old\n"); close(audio_fd); return 0; } if (!(caps & DSP_CAP_TRIGGER) || !(caps & DSP_CAP_MMAP)) { Con_Printf("Sorry but your soundcard can't do this\n"); close(audio_fd); return 0; } if (ioctl(audio_fd, SNDCTL_DSP_GETOSPACE, &info)==-1) { perror("GETOSPACE"); Con_Printf("Um, can't do GETOSPACE?\n"); close(audio_fd); return 0; } shm = &sn; shm->splitbuffer = 0; // set sample bits & speed s = getenv("QUAKE_SOUND_SAMPLEBITS"); if (s) shm->samplebits = atoi(s); /* else if ((i = COM_CheckParm("-sndbits")) != 0) shm->samplebits = atoi(com_argv[i+1]); */ if (shm->samplebits != 16 && shm->samplebits != 8) { ioctl(audio_fd, SNDCTL_DSP_GETFMTS, &fmt); if (fmt & AFMT_S16_LE) shm->samplebits = 16; else if (fmt & AFMT_U8) shm->samplebits = 8; } s = getenv("QUAKE_SOUND_SPEED"); if (s) shm->speed = atoi(s); /* else if ((i = COM_CheckParm("-sndspeed")) != 0) shm->speed = atoi(com_argv[i+1]); */ else { for (i=0 ; ispeed = tryrates[i]; } s = getenv("QUAKE_SOUND_CHANNELS"); if (s) shm->channels = atoi(s); /* else if ((i = COM_CheckParm("-sndmono")) != 0) shm->channels = 1; else if ((i = COM_CheckParm("-sndstereo")) != 0) shm->channels = 2; */ else shm->channels = 2; shm->samples = info.fragstotal * info.fragsize / (shm->samplebits/8); shm->submission_chunk = 1; // memory map the dma buffer Con_Printf("about to map %d bytes to /dev/dsp\n", info.fragstotal * info.fragsize); shm->buffer = (unsigned char *) mmap(NULL, info.fragstotal * info.fragsize, PROT_WRITE, MAP_SHARED, audio_fd, 0); if (!shm->buffer || shm->buffer == (unsigned char *)-1) { perror("/dev/dsp"); Con_Printf("Could not mmap /dev/dsp\n"); close(audio_fd); return 0; } Con_Printf("shm->buffer=%lx\n", shm->buffer); tmp = 0; if (shm->channels == 2) tmp = 1; rc = ioctl(audio_fd, SNDCTL_DSP_STEREO, &tmp); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not set /dev/dsp to stereo=%d", shm->channels); close(audio_fd); return 0; } if (tmp) shm->channels = 2; else shm->channels = 1; rc = ioctl(audio_fd, SNDCTL_DSP_SPEED, &shm->speed); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not set /dev/dsp speed to %d", shm->speed); close(audio_fd); return 0; } if (shm->samplebits == 16) { rc = AFMT_S16_LE; rc = ioctl(audio_fd, SNDCTL_DSP_SETFMT, &rc); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not support 16-bit data. Try 8-bit.\n"); close(audio_fd); return 0; } } else if (shm->samplebits == 8) { rc = AFMT_U8; rc = ioctl(audio_fd, SNDCTL_DSP_SETFMT, &rc); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not support 8-bit data.\n"); close(audio_fd); return 0; } } else { perror("/dev/dsp"); Con_Printf("%d-bit sound not supported.", shm->samplebits); close(audio_fd); return 0; } // toggle the trigger & start her up tmp = 0; rc = ioctl(audio_fd, SNDCTL_DSP_SETTRIGGER, &tmp); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not toggle.\n"); close(audio_fd); return 0; } tmp = PCM_ENABLE_OUTPUT; rc = ioctl(audio_fd, SNDCTL_DSP_SETTRIGGER, &tmp); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not toggle.\n"); close(audio_fd); return 0; } shm->samplepos = 0; snd_inited = 1; return 1; } main() { SNDDMA_Init(); memset(shm->buffer, 0, 2048); } --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sound.h" /* Copyright (C) 1996-1997 Id Software, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ // sound.h -- client sound i/o functions #ifndef __SOUND__ #define __SOUND__ #define DEFAULT_SOUND_PACKET_VOLUME 255 #define DEFAULT_SOUND_PACKET_ATTENUATION 1.0 typedef enum {false, true} qboolean; // !!! if this is changed, it much be changed in asm_i386.h too !!! typedef struct { int left; int right; } portable_samplepair_t; #if 0 typedef struct sfx_s { char name[MAX_QPATH]; cache_user_t cache; } sfx_t; // !!! if this is changed, it much be changed in asm_i386.h too !!! typedef struct { int length; int loopstart; int speed; int width; int stereo; byte data[1]; // variable sized } sfxcache_t; #endif typedef struct { qboolean gamealive; qboolean soundalive; qboolean splitbuffer; int channels; int samples; // mono samples in buffer int submission_chunk; // don't mix less than this # int samplepos; // in mono samples int samplebits; int speed; unsigned char *buffer; } dma_t; #if 0 // !!! if this is changed, it much be changed in asm_i386.h too !!! typedef struct { sfx_t *sfx; // sfx number int leftvol; // 0-255 volume int rightvol; // 0-255 volume int end; // end time in global paintsamples int pos; // sample position in sfx int looping; // where to loop, -1 = no looping int entnum; // to allow overriding a specific sound int entchannel; // vec3_t origin; // origin of sound effect vec_t dist_mult; // distance multiplier (attenuation/clipK) int master_vol; // 0-255 master volume } channel_t; typedef struct { int rate; int width; int channels; int loopstart; int samples; int dataofs; // chunk starts this many bytes from file start } wavinfo_t; void S_Init (void); void S_Startup (void); void S_Shutdown (void); void S_StartSound (int entnum, int entchannel, sfx_t *sfx, vec3_t origin, float fvol, float attenuation); void S_StaticSound (sfx_t *sfx, vec3_t origin, float vol, float attenuation); void S_StopSound (int entnum, int entchannel); void S_StopAllSounds(qboolean clear); void S_ClearBuffer (void); void S_Update (vec3_t origin, vec3_t v_forward, vec3_t v_right, vec3_t v_up); void S_ExtraUpdate (void); sfx_t *S_PrecacheSound (char *sample); void S_TouchSound (char *sample); void S_ClearPrecache (void); void S_BeginPrecaching (void); void S_EndPrecaching (void); void S_PaintChannels(int endtime); void S_InitPaintChannels (void); // picks a channel based on priorities, empty slots, number of channels channel_t *SND_PickChannel(int entnum, int entchannel); // spatializes a channel void SND_Spatialize(channel_t *ch); // initializes cycling through a DMA buffer and returns information on it qboolean SNDDMA_Init(void); // gets the current DMA position int SNDDMA_GetDMAPos(void); // shutdown the DMA xfer. void SNDDMA_Shutdown(void); // ==================================================================== // User-setable variables // ==================================================================== #define MAX_CHANNELS 128 #define MAX_DYNAMIC_CHANNELS 8 extern channel_t channels[MAX_CHANNELS]; // 0 to MAX_DYNAMIC_CHANNELS-1 = normal entity sounds // MAX_DYNAMIC_CHANNELS to MAX_DYNAMIC_CHANNELS + NUM_AMBIENTS -1 = water, etc // MAX_DYNAMIC_CHANNELS + NUM_AMBIENTS to total_channels = static sounds extern int total_channels; // // Fake dma is a synchronous faking of the DMA progress used for // isolating performance in the renderer. The fakedma_updates is // number of times S_Update() is called per second. // extern qboolean fakedma; extern int fakedma_updates; extern int paintedtime; extern vec3_t listener_origin; extern vec3_t listener_forward; extern vec3_t listener_right; extern vec3_t listener_up; extern volatile dma_t *shm; extern volatile dma_t sn; extern vec_t sound_nominal_clip_dist; extern cvar_t loadas8bit; extern cvar_t bgmvolume; extern cvar_t volume; extern qboolean snd_initialized; extern int snd_blocked; void S_LocalSound (char *s); sfxcache_t *S_LoadSound (sfx_t *s); wavinfo_t GetWavinfo (char *name, byte *wav, int wavlength); void SND_InitScaletable (void); void SNDDMA_Submit(void); void S_AmbientOff (void); void S_AmbientOn (void); #endif #endif --ReaqsoxgOBHFXBhH-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 21:58:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (m4.columbus.rr.com [204.210.252.19]) by hub.freebsd.org (Postfix) with ESMTP id 96CEA155BC; Tue, 28 Dec 1999 21:58:11 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([24.95.60.151]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Wed, 29 Dec 1999 00:58:09 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id AAA81203; Wed, 29 Dec 1999 00:58:10 -0500 (EST) (envelope-from caa) Date: Wed, 29 Dec 1999 00:58:10 -0500 From: "Charles Anderson" To: freebsd-multimedia@freebsd.org, FreeBSD Current Subject: mmaping /dev/dsp problems Message-ID: <19991229005714.C79763@midgard.dhs.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="H+4ONPRPur6+Ovig" X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --H+4ONPRPur6+Ovig Content-Type: text/plain; charset=us-ascii Hello, I'm trying to get the quake 1 source to compile and work under freebsd with glx. Most of the graphics parts work, and I can play, but I can't seem to get it to mmap the dsp dma buffer like it wants to. I have ripped out part of the code to demonstrate the problem. All I had to change to get it to compile this was to include machine/soundcard.h instead of linux/soundcard.h, but that doesn't seem to be enough to get it to work. I'm running -current with newpcm as of Dec 13, I know it's not the latest, but not much has changed in the dsp code lately. I'll build a new world tomorrow, and try it out. I have attached the files snd_linux.c & sound.h When I run snd_linux I get opening /dev/dsp audio_fd /dev/dsp=3 about to map 63488 bytes to /dev/dsp shm->buffer=280eb000 Segmentation fault (core dumped) bash-2.02$ gdb has this to say about shm->buffer (what mmap returns) $3 = ( unsigned char *) 0x280eb000 Thanks, for any help. -Charlie -- Charles Anderson caa@columbus.rr.com No quote, no nothin' --H+4ONPRPur6+Ovig Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="snd_linux.c" /* Copyright (C) 1996-1997 Id Software, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ #include #include #include #include #include #include #include #include #include #include #include "sound.h" int audio_fd; int snd_inited; static int tryrates[] = { 11025, 22051, 44100, 8000 }; #define Con_Printf printf dma_t *shm; qboolean SNDDMA_Init(void) { dma_t sn; int rc; int fmt; int tmp; int i; char *s; struct audio_buf_info info; int caps; snd_inited = 0; // open /dev/dsp, confirm capability to mmap, and get size of dma buffer Con_Printf("opening /dev/dsp\n"); audio_fd = open("/dev/dsp", O_RDWR); if (audio_fd < 0) { perror("/dev/dsp"); Con_Printf("Could not open /dev/dsp\n"); return 0; } Con_Printf("audio_fd /dev/dsp=%d\n", audio_fd); rc = ioctl(audio_fd, SNDCTL_DSP_RESET, 0); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not reset /dev/dsp\n"); close(audio_fd); return 0; } if (ioctl(audio_fd, SNDCTL_DSP_GETCAPS, &caps)==-1) { perror("/dev/dsp"); Con_Printf("Sound driver too old\n"); close(audio_fd); return 0; } if (!(caps & DSP_CAP_TRIGGER) || !(caps & DSP_CAP_MMAP)) { Con_Printf("Sorry but your soundcard can't do this\n"); close(audio_fd); return 0; } if (ioctl(audio_fd, SNDCTL_DSP_GETOSPACE, &info)==-1) { perror("GETOSPACE"); Con_Printf("Um, can't do GETOSPACE?\n"); close(audio_fd); return 0; } shm = &sn; shm->splitbuffer = 0; // set sample bits & speed s = getenv("QUAKE_SOUND_SAMPLEBITS"); if (s) shm->samplebits = atoi(s); /* else if ((i = COM_CheckParm("-sndbits")) != 0) shm->samplebits = atoi(com_argv[i+1]); */ if (shm->samplebits != 16 && shm->samplebits != 8) { ioctl(audio_fd, SNDCTL_DSP_GETFMTS, &fmt); if (fmt & AFMT_S16_LE) shm->samplebits = 16; else if (fmt & AFMT_U8) shm->samplebits = 8; } s = getenv("QUAKE_SOUND_SPEED"); if (s) shm->speed = atoi(s); /* else if ((i = COM_CheckParm("-sndspeed")) != 0) shm->speed = atoi(com_argv[i+1]); */ else { for (i=0 ; ispeed = tryrates[i]; } s = getenv("QUAKE_SOUND_CHANNELS"); if (s) shm->channels = atoi(s); /* else if ((i = COM_CheckParm("-sndmono")) != 0) shm->channels = 1; else if ((i = COM_CheckParm("-sndstereo")) != 0) shm->channels = 2; */ else shm->channels = 2; shm->samples = info.fragstotal * info.fragsize / (shm->samplebits/8); shm->submission_chunk = 1; // memory map the dma buffer Con_Printf("about to map %d bytes to /dev/dsp\n", info.fragstotal * info.fragsize); shm->buffer = (unsigned char *) mmap(NULL, info.fragstotal * info.fragsize, PROT_WRITE, MAP_SHARED, audio_fd, 0); if (!shm->buffer || shm->buffer == (unsigned char *)-1) { perror("/dev/dsp"); Con_Printf("Could not mmap /dev/dsp\n"); close(audio_fd); return 0; } Con_Printf("shm->buffer=%lx\n", shm->buffer); tmp = 0; if (shm->channels == 2) tmp = 1; rc = ioctl(audio_fd, SNDCTL_DSP_STEREO, &tmp); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not set /dev/dsp to stereo=%d", shm->channels); close(audio_fd); return 0; } if (tmp) shm->channels = 2; else shm->channels = 1; rc = ioctl(audio_fd, SNDCTL_DSP_SPEED, &shm->speed); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not set /dev/dsp speed to %d", shm->speed); close(audio_fd); return 0; } if (shm->samplebits == 16) { rc = AFMT_S16_LE; rc = ioctl(audio_fd, SNDCTL_DSP_SETFMT, &rc); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not support 16-bit data. Try 8-bit.\n"); close(audio_fd); return 0; } } else if (shm->samplebits == 8) { rc = AFMT_U8; rc = ioctl(audio_fd, SNDCTL_DSP_SETFMT, &rc); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not support 8-bit data.\n"); close(audio_fd); return 0; } } else { perror("/dev/dsp"); Con_Printf("%d-bit sound not supported.", shm->samplebits); close(audio_fd); return 0; } // toggle the trigger & start her up tmp = 0; rc = ioctl(audio_fd, SNDCTL_DSP_SETTRIGGER, &tmp); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not toggle.\n"); close(audio_fd); return 0; } tmp = PCM_ENABLE_OUTPUT; rc = ioctl(audio_fd, SNDCTL_DSP_SETTRIGGER, &tmp); if (rc < 0) { perror("/dev/dsp"); Con_Printf("Could not toggle.\n"); close(audio_fd); return 0; } shm->samplepos = 0; snd_inited = 1; return 1; } main() { SNDDMA_Init(); memset(shm->buffer, 0, 2048); } --H+4ONPRPur6+Ovig Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sound.h" /* Copyright (C) 1996-1997 Id Software, Inc. This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ // sound.h -- client sound i/o functions #ifndef __SOUND__ #define __SOUND__ #define DEFAULT_SOUND_PACKET_VOLUME 255 #define DEFAULT_SOUND_PACKET_ATTENUATION 1.0 typedef enum {false, true} qboolean; // !!! if this is changed, it much be changed in asm_i386.h too !!! typedef struct { int left; int right; } portable_samplepair_t; #if 0 typedef struct sfx_s { char name[MAX_QPATH]; cache_user_t cache; } sfx_t; // !!! if this is changed, it much be changed in asm_i386.h too !!! typedef struct { int length; int loopstart; int speed; int width; int stereo; byte data[1]; // variable sized } sfxcache_t; #endif typedef struct { qboolean gamealive; qboolean soundalive; qboolean splitbuffer; int channels; int samples; // mono samples in buffer int submission_chunk; // don't mix less than this # int samplepos; // in mono samples int samplebits; int speed; unsigned char *buffer; } dma_t; #if 0 // !!! if this is changed, it much be changed in asm_i386.h too !!! typedef struct { sfx_t *sfx; // sfx number int leftvol; // 0-255 volume int rightvol; // 0-255 volume int end; // end time in global paintsamples int pos; // sample position in sfx int looping; // where to loop, -1 = no looping int entnum; // to allow overriding a specific sound int entchannel; // vec3_t origin; // origin of sound effect vec_t dist_mult; // distance multiplier (attenuation/clipK) int master_vol; // 0-255 master volume } channel_t; typedef struct { int rate; int width; int channels; int loopstart; int samples; int dataofs; // chunk starts this many bytes from file start } wavinfo_t; void S_Init (void); void S_Startup (void); void S_Shutdown (void); void S_StartSound (int entnum, int entchannel, sfx_t *sfx, vec3_t origin, float fvol, float attenuation); void S_StaticSound (sfx_t *sfx, vec3_t origin, float vol, float attenuation); void S_StopSound (int entnum, int entchannel); void S_StopAllSounds(qboolean clear); void S_ClearBuffer (void); void S_Update (vec3_t origin, vec3_t v_forward, vec3_t v_right, vec3_t v_up); void S_ExtraUpdate (void); sfx_t *S_PrecacheSound (char *sample); void S_TouchSound (char *sample); void S_ClearPrecache (void); void S_BeginPrecaching (void); void S_EndPrecaching (void); void S_PaintChannels(int endtime); void S_InitPaintChannels (void); // picks a channel based on priorities, empty slots, number of channels channel_t *SND_PickChannel(int entnum, int entchannel); // spatializes a channel void SND_Spatialize(channel_t *ch); // initializes cycling through a DMA buffer and returns information on it qboolean SNDDMA_Init(void); // gets the current DMA position int SNDDMA_GetDMAPos(void); // shutdown the DMA xfer. void SNDDMA_Shutdown(void); // ==================================================================== // User-setable variables // ==================================================================== #define MAX_CHANNELS 128 #define MAX_DYNAMIC_CHANNELS 8 extern channel_t channels[MAX_CHANNELS]; // 0 to MAX_DYNAMIC_CHANNELS-1 = normal entity sounds // MAX_DYNAMIC_CHANNELS to MAX_DYNAMIC_CHANNELS + NUM_AMBIENTS -1 = water, etc // MAX_DYNAMIC_CHANNELS + NUM_AMBIENTS to total_channels = static sounds extern int total_channels; // // Fake dma is a synchronous faking of the DMA progress used for // isolating performance in the renderer. The fakedma_updates is // number of times S_Update() is called per second. // extern qboolean fakedma; extern int fakedma_updates; extern int paintedtime; extern vec3_t listener_origin; extern vec3_t listener_forward; extern vec3_t listener_right; extern vec3_t listener_up; extern volatile dma_t *shm; extern volatile dma_t sn; extern vec_t sound_nominal_clip_dist; extern cvar_t loadas8bit; extern cvar_t bgmvolume; extern cvar_t volume; extern qboolean snd_initialized; extern int snd_blocked; void S_LocalSound (char *s); sfxcache_t *S_LoadSound (sfx_t *s); wavinfo_t GetWavinfo (char *name, byte *wav, int wavlength); void SND_InitScaletable (void); void SNDDMA_Submit(void); void S_AmbientOff (void); void S_AmbientOn (void); #endif #endif --H+4ONPRPur6+Ovig-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 22: 6: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 6E87215005 for ; Tue, 28 Dec 1999 22:06:02 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA21911; Wed, 29 Dec 1999 16:35:53 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [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: <19991229005714.C79763@midgard.dhs.org> Date: Wed, 29 Dec 1999 16:35:52 +1030 (CST) From: "Daniel O'Connor" To: Charles Anderson Subject: RE: mmaping /dev/dsp problems Cc: FreeBSD Current , multimedia@columbus.rr.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Dec-99 Charles Anderson wrote: > Hello, > I'm trying to get the quake 1 source to compile and work under > freebsd with glx. 'me too' :) I have it working, it has some 'interesting' colour problems tho.. And it hangs after about 10 seconds of playing around. (Its killable though) Speaking of your mmap() problem.. When I try quake and the mmap sample program they get stuck in pcmflush forever :( --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 22:17:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 127E414FB5; Tue, 28 Dec 1999 22:17:23 -0800 (PST) (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.9.3/8.9.3) with ESMTP id WAA37116; Tue, 28 Dec 1999 22:17:04 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912290617.WAA37116@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Fumerola Cc: "Jordan K. Hubbard" , obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-reply-to: Your message of "Tue, 28 Dec 1999 21:50:14 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Dec 1999 22:17:04 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The details were previously posted by . Good Nite -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 22:23:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 9B76815170; Tue, 28 Dec 1999 22:23:36 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 682D51C4D; Wed, 29 Dec 1999 01:22:46 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 5942F3847; Wed, 29 Dec 1999 01:22:46 -0500 (EST) Date: Wed, 29 Dec 1999 01:22:46 -0500 (EST) From: Bill Fumerola To: Amancio Hasty Cc: "Jordan K. Hubbard" , obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-Reply-To: <199912290617.WAA37116@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Dec 1999, Amancio Hasty wrote: > The details were previously posted by . > > Good Nite > > Whatever ate the details on your previous post seems to be at it again. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 22:34:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 37B6A155C0; Tue, 28 Dec 1999 22:34:09 -0800 (PST) (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.9.3/8.9.3) with ESMTP id WAA37230; Tue, 28 Dec 1999 22:33:51 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912290633.WAA37230@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Fumerola Cc: "Jordan K. Hubbard" , obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-reply-to: Your message of "Wed, 29 Dec 1999 01:22:46 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Dec 1999 22:33:51 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 28 Dec 1999, Amancio Hasty wrote: > > > The details were previously posted by . > > > > Good Nite > > > > > > Whatever ate the details on your previous post seems to be at it again. Here is a copy of my mail post which I received from the -current mail list that is my post went out intact. Posted on Sat, 25 Dec 1999 23:17:45 -0800 ------------------------------------------------------------------- While trying to compile the latest version of XFree86 I found the following compiler bug. {root} gcc -v Using builtin specs. gcc version 2.95.2 19991024 (release) I assume that this an old version of gcc... xc/programs/Xserver/Xext cc -c -pipe -O2 -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -I. -I../include -I../../../exports/include/X11 -I../../../include/extensions -I../../../include/fonts -I../mi -I../../../programs/Xserver/hw/xfree86/common -I../../../include/fonts -I../../.. -I../../../exports/include -DCSRG_BASED -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DSMART_SCHEDULE -DNDEBUG -DFUNCPROTO=15 -DNARROWPROTO xf86vmode.c In file included from xf86vmode.c:41: ../include/extnsionst.h:91: warning: function declaration isn't a prototype ../include/extnsionst.h:100: warning: function declaration isn't a prototype ../include/extnsionst.h:106: warning: function declaration isn't a prototype xf86vmode.c: In function `ProcXF86VidModeGetMonitor': xf86vmode.c:1320: Unable to generate reloads for: (insn 300 298 302 (parallel[ (set (reg:SI 0 %eax) (fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0)))) (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) (const_int -34 [0xffffffde])) 0)) (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) (const_int -36 [0xffffffdc])) 0)) (clobber (mem:SI (plus:SI (reg:SI 6 %ebp) (const_int -40 [0xffffffd8])) 0)) (clobber (scratch:HI)) ] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil)) (expr_list:REG_DEAD (reg:SI 0 %eax) (expr_list:REG_UNUSED (scratch:HI) (nil)))) *** Error code 1 -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 22:52:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 7B47914D9B; Tue, 28 Dec 1999 22:52:45 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id CD7C81CA0; Wed, 29 Dec 1999 14:52:33 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Amancio Hasty Cc: Bill Fumerola , "Jordan K. Hubbard" , obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-Reply-To: Message from Amancio Hasty of "Tue, 28 Dec 1999 22:33:51 PST." <199912290633.WAA37230@rah.star-gate.com> Date: Wed, 29 Dec 1999 14:52:33 +0800 From: Peter Wemm Message-Id: <19991229065233.CD7C81CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > On Tue, 28 Dec 1999, Amancio Hasty wrote: > > > > > The details were previously posted by . > > > > > > Good Nite > > > > > > > > > > Whatever ate the details on your previous post seems to be at it again. > > Here is a copy of my mail post which I received from the -current mail list > that is my post went out intact. It isn't much use to anyone like this... We need to be able to reproduce this. What release of xfree86 is this? 3.9.16 as released? if not you will need to give us code if you want help. Failing that, how about a cc -E of the file in question so we can compile it standalone and see what is going wrong with the inline asm? > Posted on Sat, 25 Dec 1999 23:17:45 -0800 > ------------------------------------------------------------------- > > While trying to compile the latest version of XFree86 I found the following > compiler bug. > > {root} gcc -v > Using builtin specs. > gcc version 2.95.2 19991024 (release) > > > I assume that this an old version of gcc... > > > xc/programs/Xserver/Xext > > > cc -c -pipe -O2 -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -Wstrict-pr ototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wne sted-externs -I. > -I../include -I../../../exports/include/X11 -I../../../include/extensions -I../../../include/fonts -I../mi -I../../../programs/Xserver/hw/xfree86/ common > -I../../../include/fonts -I../../.. -I../../../exports/include -DCSRG_BASED -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGF ONT -DDPMSExtension > -DPIXPRIV -DPANORAMIX -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE > -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DSMART_SCHEDULE -DNDEBUG -DFUNCPROTO=15 -DN ARROWPROTO xf86vmode.c > In file included from xf86vmode.c:41: > ../include/extnsionst.h:91: warning: function declaration isn't a prototype > ../include/extnsionst.h:100: warning: function declaration isn't a prototype > ../include/extnsionst.h:106: warning: function declaration isn't a prototype > xf86vmode.c: In function `ProcXF86VidModeGetMonitor': > xf86vmode.c:1320: Unable to generate reloads for: > (insn 300 298 302 (parallel[ > (set (reg:SI 0 %eax) > (fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0)))) > (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) > (const_int -34 [0xffffffde])) 0)) > (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) > (const_int -36 [0xffffffdc])) 0)) > (clobber (mem:SI (plus:SI (reg:SI 6 %ebp) > (const_int -40 [0xffffffd8])) 0)) > (clobber (scratch:HI)) > ] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil)) > (expr_list:REG_DEAD (reg:SI 0 %eax) > (expr_list:REG_UNUSED (scratch:HI) > (nil)))) > *** Error code 1 > > > > > > -- > > Amancio Hasty > hasty@rah.star-gate.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 23: 2:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 77C4515170; Tue, 28 Dec 1999 23:02:18 -0800 (PST) (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.9.3/8.9.3) with ESMTP id XAA37455; Tue, 28 Dec 1999 23:01:43 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912290701.XAA37455@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm Cc: Bill Fumerola , "Jordan K. Hubbard" , obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-reply-to: Your message of "Wed, 29 Dec 1999 14:52:33 +0800." <19991229065233.CD7C81CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 Dec 1999 23:01:43 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look I stated previously and only a few hours ago: --------------------------------------------------- >Yes, I can rightfully claim that you cannot build XFree86 3.9 xxx dated >December 24 with the default gcc compiler on FreeBSD -current. > >I am running FreeBSD -current and XFree86 3.9xxx current. --------------------------------------------------- More precisely : FreeBSD -current was last cvsup on my system on Dec 23 18:59. XFree86 3.9.xxx was cvsup on December 24th I am sorry but this is sufficient information to reproduce the problem. > Amancio Hasty wrote: > > > On Tue, 28 Dec 1999, Amancio Hasty wrote: > > > > > > > The details were previously posted by . > > > > > > > > Good Nite > > > > > > > > > > > > > > Whatever ate the details on your previous post seems to be at it again. > > > > Here is a copy of my mail post which I received from the -current mail list > > that is my post went out intact. > > It isn't much use to anyone like this... We need to be able to reproduce > this. What release of xfree86 is this? 3.9.16 as released? if not you will > need to give us code if you want help. > > Failing that, how about a cc -E of the file in question so we can compile it > standalone and see what is going wrong with the inline asm? > > > > Posted on Sat, 25 Dec 1999 23:17:45 -0800 > > ------------------------------------------------------------------- > > > > While trying to compile the latest version of XFree86 I found the following > > compiler bug. > > > > {root} gcc -v > > Using builtin specs. > > gcc version 2.95.2 19991024 (release) > > > > > > I assume that this an old version of gcc... > > > > > > xc/programs/Xserver/Xext > > > > > > cc -c -pipe -O2 -ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith -Wstrict-pr > ototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wne > sted-externs -I. > > -I../include -I../../../exports/include/X11 -I../../../include/extensions > -I../../../include/fonts -I../mi -I../../../programs/Xserver/hw/xfree86/ > common > > -I../../../include/fonts -I../../.. -I../../../exports/include -DCSRG_BASED > -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGF > ONT -DDPMSExtension > > -DPIXPRIV -DPANORAMIX -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH > -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE > > -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DSMART_SCHEDULE -DNDEBUG -DFUNCPROTO=15 -DN > ARROWPROTO xf86vmode.c > > In file included from xf86vmode.c:41: > > ../include/extnsionst.h:91: warning: function declaration isn't a prototype > > ../include/extnsionst.h:100: warning: function declaration isn't a prototype > > ../include/extnsionst.h:106: warning: function declaration isn't a prototype > > xf86vmode.c: In function `ProcXF86VidModeGetMonitor': > > xf86vmode.c:1320: Unable to generate reloads for: > > (insn 300 298 302 (parallel[ > > (set (reg:SI 0 %eax) > > (fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0)))) > > (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) > > (const_int -34 [0xffffffde])) 0)) > > (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) > > (const_int -36 [0xffffffdc])) 0)) > > (clobber (mem:SI (plus:SI (reg:SI 6 %ebp) > > (const_int -40 [0xffffffd8])) 0)) > > (clobber (scratch:HI)) > > ] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil)) > > (expr_list:REG_DEAD (reg:SI 0 %eax) > > (expr_list:REG_UNUSED (scratch:HI) > > (nil)))) > > *** Error code 1 > > > > > > > > > > > > -- > > > > Amancio Hasty > > hasty@rah.star-gate.com > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au > -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 23: 6:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id ACBE114A2A; Tue, 28 Dec 1999 23:06:19 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id BDD111CA0; Wed, 29 Dec 1999 15:06:08 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Amancio Hasty Cc: Bill Fumerola , "Jordan K. Hubbard" , obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-Reply-To: Message from Amancio Hasty of "Tue, 28 Dec 1999 23:01:43 PST." <199912290701.XAA37455@rah.star-gate.com> Date: Wed, 29 Dec 1999 15:06:08 +0800 From: Peter Wemm Message-Id: <19991229070608.BDD111CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > > Look I stated previously and only a few hours ago: > > --------------------------------------------------- > >Yes, I can rightfully claim that you cannot build XFree86 3.9 xxx dated > >December 24 with the default gcc compiler on FreeBSD -current. > > > >I am running FreeBSD -current and XFree86 3.9xxx current. > --------------------------------------------------- > > More precisely : > > FreeBSD -current was last cvsup on my system on Dec 23 18:59. > > XFree86 3.9.xxx was cvsup on December 24th I am sorry but this is > sufficient information to reproduce the problem. No, it is not, because we can't *get* XFree86 3.9.xxx -current, so we cannot reproduce it, can we? You either need to give us enough to build that part, or provide a preprocessed file so we can feed the backends directly, or fix it yourself. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 28 23:56:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 7D9A3151CC; Tue, 28 Dec 1999 23:56:44 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id QAA10835; Wed, 29 Dec 1999 16:56:13 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id QAA09640; Wed, 29 Dec 1999 16:56:12 +0900 (JST) Received: from localhost ([192.168.245.125]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id QAA11390; Wed, 29 Dec 1999 16:56:10 +0900 (JST) To: boozy@rabelo.eti.br Cc: freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: -current and IPv6 In-Reply-To: References: X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991229165641J.shin@nd.net.fujitsu.co.jp> Date: Wed, 29 Dec 1999 16:56:41 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 46 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi Lists, > > How are the implementation of IPv6 in FreeBSD 4.0? Is it available? Is it > stable? The work on the current is still going on. Followings are already committed, and seems to be working well. -most of IPv6 extensions in kernel(tcp for IPv6 and IPv6 multicasting not yet) -IPsec in kernel -libc update -basic tools(ifconfig, route, netstat) -several udp and raw apps for IPv6 Now following patch is under review on freebsd-arch and cvs-committers. -tcp for IPv6 And following patch will be made for review soon. -libipsec and several ipsec related apps Then followings will be prepared. -IPv6 multicasting for kernel and apps -tcp apps for IPv6 -ppp for IPv6 -several library updates for IPv6 -many ports for IPv6 > What is better: use FreeBSD 3.4 with Kame or FreeBSD 4.0? Enough functionality is available now only on FreeBSD 3.4 with Kame. And other differencies are, - on-going merging on FreeBSD4.0 is based on KAME 19991101 SNAP, and some add on bug fixes. So FreeBSD 3.4 with Kame has newer changes based on KAME environment. (also might have newer bugs ;-) - I found some FreeBSD 3.x with Kame bugs on merging work, and fixed them on the current. Significant ones are committed to KAME repository soon, but small things might be delayed, because now I am more concentrated on 4.0 merging work. Yoshinobu Inoue > Luciano Rabelo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 0: 2:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (Postfix) with ESMTP id 15A0D15167 for ; Wed, 29 Dec 1999 00:02:46 -0800 (PST) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.8.8) id JAA17885 for current@freebsd.org; Wed, 29 Dec 1999 09:02:45 +0100 (MET) (envelope-from werner) From: Werner Griessl Message-Id: <199912290802.JAA17885@btp1da.phy.uni-bayreuth.de> Subject: unknown soundcard To: current@freebsd.org Date: Wed, 29 Dec 1999 09:02:45 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My "Terratec 128i PCI" soundcard probes as "unknown" in current: pci0: unknown card (vendor=0x125d, dev=0x1969) at 13.0 irq 17 Here are the labels read from the chip on the soundcard: ESS Solo-1 ES1938S G438 TTUB43833S P4,214,125 System is: FreeBSD werner.test.privat.priv 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Dec 28 14:46:12 CET 1999 croot@werner.test.privat.priv:/usr/src/sys/compile/SMP-WERNER i386 What can I do to make it work ? Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 0: 3:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (Postfix) with ESMTP id A0BBA15190 for ; Wed, 29 Dec 1999 00:03:56 -0800 (PST) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.8.8) id JAA17904 for current@freebsd.org; Wed, 29 Dec 1999 09:03:56 +0100 (MET) (envelope-from werner) From: Werner Griessl Message-Id: <199912290803.JAA17904@btp1da.phy.uni-bayreuth.de> Subject: broken ppp To: current@freebsd.org Date: Wed, 29 Dec 1999 09:03:56 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG current's new ppp discards the "#0001"-part from my german telekom account and makes it impossible to connect to my provider. It worked ~ 2 weeks ago with current and works also in 3.4-Stable. Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 3:39: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 52B5815579 for ; Wed, 29 Dec 1999 03:39:05 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 1CEA52DC09; Wed, 29 Dec 1999 12:39:26 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 515F87811; Wed, 29 Dec 1999 12:36:10 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 45BE610E10; Wed, 29 Dec 1999 12:36:10 +0100 (CET) Date: Wed, 29 Dec 1999 12:36:10 +0100 (CET) From: Andrzej Bialecki To: Doug White Cc: current@freebsd.org Subject: Re: SUBMIT: compat.linux.pathmunge 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, 28 Dec 1999, Doug White wrote: > Hello fellow hackers, > > I've written up a short patch to add a sysctl to control the appending of > /compat/linux/ to path requests in Linux mode. We had to get ADSM's Linux > client working on FreeBSD so we could do backups of our systems. Luckily > it comes statically linked so all was needed was this sysctl and some > creative redirections (there's a bug in the termio ioctl() emulation > still...) to get it working. Funny... I was in the process of doing almost exactly the same changes. Initially, I've done this fo /tmp and /var only, because some software was creating lock files _and_ IPC keys using (obviously) normal /tmp and /var/tmp, and they ended up having very different values, which somehow confused it... Anyway, the solution I would suggest is to have more granularity instead of all-or-nothing. I'd suggest a linked list of paths, set up by compat.linux.pathmunge.paths, and the other sysctl to turn on the checking. If the *paths sysctl is empty, it's equivalent to your functionality. Comments? :-) Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 4:34: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id CF7BF14BD2; Wed, 29 Dec 1999 04:33:58 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 339B41CA0; Wed, 29 Dec 1999 20:33:51 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Amancio Hasty Cc: Bill Fumerola , "Jordan K. Hubbard" , obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-Reply-To: Message from Amancio Hasty of "Tue, 28 Dec 1999 23:14:19 PST." <199912290714.XAA37627@rah.star-gate.com> Date: Wed, 29 Dec 1999 20:33:51 +0800 From: Peter Wemm Message-Id: <19991229123351.339B41CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > I really doubt that I am the only one here that can get XFree86 3.9.xxx -curr ent . > Nevertheless if it can help out to fix the default compiler here is the infor mation which > you reguested. > > Command Line executed to generate the output file and with the exception of t he > gcc option "-E" it is the exact same command which failed to compile xf86vmod e.c The current official release (ports/lang/egcs) also has this problem. However, ports/lang/gcc-devel (the current snapshot) compiles this file OK. Looking at the changelog, it seems that there has been a *lot* of work on the reload/clobber/etc area. So, if you want to compile the current XFree86, it looks like it'll need the port. The bad news is that the cygnus folks are absolutely determined to not support any dual-format (a.out and elf) stuff for us, this means that you won't be able to build a.out libraries. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 4:43:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id BEFE314EC4 for ; Wed, 29 Dec 1999 04:43:56 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from dyn-22.blackbox-2.netaxs.com (dyn-22.blackbox-2.netaxs.com [207.106.60.22]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id HAA08641 for ; Wed, 29 Dec 1999 07:43:01 -0500 (EST) Date: Wed, 29 Dec 1999 07:43:01 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: current@FreeBSD.ORG Subject: Re: broken ppp In-Reply-To: <199912290803.JAA17904@btp1da.phy.uni-bayreuth.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Dec 1999, Werner Griessl wrote: <> <>current's new ppp discards the "#0001"-part from my <>german telekom account and makes it impossible to <>connect to my provider. <> While we are on the subject, ppp no longer runs an external chat script. This used to work: set login "\"!chat \\\\-f /etc/ppp/login \\\\-r /var/log/connect.log\"" -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 4:58:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id BD96F14A07; Wed, 29 Dec 1999 04:58:46 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 8239D1CCF; Wed, 29 Dec 1999 20:58:33 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Bryan Liesner Cc: current@FreeBSD.ORG, brian@freebsd.org Subject: Re: broken ppp In-Reply-To: Message from Bryan Liesner of "Wed, 29 Dec 1999 07:43:01 EST." Date: Wed, 29 Dec 1999 20:58:33 +0800 From: Peter Wemm Message-Id: <19991229125833.8239D1CCF@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bryan Liesner wrote: > On Wed, 29 Dec 1999, Werner Griessl wrote: > > <> > <>current's new ppp discards the "#0001"-part from my > <>german telekom account and makes it impossible to > <>connect to my provider. > <> > > While we are on the subject, ppp no longer runs an external chat > script. This used to work: > > set login "\"!chat \\\\-f /etc/ppp/login \\\\-r /var/log/connect.log\"" Heh, I'll join in too.. I've been having ppp abort on me a few times. Today it died with "Error: Request for mbuf size 2329 denied" after I attempted to do a 'show links' on an already established pppctl connection: Dec 29 10:38:27 haywire ppp[882]: tun0: Phase: Unknown protocol 0x80fb (compression on single link in multilink group control) Dec 29 10:38:27 haywire ppp[882]: tun0: LCP: 1: SendProtocolRej(15) state = Opened Dec 29 10:39:24 haywire ppp[882]: tun0: Phase: 1: HDLC errors -> FCS: 0, ADDR: 0, COMD: 0, PROTO: 1 (pppctl connects here) Dec 29 10:55:10 haywire ppp[882]: tun0: Phase: Connected to client from 202.12.86.2:41555 Dec 29 10:55:12 haywire ppp[882]: tun0: Command: 202.12.86.2:41555: passwd ******** (and here I type 'show links') Dec 29 10:55:55 haywire ppp[882]: tun0: Phase: 1: HDLC errors -> FCS: 2, ADDR: 0, COMD: 0, PROTO: 0 Dec 29 10:55:55 haywire ppp[882]: tun0: Warning: lqr_Input: magic 0x428bf108 is wrong, expecting 0x14ae603f Dec 29 10:55:56 haywire ppp[882]: tun0: Error: Request for mbuf size 2329 denied Dec 29 10:55:56 haywire ppp[882]: tun0: Phase: 202.12.86.2:41555: Client connection dropped. Dec 29 10:55:56 haywire ppp[882]: tun0: Phase: PPP Terminated (71). Dec 29 10:55:56 haywire ppp[882]: tun0: IPCP: mp: LayerDown: 202.12.86.2 Dec 29 10:55:56 haywire ppp[882]: tun0: IPCP: mp: SendTerminateReq(15) state = Opened Dec 29 10:55:56 haywire ppp[882]: tun0: IPCP: mp: State change Opened --> Closing Dec 29 10:55:56 haywire ppp[882]: tun0: CCP: mp: State change Stopped --> Closed Dec 29 10:55:56 haywire ppp[882]: tun0: CCP: mp: State change Closed --> Initial Dec 29 10:55:56 haywire ppp[882]: tun0: Warning: Del route failed: 0.0.0.0: Non-existent Dec 29 10:55:56 haywire ppp[882]: tun0: Error: Oops, destroying a datalink in state open (he's dead jim!) Dec 29 10:56:19 haywire ppp[882]: tun0: Phase: 1: Connect time: 1112 secs: 533725 octets in, 386209 octets out Dec 29 10:56:19 haywire ppp[882]: tun0: Phase: total 827 bytes/sec, peak 4972 bytes/sec on Wed Dec 29 10:56:19 1999 > -Bryan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 6: 5:18 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 8B68114BC4; Wed, 29 Dec 1999 06:05:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7AD8D1CD821; Wed, 29 Dec 1999 06:05:17 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 29 Dec 1999 06:05:17 -0800 (PST) From: Kris Kennaway To: Emre Cc: Wilko Bulte , freebsd-current@freebsd.org Subject: Re: IPFW In-Reply-To: <19991227170258.A25978@iris.vsrc.uab.edu> 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, 27 Dec 1999, Emre wrote: > Not really. All my other boxes (NetBSD/OpenBSD) run -current so I'm > used to be on the "bleeding edge" I figured it would be enabled > by default, since FreeBSD promises to be _the_ Server O/S. Please see http://www.freebsd.org/handbook/cutting-edge.html#CURRENT This question was really freebsd-questions material and not the kind of thing which is appropriate for freebsd-current. If you're running FreeBSD-CURRENT you're expected to be familiar with the technicalities of FreeBSD (i.e. not just NetBSD/OpenBSD), which I'm not sure that you are, yet. It's not (just) about the danger to your own system, it's the hand-holding load on the developers when a FreeBSD neophyte thinks he's ready to run the developer's version :-( Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 6:47:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 7AAFC1577D for ; Wed, 29 Dec 1999 06:47:13 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) for current@freebsd.org id 123KNc-0002S8-00; Wed, 29 Dec 1999 14:47:12 +0000 Received: from localhost (jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with ESMTP id OAA82201 for ; Wed, 29 Dec 1999 14:47:12 GMT (envelope-from jcm@dogma.freebsd-uk.eu.org) Date: Wed, 29 Dec 1999 14:47:12 +0000 (GMT) From: Jonathon McKitrick To: current@freebsd.org Subject: question about egcs 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 Will egcs affect the size of the kernel or any other compiledcode? I read that the exception code can add a lot to the object size. -=> jm <=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 6:51: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 93C96155ED for ; Wed, 29 Dec 1999 06:50:47 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 123KPc-0005O8-00; Wed, 29 Dec 1999 16:49:16 +0200 From: Sheldon Hearn To: Jonathon McKitrick Cc: current@FreeBSD.ORG Subject: Re: question about egcs In-reply-to: Your message of "Wed, 29 Dec 1999 14:47:12 GMT." Date: Wed, 29 Dec 1999 16:49:16 +0200 Message-ID: <20715.946478956@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Dec 1999 14:47:12 GMT, Jonathon McKitrick wrote: > Will egcs affect the size of the kernel or any other compiledcode? Yes. Try it out for yourself and have a look, or hunt the -current mailing list archives. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 7: 5: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 2E6DA15628; Wed, 29 Dec 1999 07:04:55 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0FB561CD821; Wed, 29 Dec 1999 07:04:55 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 29 Dec 1999 07:04:54 -0800 (PST) From: Kris Kennaway To: Randy Bush Cc: FreeBSD Current , markm@freebsd.org Subject: Re: buildworld failure In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Dec 1999, Randy Bush wrote: > mkdep -f .depend -a -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/= kerberosIV/include -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include = -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/krb -I/usr= /src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kdb -I/usr/src/k= erberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm -I/usr/src/kerber= osIV/lib/libkadm/../../../crypto/kerberosIV/lib/roken -I/usr/obj/usr/src/ke= rberosIV/lib/libkadm/../../lib/libkrb -I/usr/obj/usr/src/kerberosIV/lib/lib= kadm/../../lib/libkadm -I/usr/obj/usr/src/kerberosIV/lib/libkadm -I/usr/src= /kerberosIV/lib/libkadm/../../include -DHAVE_CONFIG_H -I/usr/obj/usr/src/ke= rberosIV/lib/libkadm/../../include -DBINDIR=3D\"/usr/bin\" -DSBINDIR=3D\"/u= sr/sbin\" -I/usr/obj/usr/src/i386/usr/include /usr/src/kerberosIV/lib/libk= adm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c /usr/src/kerberosIV= /lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c /usr/src/ker= berosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c /usr/ob= j/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.c /usr/src/kerb= erosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_locl.h:79, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_cli_wrap.c:30: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: in= valid macro name > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_locl.h:82, > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/ker= berosIV/lib/kadm/kadm_cli_wrap.c:30: > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: = warning: `ERROR_TABLE_BASE_' redefined > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: wa= rning: this is the location of the previous definition > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: = invalid macro name [SNIP] I saw these too when I was building with a fresh tree checked out from internat. Mark? :) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 7:31:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 26393151B1 for ; Wed, 29 Dec 1999 07:31:40 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for current@freebsd.org id 123L4c-000Lpk-00; Wed, 29 Dec 1999 15:31:38 +0000 Received: from localhost (jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with ESMTP id PAA82425 for ; Wed, 29 Dec 1999 15:31:38 GMT (envelope-from jcm@dogma.freebsd-uk.eu.org) Date: Wed, 29 Dec 1999 15:31:38 +0000 (GMT) From: Jonathon McKitrick To: current@freebsd.org Subject: snapshot stability 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 Some time ago, Greg wrote: "USers looking for stability should be damn careful which version of the -current snapshot they run." As of right now, which would that be? The august CD snapshot release or the one available on the cvs servers right now? -=> jm <=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 7:40: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 5FCB814EB8 for ; Wed, 29 Dec 1999 07:40:01 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 123LCY-0005bd-00; Wed, 29 Dec 1999 17:39:50 +0200 From: Sheldon Hearn To: Jonathon McKitrick Cc: current@FreeBSD.ORG Subject: Re: snapshot stability In-reply-to: Your message of "Wed, 29 Dec 1999 15:31:38 GMT." Date: Wed, 29 Dec 1999 17:39:50 +0200 Message-ID: <21552.946481990@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Dec 1999 15:31:38 GMT, Jonathon McKitrick wrote: > As of right now, which would that be? The august CD snapshot release or > the one available on the cvs servers right now? If I were you, I'd hold out for 4.0-RELEASE, since it's just around the corner (January some time). Otherwise, just inhale and prepare to bleed. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 7:40:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 2F3A915596; Wed, 29 Dec 1999 07:40:50 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id CAA10513; Thu, 30 Dec 1999 02:40:47 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Thu, 30 Dec 1999 02:40:46 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: gcc compile error In-Reply-To: <19991228171415.B7516@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Dec 1999, David O'Brien wrote: > > Perhaps a later snapshot of gcc will work . > > GCC 2.95.2 is a *RELEASED* version. We don't use snapshots as the base > compiler. What every the problem is 4.0 will live with it unless someone > narrows down the problem more. The latest Polygraph (ver 2.2.8) proxy-cache benchmarking source (Available at http://www.ircache.net/Polygraph/) does not compile on my very recent 4.0 system. (rebuilding world now...) I get this error, after dl'ing polygraph-2.2.8-src.tar.gz, running 'configure', then running 'make': ... c++ -g -O3 -Wall -Wwrite-strings -Woverloaded-virtual -Iinclude -Ixstd/include -Ipgl/include -Ixparser/include -I.. -DHAVE_CONFIG_H -c Connection.cc In file included from include/PortMgr.h:29, from Connection.cc:33: include/LevelStat.h:55: invalid type `const char[1]' for default argument to `const String &' *** Error code 1 Stop in /usr/home/andyf/src/polygraph/src. *** Error code 1 Stop in /usr/home/andyf/src/polygraph. The "offending" code looks like this: ostream &print(ostream &os, const String &pfx = "") const; When I did a 'touch Connection.o ; make' it compiled another source file that included PortMgr.h / LevelStat.h just fine, but bombed out elsewhere! > > -- > -- David (obrien@NUXI.com) > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 7:49:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id EAB75150C7 for ; Wed, 29 Dec 1999 07:49:39 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 123LM2-0007qW-00; Wed, 29 Dec 1999 15:49:38 +0000 Received: from localhost (jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with ESMTP id PAA82508; Wed, 29 Dec 1999 15:49:38 GMT (envelope-from jcm@dogma.freebsd-uk.eu.org) Date: Wed, 29 Dec 1999 15:49:38 +0000 (GMT) From: Jonathon McKitrick To: Sheldon Hearn Cc: current@FreeBSD.ORG Subject: Re: snapshot stability In-Reply-To: <21552.946481990@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I read that the VM system has been revamped and egcs is the default compiler. Will either of these affect the average user besides larger binaries? Also, i'm wondering if maybe i should just wait until the 4.1 release for everything to settle down... -=> jm <=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 7:54:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 83C2C150C7 for ; Wed, 29 Dec 1999 07:54:14 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 24986 invoked from network); 29 Dec 1999 10:54:11 -0000 Received: from lca67.cvzoom.net (63.65.158.67) by ns.cvzoom.net with SMTP; 29 Dec 1999 10:54:11 -0000 Date: Wed, 29 Dec 1999 10:53:16 -0500 (EST) From: Donn Miller To: Jonathon McKitrick Cc: Sheldon Hearn , current@FreeBSD.ORG Subject: Re: snapshot stability 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, 29 Dec 1999, Jonathon McKitrick wrote: > I read that the VM system has been revamped and egcs is the default > compiler. Will either of these affect the average user besides larger > binaries? Actually, egcs WAS the default compiler. It is now (output of gcc -v): $ gcc -v Using builtin specs. gcc version 2.95.2 19991024 (release) - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 8:42:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5083214D9A for ; Wed, 29 Dec 1999 08:42:38 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA43854; Wed, 29 Dec 1999 09:42:37 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA03014; Wed, 29 Dec 1999 09:42:36 -0700 (MST) Message-Id: <199912291642.JAA03014@harmony.village.org> To: Sheldon Hearn Subject: Re: snapshot stability Cc: Jonathon McKitrick , current@FreeBSD.ORG In-reply-to: Your message of "Wed, 29 Dec 1999 17:39:50 +0200." <21552.946481990@axl.noc.iafrica.com> References: <21552.946481990@axl.noc.iafrica.com> Date: Wed, 29 Dec 1999 09:42:36 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <21552.946481990@axl.noc.iafrica.com> Sheldon Hearn writes: : If I were you, I'd hold out for 4.0-RELEASE, since it's just around the : corner (January some time). Otherwise, just inhale and prepare to : bleed. :-) I think that the January some time date may be optimistic given that we're not in feature freeze yet. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 10:34:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from nimbus.skycache.com (nimbus.skycache.com [207.239.230.67]) by hub.freebsd.org (Postfix) with ESMTP id 00C0D156B8 for ; Wed, 29 Dec 1999 10:34:04 -0800 (PST) (envelope-from gary@skycache.com) Received: from skycache.com (nat-146.skycache.com [199.34.53.146]) by nimbus.skycache.com (8.9.3/8.9.3) with ESMTP id NAA18678 for ; Wed, 29 Dec 1999 13:34:04 -0500 (EST) Message-ID: <386A5322.886494CC@skycache.com> Date: Wed, 29 Dec 1999 13:29:54 -0500 From: garrett allen X-Mailer: Mozilla 4.07 [en] (Win98; U) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 3bd2ca54 subscribe freebsd-current gary@skycache.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 10:34:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from nimbus.skycache.com (nimbus.skycache.com [207.239.230.67]) by hub.freebsd.org (Postfix) with ESMTP id 6878A1583D for ; Wed, 29 Dec 1999 10:34:50 -0800 (PST) (envelope-from gary@skycache.com) Received: from skycache.com (nat-146.skycache.com [199.34.53.146]) by nimbus.skycache.com (8.9.3/8.9.3) with ESMTP id NAA18705 for ; Wed, 29 Dec 1999 13:34:49 -0500 (EST) Message-ID: <386A534F.AAB2D2F1@skycache.com> Date: Wed, 29 Dec 1999 13:30:39 -0500 From: garrett allen X-Mailer: Mozilla 4.07 [en] (Win98; U) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth 52898cdd subscribe freebsd-stable gary@skycache.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 10:38:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 10975151F6 for ; Wed, 29 Dec 1999 10:38:08 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id TAA55881 for current@FreeBSD.org; Wed, 29 Dec 1999 19:32:04 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Wed, 29 Dec 1999 19:32:02 +0100 From: Marcel Moolenaar Message-ID: <386A53A2.9BA6A01E@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: Subject: Re: SUBMIT: compat.linux.pathmunge Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > > Please let me know if you have comments/suggestions/etc. If no one whines > too badly I'll commit these later this week and finally break my > declaration against making kernel changes. :) I'm not sure I like this. Please hold off until I've got some time to think this over. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 10:40:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 79075156E6; Wed, 29 Dec 1999 10:40:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA28360; Wed, 29 Dec 1999 10:40:47 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Amancio Hasty Cc: Peter Wemm , Bill Fumerola , obrien@FreeBSD.org, Donn Miller , current@FreeBSD.org Subject: Re: gcc compile error In-reply-to: Your message of "Tue, 28 Dec 1999 23:01:43 PST." <199912290701.XAA37455@rah.star-gate.com> Date: Wed, 29 Dec 1999 10:40:47 -0800 Message-ID: <28357.946492847@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > XFree86 3.9.xxx was cvsup on December 24th I am sorry but this is > sufficient information to reproduce the problem. Not if you actually want the problem solved. There's this thing called "making it easy on the people you're demanding things of" in order that they might have some chance of actually doing it. Insisting that someone cvsup the entire X source tree, as you've clearly *already* done, hardly falls into the category of attempting to save the gcc maintainers work in attempting to track down the problem you're complaining about. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 10:43:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6D7EB151F6; Wed, 29 Dec 1999 10:43:22 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA28392; Wed, 29 Dec 1999 10:43:33 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Amancio Hasty Cc: Peter Wemm , Bill Fumerola , obrien@FreeBSD.org, Donn Miller , current@FreeBSD.org Subject: Re: gcc compile error In-reply-to: Your message of "Tue, 28 Dec 1999 23:14:19 PST." <199912290714.XAA37627@rah.star-gate.com> Date: Wed, 29 Dec 1999 10:43:32 -0800 Message-ID: <28389.946493012@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sending out an attachment of that size to a public mailing list was hardly necessary, and the increasing stridency of your posts leading up to this only serve to indicate that you may be heading in the truly wrong direction with all this and seriously need to rethink your strategy before you do something that has people howling for your blood. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 10:44:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 75481157C0 for ; Wed, 29 Dec 1999 10:44:16 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 17680 invoked from network); 29 Dec 1999 13:44:12 -0000 Received: from lca67.cvzoom.net (63.65.158.67) by ns.cvzoom.net with SMTP; 29 Dec 1999 13:44:12 -0000 Date: Wed, 29 Dec 1999 13:43:17 -0500 (EST) From: Donn Miller To: "Jordan K. Hubbard" Cc: Amancio Hasty , Peter Wemm , Bill Fumerola , obrien@FreeBSD.org, current@FreeBSD.org Subject: Re: gcc compile error In-Reply-To: <28357.946492847@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Dec 1999, Jordan K. Hubbard wrote: > > XFree86 3.9.xxx was cvsup on December 24th I am sorry but this is > > sufficient information to reproduce the problem. [snip] > Insisting that someone cvsup the entire X source tree, as you've > clearly *already* done, hardly falls into the category of attempting > to save the gcc maintainers work in attempting to track down the > problem you're complaining about. Hmmm... are "regular people" even allowed access to the XFree86 cvs server? I thought that was just reserved for XFree86 developers? Don't tell me we have to become XFree86 developers just to solve a simple gcc problem. :) BTW, I hope they release 3.9.17 soon.... - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 10:53:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 956BD14E87 for ; Wed, 29 Dec 1999 10:53:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA08593; Wed, 29 Dec 1999 10:52:34 -0800 Date: Wed, 29 Dec 1999 10:52:34 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sheldon Hearn Cc: Jonathon McKitrick , current@FreeBSD.ORG Subject: Re: snapshot stability In-Reply-To: <21552.946481990@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Wed, 29 Dec 1999 15:31:38 GMT, Jonathon McKitrick wrote: > > > As of right now, which would that be? The august CD snapshot release or > > the one available on the cvs servers right now? > > If I were you, I'd hold out for 4.0-RELEASE, since it's just around the > corner (January some time). Otherwise, just inhale and prepare to > bleed. :-) > Despite the risk of bleeding, I have to say that I've installed several snaps (from the freebsd snapshot server) with excellent results. Now that spasm over the block device removal has gone away, things have been pretty darn stable for me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 10:57:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 6F79015713; Wed, 29 Dec 1999 10:57:45 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBTIvb348299; Wed, 29 Dec 1999 20:57:37 +0200 (SAST) Message-Id: <199912291857.dBTIvb348299@gratis.grondar.za> To: Kris Kennaway Cc: Randy Bush , FreeBSD Current Subject: Re: buildworld failure References: In-Reply-To: ; from Kris Kennaway "Wed, 29 Dec 1999 07:04:54 PST." Date: Wed, 29 Dec 1999 20:57:33 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I ain't done nuttin'!! I don't see the errors below, I see libroken breaking because libgcc.a can't be found. *grumble* M > On Sun, 26 Dec 1999, Randy Bush wrote: > > > mkdep -f .depend -a -I/usr/src/kerberosIV/lib/libkadm/../../../crypto/ke rberosIV/include -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include -I/usr /src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/krb -I/usr/src/kerbe rosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kdb -I/usr/src/kerberosIV/lib/ libkadm/../../../crypto/kerberosIV/lib/kadm -I/usr/src/kerberosIV/lib/libkadm/. ./../../crypto/kerberosIV/lib/roken -I/usr/obj/usr/src/kerberosIV/lib/libkadm/. ./../lib/libkrb -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm -I/ usr/obj/usr/src/kerberosIV/lib/libkadm -I/usr/src/kerberosIV/lib/libkadm/../../ include -DHAVE_CONFIG_H -I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/i386/usr/incl ude /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_c li_wrap.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/k adm_stream.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kad m/kadm_supp.c /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_er r.c /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_p assword.c > > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe rosIV/lib/kadm/kadm_locl.h:79, > > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe rosIV/lib/kadm/kadm_cli_wrap.c:30: > > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: inva lid macro name > > In file included from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe rosIV/lib/kadm/kadm_locl.h:82, > > from /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerbe rosIV/lib/kadm/kadm_cli_wrap.c:30: > > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: wa rning: `ERROR_TABLE_BASE_' redefined > > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warn ing: this is the location of the previous definition > > /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: in valid macro name > > [SNIP] > > I saw these too when I was building with a fresh tree checked out from > internat. Mark? :) > > Kris > -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 11: 0:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 25CC815713 for ; Wed, 29 Dec 1999 11:00:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA19586; Wed, 29 Dec 1999 11:00:30 -0800 (PST) (envelope-from dillon) Date: Wed, 29 Dec 1999 11:00:30 -0800 (PST) From: Matthew Dillon Message-Id: <199912291900.LAA19586@apollo.backplane.com> To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: gcc compile error References: <199912260717.XAA73116@rah.star-gate.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Amancio Hasty ... : :While trying to compile the latest version of XFree86 I found the following :compiler bug. : :{root} gcc -v :Using builtin specs. :gcc version 2.95.2 19991024 (release) I was able to compile up both XFree 3.9.16 with the older egcs release: apollo:/src/pub/XFree3.9.15/source/xc# gcc -v Using builtin specs. gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) I'm trying the latest gcc that is in our tree now. I'm not sure there is anything we can do about it, though, except try to isolate the bug into a smaller piece of code and pass it onto the GCC group. Judging by the previously reported error it may be possible to work around the problem by volatilizing some of the variables in the procedure the compiler is blowing up in. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 11: 0:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id EBF7D15771; Wed, 29 Dec 1999 11:00:57 -0800 (PST) (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.9.3/8.9.3) with ESMTP id LAA42935; Wed, 29 Dec 1999 11:00:26 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912291900.LAA42935@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: Peter Wemm , Bill Fumerola , obrien@FreeBSD.org, Donn Miller , current@FreeBSD.org Subject: Re: gcc compile error In-reply-to: Your message of "Wed, 29 Dec 1999 10:43:32 PST." <28389.946493012@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 11:00:26 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sending out an attachment of that size to a public mailing list was > hardly necessary, and the increasing stridency of your posts leading > up to this only serve to indicate that you may be heading in the truly > wrong direction with all this and seriously need to rethink your > strategy before you do something that has people howling for your > blood. > Thats fine . Actually "someone" did start working on the problem 8) Take Care -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 11:21:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3A32214CCF; Wed, 29 Dec 1999 11:21:41 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA20927; Wed, 29 Dec 1999 11:21:24 -0800 (PST) (envelope-from dillon) Date: Wed, 29 Dec 1999 11:21:24 -0800 (PST) From: Matthew Dillon Message-Id: <199912291921.LAA20927@apollo.backplane.com> To: Peter Wemm Cc: Amancio Hasty , Bill Fumerola , "Jordan K. Hubbard" , obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error References: <19991229070608.BDD111CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> FreeBSD -current was last cvsup on my system on Dec 23 18:59. :> :> XFree86 3.9.xxx was cvsup on December 24th I am sorry but this is :> sufficient information to reproduce the problem. : :No, it is not, because we can't *get* XFree86 3.9.xxx -current, so we :cannot reproduce it, can we? : :You either need to give us enough to build that part, or provide a :preprocessed file so we can feed the backends directly, or fix it yourself. Sure you can.... well, you can get close anyway. ftp ftp.xfree86.org cd snapshots get 3.9.16.tar.gz I've been keeping up to date myself hoping that the I128 driver (for the SGI flatscreen) would support the I^2 protocol the SGI uses to control backlight brightness, there being no external knob on the monitor to fiddle with. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 11:37:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id E019015020; Wed, 29 Dec 1999 11:37:48 -0800 (PST) (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.9.3/8.9.3) with ESMTP id LAA43173; Wed, 29 Dec 1999 11:37:18 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912291937.LAA43173@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" Cc: Peter Wemm , Bill Fumerola , obrien@FreeBSD.org, Donn Miller , current@FreeBSD.org Subject: Re: gcc compile error In-reply-to: Your message of "Wed, 29 Dec 1999 10:43:32 PST." <28389.946493012@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 11:37:18 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sending out an attachment of that size to a public mailing list was > hardly necessary, and the increasing stridency of your posts leading > up to this only serve to indicate that you may be heading in the truly > wrong direction with all this and seriously need to rethink your > strategy before you do something that has people howling for your > blood. > > - Jordan Okay folks, This is the scoop. For the benefit of those which don't have access to the latest XFree86 release you can download the file from ftp://rah.star-gate.com/pub/bug.c uname -a FreeBSD x.star-gate.com 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Mon Dec 27 13:55:25 PST 1999 root@x.star-gate.com:/usr/src/sys/compile/MUADIB i386 gcc -v Using builtin specs. gcc version 2.95.2 19991024 (release) gcc -c -O2 bug.c xf86vmode.c: In function `ProcXF86VidModeGetMonitor': xf86vmode.c:1320: Unable to generate reloads for: (insn 300 298 302 (parallel[ (set (reg:SI 0 %eax) (fix:SI (fix:SF (subreg:SF (reg:SI 0 %eax) 0)))) (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) (const_int -34 [0xffffffde])) 0)) (clobber (mem:HI (plus:SI (reg:SI 6 %ebp) (const_int -36 [0xffffffdc])) 0)) (clobber (mem:SI (plus:SI (reg:SI 6 %ebp) (const_int -40 [0xffffffd8])) 0)) (clobber (scratch:HI)) ] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil)) (expr_list:REG_DEAD (reg:SI 0 %eax) (expr_list:REG_UNUSED (scratch:HI) (nil)))) ------------------------------ Without -O or -O2 the program compiles okay. gcc -c bug.c According to Peter, the ports/lang/gcc-devel (the current snapshot) appears to compile this program fine -- that is the compiler bug has been fixed. So there appears to be two solutions to get around this problem: 1. compile without -O or 2. installed the latest snapshot of gcc. Take Care Guys -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 13:38:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon2.gun.de [192.109.159.15]) by hub.freebsd.org (Postfix) with ESMTP id 7301C15373 for ; Wed, 29 Dec 1999 13:38:17 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id WAA04188 for ; Wed, 29 Dec 1999 22:38:04 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id WAA01394 for current@FreeBSD.ORG; Wed, 29 Dec 1999 22:33:42 +0100 (CET) (envelope-from andreas) Date: Wed, 29 Dec 1999 22:33:42 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: -current runs really fine now (very performant) Message-ID: <19991229223342.A1134@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last days (week?) I silently complaint about slow/hanging xbuffy process and even mutt reading large inbox (20MB) was very very slow. Now it is again blindingly fast under -current SMP. Don't know, what change did it, but thanks to you all ! Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 14:31:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-68.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.196]) by hub.freebsd.org (Postfix) with ESMTP id 66C49156EC; Wed, 29 Dec 1999 14:31:05 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA41574; Wed, 29 Dec 1999 22:08:24 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id WAA91959; Wed, 29 Dec 1999 22:11:01 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912292211.WAA91959@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Peter Wemm Cc: Bryan Liesner , current@FreeBSD.ORG, brian@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: broken ppp In-Reply-To: Message from Peter Wemm of "Wed, 29 Dec 1999 20:58:33 +0800." <19991229125833.8239D1CCF@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 22:11:01 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bryan Liesner wrote: > > On Wed, 29 Dec 1999, Werner Griessl wrote: > > > > <> > > <>current's new ppp discards the "#0001"-part from my > > <>german telekom account and makes it impossible to > > <>connect to my provider. > > <> > > > > While we are on the subject, ppp no longer runs an external chat > > script. This used to work: > > > > set login "\"!chat \\\\-f /etc/ppp/login \\\\-r /var/log/connect.log\"" Urk ! The version you have is now *FIXED*. The above line should read: set login "\"!chat \\-f /etc/ppp/login \\-r /var/log/connect.log\"" as the - sign should only be escaped once for the chat parsing and once for the argument parsing. I'll fix the docs and update README.changes. > Heh, I'll join in too.. I've been having ppp abort on me a few times. Today > it died with "Error: Request for mbuf size 2329 denied" after I attempted to do > a 'show links' on an already established pppctl connection: > > Dec 29 10:38:27 haywire ppp[882]: tun0: Phase: Unknown protocol 0x80fb (compression on single link in multilink group control) > Dec 29 10:38:27 haywire ppp[882]: tun0: LCP: 1: SendProtocolRej(15) state = Opened > Dec 29 10:39:24 haywire ppp[882]: tun0: Phase: 1: HDLC errors -> FCS: 0, ADDR: 0, COMD: 0, PROTO: 1 > (pppctl connects here) > Dec 29 10:55:10 haywire ppp[882]: tun0: Phase: Connected to client from 202.12.86.2:41555 > Dec 29 10:55:12 haywire ppp[882]: tun0: Command: 202.12.86.2:41555: passwd ******** > (and here I type 'show links') > Dec 29 10:55:55 haywire ppp[882]: tun0: Phase: 1: HDLC errors -> FCS: 2, ADDR: 0, COMD: 0, PROTO: 0 > Dec 29 10:55:55 haywire ppp[882]: tun0: Warning: lqr_Input: magic 0x428bf108 is wrong, expecting 0x14ae603f > Dec 29 10:55:56 haywire ppp[882]: tun0: Error: Request for mbuf size 2329 denied I've no idea what tried to allocate this. It should be impossible to allocate an mbuf this size because it's illegal for either side to send a packet this size.... Even the CCP layer (which creates packets of a pretty much random size) allocates mbufs in smaller chunks and chains them, throwing the results away if they exceed the original packet size. Prior to my recent (user-)mbuf changes, this may have resulted in corruption later on (I think). Is there any chance of running under gdb and catching a stack trace when ppp calls AbortProgram() from m_get() ? Specifically, I'm interested in what's calling m_get() and why it's calling it with such a large value. > Dec 29 10:55:56 haywire ppp[882]: tun0: Phase: 202.12.86.2:41555: Client connection dropped. > Dec 29 10:55:56 haywire ppp[882]: tun0: Phase: PPP Terminated (71). Hmm, perhaps this message should be emitted at the end of AbortProgram(). It looks silly here - before all the complaints about shutting everything down in a hurry. > Dec 29 10:55:56 haywire ppp[882]: tun0: IPCP: mp: LayerDown: 202.12.86.2 > Dec 29 10:55:56 haywire ppp[882]: tun0: IPCP: mp: SendTerminateReq(15) state = Opened > Dec 29 10:55:56 haywire ppp[882]: tun0: IPCP: mp: State change Opened --> Closing > Dec 29 10:55:56 haywire ppp[882]: tun0: CCP: mp: State change Stopped --> Closed > Dec 29 10:55:56 haywire ppp[882]: tun0: CCP: mp: State change Closed --> Initial > Dec 29 10:55:56 haywire ppp[882]: tun0: Warning: Del route failed: 0.0.0.0: Non-existent > Dec 29 10:55:56 haywire ppp[882]: tun0: Error: Oops, destroying a datalink in state open > (he's dead jim!) > Dec 29 10:56:19 haywire ppp[882]: tun0: Phase: 1: Connect time: 1112 secs: 533725 octets in, 386209 octets out > Dec 29 10:56:19 haywire ppp[882]: tun0: Phase: total 827 bytes/sec, peak 4972 bytes/sec on Wed Dec 29 10:56:19 1999 > > > -Bryan [.....] > Cheers, > -Peter > -- > Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 16:22:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 7C37F14CFB for ; Wed, 29 Dec 1999 16:22:50 -0800 (PST) (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.9.3/8.9.3) with ESMTP id QAA45237 for ; Wed, 29 Dec 1999 16:22:28 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912300022.QAA45237@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: gcc compiler problem part deux Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 16:22:28 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forgot to post about this new feature of /usr/libexec/cpp : 1. Test file foo.c main() { #ifdef __FreeBSD__ printf("hello\n"); #endif } 1. old freebsd-current 2. gcc -v Using builtin specs. gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) /usr/libexec/cpp foo.c # 1 "foo.c" main() { printf("hello\n"); } /usr/libexec/cpp has __FreeBSD_ defined --- and this is not problem. 2. Now a very recent FreeBSD -current gcc -v Using builtin specs. gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) /usr/libexec/cpp foo.c # 1 "foo.c" main() { } Voila! the "printf " disappeared. This behavior breaks the XFree86 3.9.17 build because the procedure to build imake depends on /usr/libexec/cpp defining __FreeBSD__ I patched locally the imake build so just for FreeBSD it adds a -D__FreeBSD__ I presumed that the latest /usr/libexec/cpp behavior is also going to break other package. Again for me is not a problem because after a few hours I managed to circumvent the new /usr/libexec/cpp feature. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 16:24: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id 20FEE1504F for ; Wed, 29 Dec 1999 16:24:00 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 57253 invoked by uid 1010); 30 Dec 1999 00:24:00 -0000 Date: Thu, 30 Dec 1999 00:24:00 +0000 From: George Cox To: freebsd-current@freebsd.org Subject: make world failure Message-ID: <19991230002400.A57196@extremis.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [cvsupped today :-)] ===> usr.sbin/ifmcstat cc -O -pipe -DINET6 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/i fmcstat/ifmcstat.c gzip -cn /usr/src/usr.sbin/ifmcstat/ifmcstat.8 > ifmcstat.8.gz /usr/src/usr.sbin/ifmcstat/ifmcstat.c: In function `main': /usr/src/usr.sbin/ifmcstat/ifmcstat.c:109: storage size of `arpcom' isn't known Hope this helps someone :-) gjvc -- [gjvc] 4.4BSD 4.ever! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 16:27: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 49879156F9 for ; Wed, 29 Dec 1999 16:26:58 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03126; Wed, 29 Dec 1999 16:31:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912300031.QAA03126@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Amancio Hasty Cc: current@freebsd.org Subject: Re: gcc compiler problem part deux In-reply-to: Your message of "Wed, 29 Dec 1999 16:22:28 PST." <199912300022.QAA45237@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 16:31:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This was discussed weeks ago, and the new behaviour is correct. You should be using 'cc -E' instead. > > Forgot to post about this new feature of /usr/libexec/cpp : > 1. Test file > foo.c > > main() { > #ifdef __FreeBSD__ > printf("hello\n"); > #endif > } > > 1. old freebsd-current > > 2. gcc -v > Using builtin specs. > gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) > > /usr/libexec/cpp foo.c > # 1 "foo.c" > main() { > > printf("hello\n"); > > } > > /usr/libexec/cpp has __FreeBSD_ defined --- and this is not > problem. > > 2. Now a very recent FreeBSD -current > gcc -v > Using builtin specs. > gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) > > /usr/libexec/cpp foo.c > # 1 "foo.c" > > > main() { > > > > } > > Voila! the "printf " disappeared. > > This behavior breaks the XFree86 3.9.17 build because the procedure > to build imake depends on /usr/libexec/cpp defining __FreeBSD__ > > I patched locally the imake build so just for FreeBSD it adds a > -D__FreeBSD__ > > I presumed that the latest /usr/libexec/cpp behavior is also going to > break other package. Again for me is not a problem because > after a few hours I managed to circumvent the new /usr/libexec/cpp > feature. > > -- > > Amancio Hasty > hasty@rah.star-gate.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 16:32:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 139DF14F9A; Wed, 29 Dec 1999 16:32:08 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id TAA17206; Wed, 29 Dec 1999 19:31:41 -0500 (EST) Date: Wed, 29 Dec 1999 19:31:41 -0500 (EST) From: Bosko Milekic To: Amancio Hasty Cc: "Jordan K. Hubbard" , Peter Wemm , Bill Fumerola , obrien@FreeBSD.ORG, Donn Miller , current@FreeBSD.ORG Subject: Re: gcc compile error In-Reply-To: <199912291937.LAA43173@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Dec 1999, Amancio Hasty wrote: !> !>Without -O or -O2 the program compiles okay. !> !>gcc -c bug.c !> Ouch! This looks an awful lot like the last report with `GCC' and `problem' in the subject. As Matt just mentionned one or two posts ago, and as I observed in the last thread, have you tried making some of the variables `volatile?' Assuming of course that the code does compile well without the optimization flags, one would assume that the "problem" occurs because of caching of certain variable values in registers (not that this should be a problem, mind you; one would assume that the optimization isn't performed too well). Due to lack of time, and generally speaking, lack of experience with GCC, I haven't taken a detailed shot at debugging this. Bosko. -- Bosko Milekic Email: bmilekic@dsuper.net WWW: http://pages.infinit.net/bmilekic/ -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 16:49:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 027EC14F67; Wed, 29 Dec 1999 16:49:22 -0800 (PST) (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.9.3/8.9.3) with ESMTP id QAA45447; Wed, 29 Dec 1999 16:48:59 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912300048.QAA45447@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: current@freebsd.org Subject: Re: gcc compiler problem part deux In-reply-to: Your message of "Wed, 29 Dec 1999 16:31:34 PST." <199912300031.QAA03126@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 16:48:59 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are packages such as XFree86 which called directly the installed cpp. Those packages which rely on the old behavior of /usr/libexec/cpp for instance defining __FreeBSD__ are now broken . > > This was discussed weeks ago, and the new behaviour is correct. You > should be using 'cc -E' instead. > > > > > Forgot to post about this new feature of /usr/libexec/cpp : > > 1. Test file > > foo.c > > > > main() { > > #ifdef __FreeBSD__ > > printf("hello\n"); > > #endif > > } > > > > 1. old freebsd-current > > > > 2. gcc -v > > Using builtin specs. > > gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) > > > > /usr/libexec/cpp foo.c > > # 1 "foo.c" > > main() { > > > > printf("hello\n"); > > > > } > > > > /usr/libexec/cpp has __FreeBSD_ defined --- and this is not > > problem. > > > > 2. Now a very recent FreeBSD -current > > gcc -v > > Using builtin specs. > > gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) > > > > /usr/libexec/cpp foo.c > > # 1 "foo.c" > > > > > > main() { > > > > > > > > } > > > > Voila! the "printf " disappeared. > > > > This behavior breaks the XFree86 3.9.17 build because the procedure > > to build imake depends on /usr/libexec/cpp defining __FreeBSD__ > > > > I patched locally the imake build so just for FreeBSD it adds a > > -D__FreeBSD__ > > > > I presumed that the latest /usr/libexec/cpp behavior is also going to > > break other package. Again for me is not a problem because > > after a few hours I managed to circumvent the new /usr/libexec/cpp > > feature. > > -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 16:53:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id D371915105; Wed, 29 Dec 1999 16:53:49 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03485; Wed, 29 Dec 1999 16:58:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912300058.QAA03485@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Amancio Hasty Cc: Mike Smith , current@freebsd.org Subject: Re: gcc compiler problem part deux In-reply-to: Your message of "Wed, 29 Dec 1999 16:48:59 PST." <199912300048.QAA45447@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 16:58:23 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There are packages such as XFree86 which called directly the installed > cpp. Those packages which rely on the old behavior of /usr/libexec/cpp > for instance defining __FreeBSD__ are now broken . XFree86 is trivial to patch, since it already supports this behaviour (see our port), and other applications that expect cpp to define platform-specific symbols have always been broken. > > This was discussed weeks ago, and the new behaviour is correct. You > > should be using 'cc -E' instead. > > > > > > > > Forgot to post about this new feature of /usr/libexec/cpp : -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 17: 2:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id C94E215752 for ; Wed, 29 Dec 1999 17:02:37 -0800 (PST) (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.9.3/8.9.3) with ESMTP id RAA45553; Wed, 29 Dec 1999 17:02:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912300102.RAA45553@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bosko Milekic Cc: current@FreeBSD.ORG Subject: Re: gcc compile error In-reply-to: Your message of "Wed, 29 Dec 1999 19:31:41 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 17:02:11 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We just have a buggy version of gcc and it appears that the register allocator is the main problematic area. This is not really a problem for me because what I first try out is a newer version of gcc if I can not get around the compile problem. At any rate remember that at least my reported compiler bug appears to be fixed in the latest gcc-devel port. > > On Wed, 29 Dec 1999, Amancio Hasty wrote: > > !> > !>Without -O or -O2 the program compiles okay. > !> > !>gcc -c bug.c > !> > > Ouch! This looks an awful lot like the last report with `GCC' and > `problem' in the subject. As Matt just mentionned one or two posts ago, > and as I observed in the last thread, have you tried making some of the > variables `volatile?' Assuming of course that the code does compile well > without the optimization flags, one would assume that the "problem" > occurs because of caching of certain variable values in registers (not > that this should be a problem, mind you; one would assume that the > optimization isn't performed too well). > Due to lack of time, and generally speaking, lack of experience with > GCC, I haven't taken a detailed shot at debugging this. > > Bosko. > > -- > Bosko Milekic > Email: bmilekic@dsuper.net > WWW: http://pages.infinit.net/bmilekic/ > -- > > -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 17: 4:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id AC33214F14; Wed, 29 Dec 1999 17:04:34 -0800 (PST) (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.9.3/8.9.3) with ESMTP id RAA45566; Wed, 29 Dec 1999 17:04:12 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912300104.RAA45566@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: current@freebsd.org Subject: Re: gcc compiler problem part deux In-reply-to: Your message of "Wed, 29 Dec 1999 16:58:23 PST." <199912300058.QAA03485@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 17:04:12 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is more of a question of whether the packages for FreeBSD expect /usr/libexec/cpp to define __FreeBSD__ and in my case XFree86. Once I managed to find out what was wrong it was indeed easy for me to fix. If the "other" applications managed to compile correctly on FreeBSD because of /usr/libexec/cpp then I don't consider them to be broken. > > There are packages such as XFree86 which called directly the installed > > cpp. Those packages which rely on the old behavior of /usr/libexec/cpp > > for instance defining __FreeBSD__ are now broken . > > XFree86 is trivial to patch, since it already supports this behaviour (see > our port), and other applications that expect cpp to define > platform-specific symbols have always been broken. > > > > This was discussed weeks ago, and the new behaviour is correct. You > > > should be using 'cc -E' instead. > > > > > > > > > > > Forgot to post about this new feature of /usr/libexec/cpp : > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 17: 7:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 22F141559B; Wed, 29 Dec 1999 17:07:28 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 20BE41C5D; Wed, 29 Dec 1999 20:06:36 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 1B5823847; Wed, 29 Dec 1999 20:06:36 -0500 (EST) Date: Wed, 29 Dec 1999 20:06:36 -0500 (EST) From: Bill Fumerola To: Amancio Hasty Cc: Mike Smith , current@freebsd.org, rich@FreeBSD.org Subject: Re: gcc compiler problem part deux In-Reply-To: <199912300048.QAA45447@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Dec 1999, Amancio Hasty wrote: > There are packages such as XFree86 which called directly the installed > cpp. Those packages which rely on the old behavior of /usr/libexec/cpp > for instance defining __FreeBSD__ are now broken . ... and they will be fixed through bug reports. We now know what was causing your mishaps with XFree86, this has already been corrected in the port, but you are using the straight source. Perhaps our XFree86 liason can correct this behavior before XFree86 makes a release off of this branch. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 17:11:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [24.234.53.177]) by hub.freebsd.org (Postfix) with ESMTP id E476714FBA for ; Wed, 29 Dec 1999 17:11:10 -0800 (PST) (envelope-from freebsd@mrynet.com) Received: (from freebsd@localhost) by mrynet.com (8.9.3/8.9.3) id RAA47816 for freebsd-current@freebsd.org; Wed, 29 Dec 1999 17:11:05 -0800 (PST) (envelope-from freebsd) Posted-Date: Wed, 29 Dec 1999 17:11:05 -0800 (PST) Message-Id: <199912300111.RAA47816@mrynet.com> From: freebsd@mrynet.com (FreeBSD mailing list) Date: Wed, 29 Dec 1999 17:11:05 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: World fail Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i===> libroken cc -O -pipe -I/usr/src/kerberosIV/lib/libroken/../../../crypto/kerberosIV/include -I/usr/obj/usr/src/kerberosIV/lib/libroken/../../include -I/usr/src/kerberosIV/lib/libroken/../../../crypto/kerberosIV/lib/roken -I/usr/obj/usr/src/kerberosIV/lib/libroken -I/usr/src/kerberosIV/lib/libroken/../../include -Wall -DHAVE_CONFIG_H -I/usr/obj/usr/src/kerberosIV/lib/libroken/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/i386/usr/include -o make-print-version /usr/src/kerberosIV/lib/libroken/../../../crypto/kerberosIV/lib/roken/make-print-version.c /usr/obj/usr/src/i386/usr/libexec/elf/ld: cannot open libgcc.a: No such file or directory *** Error code 1 Stop in /usr/src/kerberosIV/lib/libroken. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 17:13:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 0C28D155A6 for ; Wed, 29 Dec 1999 17:13:13 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id UAA18431 for ; Wed, 29 Dec 1999 20:13:11 -0500 (EST) (envelope-from efutch@nyct.net) Date: Wed, 29 Dec 1999 20:13:11 -0500 (EST) From: "Eric D. Futch" To: freebsd-current@freebsd.org Subject: USB broken? 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 running -current that's about a week old. I configed my kernel for USB support. After turning on the USB interface in BIOS kernel panics after it probes uchi0. Below is the panic screen, I don't have much else to go on. --- uhci0: rev 0x01 int d irq 10 on pci0.7.2> kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0216a34 stack pointer = 0x10:0xc0313e18 frame pointer = 0x10:0xc0313e38 code segment = base 0x0, limit 0xfffff, type 0x16 = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPC = 0 current progess = 0 () interrupt mask = net tty bio cam <- SMP: XXX trap number = 12 panic: page fault mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 --- -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 17:36: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 0224815744 for ; Wed, 29 Dec 1999 17:35:51 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id UAA24381; Wed, 29 Dec 1999 20:39:52 -0500 From: Bill Paul Message-Id: <199912300139.UAA24381@skynet.ctr.columbia.edu> Subject: Re: USB broken? To: efutch@nyct.net (Eric D. Futch) Date: Wed, 29 Dec 1999 20:39:51 -0500 (EST) Cc: current@freebsd.org In-Reply-To: from "Eric D. Futch" at Dec 29, 99 08:13:11 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2523 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Eric D. Futch had to walk into mine and say: > I'm running -current that's about a week old. Erm... are you sure? I'm having trouble believing you. > I configed my kernel for > USB support. After turning on the USB interface in BIOS kernel panics > after it probes uchi0. Below is the panic screen, I don't have much else > to go on. > > --- > uhci0: rev 0x01 int d irq 10 on pci0.7.2> > kernel trap 12 with interrupts disabled See this kernel probe output here? This is not from a 4.0-CURRENT kernel from a week ago. This is what the probe output from a recent -current system should look like: uhci0: irq 11 at device 7.2 on pci0 Notice the difference? It's been like that for a *long* time now. Therefore I can only conclude that either you're not actually running -current, or else you thought it would be okay to substitute in a really stale entry from a system log file from a 3.x system. Either way, you need to re-evaluate the situation and provide more info. Now rather than being vague, go back and show us what uname -a says on this allegedly -current system and show it to us. Show us the *entire* dmesg output too, while you're at it. Furthermore, you should be able to test USB support without recompiling the kernel. All you need to do is kldload usb. That will load the usb.ko kernel module, which should find the UHCI controller. From the panic message you showed here, you're using SMP. Have you tested it with a UP kernel? (Yes, it's supposed to work either way, but it would be nice if you would just test it to rule out some sort of SMP-related condition.) What you should do is this: - Compile a kernel with options DDB, but *WITHOUT* USB support. - Boot this kernel. - Type kldload usb - See if the system crashes. - If it does, it will drop into the debugger. - Type 'trace' - Report what it says. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 17:39:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 1EE15150B4 for ; Wed, 29 Dec 1999 17:39:48 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 8641 invoked from network); 29 Dec 1999 20:39:42 -0000 Received: from lca67.cvzoom.net (HELO cvzoom.net) (63.65.158.67) by ns.cvzoom.net with SMTP; 29 Dec 1999 20:39:42 -0000 Message-ID: <386AB7A8.DC369061@cvzoom.net> Date: Wed, 29 Dec 1999 20:38:48 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Newpcm is broken again for mpg123 (ESS 1868 isa sound card) References: <14429.46098.1195.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14433.63218.157116.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <386278C7.B748EEF5@cvzoom.net> <14434.52947.683451.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14436.13492.839612.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <14439.4177.642029.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14439.26155.338725.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seigo Tanimura wrote: > > On Mon, 27 Dec 1999 16:08:01 +0900, > Seigo Tanimura said: > > Seigo> Another fix was made on feeding and sucking pcm data. Now chn_wrfeed() > Seigo> and the other functions do not attempt excessive feeding during DMA > Seigo> transfer to eat up the whole processor. The patch is at: > > Ouch, the patch broke Rollemup, so I fixed just now. The URI is the same. > > Seigo> http://people.FreeBSD.org/~tanimura/patches/newmidi/2ndbuf-19991227.diff.gz I just recently did another cvsup, and now newpcm is broken again. When I try to play a clip with mpg123, I hear a very short burst of the beginning of the clip repeated indefinitely, like so: "ba ba ba ba ba ba ba ba ba ba ba ba ba ba". I have the ESS 1868, of course. Well, I (wisely) saved my old kernel as /kernel.good and just booted into that. Could you also say what was fixed if you get around to it? I'd to learn a little more about the sound driver. Thanks for your help. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 18:11:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 7DF9914CF8 for ; Wed, 29 Dec 1999 18:11:37 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id VAA25832; Wed, 29 Dec 1999 21:11:28 -0500 (EST) (envelope-from efutch@nyct.net) Date: Wed, 29 Dec 1999 21:11:28 -0500 (EST) From: "Eric D. Futch" To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: USB broken? In-Reply-To: <199912300139.UAA24381@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh hehe damn did it again. Keep getting my lists mixed up. This machine is running 3.4-stable and I should have probably posted this to -stable. Sorry about that... but I really do have 4.0-current running on another machine.. so I'm not totally crazy :) -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Wed, 29 Dec 1999, Bill Paul wrote: Of all the gin joints in all the towns in all the world, Eric D. Futch had to walk into mine and say: > I'm running -current that's about a week old. Erm... are you sure? I'm having trouble believing you. > I configed my kernel for > USB support. After turning on the USB interface in BIOS kernel panics > after it probes uchi0. Below is the panic screen, I don't have much else > to go on. > > --- > uhci0: rev 0x01 int d irq 10 on pci0.7.2> > kernel trap 12 with interrupts disabled See this kernel probe output here? This is not from a 4.0-CURRENT kernel from a week ago. This is what the probe output from a recent -current system should look like: uhci0: irq 11 at device 7.2 on pci0 Notice the difference? It's been like that for a *long* time now. Therefore I can only conclude that either you're not actually running -current, or else you thought it would be okay to substitute in a really stale entry from a system log file from a 3.x system. Either way, you need to re-evaluate the situation and provide more info. Now rather than being vague, go back and show us what uname -a says on this allegedly -current system and show it to us. Show us the *entire* dmesg output too, while you're at it. Furthermore, you should be able to test USB support without recompiling the kernel. All you need to do is kldload usb. That will load the usb.ko kernel module, which should find the UHCI controller. >From the panic message you showed here, you're using SMP. Have you tested it with a UP kernel? (Yes, it's supposed to work either way, but it would be nice if you would just test it to rule out some sort of SMP-related condition.) What you should do is this: - Compile a kernel with options DDB, but *WITHOUT* USB support. - Boot this kernel. - Type kldload usb - See if the system crashes. - If it does, it will drop into the debugger. - Type 'trace' - Report what it says. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 18:45:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24]) by hub.freebsd.org (Postfix) with ESMTP id 8894F14E59 for ; Wed, 29 Dec 1999 18:45:14 -0800 (PST) (envelope-from evmax@earthlink.net) Received: from earthlink.net (sdn-ar-006njnbruP038.dialsprint.net [158.252.44.150]) by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id SAA25971 for ; Wed, 29 Dec 1999 18:45:13 -0800 (PST) Message-ID: <386AC770.800B3012@earthlink.net> Date: Wed, 29 Dec 1999 21:46:08 -0500 From: Maksim Yevmenkin X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: TAP driver for current Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, I've written a small Ethernet TAP driver for FreeBSD-current. It is useful for Ethernet tunneling. I'm using it with VTUN (http://vtun.netpedia.net). The driver sources and description can be found at: http://home.earthlink.net/~evmax/tap-fbsd-current.tar.gz (~8K) It would be realy nice, if some of the commiters review the code and may be add it to the source tree. Thanks, and have a great New Year! emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 18:49: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A736114E50 for ; Wed, 29 Dec 1999 18:49:02 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA14243; Wed, 29 Dec 1999 18:49:02 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA16116; Wed, 29 Dec 1999 18:49:01 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 1999 18:49:01 -0800 From: "David O'Brien" To: Amancio Hasty Cc: current@freebsd.org Subject: Re: gcc compiler problem part deux Message-ID: <19991229184901.A16090@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199912300022.QAA45237@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912300022.QAA45237@rah.star-gate.com>; from hasty@rah.star-gate.com on Wed, Dec 29, 1999 at 04:22:28PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Forgot to post about this new feature of /usr/libexec/cpp : NO ONE should have ever have been using /usr/libexec/cpp directly. I have no idea where this usage came from. /usr/bin/cpp should have been used. > 2. Now a very recent FreeBSD -current > gcc -v > Using builtin specs. > gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) Yes this is very well known, and has been discussed on both Ports and Current several times. A new /usr/bin/ccp is in the works that is a real binary and not the shell script we have today. *IF* world had been buildable today, we would probably have a new /usr/bin/cpp that does everything you want it to. > This behavior breaks the XFree86 3.9.17 build because the procedure > to build imake depends on /usr/libexec/cpp defining __FreeBSD__ So use ``cc -E'' instead. Simple. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 18:54:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 025E31518D for ; Wed, 29 Dec 1999 18:54:31 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA14264; Wed, 29 Dec 1999 18:54:30 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA16137; Wed, 29 Dec 1999 18:54:29 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 1999 18:54:29 -0800 From: "David O'Brien" To: Andy Farkas Cc: current@FreeBSD.ORG Subject: Re: gcc compile error Message-ID: <19991229185429.B16090@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991228171415.B7516@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from andyf@speednet.com.au on Thu, Dec 30, 1999 at 02:40:46AM +1100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 30, 1999 at 02:40:46AM +1100, Andy Farkas wrote: > In file included from include/PortMgr.h:29, > from Connection.cc:33: > include/LevelStat.h:55: invalid type `const char[1]' for default argument > to `const String &' ..snip.. > The "offending" code looks like this: > ostream &print(ostream &os, const String &pfx = "") const; What is the prototype for this function? Hint take a look. You have bad (ie, now invalid by stricter compilers) C++ code. > When I did a 'touch Connection.o ; make' it compiled another source file > that included PortMgr.h / LevelStat.h just fine, but bombed out elsewhere! I can't even fathom what you expected to accomplish by this. Are you a programmer? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 18:55:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 1BBD514DA5; Wed, 29 Dec 1999 18:55:21 -0800 (PST) (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.9.3/8.9.3) with ESMTP id SAA46368; Wed, 29 Dec 1999 18:54:58 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912300254.SAA46368@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@freebsd.org Cc: current@freebsd.org Subject: Re: gcc compiler problem part deux In-reply-to: Your message of "Wed, 29 Dec 1999 18:49:01 PST." <19991229184901.A16090@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 18:54:58 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The usage came about oh about 8 years ago with the very first port of X to 386bsd by yours truly 8) Don't forget I did fix the problem on my X build and I am running the latest XFree86 3.9.xx on my other box. Take Care > > Forgot to post about this new feature of /usr/libexec/cpp : > > NO ONE should have ever have been using /usr/libexec/cpp directly. I > have no idea where this usage came from. /usr/bin/cpp should have been > used. > > > 2. Now a very recent FreeBSD -current > > gcc -v > > Using builtin specs. > > gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) > > Yes this is very well known, and has been discussed on both Ports and > Current several times. A new /usr/bin/ccp is in the works that is a real > binary and not the shell script we have today. > > *IF* world had been buildable today, we would probably have a new > /usr/bin/cpp that does everything you want it to. > > > This behavior breaks the XFree86 3.9.17 build because the procedure > > to build imake depends on /usr/libexec/cpp defining __FreeBSD__ > > So use ``cc -E'' instead. Simple. > > -- > -- David (obrien@NUXI.com) -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 18:58:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C55C714F15 for ; Wed, 29 Dec 1999 18:58:08 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA14279; Wed, 29 Dec 1999 18:58:08 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA16155; Wed, 29 Dec 1999 18:58:08 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 1999 18:58:08 -0800 From: "David O'Brien" To: Amancio Hasty Cc: current@FreeBSD.org Subject: Re: gcc compile error Message-ID: <19991229185808.C16090@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <28389.946493012@zippy.cdrom.com> <199912291937.LAA43173@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912291937.LAA43173@rah.star-gate.com>; from hasty@rah.star-gate.com on Wed, Dec 29, 1999 at 11:37:18AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 29, 1999 at 11:37:18AM -0800, Amancio Hasty wrote: > This is the scoop. ..snip.. > gcc -v > Using builtin specs. > gcc version 2.95.2 19991024 (release) ..snip.. > Without -O or -O2 the program compiles okay. What other platforms w/gcc 2.95 have you tried to build this X11 version on? What other non-Linux platforms w/gcc 2.95 have you tried to build this X11 version on? Do you have a problem if you download the official GCC 2.95.2 release and build it the old GNU'fashion way? Does a purely stock GCC 2.95 bomb on this?? If so, it is a GCC problem and the issue should be raised with Cygnus. > So there appears to be two solutions to get around this problem: ..snip.. 3. Raise this issue with Cygnus. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 19: 4:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 5E43114F9F; Wed, 29 Dec 1999 19:04:10 -0800 (PST) (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.9.3/8.9.3) with ESMTP id TAA46481; Wed, 29 Dec 1999 19:03:47 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912300303.TAA46481@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: gcc compile error In-reply-to: Your message of "Wed, 29 Dec 1999 18:58:08 PST." <19991229185808.C16090@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 19:03:47 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 3. Raise this issue with Cygnus. Not really Cygnus is the wrong organization to raise this issue . As someone else pointed out the gcc-devel port does not exhibit the bug which I posted. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 19: 5:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id CFD3314FC8 for ; Wed, 29 Dec 1999 19:05:30 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id WAA03831 for ; Wed, 29 Dec 1999 22:05:30 -0500 (EST) (envelope-from efutch@nyct.net) Date: Wed, 29 Dec 1999 22:05:29 -0500 (EST) From: "Eric D. Futch" To: freebsd-current@FreeBSD.ORG Subject: Re: USB broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 3.4-stable with source cvsup'd about a week ago. I configed my kernel for USB support. After turning on the USB interface in BIOS kernel panics after it probes uchi0. Below is the panic message plus trace. % uname -a FreeBSD quake.nyct.net 3.4-STABLE FreeBSD 3.4-STABLE #3: Wed Dec 29 21:17:59 EST 1999 efutch@quake.nyct.net:/usr/src/sys/compile/QUAKE i386 --- uhci0: rev 0x01 int d irq 10 on pci0.7.2> kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0216a74 stack pointer = 0x10:0xc0313e18 frame pointer = 0x10:0xc0313e38 code segment = base 0x0, limit 0xfffff, type 0x16 = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPC = 0 current progess = 0 () interrupt mask = net tty bio cam <- SMP: XXX kernel: type 12 trap, code=0 Stopped at INTREN+0x2c: movl %ecx,0(%edx) db> trace INTREN(a,c01fd294,c0da1000,c028d14c,0) at INTREN+0x2c add_intrdesc(c0d93e20,400,c028a2f8,c0da1000,a) at add_intrdesc+0x29 intr_connect(c0d93e20,ffffffff,a,c01fd294,c0da1000,c028d14c,0) at intr_connect+0x2e pci_map_int_right(c0751608,c01fd294,c0da1000,c028d14c,0) at pci_map_int_right+0x31 pci_map_int(c0751608,c01fd294,c0da1000,c028d14c,c0751608,20) at pci_map_int+0x16 uhci_pci_attach(c0751608,0) at uhci_pci_attach+0x75 pci_drvattach(c0751600,c0751600,0,7,c0322f68) at pci_drvattach+0x5f pci_probebus(0,c02637b2,0) at pci_probebus+0x53 pci_probe(0,c0322f98,c0214d70,c0322fac,c014a1f7) at pci_probe+0x39 pci_configure(c0322fac,c014a1f7,0,320c00,326000) at pci_configure+0xa configure(0) at configure+0x20 main(c0322fb8,0,8000,c0161189,c0403000) at main+0x83 begin() at begin+0x55 --- -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 19: 6:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id 68CA215096 for ; Wed, 29 Dec 1999 19:06:11 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id WAA03926 for ; Wed, 29 Dec 1999 22:06:07 -0500 (EST) (envelope-from efutch@nyct.net) Date: Wed, 29 Dec 1999 22:06:06 -0500 (EST) From: "Eric D. Futch" To: freebsd-current@FreeBSD.ORG Subject: Re: USB broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Grr damn... please ignore.. I'm sorry.. not gonna post anything else. -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Wed, 29 Dec 1999, Eric D. Futch wrote: I'm running 3.4-stable with source cvsup'd about a week ago. I configed my kernel for USB support. After turning on the USB interface in BIOS kernel panics after it probes uchi0. Below is the panic message plus trace. % uname -a FreeBSD quake.nyct.net 3.4-STABLE FreeBSD 3.4-STABLE #3: Wed Dec 29 21:17:59 EST 1999 efutch@quake.nyct.net:/usr/src/sys/compile/QUAKE i386 --- uhci0: rev 0x01 int d irq 10 on pci0.7.2> kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0216a74 stack pointer = 0x10:0xc0313e18 frame pointer = 0x10:0xc0313e38 code segment = base 0x0, limit 0xfffff, type 0x16 = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPC = 0 current progess = 0 () interrupt mask = net tty bio cam <- SMP: XXX kernel: type 12 trap, code=0 Stopped at INTREN+0x2c: movl %ecx,0(%edx) db> trace INTREN(a,c01fd294,c0da1000,c028d14c,0) at INTREN+0x2c add_intrdesc(c0d93e20,400,c028a2f8,c0da1000,a) at add_intrdesc+0x29 intr_connect(c0d93e20,ffffffff,a,c01fd294,c0da1000,c028d14c,0) at intr_connect+0x2e pci_map_int_right(c0751608,c01fd294,c0da1000,c028d14c,0) at pci_map_int_right+0x31 pci_map_int(c0751608,c01fd294,c0da1000,c028d14c,c0751608,20) at pci_map_int+0x16 uhci_pci_attach(c0751608,0) at uhci_pci_attach+0x75 pci_drvattach(c0751600,c0751600,0,7,c0322f68) at pci_drvattach+0x5f pci_probebus(0,c02637b2,0) at pci_probebus+0x53 pci_probe(0,c0322f98,c0214d70,c0322fac,c014a1f7) at pci_probe+0x39 pci_configure(c0322fac,c014a1f7,0,320c00,326000) at pci_configure+0xa configure(0) at configure+0x20 main(c0322fb8,0,8000,c0161189,c0403000) at main+0x83 begin() at begin+0x55 --- -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 19: 9:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0F60E1516B for ; Wed, 29 Dec 1999 19:09:53 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA14356; Wed, 29 Dec 1999 19:09:52 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA16224; Wed, 29 Dec 1999 19:09:52 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 1999 19:09:52 -0800 From: "David O'Brien" To: Jonathon McKitrick Cc: current@freebsd.org Subject: Re: question about egcs Message-ID: <19991229190952.F16090@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jcm@dogma.freebsd-uk.eu.org on Wed, Dec 29, 1999 at 02:47:12PM +0000 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Will egcs affect the size of the kernel or any other compiledcode? Verses what other compiler?? Of course the compiler will affect the size of any compiled code. It may do worse, or even better. Various -O values will affect the size too. > I read that the exception code can add a lot to the object size. As will whether the language is C or C++. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 19:12: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9A06014E1D; Wed, 29 Dec 1999 19:12:03 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA14366; Wed, 29 Dec 1999 19:12:03 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA16246; Wed, 29 Dec 1999 19:12:01 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 1999 19:12:01 -0800 From: "David O'Brien" To: Mark Murray Cc: Kris Kennaway , Randy Bush , FreeBSD Current Subject: Re: buildworld failure Message-ID: <19991229191201.G16090@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <199912291857.dBTIvb348299@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912291857.dBTIvb348299@gratis.grondar.za>; from mark@grondar.za on Wed, Dec 29, 1999 at 08:57:33PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 29, 1999 at 08:57:33PM +0200, Mark Murray wrote: > > I don't see the errors below, I see libroken breaking because libgcc.a > can't be found. Can we track this down? Please post the output from cc -print-search-dirs cc -print-libgcc-file-name I also wouldn't mind to see the output from adding "-v" to CFLAGS in /etc/make.conf or somewhere closer to the problem. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 19:19: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7025115123 for ; Wed, 29 Dec 1999 19:19:00 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA14398; Wed, 29 Dec 1999 19:18:59 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA16312; Wed, 29 Dec 1999 19:18:59 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 1999 19:18:59 -0800 From: "David O'Brien" To: Amancio Hasty Cc: current@FreeBSD.org Subject: Re: gcc compile error Message-ID: <19991229191859.Q2130@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19991229185808.C16090@dragon.nuxi.com> <199912300303.TAA46481@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912300303.TAA46481@rah.star-gate.com>; from hasty@rah.star-gate.com on Wed, Dec 29, 1999 at 07:03:47PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 3. Raise this issue with Cygnus. > > Not really Cygnus is the wrong organization to raise this issue . Could you *please* explain why??? Gcc 2.96 will not be out before 4.0. So Gcc 2.95.x is what is going into 4.0. Now should a Gcc 2.95.3 were to come out, then we'd get a new compiler for 4.0. > As someone else pointed out the gcc-devel port does not exhibit the bug > which I posted. Lets think about this in FreeBSD terms -- 4.0 does not have some problem that 3.4-R does. However it wasn't known that 3.4-R had this problem and the reason why 4.0 does not have this problem is due to *tons* of code changes, not necessarily in response to this problem. Now would the FreeBSD Project like to know that there is a problem with 3.4-R that isn't in 4.0 along with a test case to show the problem? Would the FreeBSD Project, maybe just maybe be interested in fixing the problem and releasing a 3.5-R? Just like FreeBSD, EGCS has two code branches. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 19:29:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D76E315047 for ; Wed, 29 Dec 1999 19:29:56 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA14456; Wed, 29 Dec 1999 19:29:56 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA16443; Wed, 29 Dec 1999 19:29:55 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 1999 19:29:55 -0800 From: "David O'Brien" To: Andy Farkas Cc: current@freebsd.org Subject: Re: gcc compile error Message-ID: <19991229192954.R2130@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <19991229185429.B16090@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from andyf@speednet.com.au on Thu, Dec 30, 1999 at 02:21:48PM +1100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 30, 1999 at 02:21:48PM +1100, Andy Farkas wrote: > ...the idea was to continue the make process further along to where > another source file that also included LevelStat.h got compiled, to > check whether it bombs as well - it didn't. ``make -k'' might have been a better choice as you don't have to remember to rm the fake .o later. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 19:43:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 66B9014D3A for ; Wed, 29 Dec 1999 19:43:35 -0800 (PST) (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.9.3/8.9.3) with ESMTP id TAA46835; Wed, 29 Dec 1999 19:43:07 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912300343.TAA46835@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@NUXI.com Cc: current@FreeBSD.org Subject: Re: gcc compile error In-reply-to: Your message of "Wed, 29 Dec 1999 19:18:59 PST." <19991229191859.Q2130@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 19:43:07 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Gcc 2.96 will not be out before 4.0. So Gcc 2.95.x is what is going into >4.0. Now should a Gcc 2.95.3 were to come out, then we'd get a new >compiler for 4.0. >Lets think about this in FreeBSD terms -- 4.0 does not have some problem >that 3.4-R does. However it wasn't known that 3.4-R had this problem and Hi, I am running FreeBSD -current and I got no clue as to what is going on FreeBSD 3.xxx. The problem was reported for FreeBSD -current. Okay, lets hope that gcc 2.9.53 comes out before the release of FreeBSD 4.0. Take Care -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 20: 2:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id DCF9114ED2 for ; Wed, 29 Dec 1999 20:02:33 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id UAA15343; Wed, 29 Dec 1999 20:02:33 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 1999 20:02:32 -0800 From: "David O'Brien" To: Amancio Hasty Cc: current@FreeBSD.org Subject: Re: gcc compile error Message-ID: <19991229200232.A14403@relay.nuxi.com> Reply-To: obrien@FreeBSD.org References: <19991229191859.Q2130@dragon.nuxi.com> <199912300343.TAA46835@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <199912300343.TAA46835@rah.star-gate.com> X-Operating-System: FreeBSD 3.3-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 On Wed, Dec 29, 1999 at 07:43:07PM -0800, Amancio Hasty wrote: > >Gcc 2.96 will not be out before 4.0. So Gcc 2.95.x is what is going into > >4.0. Now should a Gcc 2.95.3 were to come out, then we'd get a new > >compiler for 4.0. > > >Lets think about this in FreeBSD terms -- 4.0 does not have some problem > >that 3.4-R does. However it wasn't known that 3.4-R had this problem and > I am running FreeBSD -current and I got no clue as to what is I *REALIZE* THAT. I was making an _analogy_. > The problem was reported for FreeBSD -current. The problem most likely needs to be reported for GCC 2.95, *NOT* FreeBSD. > Okay, lets hope that gcc 2.9.53 comes out before the release of FreeBSD 4.0. Not unless someone like you gets involved and files a bug report with Cygnus. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 20:25:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 89B3A14D29; Wed, 29 Dec 1999 20:25:10 -0800 (PST) (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.9.3/8.9.3) with ESMTP id UAA47144; Wed, 29 Dec 1999 20:24:47 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912300424.UAA47144@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: gcc compile error In-reply-to: Your message of "Wed, 29 Dec 1999 20:02:32 PST." <19991229200232.A14403@relay.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 20:24:47 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi David, Last time, the problem does not exist with the gcc-devel port which directly implies that the problem has been fixed so I see no point on reporting the bug to Cygnus. I can in the future report the bug to Cygnus if the bug has not been fixed in a subsequent snapshot. I will play with gcc-devel some tonite to see if I can use it for all my ports. Some background: I am working on XFree86 to help bring about yuv + scaling hardware support -- my main priority is X for I if get too side tracked I may miss my window of opportunity to hack . Take Care -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 20:44:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from koke.nibb.ac.jp (koke.nibb.ac.jp [133.48.46.82]) by hub.freebsd.org (Postfix) with ESMTP id ED8D914D9B; Wed, 29 Dec 1999 20:44:13 -0800 (PST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) Received: from localhost (koke.nibb.ac.jp [127.0.0.1]) by koke.nibb.ac.jp (8.9.3/8.9.3) with ESMTP id NAA33783; Thu, 30 Dec 1999 13:44:06 +0900 (JST) (envelope-from tomoaki@biol.s.u-tokyo.ac.jp) To: freebsd-current@freebsd.org Cc: tomoaki@biol.s.u-tokyo.ac.jp Cc: obrien@freebsd.org Subject: _T defined in ctype.h collides with c++ library From: Tomoaki NISHIYAMA X-Mailer: Mew version 1.94.2pre3 on XEmacs 21.1 (Big Bend) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991230134406M.tomoaki@koke.nibb.ac.jp> Date: Thu, 30 Dec 1999 13:44:06 +0900 X-Dispatcher: imput version 991025(IM133) Lines: 25 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I reported this issue as PR misc/15127, and posted once to hackers but get no response at all. In FreeBSD, _T and other two letter macros are defined in ctype.h. Some standard c++ library code use _T as local identifiers. I mean the library that come with egcs-2.95.[12] and 2.96 191110. /usr/include/g++/typemacros.h also defines _T. (in 3.3R, I'm not sure on later versions) So, I feel better to remove these two character defines from ctype.h. This procedure would involve also change the code in src/lib/libc/locale/{ctype,table}.c Substitute _T with _CTYPE_T in ctype.h and #define _T _CTYPE_T in src/lib/libc/locale/{ctype,table}.c would reduce the undocumented global namespace pollution. What do you think of this? Is this worth doing, or you won't change that, or any better way to go? I think that the c++ library should not use _T anyway, and the use of _T is reported to libstdc++-v3 group with PR #19. The usage of _T is not very few and I'm not sure I found all of them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 20:54:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 0EE2C1515F for ; Wed, 29 Dec 1999 20:54:57 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id VAA03134 for ; Wed, 29 Dec 1999 21:53:19 -0700 (MST) Received: from ip-83-110.prc.primenet.com(207.218.83.110), claiming to be "pinyon.org" via SMTP by smtp04.primenet.com, id smtpdAAAl6aagg; Wed Dec 29 21:53:10 1999 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id E299E40 for ; Wed, 29 Dec 1999 21:54:42 -0700 (MST) X-Mailer: exmh version 2.1.0 09/18/1999 To: current@freebsd.org Subject: -current buildworld dies, retch. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Dec 1999 21:54:42 -0700 From: "Russell L. Carter" Message-Id: <19991230045442.E299E40@pinyon.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Otay, please tell me how to fix: ===> usr.sbin/ifmcstat cc -O -pipe -DINET6 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/ifmcstat/ifmcstat.c gzip -cn /usr/src/usr.sbin/ifmcstat/ifmcstat.8 > ifmcstat.8.gz /usr/src/usr.sbin/ifmcstat/ifmcstat.c: In function `main': /usr/src/usr.sbin/ifmcstat/ifmcstat.c:109: storage size of `arpcom' isn't known I have for the last 12h: 1. retried cvsup'ing build; sleep (2x3600); 2. rm -rf /usr/src ; cvsup standard-supfile ; cd /usr/src ; make world Thanks, Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 21:17:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from dns.lopezgachuz.com.mx (lopezgachuz.com.mx [148.245.50.34]) by hub.freebsd.org (Postfix) with ESMTP id B006414D3A for ; Wed, 29 Dec 1999 21:17:37 -0800 (PST) (envelope-from jabc@moz.com.mx) Received: from moz.com.mx (dns [192.168.1.1]) by dns.lopezgachuz.com.mx (8.9.3/8.9.3) with ESMTP id XAA98192 for ; Wed, 29 Dec 1999 23:17:29 -0600 (CST) (envelope-from jabc@moz.com.mx) Message-ID: <386AEAE9.E4E7702@moz.com.mx> Date: Wed, 29 Dec 1999 23:17:29 -0600 From: juan X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current Subject: make world broken Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I tried to compile my world this fail... I'm Running FreeBSD 4.0-CURRENT. sh /usr/src/tools/install.sh -c -o root -g wheel -m 555 /usr/src/usr.bin/yacc/yyfix.sh /usr/obj/usr/src/i386/usr/bin/yyfix sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 555 yacc /usr/obj/usr/src/i386/usr/bin /usr/obj/usr/src/i386/usr/bin/byacc -> /usr/obj/usr/src/i386/usr/bin/yacc cd /usr/src/usr.bin/colldef; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/usr.bin/colldef created for /usr/src/usr.bin/colldef yacc -d /usr/src/usr.bin/colldef/parse.y *** Signal 12 Stop in /usr/src/usr.bin/colldef. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Any Idea ? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 21:20:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 736BA14C4F for ; Wed, 29 Dec 1999 21:20:41 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA89364; Thu, 30 Dec 1999 15:50:31 +1030 (CST) Date: Thu, 30 Dec 1999 15:50:31 +1030 From: Greg Lehey To: juan Cc: current Subject: Re: make world broken Message-ID: <19991230155030.B1316@freebie.lemis.com> References: <386AEAE9.E4E7702@moz.com.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <386AEAE9.E4E7702@moz.com.mx> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Wednesday, 29 December 1999 at 23:17:29 -0600, juan wrote: > When I tried to compile my world this fail... > > I'm Running FreeBSD 4.0-CURRENT. What date? > /usr/obj/usr/src/i386/usr/src/usr.bin/colldef created for > /usr/src/usr.bin/colldef > yacc -d /usr/src/usr.bin/colldef/parse.y > *** Signal 12 This looks like you've updated your source tree and have not built a new kernel. Try the new kernel first, then the buildworld. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 21:31:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 7897014C1D; Wed, 29 Dec 1999 21:31:09 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBU5V5350644; Thu, 30 Dec 1999 07:31:05 +0200 (SAST) Message-Id: <199912300531.dBU5V5350644@gratis.grondar.za> To: obrien@freebsd.org Cc: Kris Kennaway , Randy Bush , FreeBSD Current Subject: Re: buildworld failure References: <19991229191201.G16090@dragon.nuxi.com> In-Reply-To: <19991229191201.G16090@dragon.nuxi.com> ; from "David O'Brien" "Wed, 29 Dec 1999 19:12:01 PST." Date: Thu, 30 Dec 1999 07:31:05 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Dec 29, 1999 at 08:57:33PM +0200, Mark Murray wrote: > > > > I don't see the errors below, I see libroken breaking because libgcc.a > > can't be found. > > Can we track this down? Please post the output from > > cc -print-search-dirs > cc -print-libgcc-file-name I found it - its a binary that is used only during the build to construct a header file. Marcel is helping me sort it out. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 29 22:26:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 3C21B1500F for ; Wed, 29 Dec 1999 22:26:45 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA03457; Thu, 30 Dec 1999 16:56:35 +1030 (CST) Date: Thu, 30 Dec 1999 16:56:35 +1030 From: Greg Lehey To: "Russell L. Carter" Cc: current@FreeBSD.ORG Subject: Re: -current buildworld dies, retch. Message-ID: <19991230165635.E1316@freebie.lemis.com> References: <19991230045442.E299E40@pinyon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991230045442.E299E40@pinyon.org> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Wednesday, 29 December 1999 at 21:54:42 -0700, Russell L. Carter wrote: > > Otay, please tell me how to fix: > > ===> usr.sbin/ifmcstat > cc -O -pipe -DINET6 -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/usr.sbin/ifmcstat/ifmcstat.c > gzip -cn /usr/src/usr.sbin/ifmcstat/ifmcstat.8 > ifmcstat.8.gz > /usr/src/usr.sbin/ifmcstat/ifmcstat.c: In function `main': > /usr/src/usr.sbin/ifmcstat/ifmcstat.c:109: storage size of `arpcom' isn't known I think for this one you need to find who broke it and make him unbreak it. You may supply a pointy hat. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 0:14:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta3.snfc21.pbi.net (mta3.snfc21.pbi.net [206.13.28.141]) by hub.freebsd.org (Postfix) with ESMTP id 4D389150F8 for ; Thu, 30 Dec 1999 00:14:55 -0800 (PST) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net ([207.214.211.20]) by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FNJ0030PO875M@mta3.snfc21.pbi.net> for current@freebsd.org; Thu, 30 Dec 1999 00:14:43 -0800 (PST) Date: Thu, 30 Dec 1999 00:14:30 -0800 From: "George W. Dinolt" Subject: Re: -current buildworld dies, retch. To: current@freebsd.org Message-id: <386B1466.FAE3D68B@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Otay, please tell me how to fix: > > ===> usr.sbin/ifmcstat > cc -O -pipe -DINET6 -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/usr.sbin/ifmcstat/ifmcstat.c > gzip -cn /usr/src/usr.sbin/ifmcstat/ifmcstat.8 > ifmcstat.8.gz > /usr/src/usr.sbin/ifmcstat/ifmcstat.c: In function `main': > /usr/src/usr.sbin/ifmcstat/ifmcstat.c:109: storage size of `arpcom' isn't known It appears that in the change from "KERNEL" to "_KERNEL" the usage was not updated in ifmcstat.c. The following patch appears to fix the problem, (I just completed a make world) and ifmcstat seems to work. ------------------ diff -c ifmcstat-old/ifmcstat.c ifmcstat/ifmcstat.c *** ifmcstat-old/ifmcstat.c Wed Dec 29 19:26:58 1999 --- ifmcstat/ifmcstat.c Wed Dec 29 21:59:06 1999 *************** *** 48,58 **** #include #ifndef __NetBSD__ # ifdef __FreeBSD__ ! # define KERNEL # endif # include # ifdef __FreeBSD__ ! # undef KERNEL # endif #else # include --- 48,58 ---- #include #ifndef __NetBSD__ # ifdef __FreeBSD__ ! # define _KERNEL # endif # include # ifdef __FreeBSD__ ! # undef _KERNEL # endif #else # include To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 1:24: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id D56A315243; Thu, 30 Dec 1999 01:24:06 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 42BEA1CC6; Thu, 30 Dec 1999 17:23:52 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: obrien@FreeBSD.org Cc: Amancio Hasty , current@FreeBSD.org Subject: Re: gcc compile error In-Reply-To: Message from "David O'Brien" of "Wed, 29 Dec 1999 18:58:08 PST." <19991229185808.C16090@dragon.nuxi.com> Date: Thu, 30 Dec 1999 17:23:52 +0800 From: Peter Wemm Message-Id: <19991230092352.42BEA1CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > On Wed, Dec 29, 1999 at 11:37:18AM -0800, Amancio Hasty wrote: > > This is the scoop. > ..snip.. > > gcc -v > > Using builtin specs. > > gcc version 2.95.2 19991024 (release) > ..snip.. > > Without -O or -O2 the program compiles okay. > > What other platforms w/gcc 2.95 have you tried to build this X11 version > on? What other non-Linux platforms w/gcc 2.95 have you tried to build > this X11 version on? Do you have a problem if you download the official > GCC 2.95.2 release and build it the old GNU'fashion way? Does a purely > stock GCC 2.95 bomb on this?? If so, it is a GCC problem and the issue > should be raised with Cygnus. Yes it is a gcc-2.95.2 bug. It's fixed in the 2.96 snapshot in ports/lang/gcc-devel. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 1:32: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 5D57A14D0E for ; Thu, 30 Dec 1999 01:32:01 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 565291CA0; Thu, 30 Dec 1999 17:31:54 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Lehey Cc: "Russell L. Carter" , current@FreeBSD.ORG Subject: Re: -current buildworld dies, retch. In-Reply-To: Message from Greg Lehey of "Thu, 30 Dec 1999 16:56:35 +1030." <19991230165635.E1316@freebie.lemis.com> Date: Thu, 30 Dec 1999 17:31:54 +0800 From: Peter Wemm Message-Id: <19991230093154.565291CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Wednesday, 29 December 1999 at 21:54:42 -0700, Russell L. Carter wrote: > > > > Otay, please tell me how to fix: > > > > ===> usr.sbin/ifmcstat > > cc -O -pipe -DINET6 -I/usr/obj/usr/src/i386/usr/include -c > > /usr/src/usr.sbin/ifmcstat/ifmcstat.c > > gzip -cn /usr/src/usr.sbin/ifmcstat/ifmcstat.8 > ifmcstat.8.gz > > /usr/src/usr.sbin/ifmcstat/ifmcstat.c: In function `main': > > /usr/src/usr.sbin/ifmcstat/ifmcstat.c:109: storage size of `arpcom' isn't k nown > > I think for this one you need to find who broke it and make him > unbreak it. You may supply a pointy hat. Heh, there was a crossover of commits. I did my sweep about 36 hours before the commit and was cvs updating it as I went. It seems ifmcstat got added after the sweep, but wasn't connected to the makefile. I did actually do a 'make world' immediately prior to the commit, and ifmcstat was added to usr.sbin/Makefile after the conversion which broke the build. date: 1999/12/28 02:37:05; author: shin; state: Exp; Getaddrinfo(), getnameinfo(), and etc support in libc/net. Several udp and raw apps IPv6 support. date: 1999/12/29 04:24:49; author: peter; state: Exp; lines: +7 -7 Change #ifdef KERNEL to #ifdef _KERNEL in the public headers. date: 1999/12/29 07:11:50; author: shin; state: Exp; lines: +9 -1 Forgot to add newly added udp and raw IPv6 apps to usr.sbin SUBDIR. They are confirmed to be buildable and seems to be working. This is an example of the pitfalls of parallel development. 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 Dec 30 1:38:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id C9DF014FB1; Thu, 30 Dec 1999 01:38:35 -0800 (PST) (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.9.3/8.9.3) with ESMTP id BAA49705; Thu, 30 Dec 1999 01:37:41 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912300937.BAA49705@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm Cc: obrien@FreeBSD.org, current@FreeBSD.org Subject: Re: gcc compile error In-reply-to: Your message of "Thu, 30 Dec 1999 17:23:52 +0800." <19991230092352.42BEA1CC6@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 01:37:41 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "David O'Brien" wrote: > > On Wed, Dec 29, 1999 at 11:37:18AM -0800, Amancio Hasty wrote: > > > This is the scoop. > > ..snip.. > > > gcc -v > > > Using builtin specs. > > > gcc version 2.95.2 19991024 (release) > > ..snip.. > > > Without -O or -O2 the program compiles okay. > > > > What other platforms w/gcc 2.95 have you tried to build this X11 version > > on? What other non-Linux platforms w/gcc 2.95 have you tried to build > > this X11 version on? Do you have a problem if you download the official > > GCC 2.95.2 release and build it the old GNU'fashion way? Does a purely > > stock GCC 2.95 bomb on this?? If so, it is a GCC problem and the issue > > should be raised with Cygnus. > > Yes it is a gcc-2.95.2 bug. It's fixed in the 2.96 snapshot in > ports/lang/gcc-devel. > Yeap, gcc-devel installed from the ports directory: gcc -v Reading specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd4.0/2.96/specs gcc version 2.96 19991110 (experimental) {root} gcc -c -O2 bug.c That is as Peter said the bug is fixed on the 2.96 snapshot and I am currently rebuilding X on my other system will find out more when the build finishes in about 1/2 hour. Take Care -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 3:12:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 3C0CF150F1 for ; Thu, 30 Dec 1999 03:12:16 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id MAA21639 for current@FreeBSD.org; Thu, 30 Dec 1999 12:10:39 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 30 Dec 1999 12:10:33 +0100 From: Marcel Moolenaar Message-ID: <386B3DA9.29AB4153@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <199912300111.RAA47816@mrynet.com> Subject: Re: World fail Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD mailing list wrote: > > i===> libroken > cc -O -pipe -I/usr/src/kerberosIV/lib/libroken/../../../crypto/kerberosIV/include -I/usr/obj/usr/src/kerberosIV/lib/libroken/../../include -I/usr/src/kerberosIV/lib/libroken/../../../crypto/kerberosIV/lib/roken -I/usr/obj/usr/src/kerberosIV/lib/libroken -I/usr/src/kerberosIV/lib/libroken/../../include -Wall -DHAVE_CONFIG_H -I/usr/obj/usr/src/kerberosIV/lib/libroken/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/i386/usr/include -o make-print-version /usr/src/kerberosIV/lib/libroken/../../../crypto/kerberosIV/lib/roken/make-print-version.c > /usr/obj/usr/src/i386/usr/libexec/elf/ld: cannot open libgcc.a: No such file or directory > *** Error code 1 Fixed, thanks. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 3:42:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 98AB514E49 for ; Thu, 30 Dec 1999 03:42:16 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id MAA23163 for current@FreeBSD.org; Thu, 30 Dec 1999 12:16:30 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 30 Dec 1999 12:16:28 +0100 From: Marcel Moolenaar Message-ID: <386B3F0C.6A1B4461@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <386AEAE9.E4E7702@moz.com.mx> Subject: Re: make world broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG juan wrote: > > yacc -d /usr/src/usr.bin/colldef/parse.y > *** Signal 12 > > Stop in /usr/src/usr.bin/colldef. Are you doing anything special? If not, try cleaning /usr/obj first and make sure your source tree is ok. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 3:42:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id D5C9A1515F for ; Thu, 30 Dec 1999 03:42:18 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id MAA22877 for current@FreeBSD.org; Thu, 30 Dec 1999 12:15:07 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Thu, 30 Dec 1999 12:15:03 +0100 From: Marcel Moolenaar Message-ID: <386B3EB7.15025D0B@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <386AEAE9.E4E7702@moz.com.mx>, <19991230155030.B1316@freebie.lemis.com> Subject: Re: make world broken Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > > /usr/obj/usr/src/i386/usr/src/usr.bin/colldef created for > > /usr/src/usr.bin/colldef > > yacc -d /usr/src/usr.bin/colldef/parse.y > > *** Signal 12 > > This looks like you've updated your source tree and have not built a > new kernel. Try the new kernel first, then the buildworld. This is not a problem anymore, because we don't execute anything that is compiled against the new sources. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 4:34:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-77.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.205]) by hub.freebsd.org (Postfix) with ESMTP id 000DF14DF6 for ; Thu, 30 Dec 1999 04:34:16 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id EAA43028; Thu, 30 Dec 1999 04:24:57 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id EAA15649; Thu, 30 Dec 1999 04:27:31 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912300427.EAA15649@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Werner Griessl Cc: current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: broken ppp In-Reply-To: Message from Werner Griessl of "Wed, 29 Dec 1999 09:03:56 +0100." <199912290803.JAA17904@btp1da.phy.uni-bayreuth.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 04:27:30 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > current's new ppp discards the "#0001"-part from my > german telekom account and makes it impossible to > connect to my provider. This should work ok now. Sorry for the inconvenience. > It worked ~ 2 weeks ago with current and works also > in 3.4-Stable. > > Werner -- 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 Thu Dec 30 5:24:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id EFF671530A for ; Thu, 30 Dec 1999 05:24:30 -0800 (PST) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 123fZk-000G7C-00; Thu, 30 Dec 1999 08:25:08 -0500 To: Greg Lehey Cc: current@freebsd.org From: Gary Palmer Subject: Re: ``how to'' for Vinum and mirroring after the volume was created? In-reply-to: Your message of "Mon, 27 Dec 1999 13:35:07 +1030." <19991227133507.X1316@freebie.lemis.com> Date: Thu, 30 Dec 1999 08:25:07 -0500 Message-ID: <61949.946560307@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote in message ID <19991227133507.X1316@freebie.lemis.com>: > Again, news for me. You can stop a revive and restart it at a later > time; the state information includes the revive pointer. But the only > real answer to this one would be to see the statistics. Well, I deleted the plex and tried again: root@ohno:~> cat /root/vinum_conf plex name vol01.p1 org concat sd name vol01.p1.s0 length 0 drive d1 root@ohno:~> vinum create /root/vinum_conf 2 drives: D d0 State: up Device /dev/ad4f Avail: 0/35669 MB (0%) D d1 State: up Device /dev/ad6f Avail: 0/35669 MB (0%) 1 volumes: V vol01 State: up Plexes: 1 Size: 34 GB 2 plexes: P vol01.p0 C State: up Subdisks: 1 Size: 34 GB P vol01.p1 C State: up Subdisks: 1 Size: 34 GB 2 subdisks: S vol01.p0.s0 State: up PO: 0 B Size: 34 GB S vol01.p1.s0 State: up PO: 0 B Size: 34 GB root@ohno:~> vinum attach vol01.p1 vol01 Can't attach vol01.p1 to vol01: a (1) thats weird root@ohno:~> vinum printconfig # Vinum configuration of ohno.home.in-addr.com, saved at Thu Dec 30 08:04:40 1999 drive d0 device /dev/ad4f drive d1 device /dev/ad6f volume vol01 plex name vol01.p0 org concat vol vol01 plex name vol01.p1 org concat vol vol01 sd name vol01.p0.s0 drive d0 plex vol01.p0 len 73051272s driveoffset 265s plexoffset 0s sd name vol01.p1.s0 drive d1 plex vol01.p1 len 73051272s driveoffset 265s plexoffset 0s root@ohno:~> vinum l -v 2 drives: Drive d0: Device /dev/ad4f Created on ohno.home.in-addr.com at Fri Dec 24 10:08:55 1999 Config last updated Thu Dec 30 08:04:29 1999 Size: 37402386944 bytes (35669 MB) Used: 37402386944 bytes (35669 MB) Available: 0 bytes (0 MB) State: up Last error: none Active requests: 0 Maximum active: 10 Drive d1: Device /dev/ad6f Created on ohno.home.in-addr.com at Sat Dec 25 16:39:24 1999 Config last updated Thu Dec 30 08:04:29 1999 Size: 37402386944 bytes (35669 MB) Used: 37402386944 bytes (35669 MB) Available: 0 bytes (0 MB) State: up Last error: none Active requests: 0 Maximum active: 2 1 volumes: Volume vol01: Size: 37402251264 bytes (35669 MB) State: up Flags: open 2 plexes Read policy: round robin 2 plexes: Plex vol01.p0: Size: 37402251264 bytes (35669 MB) Subdisks: 1 State: up Organization: concat Part of volume vol01 Plex vol01.p1: Size: 37402251264 bytes (35669 MB) Subdisks: 1 State: faulty Organization: concat Part of volume vol01 2 subdisks: Subdisk vol01.p0.s0: Size: 37402251264 bytes (35669 MB) State: up Plex vol01.p0 at offset 0 (0 B) Drive d0 (/dev/ad4f) at offset 135680 (132 kB) Subdisk vol01.p1.s0: Size: 37402251264 bytes (35669 MB) State: stale Plex vol01.p1 at offset 0 (0 B) Drive d1 (/dev/ad6f) at offset 135680 (132 kB) root@ohno:~> vinum resetstats root@ohno:~> vinum lp -s vol01.p0 0 0 0 0 0 0 0 vol01.p1 0 0 0 0 0 0 0 root@ohno:~> vinum start vol01.p1 Reviving vol01.p1.s0 in the background root@ohno:~> vinum[49356]: reviving vol01.p1.s0 Worked that time. Dunno what the difference was. root@ohno:~> vinum l -v 2 drives: Drive d0: Device /dev/ad4f Created on ohno.home.in-addr.com at Fri Dec 24 10:08:55 1999 Config last updated Thu Dec 30 08:09:15 1999 Size: 37402386944 bytes (35669 MB) Used: 37402386944 bytes (35669 MB) Available: 0 bytes (0 MB) State: up Last error: none Active requests: 1 Maximum active: 10 Drive d1: Device /dev/ad6f Created on ohno.home.in-addr.com at Sat Dec 25 16:39:24 1999 Config last updated Thu Dec 30 08:09:15 1999 Size: 37402386944 bytes (35669 MB) Used: 37402386944 bytes (35669 MB) Available: 0 bytes (0 MB) State: up Last error: none Active requests: 0 Maximum active: 2 1 volumes: Volume vol01: Size: 37402251264 bytes (35669 MB) State: up Flags: 2 plexes Read policy: round robin 2 plexes: Plex vol01.p0: Size: 37402251264 bytes (35669 MB) Subdisks: 1 State: up Organization: concat Part of volume vol01 Plex vol01.p1: Size: 37402251264 bytes (35669 MB) Subdisks: 1 State: faulty Organization: concat Part of volume vol01 2 subdisks: Subdisk vol01.p0.s0: Size: 37402251264 bytes (35669 MB) State: up Plex vol01.p0 at offset 0 (0 B) Drive d0 (/dev/ad4f) at offset 135680 (132 kB) Subdisk vol01.p1.s0: Size: 37402251264 bytes (35669 MB) State: reviving Plex vol01.p1 at offset 0 (0 B) Revive pointer: 7344 kB (0%) Revive blocksize: 16 kB Revive interval: 0 seconds Drive d1 (/dev/ad6f) at offset 135680 (132 kB) root@ohno:~> vinum ls -sv Subdisk vol01.p0.s0: Size: 37402251264 bytes (35669 MB) State: up Plex vol01.p0 at offset 0 (0 B) Drive d0 (/dev/ad4f) at offset 135680 (132 kB) Reads: 5896 Bytes read: 96600064 (92 MB) Average read: 16384 bytes Writes: 0 Bytes written: 0 (0 B) Subdisk vol01.p1.s0: Size: 37402251264 bytes (35669 MB) State: reviving Plex vol01.p1 at offset 0 (0 B) Revive pointer: 184 MB (0%) Revive blocksize: 16 kB Revive interval: 0 seconds Drive d1 (/dev/ad6f) at offset 135680 (132 kB) Reads: 5895 Bytes read: 96583680 (92 MB) Average read: 16384 bytes Writes: 11791 Bytes written: 193183744 (184 MB) Average write: 16384 bytes As you can see, the revive pointer is at 184MB, but only 92MB has been read from the `good' plex, the other 92MB has been taken from the `bad' plex. It really looks like its round robining the reads like it would if it was a fully silvered mirror. The full config and stats: root@ohno:~> vinum printconfig # Vinum configuration of ohno.home.in-addr.com, saved at Thu Dec 30 08:22:19 1999 drive d0 device /dev/ad4f drive d1 device /dev/ad6f volume vol01 plex name vol01.p0 org concat vol vol01 plex name vol01.p1 org concat vol vol01 sd name vol01.p0.s0 drive d0 plex vol01.p0 len 73051272s driveoffset 265s plexoffset 0s sd name vol01.p1.s0 drive d1 plex vol01.p1 len 73051272s driveoffset 265s plexoffset 0s root@ohno:~> vinum l -sv 2 drives: Drive d0: Device /dev/ad4f Created on ohno.home.in-addr.com at Fri Dec 24 10:08:55 1999 Config last updated Thu Dec 30 08:09:15 1999 Size: 37402386944 bytes (35669 MB) Used: 37402386944 bytes (35669 MB) Available: 0 bytes (0 MB) State: up Last error: none Active requests: 0 Maximum active: 10 Reads: 17690 Bytes read: 289832960 (276 MB) Average read: 16384 bytes Writes: 0 Bytes written: 0 (0 B) Drive d1: Device /dev/ad6f Created on ohno.home.in-addr.com at Sat Dec 25 16:39:24 1999 Config last updated Thu Dec 30 08:09:15 1999 Size: 37402386944 bytes (35669 MB) Used: 37402386944 bytes (35669 MB) Available: 0 bytes (0 MB) State: up Last error: none Active requests: 1 Maximum active: 2 Reads: 17689 Bytes read: 289816576 (276 MB) Average read: 16384 bytes Writes: 35379 Bytes written: 579649536 (552 MB) Average write: 16384 bytes 1 volumes: Volume vol01: Size: 37402251264 bytes (35669 MB) State: up Flags: 2 plexes Read policy: round robin Reads: 35380 Recovered: 0 Bytes read: 579665920 (552 MB) Average read: 16384 bytes Writes: 0 Bytes written: 0 (0 B) Active requests: 1 2 plexes: Plex vol01.p0: Size: 37402251264 bytes (35669 MB) Subdisks: 1 State: up Organization: concat Part of volume vol01 Reads: 17690 Bytes read: 289832960 (276 MB) Average read: 16384 bytes Writes: 0 Bytes written: 0 (0 B) Plex vol01.p1: Size: 37402251264 bytes (35669 MB) Subdisks: 1 State: faulty Organization: concat Part of volume vol01 Reads: 17689 Bytes read: 289816576 (276 MB) Average read: 16384 bytes Writes: 0 Bytes written: 0 (0 B) 2 subdisks: Subdisk vol01.p0.s0: Size: 37402251264 bytes (35669 MB) State: up Plex vol01.p0 at offset 0 (0 B) Drive d0 (/dev/ad4f) at offset 135680 (132 kB) Reads: 17690 Bytes read: 289832960 (276 MB) Average read: 16384 bytes Writes: 0 Bytes written: 0 (0 B) Subdisk vol01.p1.s0: Size: 37402251264 bytes (35669 MB) State: reviving Plex vol01.p1 at offset 0 (0 B) Revive pointer: 552 MB (1%) Revive blocksize: 16 kB Revive interval: 0 seconds Drive d1 (/dev/ad6f) at offset 135680 (132 kB) Reads: 17689 Bytes read: 289816576 (276 MB) Average read: 16384 bytes Writes: 35379 Bytes written: 579649536 (552 MB) Average write: 16384 bytes Any ideas? Thanks, Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 7:14:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 2D1D21533F; Thu, 30 Dec 1999 07:14:41 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id A30281FCC; Thu, 30 Dec 1999 16:14:34 +0100 (CET) Date: Thu, 30 Dec 1999 16:14:34 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Cc: freebsd-ports@freebsd.org Subject: mailwrapper "breaks" postfix installs Message-ID: <19991230161434.A447@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just noticed that after my make installworld my postfix install was "busted" ... I found out that apparently there has been installed a new binary called mailwrapper that replaced my existing sendmail-symlinks (created by postfix ports' make replace command) with new symlinks to mailwrapper. I have been perfectly able to make my postfix working again by specifying the correct paths in /etc/mail/mailer.conf (set everything to /usr/local/sbin/sendmail PostFix's own sendmail-wrapper) A Heads Up would have been appreciated for this one though. This means hat the Postfix Port's make replace command .. should alter /etc/mail/mailer.conf now instead of directly changing the sendmail program and symlinks. -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 7:17:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145]) by hub.freebsd.org (Postfix) with ESMTP id 44A931533E for ; Thu, 30 Dec 1999 07:17:50 -0800 (PST) (envelope-from daeron@Wit401305.student.utwente.nl) Received: by shadowmere.student.utwente.nl (Postfix, from userid 1000) id 538CE1FC0; Thu, 30 Dec 1999 16:17:49 +0100 (CET) Date: Thu, 30 Dec 1999 16:17:49 +0100 From: Pascal Hofstee To: freebsd-current@freebsd.org Subject: KERNEL -=> _KERNEL entry missed Message-ID: <19991230161749.A479@shadowmere.student.utwente.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While compiling a new kernel after the KERNEL -=> _KERNEL change i found out that /usr/src/sys/crypto/des/des_locl.h still has a KERNEL check instead of _KERNEL which breaks kernel-building. I changed it myself and kernel compiled cleanly again. This is with crypto checked out from cvsup2.internet.FreeBSD.org -- -------------------- Pascal Hofstee - daeron@shadowmere.student.utwente.nl -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 7:43:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 901491506E for ; Thu, 30 Dec 1999 07:43:42 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id EDDFD137F73 for ; Thu, 30 Dec 1999 10:43:39 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id KAA74175; Thu, 30 Dec 1999 10:43:39 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14443.32171.86048.584143@trooper.velocet.net> Date: Thu, 30 Dec 1999 10:43:39 -0500 (EST) To: freebsd-current@freebsd.org Subject: Panic from NFS? X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like the leasing stuff in NFS has a little buglet... (This is with 4.0-CURRENT cvsup'd a few days before Christmas) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x12ffa8d4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01b5bc9 stack pointer = 0x10:0xcf632c40 frame pointer = 0x10:0xcf632ccc 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 = 3611 (cp) interrupt mask = kernel: type 12 trap, code=0 Stopped at nqsrv_send_eviction+0x9d: movl 0x14(%eax),%eax nqsrv_send_eviction(cf5f4980,c263b140,ffffffff,0,c24b0c00) at nqsrv_send_eviction+0x9d nqsrv_getlease(cf5f4980,cf632dc0,6,ffffffff,cf613680) at nqsrv_getlease+0x2cd nqnfs_vop_lease_check(cf632e10,cf632de8,c0212229,cf632e10,cf632e84) at nqnfs_vop_lease_check+0x34 vop_defaultop(cf632e10,cf632e84,c0197787,cf632e10,0) at vop_defaultop+0x15 ufs_vnoperate(cf632e10) at ufs_vnoperate+0x15 vn_open(cf632edc,602,1a4,cf613680,c029394c) at vn_open+0xdf open(cf613680,cf632f80,1,6,805465d) at open+0xb5 syscall(2f,2f,2f,805465d,6) at syscall+0x176 Xint0x80_syscall() at Xint0x80_syscall+0x26 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 8: 3:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id BB51F15334 for ; Thu, 30 Dec 1999 08:03:44 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id C8E51137F74 for ; Thu, 30 Dec 1999 11:03:43 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id LAA74736; Thu, 30 Dec 1999 11:03:42 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14443.33374.329712.324138@trooper.velocet.net> Date: Thu, 30 Dec 1999 11:03:42 -0500 (EST) To: freebsd-current@freebsd.org Subject: fsck of /, related to last post. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Related to my last post, the system came up and started to fsck. It appears, with current, that the system will refuse to r/w mount root even though the fsck has complete successfully. Is this an rc-file out-of-date issue, or has something changed in the kernel. Root is an 18G SCSI (da0s1a) on a 2940-LVD controller. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 8: 5:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id B148614D65 for ; Thu, 30 Dec 1999 08:05:23 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 467BA1C5D; Thu, 30 Dec 1999 11:04:30 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 42E1F3843; Thu, 30 Dec 1999 11:04:30 -0500 (EST) Date: Thu, 30 Dec 1999 11:04:30 -0500 (EST) From: Bill Fumerola To: David Gilbert Cc: freebsd-current@freebsd.org Subject: Re: fsck of /, related to last post. In-Reply-To: <14443.33374.329712.324138@trooper.velocet.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, 30 Dec 1999, David Gilbert wrote: > Related to my last post, the system came up and started to fsck. It > appears, with current, that the system will refuse to r/w mount root > even though the fsck has complete successfully. Is this an rc-file > out-of-date issue, or has something changed in the kernel. Reboot. I don't know why it works, but it does. :-> -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 8:15: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id ACF6F153A1 for ; Thu, 30 Dec 1999 08:15:01 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 84055137F74; Thu, 30 Dec 1999 11:14:58 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id LAA75098; Thu, 30 Dec 1999 11:14:58 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14443.34050.325756.938310@trooper.velocet.net> Date: Thu, 30 Dec 1999 11:14:58 -0500 (EST) To: Bill Fumerola Cc: David Gilbert , freebsd-current@freebsd.org Subject: Re: fsck of /, related to last post. In-Reply-To: References: <14443.33374.329712.324138@trooper.velocet.net> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Bill" == Bill Fumerola writes: Bill> On Thu, 30 Dec 1999, David Gilbert wrote: >> Related to my last post, the system came up and started to fsck. >> It appears, with current, that the system will refuse to r/w mount >> root even though the fsck has complete successfully. Is this an >> rc-file out-of-date issue, or has something changed in the kernel. Bill> Reboot. I don't know why it works, but it does. :-> Right... I already knew that, but it's a manual reboot... and this is "suboptimal" (ie. requiring operator intervention). Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 8:18:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 2C84615252 for ; Thu, 30 Dec 1999 08:18:09 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id B60221C5D; Thu, 30 Dec 1999 11:17:15 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id B2A553843; Thu, 30 Dec 1999 11:17:15 -0500 (EST) Date: Thu, 30 Dec 1999 11:17:15 -0500 (EST) From: Bill Fumerola To: David Gilbert Cc: freebsd-current@freebsd.org Subject: Re: fsck of /, related to last post. In-Reply-To: <14443.34050.325756.938310@trooper.velocet.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, 30 Dec 1999, David Gilbert wrote: > Bill> Reboot. I don't know why it works, but it does. :-> > > Right... I already knew that, but it's a manual reboot... and this is > "suboptimal" (ie. requiring operator intervention). Indeed. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 8:23:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 968B9153C4 for ; Thu, 30 Dec 1999 08:23:35 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id LAA23490; Thu, 30 Dec 1999 11:23:28 -0500 (EST) Message-ID: <19991230112328.A23129@netmonger.net> Date: Thu, 30 Dec 1999 11:23:28 -0500 From: Christopher Masto To: David Gilbert , Bill Fumerola Cc: freebsd-current@FreeBSD.ORG Subject: Re: fsck of /, related to last post. Mail-Followup-To: David Gilbert , Bill Fumerola , freebsd-current@FreeBSD.ORG References: <14443.33374.329712.324138@trooper.velocet.net> <14443.34050.325756.938310@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <14443.34050.325756.938310@trooper.velocet.net>; from David Gilbert on Thu, Dec 30, 1999 at 11:14:58AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 30, 1999 at 11:14:58AM -0500, David Gilbert wrote: > >>>>> "Bill" == Bill Fumerola writes: > > Bill> On Thu, 30 Dec 1999, David Gilbert wrote: > >> Related to my last post, the system came up and started to fsck. > >> It appears, with current, that the system will refuse to r/w mount > >> root even though the fsck has complete successfully. Is this an > >> rc-file out-of-date issue, or has something changed in the kernel. > > Bill> Reboot. I don't know why it works, but it does. :-> > > Right... I already knew that, but it's a manual reboot... and this is > "suboptimal" (ie. requiring operator intervention). If you re-MAKEDEV your device nodes, it shouldn't happen again. It would be nice if something were fixed to actually say what's going on instead of confusing the hell out of people, since there seems to be a thread on this every day on -current. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 8:24:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 03BE515103 for ; Thu, 30 Dec 1999 08:24:19 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id IAA23421; Thu, 30 Dec 1999 08:57:40 -0800 (PST) Date: Thu, 30 Dec 1999 08:57:40 -0800 (PST) From: Alfred Perlstein To: Bill Fumerola Cc: David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: fsck of /, related to last post. 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, 30 Dec 1999, Bill Fumerola wrote: > On Thu, 30 Dec 1999, David Gilbert wrote: > > > Bill> Reboot. I don't know why it works, but it does. :-> > > > > Right... I already knew that, but it's a manual reboot... and this is > > "suboptimal" (ie. requiring operator intervention). > > Indeed. Remaking your disk devices in /dev should fix this, don't forget to do both ad* and wd* if you have IDE disks. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 9:55:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id CFBB115374 for ; Thu, 30 Dec 1999 09:55:08 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA20156 for ; Thu, 30 Dec 1999 12:23:37 -0500 (EST) Received: from rac5.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id MAA15720 for ; Thu, 30 Dec 1999 12:23:35 -0500 (EST) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id MAA15716 for ; Thu, 30 Dec 1999 12:23:35 -0500 (EST) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Thu, 30 Dec 1999 12:23:35 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: -CURRENT make world broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just wondering if anyone else was having a problem making the world on -CURRENT right now? I don't remember the exact error I got because I'm at work, and my machine is at home, but for the last 3 weeks whenever I try to make world, it dies in a different place, I've tried every day, so I'm thinking maybe it's a problem with my computer's setup, or maybe I forgot to update something. What updates that I'm missing could be causing this? (for example, once I had this problem, and reinstalling the mk files in /usr/share/mk fixed it, is there something simple like this that I missed?) I will be sending the exact error as soon as I have a chance to reproduce it. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 13:39:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 6239C15071 for ; Thu, 30 Dec 1999 13:39:53 -0800 (PST) (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.9.3/8.9.3) with ESMTP id NAA54996 for ; Thu, 30 Dec 1999 13:39:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199912302139.NAA54996@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: gcc 2.96 snapshot and X Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Dec 1999 13:39:24 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last nite , I managed to compile all of XFree86 3.9.17 with no compiler bugs from gcc. /usr/local/bin/gcc -v Reading specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd4.0/2.96/specs gcc version 2.96 19991110 (experimental) Enjoy -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 14: 4:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from dc.numbersusa.com (mail.whetstonelogic.com [205.252.46.165]) by hub.freebsd.org (Postfix) with ESMTP id 28459153E5 for ; Thu, 30 Dec 1999 14:04:08 -0800 (PST) (envelope-from patrick@whetstonelogic.com) Received: from dbserver (dbserver [205.252.46.172]) by dc.numbersusa.com (8.9.3/8.9.3) with SMTP id RAA23480; Thu, 30 Dec 1999 17:05:12 -0500 (EST) (envelope-from patrick@whetstonelogic.com) Message-ID: <000901bf5313$3a9599b0$ac2efccd@whetstonelogic.com> From: "Patrick Gardella" To: "Kenneth Wayne Culver" , References: Subject: Re: -CURRENT make world broken Date: Thu, 30 Dec 1999 17:14:23 -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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I build world this morning, and it built fine. Patrick ----- Original Message ----- From: Kenneth Wayne Culver To: Sent: Thursday, December 30, 1999 12:23 PM Subject: -CURRENT make world broken > I was just wondering if anyone else was having a problem making the world > on -CURRENT right now? I don't remember the exact error I got because > I'm at work, and my machine is at home, but for the last 3 weeks whenever > I try to make world, it dies in a different place, I've tried every day, > so I'm thinking maybe it's a problem with my computer's setup, or maybe I > forgot to update something. What updates that I'm missing could be causing > this? (for example, once I had this problem, and reinstalling the mk files > in /usr/share/mk fixed it, is there something simple like this that I > missed?) I will be sending the exact error as soon as I have a chance to > reproduce it. > > > ================================================================= > | Kenneth Culver | FreeBSD: The best OS around. | > | Unix Systems Administrator | ICQ #: 24767726 | > | and student at The | AIM: AgRSkaterq | > | The University of Maryland, | Website: (Under Construction) | > | College Park. | http://www.wam.umd.edu/~culverk/| > ================================================================= > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 14:21: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B15A314D21 for ; Thu, 30 Dec 1999 14:20:55 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40324>; Fri, 31 Dec 1999 09:13:08 +1100 Content-return: prohibited Date: Fri, 31 Dec 1999 09:20:38 +1100 From: Peter Jeremy Subject: Re: gcc compiler problem part deux To: current@FreeBSD.ORG Message-Id: <99Dec31.091308est.40324@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last time I checked (I haven't moved to the latest gcc, so I can't confirm it there), one significant difference between 'cc -E' and /usr/libexec/cpp was that the latter would read from a pipe, whilst the former wouldn't. This can make converting to 'cc -E' a non-trivial exercise. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 14:33:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 128FA14C3B for ; Thu, 30 Dec 1999 14:33:38 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 783A51DA7; Thu, 30 Dec 1999 23:33:27 +0100 (CET) Date: Thu, 30 Dec 1999 23:33:27 +0100 From: "Dave J. Boers" To: Steve Price Cc: freebsd-current@FreeBSD.org Subject: Re: troubles with X Message-ID: <19991230233327.A16271@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from sprice@hiwaay.net on Mon, Dec 27, 1999 at 06:28:02PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 27, 1999 at 06:28:02PM -0600, Steve Price wrote: > For some reason now I can't startx(1) as either myself or root. > I type startx and the PAM auth routines loop forever printing > out 'Password:'. I comment out the last two lines in /etc/pam.conf > and I get an authentication failure (as I should). I'm having the same problem. Cvsupped and recompiled -current just a few hours ago. Then I recompiled X 3.3.5 and installed it. Now I can't start X anymore either. Lines containing "Password:" just keep scrolling over my terminal. The password lines are being generated by xinit. Just plain "X" works. > Anyone have any ideas what I'm doing wrong? What is the correct > method to start X on -current nowadays? AFAIK you're doing it correctly. Can someone PLEASE help out here? It's getting a bit annoying. Regards, Dave Boers. -- djb@relativity.student.utwente.nl be afraid, . . . be *very* afraid To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 14:40:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 6C5AF1525D for ; Thu, 30 Dec 1999 14:40:25 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id QAA04685; Thu, 30 Dec 1999 16:40:23 -0600 (CST) Date: Thu, 30 Dec 1999 16:40:22 -0600 (CST) From: Steve Price To: "Dave J. Boers" Cc: freebsd-current@FreeBSD.org Subject: Re: troubles with X In-Reply-To: <19991230233327.A16271@relativity.student.utwente.nl> 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, 30 Dec 1999, Dave J. Boers wrote: # I'm having the same problem. Cvsupped and recompiled -current just a few # hours ago. Then I recompiled X 3.3.5 and installed it. Now I can't start X # anymore either. Lines containing "Password:" just keep scrolling over my # terminal. The password lines are being generated by xinit. Just plain "X" # works. # # Can someone PLEASE help out here? It's getting a bit annoying. I finally had to recompile XFree86 and disable the PAM support. It was the only thing I could think of in lieu of a 'real fix'. :/ -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 14:43:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (Postfix) with ESMTP id 0C946153C0 for ; Thu, 30 Dec 1999 14:43:23 -0800 (PST) (envelope-from veldy@visi.com) Received: from barley (nic-25-c116-158.mn.mediaone.net [24.25.116.158]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id RAA01930; Thu, 30 Dec 1999 17:41:31 -0500 (EST) Message-ID: <004a01bf5317$56bc56c0$0100a8c0@veldy.org> From: "Thomas T. Veldhouse" To: , "Steve Price" Cc: References: <19991230233327.A16271@relativity.student.utwente.nl> Subject: Re: troubles with X Date: Thu, 30 Dec 1999 16:43:47 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the answer I was given by somebody on this list last week. #/etc/pam.conf # tricky tricky forgive me xserver auth sufficient pam_permit.so no_use # If we don't match anything else, default to using getpwnam(). other auth required pam_unix.so try_first_pass other account required pam_unix.so try_first_pass Tom Veldhouse veldy@visi.com ----- Original Message ----- From: "Dave J. Boers" To: "Steve Price" Cc: Sent: Thursday, December 30, 1999 4:33 PM Subject: Re: troubles with X > On Mon, Dec 27, 1999 at 06:28:02PM -0600, Steve Price wrote: > > For some reason now I can't startx(1) as either myself or root. > > I type startx and the PAM auth routines loop forever printing > > out 'Password:'. I comment out the last two lines in /etc/pam.conf > > and I get an authentication failure (as I should). > > I'm having the same problem. Cvsupped and recompiled -current just a few > hours ago. Then I recompiled X 3.3.5 and installed it. Now I can't start X > anymore either. Lines containing "Password:" just keep scrolling over my > terminal. The password lines are being generated by xinit. Just plain "X" > works. > > > Anyone have any ideas what I'm doing wrong? What is the correct > > method to start X on -current nowadays? > > AFAIK you're doing it correctly. > > Can someone PLEASE help out here? It's getting a bit annoying. > > Regards, > > Dave Boers. > > -- > djb@relativity.student.utwente.nl > be afraid, . . . be *very* afraid > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 14:55:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id ADD7014E81 for ; Thu, 30 Dec 1999 14:55:49 -0800 (PST) (envelope-from djb@Wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 46C411E2F; Thu, 30 Dec 1999 23:55:47 +0100 (CET) Date: Thu, 30 Dec 1999 23:55:47 +0100 From: "Dave J. Boers" To: "Thomas T. Veldhouse" Cc: djb@Wit389306.student.utwente.nl, Steve Price , freebsd-current@FreeBSD.ORG Subject: Re: troubles with X Message-ID: <19991230235547.A356@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <19991230233327.A16271@relativity.student.utwente.nl> <004a01bf5317$56bc56c0$0100a8c0@veldy.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <004a01bf5317$56bc56c0$0100a8c0@veldy.org>; from veldy@visi.com on Thu, Dec 30, 1999 at 04:43:47PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 30, 1999 at 04:43:47PM -0600, Thomas T. Veldhouse wrote: > Here is the answer I was given by somebody on this list last week. > > #/etc/pam.conf > # tricky tricky forgive me > xserver auth sufficient pam_permit.so no_use > # If we don't match anything else, default to using getpwnam(). > other auth required pam_unix.so > try_first_pass > other account required pam_unix.so > try_first_pass Great! That fixed it. Thanks a lot, Dave Boers. P.S. Sorry for not picking this up from the list myself. -- djb@relativity.student.utwente.nl be afraid, . . . be *very* afraid To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 15:13:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 7AB3114E40 for ; Thu, 30 Dec 1999 15:13:33 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id RAA08317; Thu, 30 Dec 1999 17:13:29 -0600 (CST) Date: Thu, 30 Dec 1999 17:13:28 -0600 (CST) From: Steve Price To: "Thomas T. Veldhouse" Cc: djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: troubles with X In-Reply-To: <004a01bf5317$56bc56c0$0100a8c0@veldy.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999, Thomas T. Veldhouse wrote: # Here is the answer I was given by somebody on this list last week. # # #/etc/pam.conf # # tricky tricky forgive me # xserver auth sufficient pam_permit.so no_use # # If we don't match anything else, default to using getpwnam(). # other auth required pam_unix.so # try_first_pass # other account required pam_unix.so # try_first_pass This is really not a 'fix' per se. It is more like a workaround as it disables PAM without having to recompile X. Or at least that's the way I read it. Surely there is a way to really use PAM authentication? If this *is* the official fix then I should probably commit it to src/etc/pam.conf because everyone setting up a new system is going to run into this very same problem if they install X. BTW, thanks for the quick reply. :) -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 16:35:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 7C41715301 for ; Thu, 30 Dec 1999 16:35:08 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 67340 invoked by uid 1001); 31 Dec 1999 00:35:07 -0000 Date: 30 Dec 1999 16:35:07 -0800 Date: Thu, 30 Dec 1999 16:35:07 -0800 From: Bill Swingle To: current@freebsd.org Subject: Building older -current on newer -current? Message-ID: <19991230163506.A67256@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey all, I've got a laptop that's giving me all kinds of pccard headaches and I'd like to get it back to -current from the begining of the month before I was having these problems. Is there any reason why I couldn't make world from some time around 12/8/99 on -current from yesterday evening? Would I have to build a new kernel first? -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 17:16:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from snowy.org (snowy.org [203.37.251.14]) by hub.freebsd.org (Postfix) with ESMTP id 8CD4E15363 for ; Thu, 30 Dec 1999 17:16:25 -0800 (PST) (envelope-from snowy@snowy.org) Received: from localhost (snowy@localhost) by snowy.org (8.9.3/8.9.3) with ESMTP id LAA96454; Fri, 31 Dec 1999 11:16:04 +1000 (EST) (envelope-from snowy@snowy.org) Date: Fri, 31 Dec 1999 11:16:04 +1000 (EST) From: Sleepless in Brisbane To: Steve Price Cc: "Thomas T. Veldhouse" , djb@Wit389306.student.utwente.nl, freebsd-current@FreeBSD.ORG Subject: Re: troubles with X 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, 30 Dec 1999, Steve Price wrote: > On Thu, 30 Dec 1999, Thomas T. Veldhouse wrote: > > # Here is the answer I was given by somebody on this list last week. > # > # #/etc/pam.conf > # # tricky tricky forgive me > # xserver auth sufficient pam_permit.so no_use > # # If we don't match anything else, default to using getpwnam(). > # other auth required pam_unix.so > # try_first_pass > # other account required pam_unix.so > # try_first_pass > > This is really not a 'fix' per se. It is more like a workaround > as it disables PAM without having to recompile X. Or at least that's > the way I read it. > > Surely there is a way to really use PAM authentication? If this *is* > the official fix then I should probably commit it to src/etc/pam.conf > because everyone setting up a new system is going to run into this > very same problem if they install X. On a side note I found this fixed a problem with logging in via XDM that I have been seeing lately as well but just haven't had the time to track down; so it could certainly be helpful for more than just those running local displays. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 17:55:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9281B14E1B for ; Thu, 30 Dec 1999 17:55:23 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA27207; Thu, 30 Dec 1999 17:55:21 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA39440; Thu, 30 Dec 1999 17:55:21 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 30 Dec 1999 17:55:21 -0800 (PST) Message-Id: <199912310155.RAA39440@vashon.polstra.com> To: unfurl@dub.net Subject: Re: Building older -current on newer -current? In-Reply-To: <19991230163506.A67256@dub.net> References: <19991230163506.A67256@dub.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991230163506.A67256@dub.net>, Bill Swingle wrote: > I've got a laptop that's giving me all kinds of pccard headaches > and I'd like to get it back to -current from the begining of the > month before I was having these problems. Is there any reason why I > couldn't make world from some time around 12/8/99 on -current from > yesterday evening? Would I have to build a new kernel first? Normally it's possible, and you don't need a new kernel to do it. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 17:57:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 58F6C15363 for ; Thu, 30 Dec 1999 17:57:26 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA27219; Thu, 30 Dec 1999 17:57:24 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA39464; Thu, 30 Dec 1999 17:57:24 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 30 Dec 1999 17:57:24 -0800 (PST) Message-Id: <199912310157.RAA39464@vashon.polstra.com> To: peter.jeremy@ALCATEL.COM.AU Subject: Re: gcc compiler problem part deux In-Reply-To: <99Dec31.091308est.40324@border.alcanet.com.au> References: <99Dec31.091308est.40324@border.alcanet.com.au> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <99Dec31.091308est.40324@border.alcanet.com.au>, Peter Jeremy wrote: > Last time I checked (I haven't moved to the latest gcc, so I can't > confirm it there), one significant difference between 'cc -E' > and /usr/libexec/cpp was that the latter would read from a pipe, > whilst the former wouldn't. This can make converting to 'cc -E' a > non-trivial exercise. That's what /dev/stdin is for: cat hello.c | cc -E -x c /dev/stdin John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 19:49:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust180.tnt6.tco2.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7F2BD14DE9; Thu, 30 Dec 1999 19:49:21 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Thu, 30 Dec 1999 22:49:19 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: gcc compiler problem part deux In-Reply-To: <99Dec31.091308est.40324@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Dec 1999, Peter Jeremy wrote: > Last time I checked (I haven't moved to the latest gcc, so I can't > confirm it there), one significant difference between 'cc -E' and > /usr/libexec/cpp was that the latter would read from a pipe, whilst > the former wouldn't. This can make converting to 'cc -E' a > non-trivial exercise. Huh? Non-trivial? {"/home/green"}$ echo __FreeBSD__ | cc -E - # 1 "" 4 > Peter -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 21:29:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 3AB1D15327 for ; Thu, 30 Dec 1999 21:29:06 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (localhost [127.0.0.1]) by picnic.mat.net (Postfix) with ESMTP id A20E572519 for ; Fri, 31 Dec 1999 00:29:06 -0500 (EST) Date: Fri, 31 Dec 1999 00:29:06 -0500 (EST) From: Chuck Robey To: FreeBSD-current@freebsd.org Subject: multiple cd devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been doing a lot of neatening up here, and one of the tasks was to get both of the cdrom drives I have (one per machine) moved over so that they are on the same machine. This was so I can use the one that's a writer in conjuntion with a reader, and do duplication. Anyhow, getting the kernel to recognize cd1 was no problem, but getting /dev/MAKEDEV to do that was a hairy PITA. I couldn't locate, in either cd(4) or cd(9), the information on the maj/min numbers, so that I could just do the mknod's manually, and MAKEDEV would simply do nothing if I entered './MAKEDEV cd1'. After *much* screwing about, in desperation (trying wierd combinations) I did a './MAKEDEV cd2', and *that* made my cd1 devices (not the cd2 ones, but I didn't have a cd2, I didn't care). This sounds pretty wrong, I think MAKEDEV is busted for this, right? And, if you don't want to have the actual maj/min numbers for the cd devices in the man pages (because you want Unix unfriendly), well, shouldn't there be a pointer to a include file that would be up to date with that info, so at least the info is available somehow? BTW, all the other MAKEDEV combinations, like cd*, cd1*, cd1a, etc, all failed noisily, like: ROOT:/dev:113 >sh MAKEDEV cd1a [: 1a: bad number [: 1a: bad number ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 22:45:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust208.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 713BC1551C; Thu, 30 Dec 1999 22:45:33 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Fri, 31 Dec 1999 01:45:31 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Chuck Robey Cc: FreeBSD-current@freebsd.org Subject: Re: multiple cd devices 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 The way certain devices, like cd with its monotonically increasing counter where devices are probed in order and assigned device based on precedence and not hardwiring/controller connection, work is consistent between the kernel and MAKEDEV. If you have 2 cd devices, you have cd0 and cd1, so MAKEDEV accepts "cd2" for "two cd devices". All CD devices work that way. Disks don't, because there is potential for hard-wiring there, and will often be gaps. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 22:59: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 6550F14DEB; Thu, 30 Dec 1999 22:59:01 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id BAA02112; Fri, 31 Dec 1999 01:59:04 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 31 Dec 1999 01:59:04 -0500 (EST) From: Chuck Robey To: Brian Fundakowski Feldman Cc: FreeBSD-current@FreeBSD.org Subject: Re: multiple cd devices 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, 31 Dec 1999, Brian Fundakowski Feldman wrote: > The way certain devices, like cd with its monotonically increasing counter > where devices are probed in order and assigned device based on precedence > and not hardwiring/controller connection, work is consistent between > the kernel and MAKEDEV. If you have 2 cd devices, you have cd0 and cd1, > so MAKEDEV accepts "cd2" for "two cd devices". All CD devices work > that way. Disks don't, because there is potential for hard-wiring > there, and will often be gaps. Why are "certain" devices wildly different than all other ones? I've never encountered that kind of syntax before, and I can't see that it's documented anywhere at all. Certainly, MAKEDEV itself (in it's comments) treats cd* just like all the others, specifying that the number following is a unit number, and *not* a quantity. I don't know when this happened, but it's surely not obvious. Not one word in the handbook, either. In fact, according to cd(4), you *can* specify the unit number: ... Prior to FreeBSD 2.1, the first device found will be attached as cd0 the next, cd1, etc. Beginning in FreeBSD 2.1 it is possible to specify what cd unit a device should come on line as; refer to scsi(4) for details on kernel configura- tion. That makes this odd setup even odder. Can't understand why this was done. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 23:44: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 25CCB14C48 for ; Thu, 30 Dec 1999 23:43:52 -0800 (PST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id IAA31250; Fri, 31 Dec 1999 08:43:35 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <014801bf5362$c677bea0$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "Chuck Robey" , References: Subject: Sv: multiple cd devices Date: Fri, 31 Dec 1999 08:27:29 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Chuck Robey To: Sent: Friday, December 31, 1999 6:29 AM Subject: multiple cd devices > Anyhow, getting the kernel to recognize cd1 was no problem, but = getting > /dev/MAKEDEV to do that was a hairy PITA. I couldn't locate, in = either > cd(4) or cd(9), the information on the maj/min numbers, so that I = could > just do the mknod's manually, and MAKEDEV would simply do nothing if I > entered './MAKEDEV cd1'. After *much* screwing about, in desperation > (trying wierd combinations) I did a './MAKEDEV cd2', and *that* made = my > cd1 devices (not the cd2 ones, but I didn't have a cd2, I didn't = care). >=20 > This sounds pretty wrong, I think MAKEDEV is busted for this, right? = And, > if you don't want to have the actual maj/min numbers for the cd = devices in > the man pages (because you want Unix unfriendly), well, shouldn't = there be > a pointer to a include file that would be up to date with that info, = so at > least the info is available somehow? >=20 The philosophy (sp?) of the numbers to MAKEDEV seems a little = inconsistent. MAKEDEV wd10 makes=20 wd10 wd10b wd10d wd10f wd10h wd10s2 wd10s4 wd10a wd10c wd10e wd10g wd10s1 wd10s3 But makedev cd makes the number of devices you want, not the last = device number. So if you do MAKEDEV cd10, you get 10 devices: cd0 to cd9. However, MAKEDEV seems a little buggy, when dealing with _many_ = cd-devices. MAKEDEV cd31 makes cd0-30 # ./MAKEDEV cd32 cd32 is invalid -- can't have more than 32 cd devices Also, when RE-making more than 10 devices, it complains: chgrp: cd10a: No such file or directory chgrp: cd10c: No such file or directory chgrp: cd11a: No such file or directory ... chgrp: cd29c: No such file or directory chgrp: cd30a: No such file or directory chgrp: cd30c: No such file or directory This only happens if the devices exist already. But the devices still = change timestamps. But I guess only a few people actually has more than 9 cd drives in one = box... I have made paches, will send-pr, when I've made sure I have = mergemaster'ed my "production" box, it's running a week old or so = current, but for some strange reason MAKEDEV isn't being installed by = default. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 30 23:44:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id ACA2214C05 for ; Thu, 30 Dec 1999 23:44:45 -0800 (PST) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id A5BA72CEA0; Fri, 31 Dec 1999 09:44:41 +0200 (EET) Received: by myhakas.matti.ee (Postfix, from userid 1000) id AB7EA126; Fri, 31 Dec 1999 09:44:43 +0200 (EET) Date: Fri, 31 Dec 1999 09:44:43 +0200 From: Vallo Kallaste To: Kenneth Wayne Culver Cc: freebsd-current@freebsd.org Subject: Re: -CURRENT make world broken Message-ID: <19991231094443.A62050@myhakas.matti.ee> Reply-To: vallo@matti.ee References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Kenneth Wayne Culver on Thu, Dec 30, 1999 at 12:23:35PM -0500 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 30, 1999 at 12:23:35PM -0500, Kenneth Wayne Culver wrote: > I was just wondering if anyone else was having a problem making the world > on -CURRENT right now? I don't remember the exact error I got because > I'm at work, and my machine is at home, but for the last 3 weeks whenever > I try to make world, it dies in a different place, I've tried every day, > so I'm thinking maybe it's a problem with my computer's setup, or maybe I > forgot to update something. What updates that I'm missing could be causing > this? (for example, once I had this problem, and reinstalling the mk files > in /usr/share/mk fixed it, is there something simple like this that I > missed?) I will be sending the exact error as soon as I have a chance to > reproduce it. I built the world yesterday just fine, althought about a week ago I had great problems with build process. Died with different signals in different places. All these were problems with my motherboard, the DIMM socket contact pins lost tight contact with DIMM because of bad material of contact pins. It seems a lot of cheap motherboards use very cheap DIMM sockets. It was quite a work to hunt it down to this. Just FYI. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 2:25:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id F277915371; Fri, 31 Dec 1999 02:25:18 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id CF6729B5B; Fri, 31 Dec 1999 05:25:17 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id C1EF5BA0C; Fri, 31 Dec 1999 05:25:17 -0500 (EST) Date: Fri, 31 Dec 1999 05:25:17 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Chuck Robey Cc: Brian Fundakowski Feldman , FreeBSD-current@FreeBSD.org Subject: Re: multiple cd devices 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, 31 Dec 1999, Chuck Robey wrote: > On Fri, 31 Dec 1999, Brian Fundakowski Feldman wrote: > > > The way certain devices, like cd with its monotonically increasing counter > > where devices are probed in order and assigned device based on precedence > > and not hardwiring/controller connection, work is consistent between > > the kernel and MAKEDEV. If you have 2 cd devices, you have cd0 and cd1, > > so MAKEDEV accepts "cd2" for "two cd devices". All CD devices work > > that way. Disks don't, because there is potential for hard-wiring > > there, and will often be gaps. > > Why are "certain" devices wildly different than all other ones? I've > never encountered that kind of syntax before, and I can't see that it's > documented anywhere at all. Certainly, MAKEDEV itself (in it's > comments) treats cd* just like all the others, specifying that the number > following is a unit number, and *not* a quantity. I don't know when this > happened, but it's surely not obvious. Not one word in the handbook, > either. > > In fact, according to cd(4), you *can* specify the unit number: > > ... Prior to FreeBSD > 2.1, the first device found will be attached as cd0 the next, cd1, etc. > Beginning in FreeBSD 2.1 it is possible to specify what cd unit a device > should come on line as; refer to scsi(4) for details on kernel configura- > tion. > > That makes this odd setup even odder. Can't understand why this was done. > FWIW, bin/13768 asks the same questions. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 4:59:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from gemma.TechFak.Uni-Bielefeld.DE (gemma.TechFak.Uni-Bielefeld.DE [129.70.136.103]) by hub.freebsd.org (Postfix) with ESMTP id 9BA14154A9 for ; Fri, 31 Dec 1999 04:59:31 -0800 (PST) (envelope-from oschonef@TechFak.Uni-Bielefeld.DE) Received: from frizzantino.TechFak.Uni-Bielefeld.DE (frizzantino.TechFak.Uni-Bielefeld.DE [129.70.133.65]) by gemma.TechFak.Uni-Bielefeld.DE (8.9.1/8.9.1/TechFak/pk+ro19980721) with SMTP id NAA01580 for ; Fri, 31 Dec 1999 13:59:29 +0100 (MET) From: Oliver Schonefeld Received: by frizzantino.TechFak.Uni-Bielefeld.DE (SMI-8.6/pk970604A) id NAA21490; Fri, 31 Dec 1999 13:59:29 +0100 Message-Id: <199912311259.NAA21490@frizzantino.TechFak.Uni-Bielefeld.DE> Subject: ida driver in -current and eisa bus attachment To: freebsd-current@freebsd.org Date: Fri, 31 Dec 1999 13:59:29 +0100 (MET) X-Mailer: ELM [version 2.4 PL25 PGP6] 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 wonder what is happening to the ida driver for comapq's smart array controller series. people say the pci version works but the eisa version is not. in the ida.c file is says: * Specific probe routines are in: * pci/ida_pci.c * i386/eisa/ida_eisa.c but unfortunatly the ida_eisa.c file seems to be missing in the source tree (i just cvsuped the whole thing). i did some research at deja and found out, that matthew dodd wrote the eisa bus attachment and it is downloadabe on his ftp site. unfortunatly (again) the eisa_add_intr() routine has changed and needs an additional argument (which happend to be the irq-trigger). i added EISA_TRIGGER_LEVEL to that call (level is what the controller uses according to the compaq bios). the kernel compiles but crashes with a trap 12 when probing ida0. it crashed in the ida_wait() routine in ida.c while initially trying to attach the board. i wonder if anybody else hat such problems and (that would be even better) has solved them. i am willing to help in developting this driver but my knowlegde of c is bad and my kernel programming excperiences are even worse ... :-( anyways, i hope somebody out there is still working on that thing, regards, oliver -- -------------------------------------------------------- And remember: "Life sucks and then you die!" email: oschonef@techfak.uni-bielefeld.de olli@psychopathen.org -------------------------------------------------------- Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! <- Save this lifeform ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 6: 7:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (as15-025.rp-plus.de [149.221.237.25]) by hub.freebsd.org (Postfix) with ESMTP id E2F3714EF4 for ; Fri, 31 Dec 1999 06:07:26 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id BB185AB7F for ; Fri, 31 Dec 1999 15:07:54 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id PAA28696 for current@freebsd.org; Fri, 31 Dec 1999 15:08:29 +0100 (CET) (envelope-from alex) Date: Fri, 31 Dec 1999 15:08:29 +0100 From: Alexander Langer To: current@freebsd.org Subject: date(1) and -v-1m Message-ID: <19991231150829.A28634@cichlids.cichlids.com> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! The behaviour of date(1) is probably specified by POSIX, but I think, date -v-1m should at least return a date a month _before_ the current month. Example: Mi 1 Dez 1999 15:06:47 CET (Dez. has 31, so it should be Nov 30, I think). More confusing is something like: alex:~ $ date -v-1m +%Y-%m 1999-12 what I wanted to use to create backup folders for my mail-system (all mails of the last month are moved to a folder of the last month). That's weird, somehow. Is this a bug or a feature? Is this POSIX-compilant? Do we want an additional option? (I want :-)) Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 6:25:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from 1Cust212.tnt1.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 61A0B1516E; Fri, 31 Dec 1999 06:25:44 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Fri, 31 Dec 1999 09:25:42 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Chuck Robey Cc: FreeBSD-current@FreeBSD.org Subject: Re: multiple cd devices 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, 31 Dec 1999, Chuck Robey wrote: > On Fri, 31 Dec 1999, Brian Fundakowski Feldman wrote: > > > The way certain devices, like cd with its monotonically increasing counter > > where devices are probed in order and assigned device based on precedence > > and not hardwiring/controller connection, work is consistent between > > the kernel and MAKEDEV. If you have 2 cd devices, you have cd0 and cd1, > > so MAKEDEV accepts "cd2" for "two cd devices". All CD devices work > > that way. Disks don't, because there is potential for hard-wiring > > there, and will often be gaps. > > Why are "certain" devices wildly different than all other ones? I've > never encountered that kind of syntax before, and I can't see that it's > documented anywhere at all. Certainly, MAKEDEV itself (in it's > comments) treats cd* just like all the others, specifying that the number > following is a unit number, and *not* a quantity. I don't know when this > happened, but it's surely not obvious. Not one word in the handbook, > either. *shrug* This is the only rationality I could think of. Obviously, this breaks POLA, so it should be changed (with ample warning). > > In fact, according to cd(4), you *can* specify the unit number: > > ... Prior to FreeBSD > 2.1, the first device found will be attached as cd0 the next, cd1, etc. > Beginning in FreeBSD 2.1 it is possible to specify what cd unit a device > should come on line as; refer to scsi(4) for details on kernel configura- > tion. > > That makes this odd setup even odder. Can't understand why this was done. So maybe it's just hysterical raisins. I'm not saying I like the behavior, just that I understand what that MAKEDEV behavior is. > > ---------------------------------------------------------------------------- > Chuck Robey | Interests include C & Java programming, > New Year's Resolution: I | electronics, communications, and > will not sphroxify gullible| signal processing. > people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and > fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| > dictionary. | > ---------------------------------------------------------------------------- > -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 7:24: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id A62D815327; Fri, 31 Dec 1999 07:24:05 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA27898; Sat, 1 Jan 2000 02:23:53 +1100 Date: Sat, 1 Jan 2000 02:23:32 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Chuck Robey Cc: Brian Fundakowski Feldman , FreeBSD-current@FreeBSD.ORG Subject: Re: multiple cd devices 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, 31 Dec 1999, Chuck Robey wrote: > Why are "certain" devices wildly different than all other ones? I've Because the CAM update broke (SCSI) cd devices in rev.1.171 of MAKEDEV. mcd and scd were in the same case statement so they were broken too. The breakage has spread to acd and ccd (although the latter is not a cdrom), but not to matcd or wcd or non-cdrom disks. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 8:46:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 7170D14D6E; Fri, 31 Dec 1999 08:46:21 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id RAA21151; Fri, 31 Dec 1999 17:18:52 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id RAA92898; Fri, 31 Dec 1999 17:13:14 +0100 (CET) (envelope-from wilko) Date: Fri, 31 Dec 1999 17:13:14 +0100 From: Wilko Bulte To: Brian Fundakowski Feldman Cc: Chuck Robey , FreeBSD-current@FreeBSD.ORG Subject: Re: multiple cd devices Message-ID: <19991231171314.A92878@yedi.iaf.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from green@FreeBSD.ORG on Fri, Dec 31, 1999 at 09:25:42AM -0500 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 31, 1999 at 09:25:42AM -0500, Brian Fundakowski Feldman wrote: > On Fri, 31 Dec 1999, Chuck Robey wrote: > > > On Fri, 31 Dec 1999, Brian Fundakowski Feldman wrote: > > > > > The way certain devices, like cd with its monotonically increasing counter > > > where devices are probed in order and assigned device based on precedence > > > and not hardwiring/controller connection, work is consistent between > > > the kernel and MAKEDEV. If you have 2 cd devices, you have cd0 and cd1, > > > so MAKEDEV accepts "cd2" for "two cd devices". All CD devices work > > > that way. Disks don't, because there is potential for hard-wiring > > > there, and will often be gaps. > > > > Why are "certain" devices wildly different than all other ones? I've > > never encountered that kind of syntax before, and I can't see that it's > > documented anywhere at all. Certainly, MAKEDEV itself (in it's > > comments) treats cd* just like all the others, specifying that the number > > following is a unit number, and *not* a quantity. I don't know when this > > happened, but it's surely not obvious. Not one word in the handbook, > > either. > > *shrug* This is the only rationality I could think of. Obviously, this > breaks POLA, so it should be changed (with ample warning). As for ample warning: I've seen MAKEDEVs display a list of the devices they are creating. I think the Tru64 version does this. I myself think this is a good behaviour (and hope people won't start yelling 'bloat' for once) W/ -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 12:15:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 485BE15617; Fri, 31 Dec 1999 12:15:16 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id PAA03528; Fri, 31 Dec 1999 15:15:02 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Fri, 31 Dec 1999 15:15:02 -0500 (EST) From: Chuck Robey To: Wilko Bulte Cc: Brian Fundakowski Feldman , FreeBSD-current@FreeBSD.ORG Subject: Re: multiple cd devices (MAKEDEV) In-Reply-To: <19991231171314.A92878@yedi.iaf.nl> 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, 31 Dec 1999, Wilko Bulte wrote: > > > Why are "certain" devices wildly different than all other ones? I've > > > never encountered that kind of syntax before, and I can't see that it's > > > documented anywhere at all. Certainly, MAKEDEV itself (in it's > > > comments) treats cd* just like all the others, specifying that the number > > > following is a unit number, and *not* a quantity. I don't know when this > > > happened, but it's surely not obvious. Not one word in the handbook, > > > either. > > > > *shrug* This is the only rationality I could think of. Obviously, this > > breaks POLA, so it should be changed (with ample warning). > > As for ample warning: I've seen MAKEDEVs display a list of the devices > they are creating. I think the Tru64 version does this. I myself think this > is a good behaviour (and hope people won't start yelling 'bloat' for once) I'd like to hack about a bit on MAKEDEV, but I was wondering, does sysinstall, in any way, use MAKEDEV? I *don't* want to mess with sysinstall! I think the idea of making MAKEDEV print the devices it's creating ought to be easy enough to hack ... ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 12:34:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id 7B21C156F4 for ; Fri, 31 Dec 1999 12:34:49 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA02777; Fri, 31 Dec 1999 12:40:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912312040.MAA02777@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Oliver Schonefeld Cc: freebsd-current@freebsd.org Subject: Re: ida driver in -current and eisa bus attachment In-reply-to: Your message of "Fri, 31 Dec 1999 13:59:29 +0100." <199912311259.NAA21490@frizzantino.TechFak.Uni-Bielefeld.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 Dec 1999 12:40:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > i wonder what is happening to the ida driver for comapq's smart array > controller series. Work on this driver is stalled owing to the fact that nobody that can and wants to work on it has access to the Compaq hardware required. You can't use these controllers except in Compaq systems, which makes things very difficult. If someone has a complete system featuring one or more of these controllers (a mixed PCI/EISA system would be best), there are several people that could put it to good use. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ 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 Dec 31 13:50: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 4FEEF151F4; Fri, 31 Dec 1999 13:50:04 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (hoefnix.ai [209.88.68.215]) by cypherpunks.ai (Postfix) with ESMTP id B34D849; Fri, 31 Dec 1999 17:50:02 -0400 (AST) Message-ID: <386D24C0.118C1980@vangelderen.org> Date: Fri, 31 Dec 1999 17:48:48 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: Chuck Robey , Brian Fundakowski Feldman , FreeBSD-current@FreeBSD.ORG Subject: Re: multiple cd devices References: 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: > > On Fri, 31 Dec 1999, Chuck Robey wrote: > > > Why are "certain" devices wildly different than all other ones? I've > > Because the CAM update broke (SCSI) cd devices in rev.1.171 of MAKEDEV. > mcd and scd were in the same case statement so they were broken too. The > breakage has spread to acd and ccd (although the latter is not a cdrom), > but not to matcd or wcd or non-cdrom disks. What about having ./MAKEDEV cd0 cd1 cd4 -da2 da6-da9 create cd0, cd1, cd4, da1, da2, da6, da7, da8, da9 ? This would be a generic solution that still allows for holes. Not possible because of compatibility issues? I'm willing to give it a go. Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 20:23:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 0A8C014C2D; Fri, 31 Dec 1999 20:23:52 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B88521CA0; Sat, 1 Jan 2000 12:23:48 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jeroen C. van Gelderen" Cc: Bruce Evans , Chuck Robey , Brian Fundakowski Feldman , FreeBSD-current@FreeBSD.ORG Subject: Re: multiple cd devices In-Reply-To: Message from "Jeroen C. van Gelderen" of "Fri, 31 Dec 1999 17:48:48 -0400." <386D24C0.118C1980@vangelderen.org> Date: Sat, 01 Jan 2000 12:23:48 +0800 From: Peter Wemm Message-Id: <20000101042348.B88521CA0@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeroen C. van Gelderen" wrote: > Bruce Evans wrote: > > > > On Fri, 31 Dec 1999, Chuck Robey wrote: > > > > > Why are "certain" devices wildly different than all other ones? I've > > > > Because the CAM update broke (SCSI) cd devices in rev.1.171 of MAKEDEV. > > mcd and scd were in the same case statement so they were broken too. The > > breakage has spread to acd and ccd (although the latter is not a cdrom), > > but not to matcd or wcd or non-cdrom disks. > > What about having > ./MAKEDEV cd0 cd1 cd4 -da2 da6-da9 > create cd0, cd1, cd4, da1, da2, da6, da7, da8, da9 ? This would be > a generic solution that still allows for holes. Not possible because > of compatibility issues? I'm willing to give it a go. "Send patches" :-) Seriously, the ultimate solution is a devfs-like system. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 20:36:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from rina.r.dl.itc.u-tokyo.ac.jp (rina.r.dl.itc.u-tokyo.ac.jp [133.11.199.247]) by hub.freebsd.org (Postfix) with ESMTP id A580E14CAD for ; Fri, 31 Dec 1999 20:36:38 -0800 (PST) (envelope-from tanimura@r.dl.itc.u-tokyo.ac.jp) Received: (from uucp@localhost) by rina.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W-r-0.1-19990829) with UUCP id NAA70053; Sat, 1 Jan 2000 13:36:35 +0900 (JST) Received: from silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (tanimura@localhost [127.0.0.1]) by silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id NAA10870; Sat, 1 Jan 2000 13:35:42 +0900 (JST) Date: Sat, 01 Jan 2000 13:35:41 +0900 Message-ID: <14445.33821.200059.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> From: Seigo Tanimura To: dmmiller@cvzoom.net Cc: current@freebsd.org Subject: Re: Newpcm is broken again for mpg123 (ESS 1868 isa sound card) In-Reply-To: In your message of "Wed, 29 Dec 1999 20:38:48 -0500" <386AB7A8.DC369061@cvzoom.net> References: <14429.46098.1195.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14433.63218.157116.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <386278C7.B748EEF5@cvzoom.net> <14434.52947.683451.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14436.13492.839612.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <14439.4177.642029.72159A@rina.r.dl.itc.u-tokyo.ac.jp> <14439.26155.338725.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> <386AB7A8.DC369061@cvzoom.net> Cc: Seigo Tanimura User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.4 (Terai) FLIM/1.12.7 (=?ISO-8859-4?Q?Y=FEzaki?=) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: Carrots MIME-Version: 1.0 (generated by SEMI 1.13.4 - "Terai") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 29 Dec 1999 20:38:48 -0500, Donn Miller said: Donn> I just recently did another cvsup, and now newpcm is broken Donn> again. When I try to play a clip with mpg123, I hear a very Donn> short burst of the beginning of the clip repeated indefinitely, Donn> like so: Donn> "ba ba ba ba ba ba ba ba ba ba ba ba ba ba". I have the ESS Donn> 1868, of course. Well, I (wisely) saved my old kernel as Donn> /kernel.good and just booted into that. Donn> Could you also say what was fixed if you get around to it? I'd Donn> to learn a little more about the sound driver. The following things were in the recent mail of mine: - All ioctl(2)s go to see the secondary buffer(if I have forget nothing). - chn_setblocksize() changes the size of the secondary buffer. - chn_mmap() maps the secondary buffer. - chn_poll() invokes DMA. - chn_wrintr() performs DMA emulation for pcm devices with no DMA functionality(requested by nyan). - SNDCTL_DSP_SETFRAGMENT handles the count correctly. - GETI/OSPACE returns the number of fragments. - DMA transfer keeps running upon underrun. Some DSPs seem to end up with an unpredictable result if the DMA gets stopped followed by immediate restart. This revokes the change in sys/dev/sound/pcm/channel.c rev 1.12. - chn_write() and chn_read() returns EAGAIN for nonblocking if there are no space to write or data to read. You can add something like: printf("chn_write: writing %d bytes, bs->fl = %d, bs->rl = %d, b->fl = %d, b->rl = %d, b->dl = %d\n", buf->uio_resid, bs->fl, bs->rl, b->fl, b->rl, b->dl); to see the state of the buffers, especially before and after triggering DMA transfer(around chn_{wr,rd}intr()) or feeding(around chn_{wr,rd}feed()). A positive value of b->dl shows that DMA transfer is taking place. -- Seigo Tanimura To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 20:51:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by hub.freebsd.org (Postfix) with ESMTP id 7F62A14F23 for ; Fri, 31 Dec 1999 20:51:07 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 124GVN-000BFy-0B; Sat, 1 Jan 2000 04:51:05 +0000 Received: from nenya (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id D026ED913; Sat, 1 Jan 2000 04:52:23 +0000 (GMT) Message-ID: <001f01bf5414$02bbbb80$0304020a@rings> From: "Cameron Grant" To: "Seigo Tanimura" , Cc: , "Seigo Tanimura" References: <14429.46098.1195.72159A@rina.r.dl.itc.u-tokyo.ac.jp><14433.63218.157116.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp><386278C7.B748EEF5@cvzoom.net><14434.52947.683451.72159A@rina.r.dl.itc.u-tokyo.ac.jp><14436.13492.839612.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp><14439.4177.642029.72159A@rina.r.dl.itc.u-tokyo.ac.jp><14439.26155.338725.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp><386AB7A8.DC369061@cvzoom.net> <14445.33821.200059.72159A@silver.carrots.uucp.r.dl.itc.u-tokyo.ac.jp> Subject: Re: Newpcm is broken again for mpg123 (ESS 1868 isa sound card) Date: Sat, 1 Jan 2000 04:52:30 -0000 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 5.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Donn> "ba ba ba ba ba ba ba ba ba ba ba ba ba ba". I have the ESS > Donn> 1868, of course. Well, I (wisely) saved my old kernel as > Donn> /kernel.good and just booted into that. > > Donn> Could you also say what was fixed if you get around to it? I'd > Donn> to learn a little more about the sound driver. > The following things were in the recent mail of mine: > > - All ioctl(2)s go to see the secondary buffer(if I have forget nothing). > - chn_setblocksize() changes the size of the secondary buffer. > - chn_mmap() maps the secondary buffer. > - chn_poll() invokes DMA. > - chn_wrintr() performs DMA emulation for pcm devices with no DMA > functionality(requested by nyan). > - SNDCTL_DSP_SETFRAGMENT handles the count correctly. > - GETI/OSPACE returns the number of fragments. > - DMA transfer keeps running upon underrun. Some DSPs seem to end up > with an unpredictable result if the DMA gets stopped followed by > immediate restart. This revokes the change in sys/dev/sound/pcm/channel.c > rev 1.12. > - chn_write() and chn_read() returns EAGAIN for nonblocking if there > are no space to write or data to read. the ess problem was a result of me reducing the buffer size to 8k instead of 64k to see what would happen. only ess cards seem to have problems, so it's back to 64k for them but 8k for other isa cards. - cameron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 20:55:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 2E9F014FF5 for ; Fri, 31 Dec 1999 20:55:37 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id WAA08012 for current@freebsd.org; Fri, 31 Dec 1999 22:55:35 -0600 (CST) Message-ID: <19991231225535.A8004@Denninger.Net> Date: Fri, 31 Dec 1999 22:55:35 +875400 From: Karl Denninger To: current@freebsd.org Subject: xntpd - VERY old folks, how about updating? :-) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is not a port, its part of the RELEASE! Its several YEARS old, and doesn't work right - you get lots of STEP changes instead of what you SHOULD get, which is a slew on the system clock. The new code (which has a current release date of this month) DOES appear to work correctly (I'm still verifying it, but it's certainly better than what is in the tree right now!) What does (someone) need to do to get this changed out/updated? I can't send it in as a port, since its part of the base package (setting it up as a port would be pretty trivial from what I can see) -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 21: 0:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id AA19C14CCA for ; Fri, 31 Dec 1999 21:00:07 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA16436; Sat, 1 Jan 2000 15:29:53 +1030 (CST) Date: Sat, 1 Jan 2000 15:29:53 +1030 From: Greg Lehey To: Karl Denninger Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <20000101152953.M1528@freebie.lemis.com> References: <19991231225535.A8004@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991231225535.A8004@Denninger.Net> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Wednesday, 29 December 1999 at 6:55:35 +2354, Karl Denninger wrote: > This is not a port, its part of the RELEASE! Well, yes, 3.4. But not -CURRENT. > Its several YEARS old, and doesn't work right - you get lots of STEP > changes instead of what you SHOULD get, which is a slew on the > system clock. > > The new code (which has a current release date of this month) DOES appear > to work correctly (I'm still verifying it, but it's certainly better > than what is in the tree right now!) > > What does (someone) need to do to get this changed out/updated? Nothing. > I can't send it in as a port, since its part of the base package > (setting it up as a port would be pretty trivial from what I can > see) When did you last update your -CURRENT? xntpd disappeared a couple of weeks ago. I'll bounce you some mail, since everybody else has read it. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 31 21:40:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 12B3314EDD; Fri, 31 Dec 1999 21:40:37 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id QAA19334; Sat, 1 Jan 2000 16:40:07 +1100 Date: Sat, 1 Jan 2000 16:39:46 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Jeroen C. van Gelderen" Cc: Chuck Robey , Brian Fundakowski Feldman , FreeBSD-current@FreeBSD.ORG Subject: Re: multiple cd devices In-Reply-To: <386D24C0.118C1980@vangelderen.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 31 Dec 1999, Jeroen C. van Gelderen wrote: > What about having > ./MAKEDEV cd0 cd1 cd4 -da2 da6-da9 > create cd0, cd1, cd4, da1, da2, da6, da7, da8, da9 ? This would be It's not the unix way. What's wrong with using standard utilities? sh MAKEDEV cd0 cd1 cd4 $(jot -w da 2) $(jot -w da 4 6) (`jot -w da 2' is bug for bug compatible with your expanded list because the default `begin' arg is 1, but disk numbers begin with 0, so -da2 should probably mean da0 da1 da2.) I can never remember syntaxes for rarely used commands like jot and MAKEDEV, so I would just type all the names if there are a small number of units, or use a shell loop for a large number of units. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message