From owner-freebsd-current Sun Apr 16 8:31:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from jhb-proxy.mweb.co.za (jhb-proxy.mweb.co.za [196.2.48.243]) by hub.freebsd.org (Postfix) with ESMTP id 493A637B584 for ; Sun, 16 Apr 2000 08:31:36 -0700 (PDT) (envelope-from rwgoosen@mweb.co.za) Received: from ami (cpt-dial-196-30-179-141.mweb.co.za) by jhb-proxy.mweb.co.za (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with SMTP id <0FT4004B98GCYE@jhb-proxy.mweb.co.za> for freebsd-current@FreeBSD.ORG; Sun, 16 Apr 2000 17:31:25 +0200 (GMT-2) Date: Sun, 16 Apr 2000 17:31:22 +0200 From: Ryan Subject: Help with OpenSSH To: freebsd-current@FreeBSD.ORG Reply-To: Ryan Message-id: <004601bfa7b8$d2bebd80$8db31ec4@ami> MIME-version: 1.0 X-Mailer: Microsoft Outlook Express 5.00.2615.200 Content-type: multipart/alternative; boundary="----=_NextPart_000_0043_01BFA7C9.9554F020" X-MSMail-Priority: High X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Priority: 1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0043_01BFA7C9.9554F020 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi there I was tryint to install OpenSSH , so i did the following=20 cd /usr/ports/security/openssh then make install=20 and it said I needed the OpenSSL Library I then cd'd into the /usr/ports/security/openssl And tried to install it when it said that its Forbidden cause it already = is installed in base system !! So How do i install OpenSSH with this problem or how do i over come it ? I'm Using FreeBSD RELEASE 4.0 Thanks for the help Ryan=20 ------=_NextPart_000_0043_01BFA7C9.9554F020 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi there

I was tryint to install OpenSSH , so i = did the=20 following

cd = /usr/ports/security/openssh

then make install

and it said I needed the OpenSSL=20 Library

I then cd'd into the=20 /usr/ports/security/openssl

And tried to install it when it said = that its=20 Forbidden cause it already is installed in base system !!

So How do i install OpenSSH with this = problem or=20 how do i over come it ?

I'm Using FreeBSD RELEASE = 4.0

Thanks for the help

Ryan

------=_NextPart_000_0043_01BFA7C9.9554F020-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 8:58:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 24A1337B819 for ; Sun, 16 Apr 2000 08:58:39 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 16 Apr 2000 16:58:31 +0100 (BST) Date: Sun, 16 Apr 2000 16:58:29 +0100 From: David Malone To: Ryan Cc: freebsd-current@FreeBSD.ORG Subject: Re: Help with OpenSSH Message-ID: <20000416165829.A81674@walton.maths.tcd.ie> References: <004601bfa7b8$d2bebd80$8db31ec4@ami> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <004601bfa7b8$d2bebd80$8db31ec4@ami>; from rwgoosen@mweb.co.za on Sun, Apr 16, 2000 at 05:31:22PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 16, 2000 at 05:31:22PM +0200, Ryan wrote: > So How do i install OpenSSH with this problem or how do i over come it ? > I'm Using FreeBSD RELEASE 4.0 OpenSSH is a builtin part of 4.0. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 10: 2:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id CC72237B94E for ; Sun, 16 Apr 2000 10:02:46 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 20416 invoked by uid 1001); 16 Apr 2000 17:02:45 -0000 Date: Sun, 16 Apr 2000 13:02:45 -0400 From: Brian Reichert To: Ryan Cc: freebsd-current@FreeBSD.ORG Subject: Re: Help with OpenSSH Message-ID: <20000416130245.A20339@numachi.com> References: <004601bfa7b8$d2bebd80$8db31ec4@ami> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <004601bfa7b8$d2bebd80$8db31ec4@ami>; from rwgoosen@mweb.co.za on Sun, Apr 16, 2000 at 05:31:22PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 16, 2000 at 05:31:22PM +0200, Ryan wrote: > Hi there > > I was tryint to install OpenSSH , so i did the following > > And tried to install it when it said that its Forbidden cause it already is installed in base system !! > So How do i install OpenSSH with this problem or how do i over come it ? > > I'm Using FreeBSD RELEASE 4.0 FreeBSD 4.0 ships with OpenSSH, but you need to install the CRYPTO distribution, with at least 'crypto', the basic services. It's not really in the 'base' system. If you install a mininal setup, you don't get it. Just found that out myself... :/ > Thanks for the help > Ryan -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Daytime number: (781) 273-4100 x161 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 10: 6:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 920AB37BC48 for ; Sun, 16 Apr 2000 10:06:18 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 20454 invoked by uid 1001); 16 Apr 2000 17:06:17 -0000 Date: Sun, 16 Apr 2000 13:06:17 -0400 From: Brian Reichert To: Ryan Cc: freebsd-current@FreeBSD.ORG Subject: Re: Help with OpenSSH Message-ID: <20000416130616.B20339@numachi.com> References: <004601bfa7b8$d2bebd80$8db31ec4@ami> <20000416130245.A20339@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <20000416130245.A20339@numachi.com>; from reichert@numachi.com on Sun, Apr 16, 2000 at 01:02:45PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 16, 2000 at 01:02:45PM -0400, Brian Reichert wrote: > FreeBSD 4.0 ships with OpenSSH, but you need to install the CRYPTO > distribution, with at least 'crypto', the basic services. > > It's not really in the 'base' system. If you install a mininal > setup, you don't get it. > > Just found that out myself... :/ Ha! I got further bit. You need to install the base system, the crypto distribution _and_ the rsaref-2.0 package... -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Daytime number: (781) 273-4100 x161 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 10:32:20 2000 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 B951837B5C7 for ; Sun, 16 Apr 2000 10:32:16 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 6684 invoked from network); 16 Apr 2000 17:32:14 -0000 Received: from lc210.cvzoom.net (208.226.154.210) by ns.cvzoom.net with SMTP; 16 Apr 2000 17:32:14 -0000 Date: Sun, 16 Apr 2000 13:32:10 -0400 (EDT) From: Donn Miller To: current@freebsd.org Subject: Parallel 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 ===> librsausa mkdir: openssl: File exists cp /usr/src/secure/lib/librsausa/../libcrypto/opensslconf-i386.h openssl/openssl conf.h *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 11:53:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail151.nifty.com (mail151.nifty.com [202.248.37.144]) by hub.freebsd.org (Postfix) with ESMTP id 6A05F37B953 for ; Sun, 16 Apr 2000 11:53:03 -0700 (PDT) (envelope-from dmdaiko@mbe.nifty.com) Received: from libretto by mail151.nifty.com (8.9.3+3.2W/3.7W-10/13/99) with SMTP id DAA26824 for ; Mon, 17 Apr 2000 03:53:00 +0900 Date: Mon, 17 Apr 2000 03:53:00 +0900 Message-Id: <200004161853.DAA26824@mail151.nifty.com> From: handwerk DM service To: Subject: =?ISO-2022-JP?B?GyRCIVY2WzVePnBKcxsoQg==?= !!=?ISO-2022-JP?B?GyRCRnxLXEgvJVMlQyUwJVclbSU4JSclLyVIO09GMBsoQg==?= =?ISO-2022-JP?B?GyRCGyhC?= !!=?ISO-2022-JP?B?GyRCIVcbKEI=?= MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP" Content-Transfer-Encoding: 7bit X-Mailer: Achi-Kochi Mail ver1.01 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------------------------------------------------------------- $B!!!!FMA3$N%a!=%k!"<:NiCW$7$^$9!#$<$R:G8e$^$G$*FI$_$/$@$5$$!#(B $B!!!!8fITMW$NJ}$K$O!"8fOM$SCW$7$^$9$H$H$b$K!"(B $B!!!!$3$N%a!<%k$r:o=|$7$F$/$@$5$$$^$9$h$&$*4j$$$$$?$7$^$9!#(B ------------------------------------------------------------- /////////////////////////////////////////////////////////////// $B!!6[5^>pJs(B!!$B!IF|K\H/!I!"%[!<%`%Z!<%8>R2p%S%8%M%9$$$h$$$h;OF0(B!! /////////////////////////////////////////////////////////////// $B!vF|K\H/!"@$3&$K8~$1$F$N%S%C%0%W%m%8%'%/%H(BStarWeb21!!$B!v(B $B6K$/:G6a%9%?!<%H$7$?$P$+$j$G$9!#:#$O$H$K$+$/2>EPO?$r$*5^$.2<$5$$!#(B $B!!2>EPO?$N0Y!"HqMQIiC4$J$7!#%j%9%/$O%<%m$G$9!#(B $B$7$+$b!"@lMQ%[!<%`%Z!<%8$h$j!"%j%"%k%?%$%`$GAH?%9=C[>u67$N3NG'$,2DG=(B!! $B@5<0;22C$O!J(B6$B7n%9%?!<%HM=Dj!K!":G=*$NAH?%?^$r3NG'$N>e$4H=CG2<$5$$!#(B $B!Z%S%8%M%935MW![(B $B!{(BHP$B$N%5%$%:$O(B20MB$B!#<+F0:n@.%=%U%HIU$J$N$G%o!<%W%m463P$G(BHP$B$,:n$l$^$9!#(B $B99$K!"(BCGI$B$d%\%$%9%a!<%kEy?tB?$/$N%5!<%S%9$,$D$$$FG/2qHq$O(B11,550$B1_!#(B $B!{%7%9%F%`$O(B2x2$B$N%P%$%J%j!<$J$N$G%9%?!<%H$HF1;~$K5^@.D9(B !! $B:#G/Cf$K$O2q0w$O(B20$BK|?M$rD6$($F%$%s%?!<%M%C%H$N2xJ*$K$J$j$=$&$G$9!#(B $B!{%P%C%/$O%$%s%?!<%M%C%H!"N.DL4X78$ND60lN.4k6H!#C1$J$k(BHP$B$NHNGd$G$O$"(B $B$j$^$;$s!#4k6H$H8D?M$N%3%_%e%K%1!<%7%g%s$rD>7k!>2q0w$b(BHP$B0J30$NB?$/$N(B $BFCE5$r5}(B $B!!6d9T?69~$G(BOK$B!>(B $B!!!p%A%'%C%/$NN>BX(B $B!{K\It$H$NO"Mm!"%5%]!<%H$bLdBj$J$7$G$9!#(B $B!}>\:Y$K$D$$$F$O!"%*%U%#%7%c%k%[!<%`%Z!<%8(B $B!!(Bhttp://www.starweb21.com $B!!$r$4;2>H2<$5$$!#(B $B!z2>EPO?4uK>e!"I,MW;v9`$rF~NO$7$F$*?=$79~$_2<$5$$!#(B $B!JEPO?%i%$%s$O!"<+F09=C[$5$l$k:8$r$*A&$aCW$7$^$9!#!K(B $B$=$N>l$G2>EPO?(BID$B5Z$S%Q%9%o!<%I!">R2p%S%8%M%9MQ%[!<%`%Z!<%8$,0!"2>EPO?$,40N;CW$7$^$7$?$i$4O"Mm2<$5$$!#:#8e$N%S%8%M%9$N?J$aJ}Ey$K$D$-!"$4(B $B@bL@$5$;$FD:$-$?$$$H;W$$$^$9!#(B $B$^$?!"%$%s%?!<%M%C%H$K@\B3=PMh$J$$J}$O!"2<5-%U%)!<%`$K$45-F~$N>e!"%a!<%k$K$F(B $B$*?=$79~$_2<$5$$!#(B ============================================================ $BEPO?%U%)!<%`(B $B%U%j%,%J!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!@-JL!!CK!&=w(B $B;aL>!!!!!!!!!!!!!!!!!!!!!!!!!!!!@8G/7nF|(B19$B!!!!G/!!!!7n!!!!F|(B $B2>EPO?F|!'!!!!!!7n!!!!F|(B $B")!!!!!!!!!!!!(B $B=;=j!'!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!(B $B#T#E#L!'!!!!!!!!!!!!!!!!!!!!!!!!#F#A#X!'(B $B#E%a!<%k(B $B!'(B: $B%3%_%C%7%g%spJs(B $B6d9TL>(B: $B;YE9L>(B: $B8}:B5A?M(B: $BM9JXCy6b$N>l9g(B $B5-9f(B: $BHV9f(B: $BL>5A?M(B: *$BL>5A?M$OEPO?r7o$G$9!#(B $B%K%C%/%M!<%`!'(B $B!!Bh0l4uK>(B $B!!BhFs4uK>(B $B!!Bh;04uK>(B *$BEPO?MQ%[!<%`%Z!<%8$N(BURL$B$N0lIt$K$J$j$^$9!#(B $B!J(Bhttp://www.starweb21.com/cp/$B%K%C%/%M!<%`$H$J$j$^$9!K(B $B$^$?!"AH?%?^$K$O!"%K%C%/%M!<%`$G5-:\$5$l$^$9!#(B $BI,$:$45-F~2<$5$$!#(B $B%K%C%/%M!<%`$G;HMQ$G$-$kJ8;z$O0J2<$NDL$j$G$9!#(B * $B1Q;z>.J8;z(B (a $B!A(B z) * $B?t;z(B (0 $B!A(B 9) * $B2<@~(B (_)$B$*$h$S%O%$%U%s(B(-) $B$J$*J8;z?t$O#2J8;z0J>e#1#6J8;z0JFb$G:G=i$NJ8;z$O1Q;z>.J8;z$H$7$F$/$@(B $B$5$$!#(B $B>R2p;&E~$GEPO?%[!<%`%Z!<%8$X$N%"%/%;%9$,=PMh$:!"%(%i!<$,IQH/$7$F(B $B!!$$$k>u67$G$9!#(B $B!!AH?%$N9=C[$OEPO?F|!&;~4V$N=gHV$H$J$j$^$9$N$G!"D|$a$:$K%H%i%$$7$F$_$F2<$5$$!#(B $B$I$&$7$F$bEPO?$G$-$J$$J}$O!">e5-EPO?%U%)!<%`$K$45-F~$N>e!"%a!<%k2<$5$$!#(B $B!!Ev%0%k!<%W@lMQ2>#I#DHV9f$rH/9T$7$^$9!#EvLL$O$3$N#I#DHV9f$r;H$$1D6H2<$5$$!#(B $B!!EPO?Be9T0MMj$,;&E~$7$F$*$j%*%U%#%7%c%k#I#D54j$$$^$9!#(B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 12:31:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id E7CAA37B9AD for ; Sun, 16 Apr 2000 12:31:24 -0700 (PDT) (envelope-from sam@inf.enst.fr) Received: from trillian.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 563CC19090; Sun, 16 Apr 2000 21:31:23 +0200 (CEST) Received: by trillian.enst.fr (Postfix, from userid 1000) id B0F4B118; Sun, 16 Apr 2000 21:31:20 +0200 (CEST) Date: Sun, 16 Apr 2000 21:31:20 +0200 To: Brian Reichert Cc: Ryan , freebsd-current@FreeBSD.ORG Subject: Re: Help with OpenSSH References: <004601bfa7b8$d2bebd80$8db31ec4@ami> <20000416130245.A20339@numachi.com> <20000416130616.B20339@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000416130616.B20339@numachi.com>; from reichert@numachi.com on Sun, Apr 16, 2000 at 01:06:17PM -0400 From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-04-16-21-31-20+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16/04, Brian Reichert wrote: | Ha! I got further bit. You need to install the base system, the | crypto distribution _and_ the rsaref-2.0 package... rsaref for a .za address? Didn't you mean rsaintl, openssl? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 12:43:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id C0B5F37B5D8 for ; Sun, 16 Apr 2000 12:43:36 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id OAA08209 for current@freebsd.org; Sun, 16 Apr 2000 14:47:25 -0500 (CDT) (envelope-from jlemon) Date: Sun, 16 Apr 2000 14:47:25 -0500 From: Jonathan Lemon To: current@freebsd.org Subject: HEADS UP; kq related changes Message-ID: <20000416144725.C1164@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just committed kq support to the tree. The first thing I forgot to mention in the commit log is that the size of `struct proc' changed, so a full buildworld is in order. Second, a man page is forthcoming, so if you're looking for that, wait a day or two. (I'm better at writing code than man pages, but will be happy to answer questions about this). -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 12:46:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 76C2A37BA48 for ; Sun, 16 Apr 2000 12:46:10 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 21481 invoked by uid 1001); 16 Apr 2000 19:46:06 -0000 Date: Sun, 16 Apr 2000 15:46:06 -0400 From: Brian Reichert To: Samuel Tardieu Cc: Brian Reichert , Ryan , freebsd-current@FreeBSD.ORG Subject: Re: Help with OpenSSH Message-ID: <20000416154606.C20339@numachi.com> References: <004601bfa7b8$d2bebd80$8db31ec4@ami> <20000416130245.A20339@numachi.com> <20000416130616.B20339@numachi.com> <2000-04-16-21-31-20+trackit+sam@inf.enst.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <2000-04-16-21-31-20+trackit+sam@inf.enst.fr>; from sam@inf.enst.fr on Sun, Apr 16, 2000 at 09:31:20PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 16, 2000 at 09:31:20PM +0200, Samuel Tardieu wrote: > On 16/04, Brian Reichert wrote: > > | Ha! I got further bit. You need to install the base system, the > | crypto distribution _and_ the rsaref-2.0 package... > > rsaref for a .za address? Didn't you mean rsaintl, openssl? Hmm, perhaps. Put, what i was pointing out, was, that for me, OpenSSH was _not_ in 'the base system'; I had to pull a few components together to make it so... -- Brian 'you Bastard' Reichert reichert@numachi.com 37 Crystal Ave. #303 Daytime number: (781) 273-4100 x161 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 13:15:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 408C037B856; Sun, 16 Apr 2000 13:15:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA81081; Sun, 16 Apr 2000 13:15:15 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 16 Apr 2000 13:15:15 -0700 (PDT) From: Kris Kennaway To: Brian Reichert Cc: Ryan , freebsd-current@FreeBSD.ORG Subject: Re: Help with OpenSSH In-Reply-To: <20000416130616.B20339@numachi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 16 Apr 2000, Brian Reichert wrote: > Ha! I got further bit. You need to install the base system, the > crypto distribution _and_ the rsaref-2.0 package... Only if you're in the US. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 14: 4:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 13C0937B953 for ; Sun, 16 Apr 2000 14:04:31 -0700 (PDT) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id VAA10488 for current@freebsd.org; Wed, 19 Apr 2000 21:40:44 -0500 (CDT) From: Joe Greco Message-Id: <200004200240.VAA10488@aurora.sol.net> Subject: OpenSSH and PAM To: current@freebsd.org Date: Wed, 19 Apr 2000 21:40:44 -0500 (CDT) 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 While I realize that 4.0 has PAM'ified SSH, I was wondering if anyone was planning to extend this in the manner that telnet/rlogin have been. From /etc/pam.d/login: auth sufficient pam_tacplus.so try_first_pass template_user=staffer Basically this'll grab the "staffer" account and use it as the basis for other arbitrary users who have been authenticated by TACACS. Very handy at an ISP where you may wish to allow or disallow access to many servers to a large number of individuals who tend to come and go. The people who don't _really_ need to access the machines on a daily basis just get a TACACS login and they get to live with the "template" user's dotfiles etc. Unfortunately, sshd does some explicit checks with getpwnam() that cause ssh connectins to fail if the user is not in /etc/passwd, and there are probably other issues as well. Any ssh hackers looking at this, by any chance? -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 15:37:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 39F6B37B625; Sun, 16 Apr 2000 15:37:34 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA94024; Sun, 16 Apr 2000 15:37:33 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 16 Apr 2000 15:37:32 -0700 (PDT) From: Kris Kennaway To: Donn Miller Cc: current@freebsd.org Subject: Re: Parallel make world 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 On Sun, 16 Apr 2000, Donn Miller wrote: > ===> librsausa > mkdir: openssl: File exists > cp /usr/src/secure/lib/librsausa/../libcrypto/opensslconf-i386.h > openssl/openssl > conf.h > *** Error code 1 What -j setting? This works fine for me. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 16: 9:18 2000 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 43B7437B69F for ; Sun, 16 Apr 2000 16:09:14 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 28867 invoked from network); 16 Apr 2000 23:09:13 -0000 Received: from lc210.cvzoom.net (208.226.154.210) by ns.cvzoom.net with SMTP; 16 Apr 2000 23:09:13 -0000 Date: Sun, 16 Apr 2000 19:09:09 -0400 (EDT) From: Donn Miller To: Kris Kennaway Cc: current@freebsd.org Subject: Re: Parallel make world 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 On Sun, 16 Apr 2000, Kris Kennaway wrote: > On Sun, 16 Apr 2000, Donn Miller wrote: > > > ===> librsausa > > mkdir: openssl: File exists > > cp /usr/src/secure/lib/librsausa/../libcrypto/opensslconf-i386.h > > openssl/openssl > > conf.h > > *** Error code 1 > > What -j setting? This works fine for me. I used make -j6 buildworld. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 17:16:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id AFBB037B625 for ; Sun, 16 Apr 2000 17:16:25 -0700 (PDT) (envelope-from helpdesk@bigpond.net.au) Received: from pc (CPE-144-132-206-82.nsw.bigpond.net.au [144.132.206.82]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id KAA18250 for ; Mon, 17 Apr 2000 10:16:12 +1000 (EST) Message-ID: <001401bfa802$224a9f60$52ce8490@nsw.bigpond.net.au> From: "Telstra Bigpond Advance Helpdesk" To: Subject: Test Date: Mon, 17 Apr 2000 10:16:09 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 18:32:16 2000 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 9EE0137B7E8 for ; Sun, 16 Apr 2000 18:32:08 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 28160 invoked from network); 17 Apr 2000 01:30:18 -0000 Received: from lc210.cvzoom.net (HELO cvzoom.net) (208.226.154.210) by ns.cvzoom.net with SMTP; 17 Apr 2000 01:30:18 -0000 Message-ID: <38FA6929.62FEC52F@cvzoom.net> Date: Sun, 16 Apr 2000 21:30:17 -0400 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: kernel link errors Content-Type: multipart/mixed; boundary="------------3404B81D515F7872AF80C9CC" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------3404B81D515F7872AF80C9CC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit With a fresh cvsup as of 1/2 hour ago, I get the following link errors during the link stage of the kernel build. (Please see attached file.) - Donn --------------3404B81D515F7872AF80C9CC Content-Type: text/plain; charset=us-ascii; name="make.log" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="make.log" linking kernel init_sysent.o(.data+0xb54): undefined reference to `kqueue' init_sysent.o(.data+0xb5c): undefined reference to `kevent' kern_descrip.o: In function `close': kern_descrip.o(.text+0x85c): undefined reference to `knote_fdclose' kern_exec.o: In function `execve': kern_exec.o(.text+0x4fb): undefined reference to `knote' kern_exit.o: In function `exit1': kern_exit.o(.text+0x46e): undefined reference to `knote' kern_fork.o: In function `fork1': kern_fork.o(.text+0x811): undefined reference to `knote' kern_sig.o: In function `psignal': kern_sig.o(.text+0x1082): undefined reference to `knote' sys_pipe.o: In function `pipe_read': sys_pipe.o(.text+0x599): undefined reference to `knote' sys_pipe.o(.text+0x9af): more undefined references to `knote' follow vfs_aio.o: In function `aio_free_entry': vfs_aio.o(.text+0x2eb): undefined reference to `knote_remove' vfs_aio.o: In function `aio_daemon': vfs_aio.o(.text+0xc6b): undefined reference to `knote' vfs_aio.o: In function `aio_qphysio': vfs_aio.o(.text+0x1155): undefined reference to `knote' vfs_aio.o: In function `_aio_aqueue': vfs_aio.o(.text+0x16fc): undefined reference to `kqueue_register' vfs_aio.o: In function `aio_physwakeup': vfs_aio.o(.text+0x1bcd): undefined reference to `knote' ffs_vnops.o: In function `ffs_write': ffs_vnops.o(.text+0x8f9): undefined reference to `knote' ufs_vnops.o: In function `ufs_create': ufs_vnops.o(.text+0xf1): undefined reference to `knote' ufs_vnops.o: In function `ufs_mknod': ufs_vnops.o(.text+0x14a): undefined reference to `knote' ufs_vnops.o: In function `ufs_setattr': ufs_vnops.o(.text+0x78b): undefined reference to `knote' ufs_vnops.o(.text+0x943): more undefined references to `knote' follow *** Error code 1 Stop in /usr/src/sys/compile/CUSTOM. --------------3404B81D515F7872AF80C9CC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 18:36:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.snickers.org (mail.snickers.org [216.126.90.4]) by hub.freebsd.org (Postfix) with ESMTP id 0413837B60F for ; Sun, 16 Apr 2000 18:36:36 -0700 (PDT) (envelope-from josh@snickers.org) Received: by mail.snickers.org (Postfix, from userid 1037) id 4562F3D1F; Sun, 16 Apr 2000 21:36:11 -0400 (EDT) Date: Sun, 16 Apr 2000 21:36:11 -0400 From: Josh Tiefenbach To: Donn Miller Cc: current@freebsd.org Subject: Re: kernel link errors Message-ID: <20000416213610.A85081@snickers.org> References: <38FA6929.62FEC52F@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <38FA6929.62FEC52F@cvzoom.net> Organization: Hah Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 16, 2000 at 09:30:17PM -0400, Donn Miller wrote: > With a fresh cvsup as of 1/2 hour ago, I get the following link errors > during the link stage of the kernel build. (Please see attached > file.) Try re-config/re-compiling your kernel after adding the following line to /sys/conf/files: kern/kern_event.c standard josh -- Give me rampant intellectualism as a coping strategy! -- Chuck Palahniuk in Invisible Monsters To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 20: 0:51 2000 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 4A54337B901 for ; Sun, 16 Apr 2000 20:00:48 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 14737 invoked from network); 17 Apr 2000 03:00:36 -0000 Received: from lc210.cvzoom.net (HELO cvzoom.net) (208.226.154.210) by ns.cvzoom.net with SMTP; 17 Apr 2000 03:00:36 -0000 Message-ID: <38FA7E54.A996D422@cvzoom.net> Date: Sun, 16 Apr 2000 23:00:36 -0400 From: Donn Miller X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Josh Tiefenbach Cc: current@freebsd.org Subject: Re: kernel link errors References: <38FA6929.62FEC52F@cvzoom.net> <20000416213610.A85081@snickers.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josh Tiefenbach wrote: > > On Sun, Apr 16, 2000 at 09:30:17PM -0400, Donn Miller wrote: > > With a fresh cvsup as of 1/2 hour ago, I get the following link errors > > during the link stage of the kernel build. (Please see attached > > file.) > > Try re-config/re-compiling your kernel after adding the following line to > /sys/conf/files: > > kern/kern_event.c standard That fixed it. Can someone please commit the changes? - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 20: 7:12 2000 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 C33B237B79E for ; Sun, 16 Apr 2000 20:07:08 -0700 (PDT) (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 VAA49541; Sun, 16 Apr 2000 21:07:06 -0600 (MDT) (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 VAA67541; Sun, 16 Apr 2000 21:06:39 -0600 (MDT) Message-Id: <200004170306.VAA67541@harmony.village.org> To: Donn Miller Subject: Re: kernel link errors Cc: Josh Tiefenbach , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 16 Apr 2000 23:00:36 EDT." <38FA7E54.A996D422@cvzoom.net> References: <38FA7E54.A996D422@cvzoom.net> <38FA6929.62FEC52F@cvzoom.net> <20000416213610.A85081@snickers.org> Date: Sun, 16 Apr 2000 21:06:39 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38FA7E54.A996D422@cvzoom.net> Donn Miller writes: : > kern/kern_event.c standard : : That fixed it. Can someone please commit the changes? Done. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 22:50:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 0466237B9B4 for ; Sun, 16 Apr 2000 22:50:33 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id WAA62787 for ; Sun, 16 Apr 2000 22:50:31 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id WAA00621 for current@freebsd.org; Sun, 16 Apr 2000 22:50:31 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200004170550.WAA00621@realtime.exit.com> Subject: Re: Sound Blaster Live! 4.0 To: current@freebsd.org Date: Sun, 16 Apr 2000 22:50:31 -0700 (PDT) Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL68 (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 (Forwarding this to -current; I think it's relevant there since 4-stable and -current haven't diverged _that_ much. Yet.) Frank Mayhar wrote: > Bryan Bradsby wrote: > > > Do _you_ have ECC memory? > > Nope. > > So far, of the folks I've polled, the ones that have had success (with the > SBLive driver) have _not_ had ECC memory. The one report of failure _was_ > using ECC memory. > > Sounds like serious driver trouble to me, and like the folks that aren't > having trouble may have weird failures in the future as their memory gets > tromped. -- Frank Mayhar frank@exit.com http://www.exit.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 16 23:18:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from ws-ilmar.ints.ru (ws-ilmar.ints.ru [194.67.173.16]) by hub.freebsd.org (Postfix) with ESMTP id 480EB37B755 for ; Sun, 16 Apr 2000 23:18:23 -0700 (PDT) (envelope-from ilmar@ws-ilmar.ints.ru) Received: (from ilmar@localhost) by ws-ilmar.ints.ru (8.9.3/8.9.3) id KAA33333 for freebsd-current@freebsd.org; Mon, 17 Apr 2000 10:18:21 +0400 (MSD) Date: Mon, 17 Apr 2000 10:18:21 +0400 (MSD) From: "Ilmar S. Habibulin" Message-Id: <200004170618.KAA33333@ws-ilmar.ints.ru> To: freebsd-current@freebsd.org Subject: fs subdir Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why not to move all fs code (ufs, procfs, isofs, etc) to /sys/fs? It allready contain hpfs subdir. What you guys think about it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 0: 7:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 84B4C37B65B for ; Mon, 17 Apr 2000 00:07:55 -0700 (PDT) (envelope-from julian@elischer.org) Received: from popserver-02.iinet.net.au (popserver-02.iinet.net.au [203.59.24.148]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id PAA32022; Mon, 17 Apr 2000 15:07:50 +0800 Received: from jules.elischer.org (reggae-11-228.nv.iinet.net.au [203.59.69.228]) by popserver-02.iinet.net.au (8.9.3/8.9.3) with SMTP id PAA18481; Mon, 17 Apr 2000 15:07:47 +0800 Message-ID: <38FAB82B.2781E494@elischer.org> Date: Mon, 17 Apr 2000 00:07:23 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: "Ilmar S. Habibulin" Cc: freebsd-current@freebsd.org Subject: Re: fs subdir References: <200004170618.KAA33333@ws-ilmar.ints.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ilmar S. Habibulin wrote: > > Why not to move all fs code (ufs, procfs, isofs, etc) to /sys/fs? It allready > contain hpfs subdir. What you guys think about it? This has been discussed and considered a GOOD IDEA but it hasn't happenned yet. there is also teh miscfs directory that could be consolidated too. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 7: 1:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id DEA1737B85B for ; Mon, 17 Apr 2000 07:01:27 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Mon, 17 Apr 2000 10:01:01 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: current@FreeBSD.org Subject: Anyone have OpenSSH + X11-fwd working? 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 not able to get X11 connection forwarding to work anymore. I've tracked it down to the packet sent for SSH_CHANNEL_X11_OPEN being completely bogus, therefore trying to extract the "proto" and "data" fails, and the connection doesn't work. Has anyone tried it recently and gotten it to work? I'd also be interested in people who have not gotten it to work and get the error message about an "invalid protocol". -- 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 Mon Apr 17 7:14:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.13.27]) by hub.freebsd.org (Postfix) with ESMTP id 3A58F37B693; Mon, 17 Apr 2000 07:14:23 -0700 (PDT) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id PAA00445; Mon, 17 Apr 2000 15:20:51 +0100 (IST) (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: Date: Mon, 17 Apr 2000 15:20:51 +0100 (IST) From: "Steve O'Hara-Smith" To: Brian Fundakowski Feldman Subject: RE: Anyone have OpenSSH + X11-fwd working? Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Apr-00 Brian Fundakowski Feldman wrote: > I'm not able to get X11 connection forwarding to work anymore. Just a data point, it works fine in 4-stable (about a week old). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 7:19:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail3.post.kek.jp (mail3.post.kek.jp [130.87.41.20]) by hub.freebsd.org (Postfix) with ESMTP id 9ED9837B770 for ; Mon, 17 Apr 2000 07:19:14 -0700 (PDT) (envelope-from yosimoto@post.kek.jp) Received: from darwin.kek.jp (darwin.kek.jp [130.87.85.49]) by mail3.post.kek.jp (8.9.3/3.6W98031818) with ESMTP id XAA29171 for ; Mon, 17 Apr 2000 23:19:12 +0900 (JST) Mime-Version: 1.0 X-Sender: yosimoto@pop.post.kek.jp X-Mailer: Macintosh Eudora Pro Version 4.2.2-Jb2-5.100 Message-Id: In-Reply-To: References: Date: Mon, 17 Apr 2000 23:19:11 +0900 To: freebsd-current@freebsd.org From: Shin-ichi YOSHIMOTO Subject: Re: Anyone have OpenSSH + X11-fwd working? Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:01 -0400 04/17/2000, Brian Fundakowski Feldman wrote: > Has anyone tried it recently and gotten it to work? Yes, sure. Check your config file. $ cat ~/.ssh/config | grep ^ForwardX11 ForwardX11 yes ---------------------------------------------------------- KEK, High Energy Accelerator Research Organization Accelerator Laboratory Shin-ichi YOSHIMOTO To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 8:23:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id D415637B81B for ; Mon, 17 Apr 2000 08:23:18 -0700 (PDT) (envelope-from sam@antinea.enst.fr) Received: from trillian.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 83CE51905C; Mon, 17 Apr 2000 17:23:16 +0200 (CEST) Received: by trillian.enst.fr (Postfix, from userid 1000) id 4179D11B; Mon, 17 Apr 2000 17:23:00 +0200 (CEST) To: Robert Watson Cc: freebsd-current@freebsd.org Subject: Re: middle mouse button emulation broken in 4.0-STABLE? References: Date: 17 Apr 2000 17:22:59 +0200 In-Reply-To: Robert Watson's message of "Fri, 14 Apr 2000 12:11:18 -0400 (EDT)" Lines: 21 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Canyonlands" From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 Message-Id: <2000-04-17-17-23-00+trackit+sam@antinea.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Robert" == Robert Watson writes: Robert> Not sure if this should go to -current or -stable, since we Robert> seem to get a lot of instant MFC's these days :-). I upgraded Robert> a notebook from 4.0-RELEASE to -STABLE last night. After Robert> doing so, I noticed that the middle mouse button emulation in Robert> moused seems to be fairly broken -- i.e., once it's enabled, I Robert> can no longer drag with the left mouse button (although I can Robert> with the emulated middle button). If I turn off emulation, Robert> the left and right buttons drag normally, but now I can no Robert> longer paste in X :-). This has been fixed in both -STABLE and -CURRENT a week ago. The left button is working, the timeout is just to long. Read moused manpage and set the timeout to 200ms as a workaround (this is the default according to the manpage, but not according to the code in 4.0-RELEASE). Sam -- Samuel Tardieu -- sam@inf.enst.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 10:22:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from Draculina.otdel-1.org (Draculina.Otdel-1.ORG [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 8ECC937B91F for ; Mon, 17 Apr 2000 10:22:39 -0700 (PDT) (envelope-from nms@otdel-1.org) Received: by Draculina.otdel-1.org (Postfix, from userid 1002) id 822E497; Mon, 17 Apr 2000 21:22:36 +0400 (MSD) Date: Mon, 17 Apr 2000 21:22:36 +0400 From: Nikolai Saoukh To: freebsd-current@freebsd.org Subject: link_elf: symbol ISA_PNP_PROBE undefined Message-ID: <20000417212236.A1187@Draculina.otdel-1.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG An attempt to kldload driver suddenly failed with message from Subject. Everything was ok before. Sources cvsuped hour ago, kernel and driver recompiled. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 10:42:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from MexComUSA.Net (adsl-63-200-120-86.dsl.mtry01.pacbell.net [63.200.120.86]) by hub.freebsd.org (Postfix) with ESMTP id 4332537B94B for ; Mon, 17 Apr 2000 10:42:23 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Received: from EnContacto.Net (adsl-63-200-120-84.dsl.mtry01.pacbell.net [63.200.120.84]) by MexComUSA.Net (8.9.3/8.9.3) with ESMTP id KAA12408; Mon, 17 Apr 2000 10:41:35 -0700 (PDT) (envelope-from eculp@EnContacto.Net) Message-ID: <38FB4CC8.8C238233@EnContacto.Net> Date: Mon, 17 Apr 2000 10:41:28 -0700 From: Edwin Culp Organization: MexComUSA.Net/EnContacto.Net X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Hay Cc: Warner Losh , Michael Vasilenko , freebsd-current@FreeBSD.ORG Subject: Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles References: <200004150819.KAA95650@zibbi.mikom.csir.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Hay wrote: > > : Are there any datasheets available for this bridge ? > > > > Yes. However, I've had several reports of the lucent wavelan bridge > > working flawlessly. > > I recall (but might be wrong) that most if not all sucess stories are > on notebooks with the TI-1225 on the motherboard. Maybe the notebook > bios do something more than isn't done on a normal pc? My TI-1220 works flawlessly. ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 10:57: 9 2000 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 AF61737B770 for ; Mon, 17 Apr 2000 10:57:05 -0700 (PDT) (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 TAA15605; Mon, 17 Apr 2000 19:57:01 +0200 (MET DST) From: Oliver Schonefeld Received: by frizzantino.TechFak.Uni-Bielefeld.DE (SMI-8.6/pk970604A) id TAA02386; Mon, 17 Apr 2000 19:57:00 +0200 Date: Mon, 17 Apr 2000 19:57:00 +0200 To: "Viren R.Shah" Cc: "Matthew N. Dodd" , freebsd-current@FreeBSD.ORG, Ian Cartwright Subject: Re: cvs commit: src/sys/dev/ida ida_eisa.c Message-ID: <20000417195700.A2358@frizzantino.TechFak.Uni-Bielefeld.DE> References: <14583.37834.772687.845973@jabberwock.rstcorp.com> <14584.36192.55759.997336@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14584.36192.55759.997336@jabberwock.rstcorp.com>; from viren@rstcorp.com on Sat, Apr 15, 2000 at 11:40:16AM -0400 X-Zen: Oooommmmmmmmmmmmmmmmmmmmmmm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello! all right ... things take longer then we expect them to take. the kernel (everything cvsup'd on saturday) boot fine and the array controller is detected just perfect. also fdisk'ing, disklabel'ing and newfs'ing the drive was no problem. i copied almost the whole current source tree on the drive ... no problem. even a simulated diskfail was no problem. but it looks like the driver is taking much system time. while coping the files a hat a system load of almost 40%, irq and user was much less. i then i ran into bog trouble. it seems that the something the the network drivers is broken ... but that has propably not much to do with the ida driver ... Eines schoenen Tages schrieb Viren R.Shah: > >> mainboard0: > >> eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 > >> ida0: at 0x6000-0x60ff, 0x6c88-0x6c9e > >> ida0: irq 15 (level) on eisa0 slot 6 > >> ida0: drives=1 firm_rev=1.66 ^^^^ i am running 2.26 on that board. maybe you should upgrade regards, oliver -- -------------------------------------------------------- And remember: "To Infinity And Far Beyond ... Somehow?!" 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 Mon Apr 17 11: 6:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from jsn.kmost.express.ru (jsn.kmost.express.ru [212.24.37.101]) by hub.freebsd.org (Postfix) with ESMTP id F2F6237B703 for ; Mon, 17 Apr 2000 11:05:43 -0700 (PDT) (envelope-from jason@jsn.kmost.express.ru) Received: (from jason@localhost) by jsn.kmost.express.ru (8.9.3/8.9.3) id WAA20589 for freebsd-current@freebsd.org; Mon, 17 Apr 2000 22:07:52 +0400 (MSD) (envelope-from jason) From: Dmitry Kim Message-Id: <200004171807.WAA20589@jsn.kmost.express.ru> Subject: setrlimit(), break() and mmap() To: freebsd-current@freebsd.org Date: Mon, 17 Apr 2000 22:07:51 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL68 (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 hello, people, i was playing with setrlimit(), break() and mmap() in freebsd 4.0 and in CURRENT, and i have a couple of questions: 1. kernel code for break() syscall checks if the requested value for the data segment size is more than RLIMIT_DATA, and, if yes, it just returns ENOMEM. thus, the calling process receives ENOMEM even in case it is trying to return some memory to the system; for example, if user process does something like "alloc(100Mb); setrlimit(RLIMIT_DATA,&{1Mb,0}); free(50Mb)", break() system call in the free() will fail, and no memory will be returned to the system. imho, the user process should always be allowed to return memory to the system, no matter what. thus, in [o]break() we should 1) check if we the process is trying to return some memory, and, if yes, let him in, and then 2) check RLIMIT_DATA, VM_MAX_USER_ADDRESS and what ever else. or am i missing anything? 2. break() is not the only way for the process to ask the system for some more memory. the user process can use mmap(NULL,..., MAP_ANON,...). for this case, RLIMIT_DATA is never checked, and i did not find any way to limit the amount of memory which is available to a specific process/user via mmap( ...,MAP_ANON...,...). seems like just any user can eat up all the memory in the system using mmap() instead of break() for his malloc/free library. which would be definitely a Bad Thing :) or am i missing something? would anyone please explain to me what is the purpose of having RLIMIT_DATA if this limitation can be so easily worked around? have a nice time of day, jsn. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 11:15:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5F14C37BC02; Mon, 17 Apr 2000 11:15:10 -0700 (PDT) (envelope-from green@FreeBSD.org) Date: Mon, 17 Apr 2000 14:14:52 -0400 (EDT) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Shin-ichi YOSHIMOTO Cc: freebsd-current@freebsd.org Subject: Re: Anyone have OpenSSH + X11-fwd working? 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, 17 Apr 2000, Shin-ichi YOSHIMOTO wrote: > At 10:01 -0400 04/17/2000, Brian Fundakowski Feldman wrote: > > Has anyone tried it recently and gotten it to work? > > Yes, sure. Check your config file. That doesn't explain the failures here. Look. The initial SSH_CHANNEL_X11_OPEN is totally fucked up.... basically nothing at all like it should be, and there's nothing to explain it. SSH Version OpenSSH-1.2.2, protocol version 1.5. Compiled with SSL. debug: Reading configuration data /home/green/.ssh/config debug: Applying options for * debug: Reading configuration data /etc/ssh/ssh_config debug: Applying options for * debug: ssh_connect: getuid 0 geteuid 0 anon 0 debug: Connecting to green.dyndns.org [10.0.0.1] port 22. debug: Allocated local port 926. debug: Connection established. debug: Remote protocol version 1.5, remote software version OpenSSH-1.2.2 debug: Waiting for server public key. debug: Received server public key (768 bits) and host key (1024 bits). debug: Host 'green.dyndns.org' is known and matches the host key. debug: Encryption type: blowfish debug: Sent encrypted session key. debug: Installing crc compensation attack detector. debug: Received encrypted confirmation. debug: Doing password authentication. debug: Requesting pty. debug: Requesting X11 forwarding with authentication spoofing. debug: Requesting shell. debug: Entering interactive session. Last login: Mon Apr 17 14:06:18 2000 from littlehost Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT (GREEN) #15: Sun Apr 9 23:06:23 EDT 2000 Welcome to FreeBSD! Before seeking technical support, please use the following resources: o Security advisories and updated errata information for all releases are at http://www.FreeBSD.org/releases/ - always consult the ERRATA section for your release first as it's updated frequently. o The Handbook and FAQ documents are at http://www.freebsd.org/ and, along with the mailing lists, can be searched by going to http://www.FreeBSD.org/search.html. If the doc distribution has been installed, they're also available formatted in /usr/share/doc. If you still have a question or problem, please take the output of `uname -a', along with any relevant error messages, and email it as a question to the questions@FreeBSD.org mailing list. If you are unfamiliar with FreeBSD's directory layout, please refer to the hier(7) man page. If you are not familiar with man pages, type "man man". You may also use `/stand/sysinstall' to re-enter the installation and configuration utility. Edit /etc/motd to change this login announcement. /usr/X11R6/bin/xauth: creating new authority file /tmp/ssh-JfGYR325/cookies {"/home/green"}$ xterm debug: Received X11 open request. debug: channel 0: new [X11 connection from localhost port 1743] debug: X11 connection uses different authentication protocol. X11 connection rejected because of wrong authentication. debug: X11 rejected 0 i1/o16 debug: channel 0: INPUT_OPEN -> INPUT_WAIT_DRAIN [read failed] debug: channel 0: shutdown_read debug: channel 0: OUTPUT_OPEN -> OUTPUT_WAIT_IEOF [write failed] debug: channel 0: shutdown_write debug: X11 rejected 0 i2/o64 debug: channel 0: INPUT_WAIT_DRAIN -> INPUT_WAIT_OCLOSE [inbuf empty, send IEOF] debug: channel 0: OUTPUT_WAIT_IEOF -> OUTPUT_CLOSED [rvcd IEOF] debug: channel 0: INPUT_WAIT_OCLOSE -> INPUT_CLOSED [rcvd OCLOSE] debug: channel 0: full closed X connection to green.dyndns.org:12.0 broken (explicit kill or server shutdown). {"/home/green"}$ ^D Connection to green.dyndns.org closed. debug: Transferred: stdin 7, stdout 1533, stderr 40 bytes in 6.8 seconds debug: Bytes per second: stdin 1.0, stdout 225.7, stderr 5.9 debug: Exit status 1 -- 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 Mon Apr 17 14:18:11 2000 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 D64E537B6C3 for ; Mon, 17 Apr 2000 14:17:20 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA12413 for ; Mon, 17 Apr 2000 23:17:15 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: FreeBSD Build status Date: Mon, 17 Apr 2000 23:17:15 +0200 Message-ID: <12411.956006235@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a machine which isn't doing much right now, so I have decided to set it up as an automatic "FreeBSD Build checker". Once per day the machine cvsups, checks out a virgin source tree, tries to build GENERIC, GENERIC98, LINT and world. If any of these builds fail it will send a report like this. On Sundays the report will always be sent. Once I have this tested a bit more, I will start mailing the the reports directly to current@freebsd.org It is not shown here, but a delta listing whining about new warnings in any of the builds is also featured. Poul-Henning ------- Forwarded Message Date: Mon, 17 Apr 2000 23:09:06 +0200 (CEST) Message-Id: <200004172109.XAA89608@otte.freebsd.dk> Subject: FreeBSD build status From: Build-o-matic To: undisclosed-recipients:; ----------------------------------- SUMMARY ----------------------------------- World compiled 637 Warnings 45 Errors Kernel LINT ***didn't compile*** 150 Warnings 0 Errors Kernel GENERIC compiled 59 Warnings 0 Errors Kernel GENERIC98 compiled 54 Warnings 0 Errors ----------------------------------- Compile errors for kernel LINT ----------------------------------- linking kernel awi.o: In function `awi_ioctl': awi.o(.text+0x3b4): undefined reference to `memcmp' awi.o(.text+0x3cf): undefined reference to `memset' awi.o: In function `awi_drvset': awi.o(.text+0x74f): undefined reference to `memcmp' awi.o(.text+0x76a): undefined reference to `memset' awi.o: In function `awi_input': awi.o(.text+0x1499): undefined reference to `memcmp' awi.o: In function `awi_init_hw': awi.o(.text+0x1c8a): undefined reference to `memcmp' awi.o: In function `awi_init_mibs': awi.o(.text+0x1e96): undefined reference to `memset' awi.o: In function `awi_start_scan': awi.o(.text+0x22f5): undefined reference to `memset' awi.o: In function `awi_stop_scan': awi.o(.text+0x24e3): undefined reference to `memcmp' awi.o: In function `awi_recv_beacon': awi.o(.text+0x266b): undefined reference to `memcmp' awi.o(.text+0x2681): undefined reference to `memcmp' awi.o(.text+0x26f8): undefined reference to `memset' awi.o: In function `awi_recv_auth': awi.o(.text+0x2e68): undefined reference to `memcmp' awi.o: In function `awi_recv_asresp': awi.o(.text+0x31d8): undefined reference to `memcmp' if_awi_pccard.o: In function `awi_pccard_probe': if_awi_pccard.o(.text+0xac): undefined reference to `memcmp' isa_compat.o(.data+0x14): undefined reference to `vtdriver' *** Error code 1 (continuing) `all' not remade because of errors. ----------------------------------- All warnings from kernel LINT ----------------------------------- ../../dev/amr/amr.c:1015: warning: `amr_wait_command' defined but not used ../../dev/amr/amr.c:1218: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:1518: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:1549: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:171: warning: cast discards qualifiers from pointer target type ../../dev/awi/awi.c:505: warning: implicit declaration of function `memcmp' ../../dev/awi/awi.c:508: warning: implicit declaration of function `memset' ../../dev/awi/if_awi_pccard.c:115: warning: assignment discards qualifiers from pointer target type ../../dev/awi/if_awi_pccard.c:90: warning: implicit declaration of function `memcmp' ../../dev/dpt/dpt_scsi.c:1296: warning: cast discards qualifiers from pointer target type ../../dev/dpt/dpt_scsi.c:501: warning: cast discards qualifiers from pointer target type ../../dev/dpt/dpt_scsi.c:612: warning: cast discards qualifiers from pointer target type ../../dev/ex/if_ex.c:1151: warning: unused variable `sc' ../../dev/fb/vga.c:1321: warning: `fill' defined but not used ../../dev/fb/vga.c:1331: warning: `filll_io' defined but not used ../../dev/hea/eni_buffer.c:115: warning: cast discards qualifiers from pointer target type ../../dev/hea/eni_vcm.c:279: warning: cast discards qualifiers from pointer target type ../../dev/hfa/fore_buffer.c:751: warning: passing arg 1 of `atm_dev_free' discards qualifiers from pointer target type ../../dev/hfa/fore_command.c:440: warning: passing arg 1 of `atm_dev_free' discards qualifiers from pointer target type ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_ENI_155P' not handled in switch ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_FORE_SBA200' not handled in switch ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_FORE_SBA200E' not handled in switch ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_UNKNOWN' not handled in switch ../../dev/hfa/fore_load.c:1361: warning: enumeration value `DEV_ENI_155P' not handled in switch ../../dev/hfa/fore_load.c:1361: warning: enumeration value `DEV_FORE_SBA200' not handled in switch ../../dev/hfa/fore_load.c:1361: warning: enumeration value `DEV_FORE_SBA200E' not handled in switch ../../dev/hfa/fore_load.c:1361: warning: enumeration value `DEV_UNKNOWN' not handled in switch ../../dev/hfa/fore_receive.c:562: warning: passing arg 1 of `atm_dev_free' discards qualifiers from pointer target type ../../dev/hfa/fore_transmit.c:343: warning: passing arg 1 of `atm_dev_free' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1237: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1326: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1326: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1343: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1355: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1400: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1538: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1552: warning: cast discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1606: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1615: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1618: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1643: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1900: warning: cast discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1916: warning: cast discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2001: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2025: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2076: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2076: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2140: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2140: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2189: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2190: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/pdq/pdq_ifsubr.c:376: warning: #warning "Implement fddi_resolvemulti!" ../../dev/sound/pcm/channel.c:339: warning: unused variable `dl' ../../dev/vn/vn.c:415: warning: passing arg 2 of `vm_pager_strategy' from incompatible pointer type ../../dev/xe/if_xe.c:1829: warning: `xe_compute_crc' defined but not used ../../dev/xe/if_xe.c:1864: warning: `xe_compute_hashbit' defined but not used ../../dev/xe/if_xe.c:2168: warning: `xe_reg_dump' defined but not used ../../dev/xe/if_xe.c:234: warning: `xe_memwrite' defined but not used ../../gnu/i386/isa/dgb.c:228: warning: (near initialization for `dgbspeedtab[0]') ../../gnu/i386/isa/dgb.c:228: warning: missing braces around initializer ../../gnu/i386/isa/dgb.c:803: warning: assignment discards qualifiers from pointer target type ../../gnu/i386/isa/dgb.c:847: warning: assignment discards qualifiers from pointer target type ../../gnu/i386/isa/dgb.c:848: warning: assignment discards qualifiers from pointer target type ../../gnu/i386/isa/dgb.c:851: warning: assignment discards qualifiers from pointer target type ../../gnu/i386/isa/dgb.c:852: warning: assignment discards qualifiers from pointer target type ../../gnu/i386/isa/dgm.c:231: warning: (near initialization for `dgmspeedtab[0]') ../../gnu/i386/isa/dgm.c:231: warning: missing braces around initializer ../../i386/ibcs2/ibcs2_sysent.c:18: warning: cast discards qualifiers from pointer target type ../../i386/isa/cy.c:447: warning: `firmware_version' might be used uninitialized in this function ../../i386/isa/if_rdp.c:511: warning: implicit declaration of function `isa_irq_pending' ../../i386/isa/istallion.c:1888: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:1967: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:1972: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:1994: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:1997: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:2047: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:2057: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:2134: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:2244: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:2274: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:3372: warning: cast discards qualifiers from pointer target type ../../i386/isa/istallion.c:3378: warning: cast discards qualifiers from pointer target type ../../i386/isa/matcd/matcd.c:2057: warning: `i' might be used uninitialized in this function ../../i386/isa/rp.c:1745: warning: (near initialization for `baud_table[0]') ../../i386/isa/rp.c:1745: warning: missing braces around initializer ../../i386/isa/tw.c:577: warning: (near initialization for `X10_HOUSE[0]') ../../i386/isa/tw.c:577: warning: missing braces around initializer ../../i386/isa/tw.c:597: warning: (near initialization for `X10_KEY[0]') ../../i386/isa/tw.c:597: warning: missing braces around initializer ../../i386/linux/linux_sysent.c:19: warning: cast discards qualifiers from pointer target type ../../kern/init_sysent.c:24: warning: cast discards qualifiers from pointer target type ../../kern/subr_diskslice.c:162: warning: unused variable `s' ../../kern/sys_generic.c:344: warning: cast discards qualifiers from pointer target type ../../kern/vfs_aio.c:1014: warning: cast discards qualifiers from pointer target type ../../kern/vfs_aio.c:1895: warning: cast discards qualifiers from pointer target type ../../kern/vfs_aio.c:1958: warning: cast discards qualifiers from pointer target type ../../kern/vfs_aio.c:575: warning: cast discards qualifiers from pointer target type ../../miscfs/nullfs/null_vfsops.c:422: warning: function declaration isn't a prototype ../../net/if_atmsubr.c:185: warning: address of register variable `m' requested ../../netatm/atm_if.c:524: warning: enumeration value `MEDIA_UNKNOWN' not handled in switch ../../netinet/in_proto.c:189: warning: initialization from incompatible pointer type ../../netinet/ip_input.c:665: warning: assignment from incompatible pointer type ../../netinet/tcp_subr.c:1244: warning: implicit declaration of function `ipsec6_hdrsiz' ../../netinet/tcp_subr.c:983: warning: `off' might be used uninitialized in this function ../../nfs/nfs_vfsops.c:406: warning: implicit declaration of function `bootpc_init' ../../pci/alpm.c:378: warning: `sts' might be used uninitialized in this function ../../pci/amd.c:838: warning: `amd_reset' defined but not used ../../pci/amd.c:880: warning: `amd_timeout' defined but not used ../../pci/if_fxp.c:1475: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../pci/if_fxp.c:1532: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../pci/if_fxp.c:2049: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../pci/intpm.c:299: warning: assignment makes pointer from integer without a cast ../../pci/isp_pci.c:367: warning: initialization makes pointer from integer without a cast ../../pci/ncr.c:5335: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5472: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5775: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5779: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5803: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5810: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5818: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5823: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5833: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5837: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:6805: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:6806: warning: cast discards qualifiers from pointer target type ../../svr4/imgact_svr4.c:129: warning: int format, long int arg (arg 2) ../../svr4/imgact_svr4.c:170: warning: int format, long int arg (arg 2) ../../svr4/imgact_svr4.c:186: warning: unsigned int format, long unsigned int arg (arg 3) ../../svr4/imgact_svr4.c:209: warning: unsigned int format, long unsigned int arg (arg 3) ../../svr4/imgact_svr4.c:90: warning: unsigned int format, long unsigned int arg (arg 2) ../../svr4/imgact_svr4.c:90: warning: unsigned int format, long unsigned int arg (arg 3) ../../svr4/imgact_svr4.c:90: warning: unsigned int format, long unsigned int arg (arg 4) ../../svr4/svr4_fcntl.c:582: warning: unsigned int format, pointer arg (arg 2) ../../svr4/svr4_ioctl.c:100: warning: unsigned int format, u_long arg (arg 2) ../../svr4/svr4_ioctl.c:115: warning: initialization from incompatible pointer type ../../svr4/svr4_ioctl.c:156: warning: initialization from incompatible pointer type ../../svr4/svr4_misc.c:256: warning: too many arguments for format ../../svr4/svr4_resource.c:219: warning: implicit declaration of function `dosetrlimit' ../../svr4/svr4_signal.c:298: warning: long unsigned int format, svr4_sig_t arg (arg 2) ../../svr4/svr4_stream.c:1531: warning: unsigned int format, pointer arg (arg 2) ../../svr4/svr4_stream.c:1533: warning: passing arg 1 of `show_strbuf' from incompatible pointer type ../../svr4/svr4_stream.c:2252: warning: assignment from incompatible pointer type ../../svr4/svr4_sysent.c:21: warning: cast discards qualifiers from pointer target type ../../svr4/svr4_sysvec.c:176: warning: initialization from incompatible pointer type ../../svr4/svr4_termios.c:496: warning: unsigned int format, u_long arg (arg 2) ../../sys/aio.h:175: warning: `struct sockbuf' declared inside parameter list ../../sys/aio.h:175: warning: its scope is only this definition or declaration, which is probably not what you want. ../../sys/devfsext.h:32: warning: #warning "Using obsolete " ../../sys/devfsext.h:32: warning: #warning "Using obsolete " ../../ufs/ffs/ffs_vfsops.c:90: warning: initialization from incompatible pointer type ----------------------------------- All warnings from kernel GENERIC ----------------------------------- ../../dev/amr/amr.c:1015: warning: `amr_wait_command' defined but not used ../../dev/amr/amr.c:1218: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:1518: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:1549: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:171: warning: cast discards qualifiers from pointer target type ../../dev/awi/if_awi_pccard.c:115: warning: assignment discards qualifiers from pointer target type ../../dev/dpt/dpt_scsi.c:1296: warning: cast discards qualifiers from pointer target type ../../dev/dpt/dpt_scsi.c:501: warning: cast discards qualifiers from pointer target type ../../dev/dpt/dpt_scsi.c:612: warning: cast discards qualifiers from pointer target type ../../dev/ex/if_ex.c:1151: warning: unused variable `sc' ../../dev/ie/if_ie.c:1237: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1326: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1326: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1343: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1355: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1400: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1538: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1552: warning: cast discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1606: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1615: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1618: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1643: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1900: warning: cast discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1916: warning: cast discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2001: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2025: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2076: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2076: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2140: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2140: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2189: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:2190: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../kern/init_sysent.c:24: warning: cast discards qualifiers from pointer target type ../../kern/subr_diskslice.c:162: warning: unused variable `s' ../../kern/sys_generic.c:344: warning: cast discards qualifiers from pointer target type ../../kern/vfs_aio.c:1014: warning: cast discards qualifiers from pointer target type ../../kern/vfs_aio.c:1426: warning: `aio_aqueue' defined but not used ../../kern/vfs_aio.c:575: warning: cast discards qualifiers from pointer target type ../../netinet/ip_input.c:665: warning: assignment from incompatible pointer type ../../netinet/tcp_subr.c:983: warning: `off' might be used uninitialized in this function ../../pci/amd.c:838: warning: `amd_reset' defined but not used ../../pci/amd.c:880: warning: `amd_timeout' defined but not used ../../pci/if_fxp.c:1475: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../pci/if_fxp.c:1532: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../pci/if_fxp.c:2049: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../pci/ncr.c:5335: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5472: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5775: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5779: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5803: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5810: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5818: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5823: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5833: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5837: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:6805: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:6806: warning: cast discards qualifiers from pointer target type ../../sys/aio.h:175: warning: `struct sockbuf' declared inside parameter list ../../sys/aio.h:175: warning: its scope is only this definition or declaration, which is probably not what you want. ----------------------------------- All warnings from kernel GENERIC98 ----------------------------------- ../../dev/amr/amr.c:1015: warning: `amr_wait_command' defined but not used ../../dev/amr/amr.c:1218: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:1518: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:1549: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:171: warning: cast discards qualifiers from pointer target type ../../i386/isa/bs/bsfunc.c:634: warning: large integer implicitly truncated to unsigned type ../../i386/isa/bs/bsfunc.c:64: warning: label `again' defined but not used ../../i386/isa/bs/bshw_dma.c:126: warning: called from here ../../i386/isa/bs/bshw_dma.c:223: warning: comparison is always true due to limited range of data type ../../i386/isa/bs/bshw_dma.c:38: warning: can't inline call to `bshw_dmastart' ../../i386/isa/bs/bshw_pdma.c:39: warning: can't inline call to `bshw_lc_smit_stop' ../../i386/isa/bs/bshw_pdma.c:49: warning: called from here ../../i386/isa/if_fe.c:1157: warning: suggest parentheses around arithmetic in operand of | ../../kern/init_sysent.c:24: warning: cast discards qualifiers from pointer target type ../../kern/subr_diskslice.c:162: warning: unused variable `s' ../../kern/sys_generic.c:344: warning: cast discards qualifiers from pointer target type ../../kern/vfs_aio.c:1014: warning: cast discards qualifiers from pointer target type ../../kern/vfs_aio.c:1426: warning: `aio_aqueue' defined but not used ../../kern/vfs_aio.c:575: warning: cast discards qualifiers from pointer target type ../../netinet/ip_input.c:665: warning: assignment from incompatible pointer type ../../netinet/tcp_subr.c:983: warning: `off' might be used uninitialized in this function ../../pc98/pc98/clock.c:1095: warning: `s' might be used uninitialized in this function ../../pc98/pc98/fd.c:1160: warning: unused variable `i' ../../pc98/pc98/fd.c:1161: warning: unused variable `st0' ../../pc98/pc98/fd.c:1161: warning: unused variable `st3' ../../pc98/pc98/fd.c:1165: warning: unused variable `fd_fifo' ../../pc98/pc98/fd.c:868: warning: unused variable `ic_type' ../../pc98/pc98/npx.c:273: warning: large integer implicitly truncated to unsigned type ../../pc98/pc98/npx.c:273: warning: large integer implicitly truncated to unsigned type ../../pc98/pc98/pc98gdc.c:1042: warning: `dump_buffer' defined but not used ../../pc98/pc98/pc98gdc.c:518: warning: `initialize_gdc' defined but not used ../../pc98/pc98/pc98gdc.c:612: warning: `gdc_nop' defined but not used ../../pc98/pc98/sio.c:1169: warning: `rsabase' might be used uninitialized in this function ../../pc98/pc98/sio.c:1301: warning: unused variable `xiobase' ../../pc98/pc98/sio.c:1302: warning: unused variable `io' ../../pci/amd.c:838: warning: `amd_reset' defined but not used ../../pci/amd.c:880: warning: `amd_timeout' defined but not used ../../pci/if_fxp.c:1475: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../pci/if_fxp.c:1532: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../pci/if_fxp.c:2049: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../pci/ncr.c:5335: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5472: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5775: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5779: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5803: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5810: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5818: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5823: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5833: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:5837: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:6805: warning: cast discards qualifiers from pointer target type ../../pci/ncr.c:6806: warning: cast discards qualifiers from pointer target type ../../sys/aio.h:175: warning: `struct sockbuf' declared inside parameter list ../../sys/aio.h:175: warning: its scope is only this definition or declaration, which is probably not what you want. ----------------------------------- All warnings from make world ----------------------------------- /otte/src/bin/ls/print.c:250: warning: `%c' yields only last 2 digits of year in some locales /otte/src/bin/ps/print.c:369: warning: `%y' yields only last 2 digits of year /otte/src/bin/ps/print.c:388: warning: `%c' yields only last 2 digits of year in some locales /otte/src/bin/rmail/../../contrib/sendmail/rmail/rmail.c:13: warning: `copyright' defined but not used /otte/src/bin/rmail/../../contrib/sendmail/rmail/rmail.c:19: warning: `sccsid' defined but not used /otte/src/games/battlestar/fly.c:76: warning: comparison between pointer and integer /otte/src/games/phantasia/misc.c:1451: warning: assignment from incompatible pointer type /otte/src/games/sail/pl_main.c:52: warning: comparison between pointer and integer /otte/src/gnu/lib/libreadline/history/doc/../../../../../contrib/libreadline/doc/hstech.texinfo:429: warning: unlikely character [ in @var. /otte/src/gnu/lib/libreadline/history/doc/../../../../../contrib/libreadline/doc/hstech.texinfo:429: warning: unlikely character ] in @var. /otte/src/gnu/lib/libreadline/readline/doc/../../../../../contrib/libreadline/doc/rluser.texinfo:1331: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/lib/libreadline/readline/doc/../../../../../contrib/libreadline/doc/rluser.texinfo:1331: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/usr.bin/awk/doc/../../../../contrib/awk/doc/gawk.texi:18072: warning: unlikely character , in @var. /otte/src/gnu/usr.bin/awk/doc/../../../../contrib/awk/doc/gawk.texi:18075: warning: unlikely character , in @var. /otte/src/gnu/usr.bin/awk/doc/../../../../contrib/awk/doc/gawk.texi:18080: warning: unlikely character , in @var. /otte/src/gnu/usr.bin/awk/doc/../../../../contrib/awk/doc/gawk.texi:18084: warning: unlikely character , in @var. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld/ld.texinfo:1837: warning: `.' or `,' must follow cross reference, not @. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld/ld.texinfo:1841: warning: `.' or `,' must follow cross reference, not @. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/ld/ld.texinfo:2396: warning: unlikely character ) in @var. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo:4647: warning: unlikely character , in @var. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo:5284: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/gdb.texinfo:6531: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/gdbint.texinfo:1026: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/stabs.texinfo:2040: warning: unlikely character , in @var. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/stabs.texinfo:2040: warning: unlikely character , in @var. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/stabs.texinfo:2139: warning: unlikely character , in @var. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/stabs.texinfo:2139: warning: unlikely character , in @var. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/stabs.texinfo:3373: warning: `.' or `,' must follow cross reference, not @. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/stabs.texinfo:875: warning: `.' or `,' must follow cross reference, not f. /otte/src/gnu/usr.bin/binutils/doc/../../../../contrib/libreadline/doc/rluser.texinfo:1331: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/callback.c:326: warning: passing arg 1 of `vfprintf_filtered' from incompatible pointer type /otte/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/callback.c:348: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/callback.c:351: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/corefile.c:312: warning: passing arg 2 of `print_address' from incompatible pointer type /otte/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/gdbarch.c:345: warning: assignment from incompatible pointer type /otte/src/gnu/usr.bin/cc/c++filt/../../../../contrib/gcc/cplus-dem.c:4527: warning: assignment discards qualifiers from pointer target type /otte/src/gnu/usr.bin/cc/c++filt/../../../../contrib/gcc/cplus-dem.c:4527: warning: assignment discards qualifiers from pointer target type /otte/src/gnu/usr.bin/cc/c++filt/../../../../contrib/gcc/cplus-dem.c:4530: warning: assignment discards qualifiers from pointer target type /otte/src/gnu/usr.bin/cc/c++filt/../../../../contrib/gcc/cplus-dem.c:4530: warning: assignment discards qualifiers from pointer target type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1655: warning: passing arg 1 of `warning' from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1655: warning: passing arg 1 of `warning' from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1678: warning: passing arg 1 of `warning' from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1678: warning: passing arg 1 of `warning' from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/reload1.c:1275: warning: passing arg 4 of `decode_asm_operands' from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/reload1.c:1275: warning: passing arg 4 of `decode_asm_operands' from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/toplev.c:1185: warning: initialization from incompatible pointer type /otte/src/gnu/usr.bin/cc/doc/../../../../contrib/gcc/rtl.texi:870: warning: unlikely character ) in @var. /otte/src/gnu/usr.bin/cc/f77doc/../../../../contrib/gcc/f/intdoc.texi:9502: warning: unlikely character ( in @var. /otte/src/gnu/usr.bin/cc/f77doc/../../../../contrib/gcc/f/intdoc.texi:9502: warning: unlikely character ) in @var. /otte/src/gnu/usr.bin/cc/f77doc/../../../../contrib/gcc/f/intdoc.texi:9581: warning: unlikely character ( in @var. /otte/src/gnu/usr.bin/cc/f77doc/../../../../contrib/gcc/f/intdoc.texi:9581: warning: unlikely character ) in @var. /otte/src/gnu/usr.bin/cvs/doc/../../../../contrib/cvs/doc/cvs.texinfo:11664: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/usr.bin/cvs/doc/../../../../contrib/cvs/doc/cvs.texinfo:11832: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/usr.bin/cvs/doc/../../../../contrib/cvs/doc/cvs.texinfo:11968: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/usr.bin/cvs/doc/../../../../contrib/cvs/doc/cvs.texinfo:12110: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/usr.bin/cvs/doc/../../../../contrib/cvs/doc/cvs.texinfo:13112: warning: @sc argument all uppercase, thus no effect. /otte/src/gnu/usr.bin/dialog/dialog.c:93: warning: second argument of `main' should be `char **' /otte/src/gnu/usr.bin/diff/../../../contrib/diff/prepend_args.c:74: warning: initialization makes pointer from integer without a cast /otte/src/gnu/usr.bin/diff/doc/../../../../contrib/diff/diff.texi:2678: warning: unlikely character ] in @var. /otte/src/gnu/usr.bin/groff/troff/../../../../contrib/groff/troff/node.cc:1494: warning: `void *' is not a pointer-to-object type /otte/src/gnu/usr.bin/ptx/doc/ptx.texinfo:116: warning: `.' or `,' must follow cross reference, not f. /otte/src/gnu/usr.bin/ptx/doc/ptx.texinfo:256: warning: `.' or `,' must follow cross reference, not f. /otte/src/gnu/usr.bin/rcs/lib/rcsutil.c:634: warning: assignment from incompatible pointer type /otte/src/lib/libcom_err/doc/com_err.texinfo:377: warning: unlikely character ( in @var. /otte/src/lib/libcom_err/doc/com_err.texinfo:377: warning: unlikely character ) in @var. /otte/src/lib/libcom_err/doc/com_err.texinfo:384: warning: unlikely character ( in @var. /otte/src/lib/libcom_err/doc/com_err.texinfo:384: warning: unlikely character ) in @var. /otte/src/lib/libcom_err/doc/com_err.texinfo:577: warning: unlikely character ( in @var. /otte/src/lib/libcom_err/doc/com_err.texinfo:577: warning: unlikely character ) in @var. /otte/src/lib/libcrypt/crypt.c:31: warning: `rcsid' defined but not used /otte/src/lib/libcrypt/crypt.c:31: warning: `rcsid' defined but not used /otte/src/lib/libcrypt/crypt.c:31: warning: `rcsid' defined but not used /otte/src/lib/libpam/libpam/../../../contrib/libpam/libpam/pam_handlers.c:578: warning: passing arg 1 of `_pam_open_static_handler' discards qualifiers from pointer target type /otte/src/libexec/ftpd/../../bin/ls/print.c:250: warning: `%c' yields only last 2 digits of year in some locales /otte/src/libexec/ftpd/ftpd.c:2560: warning: variable `dout' might be clobbered by `longjmp' or `vfork' /otte/src/libexec/ftpd/ftpd.c:2561: warning: variable `dirlist' might be clobbered by `longjmp' or `vfork' /otte/src/libexec/ftpd/ftpd.c:2562: warning: variable `simple' might be clobbered by `longjmp' or `vfork' /otte/src/libexec/ftpd/ftpd.c:2563: warning: variable `freeglob' might be clobbered by `longjmp' or `vfork' /otte/src/libexec/ftpd/popen.c:79: warning: variable `iop' might be clobbered by `longjmp' or `vfork' /otte/src/libexec/ftpd/popen.c:80: warning: variable `gargc' might be clobbered by `longjmp' or `vfork' /otte/src/libexec/rexecd/rexecd.c:182: warning: assignment discards qualifiers from pointer target type /otte/src/libexec/rlogind/rlogind.c:372: warning: `fbp' might be used uninitialized in this function /otte/src/libexec/rlogind/rlogind.c:372: warning: `pbp' might be used uninitialized in this function /otte/src/libexec/rlogind/rlogind.c:573: warning: unused variable `retval' /otte/src/libexec/rlogind/rlogind.c:574: warning: unused variable `af' /otte/src/libexec/rlogind/rlogind.c:575: warning: unused variable `addr' /otte/src/sbin/fsck/../../sys/ufs/ffs/ffs_subr.c:193: warning: this function may return with or without a value /otte/src/sbin/fsck/../../sys/ufs/ffs/ffs_subr.c:217: warning: this function may return with or without a value /otte/src/sbin/fsck/dir.c:127: warning: comparison between signed and unsigned /otte/src/sbin/fsck/dir.c:56: warning: (near initialization for `emptydir.dot_type') /otte/src/sbin/fsck/dir.c:56: warning: missing initializer /otte/src/sbin/fsck/dir.c:620: warning: comparison between signed and unsigned /otte/src/sbin/fsck/dir.c:634: warning: comparison between signed and unsigned /otte/src/sbin/fsck/pass1.c:244: warning: comparison between signed and unsigned /otte/src/sbin/fsck/pass5.c:229: warning: comparison between signed and unsigned /otte/src/sbin/fsck/pass5.c:236: warning: comparison between signed and unsigned /otte/src/sbin/fsck/pass5.c:95: warning: comparison between signed and unsigned /otte/src/sbin/quotacheck/quotacheck.c:186: warning: passing arg 3 of `checkfstab' from incompatible pointer type /otte/src/sbin/quotacheck/quotacheck.c:186: warning: passing arg 4 of `checkfstab' from incompatible pointer type /otte/src/secure/lib/libcrypt/../../../lib/libcrypt/crypt.c:31: warning: `rcsid' defined but not used /otte/src/secure/lib/libcrypt/../../../lib/libcrypt/crypt.c:31: warning: `rcsid' defined but not used /otte/src/secure/lib/libcrypt/../../../lib/libcrypt/crypt.c:31: warning: `rcsid' defined but not used /otte/src/secure/lib/libtelnet/../../../crypto/telnet/libtelnet/pk.c:228: warning: passing arg 1 of `des_cbc_encrypt' from incompatible pointer type /otte/src/secure/lib/libtelnet/../../../crypto/telnet/libtelnet/pk.c:228: warning: passing arg 1 of `des_cbc_encrypt' from incompatible pointer type /otte/src/secure/lib/libtelnet/../../../crypto/telnet/libtelnet/pk.c:228: warning: passing arg 2 of `des_cbc_encrypt' from incompatible pointer type /otte/src/secure/lib/libtelnet/../../../crypto/telnet/libtelnet/pk.c:228: warning: passing arg 2 of `des_cbc_encrypt' from incompatible pointer type /otte/src/secure/lib/libtelnet/../../../crypto/telnet/libtelnet/pk.c:265: warning: passing arg 1 of `des_cbc_encrypt' from incompatible pointer type /otte/src/secure/lib/libtelnet/../../../crypto/telnet/libtelnet/pk.c:265: warning: passing arg 1 of `des_cbc_encrypt' from incompatible pointer type /otte/src/secure/lib/libtelnet/../../../crypto/telnet/libtelnet/pk.c:265: warning: passing arg 2 of `des_cbc_encrypt' from incompatible pointer type /otte/src/secure/lib/libtelnet/../../../crypto/telnet/libtelnet/pk.c:265: warning: passing arg 2 of `des_cbc_encrypt' from incompatible pointer type /otte/src/secure/usr.bin/telnet/../../../crypto/telnet/telnet/commands.c:3085: warning: assignment makes pointer from integer without a cast /otte/src/secure/usr.sbin/sshd/../../../crypto/openssh/login.c:127: warning: passing arg 1 of `logout' discards qualifiers from pointer target type /otte/src/share/doc/papers/beyond4.3/beyond43.ms:156: warning: can't find font `C' /otte/src/share/doc/papers/diskperf/results.ms:231: warning: indent cannot be negative /otte/src/share/doc/papers/diskperf/results.ms:413: warning: indent cannot be negative /otte/src/share/doc/papers/fsinterface/fsinterface.ms:35: warning: number register `v' not defined /otte/src/share/doc/papers/fsinterface/fsinterface.ms:60: warning: number register `UX' not defined /otte/src/share/doc/papers/memfs/1.t:390: warning: `Li' not defined /otte/src/share/doc/papers/memfs/1.t:390: warning: number register `Ns' not defined /otte/src/share/doc/papers/memfs/1.t:390: warning: number register `rS' not defined /otte/src/share/doc/papers/memfs/1.t:401: warning: `FE' not defined /otte/src/share/doc/papers/memfs/1.t:401: warning: `FS' not defined /otte/src/share/doc/papers/memfs/1.t:401: warning: `[G' not defined /otte/src/share/doc/papers/memfs/1.t:401: warning: `[O' not defined /otte/src/share/doc/papers/memfs/1.t:413: warning: `[I' not defined /otte/src/share/doc/papers/memfs/1.t:413: warning: `[N' not defined /otte/src/share/doc/papers/memfs/1.t:413: warning: `[O' not defined /otte/src/share/doc/papers/memfs/1.t:413: warning: `[V' not defined /otte/src/share/doc/papers/memfs/1.t:427: warning: `[I' not defined /otte/src/share/doc/papers/memfs/1.t:427: warning: `[O' not defined /otte/src/share/doc/papers/memfs/1.t:441: warning: `[I' not defined /otte/src/share/doc/papers/memfs/1.t:441: warning: `[O' not defined /otte/src/share/doc/psd/12.make/../../../../usr.bin/make/PSD.doc/tutorial.ms:1084: warning: `Rm' not defined /otte/src/share/doc/psd/12.make/../../../../usr.bin/make/PSD.doc/tutorial.ms:171: warning: `Ix' not defined /otte/src/share/doc/psd/12.make/../../../../usr.bin/make/PSD.doc/tutorial.ms:740: warning: `Rd' not defined /otte/src/share/doc/psd/21.ipc/3.t:340: warning: indent cannot be negative /otte/src/share/doc/psd/21.ipc/4.t:353: warning: indent cannot be negative /otte/src/share/doc/psd/22.rpcgen/../../../../lib/libc/rpc/PSD.doc/rpcgen.ms:13: warning: missing closing delimiter /otte/src/share/doc/psd/22.rpcgen/../../../../lib/libc/rpc/PSD.doc/rpcgen.ms:95: warning: can't find font `CW' /otte/src/share/doc/psd/23.rpc/../../../../lib/libc/rpc/PSD.doc/rpc.prog.ms:181: warning: can't find font `CW' /otte/src/share/doc/psd/23.rpc/../../../../lib/libc/rpc/PSD.doc/rpc.prog.ms:1943: warning: `/"' not defined /otte/src/share/doc/psd/23.rpc/../../../../lib/libc/rpc/PSD.doc/rpc.prog.ms:2065: warning: number register `"' not defined /otte/src/share/doc/psd/23.rpc/../../../../lib/libc/rpc/PSD.doc/rpc.prog.ms:226: warning: missing name /otte/src/share/doc/psd/23.rpc/../../../../lib/libc/rpc/PSD.doc/rpc.prog.ms:233: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/23.rpc/../../../../lib/libc/rpc/PSD.doc/rpc.prog.ms:526: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1025: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1031: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1038: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1064: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:106: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:110: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1115: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1137: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1329: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1333: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1411: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1437: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1475: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1554: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1558: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1608: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:1751: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:17: warning: missing closing delimiter /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:185: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:190: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:208: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:213: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:506: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:510: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:514: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:518: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:522: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:526: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:530: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:556: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:596: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:598: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:602: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:84: warning: can't find font `CW' /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:86: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:875: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:904: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/24.xdr/../../../../lib/libc/rpc/PSD.doc/xdr.nts.ms:90: warning: `sp.5' not defined (probable missing space after `sp') /otte/src/share/doc/psd/25.xdrrfc/../../../../lib/libc/rpc/PSD.doc/xdr.rfc.ms:14: warning: missing closing delimiter /otte/src/share/doc/psd/25.xdrrfc/../../../../lib/libc/rpc/PSD.doc/xdr.rfc.ms:79: warning: can't find font `CW' /otte/src/share/doc/psd/26.rpcrfc/../../../../lib/libc/rpc/PSD.doc/rpc.rfc.ms:13: warning: missing closing delimiter /otte/src/share/doc/psd/26.rpcrfc/../../../../lib/libc/rpc/PSD.doc/rpc.rfc.ms:251: warning: can't find font `CW' /otte/src/share/doc/psd/27.nfsrpc/../../../../lib/libc/rpc/PSD.doc/nfs.rfc.ms:13: warning: missing closing delimiter /otte/src/share/doc/psd/27.nfsrpc/../../../../lib/libc/rpc/PSD.doc/nfs.rfc.ms:566: warning: can't find font `CW' /otte/src/share/doc/psd/28.cvs/../../../../contrib/cvs/doc/cvs-paper.ms:406: warning: indent cannot be negative /otte/src/share/doc/psd/28.cvs/../../../../contrib/cvs/doc/cvs-paper.ms:483: warning: indent cannot be negative /otte/src/share/doc/psd/28.cvs/../../../../contrib/cvs/doc/cvs-paper.ms:600: warning: can't find font `CW' /otte/src/share/doc/psd/title/Title:48: warning: `pt' not defined /otte/src/share/doc/smm/01.setup/1.t:62: warning: can't find font `CW' /otte/src/share/doc/smm/01.setup/2.t:1341: warning: can't find font `C' /otte/src/share/doc/smm/01.setup/2.t:1379: warning: indent cannot be negative /otte/src/share/doc/smm/01.setup/2.t:1423: warning: indent cannot be negative /otte/src/share/doc/smm/01.setup/6.t:672: warning: indent cannot be negative /otte/src/share/doc/smm/02.config/../../../../usr.sbin/config/SMM.doc/5.t:74: warning: indent cannot be negative /otte/src/share/doc/smm/05.fastfs/3.t:162: warning: indent cannot be negative /otte/src/share/doc/smm/05.fastfs/3.t:197: warning: indent cannot be negative /otte/src/share/doc/smm/05.fastfs/4.t:118: warning: indent cannot be negative /otte/src/share/doc/smm/10.named/../../../../contrib/bind/doc/bog/files.me:1104: warning: can't break line /otte/src/share/doc/smm/10.named/../../../../contrib/bind/doc/bog/files.me:714: warning: can't break line /otte/src/share/doc/smm/10.named/../../../../contrib/bind/doc/bog/files.me:779: warning: can't break line /otte/src/share/doc/smm/10.named/../../../../contrib/bind/doc/bog/files.me:792: warning: can't break line /otte/src/share/doc/smm/10.named/../../../../contrib/bind/doc/bog/files.me:925: warning: can't break line /otte/src/share/doc/smm/10.named/../../../../contrib/bind/doc/bog/files.me:963: warning: can't break line /otte/src/share/doc/smm/10.named/../../../../contrib/bind/doc/bog/files.me:996: warning: can't break line /otte/src/share/doc/smm/10.named/../../../../contrib/bind/doc/bog/files.me:997: warning: can't break line /otte/src/share/doc/smm/10.named/../../../../contrib/bind/doc/bog/files.me:998: warning: can't break line /otte/src/share/doc/smm/10.named/../../../../contrib/bind/doc/bog/root.cache:94: warning: can't break line /otte/src/share/doc/smm/title/Title:173: warning: `Dt' not defined /otte/src/share/doc/smm/title/Title:173: warning: `Ed' not defined /otte/src/share/doc/smm/title/Title:173: warning: `OT' not defined /otte/src/share/doc/smm/title/Title:48: warning: `pt' not defined /otte/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/vitut/vi.apwh.ms:109: warning: `LE' not defined /otte/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/vitut/vi.apwh.ms:42: warning: `CB' not defined /otte/src/share/doc/usd/12.vi/viapwh/../../../../../contrib/nvi/docs/USD.doc/vitut/vi.apwh.ms:88: warning: `VL' not defined /otte/src/share/doc/usd/title/Title:48: warning: `pt' not defined /otte/src/sys/boot/i386/loader/../../common/interp_forth.c:243: warning: passing arg 1 of `ficlBuild' discards qualifiers from pointer target type /otte/src/sys/boot/i386/loader/../../common/isapnp.c:69: warning: `isapnp_read' defined but not used /otte/src/sys/boot/i386/loader/../../common/load_aout.c:230: warning: long unsigned int format, unsigned int arg (arg 2) /otte/src/sys/boot/i386/loader/../../common/load_aout.c:240: warning: long unsigned int format, unsigned int arg (arg 2) /otte/src/sys/boot/i386/loader/../../common/pnp.c:20: warning: `pnp_readconf' declared `static' but never defined /otte/src/sys/boot/i386/loader/../../common/pnp.c:21: warning: `pnp_scankernel' declared `static' but never defined /otte/src/sys/boot/i386/loader/main.c:163: warning: `biosdev' might be used uninitialized in this function /otte/src/sys/boot/i386/loader/main.c:80: warning: return type of `main' is not `int' /otte/src/sys/modules/amr/../../dev/amr/amr.c:1015: warning: `amr_wait_command' defined but not used /otte/src/sys/modules/amr/../../dev/amr/amr.c:1218: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type /otte/src/sys/modules/amr/../../dev/amr/amr.c:1518: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type /otte/src/sys/modules/amr/../../dev/amr/amr.c:1549: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type /otte/src/sys/modules/amr/../../dev/amr/amr.c:171: warning: cast discards qualifiers from pointer target type /otte/src/sys/modules/fxp/../../pci/if_fxp.c:1475: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type /otte/src/sys/modules/fxp/../../pci/if_fxp.c:1532: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type /otte/src/sys/modules/fxp/../../pci/if_fxp.c:2049: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type /otte/src/sys/modules/ibcs2/../../i386/ibcs2/ibcs2_sysent.c:18: warning: cast discards qualifiers from pointer target type /otte/src/sys/modules/linux/../../i386/linux/linux_sysent.c:19: warning: cast discards qualifiers from pointer target type /otte/src/sys/modules/nullfs/../../miscfs/nullfs/null_vfsops.c:422: warning: function declaration isn't a prototype /otte/src/sys/modules/splash/bmp/splash_bmp.c:481: warning: cast discards qualifiers from pointer target type /otte/src/sys/modules/splash/bmp/splash_bmp.c:505: warning: cast discards qualifiers from pointer target type /otte/src/sys/modules/splash/pcx/splash_pcx.c:201: warning: passing arg 2 of pointer to function discards qualifiers from pointer target type /otte/src/sys/modules/svr4/../../svr4/svr4_resource.c:219: warning: implicit declaration of function `dosetrlimit' /otte/src/sys/modules/svr4/../../svr4/svr4_stream.c:2252: warning: assignment from incompatible pointer type /otte/src/sys/modules/svr4/../../svr4/svr4_sysent.c:21: warning: cast discards qualifiers from pointer target type /otte/src/sys/modules/svr4/../../svr4/svr4_sysvec.c:176: warning: initialization from incompatible pointer type /otte/src/sys/modules/syscons/daemon/daemon_saver.c:173: warning: array subscript has type `char' /otte/src/sys/modules/syscons/daemon/daemon_saver.c:180: warning: array subscript has type `char' /otte/src/sys/modules/syscons/daemon/daemon_saver.c:205: warning: array subscript has type `char' /otte/src/sys/modules/syscons/snake/snake_saver.c:110: warning: array subscript has type `char' /otte/src/sys/modules/syscons/snake/snake_saver.c:88: warning: array subscript has type `char' /otte/src/sys/modules/syscons/star/star_saver.c:98: warning: array subscript has type `char' /otte/src/sys/modules/union/../../miscfs/union/union_vnops.c:1801: warning: unused variable `un' /otte/src/sys/modules/vn/../../dev/vn/vn.c:415: warning: passing arg 2 of `vm_pager_strategy' from incompatible pointer type /otte/src/usr.bin/ar/contents.c:80: warning: `%c' yields only last 2 digits of year in some locales /otte/src/usr.bin/at/at.c:492: warning: `%x' yields only last 2 digits of year in some locales /otte/src/usr.bin/calendar/io.c:147: warning: `%c' yields only last 2 digits of year in some locales /otte/src/usr.bin/chat/chat.c:269: warning: value computed is not used /otte/src/usr.bin/colldef/scan.l:638: warning: `yyunput' defined but not used /otte/src/usr.bin/colldef/scan.l:638: warning: `yyunput' defined but not used /otte/src/usr.bin/compile_et/../../contrib/com_err/getarg.c:178: warning: assignment makes pointer from integer without a cast /otte/src/usr.bin/compile_et/../../contrib/com_err/getarg.c:197: warning: assignment makes pointer from integer without a cast /otte/src/usr.bin/fetch/main.c:284: warning: passing arg 1 of `sigdelset' discards qualifiers from pointer target type /otte/src/usr.bin/ftp/cmds.c:661: warning: initialization makes integer from pointer without a cast /otte/src/usr.bin/ftp/cmds.c:892: warning: assignment makes pointer from integer without a cast /otte/src/usr.bin/ftp/cmds.c:906: warning: initialization makes integer from pointer without a cast /otte/src/usr.bin/leave/leave.c:150: warning: unknown conversion type character `+' in format /otte/src/usr.bin/login/login.c:135: warning: argument `argv' might be clobbered by `longjmp' or `vfork' /otte/src/usr.bin/login/login.c:769: warning: suggest explicit braces to avoid ambiguous `else' /otte/src/usr.bin/ncal/ncal.c:390: warning: unknown conversion type character `F' in format /otte/src/usr.bin/ncal/ncal.c:581: warning: flag `O' used with type `B' /otte/src/usr.bin/ncal/ncal.c:672: warning: flag `O' used with type `B' /otte/src/usr.bin/telnet/commands.c:2906: warning: assignment makes pointer from integer without a cast /otte/src/usr.bin/vi/../../contrib/nvi/vi/getc.c:182: warning: passing arg 4 of `db_get' from incompatible pointer type /otte/src/usr.bin/vi/../../contrib/nvi/vi/getc.c:52: warning: passing arg 3 of `db_eget' from incompatible pointer type /otte/src/usr.bin/vi/../../contrib/nvi/vi/v_txt.c:2226: warning: comparison of distinct pointer types lacks a cast /otte/src/usr.bin/vi/../../contrib/nvi/vi/v_txt.c:2244: warning: comparison of distinct pointer types lacks a cast /otte/src/usr.bin/vi/../../contrib/nvi/vi/v_ulcase.c:119: warning: passing arg 4 of `db_get' from incompatible pointer type /otte/src/usr.bin/vmstat/vmstat.c:484: warning: `pgtok' redefined /otte/src/usr.bin/vmstat/vmstat.c:484: warning: `pgtok' redefined /otte/src/usr.sbin/amd/doc/../../../contrib/amd/doc/am-utils.texi:6201: warning: unlikely character [ in @var. /otte/src/usr.sbin/amd/doc/../../../contrib/amd/doc/am-utils.texi:6201: warning: unlikely character ] in @var. /otte/src/usr.sbin/apmd/apmdlex.l:440: warning: `yyunput' defined but not used /otte/src/usr.sbin/config/lang.l:1027: warning: `yy_flex_realloc' defined but not used /otte/src/usr.sbin/config/lang.l:1027: warning: `yy_flex_realloc' defined but not used /otte/src/usr.sbin/i4b/isdnd/log.c:174: warning: #warning "FreeBSD ncurses is buggy: write to last column = auto newline!" /otte/src/usr.sbin/i4b/isdnd/log.c:174: warning: #warning "FreeBSD ncurses is buggy: write to last column = auto newline!" /otte/src/usr.sbin/i4b/isdnmonitor/main.c:525: warning: #warning "FreeBSD ncurses is buggy: write to last column = auto newline!" /otte/src/usr.sbin/i4b/isdnmonitor/main.c:525: warning: #warning "FreeBSD ncurses is buggy: write to last column = auto newline!" /otte/src/usr.sbin/lpr/lpc/lpc.c:142: warning: function declaration isn't a prototype /otte/src/usr.sbin/lpr/lpd/lpd.c:129: warning: `finet' might be used uninitialized in this function /otte/src/usr.sbin/lpr/lpd/lpd.c:314: warning: `domain' might be used uninitialized in this function /otte/src/usr.sbin/lpr/lpd/lpd.c:314: warning: `s' might be used uninitialized in this function /otte/src/usr.sbin/ndp/ndp.c:244: warning: previous implicit declaration of `rtrlist' /otte/src/usr.sbin/ndp/ndp.c:826: warning: `rtrlist' was previously implicitly declared to return `int' /otte/src/usr.sbin/ndp/ndp.c:826: warning: type mismatch with previous implicit declaration /otte/src/usr.sbin/ntp/libntp/../../../contrib/ntp/libntp/gpstolfp.c:27: warning: decimal constant is so large that it is unsigned /otte/src/usr.sbin/rarpd/rarpd.c:705: warning: passing arg 2 of `ether_ntohost' from incompatible pointer type /otte/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/print-token.c:74: warning: assignment of read-only location /otte/src/usr.sbin/tcpdump/tcpslice/gwtm2secs.c:49: warning: suggest explicit braces to avoid ambiguous `else' /otte/src/usr.sbin/trpt/trpt.c:199: warning: passing arg 4 of `qsort' from incompatible pointer type /otte/src/usr.sbin/ypset/ypset.c:87: warning: passing arg 2 of `bcopy' makes pointer from integer without a cast /usr/obj/otte/src/i386/usr/include/machine/param.h:158: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/machine/param.h:158: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/sys/cdrio.h:59: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/sys/cdrio.h:59: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/sys/cdrio.h:59: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/sys/cdrio.h:59: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/sys/cdrio.h:59: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/sys/cdrio.h:59: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/otte/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/otte/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/otte/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/otte/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/otte/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:44: warning: `B50' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:44: warning: `B50' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:44: warning: `B50' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:44: warning: `B50' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:44: warning: `B50' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:44: warning: `B50' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:45: warning: `B75' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:45: warning: `B75' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:45: warning: `B75' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:45: warning: `B75' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:45: warning: `B75' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:45: warning: `B75' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:46: warning: `B110' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:46: warning: `B110' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:46: warning: `B110' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:46: warning: `B110' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:46: warning: `B110' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:46: warning: `B110' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:47: warning: `B134' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:47: warning: `B134' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:47: warning: `B134' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:47: warning: `B134' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:47: warning: `B134' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:47: warning: `B134' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:48: warning: `B150' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:48: warning: `B150' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:48: warning: `B150' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:48: warning: `B150' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:48: warning: `B150' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:48: warning: `B150' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:49: warning: `B200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:49: warning: `B200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:49: warning: `B200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:49: warning: `B200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:49: warning: `B200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:49: warning: `B200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:50: warning: `B300' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:50: warning: `B300' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:50: warning: `B300' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:50: warning: `B300' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:50: warning: `B300' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:50: warning: `B300' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:51: warning: `B600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:51: warning: `B600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:51: warning: `B600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:51: warning: `B600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:51: warning: `B600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:51: warning: `B600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:52: warning: `B1200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:52: warning: `B1200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:52: warning: `B1200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:52: warning: `B1200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:52: warning: `B1200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:52: warning: `B1200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:53: warning: `B1800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:53: warning: `B1800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:53: warning: `B1800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:53: warning: `B1800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:53: warning: `B1800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:53: warning: `B1800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:54: warning: `B2400' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:54: warning: `B2400' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:54: warning: `B2400' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:54: warning: `B2400' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:54: warning: `B2400' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:54: warning: `B2400' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:55: warning: `B4800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:55: warning: `B4800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:55: warning: `B4800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:55: warning: `B4800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:55: warning: `B4800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:55: warning: `B4800' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:56: warning: `B9600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:56: warning: `B9600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:56: warning: `B9600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:56: warning: `B9600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:56: warning: `B9600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:56: warning: `B9600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:57: warning: `EXTA' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:57: warning: `EXTA' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:57: warning: `EXTA' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:57: warning: `EXTA' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:57: warning: `EXTA' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:57: warning: `EXTA' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:58: warning: `EXTB' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:58: warning: `EXTB' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:58: warning: `EXTB' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:58: warning: `EXTB' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:58: warning: `EXTB' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:58: warning: `EXTB' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:59: warning: `B57600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:59: warning: `B57600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:59: warning: `B57600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:59: warning: `B57600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:59: warning: `B57600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:59: warning: `B57600' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:60: warning: `B115200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:60: warning: `B115200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:60: warning: `B115200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:60: warning: `B115200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:60: warning: `B115200' redefined /usr/obj/otte/src/i386/usr/include/sys/ttydev.h:60: warning: `B115200' redefined /usr/obj/otte/src/i386/usr/include/sys/wormio.h:102: warning: `CDRIOCBLANK' redefined /usr/obj/otte/src/i386/usr/include/sys/wormio.h:102: warning: `CDRIOCBLANK' redefined /usr/obj/otte/src/i386/usr/include/sys/wormio.h:102: warning: `CDRIOCBLANK' redefined /usr/obj/otte/src/i386/usr/include/sys/wormio.h:102: warning: `CDRIOCBLANK' redefined /usr/obj/otte/src/i386/usr/include/sys/wormio.h:102: warning: `CDRIOCBLANK' redefined /usr/obj/otte/src/i386/usr/include/sys/wormio.h:102: warning: `CDRIOCBLANK' redefined /usr/obj/otte/src/i386/usr/include/termios.h:206: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:206: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:206: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:206: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:206: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:206: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:207: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:207: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:207: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:207: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:207: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:207: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:208: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:208: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:208: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:208: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:208: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:208: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:209: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:209: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:209: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:209: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:209: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:209: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:210: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:210: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:210: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:210: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:210: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:210: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:211: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:211: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:211: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:211: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:211: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:211: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:212: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:212: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:212: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:212: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:212: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:212: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:213: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:213: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:213: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:213: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:213: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:213: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:214: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:214: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:214: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:214: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:214: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:214: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:215: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:215: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:215: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:215: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:215: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:215: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:216: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:216: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:216: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:216: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:216: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:216: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:217: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:217: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:217: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:217: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:217: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:217: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:218: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:218: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:218: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:218: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:218: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:218: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:225: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:225: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:225: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:225: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:225: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:225: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:227: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:227: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:227: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:227: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:227: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:227: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:229: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:229: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:229: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:229: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:229: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:229: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:230: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:230: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:230: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:230: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:230: warning: this is the location of the previous definition /usr/obj/otte/src/i386/usr/include/termios.h:230: warning: this is the location of the previous definition 3.t:203: warning: indent cannot be negative 3.t:363: warning: indent cannot be negative 3.t:626: warning: indent cannot be negative 3.t:769: warning: indent cannot be negative 4.t:645: warning: indent cannot be negative :1112: warning: indent cannot be negative :1270: warning: indent cannot be negative :2538: warning: `FK' not defined :331: warning: indent cannot be negative :34: warning: number register `xx' not defined :3554: warning: `1.6' not defined A.gt:110: warning: `vS' not defined A.gt:14: warning: number register `v' not defined A.gt:154: warning: number register `x' not defined A.gt:351: warning: `vE' not defined A.gt:3: warning: only `z' and `u' scale indicators valid in this context External Data Representation ... /otte/src/share/doc/psd/25.xdrrfc/../../../../lib/libc/rpc/PSD.doc/xdr.rfc.ms:13: warning: number register `PN' not defined Network Programming ... /otte/src/share/doc/psd/23.rpc/../../../../lib/libc/rpc/PSD.doc/rpc.prog.ms:8: warning: number register `PN' not defined appendix.ms:107: warning: `vS' not defined appendix.ms:131: warning: number register `x' not defined appendix.ms:14: warning: number register `v' not defined appendix.ms:271: warning: `vE' not defined appendix.ms:3: warning: only `z' and `u' scale indicators valid in this context appendix.tmp:134: warning: number register `x' not defined appendix.tmp:14: warning: number register `v' not defined appendix.tmp:3: warning: only `z' and `u' scale indicators valid in this context appendix.tmp:848: warning: only `z' and `u' scale indicators valid in this context bootparam_prot_svc.c:59: warning: passing arg 3 of pointer to function from incompatible pointer type bootparam_prot_svc.c:67: warning: passing arg 3 of pointer to function from incompatible pointer type bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() bucomm.o(.text+0x343): warning: mktemp() possibly used unsafely; consider using mkstemp() choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() choose-temp.o(.text+0x13e): warning: mktemp() possibly used unsafely; consider using mkstemp() crunchgen.o(.text+0x1f8): warning: mktemp() possibly used unsafely; consider using mkstemp() ctm_pass2.o(.text+0x7fa): warning: tempnam() possibly used unsafely; consider using mkstemp() dhclient.o(.text+0x2c1b): warning: mktemp() possibly used unsafely; consider using mkstemp() eval.o(.text+0x417): warning: mktemp() possibly used unsafely; consider using mkstemp() indxbib.o(.text+0x40b): warning: mktemp() possibly used unsafely; consider using mkstemp() kernmalloc.ms:408: warning: number register `OI' not defined kernmalloc.ms:66: warning: number register `d' not defined list.o(.text+0xb0a): warning: mktemp() possibly used unsafely; consider using mkstemp() list.o(.text+0xb0a): warning: mktemp() possibly used unsafely; consider using mkstemp() main.o(.text+0x33a): warning: mktemp() possibly used unsafely; consider using mkstemp() mk-amd-map.o(.text+0x575): warning: mktemp() possibly used unsafely; consider using mkstemp() mount_portal.o(.text+0xeb): warning: mktemp() possibly used unsafely; consider using mkstemp() patch.o(.text+0xc8): warning: mktemp() possibly used unsafely; consider using mkstemp() printjob.o(.text+0xf1): warning: mktemp() possibly used unsafely; consider using mkstemp() quit.o(.text+0xb76): warning: mktemp() possibly used unsafely; consider using mkstemp() rcsedit.o(.text+0x1936): warning: mktemp() possibly used unsafely; consider using mkstemp() rcsedit.o(.text+0x1936): warning: mktemp() possibly used unsafely; consider using mkstemp() rcsedit.o(.text+0x1936): warning: mktemp() possibly used unsafely; consider using mkstemp() rcsedit.o(.text+0x1936): warning: mktemp() possibly used unsafely; consider using mkstemp() rcsfnms.o(.text+0xd0): warning: mktemp() possibly used unsafely; consider using mkstemp() rcsfnms.o(.text+0xd0): warning: mktemp() possibly used unsafely; consider using mkstemp() rcsfnms.o(.text+0xd0): warning: mktemp() possibly used unsafely; consider using mkstemp() rcsfnms.o(.text+0xd0): warning: mktemp() possibly used unsafely; consider using mkstemp() regex.texi:876: warning: unlikely character , in @var. regex.texi:880: warning: unlikely character , in @var. sdiff.o(.text+0x10c7): warning: tmpnam() possibly used unsafely; consider using mkstemp() tables.o(.text+0x348): warning: tempnam() possibly used unsafely; consider using mkstemp() texindex.o(.text+0xbd): warning: mktemp() possibly used unsafely; consider using mkstemp() texindex.o(.text+0xbd): warning: mktemp() possibly used unsafely; consider using mkstemp() xlint.o(.text+0x4b2): warning: mktemp() possibly used unsafely; consider using mkstemp() xstr.o(.text+0xbe): warning: mktemp() possibly used unsafely; consider using mkstemp() y.tab.c:269: warning: implicit declaration of function `yylex' y.tab.c:310: warning: implicit declaration of function `yyerror' yppasswdd_server.o(.text+0xba9): warning: mktemp() possibly used unsafely; consider using mkstemp() ----------------------------------- END ----------------------------------- ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 14:49:38 2000 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 903EA37B6C3 for ; Mon, 17 Apr 2000 14:49:35 -0700 (PDT) (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 OAA02329; Mon, 17 Apr 2000 14:51:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Mon, 17 Apr 2000 23:17:15 +0200." <12411.956006235@critter.freebsd.dk> Date: Mon, 17 Apr 2000 14:51:20 -0700 Message-ID: <2326.956008280@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a machine which isn't doing much right now, so I have decided > to set it up as an automatic "FreeBSD Build checker". Welcome to the current.freebsd.org game. :) > Once per day the machine cvsups, checks out a virgin source tree, > tries to build GENERIC, GENERIC98, LINT and world. If any of these > builds fail it will send a report like this. > > On Sundays the report will always be sent. > > Once I have this tested a bit more, I will start mailing the the > reports directly to current@freebsd.org And now we get into a slightly twitchy area... These error messages can be quite long and annoying, far too detailed for the likes of the -current mailing list, which is why I've been sending them only to an opt-in alias called "build-reports@freebsd.org" which sends a success/failure summary like yours and include the last 100 lines of failure output for debugging. It also does this for both the RELENG_4 branch and -current. That said, I've also done a singularly bad job of actually letting people know that build-reports even exists so I wouldn't expect you or anyone else (except maybe Bill Paul) to have known about it. It's just an alias on hub.freebsd.org right now and not a real majordomo-managed mailing list, so I wasn't inclined to take on the workload of managing the alias. It does at least log its results to the build-reports mail archive so anyone looking in /home/mail/build-reports on hub can also spy on the current status of both active branches. If there's a real interest in this, then this should obviously be created as a real mailing list and probably split into build-reports-stable and build-reports-current for people who only want one or the other. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 14:52: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from modemcable127.61-201-24.mtl.mc.videotron.net (modemcable127.61-201-24.mtl.mc.videotron.net [24.201.61.127]) by hub.freebsd.org (Postfix) with SMTP id 6446837B5A8 for ; Mon, 17 Apr 2000 14:52:04 -0700 (PDT) (envelope-from patrick@mindstep.com) Received: (qmail 53940 invoked from network); 17 Apr 2000 21:52:02 -0000 Received: from patrak.local.mindstep.com (HELO PATRAK) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 17 Apr 2000 21:52:02 -0000 Message-ID: <01a501bfa8b7$19f2fe60$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "Poul-Henning Kamp" Cc: References: <12411.956006235@critter.freebsd.dk> Subject: Re: FreeBSD Build status Date: Mon, 17 Apr 2000 17:51:35 -0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_01A2_01BFA895.92CBDA90" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_01A2_01BFA895.92CBDA90 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit Hi, I have a patch against these warnings. They are the result of a function being called with a pointer to a function rather than a string... /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1655: warning: passing arg 1 of `warning' from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1655: warning: passing arg 1 of `warning' from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1678: warning: passing arg 1 of `warning' from incompatible pointer type /otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1678: warning: passing arg 1 of `warning' from incompatible pointer type The patch: --- c-common.c.orig Mon Nov 1 13:41:09 1999 +++ c-common.c Sat Apr 8 06:32:52 2000 @@ -1652,7 +1652,7 @@ /* There should be an int arg to control the string arg. */ if (params == 0) { - warning (tfaff); + tfaff (); return; } if (info->first_arg_num != 0) @@ -1675,7 +1675,7 @@ /* There should be an unsigned char * arg before the string arg. */ if (params == 0) { - warning (tfaff); + tfaff (); return; } if (info->first_arg_num != 0) Should I just send a PR ? Patrick. ------=_NextPart_000_01A2_01BFA895.92CBDA90 Content-Type: application/octet-stream; name="c-common.c.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="c-common.c.patch" --- c-common.c.orig Mon Nov 1 13:41:09 1999=0A= +++ c-common.c Sat Apr 8 06:32:52 2000=0A= @@ -1652,7 +1652,7 @@=0A= /* There should be an int arg to control the string arg. */=0A= if (params =3D=3D 0)=0A= {=0A= - warning (tfaff);=0A= + tfaff ();=0A= return;=0A= }=0A= if (info->first_arg_num !=3D 0)=0A= @@ -1675,7 +1675,7 @@=0A= /* There should be an unsigned char * arg before the string arg. */=0A= if (params =3D=3D 0)=0A= {=0A= - warning (tfaff);=0A= + tfaff ();=0A= return;=0A= }=0A= if (info->first_arg_num !=3D 0)=0A= ------=_NextPart_000_01A2_01BFA895.92CBDA90-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 14:58:55 2000 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 30FF037B9A9 for ; Mon, 17 Apr 2000 14:58:52 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA12607; Mon, 17 Apr 2000 23:58:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Mon, 17 Apr 2000 14:51:20 PDT." <2326.956008280@zippy.cdrom.com> Date: Mon, 17 Apr 2000 23:58:44 +0200 Message-ID: <12605.956008724@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <2326.956008280@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >That said, I've also done a singularly bad job of actually letting >people know that build-reports even exists so I wouldn't expect you or >anyone else (except maybe Bill Paul) to have known about it. It's >just an alias on hub.freebsd.org right now and not a real >majordomo-managed mailing list, so I wasn't inclined to take on the >workload of managing the alias. It does at least log its results to >the build-reports mail archive so anyone looking in /home/mail/build-reports >on hub can also spy on the current status of both active branches. But does this also check the kernels ? It was my understanding that it only did world/release ? As for the lists being tedious and long: I've sorted the content by relevance, and it was my hope that over time they would shrink to zero if we annoyed people enough with them. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 15: 2:43 2000 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 13FDC37B8B6 for ; Mon, 17 Apr 2000 15:02:40 -0700 (PDT) (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 QAA52927; Mon, 17 Apr 2000 16:02:38 -0600 (MDT) (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 QAA73643; Mon, 17 Apr 2000 16:02:08 -0600 (MDT) Message-Id: <200004172202.QAA73643@harmony.village.org> To: Poul-Henning Kamp Subject: Re: FreeBSD Build status Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Apr 2000 23:17:15 +0200." <12411.956006235@critter.freebsd.dk> References: <12411.956006235@critter.freebsd.dk> Date: Mon, 17 Apr 2000 16:02:08 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <12411.956006235@critter.freebsd.dk> Poul-Henning Kamp writes: : awi.o(.text+0x3b4): undefined reference to `memcmp' : awi.o(.text+0x3cf): undefined reference to `memset' What I want to know is why I don't get these with the GENERIC + awi config file I have :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 15: 5: 2 2000 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 1BE9B37B5A8 for ; Mon, 17 Apr 2000 15:04:58 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id AAA12682; Tue, 18 Apr 2000 00:04:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Mon, 17 Apr 2000 16:02:08 MDT." <200004172202.QAA73643@harmony.village.org> Date: Tue, 18 Apr 2000 00:04:43 +0200 Message-ID: <12680.956009083@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004172202.QAA73643@harmony.village.org>, Warner Losh writes: >In message <12411.956006235@critter.freebsd.dk> Poul-Henning Kamp writes: >: awi.o(.text+0x3b4): undefined reference to `memcmp' >: awi.o(.text+0x3cf): undefined reference to `memset' > >What I want to know is why I don't get these with the GENERIC + awi >config file I have :-( That is probably a Bruce question, but I would suspect that LINT is more paranoid about disabling GCC builtins ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 15: 7: 5 2000 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 3CC0D37B8A0 for ; Mon, 17 Apr 2000 15:07:03 -0700 (PDT) (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 PAA02443; Mon, 17 Apr 2000 15:08:48 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Mon, 17 Apr 2000 23:58:44 +0200." <12605.956008724@critter.freebsd.dk> Date: Mon, 17 Apr 2000 15:08:48 -0700 Message-ID: <2440.956009328@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But does this also check the kernels ? It was my understanding that > it only did world/release ? It only does the world/release (and it's the chrooted make release "world build" which is reported on, not the host system's BTW) but could easily add a kernel build just for the benefit of the mailing list folks. It would be trivial to add. > As for the lists being tedious and long: I've sorted the content by > relevance, and it was my hope that over time they would shrink to > zero if we annoyed people enough with them. I think that's too much annoyance, really. I can see most people simply unsubscribing from -current in the face of a mail that long and tedious (and daily) and -current was never created as a place for daemons to talk to people in any case, it was created as a discussion forum. Let's do this, by all means, but let's plase do it elsewhere. Anyone who starts sending daily automated anythings to any of our "top level" mailing lists will classify themselves as a spammer on my and many other people's radar. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 15:14:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 9CA3437B5E8 for ; Mon, 17 Apr 2000 15:14:15 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id QAA23713; Mon, 17 Apr 2000 16:13:46 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id QAA09088; Mon, 17 Apr 2000 16:13:45 -0600 (MDT) (envelope-from nate) Date: Mon, 17 Apr 2000 16:13:45 -0600 (MDT) Message-Id: <200004172213.QAA09088@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-Reply-To: <12680.956009083@critter.freebsd.dk> References: <200004172202.QAA73643@harmony.village.org> <12680.956009083@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >: awi.o(.text+0x3b4): undefined reference to `memcmp' > >: awi.o(.text+0x3cf): undefined reference to `memset' > > > >What I want to know is why I don't get these with the GENERIC + awi > >config file I have :-( Are you compiling with optimization turned on? I believe mem* are inlined if optimization is enabled. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 15:14:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (Postfix) with SMTP id C633F37B7BF for ; Mon, 17 Apr 2000 15:14:18 -0700 (PDT) (envelope-from nordwick@scam.xcf.berkeley.edu) Received: (qmail 90802 invoked by uid 27268); 17 Apr 2000 22:14:10 -0000 Message-ID: <20000417221410.90801.qmail@scam.xcf.berkeley.edu> To: freebsd-current@freebsd.org Subject: cvsup crash MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <90799.956009649.1@scam.XCF.Berkeley.EDU> Date: Mon, 17 Apr 2000 15:14:10 -0700 From: Jason Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I didn't know here to send this, but I thought that other people trying to keep current might have had this problem before: When I run cvsup with the default cvsup file from /usr/share/examples/cvsup/cvs-supfile (after putting in the correct cvsup server address) it crashes: bash-2.03# cvsup cvs-supfile *** *** runtime error: *** Segmentation violation - possible attempt to dereference NIL *** pc = 0x81f0708 = Cat + 0x18 in /b/jdp/pm3/pm3/libs/m3core/src/text/Text.m3 *** use option @M3stackdump to get a stack trace Abort trap (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 15:43: 9 2000 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 8D1D437BA77 for ; Mon, 17 Apr 2000 15:43:06 -0700 (PDT) (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 QAA53055; Mon, 17 Apr 2000 16:43:05 -0600 (MDT) (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 QAA85349; Mon, 17 Apr 2000 16:42:34 -0600 (MDT) Message-Id: <200004172242.QAA85349@harmony.village.org> To: nate@yogotech.com (Nate Williams) Subject: Re: FreeBSD Build status Cc: Poul-Henning Kamp , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Apr 2000 16:13:45 MDT." <200004172213.QAA09088@nomad.yogotech.com> References: <200004172213.QAA09088@nomad.yogotech.com> <200004172202.QAA73643@harmony.village.org> <12680.956009083@critter.freebsd.dk> Date: Mon, 17 Apr 2000 16:42:34 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004172213.QAA09088@nomad.yogotech.com> Nate Williams writes: : Are you compiling with optimization turned on? I believe mem* are : inlined if optimization is enabled. Don't think so. Both build -O. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 15:45: 8 2000 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 574D137B8C2 for ; Mon, 17 Apr 2000 15:45:06 -0700 (PDT) (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 QAA53072; Mon, 17 Apr 2000 16:45:05 -0600 (MDT) (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 QAA85492; Mon, 17 Apr 2000 16:44:35 -0600 (MDT) Message-Id: <200004172244.QAA85492@harmony.village.org> Subject: Re: FreeBSD Build status Cc: Poul-Henning Kamp , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Apr 2000 16:02:08 MDT." <200004172202.QAA73643@harmony.village.org> References: <200004172202.QAA73643@harmony.village.org> <12411.956006235@critter.freebsd.dk> Date: Mon, 17 Apr 2000 16:44:34 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004172202.QAA73643@harmony.village.org> Warner Losh writes: : In message <12411.956006235@critter.freebsd.dk> Poul-Henning Kamp writes: : : awi.o(.text+0x3b4): undefined reference to `memcmp' : : awi.o(.text+0x3cf): undefined reference to `memset' : : What I want to know is why I don't get these with the GENERIC + awi : config file I have :-( Its the -fno-builtin that's causing it :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 15:45:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 9C98D37BB8E for ; Mon, 17 Apr 2000 15:45:14 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id QAA23947; Mon, 17 Apr 2000 16:44:53 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id QAA09270; Mon, 17 Apr 2000 16:44:52 -0600 (MDT) (envelope-from nate) Date: Mon, 17 Apr 2000 16:44:52 -0600 (MDT) Message-Id: <200004172244.QAA09270@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: nate@yogotech.com (Nate Williams), Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-Reply-To: <200004172242.QAA85349@harmony.village.org> References: <200004172213.QAA09088@nomad.yogotech.com> <200004172202.QAA73643@harmony.village.org> <12680.956009083@critter.freebsd.dk> <200004172242.QAA85349@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Are you compiling with optimization turned on? I believe mem* are > : inlined if optimization is enabled. > > Don't think so. Both build -O. Poul's build may not have optimization turned on, since it's controlled by /etc/make.conf. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 15:47:50 2000 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 8EFDB37BAD0 for ; Mon, 17 Apr 2000 15:47:47 -0700 (PDT) (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 QAA53089; Mon, 17 Apr 2000 16:47:46 -0600 (MDT) (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 QAA85536; Mon, 17 Apr 2000 16:47:15 -0600 (MDT) Message-Id: <200004172247.QAA85536@harmony.village.org> To: nate@yogotech.com (Nate Williams) Subject: Re: FreeBSD Build status Cc: Poul-Henning Kamp , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Apr 2000 16:44:52 MDT." <200004172244.QAA09270@nomad.yogotech.com> References: <200004172244.QAA09270@nomad.yogotech.com> <200004172213.QAA09088@nomad.yogotech.com> <200004172202.QAA73643@harmony.village.org> <12680.956009083@critter.freebsd.dk> <200004172242.QAA85349@harmony.village.org> Date: Mon, 17 Apr 2000 16:47:15 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004172244.QAA09270@nomad.yogotech.com> Nate Williams writes: : > : Are you compiling with optimization turned on? I believe mem* are : > : inlined if optimization is enabled. : > : > Don't think so. Both build -O. : : Poul's build may not have optimization turned on, since it's controlled : by /etc/make.conf. It isn't something specific to Poul's system. I've recreated it here as well. I've also tracked it down to the -fno-builtin that is in LINT, but not in GENERIC. Now, to think about what to do about it... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 15:50:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 204E037B801 for ; Mon, 17 Apr 2000 15:50:34 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id QAA24005; Mon, 17 Apr 2000 16:50:28 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id QAA09311; Mon, 17 Apr 2000 16:50:27 -0600 (MDT) (envelope-from nate) Date: Mon, 17 Apr 2000 16:50:27 -0600 (MDT) Message-Id: <200004172250.QAA09311@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: nate@yogotech.com (Nate Williams), Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-Reply-To: <200004172247.QAA85536@harmony.village.org> References: <200004172244.QAA09270@nomad.yogotech.com> <200004172213.QAA09088@nomad.yogotech.com> <200004172202.QAA73643@harmony.village.org> <12680.956009083@critter.freebsd.dk> <200004172242.QAA85349@harmony.village.org> <200004172247.QAA85536@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : > : Are you compiling with optimization turned on? I believe mem* are > : > : inlined if optimization is enabled. > : > > : > Don't think so. Both build -O. > : > : Poul's build may not have optimization turned on, since it's controlled > : by /etc/make.conf. > > It isn't something specific to Poul's system. I've recreated it here > as well. I've also tracked it down to the -fno-builtin that is in > LINT, but not in GENERIC. Now, to think about what to do about it... I thought that the use of mem* and friends violated KNF. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 16: 3: 9 2000 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 61E0D37BB80 for ; Mon, 17 Apr 2000 16:03:04 -0700 (PDT) (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 RAA53149; Mon, 17 Apr 2000 17:03:02 -0600 (MDT) (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 RAA85989; Mon, 17 Apr 2000 17:02:32 -0600 (MDT) Message-Id: <200004172302.RAA85989@harmony.village.org> To: nate@yogotech.com (Nate Williams) Subject: Re: FreeBSD Build status Cc: Poul-Henning Kamp , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Apr 2000 16:50:27 MDT." <200004172250.QAA09311@nomad.yogotech.com> References: <200004172250.QAA09311@nomad.yogotech.com> <200004172244.QAA09270@nomad.yogotech.com> <200004172213.QAA09088@nomad.yogotech.com> <200004172202.QAA73643@harmony.village.org> <12680.956009083@critter.freebsd.dk> <200004172242.QAA85349@harmony.village.org> <200004172247.QAA85536@harmony.village.org> Date: Mon, 17 Apr 2000 17:02:31 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004172250.QAA09311@nomad.yogotech.com> Nate Williams writes: : I thought that the use of mem* and friends violated KNF. They do, iirc. However, this driver tries to be maximally portable and choses to use the NetBSD convention. I've added compat code so that differences between the two drivers can be held to a minimum. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 16: 5:55 2000 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 CB79B37BBC0 for ; Mon, 17 Apr 2000 16:05:52 -0700 (PDT) (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 RAA53171; Mon, 17 Apr 2000 17:05:51 -0600 (MDT) (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 RAA86034; Mon, 17 Apr 2000 17:05:21 -0600 (MDT) Message-Id: <200004172305.RAA86034@harmony.village.org> Subject: Re: FreeBSD Build status To: Poul-Henning Kamp , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 17 Apr 2000 17:02:31 MDT." <200004172302.RAA85989@harmony.village.org> References: <200004172302.RAA85989@harmony.village.org> <200004172250.QAA09311@nomad.yogotech.com> <200004172244.QAA09270@nomad.yogotech.com> <200004172213.QAA09088@nomad.yogotech.com> <200004172202.QAA73643@harmony.village.org> <12680.956009083@critter.freebsd.dk> <200004172242.QAA85349@harmony.village.org> <200004172247.QAA85536@harmony.village.org> Date: Mon, 17 Apr 2000 17:05:21 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG LINT is now building again. I went ahead and fixed the vtdriver not defined problem by removing it from isa_comapt.h. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 17: 0:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id 9E1F737B844 for ; Mon, 17 Apr 2000 17:00:20 -0700 (PDT) (envelope-from areilly@nsw.bigpond.net.au) Received: from areilly.bpc-users.org (CPE-144-132-171-71.nsw.bigpond.net.au [144.132.171.71]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id KAA21628 for ; Tue, 18 Apr 2000 10:00:17 +1000 (EST) Received: (qmail 69247 invoked by uid 1000); 18 Apr 2000 00:00:16 -0000 From: "Andrew Reilly" Date: Tue, 18 Apr 2000 10:00:16 +1000 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: FreeBSD Build status Message-ID: <20000418100016.A67726@gurney.reilly.home> References: <12411.956006235@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <12411.956006235@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Apr 17, 2000 at 11:17:15PM +0200, Poul-Henning Kamp wrote: > Once per day the machine cvsups, checks out a virgin source tree, > tries to build GENERIC, GENERIC98, LINT and world. If any of these > builds fail it will send a report like this. > > On Sundays the report will always be sent. Are any of these warnings of the "helpful gcc" type, rather than actual dangers? It would be a shame if this resulted in obfuscation of the code base _just_ to shut gcc up. Of course if gcc is well-behaved on this point, and the warning flags are well sorted and agreed-upon, then there isn't a problem. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 17:11:29 2000 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 776BE37B71F for ; Mon, 17 Apr 2000 17:11:25 -0700 (PDT) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (trang.cdrom.com [204.216.28.153]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA91773; Mon, 17 Apr 2000 17:11:21 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA01269; Mon, 17 Apr 2000 17:10:50 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Apr 2000 17:10:50 -0700 From: "David O'Brien" To: Patrick Bihan-Faou Cc: freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD Build status Message-ID: <20000417171049.A1207@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <12411.956006235@critter.freebsd.dk> <01a501bfa8b7$19f2fe60$040aa8c0@local.mindstep.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <01a501bfa8b7$19f2fe60$040aa8c0@local.mindstep.com>; from patrick@mindstep.com on Mon, Apr 17, 2000 at 05:51:35PM -0400 X-Operating-System: FreeBSD 5.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 Mon, Apr 17, 2000 at 05:51:35PM -0400, Patrick Bihan-Faou wrote: > I have a patch against these warnings. They are the result of a function > being called with a pointer to a function rather than a string... ...snip... > Should I just send a PR ? You should send a PR to the GCC developers, not us for this. -- -- 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 Mon Apr 17 18:41:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 6AB8A37B74F for ; Mon, 17 Apr 2000 18:41:32 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:t+YlSUFv2Trgu6UFQLK5xcafs9EI6NFp@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id KAA08007; Tue, 18 Apr 2000 10:41:22 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id KAA12341; Tue, 18 Apr 2000 10:47:56 +0900 (JST) Message-Id: <200004180147.KAA12341@zodiac.mech.utsunomiya-u.ac.jp> To: Samuel Tardieu Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: middle mouse button emulation broken in 4.0-STABLE? In-reply-to: Your message of "17 Apr 2000 17:22:59 +0200." <2000-04-17-17-23-00+trackit+sam@antinea.enst.fr> References: <2000-04-17-17-23-00+trackit+sam@antinea.enst.fr> Date: Tue, 18 Apr 2000 10:47:56 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >This has been fixed in both -STABLE and -CURRENT a week ago. The left >button is working, the timeout is just to long. Read moused manpage >and set the timeout to 200ms as a workaround (this is the default >according to the manpage, but not according to the code in >4.0-RELEASE). > > Sam 200 msec may be still too long. Maybe we had better change the default value to 100 msec or so... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 19:44: 2 2000 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 10C0337B9AB for ; Mon, 17 Apr 2000 19:43:58 -0700 (PDT) (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 WAA46529; Mon, 17 Apr 2000 22:43:22 -0400 (EDT) (envelope-from sjr@cc158233-a.catv1.md.home.com) Message-Id: <200004180243.WAA46529@cc158233-a.catv1.md.home.com> Date: Mon, 17 Apr 2000 22:43:20 -0400 (EDT) From: "Stephen J. Roznowski" Subject: Re: cvsup crash To: nordwick@scam.xcf.berkeley.edu Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <20000417221410.90801.qmail@scam.xcf.berkeley.edu> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Apr, Jason wrote: > I didn't know here to send this, but I thought that other people trying > to keep current might have had this problem before: > > When I run cvsup with the default cvsup file from > /usr/share/examples/cvsup/cvs-supfile (after putting in the correct cvsup > server address) it crashes: > > bash-2.03# cvsup cvs-supfile > > > *** > *** runtime error: > *** Segmentation violation - possible attempt to dereference NIL > *** pc = 0x81f0708 = Cat + 0x18 in /b/jdp/pm3/pm3/libs/m3core/src/text/Text.m3 > *** > > use option @M3stackdump to get a stack trace > Abort trap (core dumped) This look familiar... Last time I got something like this, reinstalling the modula ports (perhaps just modula-3-lib) and recompiling cvsup fixed the problem. -SR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 19:48:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from fuggle.veldy.net (veldy-host201.dsl.visi.com [208.42.48.201]) by hub.freebsd.org (Postfix) with ESMTP id 0E76737B804 for ; Mon, 17 Apr 2000 19:48:21 -0700 (PDT) (envelope-from veldy@veldy.net) Received: by fuggle.veldy.net (Postfix, from userid 1000) id 4E7413D34; Mon, 17 Apr 2000 21:50:24 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by fuggle.veldy.net (Postfix) with ESMTP id 4A3915BBB; Mon, 17 Apr 2000 21:50:24 -0500 (CDT) Date: Mon, 17 Apr 2000 21:50:24 -0500 (CDT) From: "Thomas T. Veldhouse" To: "Stephen J. Roznowski" Cc: nordwick@scam.xcf.berkeley.edu, freebsd-current@FreeBSD.ORG Subject: Re: cvsup crash In-Reply-To: <200004180243.WAA46529@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 This happened to me when I was using cvsup-bin. I didn't want all of the modula overhead. Any ideas? Tom Veldhouse veldy@veldy.net On Mon, 17 Apr 2000, Stephen J. Roznowski wrote: > On 17 Apr, Jason wrote: > > I didn't know here to send this, but I thought that other people trying > > to keep current might have had this problem before: > > > > When I run cvsup with the default cvsup file from > > /usr/share/examples/cvsup/cvs-supfile (after putting in the correct cvsup > > server address) it crashes: > > > > bash-2.03# cvsup cvs-supfile > > > > > > *** > > *** runtime error: > > *** Segmentation violation - possible attempt to dereference NIL > > *** pc = 0x81f0708 = Cat + 0x18 in /b/jdp/pm3/pm3/libs/m3core/src/text/Text.m3 > > *** > > > > use option @M3stackdump to get a stack trace > > Abort trap (core dumped) > > This look familiar... Last time I got something like this, reinstalling > the modula ports (perhaps just modula-3-lib) and recompiling cvsup fixed > the problem. > > -SR > > > > 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 Apr 17 20:25:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.originative.co.uk (mailgate.originative.co.uk [194.217.50.228]) by hub.freebsd.org (Postfix) with ESMTP id BA28837BB3A for ; Mon, 17 Apr 2000 20:25:22 -0700 (PDT) (envelope-from paul@originative.co.uk) Received: from originative.co.uk (lobster.originative.co.uk [194.217.50.241]) by mailgate.originative.co.uk (Postfix) with ESMTP id D7FA01D15F; Tue, 18 Apr 2000 04:25:19 +0100 (BST) Message-ID: <38FBD59F.61B9DA95@originative.co.uk> Date: Tue, 18 Apr 2000 04:25:19 +0100 From: Paul Richards Organization: Originative Solutions Ltd X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en-GB, en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: FreeBSD Build status References: <2440.956009328@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > But does this also check the kernels ? It was my understanding that > > it only did world/release ? > > It only does the world/release (and it's the chrooted make release > "world build" which is reported on, not the host system's BTW) but > could easily add a kernel build just for the benefit of the > mailing list folks. It would be trivial to add. > > > As for the lists being tedious and long: I've sorted the content by > > relevance, and it was my hope that over time they would shrink to > > zero if we annoyed people enough with them. > > I think that's too much annoyance, really. I can see most people > simply unsubscribing from -current in the face of a mail that long and > tedious (and daily) and -current was never created as a place for > daemons to talk to people in any case, it was created as a discussion > forum. Let's do this, by all means, but let's plase do it elsewhere. > Anyone who starts sending daily automated anythings to any of our "top > level" mailing lists will classify themselves as a spammer on my and > many other people's radar. Not sure I agree with the annoyance issue. It's already got a few people thinking about some of the issues so I think it's useful. If we lose some readers of -current because a report of development problems is too much for them then they probably shouldn't be -current subscribers in the first place. Hackers is supposed to be the mailing list for people generally interested in hacking on FreeBSD, current *should* be for people who want to see long tedious reports on the problems in the current branch. Also, the length of the report should fall dramatically as the problems are addressed and a sudden long report will immediately focus developers attention to the cause. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 20:46:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 2E88537BB62 for ; Mon, 17 Apr 2000 20:46:06 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 25325 invoked from network); 18 Apr 2000 03:46:01 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 18 Apr 2000 03:46:01 -0000 Date: Tue, 18 Apr 2000 13:45:57 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Patrick Bihan-Faou Cc: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-Reply-To: <01a501bfa8b7$19f2fe60$040aa8c0@local.mindstep.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Apr 2000, Patrick Bihan-Faou wrote: > The patch: > > --- c-common.c.orig Mon Nov 1 13:41:09 1999 > +++ c-common.c Sat Apr 8 06:32:52 2000 > @@ -1652,7 +1652,7 @@ > /* There should be an int arg to control the string arg. */ > if (params == 0) > { > - warning (tfaff); > + tfaff (); > return; > } > if (info->first_arg_num != 0) > @@ -1675,7 +1675,7 @@ > /* There should be an unsigned char * arg before the string arg. */ > if (params == 0) > { > - warning (tfaff); > + tfaff (); > return; > } > if (info->first_arg_num != 0) > > Should I just send a PR ? No, there is already a PR for this (15549). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 21:14:41 2000 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 7EF1D37BB0D for ; Mon, 17 Apr 2000 21:14:38 -0700 (PDT) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (trang.cdrom.com [204.216.28.153]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id VAA92632; Mon, 17 Apr 2000 21:14:24 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id VAA04845; Mon, 17 Apr 2000 21:13:54 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Apr 2000 21:13:54 -0700 From: "David O'Brien" To: Bruce Evans Cc: Patrick Bihan-Faou , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: FreeBSD Build status Message-ID: <20000417211354.A4378@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <01a501bfa8b7$19f2fe60$040aa8c0@local.mindstep.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bde@zeta.org.au on Tue, Apr 18, 2000 at 01:45:57PM +1000 X-Operating-System: FreeBSD 5.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 Tue, Apr 18, 2000 at 01:45:57PM +1000, Bruce Evans wrote: > > Should I just send a PR ? > No, there is already a PR for this (15549). Doh! The problem is in our code, not the FSF code. Fixed. -- -- 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 Mon Apr 17 21:31:58 2000 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 893A937BC3F for ; Mon, 17 Apr 2000 21:31:53 -0700 (PDT) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (trang.cdrom.com [204.216.28.153]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id VAA92742 for ; Mon, 17 Apr 2000 21:31:52 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id VAA05134 for freebsd-current@freebsd.org; Mon, 17 Apr 2000 21:31:21 -0700 (PDT) (envelope-from obrien) Date: Mon, 17 Apr 2000 21:31:21 -0700 From: "David O'Brien" To: freebsd-current@freebsd.org Subject: ** HEADS UP ** ELF Branding changes require action on your part. Message-ID: <20000417213121.A5099@dragon.nuxi.com> Reply-To: obrien@NUXI.ucdavis.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 5.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 ----- Forwarded message from "David E. O'Brien" ----- Log: Change our ELF binary branding to something more acceptable to the Binutils maintainers. ... Note that a new kernel can still properly load old binaries except for Linux static binaries branded in our old method. ----- End forwarded message ----- One statically linked Linux binary that will cause you trouble after you build world is the Linux ``ldconfig''. After your ``make world'' and before you reboot that new kernel, issue: brandelf -t Linux /compat/linux/sbin/ldconfig -- -- 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 Mon Apr 17 21:41: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by hub.freebsd.org (Postfix) with ESMTP id A898D37BC86 for ; Mon, 17 Apr 2000 21:40:54 -0700 (PDT) (envelope-from csg@dustdevil.waterspout.com) Received: (from csg@localhost) by dustdevil.waterspout.com (8.9.3/8.9.3) id XAA01048; Mon, 17 Apr 2000 23:48:02 -0500 (EST) (envelope-from csg) Date: Mon, 17 Apr 2000 23:48:01 -0500 From: "C. Stephen Gunn" To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c Message-ID: <20000417234801.A979@waterspout.com> References: <38EE011D.B81BA63C@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38EE011D.B81BA63C@cvzoom.net>; from dmmiller@cvzoom.net on Fri, Apr 07, 2000 at 11:39:09AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 07, 2000 at 11:39:09AM -0400, Donn Miller wrote: > /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! I was discussing this issue with Robert Watson the other day on IRC. The issue is more complicated than just removing the notification in sys/netinet/if_ether.c. It's a fundamental problem with the way in_arpinput() seems to process packets, and checking the receive interface versus several interefaces that may or may-not have IPV4 addresses. If I remember Robert's remark in particular, it was related to ARP processing on IPV6 only interfaces that might be plugged into the same wire as IPV4 interfaces on the same machine. This physical configuration yields "host is on but received arp on " errors to be logged as well. Robert's suggestion, that I started researching, was to not perform ARP processing on interfaces that don't have IPV4 addresses assigned. This soultion should also address the problems for logging 0.0.0.0 addresses. If anybody is seriously interested, I'll bump the priority on generating a diff, and posting it here. - Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 22: 3:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id E85B237B691 for ; Mon, 17 Apr 2000 22:03:28 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id WAA01879; Mon, 17 Apr 2000 22:03:25 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200004180503.WAA01879@troutmask.apl.washington.edu> Subject: Re: ** HEADS UP ** ELF Branding changes require action on your part. In-Reply-To: <20000417213121.A5099@dragon.nuxi.com> from "David O'Brien" at "Apr 17, 2000 09:31:21 pm" To: obrien@NUXI.ucdavis.edu Date: Mon, 17 Apr 2000 22:03:25 -0700 (PDT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (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 David O'Brien wrote: > ----- Forwarded message from "David E. O'Brien" ----- > Log: > Change our ELF binary branding to something more acceptable to the Binutils > maintainers. > ... > Note that a new kernel can still properly load old binaries except for > Linux static binaries branded in our old method. > ----- End forwarded message ----- > > One statically linked Linux binary that will cause you trouble after you > build world is the Linux ``ldconfig''. After your ``make world'' and > before you reboot that new kernel, issue: > > brandelf -t Linux /compat/linux/sbin/ldconfig > Does this mean that we can re-brand any statically linux binary if it fails? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 22:25:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 80DF937B64F for ; Mon, 17 Apr 2000 22:25:16 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115213>; Tue, 18 Apr 2000 15:25:37 +1000 Content-return: prohibited From: Peter Jeremy Subject: Re: FreeBSD Build status In-reply-to: <2440.956009328@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Tue, Apr 18, 2000 at 08:07:45AM +1000 To: "Jordan K. Hubbard" Cc: Poul-Henning Kamp , current@FreeBSD.ORG Message-Id: <00Apr18.152537est.115213@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <12605.956008724@critter.freebsd.dk> <2440.956009328@zippy.cdrom.com> Date: Tue, 18 Apr 2000 15:25:35 +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Apr-18 08:07:45 +1000, "Jordan K. Hubbard" wrote: >> As for the lists being tedious and long: I've sorted the content by >> relevance, and it was my hope that over time they would shrink to >> zero if we annoyed people enough with them. > >I think that's too much annoyance, really. I can see most people >simply unsubscribing from -current in the face of a mail that long and >tedious IMHO, it's not such a bad idea. freebsd-current _is_ the place to report problems with -current, why can't the report be produced by a daemon? All the MUA's I've ever used allowed me to delete a mail before reading all of it, so I don't see that having detailed information (at the end) is a real issue (though it might be for someove paying by the byte). Comments: - I hope it has a well-defined subject so it can be easily recognized. - I presume it's built using the default make.conf. - It would be nice if it reported changes since the previous day (or successful build). This would make it easier to see what has been broken recently. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 22:37: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id E806037BA61 for ; Mon, 17 Apr 2000 22:37:00 -0700 (PDT) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id HAA29563; Tue, 18 Apr 2000 07:37:24 +0200 (MET DST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 12hQgz-0008SZ-00 for ; Tue, 18 Apr 2000 07:36:57 +0200 Date: Tue, 18 Apr 2000 07:36:57 +0200 From: Szilveszter Adam To: current@FreeBSD.ORG Subject: Re: FreeBSD Build status Message-ID: <20000418073657.A32400@petra.hos.u-szeged.hu> Mail-Followup-To: current@FreeBSD.ORG References: <12605.956008724@critter.freebsd.dk> <2440.956009328@zippy.cdrom.com> <00Apr18.152537est.115213@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: <00Apr18.152537est.115213@border.alcanet.com.au>; from peter.jeremy@alcatel.com.au on Tue, Apr 18, 2000 at 03:25:35PM +1000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 18, 2000 at 03:25:35PM +1000, Peter Jeremy wrote: > On 2000-Apr-18 08:07:45 +1000, "Jordan K. Hubbard" wrote: > >> As for the lists being tedious and long: I've sorted the content by > >> relevance, and it was my hope that over time they would shrink to > >> zero if we annoyed people enough with them. > > > >I think that's too much annoyance, really. I can see most people > >simply unsubscribing from -current in the face of a mail that long and > >tedious > > IMHO, it's not such a bad idea. freebsd-current _is_ the place to > report problems with -current, why can't the report be produced by a > daemon? All the MUA's I've ever used allowed me to delete a mail > before reading all of it, so I don't see that having detailed > information (at the end) is a real issue (though it might be for > someove paying by the byte). Sorry that I just chime in, but wouldn't it be more appropriate to go for a system similar to the one at mozilla.org? They do pretty much the same things that have been discussed here, but it looks so cooool... and does not bother people on normal mailing lists. They have tinderbox.mozilla.org, which always inidcates current build status on a number of machines (and OS-es) the log is available too. And it is integrated with the CVS system so you can see at once what commits have been made since the last build attempt, etc. Maybe we could adapt this system to our needs? (they do not bother about warnings, for example.) Just my thoughts... Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 23:19:28 2000 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 9343537B688 for ; Mon, 17 Apr 2000 23:19:24 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA14052; Tue, 18 Apr 2000 08:19:04 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: nate@yogotech.com (Nate Williams), current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Mon, 17 Apr 2000 16:47:15 MDT." <200004172247.QAA85536@harmony.village.org> Date: Tue, 18 Apr 2000 08:19:04 +0200 Message-ID: <14050.956038744@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004172247.QAA85536@harmony.village.org>, Warner Losh writes: >It isn't something specific to Poul's system. I've recreated it here >as well. I've also tracked it down to the -fno-builtin that is in >LINT, but not in GENERIC. Now, to think about what to do about it... It is to be left there to catch people who use functions which are not in the kernel, but which gcc implements as built-ins :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 23:19:57 2000 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 6E18E37B64F for ; Mon, 17 Apr 2000 23:19:53 -0700 (PDT) (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 XAA03959; Mon, 17 Apr 2000 23:21:24 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Peter Jeremy Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Tue, 18 Apr 2000 15:25:35 +1000." <00Apr18.152537est.115213@border.alcanet.com.au> Date: Mon, 17 Apr 2000 23:21:24 -0700 Message-ID: <3956.956038884@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > IMHO, it's not such a bad idea. freebsd-current _is_ the place to > report problems with -current, why can't the report be produced by a > daemon? Becuase it's chunky and regular enough that I don't see why we also can't just create a new notification service for it. Think a bit bigger-picture also; theoretically, we should have these reports for -current and the RELENG_3 and RELENG_4 branches. The machine-resources are available for it, we just haven't organized it properly. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 23:26:33 2000 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 EAE7837B8D7 for ; Mon, 17 Apr 2000 23:26:25 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA14261; Tue, 18 Apr 2000 08:26:01 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Jeremy Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Tue, 18 Apr 2000 15:25:35 +1000." <00Apr18.152537est.115213@border.alcanet.com.au> Date: Tue, 18 Apr 2000 08:26:01 +0200 Message-ID: <14259.956039161@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00Apr18.152537est.115213@border.alcanet.com.au>, Peter Jeremy write s: >IMHO, it's not such a bad idea. freebsd-current _is_ the place to >report problems with -current, why can't the report be produced by a >daemon? All the MUA's I've ever used allowed me to delete a mail >before reading all of it, so I don't see that having detailed >information (at the end) is a real issue (though it might be for >someove paying by the byte). I agree. >Comments: >- I hope it has a well-defined subject so it can be easily recognized. "FreeBSD Build status" >- I presume it's built using the default make.conf. Yes. >- It would be nice if it reported changes since the previous day (or > successful build). This would make it easier to see what has been > broken recently. Well, it reports on sundays and if anything doesn't build. If it reports, it includes the errors which from the non-building components and "New warnings in *" delta lists relative to the previous report. I've sorted the report so that the most interesting things are at the top. Other ideas welcome. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 23:39:14 2000 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 B864F37BC0D for ; Mon, 17 Apr 2000 23:39:08 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id IAA14396; Tue, 18 Apr 2000 08:38:47 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: Peter Jeremy , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Mon, 17 Apr 2000 23:21:24 PDT." <3956.956038884@zippy.cdrom.com> Date: Tue, 18 Apr 2000 08:38:47 +0200 Message-ID: <14394.956039927@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3956.956038884@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> IMHO, it's not such a bad idea. freebsd-current _is_ the place to >> report problems with -current, why can't the report be produced by a >> daemon? > >Becuase it's chunky and regular enough that I don't see why we >also can't just create a new notification service for it. Because the people who don't compile LINT are unlikely to subscribe to it. The alternative is to send it to committers, but I pressume all the ports people would be pretty annoyed, and by sending it to -current maybe a new junior hacker or two could be ferret out :-) >Think a bit bigger-picture also; theoretically, we should have these >reports for -current and the RELENG_3 and RELENG_4 branches. The >machine-resources are available for it, we just haven't organized >it properly. That makes sense. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Apr 17 23:56:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id B578E37BB22 for ; Mon, 17 Apr 2000 23:56:19 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA24942; Tue, 18 Apr 2000 02:55:41 -0400 Date: Tue, 18 Apr 2000 02:55:41 -0400 (EDT) From: Mike Nowlin To: Poul-Henning Kamp Cc: Peter Jeremy , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-Reply-To: <14259.956039161@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Comments: > >- I hope it has a well-defined subject so it can be easily recognized. > > "FreeBSD Build status" Procmail is your friend... A lot of the list message I receive get bounced to a lower-priority-that-I-have-to-read-these folder, but anything with "HEADS-UP"(?) gets sent to my primary folder. My vote is that this is A Good Idea. mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 0: 1:19 2000 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 4171537B64F for ; Tue, 18 Apr 2000 00:01:15 -0700 (PDT) (envelope-from obrien@NUXI.ucdavis.edu) Received: from dragon.nuxi.com (root@18-075.006.popsite.net [216.126.138.75]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA93207; Tue, 18 Apr 2000 00:01:12 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA01171; Tue, 18 Apr 2000 00:01:10 -0700 (PDT) (envelope-from obrien) Date: Tue, 18 Apr 2000 00:01:09 -0700 From: "David O'Brien" To: Steve Kargl Cc: freebsd-current@FreeBSD.ORG Subject: Re: ** HEADS UP ** ELF Branding changes require action on your part. Message-ID: <20000418000109.A1150@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000417213121.A5099@dragon.nuxi.com> <200004180503.WAA01879@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004180503.WAA01879@troutmask.apl.washington.edu>; from sgk@troutmask.apl.washington.edu on Mon, Apr 17, 2000 at 10:03:25PM -0700 X-Operating-System: FreeBSD 5.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 Mon, Apr 17, 2000 at 10:03:25PM -0700, Steve Kargl wrote: > > brandelf -t Linux /compat/linux/sbin/ldconfig .... > Does this mean that we can re-brand any statically > linux binary if it fails? Yes. Just like the above. -- -- 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 Apr 18 0:13:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 0FE8837BB58 for ; Tue, 18 Apr 2000 00:13:02 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id JAA30527; Tue, 18 Apr 2000 09:12:28 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Tue, 18 Apr 2000 09:12:27 +0200 (EET) From: Narvi To: Peter Jeremy Cc: "Jordan K. Hubbard" , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-Reply-To: <00Apr18.152537est.115213@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 Tue, 18 Apr 2000, Peter Jeremy wrote: > On 2000-Apr-18 08:07:45 +1000, "Jordan K. Hubbard" wrote: > >> As for the lists being tedious and long: I've sorted the content by > >> relevance, and it was my hope that over time they would shrink to > >> zero if we annoyed people enough with them. > > > >I think that's too much annoyance, really. I can see most people > >simply unsubscribing from -current in the face of a mail that long and > >tedious > > IMHO, it's not such a bad idea. freebsd-current _is_ the place to > report problems with -current, why can't the report be produced by a > daemon? All the MUA's I've ever used allowed me to delete a mail > before reading all of it, so I don't see that having detailed > information (at the end) is a real issue (though it might be for > someove paying by the byte). > It *IS* a bad idea. Consider how big the failure report can be. Why not instead: 1) have the report automatically uploaded on web 2) have the summary of summaries be sent to -current The summary of summaries would roughly look like this: Subject: -current build report Success: world, generic Fail: lint For details, see http://blah.foo.bar/FreeBSD-build/date It conveys the information most needed, and can hardly hurt anybody's mailbox. > > Peter > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 0:14:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 5C6F237B64F for ; Tue, 18 Apr 2000 00:14:12 -0700 (PDT) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12hSCS-000LVk-00; Tue, 18 Apr 2000 14:13:32 +0700 Date: Tue, 18 Apr 2000 14:13:31 +0700 (ALMST) From: Boris Popov To: Poul-Henning Kamp Cc: Peter Jeremy , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-Reply-To: <14259.956039161@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Apr 2000, Poul-Henning Kamp wrote: > In message <00Apr18.152537est.115213@border.alcanet.com.au>, Peter Jeremy write > s: > > >IMHO, it's not such a bad idea. freebsd-current _is_ the place to > >report problems with -current, why can't the report be produced by a > >daemon? All the MUA's I've ever used allowed me to delete a mail > >before reading all of it, so I don't see that having detailed > >information (at the end) is a real issue (though it might be for > >someove paying by the byte). > > I agree. As one of those who pays for an incoming traffic I'm prefer a short letter with a list of directories where warning/errors happens and an URL with full listing. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 0:17:18 2000 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 E53CD37B688 for ; Tue, 18 Apr 2000 00:17:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA14710; Tue, 18 Apr 2000 09:16:51 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Narvi Cc: Peter Jeremy , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Tue, 18 Apr 2000 09:12:27 +0200." Date: Tue, 18 Apr 2000 09:16:51 +0200 Message-ID: <14705.956042211@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Nar vi writes: >The summary of summaries would roughly look like this: > > Subject: -current build report > > Success: world, generic > Fail: lint The First part of the email is a summary just like that. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 0:45:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 1C28A37BA4D for ; Tue, 18 Apr 2000 00:45:17 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id JAA35065; Tue, 18 Apr 2000 09:44:33 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Tue, 18 Apr 2000 09:44:32 +0200 (EET) From: Narvi To: Poul-Henning Kamp Cc: Peter Jeremy , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-Reply-To: <14705.956042211@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 18 Apr 2000, Poul-Henning Kamp wrote: > In message , Nar > vi writes: > > >The summary of summaries would roughly look like this: > > > > Subject: -current build report > > > > Success: world, generic > > Fail: lint > > The First part of the email is a summary just like that. > See what Boris Popov writes on the issue. I am sure there are more people who think that a big status report is not cost effective, if they can get a *short* summary, and an url where they can get the full report. > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD coreteam member | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 0:48:35 2000 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 E32C637BA34 for ; Tue, 18 Apr 2000 00:48:30 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA14872; Tue, 18 Apr 2000 09:48:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Narvi Cc: Peter Jeremy , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: FreeBSD Build status In-reply-to: Your message of "Tue, 18 Apr 2000 09:44:32 +0200." Date: Tue, 18 Apr 2000 09:48:11 +0200 Message-ID: <14870.956044091@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Nar vi writes: >> >The summary of summaries would roughly look like this: >> > >> > Subject: -current build report >> > >> > Success: world, generic >> > Fail: lint >> >> The First part of the email is a summary just like that. >> > >See what Boris Popov writes on the issue. I am sure there are more people >who think that a big status report is not cost effective, if they can get >a *short* summary, and an url where they can get the full report. Listen, we are talking about an email which is shorter than the list of open PRs, and if people actually *DO* something about it it will get shorter fast The only reason it is a long report right now is that people are sloppy! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 2:33:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mmu.edu.my (ext-dns.mmu.edu.my [203.106.62.11]) by hub.freebsd.org (Postfix) with ESMTP id CA05A37B64F for ; Tue, 18 Apr 2000 02:33:18 -0700 (PDT) (envelope-from s9810710@mmu.edu.my) Received: from venus.cyber.mmu.edu.my (venus.cyber.mmu.edu.my [203.106.62.12]) by mmu.edu.my (8.9.1b+Sun/8.9.1) with ESMTP id RAA28987 for ; Tue, 18 Apr 2000 17:15:37 +0800 (MYT) Received: from adina ([10.100.94.192]) by venus.cyber.mmu.edu.my (8.8.8+Sun/8.8.8) with SMTP id RAA22610 for ; Tue, 18 Apr 2000 17:26:51 +0800 (SGT) Message-ID: <000501bfa918$6bf52380$c05e640a@cyber.mmu.edu.my> From: "ADiNA" To: Date: Tue, 18 Apr 2000 17:28:12 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 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 subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 3:31: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E522A37B614; Tue, 18 Apr 2000 03:30:53 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA68166; Tue, 18 Apr 2000 12:30:51 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200004181030.MAA68166@freebsd.dk> Subject: HEADSUP! linprocfs going away in 72 hours. To: current@freebsd.org, des@freebsd.org Date: Tue, 18 Apr 2000 12:30:51 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL54 (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 Some time ago -core requested that linprocfs should move into the linuxulator. Nothing has happend on that account, so -core is now forced to take action. This is the announcement that linprocfs will be removed from the -current tree in 72 hours, giving the involved parties a final deadline for getting this done the way it was decided by -core. The linprocfs bits has already been removed from the RELENG_4 branch since it should never have entered there. The FreeBSD Core Team To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 3:53:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id EF65C37B93C for ; Tue, 18 Apr 2000 03:53:08 -0700 (PDT) (envelope-from julian@elischer.org) Received: from popserver-02.iinet.net.au (popserver-02.iinet.net.au [203.59.24.148]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id SAA14174; Tue, 18 Apr 2000 18:53:04 +0800 Received: from jules.elischer.org (reggae-11-34.nv.iinet.net.au [203.59.69.34]) by popserver-02.iinet.net.au (8.9.3/8.9.3) with SMTP id SAA08357; Tue, 18 Apr 2000 18:52:59 +0800 Message-ID: <38FC3E40.446B9B3D@elischer.org> Date: Tue, 18 Apr 2000 03:51:44 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Soren Schmidt Cc: current@freebsd.org Subject: Re: HEADSUP! linprocfs going away in 72 hours. References: <200004181030.MAA68166@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I presume this means that it should remain part of the standard system but that the source should be moved to /sys/i386/linux? as long as it remains part of the system I don't care where it lives.. It's too massively important to totally drop. Having it as a port was a losing proposition. Julian Soren Schmidt wrote: > > Some time ago -core requested that linprocfs should move into the linuxulator. > > Nothing has happend on that account, so -core is now forced to take action. > > This is the announcement that linprocfs will be removed from the -current > tree in 72 hours, giving the involved parties a final deadline for getting > this done the way it was decided by -core. > > The linprocfs bits has already been removed from the RELENG_4 branch since > it should never have entered there. > > The FreeBSD Core Team > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 5:36: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id 40ABF37B5FC for ; Tue, 18 Apr 2000 05:35:47 -0700 (PDT) (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 A24141CD7; Tue, 18 Apr 2000 05:35:37 -0700 (PDT) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Julian Elischer Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: HEADSUP! linprocfs going away in 72 hours. In-Reply-To: Message from Julian Elischer of "Tue, 18 Apr 2000 03:51:44 PDT." <38FC3E40.446B9B3D@elischer.org> Date: Tue, 18 Apr 2000 05:35:37 -0700 From: Peter Wemm Message-Id: <20000418123537.A24141CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > I presume this means that it should remain part of the standard system > but that the source should be moved to /sys/i386/linux? > > as long as it remains part of the system I don't care where it lives.. > It's too massively important to totally drop. Having it as a port was > a losing proposition. The biggest problem is that it re-opens a security hole that was explicitly patched in procfs. Also, the way I see it, the linux procfs should probably only be visible to linux sysvec processes... It would be a damn shame to let /compat/linux/procfs "sneak in" to the expected system requirements for bsd programs so that developers can use the easy way out rather than doing something properly. > Julian 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 Apr 18 5:43: 2 2000 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 58E8737B83F for ; Tue, 18 Apr 2000 05:42:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id OAA15890; Tue, 18 Apr 2000 14:42:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Julian Elischer , Soren Schmidt , current@FreeBSD.ORG Subject: Re: HEADSUP! linprocfs going away in 72 hours. In-reply-to: Your message of "Tue, 18 Apr 2000 05:35:37 PDT." <20000418123537.A24141CD7@overcee.netplex.com.au> Date: Tue, 18 Apr 2000 14:42:19 +0200 Message-ID: <15888.956061739@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000418123537.A24141CD7@overcee.netplex.com.au>, Peter Wemm writes : >Julian Elischer wrote: >> I presume this means that it should remain part of the standard system >> but that the source should be moved to /sys/i386/linux? >> >> as long as it remains part of the system I don't care where it lives.. >> It's too massively important to totally drop. Having it as a port was >> a losing proposition. > >The biggest problem is that it re-opens a security hole that was explicitly >patched in procfs. > >Also, the way I see it, the linux procfs should probably only be visible to >linux sysvec processes... It would be a damn shame to let >/compat/linux/procfs "sneak in" to the expected system requirements for bsd >programs so that developers can use the easy way out rather than doing >something properly. Fully agreement here, and that was also what the core decision said: only visible to processed run under the linuxolator. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 6:22: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id ABE8C37B59F; Tue, 18 Apr 2000 06:22:00 -0700 (PDT) Date: Tue, 18 Apr 2000 06:22:00 -0700 From: "Andrey A. Chernov" To: current@freebsd.org Subject: event.h troubles Message-ID: <20000418062200.A85325@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now I got lost of /usr/include/sys/event.h:159: warning: `struct timespec' declared inside parameter list. because include it. Please fix somehow. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 7: 4:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id A131237B86F; Tue, 18 Apr 2000 07:04:08 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id JAA84381; Tue, 18 Apr 2000 09:07:44 -0500 (CDT) (envelope-from jlemon) Date: Tue, 18 Apr 2000 09:07:44 -0500 (CDT) From: Jonathan Lemon Message-Id: <200004181407.JAA84381@prism.flugsvamp.com> To: ache@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: event.h troubles X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Now I got lost of > >/usr/include/sys/event.h:159: warning: `struct timespec' declared inside >parameter list. > >because include it. >Please fix somehow. I'm looking at this now. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 7:21: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 882E837B565 for ; Tue, 18 Apr 2000 07:20:58 -0700 (PDT) (envelope-from julian@elischer.org) Received: from gothic.iinet.net.au (gothic.iinet.net.au [203.59.24.252]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id WAA32059; Tue, 18 Apr 2000 22:20:55 +0800 Received: from jules.elischer.org (reggae-11-45.nv.iinet.net.au [203.59.69.45]) by gothic.iinet.net.au (8.8.5/8.8.5) with SMTP id WAA16915; Tue, 18 Apr 2000 22:20:48 +0800 Message-ID: <38FC6EF4.1CFBAE39@elischer.org> Date: Tue, 18 Apr 2000 07:19:32 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Peter Wemm Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: HEADSUP! linprocfs going away in 72 hours. References: <20000418123537.A24141CD7@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: > > > The biggest problem is that it re-opens a security hole that > was explicitly patched in procfs. then look at the hole, don't remove it. That's throwing the baby out with the bathwater.. It's a godsend when trying to run Linux binaries. > > Also, the way I see it, the linux procfs should probably only be > visible to linux sysvec processes... I think that you're overly compilcating things for the sake of an aesthetic argument. > It would be a damn shame to let > /compat/linux/procfs "sneak in" to the expected system > requirements for bsd > programs so that developers can use the easy way out rather than doing > something properly. That's extremely unlikely as most systems wouldn't have it.. Since I need it, I thought all my christmasses had come at once when I found it in the system as standard! The old port was cumbersom, always got out of date, and was not automatically updated when you rebuilt everything leading to lots of hours wasted looking for the reason for crashes. I can see moving it out to where the rest of the linux emulation code is but to remove it entirely seems the typical viking axe bloody-minded behaviour that's getting too familiar. > > > Julian > > Cheers, > -Peter -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 7:37:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from longneck.netc.pt (longneck.netc.pt [212.18.160.140]) by hub.freebsd.org (Postfix) with ESMTP id C008537B9DB for ; Tue, 18 Apr 2000 07:37:37 -0700 (PDT) (envelope-from jpedras@webvolution.net) Received: from manecao.tafkap.priv (p059-17.netc.pt) by longneck.netc.pt (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FT7007MLU938Q@longneck.netc.pt>; Tue, 18 Apr 2000 15:15:07 +0100 (WET DST) Date: Tue, 18 Apr 2000 15:15:16 +0100 (BST) From: Joao Pedras Subject: RE: Parallel make world broken In-reply-to: To: Donn Miller Cc: current@FreeBSD.ORG Message-id: MIME-version: 1.0 X-Mailer: XFMail 1.3.1 [p0] on FreeBSD Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 8bit X-Priority: 3 (Normal) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG here too Donn Miller wrote: > ===> librsausa > mkdir: openssl: File exists > cp /usr/src/secure/lib/librsausa/../libcrypto/opensslconf-i386.h > openssl/openssl > conf.h > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > > - Donn > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ^\ /^ O O ----------------------------------------o00-(_)-00o-------------------------- Texas law forbids anyone to have a pair of pliers in his possession. ----------------------------------------------------------------------------- PGP key available upon request or may be cut at http://pedras.webvolution.net/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 7:52: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id 50EB637B68D for ; Tue, 18 Apr 2000 07:52:04 -0700 (PDT) (envelope-from julian@elischer.org) Received: from popserver-02.iinet.net.au (popserver-02.iinet.net.au [203.59.24.148]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id WAA05672; Tue, 18 Apr 2000 22:52:00 +0800 Received: from jules.elischer.org (reggae-11-45.nv.iinet.net.au [203.59.69.45]) by popserver-02.iinet.net.au (8.9.3/8.9.3) with SMTP id WAA10675; Tue, 18 Apr 2000 22:51:57 +0800 Message-ID: <38FC762C.FF6D5DF@elischer.org> Date: Tue, 18 Apr 2000 07:50:45 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: HEADSUP! linprocfs going away in 72 hours. References: <15888.956061739@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > Fully agreement here, and that was also what the core decision said: > only visible to processed run under the linuxolator. This sounds like a very poor decision to me.. It doesn't help the security issue at all and it makes it more difficult to find out what is going on and debug problems. This sounds more like a personal NIH problem than a technical decision. A case of someone's bruised ego or something. > __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 8:18:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from happy.checkpoint.com (happy.checkpoint.com [199.203.156.41]) by hub.freebsd.org (Postfix) with ESMTP id 31D2F37B9A3 for ; Tue, 18 Apr 2000 08:18:25 -0700 (PDT) (envelope-from mellon@pobox.com) Received: (from mellon@localhost) by happy.checkpoint.com (8.9.3/8.9.3) id SAA54096; Tue, 18 Apr 2000 18:17:27 GMT (envelope-from mellon@pobox.com) Date: Tue, 18 Apr 2000 18:17:27 +0000 From: Anatoly Vorobey To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: FreeBSD Build status Message-ID: <20000418181726.A54017@happy.checkpoint.com> References: <3956.956038884@zippy.cdrom.com> <14394.956039927@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <14394.956039927@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Apr 18, 2000 at 08:38:47AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 18, 2000 at 08:38:47AM +0200, Poul-Henning Kamp wrote: > In message <3956.956038884@zippy.cdrom.com>, "Jordan K. Hubbard" writes: > >> IMHO, it's not such a bad idea. freebsd-current _is_ the place to > >> report problems with -current, why can't the report be produced by a > >> daemon? > > > >Becuase it's chunky and regular enough that I don't see why we > >also can't just create a new notification service for it. > > Because the people who don't compile LINT are unlikely to subscribe > to it. > > The alternative is to send it to committers, but I pressume all the > ports people would be pretty annoyed, and by sending it to -current > maybe a new junior hacker or two could be ferret out :-) > > >Think a bit bigger-picture also; theoretically, we should have these > >reports for -current and the RELENG_3 and RELENG_4 branches. The > >machine-resources are available for it, we just haven't organized > >it properly. I think reports for RELENG_3 and RELENG_4 should be sent to -stable rather than here, and sent only if something doesn't build or new warnings appear wrt the previous build; this should be rare enough not to bother -stable people and anyone MFCing should be reading -stable anyway? And I think sending -current reports here is a *great* idea and including kernel builds, not just make world, is also very good. Just my $0.02. -- Anatoly Vorobey, mellon@pobox.com http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 9:35:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (adsl-63-193-112-57.dsl.snfc21.pacbell.net [63.193.112.57]) by hub.freebsd.org (Postfix) with ESMTP id 5353437B68D for ; Tue, 18 Apr 2000 09:35:33 -0700 (PDT) (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 JAA02765; Tue, 18 Apr 2000 09:42:06 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200004181642.JAA02765@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Julian Elischer Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADSUP! linprocfs going away in 72 hours. In-reply-to: Your message of "Tue, 18 Apr 2000 07:50:45 PDT." <38FC762C.FF6D5DF@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Apr 2000 09:42:06 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Poul-Henning Kamp wrote: > > > > > Fully agreement here, and that was also what the core decision said: > > only visible to processed run under the linuxolator. > > This sounds like a very poor decision to me.. > It doesn't help the security issue at all and it > makes it more difficult to find out what is going on and > debug problems. This sounds more like a personal NIH problem > than a technical decision. > > A case of someone's bruised ego or something. It's already been resolved that having it in /compat/linux qualifies as good enough 'hiding'; we don't need to go down this again. -- \\ 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 Tue Apr 18 10:17:42 2000 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 901DB37B60D; Tue, 18 Apr 2000 10:17:39 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA14421; Tue, 18 Apr 2000 10:17:36 -0700 (PDT) (envelope-from dillon) Date: Tue, 18 Apr 2000 10:17:36 -0700 (PDT) From: Matthew Dillon Message-Id: <200004181717.KAA14421@apollo.backplane.com> To: Jonathan Lemon Cc: ache@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: event.h troubles References: <200004181407.JAA84381@prism.flugsvamp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In article you write: :>Now I got lost of :> :>/usr/include/sys/event.h:159: warning: `struct timespec' declared inside :>parameter list. :> :>because include it. :>Please fix somehow. : :I'm looking at this now. :-- :Jonathan this just means you have: int fubar(struct blah *ptr) ... Where 'struct blah' has not been previously struct. This is one of those broken ANSIsms. The solution is simple: struct blah; int fubar(struct blah *ptr) ... -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 Tue Apr 18 10:30:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from firehouse.net (spook.networkoperations.com [209.42.203.59]) by hub.freebsd.org (Postfix) with SMTP id 729B437B54D for ; Tue, 18 Apr 2000 10:30:34 -0700 (PDT) (envelope-from abc@firehouse.net) Received: (qmail 22933 invoked by uid 1000); 18 Apr 2000 17:30:27 -0000 Date: Tue, 18 Apr 2000 13:30:27 -0400 From: Alan Clegg To: freebsd-current@freebsd.org Subject: Patch to allow TSC with APM Message-ID: <20000418133027.D21818@ecto.greenpeas.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like to recommend the following patches. Adding the option "CLK_USE_TSC_ANYWAY" allows my laptop to use the TSC even though it is "flakey". This option should not be set by default. /usr/src/sys/i386/isa: *** clock.c.ORIG Tue Apr 18 09:45:52 2000 --- clock.c Tue Apr 18 10:21:49 2000 *************** *** 816,822 **** --- 816,832 ---- * We don't know at this point whether APM is going to be used * or not, nor when it might be activated. Play it safe. */ + #ifdef CLK_USE_TSC_ANYWAY + /* + * Some laptops lose so much time without the TSC that even if + * it is not "good", it is better than nothing. This allows + * a WinBook XL2 with no APM control to keep clock. Wihout + * this option, it loses over six seconds per minute. + */ + printf("Using TSC with APM\n"); + #else return; + #endif /* CLK_USE_TSC_ANYWAY */ #endif /* NAPM > 0 */ if (tsc_present && tsc_freq != 0 && !tsc_is_broken) { /usr/src/sys/conf: *** options.i386.orig Tue Apr 18 09:44:40 2000 --- options.i386 Tue Apr 18 10:22:38 2000 *************** *** 37,42 **** --- 37,43 ---- CLK_CALIBRATION_LOOP opt_clock.h CLK_USE_I8254_CALIBRATION opt_clock.h CLK_USE_TSC_CALIBRATION opt_clock.h + CLK_USE_TSC_ANYWAY opt_clock.h TIMER_FREQ opt_clock.h NO_F00F_HACK opt_cpu.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 10:36:21 2000 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 B7C6D37B9F7; Tue, 18 Apr 2000 10:36:15 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA14683; Tue, 18 Apr 2000 10:36:15 -0700 (PDT) (envelope-from dillon) Date: Tue, 18 Apr 2000 10:36:15 -0700 (PDT) From: Matthew Dillon Message-Id: <200004181736.KAA14683@apollo.backplane.com> To: Brian Fundakowski Feldman Cc: Alfred Perlstein , Michael Reifenberger , current@FreeBSD.org, alc@FreeBSD.org Subject: Anyone able to verify the fix for (was Re: panic: vm_object_shadow: source object has OBJ_ONEMAPPING set.) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has Brian or Michael or anyone been able to verify whether my patch below fixes the reported vm_object_shadow panics yet? I'd like to get it committed (or scrapped). -Matt Index: vm_map.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_map.c,v retrieving revision 1.187 diff -u -r1.187 vm_map.c --- vm_map.c 2000/02/28 04:10:35 1.187 +++ vm_map.c 2000/04/15 18:02:06 @@ -2119,10 +2119,14 @@ } /* - * Add the reference before calling vm_object_shadow - * to insure that a shadow object is created. + * Clear OBJ_ONEMAPPING before calling vm_object_shadow + * to ensure that a shadow object is created. Add a + * reference to cover the new vm_map_entry being + * associated with the object. */ vm_object_reference(object); + vm_object_clear_flag(object, OBJ_ONEMAPPING); + if (old_entry->eflags & MAP_ENTRY_NEEDS_COPY) { vm_object_shadow(&old_entry->object.vm_object, &old_entry->offset, @@ -2130,7 +2134,6 @@ old_entry->eflags &= ~MAP_ENTRY_NEEDS_COPY; object = old_entry->object.vm_object; } - vm_object_clear_flag(object, OBJ_ONEMAPPING); /* * Clone the entry, referencing the shared object. Index: vm_object.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_object.c,v retrieving revision 1.171.2.1 diff -u -r1.171.2.1 vm_object.c --- vm_object.c 2000/03/17 10:47:35 1.171.2.1 +++ vm_object.c 2000/04/15 18:13:58 @@ -900,7 +900,13 @@ source = *object; /* - * Don't create the new object if the old object isn't shared. + * If the old object is not shared we may be able to simply use it + * as the shadow rather then have to create a new object. Only + * objects that we can guarentee this case can be optimized - that is, + * only objects with no handles that other processes can get a hold + * of which are otherwise unassociated, have only one mapping, and + * only one reference count. XXX do we need the reference count check + * any more? XXX */ if (source != NULL && To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 10:38:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id F2E3F37B75D for ; Tue, 18 Apr 2000 10:38:17 -0700 (PDT) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000418173817.BWSU26343.mail.rdc1.ct.home.com@home.com> for ; Tue, 18 Apr 2000 10:38:17 -0700 Message-ID: <38FC9D51.4DD02C6E@home.com> Date: Tue, 18 Apr 2000 13:37:21 -0400 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: current errors Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any ideas as to the cause of the following errors in current. I have (2)isa non-pnp cards.. SB16(pcm) and a ne2000(ed0). The only other card is an AGP TNT2 video card. Apr 17 23:07:42 telecast /kernel: unknown0: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 Apr 17 23:07:42 telecast /kernel: unknown1: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 Apr 17 23:07:42 telecast /kernel: unknown2: at port 0x40-0x43 irq 0 on isa0 Apr 17 23:07:42 telecast /kernel: unknown3: at port 0x70-0x71 irq 8 on isa0 Apr 17 23:07:42 telecast /kernel: unknown: can't assign resources Apr 17 23:07:42 telecast /kernel: unknown4: at port 0x61 on isa0 Apr 17 23:07:42 telecast /kernel: unknown5: at port 0xf0-0xff irq 13 on isa0 Apr 17 23:07:42 telecast /kernel: unknown6: at iomem 0-0x9ffff,0xfffe0000-0xffffffff,0xfec00000-0xfec0ffff,0xfee00000-0xfee0ffff,0x100000-0x7ffffff on isa0 Apr 17 23:07:42 telecast /kernel: unknown7: at iomem 0xf0000-0xf3fff,0xf4000-0xf7fff,0xf8000-0xfbfff,0xfc000-0xfffff on isa0 Apr 17 23:07:42 telecast /kernel: unknown: can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: can't assign resources Apr 17 23:07:42 telecast /kernel: unknown: can't assign resources Apr 17 23:07:42 telecast /kernel: APIC_IO: Testing 8254 interrupt delivery Apr 17 23:07:42 telecast /kernel: APIC_IO: routing 8254 via IOAPIC #0 intpin 2 Apr 17 23:07:42 telecast /kernel: SMP: AP CPU #1 Launched! Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 10:46:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id EADA637B52A for ; Tue, 18 Apr 2000 10:46:48 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA95609; Tue, 18 Apr 2000 13:46:44 -0400 (EDT) (envelope-from wollman) Date: Tue, 18 Apr 2000 13:46:44 -0400 (EDT) From: Garrett Wollman Message-Id: <200004181746.NAA95609@khavrinen.lcs.mit.edu> To: tsikora@powerusersbbs.com Cc: "current@FreeBSD.ORG" Subject: current errors In-Reply-To: <38FC9D51.4DD02C6E@home.com> References: <38FC9D51.4DD02C6E@home.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Any ideas as to the cause of the following errors in current. Harmless. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 10:47:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 243C237B674 for ; Tue, 18 Apr 2000 10:47:45 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn25.imasy.or.jp [202.227.24.217]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.04) with ESMTP id CAA24371; Wed, 19 Apr 2000 02:47:42 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200004181747.CAA24371@tasogare.imasy.or.jp> To: abc@firehouse.net Cc: freebsd-current@freebsd.org Subject: Re: Patch to allow TSC with APM In-Reply-To: Your message of "Tue, 18 Apr 2000 13:30:27 -0400" <20000418133027.D21818@ecto.greenpeas.org> References: <20000418133027.D21818@ecto.greenpeas.org> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 19 Apr 2000 02:47:41 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > I'd like to recommend the following patches. Adding the option > "CLK_USE_TSC_ANYWAY" allows my laptop to use the TSC even though it > is "flakey". This option should not be set by default. I saw the same kind of patches and my laptop has this w/o any problems for long time. I'd like to commit submitted patch 2 or 3 days later if no objections. Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 10:53:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id C265F37B6B8; Tue, 18 Apr 2000 10:53:15 -0700 (PDT) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id MAA58609; Tue, 18 Apr 2000 12:56:50 -0500 (CDT) (envelope-from jlemon) Date: Tue, 18 Apr 2000 12:56:50 -0500 From: Jonathan Lemon To: Matthew Dillon Cc: Jonathan Lemon , ache@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: event.h troubles Message-ID: <20000418125650.G62026@prism.flugsvamp.com> References: <200004181407.JAA84381@prism.flugsvamp.com> <200004181717.KAA14421@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200004181717.KAA14421@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 18, 2000 at 10:17:36AM -0700, Matthew Dillon wrote: > > :In article you write: > :>Now I got lost of > :> > :>/usr/include/sys/event.h:159: warning: `struct timespec' declared inside > :>parameter list. > :> > :>because include it. > :>Please fix somehow. > : > :I'm looking at this now. > :-- > :Jonathan > > this just means you have: > > int fubar(struct blah *ptr) ... > > Where 'struct blah' has not been previously struct. This is one of those > broken ANSIsms. The solution is simple: Yeah, I know, but I fed the change through a full buildworld anyway to make sure I didn't break anything else. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 11: 1:37 2000 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 7BAAC37BA4C for ; Tue, 18 Apr 2000 11:01:34 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA17285; Tue, 18 Apr 2000 20:01:09 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mitsuru IWASAKI Cc: abc@firehouse.net, freebsd-current@FreeBSD.ORG Subject: Re: Patch to allow TSC with APM In-reply-to: Your message of "Wed, 19 Apr 2000 02:47:41 +0900." <200004181747.CAA24371@tasogare.imasy.or.jp> Date: Tue, 18 Apr 2000 20:01:09 +0200 Message-ID: <17283.956080869@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200004181747.CAA24371@tasogare.imasy.or.jp>, Mitsuru IWASAKI writes : >Hi, > >> I'd like to recommend the following patches. Adding the option >> "CLK_USE_TSC_ANYWAY" allows my laptop to use the TSC even though it >> is "flakey". This option should not be set by default. > >I saw the same kind of patches and my laptop has this w/o any problems >for long time. >I'd like to commit submitted patch 2 or 3 days later if no objections. It would be nice to have some kind of understanding why the tsc is better than the i8254 before we kludge it... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 11: 7: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from firehouse.net (spook.networkoperations.com [209.42.203.59]) by hub.freebsd.org (Postfix) with SMTP id 2B29437BA7B for ; Tue, 18 Apr 2000 11:07:04 -0700 (PDT) (envelope-from abc@firehouse.net) Received: (qmail 23313 invoked by uid 1000); 18 Apr 2000 18:07:00 -0000 Date: Tue, 18 Apr 2000 14:07:00 -0400 From: Alan Clegg To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: Patch to allow TSC with APM Message-ID: <20000418140700.A23152@ecto.greenpeas.org> References: <200004181747.CAA24371@tasogare.imasy.or.jp> <17283.956080869@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <17283.956080869@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Apr 18, 2000 at 08:01:09PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of the ether, Poul-Henning Kamp spewed forth the following bitstream: > >> I'd like to recommend the following patches. Adding the option > >> "CLK_USE_TSC_ANYWAY" allows my laptop to use the TSC even though it > >> is "flakey". This option should not be set by default. > > > >I saw the same kind of patches and my laptop has this w/o any problems > >for long time. > >I'd like to commit submitted patch 2 or 3 days later if no objections. > It would be nice to have some kind of understanding why the tsc is > better than the i8254 before we kludge it... Any ideas on what would be needed to go forward with that? AlanC -- \ Alan B. Clegg Just because I can \ abc@firehouse.net does not mean I will. \ \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 11:11:52 2000 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 9800837B52E for ; Tue, 18 Apr 2000 11:11:43 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id UAA17399; Tue, 18 Apr 2000 20:11:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alan Clegg Cc: freebsd-current@FreeBSD.ORG Subject: Re: Patch to allow TSC with APM In-reply-to: Your message of "Tue, 18 Apr 2000 14:07:00 EDT." <20000418140700.A23152@ecto.greenpeas.org> Date: Tue, 18 Apr 2000 20:11:33 +0200 Message-ID: <17397.956081493@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000418140700.A23152@ecto.greenpeas.org>, Alan Clegg writes: >Out of the ether, Poul-Henning Kamp spewed forth the following bitstream: > >> >> I'd like to recommend the following patches. Adding the option >> >> "CLK_USE_TSC_ANYWAY" allows my laptop to use the TSC even though it >> >> is "flakey". This option should not be set by default. >> > >> >I saw the same kind of patches and my laptop has this w/o any problems >> >for long time. >> >I'd like to commit submitted patch 2 or 3 days later if no objections. > >> It would be nice to have some kind of understanding why the tsc is >> better than the i8254 before we kludge it... > >Any ideas on what would be needed to go forward with that? If the offset is systematic, maybe we should do more to calibrate the i8254 against the RTC, say a 10 second period instead of just one sec (can be done in the back-ground). If it is because the bios fiddles the frequency all the time we should maybe understand the APM bios better. If it is because SMI interrupts "steal" time from us, then the TSC is maybe better. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 11:16:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 7E7F337BAA2 for ; Tue, 18 Apr 2000 11:16:34 -0700 (PDT) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000418181632.CONV26343.mail.rdc1.ct.home.com@home.com> for ; Tue, 18 Apr 2000 11:16:32 -0700 Message-ID: <38FCA648.BD7C7A81@home.com> Date: Tue, 18 Apr 2000 14:15:36 -0400 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: MAKEDEV warning Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After building a new kernel yesterday after a cvsup the following appeared. Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before 2000-06-01 to get rid of block devices I did a MAKEDEV all and the message still persists. Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 11:19:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from dragonstar.dhs.org (dsl-028-a.resnet.purdue.edu [128.211.161.178]) by hub.freebsd.org (Postfix) with ESMTP id 3D7E137BAF9 for ; Tue, 18 Apr 2000 11:19:40 -0700 (PDT) (envelope-from jonsmith@dragonstar.dhs.org) Received: from localhost (jonsmith@localhost) by dragonstar.dhs.org (8.9.3/8.9.3) with ESMTP id NAA58172; Tue, 18 Apr 2000 13:19:18 -0500 (EST) (envelope-from jonsmith@dragonstar.dhs.org) Date: Tue, 18 Apr 2000 13:19:18 -0500 (EST) From: Jonathan Smith To: tsikora@powerusersbbs.com Cc: "current@FreeBSD.ORG" Subject: Re: MAKEDEV warning In-Reply-To: <38FCA648.BD7C7A81@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 Did you install an updated MAKEDEV script? I *think* the point is that you need to bet rid of block devices, and to do so, you need a MAKEDEV script that doesn't make them... Just a guess.... On Tue, 18 Apr 2000, Ted Sikora wrote: > After building a new kernel yesterday after a cvsup the following > appeared. > > Apr 17 23:07:42 telecast /kernel: WARNING: run /dev/MAKEDEV before > 2000-06-01 to get rid of block devices > I did a MAKEDEV all and the message still persists. > > Regards, > -- > Ted Sikora > Jtl Development Group > tsikora@powerusersbbs.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Apr 18 11:19:48 2000 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 CAE7B37BABD for ; Tue, 18 Apr 2000 11:19:42 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 35A459EB3; Tue, 18 Apr 2000 14:19:40 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 2CFCDBCE0; Tue, 18 Apr 2000 14:19:40 -0400 (EDT) Date: Tue, 18 Apr 2000 14:19:40 -0400 (EDT) From: "Chris D. Faulhaber"