From owner-freebsd-stable Sun Jun 24 0:37:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id 527A337B405 for ; Sun, 24 Jun 2001 00:37:18 -0700 (PDT) (envelope-from aw1@stade.co.uk) Received: from stade.demon.co.uk ([158.152.29.164]) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 15E4TP-000NJH-0V for stable@freebsd.org; Sun, 24 Jun 2001 08:38:24 +0100 Received: from titus.stade.co.uk (titus [192.168.1.5]) by stade.demon.co.uk (8.11.4/8.11.4) with ESMTP id f5O7bHY06415 for ; Sun, 24 Jun 2001 08:37:17 +0100 (BST) (envelope-from aw1@titus.stade.co.uk) Received: (from aw1@localhost) by titus.stade.co.uk (8.11.4/8.11.4) id f5O7XdK50953 for stable@freebsd.org; Sun, 24 Jun 2001 08:33:39 +0100 (BST) (envelope-from aw1) Date: Sun, 24 Jun 2001 08:33:38 +0100 From: Adrian Wontroba To: stable@freebsd.org Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010624083338.A32993@titus.stade.co.uk> Reply-To: aw1@stade.co.uk Mail-Followup-To: Adrian Wontroba , stable@freebsd.org References: <15155.29806.145760.832648@guru.mired.org> <15155.56039.812973.488190@zircon.zircon.seattle.wa.us> <20010622235410.A41593@bean.overtone.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010622235410.A41593@bean.overtone.org>; from kevin.way@overtone.org on Fri, Jun 22, 2001 at 11:54:10PM -0400 X-Operating-System: FreeBSD 4.3-STABLE Organization: Yes, I need some of that. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 22, 2001 at 11:54:10PM -0400, Kevin Way wrote: > cvsup works fine over dialup, and not unacceptably slowly either. I cvsup the whole thing, maintaining my own local copy of the entire repository. Source, ports, doc, gnats, www. No refuse files at all (not got round to it). I normally use a 64K ISDN connection to my ISP, and the cvsup server is fairly "close" to them. Line utilisation is close to 100% only when rsyncing big files in the www collection (book.html etc). Most of the time line utilisation is very much less. Elapsed time is bearable. Of course, if you start with nothing, the first cvsup takes a while - 7 hours with two channels (128K) going, close to flat out as I recall. > A satisfied dialup cvsup user, Me too. I started with CTM, moved to checking out "stable" from a cvsup mirror, and on to having my own repository. Its all a bit heavy on disk space, but that is fairly plentiful nowadays. Aside: my first UNIX box ran SCO ODT, with 120 MB of disk and 8 MB of memory. Definitely too little disk (8-( -- Adrian Wontroba To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 0:43:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 9EB8837B406 for ; Sun, 24 Jun 2001 00:43:53 -0700 (PDT) (envelope-from cjc@earthlink.net) Received: from blossom.cjclark.org (dialup-209.245.139.105.Dial1.SanJose1.Level3.net [209.245.139.105]) by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA09441 for ; Sun, 24 Jun 2001 00:43:51 -0700 (PDT) Received: (from cjc@localhost) by blossom.cjclark.org (8.11.4/8.11.3) id f5O7jEP10933 for freebsd-stable@freebsd.org; Sun, 24 Jun 2001 00:45:14 -0700 (PDT) (envelope-from cjc) Date: Sun, 24 Jun 2001 00:45:14 -0700 From: "Crist J. Clark" To: freebsd-stable@freebsd.org Subject: /dev/console and Serial Device Problems Message-ID: <20010624004514.A10875@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just started having some really odd problems with a -STABLE I built this afternoon. /dev/console seems to be blocking when I use the serial port. I noticed since syslogd(8) did not seem to be working. I brought it up in debug and it would get caught on the first entry with /dev/console and just stick there, # syslogd -ds -vv sending on inet and/or inet6 socket off & running.... init cfline("*.err;kern.debug;auth.notice;mail.crit /dev/console", f, "*", "*") syslogd: /dev/console: Interrupted system call logmsg: pri 53, flags 4, from blossom, msg syslogd: /dev/console: Interrupted system call I removed all of the /dev/console lines one by one. Each time I ran syslogd(8) it would get caught at the next. It's now running fine with all /dev/console lines commented out. Just to see if it wasn't syslogd(8) I just did, # echo "hello" > /dev/console And it looked like I've hung that shell up hard. Then... I quit the tip(1) sesssion I had going in another window and the echo finished. I killed syslogd(8) and started it again with all of the console lines in place and it is fine... But now, if I try to start tip(1) again, # tip -9600 cuaa0c tip: /dev/cuaa0: Device busy link down Something seems broken. Note, # ls /var/spool/lock LCK..cuaa1 That's the lock on the modem, not the line to the other machine which is on cuaa0. Also, # ls -ali /dev/cua*0 /dev/console /dev/tty*d0 6334 crw------- 1 root wheel 0, 0 Jun 24 00:38 /dev/console 6814 crw-rw---- 1 uucp dialer 28, 128 Jun 24 00:28 /dev/cuaa0 6815 crw-rw---- 1 uucp dialer 28, 160 Jun 23 15:06 /dev/cuaia0 6816 crw-rw---- 1 uucp dialer 28, 192 Jun 23 15:06 /dev/cuala0 7374 crw------- 1 root wheel 28, 0 Jun 23 23:20 /dev/ttyd0 7375 crw------- 1 root wheel 28, 32 Jun 23 15:06 /dev/ttyid0 7376 crw------- 1 root wheel 28, 64 Jun 23 15:06 /dev/ttyld0 # fstat | egrep '(cua.*|tty.*d)0' # Any ideas? Not being able to use tip(1) to access other machines via serial console is annoying. -- Crist J. Clark cjclark@alum.mit.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 2: 2: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 2D9E337B401; Sun, 24 Jun 2001 02:01:39 -0700 (PDT) (envelope-from tedm@toybox.placo.com) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f5O91al92800; Sun, 24 Jun 2001 02:01:36 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: , , , Subject: RE: Kernel Panic Date: Sun, 24 Jun 2001 02:01:34 -0700 Message-ID: <004101c0fc8c$44e12280$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal In-Reply-To: <200106221156.AA442106040@stmail.pace.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG That would be impossible unless you had "." in your path. If you did (which is a very BAD thing) then yes your script probably loaded itself (assuming you named it "pine). This is why the system defaults to NOT having "." in the path. However, if the script DID load itself, a recursive script under an ordinary user ID isn't allowed to crash the system. I'd be very interested in seeing someone who thinks differently post a script that could do this. The ordinary users have limits restrictions that styme forkbombs and such like that. Of course, if a setuid-to-root binary has a programming bug that allows an ordinary user to call it recursively, then all bets are off. But pine is not normally setuid to root. But, since you are apparently so determined to NOT believe that your system has a hardware problem, in the interests of putting this issue to final rest, here is what I did on my own system (FreeBSD 4.2) 1) Logged in as an ordinary user 2) Issued the commands PATH=.:$PATH export PATH 3) Created the script: #!/bin/sh ./pine -i rm -rf $HOME/dead.letter (note that not only did I put current directory in my path - I forced the script to reload itself just to be as convincing as possible) 4) Then issued the command: pine 5) After about 16 seconds, I got this error message: ./pine: Cannot fork: Resource temporarily unavailable and the script exited and came back to the $ prompt. And, just for the sake of argument, I ALSO did the exact same thing as the root user, and got the exact same response. Please, you need to give the FreeBSD developers credit for SOME sense at least. Your not the only one that has ever built a recursive script by accident, you know. FreeBSD is not so fragile that this kind of thing is going to kill it. Like I said, you need to focus your attention on your disk subsystem. The script you built, called recursively, creates an intense burst of disk activity until the system runs out of resources. It's that burst of activity that's taking your system down, not the fact that the recursive script is consuming all free resources. Undoubtedly, if you were to run other equally disk-intensive programs on your machine they would cause it to crash as well. If you don't want to believe you have a hardware problem then fine, but please don't throw unwarranted stones at the OS in place of that. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Jonathan Slivko >Sent: Friday, June 22, 2001 8:56 AM >To: js43064n@pace.edu; freebsd-questions@FreeBSD.ORG; >freebsd-stable@FreeBSD.ORG; freebsd-security@FreeBSD.ORG; Ted >Mittelstaedt >Subject: RE: Kernel Panic > > >I think I see what caused the kernel to crash. What happened was >this, I believe, is that since I didn't specify the regular pine >binary, the script just loaded itself, thus throwing it into a >loop. It's really a sad situation. -- Jonathan > >______________________________________________ >Jonathan M. Slivko >Technical Support, Black Lotus Communications >http://www.blacklotus.net -- check us out! >---------------------------------------------- > > > >---------- Original Message ---------------------------------- >From: "Ted Mittelstaedt" >Date: Thu, 21 Jun 2001 23:34:02 -0700 > >>That absolutely will not crash a FreeBSD system that's not >>got other problems. >> >>However, what I think is going on here is that the system that >>you ran this on has buggy disk hardware. It's probably some >>IDE disk, right? >> >>I've got a system here that I've tried 5 different IDE paddle >>cards in, and on every one I've tried installing FreeBSD and >>doing different operations and within about 20 minutes I >>had crashed it and screweged the filesystem. >> >>I finally got so annoyed I dug up an old AHA1520 SCSI card >>and slapped a 1GB SCSI disk on it (the system isn't intended >>to be doing anything fancy) and it's been solid as a rock >>ever since. The best conclusion I have is that the ISA bus >>in the system has some clock speed error that doesen't affect >>the SCSI disk system. >> >>Ted Mittelstaedt tedm@toybox.placo.com >>Author of: The FreeBSD Corporate Networker's Guide >>Book website: http://www.freebsd-corp-net-guide.com >> >> >>>-----Original Message----- >>>From: owner-freebsd-questions@FreeBSD.ORG >>>[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of >Jonathan Slivko >>>Sent: Thursday, June 21, 2001 4:59 PM >>>To: freebsd-questions@FreeBSD.ORG; freebsd-stable@FreeBSD.ORG; >>>freebsd-security@FreeBSD.ORG >>>Subject: Kernel Panic >>> >>> >>>Hello, >>> >>>I just wrote a little shell script that, on the machine I tested >>>it on, crashed the box and forced a reboot. The contents of the >>>script was: >>> >>>#!/bin/sh >>>pine -i >>>rm -rf $HOME/dead.letter >>> >>>Thats the whole script. I don't see how something like that >could >>>cause a kernel to crash. Would anyone mind trying to replicate >>>this on a test box. If it's a security issue, i'll forward it to >>>security when I get more information. >>> >>>-- Jonathan >>> >>>______________________________________________ >>>Jonathan M. Slivko >>>Technical Support, Black Lotus Communications >>>http://www.blacklotus.net -- check us out! >>>---------------------------------------------- >>> >>>_________________________________________________________________ >__ >>>___ >>>Sent via the Pace University Mail system at stmail.pace.edu >>> >>> >>> >>> >>> >>>To Unsubscribe: send mail to majordomo@FreeBSD.org >>>with "unsubscribe freebsd-questions" in the body of the message >>> >> >>To Unsubscribe: send mail to majordomo@FreeBSD.org >>with "unsubscribe freebsd-stable" in the body of the message >> > > >___________________________________________________________________ >___ >Sent via the Pace University Mail system at stmail.pace.edu > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 2:35:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id CD5B437B40A for ; Sun, 24 Jun 2001 02:35:05 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.4/8.11.3) with ESMTP id f5O9Y3t21637; Sun, 24 Jun 2001 02:34:03 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: juha@saarinen.org Cc: joe@zircon.seattle.wa.us, stable@FreeBSD.ORG Subject: RE: Staying *really stable* in FreeBSD In-Reply-To: <00cf01c0fc40$c0348db0$0a01a8c0@den2> References: <15157.11221.593513.478892@zircon.zircon.seattle.wa.us> <00cf01c0fc40$c0348db0$0a01a8c0@den2> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010624023403R.jkh@osd.bsdi.com> Date: Sun, 24 Jun 2001 02:34:03 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: "Juha Saarinen" Subject: RE: Staying *really stable* in FreeBSD Date: Sun, 24 Jun 2001 12:00:59 +1200 > "19.2.2.2. Who needs FreeBSD-STABLE? > If you are a commercial user or someone who puts maximum stability of > their FreeBSD system before all other concerns, you should consider > tracking FreeBSD-STABLE. This is especially true if you have installed It's probably time to rewrite that paragraph substantially. It was something of a tactical error to encourage certain interest groups to run "work in progress" code, even if that work is very carefully bounded and kept "in progress" for the shortest periods possible. You just can't have a code base which is actually going places and having things actively updated (which is generally a really good idea, especially when the updates involved fixing bugs) and also guarantee that it's particularly usable for anything. Whether it builds flawlessly without warnings or not, it still represents a fairly significant unknown quantity until such time as you've frozen the code and spent a few weeks, at minimum, collecting user reports and making very carefully selected changes. We've also heard any number of suggestions for "fixing" the problem, from aggressive automated tagging (which would be tremendously expensive with CVS and not fix the "builds but doesn't work" problem) to extensive regression test suites that nobody seems to have time to actually write. As I said at the beginning, perhaps it's time to simply re-write the Handbook paragraph which inadvertently "sells" -stable as a solution for certain types of problems it was never meant to solve. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 4:24:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c007.snv.cp.net (c007-h011.c007.snv.cp.net [209.228.33.217]) by hub.freebsd.org (Postfix) with SMTP id 3EBC937B401 for ; Sun, 24 Jun 2001 04:24:16 -0700 (PDT) (envelope-from otterr@telocity.com) Received: (cpmta 2928 invoked from network); 24 Jun 2001 04:24:15 -0700 Received: from dsl-216-227-91-85.telocity.com (HELO zoso) (216.227.91.85) by smtp.telocity.com (209.228.33.217) with SMTP; 24 Jun 2001 04:24:15 -0700 X-Sent: 24 Jun 2001 11:24:15 GMT Reply-To: From: "Otter" To: , Subject: RE: /dev/console and Serial Device Problems Date: Sun, 24 Jun 2001 07:22:26 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20010624004514.A10875@blossom.cjclark.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Crist, This is something I've noticed recently also. I have a -stable machine with source from June 9th, 2001. I tried using both cu AND kermit to hook up to my Sun Sparcstation 5 to do a console install on it and my FreeBSD box locks up tighter than a drum with both applications. Because I had a few transfers going at the time and the FreeBSD machine in question is my gateway, I scrapped the idea just to get the thing back up and online by cycling power to the computer. I didn't have time then to troubleshoot the problem, but I'm open to ideas and can provide the time if anyone has any ideas. -Otter > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Crist J. Clark > Sent: Sunday, June 24, 2001 3:45 AM > To: freebsd-stable@freebsd.org > Subject: /dev/console and Serial Device Problems > > > I just started having some really odd problems with a > -STABLE I built > this afternoon. /dev/console seems to be blocking when I use the > serial port. I noticed since syslogd(8) did not seem to be > working. I > brought it up in debug and it would get caught on the first > entry with > /dev/console and just stick there, > > # syslogd -ds -vv > sending on inet and/or inet6 socket > off & running.... > init > cfline("*.err;kern.debug;auth.notice;mail.crit > /dev/console", f, "*", "*") > syslogd: /dev/console: Interrupted system call > logmsg: pri 53, flags 4, from blossom, msg syslogd: > /dev/console: Interrupted system call > > I removed all of the /dev/console lines one by one. Each time I ran > syslogd(8) it would get caught at the next. It's now > running fine with > all /dev/console lines commented out. > > Just to see if it wasn't syslogd(8) I just did, > > # echo "hello" > /dev/console > > And it looked like I've hung that shell up hard. > > Then... I quit the tip(1) sesssion I had going in another window and > the echo finished. I killed syslogd(8) and started it again with all > of the console lines in place and it is fine... > > But now, if I try to start tip(1) again, > > # tip -9600 cuaa0c > tip: /dev/cuaa0: Device busy > link down > > Something seems broken. Note, > > # ls /var/spool/lock > LCK..cuaa1 > > That's the lock on the modem, not the line to the other > machine which > is on cuaa0. Also, > > # ls -ali /dev/cua*0 /dev/console /dev/tty*d0 > 6334 crw------- 1 root wheel 0, 0 Jun 24 00:38 > /dev/console > 6814 crw-rw---- 1 uucp dialer 28, 128 Jun 24 00:28 /dev/cuaa0 > 6815 crw-rw---- 1 uucp dialer 28, 160 Jun 23 15:06 /dev/cuaia0 > 6816 crw-rw---- 1 uucp dialer 28, 192 Jun 23 15:06 /dev/cuala0 > 7374 crw------- 1 root wheel 28, 0 Jun 23 23:20 /dev/ttyd0 > 7375 crw------- 1 root wheel 28, 32 Jun 23 15:06 /dev/ttyid0 > 7376 crw------- 1 root wheel 28, 64 Jun 23 15:06 /dev/ttyld0 > # fstat | egrep '(cua.*|tty.*d)0' > # > > Any ideas? Not being able to use tip(1) to access other machines via > serial console is annoying. > -- > Crist J. Clark cjclark@alum.mit.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 4:58: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from arcadia.megadeb.org (cpe.atm0-0-0-218131.arcnxx5.customer.tele.dk [62.242.79.117]) by hub.freebsd.org (Postfix) with ESMTP id B1E3937B405 for ; Sun, 24 Jun 2001 04:57:53 -0700 (PDT) (envelope-from chopra@runbox.com) Received: (from chopra@localhost) by arcadia.megadeb.org (8.11.4/8.11.3) id f5OBxlX12658 for freebsd-stable@FreeBSD.ORG; Sun, 24 Jun 2001 13:59:47 +0200 (CEST) (envelope-from chopra) Date: Sun, 24 Jun 2001 13:59:47 +0200 From: Munish Chopra To: "freebsd-stable@FreeBSD.ORG" Subject: Re: /var/mail permissions: 0755 or 01777 ? Message-ID: <20010624135947.M284@arcadia.megadeb.org> Mail-Followup-To: "freebsd-stable@FreeBSD.ORG" References: <20010623134628.A511-100000@zoraida.reyes.somos.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from juha@saarinen.org on Sun, Jun 24, 2001 at 10:03:37AM +1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jun 24, 2001 at 10:03:37AM +1200, Juha Saarinen wrote: > > There's an automated muttrc configurator on the Web somewhere. It's not as http://mutt.netliberte.org -- -Munish To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 6:16:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from diarmadhi.mushhaven.net (diarmadhi.mushhaven.net [209.16.107.11]) by hub.freebsd.org (Postfix) with ESMTP id BBBEF37B401 for ; Sun, 24 Jun 2001 06:16:42 -0700 (PDT) (envelope-from mistwolf@diarmadhi.mushhaven.net) Received: (from mistwolf@localhost) by diarmadhi.mushhaven.net (8.11.4/8.11.4) id f5ODFMR26627 for freebsd-stable@freebsd.org; Sun, 24 Jun 2001 09:15:22 -0400 (EDT) (envelope-from mistwolf) Date: Sun, 24 Jun 2001 09:15:22 -0400 From: Jamie Norwood To: freebsd-stable@freebsd.org Subject: Swap problems. Message-ID: <20010624091522.A26604@mushhaven.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I get the below errors while compiling the kernel. Can anyone offer enlightenment on what is wrong and how to fix it? Jamie -- Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15248,size 12288, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15272,size 4096, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15272,size 4096, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15280,size 12288, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15280,size 12288, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15304,size 4096, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15304,size 4096, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15312,size 8192, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15312,size 8192, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15328,size 12288, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15328,size 12288, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15352,size 4096, error 6 Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15352,size 4096, error 6 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 6:41:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 2339537B405 for ; Sun, 24 Jun 2001 06:41:45 -0700 (PDT) (envelope-from j_trzaska@gmx.net) Received: (qmail 18779 invoked by uid 0); 24 Jun 2001 13:41:43 -0000 Received: from pd903741b.dip.t-dialin.net (HELO gmx.net) (217.3.116.27) by mail.gmx.net (mail06) with SMTP; 24 Jun 2001 13:41:43 -0000 Message-ID: <3B35EDD1.C27176F9@gmx.net> Date: Sun, 24 Jun 2001 15:40:33 +0200 From: Jens Trzaska X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: cjclark@alum.mit.edu Cc: freebsd-stable@freebsd.org Subject: Re: /dev/console and Serial Device Problems References: <20010624004514.A10875@blossom.cjclark.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello! "Crist J. Clark" wrote: > > I just started having some really odd problems with a -STABLE I built > this afternoon. /dev/console seems to be blocking when I use the > serial port. I noticed since syslogd(8) did not seem to be working. I > brought it up in debug and it would get caught on the first entry with > /dev/console and just stick there, > > # syslogd -ds -vv > sending on inet and/or inet6 socket > off & running.... > init > cfline("*.err;kern.debug;auth.notice;mail.crit /dev/console", f, "*", "*") > syslogd: /dev/console: Interrupted system call > logmsg: pri 53, flags 4, from blossom, msg syslogd: /dev/console: Interrupted system call For me its nearly the same. 2 or 3 weeks ago i put '-Dh' into boot.config to get the serial console working. It worked so far for 1 to 2 days. After that time I noticed that I was not able to su to root. The probem was that su makes an entry throug syslogd and that didn't react. And I was not able to get syslogd running without a reboot. It also could not use /dev/console. Now I'm running again without the serial console. I read some older messages in the archives about nearly the same problems. I think that needs to be corrected. Regards Jens Trzaska To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 7:25:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail13.sdc1.sfba.home.com (femail13.sdc1.sfba.home.com [24.0.95.140]) by hub.freebsd.org (Postfix) with ESMTP id 2B13437B401 for ; Sun, 24 Jun 2001 07:25:23 -0700 (PDT) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu ([24.12.197.197]) by femail13.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010624142522.SGCT26767.femail13.sdc1.sfba.home.com@math.missouri.edu> for ; Sun, 24 Jun 2001 07:25:22 -0700 Message-ID: <3B35F852.2290E18F@math.missouri.edu> Date: Sun, 24 Jun 2001 09:25:22 -0500 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Problems with md5 -p Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Suppose I have a file xxx. If I type md5 -p < xxx it should return the contents of the file followed by its md5 number: Some junk in the file 334911f8bcde69fe8edac561197e876f But now I get two numbers: Some junk in the file 334911f8bcde69fe8edac561197e876f d41d8cd98f00b204e9800998ecf8427e This is using FreeBSD stable of June 16. (Maybe this has been fixed more recently - please tell me of it has. It is a bit tricky for me to update sources because I use CTM which has been out recently - probably for just this very reason. But if I know the problem has been fixed then I will go through the effort of using cvsup.) -- Stephen Montgomery-Smith stephen@math.missouri.edu http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 8:57:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8ED5C37B401; Sun, 24 Jun 2001 08:57:31 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA82599; Sun, 24 Jun 2001 17:57:26 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Ted Mittelstaedt" Cc: , , , Subject: Re: Kernel Panic References: <004101c0fc8c$44e12280$1401a8c0@tedm.placo.com> From: Dag-Erling Smorgrav Date: 24 Jun 2001 17:57:26 +0200 In-Reply-To: <004101c0fc8c$44e12280$1401a8c0@tedm.placo.com> Message-ID: Lines: 26 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Ted Mittelstaedt" writes: > That would be impossible unless you had "." in your path. If > you did (which is a very BAD thing) then yes your script probably > loaded itself (assuming you named it "pine). This is why the > system defaults to NOT having "." in the path. No: 1) he simply had the script, named "pine", in a directory that was in his search path (e.g. $HOME/bin), and 2) the reason why you shouldn't have any relative path ("." included) in your search path is that you'd get unpredictible and surprising results, and potentially stumble across trojans (imagine an "ls" binary in some random user's home directory that, when you ran it, installed a setuid shell, or sent spam in your name, before giving you a carefully edited directory listing) > However, if the script DID load itself, a recursive script > under an ordinary user ID isn't allowed to crash the > system. Yes it is, unfortunately. FreeBSD doesn't like running out of swap space. Matt Dillon has been trying to correct this in -CURRENT, but it's not completely fixed yet. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 9:20:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 2805B37B401; Sun, 24 Jun 2001 09:20:10 -0700 (PDT) (envelope-from tedm@toybox.placo.com) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f5OGK3l93560; Sun, 24 Jun 2001 09:20:04 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: Cc: , , , Subject: RE: Kernel Panic Date: Sun, 24 Jun 2001 09:20:03 -0700 Message-ID: <006001c0fcc9$86301ce0$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: des@ofug.org [mailto:des@ofug.org] >Sent: Sunday, June 24, 2001 8:57 AM >To: Ted Mittelstaedt >Cc: js43064n@pace.edu; freebsd-questions@FreeBSD.ORG; >freebsd-stable@FreeBSD.ORG; freebsd-security@FreeBSD.ORG >Subject: Re: Kernel Panic > > >"Ted Mittelstaedt" writes: >> That would be impossible unless you had "." in your path. If >> you did (which is a very BAD thing) then yes your script probably >> loaded itself (assuming you named it "pine). This is why the >> system defaults to NOT having "." in the path. > >No: 1) he simply had the script, named "pine", in a directory that was >in his search path (e.g. $HOME/bin), That's a case I hadn't thought of - however, "local" search paths should generally be at the END of the user's path, not the beginning, in which case the system binary gets called first. Both cases are bad practice, and shouldn't be present on a normal system. > >Yes it is, unfortunately. FreeBSD doesn't like running out of swap >space. Matt Dillon has been trying to correct this in -CURRENT, but >it's not completely fixed yet. > I think in that situation you would have to have a swap partition that's smaller than the maximum amount of ram that a normal user is permitted to allocate - in that case the limits are set too high. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 9:22:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 1F2E737B405; Sun, 24 Jun 2001 09:22:42 -0700 (PDT) (envelope-from tedm@toybox.placo.com) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f5OGMbl93571; Sun, 24 Jun 2001 09:22:37 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: Cc: , , , Subject: RE: Kernel Panic Date: Sun, 24 Jun 2001 09:22:37 -0700 Message-ID: <006101c0fcc9$e1a84020$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: des@ofug.org [mailto:des@ofug.org] >Sent: Sunday, June 24, 2001 8:57 AM > > >Yes it is, unfortunately. FreeBSD doesn't like running out of swap >space. Matt Dillon has been trying to correct this in -CURRENT, but >it's not completely fixed yet. > One other thing - the recursive script the user originally posted does not appear to consume all free swap in the system. I still maintain he has a hardware error in the disk system. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 9:25:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id B2FDD37B405; Sun, 24 Jun 2001 09:25:09 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA82755; Sun, 24 Jun 2001 18:25:05 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Ted Mittelstaedt" Cc: , , , Subject: Re: Kernel Panic References: <006001c0fcc9$86301ce0$1401a8c0@tedm.placo.com> From: Dag-Erling Smorgrav Date: 24 Jun 2001 18:25:05 +0200 In-Reply-To: <006001c0fcc9$86301ce0$1401a8c0@tedm.placo.com> Message-ID: Lines: 22 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Ted Mittelstaedt" writes: > That's a case I hadn't thought of - however, "local" search paths should > generally be at the END of the user's path, not the beginning, in which case > the system binary gets called first. No! Local paths should be at the beginning, so local binaries (wrappers etc.) can ovverride system binaries. > Both cases are bad practice, and shouldn't be present on a normal system. Bollocks. > I think in that situation you would have to have a swap partition that's > smaller than the maximum amount of ram that a normal user is permitted to > allocate - in that case the limits are set too high. That, or the limits simply don't account for all the resources a user can consume, as is the case with mmap(). DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 9:26:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 0006F37B401; Sun, 24 Jun 2001 09:26:37 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA82771; Sun, 24 Jun 2001 18:26:34 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Ted Mittelstaedt" Cc: , , , Subject: Re: Kernel Panic References: <006101c0fcc9$e1a84020$1401a8c0@tedm.placo.com> From: Dag-Erling Smorgrav Date: 24 Jun 2001 18:26:33 +0200 In-Reply-To: <006101c0fcc9$e1a84020$1401a8c0@tedm.placo.com> Message-ID: Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Ted Mittelstaedt" writes: > One other thing - the recursive script the user originally posted does not > appear to consume all free swap in the system. I still maintain he has a > hardware error in the disk system. A disk error would not crash the system. Please stop spouting unfounded (though highly imaginative) bullshit. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 9:45: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 4D99F37B406; Sun, 24 Jun 2001 09:44:55 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id TRF97279; Sun, 24 Jun 2001 19:44:44 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.4/8.11.4) id f5OGheO00896; Sun, 24 Jun 2001 19:43:40 +0300 (EEST) (envelope-from netch) Date: Sun, 24 Jun 2001 19:43:40 +0300 From: Valentin Nechayev To: Stephen Montgomery-Smith Cc: freebsd-stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems with md5 -p Message-ID: <20010624194339.A717@iv.nn.kiev.ua> References: <3B35F852.2290E18F@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B35F852.2290E18F@math.missouri.edu>; from stephen@math.missouri.edu on Sun, Jun 24, 2001 at 09:25:22AM -0500 X-42: On Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sun, Jun 24, 2001 at 09:25:22, stephen (Stephen Montgomery-Smith) wrote about "Problems with md5 -p": I reproduce it stably on my -current. The second checksum is constant and it is MD5 checksum of an empty stream: root@iv:/usr/HEAD/src/sbin/md5##md5 Suppose I have a file xxx. If I type > > md5 -p < xxx > > it should return the contents of the file followed by its md5 number: > > Some junk in the file > > 334911f8bcde69fe8edac561197e876f > > But now I get two numbers: > > Some junk in the file > > 334911f8bcde69fe8edac561197e876f > d41d8cd98f00b204e9800998ecf8427e > > This is using FreeBSD stable of June 16. (Maybe this has been fixed > more recently - please tell me of it has. It is a bit tricky for me to > update sources because I use CTM which has been out recently - probably > for just this very reason. But if I know the problem has been fixed > then I will go through the effort of using cvsup.) /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 9:54:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 1E40C37B406; Sun, 24 Jun 2001 09:54:09 -0700 (PDT) (envelope-from tedm@toybox.placo.com) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f5OGs3l93676; Sun, 24 Jun 2001 09:54:04 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: Cc: , , , Subject: RE: Kernel Panic Date: Sun, 24 Jun 2001 09:54:03 -0700 Message-ID: <006501c0fcce$45fc5080$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: des@ofug.org [mailto:des@ofug.org] >Sent: Sunday, June 24, 2001 9:25 AM >To: Ted Mittelstaedt >Cc: js43064n@pace.edu; freebsd-questions@FreeBSD.ORG; >freebsd-stable@FreeBSD.ORG; freebsd-security@FreeBSD.ORG >Subject: Re: Kernel Panic > > >"Ted Mittelstaedt" writes: >> That's a case I hadn't thought of - however, "local" search paths should >> generally be at the END of the user's path, not the beginning, >in which case >> the system binary gets called first. > >No! Local paths should be at the beginning, so local binaries >(wrappers etc.) can ovverride system binaries. > I was half-expecting you to say something like that. In response: NO, local wrappers should NEVER be named the same as system binaries because the user then gets used to assuming that the wrapper is in place for all systems Imagine a local wrapper named "rm" that instead of deleting the file puts it in a "garbage pail". You get used to the garbage pail and get sloppy in what you remove - then one day your on another system and do an "rm" without thinking, then realize a mistake, go to the "garbage pail" and find that it doesen't exist. Wahhh!!!! Now, if you are the administrator and you want to wrap a system binary then you do it by renaming the system binary something else, and putting the wrapper in the place the system binary is. But that's not a case of a local binary. >> Both cases are bad practice, and shouldn't be present on a normal system. > >Bollocks. > Bollocks back. If you name your local wrappers your own names then the wrapper works fine if the local path is at the end of the search path. I can see putting the local path at the front for TEMPORARY use - like if you were developing a system binary you wanted to repeatedly test - but you go on a big limb by making a bunch of custom wrappers that duplicate the system binary names. >> I think in that situation you would have to have a swap partition that's >> smaller than the maximum amount of ram that a normal user is permitted to >> allocate - in that case the limits are set too high. > >That, or the limits simply don't account for all the resources a user >can consume, as is the case with mmap(). > OK - but then this is a case where the limiting device is broken. Maybe that should be worked on as well as the swap problem too, no? Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 9:57:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 44A6737B407; Sun, 24 Jun 2001 09:57:01 -0700 (PDT) (envelope-from tedm@toybox.placo.com) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f5OGuvl93700; Sun, 24 Jun 2001 09:56:57 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: Cc: , , , Subject: RE: Kernel Panic Date: Sun, 24 Jun 2001 09:56:56 -0700 Message-ID: <006601c0fcce$ad789fc0$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I didn't say "disk error" I said "disk system" and I made a particular point in the first message of saying that such an error is most likely due to a combination of problems with the motherboard and disk. And YES, a disk subsystem error CAN crash the system in fact not only crash it but completely garbage the filesystem in the process. I think your own imagination has run away with you. ;-) Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: des@ofug.org [mailto:des@ofug.org] >Sent: Sunday, June 24, 2001 9:27 AM >To: Ted Mittelstaedt >Cc: js43064n@pace.edu; freebsd-questions@FreeBSD.ORG; >freebsd-stable@FreeBSD.ORG; freebsd-security@FreeBSD.ORG >Subject: Re: Kernel Panic > > >"Ted Mittelstaedt" writes: >> One other thing - the recursive script the user originally >posted does not >> appear to consume all free swap in the system. I still maintain >he has a >> hardware error in the disk system. > >A disk error would not crash the system. Please stop spouting >unfounded (though highly imaginative) bullshit. > >DES >-- >Dag-Erling Smorgrav - des@ofug.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 11:16:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail12.sdc1.sfba.home.com (femail12.sdc1.sfba.home.com [24.0.95.108]) by hub.freebsd.org (Postfix) with ESMTP id C7D6F37B431; Sun, 24 Jun 2001 11:16:08 -0700 (PDT) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu ([24.12.197.197]) by femail12.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010624181608.ZNJM1636.femail12.sdc1.sfba.home.com@math.missouri.edu>; Sun, 24 Jun 2001 11:16:08 -0700 Message-ID: <3B362E67.5BFC9AF2@math.missouri.edu> Date: Sun, 24 Jun 2001 13:16:07 -0500 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Valentin Nechayev Cc: freebsd-stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems with md5 -p References: <3B35F852.2290E18F@math.missouri.edu> <20010624194339.A717@iv.nn.kiev.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK, I'm going to make this into a PR so that it gets fixed soon. (The problem in stable appeared between May 19 and June 16.) Valentin Nechayev wrote: > > Sun, Jun 24, 2001 at 09:25:22, stephen (Stephen Montgomery-Smith) wrote about "Problems with md5 -p": > > I reproduce it stably on my -current. The second checksum is constant > and it is MD5 checksum of an empty stream: > > root@iv:/usr/HEAD/src/sbin/md5##md5 d41d8cd98f00b204e9800998ecf8427e > > A fix: > > --- md5.c.orig Mon Jun 4 00:38:02 2001 > +++ md5.c Sun Jun 24 19:37:13 2001 > @@ -65,7 +65,7 @@ > switch (ch) { > case 'p': > MDFilter(1); > - break; > + exit(0); > case 'q': > qflag = 1; > break; > > This avoids determination of other options, but this does not conflict > directly with man page. > > Moreover such exit(0) should be applied not only with -p, but also with > -x, -t and -s: all these options should not gather any input files. > Patch is trivial. > > > Suppose I have a file xxx. If I type > > > > md5 -p < xxx > > > > it should return the contents of the file followed by its md5 number: > > > > Some junk in the file > > > > 334911f8bcde69fe8edac561197e876f > > > > But now I get two numbers: > > > > Some junk in the file > > > > 334911f8bcde69fe8edac561197e876f > > d41d8cd98f00b204e9800998ecf8427e > > > > This is using FreeBSD stable of June 16. (Maybe this has been fixed > > > more recently - please tell me of it has. It is a bit tricky for me to > > update sources because I use CTM which has been out recently - probably > > for just this very reason. But if I know the problem has been fixed > > then I will go through the effort of using cvsup.) > > /netch -- Stephen Montgomery-Smith stephen@math.missouri.edu http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 11:28:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 1B8EE37B405 for ; Sun, 24 Jun 2001 11:28:40 -0700 (PDT) (envelope-from oberman@ptavv.es.net) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id f5OIScc25602; Sun, 24 Jun 2001 11:28:38 -0700 (PDT) Message-Id: <200106241828.f5OIScc25602@ptavv.es.net> To: Donn Miller Cc: Stephen Montgomery-Smith , freebsd-stable@freebsd.org Subject: Re: Printer problems In-reply-to: Your message of "Sat, 23 Jun 2001 22:12:41 PDT." <20010624051241.24915.qmail@web14704.mail.yahoo.com> Date: Sun, 24 Jun 2001 11:28:38 -0700 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Sat, 23 Jun 2001 22:12:41 -0700 (PDT) > From: Donn Miller > Sender: owner-freebsd-stable@FreeBSD.ORG > > Actually, I don't think this is the case with your printer, but I > thought I would give it a shot. I think it's a thing with the HP > printers that they seem to not work very well unless you use polling. Ahh. This sounds interesting! I have been having the same problem with my HP 610C. Is it possible to set up the printer to do polling in FreeBSD? The only reference I see to polling in the man page is in "BUGS" and it only says that: Polling timeouts are controlled by counting loop iterations rather than timers, and so are dependent on CPU speed. I'd love to get this resolved some day. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 11:53:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from aragorn.neomedia.it (aragorn.neomedia.it [195.103.207.6]) by hub.freebsd.org (Postfix) with ESMTP id 1019137B407 for ; Sun, 24 Jun 2001 11:53:22 -0700 (PDT) (envelope-from bartequi@neomedia.it) Received: (from httpd@localhost) by aragorn.neomedia.it (8.11.3/8.10.1) id f5OIrBd04203; Sun, 24 Jun 2001 20:53:11 +0200 (CEST) To: Kevin Oberman Subject: Re: Printer problems Message-ID: <993408791.3b36371730743@webmail.neomedia.it> Date: Sun, 24 Jun 2001 20:53:11 +0200 (CEST) From: Salvo Bartolotta Cc: Donn Miller , Stephen Montgomery-Smith , freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.4-cvs X-WebMail-Company: Neomedia s.a.s. X-Originating-IP: 62.98.237.187 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Is it possible to set up the printer to do polling in > FreeBSD? man lptcontrol I haven't (yet) used a HP printer under FreeBSD. Mit freundlischen Gruessen, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 12:52:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 05D5137B401; Sun, 24 Jun 2001 12:52:26 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f5OJpqV79628; Sun, 24 Jun 2001 12:51:52 -0700 (PDT) (envelope-from dillon) Date: Sun, 24 Jun 2001 12:51:52 -0700 (PDT) From: Matt Dillon Message-Id: <200106241951.f5OJpqV79628@earth.backplane.com> To: Dag-Erling Smorgrav Cc: "Ted Mittelstaedt" , , , , Subject: Re: Kernel Panic References: <004101c0fc8c$44e12280$1401a8c0@tedm.placo.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :> However, if the script DID load itself, a recursive script :> under an ordinary user ID isn't allowed to crash the :> system. : :Yes it is, unfortunately. FreeBSD doesn't like running out of swap :space. Matt Dillon has been trying to correct this in -CURRENT, but :it's not completely fixed yet. : :DES :-- :Dag-Erling Smorgrav - des@ofug.org The out of swap handling should be completely fixed on -current and -stable now. My tests and Paul Saab's tests come up roses now. In regards to the original authors bug report... I haven't heard what version of FreeBSD he is running. Under normal circumstances a runaway script should not be able to take the machine down. Prior to the swap handling fixes if sufficient resource limits are set or the script is run as root, then such a script could lockup the machhine. But it is also unclear to me what the author meant by "crash"... did it panic? Was there a panic message? Did it start bashing the disks and appear not to stop? What? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 14:10: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rz.uni-ulm.de (sirius-giga.rz.uni-ulm.de [134.60.246.36]) by hub.freebsd.org (Postfix) with ESMTP id 2086C37B405 for ; Sun, 24 Jun 2001 14:10:02 -0700 (PDT) (envelope-from siegbert.baude@gmx.de) Received: from gmx.de (lilith.wohnheim.uni-ulm.de [134.60.106.64]) by mail.rz.uni-ulm.de (8.9.3/8.9.3) with ESMTP id XAA08712; Sun, 24 Jun 2001 23:09:57 +0200 (MEST) Message-ID: <3B365723.7C8E6E4D@gmx.de> Date: Sun, 24 Jun 2001 23:09:55 +0200 From: Siegbert Baude X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: de, en MIME-Version: 1.0 To: Kevin Oberman Cc: freebsd-stable@freebsd.org Subject: Re: Printer problems References: <200106241828.f5OIScc25602@ptavv.es.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Kevin: > > Actually, I don't think this is the case with your printer, but I > > thought I would give it a shot. I think it's a thing with the HP > > printers that they seem to not work very well unless you use polling. > > Ahh. This sounds interesting! I have been having the same problem with > my HP 610C. Is it possible to set up the printer to do polling in > FreeBSD? The only reference I see to polling in the man page is in > "BUGS" and it only says that: > Polling timeouts are controlled by counting loop iterations rather than > timers, and so are dependent on CPU speed. I think this can also be set in the kernel. Look at man ppbus and ppc. I can't remeber exactly, but isn't disabling an irq for the printer equivalent to polling mode? This would be possible there. Hth Siegbert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 14:11: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 1D57237B405; Sun, 24 Jun 2001 14:10:50 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id AEC07402; Mon, 25 Jun 2001 00:10:39 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.4/8.11.4) id f5OLAKh04999; Mon, 25 Jun 2001 00:10:20 +0300 (EEST) (envelope-from netch) Date: Mon, 25 Jun 2001 00:10:20 +0300 From: Valentin Nechayev To: Stephen Montgomery-Smith , ru@freebsd.org Cc: freebsd-stable@freebsd.org, current@freebsd.org Subject: Re: Problems with md5 -p Message-ID: <20010625001020.B4663@iv.nn.kiev.ua> References: <3B35F852.2290E18F@math.missouri.edu> <20010624194339.A717@iv.nn.kiev.ua> <3B362E67.5BFC9AF2@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B362E67.5BFC9AF2@math.missouri.edu>; from stephen@math.missouri.edu on Sun, Jun 24, 2001 at 01:16:07PM -0500 X-42: On Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sun, Jun 24, 2001 at 13:16:07, stephen (Stephen Montgomery-Smith) wrote about "Re: Problems with md5 -p": > OK, I'm going to make this into a PR so that it gets fixed soon. (The > problem in stable appeared between May 19 and June 16.) Yes, it appeared with commits: ru 2001/05/22 03:33:44 PDT Modified files: sbin/md5 Makefile md5.c Removed files: sbin/md5 global.h Log: Fix argument processing. Make this compile with WARNS=2. PR: bin/27524 MFC after: 3 days Revision Changes Path 1.5 +3 -1 src/sbin/md5/Makefile 1.22 +46 -52 src/sbin/md5/md5.c ru 2001/05/26 05:08:35 PDT Modified files: (Branch: RELENG_4) sbin/md5 md5.c Removed files: (Branch: RELENG_4) sbin/md5 global.h Log: MFC: fix argument processing. Revision Changes Path 1.20.2.2 +46 -52 src/sbin/md5/md5.c Before them the case when MDFilter(0) should be called, checked separately (argc==1). After them it is not checked, "fix argument processing" is somehow wrong. IMO these commits should be reverted. > Valentin Nechayev wrote: > > > > Sun, Jun 24, 2001 at 09:25:22, stephen (Stephen Montgomery-Smith) wrote about "Problems with md5 -p": > > > > I reproduce it stably on my -current. The second checksum is constant > > and it is MD5 checksum of an empty stream: > > > > root@iv:/usr/HEAD/src/sbin/md5##md5 > d41d8cd98f00b204e9800998ecf8427e > > > > A fix: > > > > --- md5.c.orig Mon Jun 4 00:38:02 2001 > > +++ md5.c Sun Jun 24 19:37:13 2001 > > @@ -65,7 +65,7 @@ > > switch (ch) { > > case 'p': > > MDFilter(1); > > - break; > > + exit(0); > > case 'q': > > qflag = 1; > > break; > > > > This avoids determination of other options, but this does not conflict > > directly with man page. > > > > Moreover such exit(0) should be applied not only with -p, but also with > > -x, -t and -s: all these options should not gather any input files. > > Patch is trivial. > > > > > Suppose I have a file xxx. If I type > > > > > > md5 -p < xxx > > > > > > it should return the contents of the file followed by its md5 number: > > > > > > Some junk in the file > > > > > > 334911f8bcde69fe8edac561197e876f > > > > > > But now I get two numbers: > > > > > > Some junk in the file > > > > > > 334911f8bcde69fe8edac561197e876f > > > d41d8cd98f00b204e9800998ecf8427e > > > > > > This is using FreeBSD stable of June 16. (Maybe this has been fixed > > > > > more recently - please tell me of it has. It is a bit tricky for me to > > > update sources because I use CTM which has been out recently - probably > > > for just this very reason. But if I know the problem has been fixed > > > then I will go through the effort of using cvsup.) /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 15:11:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f12.law7.hotmail.com [216.33.237.12]) by hub.freebsd.org (Postfix) with ESMTP id 5BD1B37B405 for ; Sun, 24 Jun 2001 15:11:12 -0700 (PDT) (envelope-from dimuthu@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 24 Jun 2001 15:11:12 -0700 Received: from 203.39.46.163 by lw7fd.law7.hotmail.msn.com with HTTP; Sun, 24 Jun 2001 22:11:11 GMT X-Originating-IP: [203.39.46.163] From: "Dimuthu Bandara" To: freebsd-stable@freebsd.org Subject: Kernel Error Message Date: Sun, 24 Jun 2001 22:11:11 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 24 Jun 2001 22:11:12.0102 (UTC) FILETIME=[93F9D060:01C0FCFA] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Can Somebody explain me why I get this error? Jun 25 03:08:43 bs /kernel: (da1:ahc0:0:2:0): SCB 0x10 - timed out in Data-in phase, SEQADDR == 0x87 Jun 25 03:08:43 bs /kernel: STACK == 0x84, 0x189, 0x149, 0x0 Jun 25 03:08:43 bs /kernel: SXFRCTL0 == 0xa8 Jun 25 03:08:43 bs /kernel: ahc0: Dumping Card State at SEQADDR 0x87 Jun 25 03:08:43 bs /kernel: SCSISEQ = 0x12, SBLKCTL = 0x2, SSTAT0 0x7 Jun 25 03:08:43 bs /kernel: SCB count = 80 Jun 25 03:08:43 bs /kernel: Kernel NEXTQSCB = 30 Jun 25 03:08:43 bs /kernel: Card NEXTQSCB = 26 Jun 25 03:08:43 bs /kernel: QINFIFO entries: 26 44 47 6 22 69 14 35 79 Jun 25 03:08:43 bs /kernel: Waiting Queue entries: Jun 25 03:08:43 bs /kernel: Disconnected Queue entries: Jun 25 03:08:43 bs /kernel: QOUTFIFO entries: Jun 25 03:08:43 bs /kernel: Sequencer Free SCB List: 7 11 1 2 5 12 9 10 8 3 4 6 15 13 0 Jun 25 03:08:43 bs /kernel: Pending list: 79 35 14 69 22 6 47 44 26 16 Jun 25 03:08:43 bs /kernel: Kernel Free SCB list: 58 53 67 31 36 13 10 20 52 37 34 45 28 56 2 25 7 43 42 33 62 59 5 19 68 3 4 15 27 49 24 8 65 54 1 0 11 51 12 76 40 57 17 48 46 21 23 39 18 9 38 41 66 32 64 77 78 63 29 61 60 50 55 75 74 73 72 71 70 Jun 25 03:08:43 bs /kernel: sg[0] - Addr 0x7d8000 : Length 4096 Jun 25 03:08:43 bs /kernel: sg[1] - Addr 0x2e99000 : Length 2048 Jun 25 03:08:43 bs /kernel: (da1:ahc0:0:2:0): BDR message in message buffer Jun 25 03:08:43 bs /kernel: (da1:ahc0:0:2:0): SCB 0x10 - timed out in Data-in phase, SEQADDR == 0x87 Jun 25 03:08:43 bs /kernel: STACK == 0x84, 0x189, 0x149, 0x0 Jun 25 03:08:43 bs /kernel: SXFRCTL0 == 0xa8 Jun 25 03:08:43 bs /kernel: ahc0: Dumping Card State at SEQADDR 0x87 Jun 25 03:08:43 bs /kernel: SCSISEQ = 0x12, SBLKCTL = 0x2, SSTAT0 0x7 Jun 25 03:08:43 bs /kernel: SCB count = 80 Jun 25 03:08:43 bs /kernel: Kernel NEXTQSCB = 30 Jun 25 03:08:43 bs /kernel: Card NEXTQSCB = 26 Jun 25 03:08:43 bs /kernel: QINFIFO entries: 26 44 47 6 22 69 14 35 79 Jun 25 03:08:43 bs /kernel: Waiting Queue entries: Jun 25 03:08:43 bs /kernel: Disconnected Queue entries: Jun 25 03:08:43 bs /kernel: QOUTFIFO entries: Jun 25 03:08:43 bs /kernel: Sequencer Free SCB List: 7 11 1 2 5 12 9 10 8 3 4 6 15 13 0 Jun 25 03:08:43 bs /kernel: Pending list: 79 35 14 69 22 6 47 44 26 16 Jun 25 03:08:43 bs /kernel: Kernel Free SCB list: 58 53 67 31 36 13 10 20 52 37 34 45 28 56 2 25 7 43 42 33 62 59 5 19 68 3 4 15 27 49 24 8 65 54 1 0 11 51 12 76 40 57 17 48 46 21 23 39 18 9 38 41 66 32 64 77 78 63 29 61 60 50 55 75 74 73 72 71 70 Jun 25 03:08:43 bs /kernel: sg[0] - Addr 0x7d8000 : Length 4096 Jun 25 03:08:43 bs /kernel: sg[1] - Addr 0x2e99000 : Length 2048 Jun 25 03:08:43 bs /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b Jun 25 03:08:43 bs /kernel: ahc0: Issued Channel A Bus Reset. 10 SCBs aborted Regards Dimuthu _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 15:33:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id A8C3A37B405 for ; Sun, 24 Jun 2001 15:33:21 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f5OMXJp80303; Sun, 24 Jun 2001 15:33:19 -0700 (PDT) (envelope-from dillon) Date: Sun, 24 Jun 2001 15:33:19 -0700 (PDT) From: Matt Dillon Message-Id: <200106242233.f5OMXJp80303@earth.backplane.com> To: Jamie Norwood Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Swap problems. References: <20010624091522.A26604@mushhaven.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :I get the below errors while compiling the kernel. Can anyone offer :enlightenment on what is wrong and how to fix it? : :Jamie Hmm. Please provide the contents of your /var/run/dmesg.boot and /etc/rc.conf, and the output from 'pstat -s' and 'df'. The only thing I can think of is that you are configuring swap on the wrong device. -Matt :-- : :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15248,size 12288, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15272,size 4096, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15272,size 4096, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15280,size 12288, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15280,size 12288, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15304,size 4096, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15304,size 4096, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15312,size 8192, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15312,size 8192, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15328,size 12288, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15328,size 12288, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15352,size 4096, error 6 :Jun 24 09:12:45 perath /kernel: swap_pager: I/O error - pageout failed; blkno 15352,size 4096, error 6 : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-stable" in the body of the message : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 17:39:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-172.zoominternet.net [24.154.28.172]) by hub.freebsd.org (Postfix) with ESMTP id 852B437B401 for ; Sun, 24 Jun 2001 17:39:41 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from topperwein.dyndns.org (topperwein.dyndns.org [192.168.168.10]) by topperwein.dyndns.org (8.11.4/8.11.4) with ESMTP id f5P0fAM18357 for ; Sun, 24 Jun 2001 20:41:10 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Sun, 24 Jun 2001 20:41:10 -0400 (EDT) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD-Stable Subject: RE: Staying *really stable* in FreeBSD In-Reply-To: <15155.56039.812973.488190@zircon.zircon.seattle.wa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 22 Jun 2001, Joe Kelsey wrote: > I personally think it does not matter how often you cvsup and rebuild. > Sometimes, I go for months, sometimes I do it daily. It all depends. Indeed. If there aren't any recent "gotchas" posted to -stable without "here's the fix, it's already been MFC'd", cvsup away. If there *are* gotchas, hold off. It's not possible to predict, which is why you must follow the list to avoid being bitten. > If you have any thoughts of running cvsup at all, you need to have a > fast connection. It is definitely not for dialup users. Maybe that > should go in the handbook--only do it if you have DSL or cable modem or > better. That's not true. When I still had only a dialup connection, I'd fire up cvsup, go to bed, and then start my buildworld in the morning. It worked just fine. > My basic point is that it is not possible to "schedule" the activity in > advance due to the changing nature of the source tree. You have to > constantly monitor the mailing list and make your own decision based on > mailing list traffic. Ayup. -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 17:53: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-172.zoominternet.net [24.154.28.172]) by hub.freebsd.org (Postfix) with ESMTP id 7E9B137B406 for ; Sun, 24 Jun 2001 17:53:00 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from topperwein.dyndns.org (topperwein.dyndns.org [192.168.168.10]) by topperwein.dyndns.org (8.11.4/8.11.4) with ESMTP id f5P0sTM18384 for ; Sun, 24 Jun 2001 20:54:29 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Sun, 24 Jun 2001 20:54:29 -0400 (EDT) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD-Stable Subject: Re: Staying *really stable* in FreeBSD In-Reply-To: <15157.18428.497356.447656@zircon.zircon.seattle.wa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Jun 2001, Joe Kelsey wrote: > I think we need to change the handbook to indicate the pitfalls inherent > in attempting to track stable or current via cvsup or other source > updating. Even tracking RELEASE_X_Y is problematic since it involves > recompiling from source, which is, of course the only way to customize > your kernel. Sort of. You can do a lot with klds, as you observe, and you can do still more with sysctl. (Aside: what *can't* you set with sysctl? It'd be a useful exercise to compile that list, and make it smaller.) -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 18:19:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from topperwein.dyndns.org (acs-24-154-28-172.zoominternet.net [24.154.28.172]) by hub.freebsd.org (Postfix) with ESMTP id B544A37B401 for ; Sun, 24 Jun 2001 18:19:09 -0700 (PDT) (envelope-from behanna@zbzoom.net) Received: from topperwein.dyndns.org (topperwein.dyndns.org [192.168.168.10]) by topperwein.dyndns.org (8.11.4/8.11.4) with ESMTP id f5P1KcM18421 for ; Sun, 24 Jun 2001 21:20:39 -0400 (EDT) (envelope-from behanna@zbzoom.net) Date: Sun, 24 Jun 2001 21:20:38 -0400 (EDT) From: Chris BeHanna Reply-To: Chris BeHanna To: FreeBSD-Stable Subject: RE: Staying *really stable* in FreeBSD In-Reply-To: <15157.25654.158066.311481@guru.mired.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Jun 2001, Mike Meyer wrote: > FreeBSD Admin types: > > I haven't posting anything in some time, so I'm making up for it now with > > this tome. 8-) It says nothing important and means nothing, so skip as you > > like. > > You do have some very good points, and some of them are being > addressed already. > > > Don't think that the computer industry doesn't look at what goes on at the > > FreeBSD jamboree. FreeBSD could be the next Linux, (stop booing) in terms > > of gaining a much larger industry following since we all know it totally > > trashes Linux. But and it's a big BUT, the industry PERCEPTION of the > > FreeBSD community, it's response to security problems, it's ability to > > recognize problems with stability, and reliability, seems to matter more > > than what the reality is. > > This is all very true, but you have to consider what the goal of the > project - or rather, the people working on it - is. While I don't > speak for them, as far as I'm concerned getting lots of people to use > FreeBSD is less important than continuing to provide a quality > computing platform. One of the advantages of open source is that the > developers can ignore the popularity contest of the market, and > concentrate on quality. Not that I wouldn't like FreeBSD to be the > most popular platform around, but if it has to become Windows - or > even Linux - to do so, it clearly isn't worth it. I've seen enough > tools go sour in pursuit of market share that I'd rather not see a > single change that sacrifices quality for market share. > There's an answer for those who want FreeBSD and "professional" support, testing, etc.: BSD/OS. Short of folks stepping up and volunteering to certify -STABLE on a given configuration (and of course, that's all that could be certified, complicated hardware and software interactions being, well, complicated), that's the best you're going to do. I'm just thinking out loud here; none of what follows should be read as "Somebody *should* do this." By way of background, I worked on the SVR 4.2 MIPS port back in 1992, and was involved in some detail with what is done to verify the quality of a commercial UNIX operating system release. I've worked in the commercial software field ever since, including for the world's major source of telecomm software, and I've lived firsthand the CMM Level 5 lifestyle. I like FreeBSD, and if things continue as they have been, I'll continue using it, tracking the list and cvsup'ing at what appear to be opportune times, tar-ing off my last good build beforehand, and saving my last known good kernels. I am, to my great chagrin, NOT an experienced kernel hacker, and I haven't spent much time in the depths of libc (apart from the SYSV rtld code). Almost all of my experience is in user-level code. That said: I don't have the time to write an entire "BVS" ("BSD Verification Suite"), nor to keep it up-to-date; however, I'd be willing to contribute (and maintain) pieces here and there if a test framework and/or harness (read: API/coding convention) were put into place. There's DejaGNU, but it suffers from the GPL. eTET might be a possibility. I'll be happy to investigate this in my (limited) spare time if Jordan (or whomever else) is willing to help me find a place to put it (be kind! :-). Ideally, the authors of a given piece of FreeBSD would write and maintain the code that tested their piece, and would add tests to reproduce bugs as they attacked those bugs. Inevitably, some parts of the test suite would lag behind, and would emit spurious failure reports. The code freeze on FreeBSD proper prior to a release might be a good time to update those parts of the test suite. Once an (up-to-date) test suite is in place, regression will help to verify that -STABLE really is stable--but again, only on the platform and for the configuration on which the test suite is run. A list of volunteers could submit their results leading up to a release, and that list could be posted ("FreeBSD m.n has been verified to run on such-and-so hardware with such-and-so configuration; deviate at your own risk...."). A similar service could be provided (again by volunteers) for given snapshots of -STABLE, and for testing of binary patches. Tracking of the rates of bugs of varying severities is as simple as a cron job firing off a script, but someone has to have the time to write it. For commercial purposes, aging of bugs could also be tracked, although, given that this is a volunteer effort, that might put undue pressure on committers, and might make them quit if people hound them ceaselessly to do more than they have time to do. (Heck, I have bugs in my own for-pay job that are older than I want them to be, yet no one there would remotely consider characterizing me as a slacker.) OK, no more half-baked ramblings (for now). -- Chris BeHanna Software Engineer (Remove "bogus" before responding.) behanna@bogus.zbzoom.net I was raised by a pack of wild corn dogs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 18:41:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.hk.outblaze.com (smtp1.hk.outblaze.com [202.77.223.49]) by hub.freebsd.org (Postfix) with SMTP id 1653937B405 for ; Sun, 24 Jun 2001 18:41:40 -0700 (PDT) (envelope-from yusufg@outblaze.com) Received: (qmail 10744 invoked from network); 25 Jun 2001 01:41:27 -0000 Received: from unknown (HELO yusufg.portal2.com) (202.77.181.217) by smtp1.hk.outblaze.com with SMTP; 25 Jun 2001 01:41:27 -0000 Received: (qmail 26586 invoked by uid 500); 25 Jun 2001 01:48:01 -0000 Date: Mon, 25 Jun 2001 09:48:01 +0800 From: Yusuf Goolamabbas To: freebsd-stable@freebsd.org Subject: Termcap definitions for rxvt Message-ID: <20010625094801.A26548@outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Recently I upgraded my desktop box to Redhat 7.1 and it comes along with rxvt 2.7.5 [don't remember what RH 7.0 has, I'll check on another box when I get back to office]. rxvt sets the TERM environment variable to "rxvt". When I ssh into a FreeBSD box, I am unable to use any ncurses applications since that termcap entry isn't there. If I change my TERM to "xterm", everything works as expected I see ncurses 5.1 in /usr/src/contrib/ncurses but don't think the termcap/terminfo definitions get installed into the system or have I missed something. Would it be possible to add termcap entries from the ncurses installtion into the stock FreeBSD tree ? Regards, Yusuf -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 19:19:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gateway.dignus.com (sdsl-66-80-58-206.dsl.lax.megapath.net [66.80.58.206]) by hub.freebsd.org (Postfix) with ESMTP id 43DAD37B406 for ; Sun, 24 Jun 2001 19:19:09 -0700 (PDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by gateway.dignus.com (8.11.3/8.11.3) id f5P2J8r00678 for freebsd-stable@freebsd.org; Sun, 24 Jun 2001 22:19:08 -0400 (EDT) (envelope-from rivers) Date: Sun, 24 Jun 2001 22:19:08 -0400 (EDT) From: Thomas David Rivers Message-Id: <200106250219.f5P2J8r00678@gateway.dignus.com> To: freebsd-stable@freebsd.org Subject: Sound (AC'97) too fast??? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've got an MSI i815-based motherboard... thus, I'm using an AC97 sound interface. I walked through the archives and found the following reference: > > For the i815E motherboard, you can try the ICH audio driver > > at http://www.katsurajima.seya.yokohama.jp/ich/ Which I delightedly grabbed and installed, etc... Now, however, when I cat a .au file (which worked great on my previous SoundBlaster setup) - it's quite obviously *way* too fast (like a cassette tape running amok.) xanim suffers from the same "too fast" symptoms (I've got a Honda promotional quick-time clip I use to test this.) It reports: XAnim Rev 2.80.2 BETA by Mark Podlipec Copyright (C) 1991-2000. All Rights Reser ved Linux_Audio: err setting freq 15bb This is with a 4.3-RELEASE system with only the `ich.c' driver added.. from dmesg: pcm0: port 0xbc00-0xbc3f,0xb800-0xb8ff irq 9 at devi ce 31.5 on pci0 I can supply the .au file and/or the Honda promo to anyone interested... But - can anyone let me know how to reign this beastie in? - Thanks! - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 19:28:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gateway.dignus.com (sdsl-66-80-58-206.dsl.lax.megapath.net [66.80.58.206]) by hub.freebsd.org (Postfix) with ESMTP id F335637B422 for ; Sun, 24 Jun 2001 19:28:47 -0700 (PDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by gateway.dignus.com (8.11.3/8.11.3) id f5P2SjG00699; Sun, 24 Jun 2001 22:28:45 -0400 (EDT) (envelope-from rivers) Date: Sun, 24 Jun 2001 22:28:45 -0400 (EDT) From: Thomas David Rivers Message-Id: <200106250228.f5P2SjG00699@gateway.dignus.com> To: freebsd-stable@FreeBSD.ORG, rivers@dignus.com Subject: Re: Sound (AC'97) too fast??? In-Reply-To: <200106250219.f5P2J8r00678@gateway.dignus.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just a reply to add some more information - here's what boot -v says: pcm0: port 0xbc00-0xbc3f,0xb800-0xb8ff irq 9 at devi ce 31.5 on pci0 pcm0: ac97 codec id 0x83847608 (SigmaTel STAC9708) pcm0: ac97 codec features 18 bit DAC, 18 bit ADC, 5 bit master volume, SigmaTel 3D Enhancement pcm0: ac97 primary codec extended features surround DAC pcm: setmap 32000, 10000; 0xcbfcf000 -> 32000 pcm0: setmap(0x42000, 0x100) pcm0: Play codec support rate(Hz): 48000 pcm: setmap 52000, 10000; 0xcbfef000 -> 52000 pcm0: setmap(0x62000, 0x100) pcm0: Record codec support rate(Hz): 48000 which, I take it would mean that pcm0 only supports a 48000 play rate? - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 21:15:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from web14703.mail.yahoo.com (web14703.mail.yahoo.com [216.136.224.120]) by hub.freebsd.org (Postfix) with SMTP id 5860F37B405 for ; Sun, 24 Jun 2001 21:15:30 -0700 (PDT) (envelope-from hackr_d@yahoo.com) Message-ID: <20010625041530.43128.qmail@web14703.mail.yahoo.com> Received: from [63.67.120.228] by web14703.mail.yahoo.com; Sun, 24 Jun 2001 21:15:30 PDT Date: Sun, 24 Jun 2001 21:15:30 -0700 (PDT) From: Donn Miller Subject: RE: Staying *really stable* in FreeBSD To: Chris BeHanna , FreeBSD-Stable In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- Chris BeHanna wrote: > That's not true. When I still had only a dialup connection, I'd > fire up cvsup, go to bed, and then start my buildworld in the > morning. > It worked just fine. Actually, it's much easier than this. All you have to do is cd /usr/src make update buildworld And in the morning, do make installworld. :) See, "make update" does the cvsup for you. -Donn __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 21:43:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 710B937B401 for ; Sun, 24 Jun 2001 21:43:18 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15EODV-0000f8-00 for ; Mon, 25 Jun 2001 16:43:17 +1200 Date: Mon, 25 Jun 2001 16:43:17 +1200 (NZST) From: Juha Saarinen To: Subject: Still getting "Checksum mismatch" etc. Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I don't suppose anyone's got a fix for the below ugliness...? src/contrib/libpam/libpam_misc/misc_conv.c: Checksum mismatch -- will transfer entire file Edit src/contrib/libpam/libpam_misc/xstrdup.c Add delta 1.2.6.1 2001.06.07.09.07.35 markm Add delta 1.2.6.2 2001.06.11.15.28.15 markm src/contrib/libpam/libpam_misc/xstrdup.c: Checksum mismatch -- will transfer entire file Edit src/contrib/libpam/modules/pam_deny/Makefile Add delta 1.3.4.1 2001.06.07.09.07.39 markm Add delta 1.3.4.2 2001.06.11.15.28.17 markm src/contrib/libpam/modules/pam_deny/Makefile: Cannot get edited text: "d" edit command specifies line past end of base delta -- will transfer entire file Edit src/contrib/libpam/modules/pam_deny/pam_deny.c Add delta 1.3.4.1 2001.06.07.09.07.39 markm Add delta 1.3.4.2 2001.06.11.15.28.17 markm src/contrib/libpam/modules/pam_deny/pam_deny.c: Checksum mismatch -- will transfer entire file Edit src/contrib/libpam/modules/pam_permit/Makefile Add delta 1.3.4.1 2001.06.07.09.07.47 markm Add delta 1.3.4.2 2001.06.11.15.28.23 markm src/contrib/libpam/modules/pam_permit/Makefile: Cannot get edited text: "d" edit command specifies line past end of base delta -- will transfer entire file Edit src/contrib/libpam/modules/pam_permit/pam_permit.c Add delta 1.3.4.1 2001.06.07.09.07.47 markm Add delta 1.3.4.2 2001.06.11.15.28.23 markm src/contrib/libpam/modules/pam_permit/pam_permit.c: Checksum mismatch -- will transfer entire file -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 22:32:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 38E6D37B405 for ; Sun, 24 Jun 2001 22:32:30 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id IML23774; Mon, 25 Jun 2001 08:32:20 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.4/8.11.4) id f5P5Meo00783; Mon, 25 Jun 2001 08:22:40 +0300 (EEST) (envelope-from netch) Date: Mon, 25 Jun 2001 08:22:40 +0300 From: Valentin Nechayev To: Dimuthu Bandara Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Kernel Error Message Message-ID: <20010625082240.A707@iv.nn.kiev.ua> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from dimuthu@hotmail.com on Sun, Jun 24, 2001 at 10:11:11PM +0000 X-42: On Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sun, Jun 24, 2001 at 22:11:11, dimuthu (Dimuthu Bandara) wrote about "Kernel Error Message": > Can Somebody explain me why I get this error? Bad disk, or bad cables, or cables unproperly attached, or bad controller, or nonstandard memory bug, or neutrino stream... Most probably, bad block on disk. > Jun 25 03:08:43 bs /kernel: (da1:ahc0:0:2:0): SCB 0x10 - timed out in > Data-in phase, SEQADDR == 0x87 /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 24 23:36:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c576194-a.saltlk1.ut.home.com (c576194-a.saltlk1.ut.home.com [65.5.60.246]) by hub.freebsd.org (Postfix) with SMTP id 7BACB37B405 for ; Sun, 24 Jun 2001 23:36:44 -0700 (PDT) (envelope-from mupi@mknet.org) Received: (qmail 85754 invoked from network); 25 Jun 2001 06:36:44 -0000 Received: from localhost (HELO mukappa.home.com) (ovsjiv@127.0.0.1) by localhost with SMTP; 25 Jun 2001 06:36:44 -0000 From: Mike Porter Reply-To: mupi@Mknet.org To: Chris BeHanna , FreeBSD-Stable Subject: Re: Staying *really stable* in FreeBSD Date: Mon, 25 Jun 2001 00:36:44 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="US-ASCII" References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01062500364404.80326@mukappa.home.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday 24 June 2001 19:20, Chris BeHanna wrote: Having recently stumbled across a library copy of "The Software Conspiracy" (if you are a contributor, I would have to urge you in the strongest possible terms to get your hands on a copy of that book and read it, if you haven't already....it contains a lot of pretty valuable information IMHO for the "rest" of us, too....). I really really like the idea of CMM level 5 stuff, but I am not sure it is entirely practical in a volunteer situation, as there are no "managers" to track the paperwork side, and keeping tabs on stuff as described below would be pretty hideous. That said, I would imagine that there are a number of people like me, who have a vague understanding of the basic ideas, but not much practical experience, and worse, very little time to learn. I can keep my system running smoothly, and pretty much self handle most any issue that arises (with the help of the handbook and/or brute forcing my way logically through the problem), but I have no real desire to penetrate much deeper than what I need to know for troubleshooting and fixing stuff ('man ....' <(}:). However, the idea of some consistent procedures for testing, bug fixing, estimating project completion dates, and a way to document and track such activity is extremely appealing, and the sort of thing that I could do easily. I have a hard time believing on a list this size that I am the only one in that situation. It would be most amusing to see the M$ guys eat thier shorts trying to explain how "open source" (did somebody say "potentially viral software"?? damn, I must be hearing things again....) software produced by volunteers can be CMM 5 certified, but their expensive fancy whatever OS + service pack of the hour can't.... The balance would have to be very carefully drawn however, as the people such as myself who might volunteer in these positions would be doing functions traditionally carried out by "Management" in CMM enterprises, I would certainly not want to be seen that way (how can yuo "manage" a volunteer anyway, really?) I guess if we take the ideas expressed byt he author of "the software consipiracy" to their logical step, what we would wind up with is three groups of volunteers: the "genius hackers" working on new features and stuff in current, the "army of 'average' programmers" working primarily on bug fixes, fleshing out the ideas proposed by the "hacker" core, and the "invisibles", tracking the progress of the two groups, perhaps assigning projects to the "average" group based on past experience with that persons work (ie how many bugs/line of code, how accurate time estimates are, etc). If he is right, such a structured environment would produce better code, faster, and allow more people to participate. I guess in function the current system isn't too different from this, with committers and "core" group assigning projects and doing a lot of the "dream" work in current ( and though I run stable not current, -stable was at some point in the past a current, too). The biggest difference would be the addition of specific documentation procedures to track stuff in a more concrete manner. Or am I missing something here? If this scenario were to be implemented, then the "invisibles" would have a pretty good grasp at any given time of the actual relative stability of stable (and current, too for that matter), although of course, as mentioned previously in this thread complex software and hardware ineteractions can be, well, complex, and the only guarantee of software reliability would be to actually test on the same hardware. (even then, such minor details as a flakey few bits in a SDRAM chip could cause wierd things to happen on one machine that don't happen on another, but those sorts of things, in general, are becoming less frequent than they used to be. ( i guess there may never be a cure for the "it works OK in THIS PCI/DIMM slot, but if I move it to THAT slot, it fails. But this OTHER card works OK in either slot....but hey we can dream can't we). Some purely theoretical side effects of this idea would be that 1) the code freeze at -RELEASE could most likely be shortened (if there are fewer bugs to start with, there is less need for testing, right?) and 2) spinning off an interim release at any given point (or traking stable) becomes much less risky. and 3) the people in the "invisibles" category would know about bugs pretty quickly in most cases and would be good people to contact if you were unsure about the state of the code at any given arbitrary point in time. And cna't CVS track to a specific date, anyway, so you could "roll back" to a more stable period? as a side effect of 2) and 3) it becomes more practical to attempt binary releases (though no guarantee, look at sysinstalls success rate installing binaries compared to the ports trees....face it, FreeBSD as an OS is pretty much designed to be built from scratch to update it; if you want binary patches and the like, go to BSDi or somebody. But it occurs to me that if we decrease BSDI's workload, we just might find additional funding, too, and that wouldn't be a bad thing, would it? Speaking of half-baked ramblings, I better stop now... mike > > I'm just thinking out loud here; none of what follows should be > read as "Somebody *should* do this." By way of background, I worked > on the SVR 4.2 MIPS port back in 1992, and was involved in some detail > with what is done to verify the quality of a commercial UNIX operating > system release. I've worked in the commercial software field ever > since, including for the world's major source of telecomm software, > and I've lived firsthand the CMM Level 5 lifestyle. I like FreeBSD, > and if things continue as they have been, I'll continue using it, > tracking the list and cvsup'ing at what appear to be opportune times, > tar-ing off my last good build beforehand, and saving my last known > good kernels. I am, to my great chagrin, NOT an experienced kernel > hacker, and I haven't spent much time in the depths of libc (apart > from the SYSV rtld code). Almost all of my experience is in > user-level code. > > That said: > > I don't have the time to write an entire "BVS" ("BSD Verification > Suite"), nor to keep it up-to-date; however, I'd be willing to > contribute (and maintain) pieces here and there if a test framework > and/or harness (read: API/coding convention) were put into place. > There's DejaGNU, but it suffers from the GPL. eTET might be a > possibility. I'll be happy to investigate this in my (limited) spare > time if Jordan (or whomever else) is willing to help me find a place > to put it (be kind! :-). > > Ideally, the authors of a given piece of FreeBSD would write and > maintain the code that tested their piece, and would add tests to > reproduce bugs as they attacked those bugs. Inevitably, some parts of > the test suite would lag behind, and would emit spurious failure > reports. The code freeze on FreeBSD proper prior to a release might > be a good time to update those parts of the test suite. > > Once an (up-to-date) test suite is in place, regression will help > to verify that -STABLE really is stable--but again, only on the > platform and for the configuration on which the test suite is run. A > list of volunteers could submit their results leading up to a release, > and that list could be posted ("FreeBSD m.n has been verified to run > on such-and-so hardware with such-and-so configuration; deviate at > your own risk...."). > > A similar service could be provided (again by volunteers) for > given snapshots of -STABLE, and for testing of binary patches. > > Tracking of the rates of bugs of varying severities is as simple > as a cron job firing off a script, but someone has to have the time to > write it. For commercial purposes, aging of bugs could also be > tracked, although, given that this is a volunteer effort, that might > put undue pressure on committers, and might make them quit if people > hound them ceaselessly to do more than they have time to do. (Heck, I > have bugs in my own for-pay job that are older than I want them to > be, yet no one there would remotely consider characterizing me as a > slacker.) > > OK, no more half-baked ramblings (for now). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 0:57:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sbtx.tmn.ru (sbtx.tmn.ru [212.76.160.49]) by hub.freebsd.org (Postfix) with ESMTP id EAD8D37B406 for ; Mon, 25 Jun 2001 00:57:34 -0700 (PDT) (envelope-from serg@sbtx.tmn.ru) Received: from sv.tech.sibitex.tmn.ru (sv.tech.sibitex.tmn.ru [212.76.160.59]) by sbtx.tmn.ru (8.11.3/8.11.3) with ESMTP id f5P7vQI09705; Mon, 25 Jun 2001 13:57:27 +0600 (YEKST) (envelope-from serg@sbtx.tmn.ru) Received: (from serg@localhost) by sv.tech.sibitex.tmn.ru (8.11.4/8.11.4) id f5P7vNp83106; Mon, 25 Jun 2001 13:57:23 +0600 (YEKST) (envelope-from serg) Date: Mon, 25 Jun 2001 13:57:23 +0600 From: "Sergey N. Voronkov" To: Evren Yurtesen Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Kerberos: No default realm defined for Kerberos! Message-ID: <20010625135723.A83063@sv.tech.sibitex.tmn.ru> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from yurtesen@ispro.net.tr on Sat, Jun 23, 2001 at 09:39:30PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Jun 23, 2001 at 09:39:30PM +0300, Evren Yurtesen wrote: > Hi > It is funny but when I make a telnet connection to my Cisco router I > started to get this message only from a machine I have upgraded recently > to stable recently! > > Kerberos: No default realm defined for Kerberos! > > AND It only happens when I connect to Cisco routers and not when I telnet > to my switch or to my smtp server. > > >From all other machines everything is fine. > > Why is it so? > Some additional features of telnet protocol are now defaults to each session (Don't know wath was a reason to do that 8-( ). One of it is so named "autologin". One way to fix: echo default unset autologin >> ~/.telnetrc Second one - use 'telnet -K somehost.somenet'. Bye, Serg N. Voronkov. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 1:39:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail15.bigmailbox.com (mail15.bigmailbox.com [209.132.220.46]) by hub.freebsd.org (Postfix) with ESMTP id 67F5E37B406 for ; Mon, 25 Jun 2001 01:39:17 -0700 (PDT) (envelope-from mujahidin@egypt.net) Received: œby mail15.bigmailbox.com (8.8.7/8.8.7) id BAA29241; Mon, 25 Jun 2001 01:39:17 -0700 Date: Mon, 25 Jun 2001 01:39:17 -0700 Message-Id: <200106250839.BAA29241@mail15.bigmailbox.com> Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary X-Mailer: MIME-tools 4.104 (Entity 4.116) Mime-Version: 1.0 X-Originating-Ip: [212.116.158.36] From: "Cheffo Izroda" To: stable@freebsd.org Subject: CD-RW at ata1-master using PIO4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a CD-RW (TEAC). Someone to know is it posible to use cdrecord/mkisofs on it or must be SCSI dev ? Is there any program that can write cd blanks with this drive ? -= Cheffo =- ------------------------------------------------------------ ------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 1:52:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from r220-1.rz.RWTH-Aachen.DE (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by hub.freebsd.org (Postfix) with ESMTP id 2568D37B401 for ; Mon, 25 Jun 2001 01:52:10 -0700 (PDT) (envelope-from stolz@I2.Informatik.RWTH-Aachen.DE) Received: from r220-1.rz.RWTH-Aachen.DE (relay2.RWTH-Aachen.DE [134.130.3.1]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3-2) with ESMTP id f5P8q8700316; Mon, 25 Jun 2001 10:52:08 +0200 (MEST) Received: from hyperion.informatik.rwth-aachen.de (hyperion.Informatik.RWTH-Aachen.DE [137.226.112.212]) by r220-1.rz.RWTH-Aachen.DE (8.10.1/8.11.3/4) with ESMTP id f5P8q7W00307; Mon, 25 Jun 2001 10:52:07 +0200 (MEST) Received: from agamemnon.informatik.rwth-aachen.de (agamemnon.Informatik.RWTH-Aachen.DE [137.226.194.74]) by hyperion.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1/2) with ESMTP id KAA02725; Mon, 25 Jun 2001 10:52:03 +0200 (MET DST) Received: (from stolz@localhost) by agamemnon.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1-gb-2) id KAA00907; Mon, 25 Jun 2001 10:52:06 +0200 (MET DST) Date: Mon, 25 Jun 2001 10:52:05 +0200 From: Volker Stolz To: mujahidin@egypt.net, stable@FreeBSD.ORG Subject: Re: CD-RW at ata1-master using PIO4 Message-ID: <20010625105205.A902@i2.informatik.rwth-aachen.de> References: <200106250839.BAA29241@mail15.bigmailbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.17i In-Reply-To: <200106250839.BAA29241@mail15.bigmailbox.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In local.freebsd-stable, you wrote: > I have a CD-RW (TEAC). Someone to know is it posible to use > cdrecord/mkisofs on it or must be SCSI dev ? cdrecord is only for SCSI on FreeBSD. Use /usr/sbin/burncd. You may find /usr/share/examples/worm/makecdfs.sh helpful, too. > Is there any program that can write cd blanks with this drive ? You mean blanking? 'burncd' can do this, too. -- Abstrakte Syntaxträume. Volker Stolz * stolz@i2.informatik.rwth-aachen.de * PGP + S/MIME To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 2: 4:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 8C22F37B401; Mon, 25 Jun 2001 02:04:21 -0700 (PDT) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f5P93bH24022; Mon, 25 Jun 2001 12:03:37 +0300 (EEST) (envelope-from ru) Date: Mon, 25 Jun 2001 12:03:37 +0300 From: Ruslan Ermilov To: Valentin Nechayev Cc: Stephen Montgomery-Smith , freebsd-stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems with md5 -p Message-ID: <20010625120337.B22256@sunbay.com> Mail-Followup-To: Valentin Nechayev , Stephen Montgomery-Smith , freebsd-stable@FreeBSD.ORG, current@FreeBSD.ORG References: <3B35F852.2290E18F@math.missouri.edu> <20010624194339.A717@iv.nn.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010624194339.A717@iv.nn.kiev.ua>; from netch@iv.nn.kiev.ua on Sun, Jun 24, 2001 at 07:43:40PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jun 24, 2001 at 07:43:40PM +0300, Valentin Nechayev wrote: > --- md5.c.orig Mon Jun 4 00:38:02 2001 > +++ md5.c Sun Jun 24 19:37:13 2001 > @@ -65,7 +65,7 @@ > switch (ch) { > case 'p': > MDFilter(1); > - break; > + exit(0); > case 'q': > qflag = 1; > break; > > This avoids determination of other options, but this does not conflict > directly with man page. > Yes it *does*. From the manpage: : The following four options may be used in any combination ... ^^^^^^^^^^^^^^^^^^ I'm not sure how useful it is though. :-) I'm going to merge OpenBSD refinements made to md5(1) sometime this week. This would also mean that most of the md5(1) options will be made mutually exclusive. This also corresponds to the NetBSD behavior. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 3: 6:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93]) by hub.freebsd.org (Postfix) with ESMTP id 4FBFF37B405 for ; Mon, 25 Jun 2001 03:06:29 -0700 (PDT) (envelope-from rasputin@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97] ident=root) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #6) id 15ETGG-000LWn-00 for stable@freebsd.org; Mon, 25 Jun 2001 11:06:28 +0100 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.3/8.11.1) id f5PA6K044426 for stable@freebsd.org; Mon, 25 Jun 2001 11:06:20 +0100 (BST) (envelope-from rasputin) Date: Mon, 25 Jun 2001 11:06:20 +0100 From: Rasputin To: stable@freebsd.org Subject: Re: XFree86-4.1.0+mga+dri+FreeBSD-4.3-stable == hang Message-ID: <20010625110619.A44348@dogma.freebsd-uk.eu.org> Reply-To: Rasputin References: <200106140436.OAA20451@hadrian.staff.apnic.net> <20010614141859.B67187@node7.cluster.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010614141859.B67187@node7.cluster.srrc.usda.gov>; from gjohnson@srrc.ars.usda.gov on Thu, Jun 14, 2001 at 02:18:59PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Glenn Johnson [010614 20:27]: > On Thu, Jun 14, 2001 at 02:36:00PM -0500, ggm@apnic.net wrote: > > > Say I have a Matrox G400, on FreeBSD-4.3-stable, I have installed the > > FreeBSD 'port' of XFree86-4.1.0 and I try to enable dri, and it hangs. > > The DRI stuff does not work with XF86-4.1 and FreeBSD. > > > Do I try to foist blame on XFree86, or do I try to foist blame on > > FreeBSD? > > > > I realize this isn't a well formed bug report, I'm holding off on > > that, until I understand who wants to be put in the frame. > > > > My suspicion is that Its FreeBSD, because it relates to their > > kernel agp.ko module (which I am guessing is required to support > > DRI->agp->G400 interrelationships somehow. > > The agp.ko module is built with the FreeBSD sources and as far as I know > works fine for most motherboard chip sets. It is required for DRI but > not sufficient. The other required kernel modules for DRI with a Matrox > G400 are the mga.ko and the drm.ko modules. These are [optionally] > built as part of XFree86. The problem is that nobody is keeping the BSD > branch of the DRI source tree up to date. If you go to http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/XFree86-4/?only_with_tag=RELEASE_4_3_0 you'l get a version of the port that *should* build the dri modules you need. You still need to preload agp.ko and mga.ko from /boot/loader.conf, and load the dri module in XF86Config , but you should be OK. Unlike me ,since that port doesn't appear to build tdfx_dri.so ......... If anyone's got DRi on a Voodoo 3 working, please let me know. Ta! -- Moon, n.: 1. A celestial object whose phase is very important to hackers. See PHASE OF THE MOON. 2. Dave Moon (MOON@MC). Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 4: 0:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 07B3637B406 for ; Mon, 25 Jun 2001 04:00:15 -0700 (PDT) (envelope-from postmaster@plab.ku.dk) Received: (from root@localhost) by plab.ku.dk (8.11.3/8.9.3) id f5PB0Aw91601 for freebsd-stable@freebsd.org.AVP; Mon, 25 Jun 2001 13:00:10 +0200 (CEST) (envelope-from postmaster@plab.ku.dk) Received: from raven.plab.ku.dk (raven.plab.ku.dk [130.225.105.67]) by plab.ku.dk (8.11.3/8.9.3) with ESMTP id f5PB09991593 for ; Mon, 25 Jun 2001 13:00:09 +0200 (CEST) (envelope-from postmaster@plab.ku.dk) In-Reply-To: Joe Kelsey's message of "Sat, 23 Jun 2001 16:52:53 -0700" Subject: Re: Staying *really stable* in FreeBSD Content-Transfer-Encoding: 8bit References: <15155.29806.145760.832648@guru.mired.org> <4.3.2.7.2.20010623150807.034a09a0@24.0.95.106> <15157.11221.593513.478892@zircon.zircon.seattle.wa.us> To: freebsd-stable@freebsd.org From: Dmitry Karasik Keywords: 2001334874 X-Comment-To: Joe Kelsey Content-Type: text/plain; charset="koi8-r" Lines: 18 Mime-Version: 1.0 Date: 25 Jun 2001 12:58:37 +0200 X-Mailer: Mail::Mailer[v1.18] Net::SMTP[v2.13] Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Joe! On 23 Jun 01 at 16:52, "Joe" (Joe Kelsey) wrote: Joe> Either get newer hardware to work with or go through ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I admire that sort of advice. Really. Joe>the upgrade based on your subscription disks. -- Sincerely, Dmitry --- www.karasik.eu.org --- Life ain't fair, but the root password helps. - BOFH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 4:28:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 69A5037B407 for ; Mon, 25 Jun 2001 04:28:46 -0700 (PDT) (envelope-from mike@sentex.net) Received: (from root@localhost) by cage.simianscience.com (8.11.4/8.11.2) id f5PBSjP70104; Mon, 25 Jun 2001 07:28:45 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.4/8.11.2av) with ESMTP id f5PBSaA70095; Mon, 25 Jun 2001 07:28:36 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010625072756.031a6118@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 25 Jun 2001 07:28:35 -0400 To: Juha Saarinen , From: Mike Tancsa Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Perhaps its particular server your are cvsuping from. Which one is it ? ---Mike At 04:43 PM 6/25/2001 +1200, Juha Saarinen wrote: >I don't suppose anyone's got a fix for the below ugliness...? > > >src/contrib/libpam/libpam_misc/misc_conv.c: Checksum mismatch -- will >transfer entire file > Edit src/contrib/libpam/libpam_misc/xstrdup.c > Add delta 1.2.6.1 2001.06.07.09.07.35 markm > Add delta 1.2.6.2 2001.06.11.15.28.15 markm >src/contrib/libpam/libpam_misc/xstrdup.c: Checksum mismatch -- will >transfer entire file > Edit src/contrib/libpam/modules/pam_deny/Makefile > Add delta 1.3.4.1 2001.06.07.09.07.39 markm > Add delta 1.3.4.2 2001.06.11.15.28.17 markm >src/contrib/libpam/modules/pam_deny/Makefile: Cannot get edited text: "d" >edit command specifies line past end of base delta -- will transfer entire >file > Edit src/contrib/libpam/modules/pam_deny/pam_deny.c > Add delta 1.3.4.1 2001.06.07.09.07.39 markm > Add delta 1.3.4.2 2001.06.11.15.28.17 markm >src/contrib/libpam/modules/pam_deny/pam_deny.c: Checksum mismatch -- will >transfer entire file > Edit src/contrib/libpam/modules/pam_permit/Makefile > Add delta 1.3.4.1 2001.06.07.09.07.47 markm > Add delta 1.3.4.2 2001.06.11.15.28.23 markm >src/contrib/libpam/modules/pam_permit/Makefile: Cannot get edited text: >"d" edit command specifies line past end of base delta -- will transfer >entire file > Edit src/contrib/libpam/modules/pam_permit/pam_permit.c > Add delta 1.3.4.1 2001.06.07.09.07.47 markm > Add delta 1.3.4.2 2001.06.11.15.28.23 markm >src/contrib/libpam/modules/pam_permit/pam_permit.c: Checksum mismatch -- >will transfer entire file > > >-- >Regards, > > >Juha > >PGP fingerprint: >B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 4:35:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id BED2F37B407 for ; Mon, 25 Jun 2001 04:35:39 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15EUeW-0000rY-00; Mon, 25 Jun 2001 23:35:36 +1200 Date: Mon, 25 Jun 2001 23:35:36 +1200 (NZST) From: Juha Saarinen To: Mike Tancsa Cc: "freebsd-stable@freebsd.org" Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: <4.2.2.20010625072756.031a6118@192.168.0.12> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG cvsup.au.freebsd.org -- I'll try the NZ one to see if it makes a difference. Thanks. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 5:30:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cvis21.Marconicomms.com (cvis21.marconicomms.com [195.99.244.53]) by hub.freebsd.org (Postfix) with ESMTP id C32B037B401 for ; Mon, 25 Jun 2001 05:30:56 -0700 (PDT) (envelope-from sje2bk@marconi.com) Received: from cvis01.gpt.co.uk (unverified) by cvis21.Marconicomms.com (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Mon, 25 Jun 2001 13:30:50 +0100 Received: from bkrzu6.de.marconicomms.com by cvis01.gpt.co.uk with ESMTP (8.8.8+Sun/cvms-32) id NAA10110; Mon, 25 Jun 2001 13:30:51 +0100 (BST) Received: from bk4957.de.marconicomms.com (bk4957.de.marconicomms.com [172.28.39.232]) by bkrzu6.de.marconicomms.com (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id NAA28286; Mon, 25 Jun 2001 13:36:34 +0200 (METDST) Received: (from sje2bk@localhost) by bk4957.de.marconicomms.com (8.11.1/8.11.1) id f5PBaXN00653; Mon, 25 Jun 2001 13:36:33 +0200 (CEST) (envelope-from sje2bk) Date: Mon, 25 Jun 2001 13:36:33 +0200 From: Jens Schweikhardt To: yusufg@outblaze.com Cc: freebsd-stable@freebsd.org Subject: Termcap definitions for rxvt Message-ID: <20010625133633.B289@bk4957.de.marconicomms.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yusuf, a few days ago I committed the rxvt termcap from the rxvt sources to -current. It will be MFC'd to -stable during this week. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 6:22:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id 4E19F37B40A for ; Mon, 25 Jun 2001 06:22:08 -0700 (PDT) (envelope-from andy@tecc.co.uk) Received: from southampton [195.217.37.155] by relay.tecc.co.uk with smtp (Exim 1.70 #1) id 15EWJZ-00058E-00; Mon, 25 Jun 2001 14:22:06 +0100 From: "Andy" To: , Cc: Subject: RE: shutdown not completing (more info) Date: Mon, 25 Jun 2001 14:22:06 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: x-mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bad one this. I was on Alt-F1. I repeated process from 4.2->4.3->4.-STABLE. I can no longer recreate the problem. I can assure you what I saw was on Alt-F1, I don't use the other terms available when on console. The way I see it, if I'm on console, I'm in trouble! However, not now being able to reproduce this means I can hardly add further details at this time. Tough one. I know, can't recreate/repeat then usually can't fix. Regards Ak > This is sort of like an "is it plugged in" sanity check, but... > > After issuing 'shutdown now', I believe that you need to go to screen > one (Alt-F1) where you're prompted for which shell to use and then > dropped into single-user. > > If you don't go to screen one, then the machine will have the > appearance of hanging. > > Regards, > Steven > > > 4.2-RELEASE from CDRom, GENERIC kernel > > "shutdown now" works fine. > > > > 4.3-RELEASE from CDRom, GENERIC kernel > > "shutdown now" fails, hangs machine. > > "shutdown now" causes system to fall to single-user mode. > If it reboots, stops it or switches the power off, your 4.2 was broken. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 6:28:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id D855337B405 for ; Mon, 25 Jun 2001 06:28:33 -0700 (PDT) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id GAA17312; Mon, 25 Jun 2001 06:27:46 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda17310; Mon Jun 25 06:27:39 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.4/8.9.1) id f5PDRZM51559; Mon, 25 Jun 2001 06:27:35 -0700 (PDT) Received: from UNKNOWN(10.1.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdL51551; Mon Jun 25 06:27:06 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.4/8.9.1) id f5PDPg641843; Mon, 25 Jun 2001 06:25:42 -0700 (PDT) Message-Id: <200106251325.f5PDPg641843@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdx41839; Mon Jun 25 06:25:25 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Valentin Nechayev Cc: Dimuthu Bandara , freebsd-stable@FreeBSD.ORG Subject: Re: Kernel Error Message In-reply-to: Your message of "Mon, 25 Jun 2001 08:22:40 +0300." <20010625082240.A707@iv.nn.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Jun 2001 06:25:25 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG n message <20010625082240.A707@iv.nn.kiev.ua>, Valentin Nechayev writes: > Sun, Jun 24, 2001 at 22:11:11, dimuthu (Dimuthu Bandara) wrote about "Kernel > Error Message": > > > Can Somebody explain me why I get this error? > > Bad disk, or bad cables, or cables unproperly attached, or bad controller, > or nonstandard memory bug, or neutrino stream... > > Most probably, bad block on disk. I've had this before. Replacing the bad disk solved the problem. > > > Jun 25 03:08:43 bs /kernel: (da1:ahc0:0:2:0): SCB 0x10 - timed out in > > Data-in phase, SEQADDR == 0x87 Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC I To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 7: 6:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105]) by hub.freebsd.org (Postfix) with ESMTP id D0C2037B405 for ; Mon, 25 Jun 2001 07:06:27 -0700 (PDT) (envelope-from khera@kcilink.com) Received: from onceler.kciLink.com (onceler.kciLink.com [216.194.193.106]) by yertle.kciLink.com (Postfix) with ESMTP id 39DEC2E45F for ; Mon, 25 Jun 2001 10:06:26 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.4/8.11.3) id f5PE6QW51405; Mon, 25 Jun 2001 10:06:26 -0400 (EDT) (envelope-from khera@kcilink.com) X-Authentication-Warning: onceler.kciLink.com: khera set sender to khera@kcilink.com using -f To: stable@freebsd.org Subject: Re: shutdown not completing References: From: Vivek Khera Date: 25 Jun 2001 10:06:25 -0400 In-Reply-To: Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "a" == andy writes: a> On doing "shutdown now" with this kernel I go a> to single user mode. a> So, the "shutdown now" problem appears to be a> connected with shutting down processor #1 ?? I have this problem on 4 machines: two SMP and one UP. All Dell poweredge (one dual proc is model 2450, the others are 1550). I don't think it is related to SMP. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 7:11:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kcilink.com [216.194.193.105]) by hub.freebsd.org (Postfix) with ESMTP id 8ED1237B406 for ; Mon, 25 Jun 2001 07:11:43 -0700 (PDT) (envelope-from khera@kcilink.com) Received: from onceler.kciLink.com (onceler.kciLink.com [216.194.193.106]) by yertle.kciLink.com (Postfix) with ESMTP id AA7192E45F for ; Mon, 25 Jun 2001 10:11:40 -0400 (EDT) Received: (from khera@localhost) by onceler.kciLink.com (8.11.4/8.11.3) id f5PEBeY59161; Mon, 25 Jun 2001 10:11:40 -0400 (EDT) (envelope-from khera@kcilink.com) X-Authentication-Warning: onceler.kciLink.com: khera set sender to khera@kcilink.com using -f To: stable@freebsd.org Subject: Re: shutdown not completing (more info) References: From: Vivek Khera Date: 25 Jun 2001 10:11:40 -0400 In-Reply-To: Message-ID: Lines: 21 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "a" == andy writes: >> After issuing 'shutdown now', I believe that you need to go to screen >> one (Alt-F1) where you're prompted for which shell to use and then >> dropped into single-user. >> I've had the same problem with shutdown not completing. Unfortunately, I'm on a serial console, and you can't break to debugger once getty dies (I have a patch for serial console debugger, but installing it is a catch 22 since I have to do it remotely -- I guess I can get a tech to go hit the reset switch...) I'll follow up with debugger details on where it hangs. Luckily I have a spare box to test this on at the production facility. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 7:15:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by hub.freebsd.org (Postfix) with ESMTP id 9308E37B40F for ; Mon, 25 Jun 2001 07:15:40 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id BEF4210F418; Sat, 23 Jun 2001 11:12:11 -0500 (CDT) Date: Sat, 23 Jun 2001 11:12:11 -0500 From: "David W. Chapman Jr." To: stable@freebsd.org Subject: this morning's build Message-ID: <20010623111211.A25162@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.19i X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I cvsuped and tried to build a kernel from this morning. My make world was from last night. Warning: Object directory not changed from original /stripe1/compile/src/lib/libpam/modules/pam_cleartext_pass_ok ===> lib/libpam/modules/pam_deny Warning: Object directory not changed from original /stripe1/compile/src/lib/libpam/modules/pam_deny ===> lib/libpam/modules/pam_opie Warning: Object directory not changed from original /stripe1/compile/src/lib/libpam/modules/pam_opie ===> lib/libpam/modules/pam_permit Warning: Object directory not changed from original /stripe1/compile/src/lib/libpam/modules/pam_permit ===> lib/libpam/modules/pam_radius Warning: Object directory not changed from original /stripe1/compile/src/lib/libpam/modules/pam_radius ===> lib/libpam/modules/pam_skey Warning: Object directory not changed from original /stripe1/compile/src/lib/libpam/modules/pam_skey ===> lib/libpam/modules/pam_ssh Warning: Object directory not changed from original /stripe1/compile/src/lib/libpam/modules/pam_ssh building shared library pam_ssh.so /usr/libexec/elf/ld: cannot find -lssh *** Error code 1 -- David W. Chapman Jr. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 7:22:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by hub.freebsd.org (Postfix) with ESMTP id 43FE037B406 for ; Mon, 25 Jun 2001 07:22:50 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id E3F3110F410; Mon, 25 Jun 2001 09:22:51 -0500 (CDT) Date: Mon, 25 Jun 2001 09:22:51 -0500 From: "David W. Chapman Jr." To: "David W. Chapman Jr." Cc: stable@freebsd.org Subject: Re: this morning's build Message-ID: <20010625092251.B42889@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: "David W. Chapman Jr." , stable@freebsd.org References: <20010623111211.A25162@leviathan.inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010623111211.A25162@leviathan.inethouston.net> User-Agent: Mutt/1.3.19i X-Operating-System: FreeBSD 4.3-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ignore this thread, this was thursday and due to a bad cvsup. I had dns problems that prevented this from going out for a few days. -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 7:25:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtpproxy1.mitre.org (mb-20-100.mitre.org [129.83.20.100]) by hub.freebsd.org (Postfix) with ESMTP id 9EDEA37B409 for ; Mon, 25 Jun 2001 07:25:33 -0700 (PDT) (envelope-from jandrese@mitre.org) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.9.3/8.9.3) with ESMTP id KAA07071; Mon, 25 Jun 2001 10:25:22 -0400 (EDT) Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31]) by smtpsrv1.mitre.org (8.9.3/8.9.3) with ESMTP id KAA12586; Mon, 25 Jun 2001 10:25:20 -0400 (EDT) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub1.mitre.org with SMTP id 6871176; Mon, 25 Jun 2001 10:25:00 -0400 Message-ID: <3B3749D2.81285C93@mitre.org> Date: Mon, 25 Jun 2001 10:25:22 -0400 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Jason Watkins Cc: Stable Subject: Re: Staying *really stable* in FreeBSD References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jason Watkins wrote: > > And this would be different than -stable how? > > >> Then we (paranoid and lazy types) can just cvsup that tag without > >> needing to change from RELENG_X_Y to RELENG_X_Y+1 and RELENG_X+1_0. > > Don't camoflage one problem by providing a solution to another. What you're > really worried about is how stable -stable is. Address that, and things will > be better than managing: > > -its_not_stable_but_we_pretend > -stable > -yet_more_stable > -so_stable_its_more_stale_than_the_cheesewiz_in_my_house [This is slightly paraphrased, I can't remember the exact lines] Mr. Burns: How are my shares of Confederated Slaveholdings? Sycophant Investors: They're...stable. -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 7:32:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (oe19.pav1.hotmail.com [64.4.30.123]) by hub.freebsd.org (Postfix) with ESMTP id A94E137B407; Mon, 25 Jun 2001 07:32:40 -0700 (PDT) (envelope-from karen_zheng21@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 25 Jun 2001 07:32:40 -0700 X-Originating-IP: [216.95.234.119] From: "Karen@hotmail" To: , Subject: RIP not running due to UDPchecksum disabled Date: Mon, 25 Jun 2001 10:37:27 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0021_01C0FD62.D41AEA90" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: X-OriginalArrivalTime: 25 Jun 2001 14:32:40.0363 (UTC) FILETIME=[B01D57B0:01C0FD83] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0021_01C0FD62.D41AEA90 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I've installed GateD 3.6 on FreeBSD 4.2 (PC), I've set the system = variables as follow: sysctl -w net.inet.ip.forwarding =3D1 sysctl -w net.inet.udp.checksum =3D1 the /etc/gated.conf is as follows: kzheng# cat /etc/gated.conf rip yes { nobroadcast ; }; however, when I started GateD with gdc, and made GateD dump core: gdc COREDUMP I found in /var/tmp/gated.core sum message about RIP not running due to = UDPchecksums DISABLED: Target_Build^@RIP^@^@^@^@^@^@^@^@^@^@^@^@^@rip_init: UDP checksums = *DISABLED* in kernel; RIP disab led^@=F2dp^@route^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@= rip_init: is routed or an old copy of gated running? ... I tried several times and couldn't figure out what was going wrong. = Could you help me out of the problem? Thanks a lot. Karen ------=_NextPart_000_0021_01C0FD62.D41AEA90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I've installed GateD 3.6 on FreeBSD 4.2 = (PC), I've=20 set the system variables as follow:
    sysctl -w=20 net.inet.ip.forwarding =3D1
    sysctl -w=20 net.inet.udp.checksum =3D1
the /etc/gated.conf is as follows:
    kzheng# cat=20 /etc/gated.conf
    rip yes=20 {
            = nobroadcast=20 ;
           =20 };
 
however, when I started GateD with gdc, and made GateD dump = core:
    gdc COREDUMP
I found in /var/tmp/gated.core sum message about RIP not running = due to=20 UDPchecksums DISABLED:
Target_Build^@RIP^@^@^@^@^@^@^@^@^@^@^@^@^@rip_init: UDP = checksums=20 *DISABLED* in kernel; RIP=20 disab
led^@=F2dp^@route^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^= @^@^@^@^@rip_init:=20 is routed or an old
 copy of gated running?
...
 
I tried several times and couldn't figure out what was going wrong. = Could=20 you help me out of the problem? Thanks a lot.
 
Karen
------=_NextPart_000_0021_01C0FD62.D41AEA90-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 8:26:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [130.64.1.215]) by hub.freebsd.org (Postfix) with ESMTP id 8F52F37B409 for ; Mon, 25 Jun 2001 08:26:26 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 15EYFt-0007BW-00 for stable@FreeBSD.ORG; Mon, 25 Jun 2001 11:26:25 -0400 Date: Mon, 25 Jun 2001 11:26:25 -0400 From: Peter Radcliffe To: stable@FreeBSD.ORG Subject: pcmcia insert/remove problems recently Message-ID: <20010625112625.B26884@pir.net> Reply-To: stable@freebsd.org Mail-Followup-To: stable@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Fairly recently I've been having more pcmcia problems with -STABLE on my sony Z505HS. At the moment most insert/remove events will work once or twice and after that I either get the machine hanging up for a while and then possibly coming back or just giving me null/null on any pcmcia card :/ I have to reboot to recover this. I've been using the same configuration that I've been using for some time and this used to happen, but only very rarely. Now it is happening very frequently, and given that I'm at USENIX and using wireless a great deal it's gotten very annoying ... P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 8:28:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D00EF37B406 for ; Mon, 25 Jun 2001 08:28:41 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f5PFSZ232242; Mon, 25 Jun 2001 08:28:35 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f5PFSZS86318; Mon, 25 Jun 2001 08:28:35 -0700 (PDT) (envelope-from jdp) Date: Mon, 25 Jun 2001 08:28:35 -0700 (PDT) Message-Id: <200106251528.f5PFSZS86318@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: juha@saarinen.org Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , Juha Saarinen wrote: > I don't suppose anyone's got a fix for the below ugliness...? > > > src/contrib/libpam/libpam_misc/misc_conv.c: Checksum mismatch -- will > transfer entire file > Edit src/contrib/libpam/libpam_misc/xstrdup.c > Add delta 1.2.6.1 2001.06.07.09.07.35 markm > Add delta 1.2.6.2 2001.06.11.15.28.15 markm > src/contrib/libpam/libpam_misc/xstrdup.c: Checksum mismatch -- will > transfer entire file [...] No fix is needed. The message is telling you that CVSup has noticed a problem and is fixing it itself. CVSup _will_not_ give you a bad update unless your underlying hardware (or OS) garbles the data on the way to the disk drive. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 9: 0:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from algol.sdata.de (algol.sdata.de [193.30.133.39]) by hub.freebsd.org (Postfix) with ESMTP id 01A6637B405 for ; Mon, 25 Jun 2001 09:00:25 -0700 (PDT) (envelope-from cs@sdata.de) Received: from sdata.de (vega.sdata.de [193.30.133.36]) by algol.sdata.de (8.11.3/8.11.3) with ESMTP id f5PG0N375587 for ; Mon, 25 Jun 2001 18:00:23 +0200 (CEST) (envelope-from cs@sdata.de) Message-ID: <3B376016.7258B474@sdata.de> Date: Mon, 25 Jun 2001 18:00:22 +0200 From: Christoph Splittgerber X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: indefinite wait buffer ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hallo, found this in the /var/log/messages: iguana /kernel: swap_pager: indefinite wait buffer: device: #ad/0x20001, blkno: 11520, size: 8192 ... and I'm trying to find out what might cause an error like this. Is this a physically bad block on the swap device? Before I start digging into the sources, can somebody point me in the right direction please. Thanks in advance, Christoph To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 10:17:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dargo.talarian.com (dargo.talarian.com [207.5.33.3]) by hub.freebsd.org (Postfix) with ESMTP id 8E45A37B405 for ; Mon, 25 Jun 2001 10:17:28 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Received: from moya.talarian.com (moya.talarian.com [10.4.10.8]) by dargo.talarian.com (Postfix) with ESMTP id D620522B09; Mon, 25 Jun 2001 10:15:08 -0700 (PDT) Received: from beast.talarian.com (beast.talarian.com [10.4.10.6]) by moya.talarian.com (Postfix) with ESMTP id D8CBA131; Mon, 25 Jun 2001 10:17:27 -0700 (PDT) Received: from quack.kfu.com (localhost [::1]) by beast.talarian.com (8.11.3/8.11.3) with ESMTP id f5PHHRP48504; Mon, 25 Jun 2001 10:17:27 -0700 (PDT) (envelope-from nsayer@quack.kfu.com) Message-ID: <3B377227.9000102@quack.kfu.com> Date: Mon, 25 Jun 2001 10:17:27 -0700 From: Nick Sayer User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.3-RELEASE i386; en-US; rv:0.9.1) Gecko/20010613 X-Accept-Language: en-us MIME-Version: 1.0 To: art@pilikia.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD sendmail libmilter References: <200105252131470280.121DDA87@smtp> <200105252133160100.121F354E@smtp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Arthur W. Neilson III wrote: > Recently I downloaded amavis-perl-11 and want to implement it using the miltering > interface. It's not clear to me how to build the sendmail 8.11.3 which is integrated > with FreeBSD 4.3 with libmilter support. You don't. You build sendmail from the ports. There it has options to turn milter on, among other things. The port will direct you to edit /etc/mail/mailer.conf in order to make the installed sendmail the one the system uses by default. Last I heard, the plan was to turn on milter in the base when it's no longer an FFR in sendmail itself. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 12:51:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sneakerz.org (sneakerz.org [216.33.66.254]) by hub.freebsd.org (Postfix) with ESMTP id C065637B407; Mon, 25 Jun 2001 12:51:34 -0700 (PDT) (envelope-from bright@sneakerz.org) Received: by sneakerz.org (Postfix, from userid 1092) id 2984F5D010; Mon, 25 Jun 2001 14:51:24 -0500 (CDT) Date: Mon, 25 Jun 2001 14:51:24 -0500 From: Alfred Perlstein To: freebsd-stable@freebsd.org Cc: dillon@freebsd.org, tegge@freebsd.org Subject: -stable weird panics Message-ID: <20010625145124.D64836@sneakerz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to get some people at Netzero using FreeBSD, actually they're trying to use FreeBSD and I'm trying to get it to stop crashing on them. (see my sys_pipe.c commits) Anyhow, they keep dying on getnewvnode like so: #5 0xc031d9bf in trap (frame={tf_fs = -1070858216, tf_es = -1007878128, tf_ds = -1069809648, tf_edi = 0, tf_esi = -1002983424, tf_ebp = -62104564, tf_isp = -62104632, tf_ebx = 0, tf_edx = -1744880709, tf_ecx = 42, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -1070480145, tf_cs = 8, tf_eflags = 66050, tf_esp = -1003572608, tf_ss = -1071798700}) at ../../i386/i386/trap.c:443 #6 0xc031c4ef in generic_bzero () #7 0xc02ae6af in ffs_vget (mp=0xc425ee00, ino=135970, vpp=0xfc4c5ca0) at ../../ufs/ffs/ffs_vfsops.c:1069 #8 0xc02a376f in ffs_valloc (pvp=0xfb9dcec0, mode=33188, cred=0xc47b1d00, vpp=0xfc4c5ca0) at ../../ufs/ffs/ffs_alloc.c:600 #9 0xc02b628f in ufs_makeinode (mode=33188, dvp=0xfb9dcec0, vpp=0xfc4c5edc, cnp=0xfc4c5ef0) at ../../ufs/ufs/ufs_vnops.c:2088 #10 0xc02b3c00 in ufs_create (ap=0xfc4c5dfc) at ../../ufs/ufs/ufs_vnops.c:190 #11 0xc02b658d in ufs_vnoperate (ap=0xfc4c5dfc) at ../../ufs/ufs/ufs_vnops.c:2373 #12 0xc01e20ac in vn_open (ndp=0xfc4c5ec8, fmode=2562, cmode=420) at vnode_if.h:106 #13 0xc01de2f4 in open (p=0xfc49b2a0, uap=0xfc4c5f80) at ../../kern/vfs_syscalls.c:995 #7 0xc02ae6af in ffs_vget (mp=0xc425ee00, ino=135970, vpp=0xfc4c5ca0) at ../../ufs/ffs/ffs_vfsops.c:1069 1069 error = getnewvnode(VT_UFS, mp, ffs_vnodeop_p, &vp); (kgdb) list 1064 */ 1065 MALLOC(ip, struct inode *, sizeof(struct inode), 1066 ump->um_malloctype, M_WAITOK); 1067 1068 /* Allocate a new vnode/inode. */ 1069 error = getnewvnode(VT_UFS, mp, ffs_vnodeop_p, &vp); 1070 if (error) { 1071 if (ffs_inode_hash_lock < 0) 1072 wakeup(&ffs_inode_hash_lock); 1073 ffs_inode_hash_lock = 0; It really looks like the zalloc() call in getnewvnode() is returning NULL, and instead of bailing getnewvnode() tries to zero a NULL pointer. I'm weirded out that zalloc is failing because I think we've tuned the kernel memory for quite a large pool: options VM_KMEM_SIZE="(400*1024*1024)" options VM_KMEM_SIZE_MAX="(400*1024*1024)" however.. % vmstat -m -M /var/qmail/crash/vmcore.6 Memory Totals: In Use Free Requests 17408K 137K 7909365 % vmstat -z -M /var/qmail/crash/vmcore.6 ZONE used total mem-use PIPE 55 408 8/63K SWAPMETA 0 0 0/0K tcpcb 303 371 160/197K unpcb 4 128 0/8K ripcb 0 21 0/3K tcpcb 0 0 0/0K udpcb 41 84 7/15K socket 354 441 66/82K KNOTE 1 128 0/8K NFSNODE 99464 99480 31082/31087K NFSMOUNT 26 35 13/18K VNODE 105046 105046 19696/19696K NAMEI 2 48 2/48K VMSPACE 97 320 18/60K PROC 101 294 41/119K DP fakepg 0 0 0/0K PV ENTRY 33850 524263 925/14335K MAP ENTRY 1057 2593 49/121K KMAP ENTRY 824 1148 38/53K MAP 7 10 0/1K VM OBJECT 66326 66406 6218/6225K ------------------------------------------ TOTAL 58330/72146K So why is zalloc dying when it looks like only about 90 megs of kernel memory is allocated? Anyhow, I've added a check in getnewvnode to return ENOMEM if zalloc fails, my concern is that other parts of the kernel are going to blow up immediately after that is caught because it looks like the majority of places don't expect zalloc to fail. Any suggestions will be helpful, any requests for more information will happily be attempted. thanks, -Alfred here's another core, this time in getnewvnode called from NFS: (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:469 #1 0xc01af6ef in boot (howto=256) at ../../kern/kern_shutdown.c:309 #2 0xc01afab9 in panic (fmt=0xc0386b6f "page fault") at ../../kern/kern_shutdown.c:556 #3 0xc031e224 in trap_fatal (frame=0xf1b76b90, eva=0) at ../../i386/i386/trap.c:951 #4 0xc031de95 in trap_pfault (frame=0xf1b76b90, usermode=0, eva=0) at ../../i386/i386/trap.c:844 #5 0xc031d9bf in trap (frame={tf_fs = -1070858216, tf_es = -1008140272, tf_ds = -1069809648, tf_edi = 0, tf_esi = -18221184, tf_ebp = -239637504, tf_isp = -239637572, tf_ebx = 0, tf_edx = -1744880709, tf_ecx = 42, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -1070480145, tf_cs = 8, tf_eflags = 66050, tf_esp = -1005287872, tf_ss = -1071798700}) at ../../i386/i386/trap.c:443 #6 0xc031c4ef in generic_bzero () #7 0xc022a09d in nfs_nget (mntp=0xc4225600, fhp=0xc3a32858, fhsize=32, npp=0xf1b76c9c) at ../../nfs/nfs_node.c:145 #8 0xc024faa3 in nfs_lookup (ap=0xf1b76d68) at ../../nfs/nfs_vnops.c:942 #9 0xc01d99c5 in lookup (ndp=0xf1b76ec8) at vnode_if.h:52 #10 0xc01d9503 in namei (ndp=0xf1b76ec8) at ../../kern/vfs_lookup.c:153 #11 0xc01e2173 in vn_open (ndp=0xf1b76ec8, fmode=1, cmode=384) at ../../kern/vfs_vnops.c:137 #12 0xc01de2f4 in open (p=0xf1b19440, uap=0xf1b76f80) at ../../kern/vfs_syscalls.c:995 (kgdb) up #7 0xc022a09d in nfs_nget (mntp=0xc4225600, fhp=0xc3a32858, fhsize=32, npp=0xf1b76c9c) at ../../nfs/nfs_node.c:145 145 error = getnewvnode(VT_NFS, mntp, nfsv2_vnodeop_p, &nvp); (kgdb) list 140 */ 141 np = zalloc(nfsnode_zone); 142 if (np == NULL) 143 error = ENFILE; 144 else 145 error = getnewvnode(VT_NFS, mntp, nfsv2_vnodeop_p, &nvp); 146 if (error) { 147 if (nfs_node_hash_lock < 0) 148 wakeup(&nfs_node_hash_lock); 149 nfs_node_hash_lock = 0; (i thought that zalloc was failing here, but it doesn't seem to be) % vmstat -m -M /var/qmail/crash/vmcore.5 Memory Totals: In Use Free Requests 51586K 1707K 39661043 % vmstat -z -M /var/qmail/crash/vmcore.5 ZONE used total mem-use PIPE 53 918 8/143K SWAPMETA 0 0 0/0K tcpcb 298 399 158/211K unpcb 4 128 0/8K ripcb 0 21 0/3K tcpcb 0 0 0/0K udpcb 35 84 6/15K socket 342 462 64/86K KNOTE 0 128 0/8K NFSNODE 446814 446832 139629/139635K NFSMOUNT 26 35 13/18K VNODE 450712 450712 84508/84508K NAMEI 1 152 1/152K VMSPACE 93 576 17/108K PROC 97 588 39/238K DP fakepg 0 0 0/0K PV ENTRY 92980 524263 2542/14335K MAP ENTRY 1028 5228 48/245K KMAP ENTRY 1401 2253 65/105K MAP 7 10 0/1K VM OBJECT 281413 281530 26382/26393K ------------------------------------------ TOTAL 253486/266219K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 12:56:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from voyager.myzona.net (dsl027-179-063.sfo1.dsl.speakeasy.net [216.27.179.63]) by hub.freebsd.org (Postfix) with ESMTP id ACE2B37B401 for ; Mon, 25 Jun 2001 12:56:41 -0700 (PDT) (envelope-from alex@myzona.net) Received: from parkson (adsl-64-166-86-205.dsl.sntc01.pacbell.net [64.166.86.205]) by voyager.myzona.net (8.11.4/8.11.1) with SMTP id f5PJrNw46033 for ; Mon, 25 Jun 2001 12:53:24 -0700 (PDT) (envelope-from alex@myzona.net) Message-ID: <002501c0fdb0$95e5a320$ea31fea9@parkson> Reply-To: "Alex M" From: "Alex M" To: "FreeBSD STABLE" Subject: Updating OpenSSH on -release Date: Mon, 25 Jun 2001 12:54:03 -0700 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 6.00.2479.0006 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, What I am trying to do is update my OpenSSH from the base system, I am running 4.2-RELEASE, and I have cvsup'ed the -stable source tree, but I dont want to make world, just some parts, like openssh. I dont know if its even recommended, but heres what I am doing: cd /usr/src/crypto/openssh make ===> lib "Makefile", line 19: Malformed conditional ((${KERBEROS:L} == "yes")) "Makefile", line 19: Missing dependency operator "Makefile", line 21: Malformed conditional ((${AFS:L} == "yes")) "Makefile", line 21: Missing dependency operator "Makefile", line 24: if-less endif "Makefile", line 24: Need an operator "Makefile", line 25: if-less endif "Makefile", line 25: Need an operator make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /usr/src/crypto/openssh. I guess I am doing something wrong. Any help would be appreciated. Thanks. -=-=-=- Regards, Alex M aka TZapper alex@myzona.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 13:36:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 26DBE37B401 for ; Mon, 25 Jun 2001 13:36:23 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15Ed5m-000183-00; Tue, 26 Jun 2001 08:36:18 +1200 Date: Tue, 26 Jun 2001 08:36:18 +1200 (NZST) From: Juha Saarinen To: John Polstra Cc: "stable@freebsd.org" Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: <200106251528.f5PFSZS86318@vashon.polstra.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Jun 2001, John Polstra wrote: > No fix is needed. The message is telling you that CVSup has noticed > a problem and is fixing it itself. CVSup _will_not_ give you a bad > update unless your underlying hardware (or OS) garbles the data on the > way to the disk drive. Yes, I assumed it was a sanity check of some kind. Thing is though, it's been going on for over a week now, on three machines. Is it a local problem, or a problem with the repository? -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 13:47:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id 4D57437B401 for ; Mon, 25 Jun 2001 13:47:45 -0700 (PDT) (envelope-from jwatkins@firstplan.com) Received: from nightstalker ([206.129.94.230]) by smtp.easystreet.com (8.11.2/8.11.2) with SMTP id f5PKldO03711; Mon, 25 Jun 2001 13:47:39 -0700 (PDT) From: "Jason Watkins" To: "Steve O'Hara-Smith" Cc: , Subject: RE: Staying *really stable* in FreeBSD Date: Mon, 25 Jun 2001 13:47:37 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <20010623103557.547f67c5.steveo@eircom.net> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG JW> I react rather badly to some of your comments concerning the usability of JW> FreeBSD. Our goal *should* be a simple and turnkey system, or at the least, SH> That would be a RELEASE. They are usually pretty good at being just that IMHO. No, usability follows from design and functionality. That means thinking about it at the release canidate stage is to late. JW> I mean better equip the commiters. Such things are possible, and done every JW> day in the software world. Many aspects of code review and regression JW> testing can be automated. The time of volenteers in the committer group is SH> The time it takes to set up good automated regression testing is amazing, it is also a good way to perpetuate bugs. More importantly such testing is nearly useless in the face of new functionality, or timing and compatability issues. The general quality of -stable indicates that pre commit testing is done rather better than average in the industry. Remember that in most of the industry the only people who see software at the equivalent of -stable are *developers*. It is not unusual for software to emerge from several weeks of regression, integration, acceptance and soak testing into the field only to get bug reports in the first week of real use. It's true that these methods are not siliver bullets. The methodology religion folks (I guess XP is the newest one of those) tend to fall into that hope. But reguardless, some simple things do work. For example, structuring peer review and tracking repeated mistakes of practice. This has nothing to do with a smart automated system of any sort, but does help keep track of things for developers, especially helping to codify the expierence of the senior developers for the benifit of all. JW> Again, what I see as the problem is -stable isn't as stable as some people SH> Frankly you are dreaming if you think -stable can get much better without slowing down a lot, at which point you hit the security fix branch which never contains any feature that hasn't survived a Beta test. Hammer on the Beta and RC phases to improve the quality of this. Sure I'm dreaming, but it's certainly not an imposible dream. Stability comes from design. It's true that some means of achieving that goal have performance implications, but for the most part, it's completely independent of the speed of the code. And as far as that goes, I'll take *any* improvement in stability over speed any day. I help build rally cars. 90% of winning in rally is about reliability and useability: keeping things running smoothly and consistantly till the end. There are plenty of hotshots out there with very impressive and fast cars. But when you roll it off the road or blow the engine because you're a boost junky, all you do is let someone with half the horsepower and consistant performance walk all over you in the championship. Anyhow, I run -stable, and for the most part, haven't had many problems. But I think there perhaps should be more emphasis on keeping the standards of -stable a bit higher. jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 13:50:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from granger.centurytel.net (granger.centurytel.net [209.142.136.117]) by hub.freebsd.org (Postfix) with ESMTP id 277B837B401 for ; Mon, 25 Jun 2001 13:50:21 -0700 (PDT) (envelope-from lambert@lambertfam.org) Received: from laptop.lambertfam.org (laptop.lambertfam.org [209.142.170.27]) by granger.centurytel.net (8.11.4/8.11.4) with ESMTP id f5PKoJD29027 for ; Mon, 25 Jun 2001 15:50:20 -0500 (CDT) Received: by laptop.lambertfam.org (Postfix, from userid 1000) id E7CA428B36; Mon, 25 Jun 2001 15:50:17 -0500 (CDT) Date: Mon, 25 Jun 2001 15:50:17 -0500 From: Scott Lambert To: FreeBSD-STABLE@FreeBSD.org Subject: Re: Still getting "Checksum mismatch" etc. Message-ID: <20010625155017.A2668@laptop.lambertfam.org> Reply-To: FreeBSD-STABLE@FreeBSD.org Mail-Followup-To: FreeBSD-STABLE@FreeBSD.org References: <200106251528.f5PFSZS86318@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from juha@saarinen.org on Tue, Jun 26, 2001 at 08:36:18AM +1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jun 26, 2001 at 08:36:18AM +1200, Juha Saarinen wrote: > On Mon, 25 Jun 2001, John Polstra wrote: > > > No fix is needed. The message is telling you that CVSup has noticed > > a problem and is fixing it itself. CVSup _will_not_ give you a bad > > update unless your underlying hardware (or OS) garbles the data on the > > way to the disk drive. > > Yes, I assumed it was a sanity check of some kind. Thing is though, it's > been going on for over a week now, on three machines. Is it a local > problem, or a problem with the repository? But how many CVSups on each machine. There was a commit of libpam stuff that didn't work. Some time later the commit was backed out. The first commit required the new downloads. The backout commit required downloading the old versions again. Apparently the files are different enough that CVSup falls back to transfer the whole file rather than just edit. -- Scott Lambert Unix SysAdmin -- Looking for work. lambert@lambertfam.org http://www.lambertfam.org/~lambert/resume.html Two and a half years Sr. SysAdmin experience with FreeBSD in a small, 15,000 dial-up accounts, 19,000+ e-mail accounts, ISP. The last 5 months have included exposure to Solaris 7, True64 5, and Linux. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 13:59:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 463B037B405 for ; Mon, 25 Jun 2001 13:59:04 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15EdRn-00018r-00 for ; Tue, 26 Jun 2001 08:59:03 +1200 Date: Tue, 26 Jun 2001 08:59:03 +1200 (NZST) From: Juha Saarinen To: "FreeBSD-STABLE@FreeBSD.org" Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: <20010625155017.A2668@laptop.lambertfam.org> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Jun 2001, Scott Lambert wrote: > But how many CVSups on each machine. I run a daily cvsup cron job (well, it's nightly, really). I get the error messages if I do 'make update' in /usr/src as well. > There was a commit of libpam stuff that > didn't work. Some time later the commit was backed out. The first commit > required the new downloads. The backout commit required downloading the > old versions again. Apparently the files are different enough that CVSup > falls back to transfer the whole file rather than just edit. So, I need to download the old version(s) of the libpam files? How would I do that with CVSup? -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 14: 5:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id D2B1137B406 for ; Mon, 25 Jun 2001 14:05:52 -0700 (PDT) (envelope-from jwatkins@firstplan.com) Received: from nightstalker ([206.129.94.230]) by smtp.easystreet.com (8.11.2/8.11.2) with SMTP id f5PL5qL21116; Mon, 25 Jun 2001 14:05:52 -0700 (PDT) From: "Jason Watkins" To: "Stable" , "Joe Kelsey" Subject: RE: Staying *really stable* in FreeBSD Date: Mon, 25 Jun 2001 14:05:50 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <15157.11221.593513.478892@zircon.zircon.seattle.wa.us> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG JK> All of your problems can be traced back to old hardware or inexperience with the latest thinking in BSD land. Because you have not upgraded your 2.x system, you are essentially stuck. Either get newer hardware to work with or go through the upgrade based on your subscription disks. While that's true in the particular it's still useless advice, and what you're missing is his intent: ie he *shouldn't* be stuck and forced to build a fresh system, and that we should do something to ensure that doesn't happen again. JK> The tracking of stable is not for everyone. Noone *needs* to track stable. JK> What we need is an apt-get-like upgrade path for security fixes that solves the problem of people tracking one version of stable or another. Remove the necessity of recompiling from source and we remove almost all reasons for people to complain about the stableness of stable just because they ran into a minor problem of timing WRT cvsup and updates to the source tree. That's what -stable is SUPPOSED to be, incremental stable bugfixes and functionality updates from the most recent release. Also, there are many advantages to building from source rather than running genericly compiled i386 binaries. I personally love letting gcc be as agressive about optimising to my architecture as possible. On top of that is the standard kernal tuning argument and advantages. I also disagree with your comments re make and the difficulty of rebuilding a system. I am completely new to the unix developement world and make. I'm completely new to freebsd. I was able to rebuild my system without incident following 5 lines of instructions from someone on this list. Obviously this *isn't* rocket science, and aside from eyeballing things in mergemaster, we shouldn't sit back on our haunches and perpetuate the idea that building from -stable is something only for the freebsd cognizati elite. We are not talking about what *is*, we are exploring what we feel things *should* be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 14:21:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from granger.centurytel.net (granger.centurytel.net [209.142.136.117]) by hub.freebsd.org (Postfix) with ESMTP id 57A4737B405 for ; Mon, 25 Jun 2001 14:21:43 -0700 (PDT) (envelope-from lambert@lambertfam.org) Received: from laptop.lambertfam.org (laptop.lambertfam.org [209.142.170.27]) by granger.centurytel.net (8.11.4/8.11.4) with ESMTP id f5PLLfC03037 for ; Mon, 25 Jun 2001 16:21:41 -0500 (CDT) Received: by laptop.lambertfam.org (Postfix, from userid 1000) id 3CB1B28B37; Mon, 25 Jun 2001 16:21:40 -0500 (CDT) Date: Mon, 25 Jun 2001 16:21:40 -0500 From: Scott Lambert To: "FreeBSD-STABLE@FreeBSD.org" Subject: Re: Still getting "Checksum mismatch" etc. Message-ID: <20010625162140.C2668@laptop.lambertfam.org> Mail-Followup-To: "FreeBSD-STABLE@FreeBSD.org" References: <20010625155017.A2668@laptop.lambertfam.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from juha@saarinen.org on Tue, Jun 26, 2001 at 08:59:03AM +1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jun 26, 2001 at 08:59:03AM +1200, Juha Saarinen wrote: > On Mon, 25 Jun 2001, Scott Lambert wrote: > > > But how many CVSups on each machine. > > I run a daily cvsup cron job (well, it's nightly, really). I get the error > messages if I do 'make update' in /usr/src as well. > > > > There was a commit of libpam stuff that > > didn't work. Some time later the commit was backed out. The first commit > > required the new downloads. The backout commit required downloading the > > old versions again. Apparently the files are different enough that CVSup > > falls back to transfer the whole file rather than just edit. > > So, I need to download the old version(s) of the libpam files? How would I > do that with CVSup? It should have been cleared up by now with a nightly cvsup. Mine boxes just had the two instances where they downloaded all the libpam stuff. After that, it was business as usual. So, are you saying you get to download those files each time you cvsup? Have you tried deleting those files from your source tree? -- Scott Lambert Unix SysAdmin -- Looking for work. lambert@lambertfam.org http://www.lambertfam.org/~lambert/resume.html Two and a half years Sr. SysAdmin experience with FreeBSD in a small, 15,000 dial-up accounts, 19,000+ e-mail accounts, ISP. The last 5 months have included exposure to Solaris 7, True64 5, and Linux. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 14:23:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id E654137B405 for ; Mon, 25 Jun 2001 14:23:49 -0700 (PDT) (envelope-from jwatkins@firstplan.com) Received: from nightstalker ([206.129.94.230]) by smtp.easystreet.com (8.11.2/8.11.2) with SMTP id f5PLNjL08286; Mon, 25 Jun 2001 14:23:49 -0700 (PDT) From: "Jason Watkins" To: "Jordan Hubbard" Cc: "Stable" Subject: RE: Staying *really stable* in FreeBSD Date: Mon, 25 Jun 2001 14:23:43 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <20010624023403R.jkh@osd.bsdi.com> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I think it's become clear in this discussion that some people reguard -stable as the secure, regularly updated moving release canidate. Other people view -stable as a just stable enough branch for developers to coordinate building new functionality. If the 2nd view is the official one, then a new branch should be started that has the first purpose in mind. Weither you like it or not, a great many users are simply going to insist that they have some way of updating the system at a days notice of security or stability issues imbetween releases. In my own expierences working in the software world (CRM, not anything systems related) releasing new functionality often in small doses, basicly as often as your clients IT staff can stomach dealing with, absolutely obliterates any other approach. Changes in idiology, functionality or configuration are small, delt with quickly, and the feedback loop between request/response and actual implimentation shorts to mere weeks. Everyone ends up much happyer. I was under the understanding, gleaned from the handbook and from some people here, that -stable was the place for this sort of mentality. If it's not, then IMHO, we need a place for it. As anicdotal evidence, I used debian quite a bit a few years back. There certainly was no problem staying with the stable branch there. The OpenBSD team also seems to show it's possible to maintain a stable moving codebase as well. Is it actually any individuals role to oversee the stability of stable? Or is it left to each individual committer who's checked out certain tasks to judge if his code is safe enough to move from -current to -stable? Whole holds the vision of common practices and evangalises them to the rest of the developers? Who ensures (by review) that a mistake of practice only happens once? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 14:29:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 0CA7337B406 for ; Mon, 25 Jun 2001 14:29:19 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15Eduz-0001AS-00; Tue, 26 Jun 2001 09:29:13 +1200 Date: Tue, 26 Jun 2001 09:29:13 +1200 (NZST) From: Juha Saarinen To: Scott Lambert Cc: "FreeBSD-STABLE@FreeBSD.org" Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: <20010625162140.C2668@laptop.lambertfam.org> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Jun 2001, Scott Lambert wrote: > It should have been cleared up by now with a nightly cvsup. Mine boxes just > had the two instances where they downloaded all the libpam stuff. After that, > it was business as usual. > > So, are you saying you get to download those files each time you cvsup? > > Have you tried deleting those files from your source tree? No, that's what I was wondering as well, if I could just rm the offending files. Anyway, just checked the daily output logs on the affected systems, and the problem seems to have gone away now. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 14:39:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (Postfix) with ESMTP id 19A8C37B407 for ; Mon, 25 Jun 2001 14:39:10 -0700 (PDT) (envelope-from jwatkins@firstplan.com) Received: from nightstalker ([206.129.94.230]) by smtp.easystreet.com (8.11.2/8.11.2) with SMTP id f5PLd9L23669 for ; Mon, 25 Jun 2001 14:39:09 -0700 (PDT) From: "Jason Watkins" To: "Stable" Subject: RE: Still getting "Checksum mismatch" etc. Date: Mon, 25 Jun 2001 14:39:07 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <200106251528.f5PFSZS86318@vashon.polstra.com> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I also was getting these errors, along with some odd behaviour in the ports tree. I ended up simply blasting out my src and cvs files and pulling everything down from scratch. Certainly a case of useing a broadswoard for a letter opener, but it worked. If you're getting these errors, be aware that any additional errors are not other isolated problems but that your cvs is probibly mistracking as mine was. I still haven't determined why mine went awry. jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 15: 2:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kcmgwp01.corp.sprint.com (parker1.sprint.com [208.18.122.165]) by hub.freebsd.org (Postfix) with ESMTP id 5906137B405 for ; Mon, 25 Jun 2001 15:02:12 -0700 (PDT) (envelope-from steve.d.meacham@mail.sprint.com) Received: from kcmgwp02.corp.sprint.com (kcmgwp02 [10.185.6.93]) by kcmgwp01.corp.sprint.com (Switch-2.0.2/Switch-2.0.2) with ESMTP id f5PM2BV29596 for ; Mon, 25 Jun 2001 17:02:11 -0500 (CDT) Received: from kcopmp01.corp.sprint.com (kcopmp01m.corp.sprint.com [10.74.2.72]) by kcmgwp02.corp.sprint.com (Switch-2.0.2/Switch-2.0.2) with ESMTP id f5PM2Bg29575 for ; Mon, 25 Jun 2001 17:02:11 -0500 (CDT) Received: from localhost (root@localhost) by kcopmp01.corp.sprint.com (8.8.6 (PHNE_17190)/8.8.6) with ESMTP id RAA10879 for ; Mon, 25 Jun 2001 17:02:10 -0500 (CDT) From: steve.d.meacham@mail.sprint.com X-OpenMail-Hops: 1 Date: Mon, 25 Jun 2001 17:02:09 -0500 Message-Id: Subject: Best time to cvsup -STABLE MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: multipart/mixed; boundary="openmail-part-4815ac74-00000001" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --openmail-part-4815ac74-00000001 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline ;Creation-Date="Mon, 25 Jun 2001 17:02:08 -0500" Content-Transfer-Encoding: 7bit I'd like to know if there is a time window where -STABLE is most likely to not be getting updated. This should allow us to avoid grabbing and building source that by chance has some changes only partially checked in and then getting strange behaviour or build errors. I heard mention on this list that there should be such a window but I'm not certain if there is one or not. --openmail-part-4815ac74-00000001-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 15:22:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cokane.org (ip-216-23-48-4.adsl.one.net [216.23.48.4]) by hub.freebsd.org (Postfix) with ESMTP id 97F4037B405 for ; Mon, 25 Jun 2001 15:22:20 -0700 (PDT) (envelope-from cokane@cokane.org) Received: (from cokane@localhost) by cokane.org (8.11.4/8.11.4) id f5QAOlr92205; Tue, 26 Jun 2001 06:24:47 -0400 (EDT) (envelope-from cokane) Date: Tue, 26 Jun 2001 06:24:47 -0400 From: Coleman Kane To: Rasputin Cc: stable@freebsd.org Subject: Re: XFree86-4.1.0+mga+dri+FreeBSD-4.3-stable == hang Message-ID: <20010626062447.C91902@evil.apt> References: <200106140436.OAA20451@hadrian.staff.apnic.net> <20010614141859.B67187@node7.cluster.srrc.usda.gov> <20010625110619.A44348@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010625110619.A44348@dogma.freebsd-uk.eu.org>; from rara.rasputin@virgin.net on Mon, Jun 25, 2001 at 11:06:20AM +0100 X-VIM-Settings: vim:ts=4:sw=4:tw=70: X-Operating-System: FreeBSD evil.apt 5.0-CURRENT FreeBSD 5.0-CURRENT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I thought that dfr was supposed to be taking care of this...maybe not anymore. On Mon, Jun 25, 2001 at 11:06:20AM +0100, Rasputin wrote, and it was proclaimed: > * Glenn Johnson [010614 20:27]: > > On Thu, Jun 14, 2001 at 02:36:00PM -0500, ggm@apnic.net wrote: > > > > > Say I have a Matrox G400, on FreeBSD-4.3-stable, I have installed the > > > FreeBSD 'port' of XFree86-4.1.0 and I try to enable dri, and it hangs. > > > > The DRI stuff does not work with XF86-4.1 and FreeBSD. > > > > > Do I try to foist blame on XFree86, or do I try to foist blame on > > > FreeBSD? > > > > > > I realize this isn't a well formed bug report, I'm holding off on > > > that, until I understand who wants to be put in the frame. > > > > > > My suspicion is that Its FreeBSD, because it relates to their > > > kernel agp.ko module (which I am guessing is required to support > > > DRI->agp->G400 interrelationships somehow. > > > > The agp.ko module is built with the FreeBSD sources and as far as I know > > works fine for most motherboard chip sets. It is required for DRI but > > not sufficient. The other required kernel modules for DRI with a Matrox > > G400 are the mga.ko and the drm.ko modules. These are [optionally] > > built as part of XFree86. The problem is that nobody is keeping the BSD > > branch of the DRI source tree up to date. > > If you go to > > http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11/XFree86-4/?only_with_tag=RELEASE_4_3_0 > > you'l get a version of the port that *should* build the dri modules you need. > You still need to preload agp.ko and mga.ko from /boot/loader.conf, and load > the dri module in XF86Config , but you should be OK. > > Unlike me ,since that port doesn't appear to build tdfx_dri.so ......... > > If anyone's got DRi on a Voodoo 3 working, please let me know. > Ta! > -- > Moon, n.: > 1. A celestial object whose phase is very important to > hackers. See PHASE OF THE MOON. 2. Dave Moon (MOON@MC). > Rasputin :: Jack of All Trades - Master of Nuns :: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 15:43:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 6786437B401; Mon, 25 Jun 2001 15:43:42 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f5PHeAY11356; Mon, 25 Jun 2001 10:40:10 -0700 (PDT) (envelope-from dillon) Date: Mon, 25 Jun 2001 10:40:10 -0700 (PDT) From: Matt Dillon Message-Id: <200106251740.f5PHeAY11356@earth.backplane.com> To: Alfred Perlstein Cc: freebsd-stable@FreeBSD.ORG, tegge@FreeBSD.ORG Subject: Re: -stable weird panics References: <20010625145124.D64836@sneakerz.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :% vmstat -m -M /var/qmail/crash/vmcore.6 :Memory Totals: In Use Free Requests : 17408K 137K 7909365 :% vmstat -z -M /var/qmail/crash/vmcore.6 : :ZONE used total mem-use :PIPE 55 408 8/63K :SWAPMETA 0 0 0/0K :tcpcb 303 371 160/197K :unpcb 4 128 0/8K :ripcb 0 21 0/3K :tcpcb 0 0 0/0K :udpcb 41 84 7/15K :socket 354 441 66/82K :KNOTE 1 128 0/8K :NFSNODE 99464 99480 31082/31087K :NFSMOUNT 26 35 13/18K :VNODE 105046 105046 19696/19696K :NAMEI 2 48 2/48K :VMSPACE 97 320 18/60K :PROC 101 294 41/119K :DP fakepg 0 0 0/0K :PV ENTRY 33850 524263 925/14335K :MAP ENTRY 1057 2593 49/121K :KMAP ENTRY 824 1148 38/53K :MAP 7 10 0/1K :VM OBJECT 66326 66406 6218/6225K :------------------------------------------ :TOTAL 58330/72146K : :So why is zalloc dying when it looks like only about 90 megs of :kernel memory is allocated? Are those active vnodes or cached vnodes? What is kern.maxvnodes set to? Also, what's the full vmstat -m output on the crash dump? :Anyhow, I've added a check in getnewvnode to return ENOMEM if zalloc :fails, my concern is that other parts of the kernel are going to :blow up immediately after that is caught because it looks like :the majority of places don't expect zalloc to fail. : :Any suggestions will be helpful, any requests for more information :will happily be attempted. : :thanks, :-Alfred Well, there's definitely some kind of limit being hit here. You have to figure out what it is first. Print out the zalloc zone structure being used to see why it is returning NULL. Maybe it has hit it's max count or something and the bug is that the zalloc zone isn't scaled with kern.maxvnodes, or something like that. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 16: 0:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from woody.ichilton.co.uk (woody.ichilton.co.uk [216.29.174.40]) by hub.freebsd.org (Postfix) with ESMTP id 7828737B406 for ; Mon, 25 Jun 2001 16:00:53 -0700 (PDT) (envelope-from ian@woody.ichilton.co.uk) Received: by woody.ichilton.co.uk (Postfix, from userid 1000) id BB7F57D1D; Tue, 26 Jun 2001 00:00:41 +0100 (BST) Date: Tue, 26 Jun 2001 00:00:41 +0100 From: Ian Chilton To: freebsd-stable@freebsd.org Subject: Problems with Ports Message-ID: <20010626000041.B25545@woody.ichilton.co.uk> Reply-To: Ian Chilton Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.13i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I synced the ports tree yesturday, but am having problems with 3 ports: 1) Mozilla 2) Minicom 3) Netscape Navigator Here we go: 1) Mozilla: Building deps for nsCSSFrameConstructor.cpp c++ -o nsCSSFrameConstructor.o -c -DOSTYPE=\"FreeBSD4\" -DOSARCH=\"FreeBSD\" -DOJI -D_IMPL_NS_HTML -DENDER_LITE -I../../../../dist/include -I../../../../dist/include -I/usr/ports/www/mozilla/work/mozilla/dist/include/nspr -I/usr/local/include -I/usr/local/include -I./../../base/src -I./../../../base/src -I./../../table/src -I./../../forms/src -I./../../content/src -I./../../../xul/content/src -I./. -I./../../../xul/base/src -I./../../../mathml/content/src -I./../../../mathml/base/src -I./../../../svg/content/src -I./../../../svg/base/src -I/usr/X11R6/include -fPIC -I/usr/X11R6/include -I/usr/X11R6/include -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Wbad-function-cast -Wcast-align -Woverloaded-virtual -Wsynth -Wno-long-long -O -pipe -pipe -O -DNDEBUG -DTRIMMED -I/usr/X11R6/include -I/usr/X11R6/include -DMOZILLA_CLIENT -include ../../../../config-defs.h nsCSSFrameConstructor.cpp In file included from ../../base/src/nsLineLayout.h:35, from ../../base/src/nsInlineFrame.h:27, from nsCSSFrameConstructor.cpp:111: ../../base/src/nsLineBox.h: In method `void nsLineBox::SetBreakType(unsigned char)': ../../base/src/nsLineBox.h:268: warning: statement with no effect ../../../../dist/include/nsBufferHandle.h: In function `static const struct nsIID & nsIBox::GetIID()': ../../../../dist/include/nsBufferHandle.h:359: Internal compiler error. ../../../../dist/include/nsBufferHandle.h:359: Please submit a full bug report. ../../../../dist/include/nsBufferHandle.h:359: See for instructions. gmake[4]: *** [nsCSSFrameConstructor.o] Error 1 gmake[4]: Leaving directory `/usr/ports/www/mozilla/work/mozilla/layout/html/style/src' gmake[3]: *** [install] Error 2 gmake[3]: Leaving directory `/usr/ports/www/mozilla/work/mozilla/layout/html/style' gmake[2]: *** [install] Error 2 gmake[2]: Leaving directory `/usr/ports/www/mozilla/work/mozilla/layout/html' gmake[1]: *** [install] Error 2 gmake[1]: Leaving directory `/usr/ports/www/mozilla/work/mozilla/layout' gmake: *** [install] Error 2 *** Error code 2 Stop in /usr/ports/www/mozilla. *** Error code 1 Stop in /usr/ports/www/mozilla. *** Error code 1 Stop in /usr/ports/www/mozilla. 2) Minicom: [root@jester:/usr/ports/comms/minicom]# make install ===> minicom-1.83.1_2 is forbidden: Local exploit yielding setuid uucp. 3) Netscape: [root@jester:/usr/ports/www/netscape47-navigator]# make install ===> netscape-navigator-4.76 is marked as broken: Has a serious security hole, use 4.77 instead. Bye for Now, Ian \|||/ (o o) /-----------------------------ooO-(_)-Ooo----------------------------\ | Ian Chilton E-Mail: ian@ichilton.co.uk | | IRC Nick: GadgetMan Backup: ichilton@www.linux.org.uk | | ICQ: 16007717 / 104665842 Web : http://www.ichilton.co.uk | |--------------------------------------------------------------------| | For people who like peace and quiet: a phoneless cord | \--------------------------------------------------------------------/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 16: 5: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from zircon.seattle.wa.us (sense-sea-CovadSub-0-228.oz.net [216.39.147.228]) by hub.freebsd.org (Postfix) with SMTP id 5BAB237B406 for ; Mon, 25 Jun 2001 16:05:00 -0700 (PDT) (envelope-from joe@zircon.seattle.wa.us) Received: (qmail 35968 invoked by uid 1001); 25 Jun 2001 23:06:03 -0000 From: Joe Kelsey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15159.50139.551865.224398@zircon.zircon.seattle.wa.us> Date: Mon, 25 Jun 2001 16:06:03 -0700 To: mupi@Mknet.org Cc: Chris BeHanna , FreeBSD-Stable Subject: Re: Staying *really stable* in FreeBSD In-Reply-To: <01062500364404.80326@mukappa.home.com> References: <01062500364404.80326@mukappa.home.com> X-Mailer: VM 6.90 under Emacs 20.7.1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Porter writes: > [Lots of rambling ideas ...] First of all Mike, quite an interesting post. Unfortuantely, either the author of the book didn't understand or didn't explain the CMM well enough for you to be able to use it. I have worked as a Software Quality Engineer (really doing Quality, not being a glorfied tester as the software industry seems to call anyone who runs a test a "quality engineer", just like anyone who has written a line of code gets to call themselves a "software engineer"...) and I have helped organizations achieve CMM Level 3 and above. If you look at the actual CMM, you could argue that the general FreeBSD process qualifies for Level 2, given a little more work on the Project Management and Configuration Management fronts. The main things missing is good design documentation and real attention to CM issues. However, I do not think it is possible for any "open source" volunteer effort to get better than Level 2. It requires really dedicated resources in the upper management areas that just won't happen outside of a corporate context. Also, when you start throwing process ideas around a group like this, you might not be received very well... I suggest you go read the various XP books (eXtreme Programming). They are small and easy to digest and are much more applicable to this environment (except for the pair programming part...) /Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 16: 7: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f123.law7.hotmail.com [216.33.237.123]) by hub.freebsd.org (Postfix) with ESMTP id 2455337B409 for ; Mon, 25 Jun 2001 16:07:00 -0700 (PDT) (envelope-from dimuthu@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 25 Jun 2001 16:06:59 -0700 Received: from 203.39.46.163 by lw7fd.law7.hotmail.msn.com with HTTP; Mon, 25 Jun 2001 23:06:59 GMT X-Originating-IP: [203.39.46.163] From: "Dimuthu Bandara" To: freebsd-stable@freebsd.org Subject: ServeRaid 4L support ? Date: Mon, 25 Jun 2001 23:06:59 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 25 Jun 2001 23:06:59.0777 (UTC) FILETIME=[89C23B10:01C0FDCB] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I tried to install Freebsd 4.3 Release on IBM Netfinity 5000 with ServeRaid 4L. And it doesn't even detect the drives. Is there anyway to install Freebsd this server with RAID 5. Are there drivers for servRaid? I know it's not listed in HARDWARE.TXT Please help me. Regards dimuthu _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 16: 9:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (dhcp44-21.dis.org [216.240.44.21]) by hub.freebsd.org (Postfix) with ESMTP id 26B4537B417 for ; Mon, 25 Jun 2001 16:09:37 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f5PNLaH00818; Mon, 25 Jun 2001 16:21:36 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106252321.f5PNLaH00818@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Dimuthu Bandara" Cc: freebsd-stable@freebsd.org Subject: Re: ServeRaid 4L support ? In-reply-to: Your message of "Mon, 25 Jun 2001 23:06:59." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Jun 2001 16:21:35 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hi, > > I tried to install Freebsd 4.3 Release on IBM Netfinity 5000 with ServeRaid > 4L. And it doesn't even detect the drives. Is there anyway to install > Freebsd this server with RAID 5. Are there drivers for servRaid? I know it's > not listed in HARDWARE.TXT There is no support for the IBM ServeRAID family of controllers. You'll need to use a different controller. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 16:14:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from zircon.seattle.wa.us (sense-sea-CovadSub-0-228.oz.net [216.39.147.228]) by hub.freebsd.org (Postfix) with SMTP id 3A5AF37B40B for ; Mon, 25 Jun 2001 16:14:21 -0700 (PDT) (envelope-from joe@zircon.seattle.wa.us) Received: (qmail 36008 invoked by uid 1001); 25 Jun 2001 23:15:25 -0000 From: Joe Kelsey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15159.50701.307221.964848@zircon.zircon.seattle.wa.us> Date: Mon, 25 Jun 2001 16:15:25 -0700 To: freebsd-stable@freebsd.org Subject: STABLE vs. RELENG X-Mailer: VM 6.90 under Emacs 20.7.1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jason seems to have missed out on the discussion of the security fix branch, RELENG_X_Y. We really need to update the handbook to indicate that STABLE is only relatively stable. It is a DEVELOPMENT branch, intended to be more stable than CURRENT, but still prone to instability just as all development projects are. Also, there are a lot of people making good and interesting suggestions. I think my comments about upgrading hardware should really be taken seriously. If you intend to try to do a source upgrade from one major release to another you really need up to date hardware or a lot of experience solving hardware/software conflicts. Binary upgrade is the easiest way to go between versions, but the horror stories people have told of prove that it is not foolproof. Perhaps the only safe way to go is to have multiple machines on a local network. Do a fresh install on one, copy the user files over to the new machine and destroy the old machine (or erase the disks or install a new OS...) I think that the FreeBSD project is close to a situation where we can encourage people to operate in "sourceless" mode, at least as far as world/kernel goes. The ports tree already has tools to allow selective fetch and build. The world/kernel area now has binary package updates for security fixes (in world at least) and with kld and sysctl we can probably just ship a useful GENERIC configuration with the instructions on how to load the sound drivers or whatever else you need. This has actually been a better discussion than I at first feared it would be. At least it's not the usual RC/BETA issue... /Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 16:20: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp-2.enteract.com (smtp-2.enteract.com [207.229.143.4]) by hub.freebsd.org (Postfix) with ESMTP id A5F3137B405 for ; Mon, 25 Jun 2001 16:19:58 -0700 (PDT) (envelope-from presence@churchofinformationwarfare.org) Received: from shell-3.enteract.com (shell-3.enteract.com [207.229.143.42]) by smtp-2.enteract.com (Postfix) with ESMTP id 3420F6099 for ; Mon, 25 Jun 2001 18:19:58 -0500 (CDT) Date: Mon, 25 Jun 2001 18:19:57 -0500 (CDT) From: Reverend K Kanno X-Sender: presence@shell-3.enteract.com To: freebsd-stable@freebsd.org Subject: HP Netserver e800 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greetings, Has anybody run into any problems with FreeBSD 4.x on HP Netserver e800 junior class servers? My question pertains mostly to the integrated Ultra2 LSI Logic embedded SCSI host adapter. I know Dell likes to use old broken BIOSes on their integrated Adaptec SCSI HAs. ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== The Exploding Fruit Challenge! Rev. K. Kanno www.energybeam.com blowup-fruit@energybeam.com ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 17:23:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sneakerz.org (sneakerz.org [216.33.66.254]) by hub.freebsd.org (Postfix) with ESMTP id DC41B37B401; Mon, 25 Jun 2001 17:23:02 -0700 (PDT) (envelope-from bright@sneakerz.org) Received: by sneakerz.org (Postfix, from userid 1092) id 54BB65D010; Mon, 25 Jun 2001 19:22:52 -0500 (CDT) Date: Mon, 25 Jun 2001 19:22:52 -0500 From: Alfred Perlstein To: Matt Dillon Cc: freebsd-stable@FreeBSD.ORG, tegge@FreeBSD.ORG Subject: Re: -stable weird panics Message-ID: <20010625192252.G64836@sneakerz.org> References: <20010625145124.D64836@sneakerz.org> <200106251740.f5PHeAY11356@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200106251740.f5PHeAY11356@earth.backplane.com>; from dillon@earth.backplane.com on Mon, Jun 25, 2001 at 10:40:10AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Matt Dillon [010625 17:43] wrote: > : > :So why is zalloc dying when it looks like only about 90 megs of > :kernel memory is allocated? > > Are those active vnodes or cached vnodes? What is kern.maxvnodes > set to? (kgdb) print desiredvnodes $1 = 132756 (kgdb) print wantfreevnodes $2 = 25 (kgdb) print freevnodes $3 = 24 It looks like we're at a low watermark: if (wantfreevnodes && freevnodes < wantfreevnodes) { vp = NULL; ... which forces us to call zalloc, which is returning NULL. (kgdb) print *vnode_zone $5 = {zlock = {lock_data = 0}, zitems = 0x0, zfreecnt = 0, zfreemin = 21, znalloc = 91584, zkva = 0, zpagecount = 0, zpagemax = 0, zmax = 0, ztotal = 91584, zsize = 192, zalloc = 5, zflags = 0, zallocflag = 2, zobj = 0x0, zname = 0xc03578c8 "VNODE", znext = 0xc464ce80} > Also, what's the full vmstat -m output on the crash dump? See bottom of this mail for latest core. > :Anyhow, I've added a check in getnewvnode to return ENOMEM if zalloc > :fails, my concern is that other parts of the kernel are going to > :blow up immediately after that is caught because it looks like > :the majority of places don't expect zalloc to fail. > : > :Any suggestions will be helpful, any requests for more information > :will happily be attempted. > : > :thanks, > :-Alfred > > Well, there's definitely some kind of limit being hit here. You > have to figure out what it is first. Print out the zalloc zone > structure being used to see why it is returning NULL. Maybe it > has hit it's max count or something and the bug is that the zalloc > zone isn't scaled with kern.maxvnodes, or something like that. There is no zone max, there's a malloc max, but afaik zalloc can't hit this sort of limit. Why is zalloc using kmem_alloc() instead of kmem_alloc_wait() ? I think this is what's getting hit, i don't really understand why we're short on memory, it sure doesn't seem like we should be failing in kmem_alloc() :(. Here's the stats from the latest crash, it's about the same place, 90megs and getnewvnode's zalloc call starts not behaving properly. Making getnewvnode() catch NULL return from zalloc() and return ENOMEM kept the system up, but sure pissed off the userland applications trying to open files. Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 16 744 280 754299 0 1280 32 90540 212 987589 0 640 64 93864 216 4267909 0 320 128 1575 185 959343 0 160 256 2049 95 594972 0 80 512 952 24 4167 0 40 1K 210 70 6191 0 20 2K 22 8 171 0 10 4K 29 1 335 0 5 8K 2 0 31 0 5 16K 11 0 11 0 5 32K 3 0 11 0 5 64K 1 0 1 0 5 128K 1 0 15 0 5 256K 1 0 1 0 5 512K 7 0 7 0 5 Memory usage type by bucket size Size Type(s) 16 uc_devlist, kld, MD disk, USB, p1003.1b, routetbl, ether_multi, vnodes, mount, pcb, soname, rman, bus, sysctl, temp, devbuf, atexit, proc-args 32 atkbddev, kld, USB, tseg_qent, in_multi, routetbl, ether_multi, ifaddr, BPF, vnodes, cluster_save buffer, pcb, soname, taskqueue, SWAP, eventhandler, bus, sysctl, uidinfo, subproc, pgrp, temp, devbuf, proc-args, sigio 64 AD driver, isadev, NFS req, in6_multi, routetbl, ether_multi, ifaddr, vnodes, cluster_save buffer, vfscache, pcb, rman, eventhandler, bus, subproc, session, ip6ndp, temp, devbuf, lockf, proc-args, file 128 kld, USBdev, USB, ZONE, routetbl, vnodes, mount, vfscache, soname, ppbusdev, ttys, bus, cred, temp, devbuf, zombie, proc-args, dev_t, timecounter 256 FFS node, newblk, NFS daemon, routetbl, ifaddr, vnodes, ttys, bus, subproc, temp, devbuf, proc-args, file desc 512 ATA generic, USBdev, UFS mount, NFSV3 diroff, ifaddr, mount, BIO buffer, ptys, msg, ioctlops, bus, ip6ndp, temp, devbuf, file desc 1K MD disk, AD driver, NQNFS Lease, Export Host, ifaddr, BIO buffer, sem, ioctlops, bus, uidinfo, temp, devbuf 2K uc_devlist, UFS mount, BIO buffer, pcb, bus, temp, devbuf 4K memdesc, USB, UFS mount, sem, msg, bus, proc, temp, devbuf 8K mbuf, shm, bus 16K msg, devbuf 32K UFS mount, bus, devbuf 64K pagedep 128K bus, temp 256K MSDOSFS mount 512K VM pgdata, UFS ihash, inodedep, NFS hash, vfscache, ISOFS mount, SWAP Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) atkbddev 2 1K 1K204800K 2 0 0 32 uc_devlist 30 3K 3K204800K 30 0 0 16,2K memdesc 1 4K 4K204800K 1 0 0 4K mbuf 1 8K 8K204800K 1 0 0 8K kld 4 1K 1K204800K 35 0 0 16,32,128 MD disk 2 2K 2K204800K 2 0 0 16,1K AD driver 1 1K 2K204800K 6 0 0 64,1K ATA generic 0 1K 1K204800K 1 0 0 512 isadev 23 2K 2K204800K 23 0 0 64 USBdev 1 1K 1K204800K 2 0 0 128,512 USB 14 17K 17K204800K 30 0 0 16,32,128,4K ZONE 15 2K 2K204800K 15 0 0 128 VM pgdata 1 512K 512K204800K 1 0 0 512K UFS mount 15 47K 47K204800K 15 0 0 512,2K,4K,32K UFS ihash 1 512K 512K204800K 1 0 0 512K FFS node 1577 395K 396K204800K 152351 0 0 256 newblk 1 1K 1K204800K 1 0 0 256 inodedep 1 512K 512K204800K 1 0 0 512K pagedep 1 64K 64K204800K 1 0 0 64K p1003.1b 1 1K 1K204800K 1 0 0 16 NFS hash 1 512K 512K204800K 1 0 0 512K NQNFS Lease 1 1K 1K204800K 1 0 0 1K NFSV3 diroff 872 436K 436K204800K 872 0 0 512 NFS daemon 1 1K 1K204800K 1 0 0 256 NFS req 0 0K 2K204800K 864655 0 0 64 in6_multi 8 1K 1K204800K 8 0 0 64 tseg_qent 3 1K 2K204800K 75610 0 0 32 Export Host 8 8K 8K204800K 8 0 0 1K in_multi 3 1K 1K204800K 3 0 0 32 routetbl 428 61K 252K204800K 39047 0 0 16,32,64,128,256 ether_multi 46 2K 2K204800K 46 0 0 16,32,64 ifaddr 39 10K 10K204800K 39 0 0 32,64,256,512,1K BPF 11 1K 1K204800K 11 0 0 32 MSDOSFS mount 1 256K 256K204800K 1 0 0 256K vnodes 89998 2818K 2818K204800K 444161 0 0 16,32,64,128,256 mount 32 16K 16K204800K 34 0 0 16,128,512 cluster_save buffer 0 0K 1K204800K 6790 0 0 32,64 vfscache 93127 6845K 6845K204800K 690773 0 0 64,128,512K BIO buffer 172 175K 237K204800K 550 0 0 512,1K,2K ISOFS mount 1 512K 512K204800K 1 0 0 512K pcb 70 10K 11K204800K 149922 0 0 16,32,64,2K soname 27 1K 1K204800K 569923 0 0 16,32,128 ppbusdev 3 1K 1K204800K 3 0 0 128 ptys 3 2K 2K204800K 3 0 0 512 ttys 451 58K 63K204800K 958 0 0 128,256 shm 1 8K 8K204800K 1 0 0 8K sem 3 6K 6K204800K 3 0 0 1K,4K msg 4 25K 25K204800K 4 0 0 512,4K,16K rman 65 4K 4K204800K 157 0 0 16,64 ioctlops 0 0K 1K204800K 16 0 0 512,1K taskqueue 1 1K 1K204800K 1 0 0 32 SWAP 2 549K 549K204800K 2 0 0 32,512K eventhandler 13 1K 1K204800K 13 0 0 32,64 bus 769 68K 150K204800K 1636 0 0 16,32,64,128,256, 512,1K,2K,4K,8K,32K,128K sysctl 0 0K 1K204800K 1022 0 0 16,32 uidinfo 8 2K 2K204800K 19554 0 0 32,1K cred 193 25K 38K204800K 314724 0 0 128 subproc 169 11K 23K204800K 646965 0 0 32,64,256 proc 2 8K 8K204800K 2 0 0 4K session 18 2K 2K204800K 236 0 0 64 pgrp 18 1K 1K204800K 524 0 0 32 ip6ndp 1 1K 1K204800K 3 0 0 64,512 temp 375 99K 128K204800K 380712 0 0 16,32,64,128,256, 512,1K,2K,4K,128K devbuf 438 348K 348K204800K 10670 0 0 16,32,64,128,256, 512,1K,2K,4K,16K,32K lockf 3 1K 1K204800K 11617 0 0 64 atexit 1 1K 1K204800K 1 0 0 16 zombie 5 1K 3K204800K 323293 0 0 128 proc-args 58 5K 15K204800K 311493 0 0 16,32,64,128,256 sigio 1 1K 1K204800K 1 0 0 32 file 160 10K 33K204800K 2227982 0 0 64 file desc 76 20K 90K204800K 327851 0 0 256,512 dev_t 619 78K 78K204800K 619 0 0 128 timecounter 10 2K 2K204800K 10 0 0 128 Memory Totals: In Use Free Requests 15063K 174K 7575053 ZONE used total mem-use PIPE 31 306 4/47K SWAPMETA 0 0 0/0K unpcb 4 128 0/8K ripcb 0 21 0/3K tcpcb 237 735 125/390K udpcb 35 84 6/15K tcpcb 0 0 0/0K socket 276 798 51/149K KNOTE 0 128 0/8K NFSNODE 89972 90000 28116/28125K NFSMOUNT 26 35 13/18K VNODE 91584 91584 17172/17172K NAMEI 0 32 0/32K VMSPACE 75 256 14/48K PROC 79 245 32/99K DP fakepg 0 0 0/0K PV ENTRY 28489 524263 778/14335K MAP ENTRY 791 2253 37/105K KMAP ENTRY 598 978 28/45K MAP 7 10 0/1K VM OBJECT 56500 57040 5296/5347K ------------------------------------------ TOTAL 51679/65954K Yup, about the same place, 90megs. vfs.vmiodirenable=1 is set. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 18:17:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id A7A1137B405 for ; Mon, 25 Jun 2001 18:17:36 -0700 (PDT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id SAA02837; Mon, 25 Jun 2001 18:15:45 -0700 (PDT) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200106260115.SAA02837@gndrsh.dnsmgr.net> Subject: Re: Staying *really stable* in FreeBSD In-Reply-To: <20010622162922F.jkh@osd.bsdi.com> from Jordan Hubbard at "Jun 22, 2001 04:29:22 pm" To: jkh@osd.bsdi.com (Jordan Hubbard) Date: Mon, 25 Jun 2001 18:15:45 -0700 (PDT) Cc: netch@iv.nn.kiev.ua, mwm@mired.org, davep@who.net, freebsd-stable@FreeBSD.ORG 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-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Moreover, I know a man which says that the last Really Stable release > > was 1.1.5.1. > > Ah, tell Rod I said Hi! ;-) You told him yourself... :-) Hi Jordan, and good luck in the new job with Apple! Ohhh.. and the oldest thing I run is 3.2. Legally I can still use 1.x for my own purposes, but I can't give it to anyone :-(. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 18:19:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.noos.fr (camus.noos.net [212.198.2.70]) by hub.freebsd.org (Postfix) with ESMTP id BC43737B40C for ; Mon, 25 Jun 2001 18:19:05 -0700 (PDT) (envelope-from clefevre@redirect.to) Received: (qmail 8757483 invoked by uid 0); 26 Jun 2001 01:19:04 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.231.187]) (envelope-sender ) by 212.198.2.70 (qmail-ldap-1.03) with SMTP for ; 26 Jun 2001 01:19:04 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.4/8.11.4) id f5Q1J3P45305; Tue, 26 Jun 2001 03:19:03 +0200 (CEST) (envelope-from clefevre@redirect.to) To: freebsd-stable@freebsd.org Cc: freebsd-current@freebsd.org Subject: please, commit thoses PR X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C Reply-To: Cyrille Lefevre Mail-Copies-To: never From: Cyrille Lefevre Date: 26 Jun 2001 03:19:02 +0200 Message-ID: Lines: 34 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, by order fo importance, sendmail.cf is missing some STARTTLS support http://www.FreeBSD.org/cgi/query-pr.cgi?pr=28361 (w/o this one, depending on the provider, mails aren't can't go out...) make sysinstall ask for the keymap at installation time http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27483 (this one is important for, at least, french users, since Q and A key are inverted and may cause damages at instalation time using fdisk) well, not so important, thoses are waiting for month right now... add -c for grand total to df(1), like du(1) does http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19635 (just for memory) skeyaccess(3) doesn't for primary group http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22212 (ditto) thanks. To -stable CC -current Cyrille. -- home: mailto:clefevre@redirect.to UNIX is user-friendly; it's just particular work: mailto:Cyrille.Lefevre@edf.fr about who it chooses to be friends with. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 19:14: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B97F237B406 for ; Mon, 25 Jun 2001 19:14:00 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f5Q2Dv235248; Mon, 25 Jun 2001 19:13:57 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f5Q2Du388478; Mon, 25 Jun 2001 19:13:56 -0700 (PDT) (envelope-from jdp) Date: Mon, 25 Jun 2001 19:13:56 -0700 (PDT) Message-Id: <200106260213.f5Q2Du388478@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: juha@saarinen.org Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , Juha Saarinen wrote: > On Mon, 25 Jun 2001, Scott Lambert wrote: > > > It should have been cleared up by now with a nightly cvsup. Mine boxes just > > had the two instances where they downloaded all the libpam stuff. After that, > > it was business as usual. > > > > So, are you saying you get to download those files each time you cvsup? > > > > Have you tried deleting those files from your source tree? > > No, that's what I was wondering as well, if I could just rm the offending > files. Yes, you can do that if you are not using the "-s" option on your cvsup command. But it should not be necessary. > Anyway, just checked the daily output logs on the affected systems, and > the problem seems to have gone away now. Good. When it says it will send the whole file, that should clear up any kind of problem. Note, however, that these fixups happen at the very end of the cvsup run. If you kill it before it finishes, you'll get the same thing on the next run. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 19:16: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 089DC37B407 for ; Mon, 25 Jun 2001 19:16:04 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15EiOW-0001VO-00; Tue, 26 Jun 2001 14:16:00 +1200 Date: Tue, 26 Jun 2001 14:16:00 +1200 (NZST) From: Juha Saarinen To: John Polstra Cc: "stable@freebsd.org" Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: <200106260213.f5Q2Du388478@vashon.polstra.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Jun 2001, John Polstra wrote: > Good. When it says it will send the whole file, that should clear > up any kind of problem. Note, however, that these fixups happen at > the very end of the cvsup run. If you kill it before it finishes, > you'll get the same thing on the next run. Ahh... at the very end, you say? I wonder if this is due to the jakarta-tomcat thing? Noticed that 'make update' would bomb out because it couldn't delete that Port of Infamy ;-) -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 19:23:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3278D37B405 for ; Mon, 25 Jun 2001 19:23:06 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f5Q2N2235317; Mon, 25 Jun 2001 19:23:02 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f5Q2N2Y88522; Mon, 25 Jun 2001 19:23:02 -0700 (PDT) (envelope-from jdp) Date: Mon, 25 Jun 2001 19:23:02 -0700 (PDT) Message-Id: <200106260223.f5Q2N2Y88522@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: juha@saarinen.org Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article , Juha Saarinen wrote: > On Mon, 25 Jun 2001, John Polstra wrote: > > > Good. When it says it will send the whole file, that should clear > > up any kind of problem. Note, however, that these fixups happen at > > the very end of the cvsup run. If you kill it before it finishes, > > you'll get the same thing on the next run. > > Ahh... at the very end, you say? I wonder if this is due to the > jakarta-tomcat thing? Noticed that 'make update' would bomb out because it > couldn't delete that Port of Infamy ;-) Yep, that would explain it. That jakarta-tomcat thing is going to be the death of me. :-( The "checksum mismatch ..." message is a "should not happen" kind of scenario. It only happens if (a) somebody manually dinked around with the repository files [this case], or (b) somebody manually dinked around with the local files in a very devious way without changing the timestamp, or (c) some internal CVSup error happened. I am not aware of any occurrances of (c) for several years. Anyway, by the time it detects the checksum mismatch, the best it can do is make a note to fix things up at the end. If you kill it (or it dies) before then, the offending file will be unchanged on your machine (i.e., your original version before the update run) and the checksum mismatch will happen again next time. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 20:54:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xyzzy.intranet.snsonline.net (dhcp.looksmart.com.au [202.53.47.178]) by hub.freebsd.org (Postfix) with ESMTP id 122A937B406 for ; Mon, 25 Jun 2001 20:54:35 -0700 (PDT) (envelope-from msergeant@snsonline.net) Received: from xyzzy.intranet.snsonline.net (localhost [127.0.0.1]) by xyzzy.intranet.snsonline.net (8.11.4/8.11.3) with SMTP id f5Q3s0m00851; Tue, 26 Jun 2001 13:54:02 +1000 (EST) (envelope-from msergeant@snsonline.net) Message-Id: <200106260354.f5Q3s0m00851@xyzzy.intranet.snsonline.net> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 From: "Mark Sergeant" To: Thomas David Rivers , freebsd-stable@FreeBSD.ORG Subject: Re: Sound (AC'97) too fast??? X-Mailer: Pronto v2.2.5 On freebsd/mysql Date: 25 Jun 2001 22:53:53 EST Reply-To: "Mark Sergeant" In-Reply-To: <200106250219.f5P2J8r00678@gateway.dignus.com> References: <200106250219.f5P2J8r00678@gateway.dignus.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I to have problems with the ich.c driver but it plays mp3's ok. The main problem is sound in games is extremely delayed. Playing DVD's the sound is useless as well. The best thing to do is live with it for now or rewrite some of the driver... which I personally am unable to do so will live with it and be thankful I can play DVD's Cheers, Mark On Sun, 24 Jun 2001 22:19:08 -0400 (EDT), Thomas David Rivers said: -snip- > > But - can anyone let me know how to reign this beastie in? > > - Thanks! - > - Dave Rivers - > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > -- Mark Sergeant Unix Systems Administrator Fortune follows... Good leaders being scarce, following yourself is allowed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 21: 1: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from zaapth.twnet.org (mcns152.docsis147.singa.pore.net [202.156.147.152]) by hub.freebsd.org (Postfix) with ESMTP id CBAF537B405 for ; Mon, 25 Jun 2001 21:01:02 -0700 (PDT) (envelope-from twchan@singnet.com.sg) Received: from localhost (twchan@localhost) by zaapth.twnet.org (8.11.3/8.11.3) with ESMTP id f5Q3tHl07527 for ; Tue, 26 Jun 2001 11:55:17 +0800 (SGT) (envelope-from twchan@singnet.com.sg) X-Authentication-Warning: zaapth.twnet.org: twchan owned process doing -bs Date: Tue, 26 Jun 2001 11:55:17 +0800 (SGT) From: Chan Tur Wei X-X-Sender: To: Subject: Re: Still getting "Checksum mismatch" etc. In-Reply-To: <200106260223.f5Q2N2Y88522@vashon.polstra.com> Message-ID: <20010626114744.A7501-100000@zaapth.twnet.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Jun 2001, John Polstra wrote: > Date: Mon, 25 Jun 2001 19:23:02 -0700 (PDT) > From: John Polstra > To: stable@FreeBSD.ORG > Cc: juha@saarinen.org > Subject: Re: Still getting "Checksum mismatch" etc. > > In article , > Juha Saarinen wrote: > > On Mon, 25 Jun 2001, John Polstra wrote: > > > > > Good. When it says it will send the whole file, that should clear > > > up any kind of problem. Note, however, that these fixups happen at > > > the very end of the cvsup run. If you kill it before it finishes, > > > you'll get the same thing on the next run. > > > > Ahh... at the very end, you say? I wonder if this is due to the > > jakarta-tomcat thing? Noticed that 'make update' would bomb out because= it > > couldn't delete that Port of Infamy ;-) > > Yep, that would explain it. That jakarta-tomcat thing is going to > be the death of me. :-( > > The "checksum mismatch ..." message is a "should not happen" kind of > scenario. It only happens if (a) somebody manually dinked around with > the repository files [this case], or (b) somebody manually dinked > around with the local files in a very devious way without changing > the timestamp, or (c) some internal CVSup error happened. I am not > aware of any occurrances of (c) for several years. Anyway, by the > time it detects the checksum mismatch, the best it can do is make a > note to fix things up at the end. If you kill it (or it dies) before > then, the offending file will be unchanged on your machine (i.e., your > original version before the update run) and the checksum mismatch will > happen again next time. > > John > -- > John Polstra jdp@polstra.= com > John D. Polstra & Co., Inc. Seattle, Washington = USA > "Disappointment is a good sign of basic intelligence." -- Ch=F6gyam Tr= ungpa > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > Hi, In my previous cvsup run, on June 20, I had loads of those "checksum mismatch" errors; most of which had to do with some pam stuff. The system built and ran, though. Unfortunately I'd zapped the cvsup log; so I don't have exactly which were the files. I don't remember which server I cvsup'ed from... I think it was cvsup10.freebsd.org or so. A new cvsup today (June 26) from cvsup2.freebsd.org had no more of those errors, so I suppose things are right again. Regards -T.W.Chan- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 23:14:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 9D3F737B401 for ; Mon, 25 Jun 2001 23:14:36 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.3/8.11.2) id f5Q6EVd20304; Mon, 25 Jun 2001 23:14:31 -0700 (PDT) (envelope-from dillon) Date: Mon, 25 Jun 2001 23:14:31 -0700 (PDT) From: Matt Dillon Message-Id: <200106260614.f5Q6EVd20304@earth.backplane.com> To: Christoph Splittgerber Cc: freebsd-stable@FreeBSD.ORG Subject: Re: indefinite wait buffer ? References: <3B376016.7258B474@sdata.de> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Hallo, : :found this in the /var/log/messages: :iguana /kernel: swap_pager: indefinite wait buffer: device: #ad/0x20001, :blkno: 11520, size: 8192 : :... and I'm trying to find out what might cause an error like this. Is this a :physically bad block on the swap device? Before I start digging into the :sources, can somebody point me in the right direction please. : :Thanks in advance, : :Christoph It depends how persistent it is... if the message is being generated over and over again (every 20 seconds or so), then it is either a hard error on the disk or a bug in the kernel. If the message appeared once it is more likely that your HD was overloading doing something else and the pagein's read request could not be handled within 20 seconds or so, but then recovered. You could also check to see if you have any processes stuck in the 'swread' state, using 'ps axl'. If not whatever it was recovered. If so you may have a stuck process looping waiting for a pagein from somewhere. Any disk error would also be reported in /var/log/messages. If you don't see any disk-specific read errors then the disk is probably just fine. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 23:36:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by hub.freebsd.org (Postfix) with ESMTP id 4F99037B401 for ; Mon, 25 Jun 2001 23:36:29 -0700 (PDT) (envelope-from ertr1013@student.uu.se) Received: from d1o913.telia.com (d1o913.telia.com [195.252.44.241]) by mailc.telia.com (8.11.2/8.11.0) with ESMTP id f5Q6aRl04098 for ; Tue, 26 Jun 2001 08:36:27 +0200 (CEST) Received: from ertr1013.student.uu.se (h185n2fls20o913.telia.com [212.181.163.185]) by d1o913.telia.com (8.8.8/8.8.8) with SMTP id IAA18370 for ; Tue, 26 Jun 2001 08:36:27 +0200 (CEST) Received: (qmail 85681 invoked by uid 1001); 26 Jun 2001 06:35:52 -0000 Date: Tue, 26 Jun 2001 08:35:51 +0200 From: Erik Trulsson To: steve.d.meacham@mail.sprint.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Best time to cvsup -STABLE Message-ID: <20010626083551.A85668@student.uu.se> Mail-Followup-To: steve.d.meacham@mail.sprint.com, freebsd-stable@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.19i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jun 25, 2001 at 05:02:09PM -0500, steve.d.meacham@mail.sprint.com wrote: > I'd like to know if there is a time window where -STABLE is most likely > to not be getting updated. This should allow us to avoid grabbing and > building source that by chance has some changes only partially checked > in and then getting strange behaviour or build errors. > > I heard mention on this list that there should be such a window but I'm > not certain if there is one or not. There is not really any such time, no. You might analyze the commitlogs and see if there is any particular time when there is a low number of commits usually made but I don't think there is. Or you might just read the cvs-all list and see if there is anything special going on at the moment. Works for me. Note that there are committers working from (among other places) Europe, Japan, and North America which means that there is somebody awake and active 24 hours a day more or less. -- Erik Trulsson ertr1013@student.uu.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 25 23:46:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from net2.dinoex.sub.org (net2.dinoex.de [212.184.201.182]) by hub.freebsd.org (Postfix) with ESMTP id DD6E337B401 for ; Mon, 25 Jun 2001 23:46:36 -0700 (PDT) (envelope-from dirk.meyer@dinoex.sub.org) Received: from gate.dinoex.sub.org (dinoex@localhost) by net2.dinoex.sub.org (8.11.4/8.11.3) with BSMTP id f5Q6j7V02529; Tue, 26 Jun 2001 08:45:07 +0200 (CEST) (envelope-from dirk.meyer@dinoex.sub.org) To: freebsd-stable@FreeBSD.ORG, alex@myzona.net Message-ID: From: dirk.meyer@dinoex.sub.org (Dirk Meyer) Organization: privat Subject: Re: Updating OpenSSH on -release Date: Tue, 26 Jun 2001 08:41:54 +0200 X-Mailer: Dinoex 1.77 References: <002501c0fdb0$95e5a320$ea31fea9@parkson> X-Gateway: ZCONNECT gate.dinoex.sub.org [UNIX/Connect 0.91] X-Accept-Language: de,en X-PGP-Fingerprint: 44 16 EC 0A D3 3A 4F 28 8A 8A 47 93 F1 CF 2F 12 X-Noad: Please don't send me ad's by mail. I'm bored by this type of mail. X-Copyright: (C) Copyright 1999 by Dirk Meyer -- All rights reserved. X-Note: sending SPAM is a violation of both german and US law and will at least trigger a complaint at your provider's postmaster. X-PGP-Key-Avail: mailto:pgp-public-keys@keys.de.pgp.net Subject:GET 0x331CDA5D X-ZC-VIA: 20010626000000S+2@dinoex.sub.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alex M wrote: > What I am trying to do is update my OpenSSH from the base system, I am > running 4.2-RELEASE, and I have cvsup'ed the -stable source tree, but I dont > want to make world, just some parts, like openssh. I dont know if its even > recommended, but heres what I am doing: > cd /usr/src/crypto/openssh > make openssh uses a new feature of make, please update your make too. They may be changes in pam too, consider to do a "make world" if you run into such problems. > "Makefile", line 19: Malformed conditional ((${KERBEROS:L} == "yes")) > "Makefile", line 21: Malformed conditional ((${AFS:L} == "yes")) > I guess I am doing something wrong. > Any help would be appreciated. You can try one of the openssh-ports, but they behave a bit diffrent in case of RSA-keys over SSH2 protocol, as the base version does. /usr/ports/security/openshh$ make /usr/ports/security/openshh-portable$ make kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 0:43:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from finland.ispro.net.tr (finland.ispro.net.tr [217.21.68.1]) by hub.freebsd.org (Postfix) with ESMTP id 0D3B537B401 for ; Tue, 26 Jun 2001 00:43:08 -0700 (PDT) (envelope-from yurtesen@ispro.net.tr) Received: from localhost (yurtesen@localhost) by finland.ispro.net.tr (8.11.4/8.11.2) with ESMTP id f5PB14a58951; Mon, 25 Jun 2001 14:01:04 +0300 (EEST) (envelope-from yurtesen@ispro.net.tr) Date: Mon, 25 Jun 2001 14:01:04 +0300 (EEST) From: Evren Yurtesen To: "Sergey N. Voronkov" Cc: Subject: Re: Kerberos: No default realm defined for Kerberos! In-Reply-To: <20010625135723.A83063@sv.tech.sibitex.tmn.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG how can I set a system wide default for that?! I dont like to see that message really! Evren On Mon, 25 Jun 2001, Sergey N. Voronkov wrote: > On Sat, Jun 23, 2001 at 09:39:30PM +0300, Evren Yurtesen wrote: > > Hi > > It is funny but when I make a telnet connection to my Cisco router I > > started to get this message only from a machine I have upgraded recently > > to stable recently! > > > > Kerberos: No default realm defined for Kerberos! > > > > AND It only happens when I connect to Cisco routers and not when I telnet > > to my switch or to my smtp server. > > > > >From all other machines everything is fine. > > > > Why is it so? > > > > Some additional features of telnet protocol are now defaults to each > session (Don't know wath was a reason to do that 8-( ). One of it is > so named "autologin". > > One way to fix: > echo default unset autologin >> ~/.telnetrc > > Second one - use 'telnet -K somehost.somenet'. > > Bye, > > Serg N. Voronkov. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 0:44:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from [192.168.100.19] (smtp.kpnqwest.com [193.242.92.8]) by hub.freebsd.org (Postfix) with ESMTP id E575137B401 for ; Tue, 26 Jun 2001 00:44:37 -0700 (PDT) (envelope-from Marek.Kozlovsky@kpnqwest.com) Received: from ntexghub01.kpnqwest.com (unverified) by (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Tue, 26 Jun 2001 09:44:35 +0200 Received: by ntexghub01 with Internet Mail Service (5.5.2653.19) id ; Tue, 26 Jun 2001 09:44:34 +0200 Message-ID: <31FD3FA70CBED31189E700508B6401712C74DC@ntexgpra01> From: "Kozlovsky, Marek" To: "'freebsd-stable@freebsd.org'" Subject: RE: Problems with Ports Date: Tue, 26 Jun 2001 09:44:29 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, first, I'm not subscribed to -ports, that's why I answer here. > Hello, > > I synced the ports tree yesturday, but am having problems > with 3 ports: > > 1) Mozilla > 2) Minicom > 3) Netscape Navigator I think you can add 4) smbfs buki@xxx:/usr/ports/net/smbfs#make NOTE: SMP support can be enabled by adding "SMP_SUPPORT=yes" to argument of make. ===> Extracting for smbfs-1.4.1 >> Checksum OK for smbfs-1.4.1.tar.gz. ===> Patching for smbfs-1.4.1 ===> Configuring for smbfs-1.4.1 echo PREFIX= /usr/local > config.int echo SYSDIR=/usr/src/sys >> config.int echo KMODDIR=/modules >> config.int echo SINGLEKLD=yes >> config.int echo ENCRYPTED_PASSWD=yes >> config.int ===> Building for smbfs-1.4.1 ===> lib ===> lib/smb Warning: Object directory not changed from original /usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb cc -O -pipe -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../include -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel/mysys -Wall -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel -I/usr/local//usr/include -c rcfile.c -o rcfile.o cc -O -pipe -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../include -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel/mysys -Wall -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel -I/usr/local//usr/include -c ctx.c -o ctx.o cc -O -pipe -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../include -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel/mysys -Wall -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel -I/usr/local//usr/include -c cfopt.c -o cfopt.o cc -O -pipe -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../include -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel/mysys -Wall -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel -I/usr/local//usr/include -c subr.c -o subr.o cc -O -pipe -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../include -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel/mysys -Wall -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel -I/usr/local//usr/include -c nls.c -o nls.o cc -O -pipe -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../include -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel/mysys -Wall -I/usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb/../../kernel -I/usr/local//usr/include -c rap.c -o rap.o rap.c:47: sys/mchain.h: No such file or directory rap.c: In function `smb_rap_getNparam': rap.c:292: warning: implicit declaration of function `letohs' *** Error code 1 Stop in /usr/ports/net/smbfs/work/smbfs-1.4.1/lib/smb. *** Error code 1 Stop in /usr/ports/net/smbfs/work/smbfs-1.4.1/lib. *** Error code 1 Stop in /usr/ports/net/smbfs/work/smbfs-1.4.1. *** Error code 1 Stop in /usr/ports/net/smbfs. *** Error code 1 Stop in /usr/ports/net/smbfs. *** Error code 1 Stop in /usr/ports/net/smbfs. > > > Bye for Now, > > Ian Buki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 1:48:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gscamnlm03.wr.usgs.gov (gscamnlm03.wr.usgs.gov [130.118.4.113]) by hub.freebsd.org (Postfix) with ESMTP id 5345837B401; Tue, 26 Jun 2001 01:48:08 -0700 (PDT) (envelope-from rsowders@usgs.gov) To: Volker Stolz Cc: mujahidin@egypt.net, owner-freebsd-stable@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: CD-RW at ata1-master using PIO4 MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Robert L Sowders" Date: Tue, 26 Jun 2001 01:48:03 -0700 X-MIMETrack: Serialize by Router on gscamnlm03/SERVER/USGS/DOI(Release 5.0.7 |March 21, 2001) at 06/26/2001 01:48:07 AM, Serialize complete at 06/26/2001 01:48:07 AM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yes it can, I even hacked a module for webmin to do just that. Volker Stolz Sent by: owner-freebsd-stable@FreeBSD.ORG 06/25/2001 01:52 AM =20 To: mujahidin@egypt.net, stable@FreeBSD.ORG cc:=20 Subject: Re: CD-RW at ata1-master using PIO4 In local.freebsd-stable, you wrote: > I have a CD-RW (TEAC). Someone to know is it posible to use > cdrecord/mkisofs on it or must be SCSI dev ? cdrecord is only for SCSI on FreeBSD. Use /usr/sbin/burncd. You may find /usr/share/examples/worm/makecdfs.sh helpful, too. > Is there any program that can write cd blanks with this drive ? You mean blanking? 'burncd' can do this, too. --=20 Abstrakte Syntaxtr=E4ume. Volker Stolz * stolz@i2.informatik.rwth-aachen.de * PGP + S/MIME To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 3: 5: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dilbert.firstcallgroup.co.uk (dilbert.firstcallgroup.co.uk [194.203.69.166]) by hub.freebsd.org (Postfix) with ESMTP id 6099637B405 for ; Tue, 26 Jun 2001 03:05:04 -0700 (PDT) (envelope-from pfrench@firstcallgroup.co.uk) Received: from pfrench by dilbert.firstcallgroup.co.uk with local (Exim 3.22 #1) id 15EpiF-00006X-00; Tue, 26 Jun 2001 11:04:51 +0100 To: freebsd-stable@freebsd.org, Marek.Kozlovsky@KPNQwest.com Subject: SMBFS (was RE: Problems with Ports) In-Reply-To: <31FD3FA70CBED31189E700508B6401712C74DC@ntexgpra01> Message-Id: From: Pete French Date: Tue, 26 Jun 2001 11:04:51 +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I think you can add 4) smbfs smbfs builds fine for me here however - there *is* a small problem though in that you cant just 'make install' as it doesnt work. Trying to mount gives the error: mount_smbfs: vfsload(smbfs): No such file or directory The fix is to do a 'make installkernel' *after* the install of smbfs from the ports directory. I guess the port is clobbering some module that it shouldnt somehow. cvsup from around 2.00PM GMT yesterday (this behaves the same on two different machines) -pcf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 3:33:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 4EC0637B401 for ; Tue, 26 Jun 2001 03:33:14 -0700 (PDT) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (localhost [127.0.0.1]) by jfh00.fernuni-hagen.de (8.11.4/8.11.4) with ESMTP id f5QAX9r01888; Tue, 26 Jun 2001 12:33:09 +0200 (CEST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <3B3864E5.B0E6AFF0@fernuni-hagen.de> Date: Tue, 26 Jun 2001 12:33:09 +0200 From: Fritz Heinrichmeyer X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: de, en MIME-Version: 1.0 To: Cheffo Izroda Cc: stable@FreeBSD.ORG Subject: Re: CD-RW at ata1-master using PIO4 References: <200106250839.BAA29241@mail15.bigmailbox.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cheffo Izroda wrote: > > I have a CD-RW (TEAC). Someone to know is it posible to use cdrecord/mkisofs on it or must be SCSI dev ? Is there any program that can write cd blanks with this drive ? > > > > -= Cheffo =- > > ------------------------------------------------------------ > ------------------------------------------------------------ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message try burncd (part of the base system, no port), it worked at home with my medion/hp-9340i drive. -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 7: 7:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fepE.post.tele.dk (fepE.post.tele.dk [195.41.46.137]) by hub.freebsd.org (Postfix) with ESMTP id CBE4037B401 for ; Tue, 26 Jun 2001 07:07:12 -0700 (PDT) (envelope-from mekanix@privat.dk) Received: from mekanix.my.domain ([62.243.77.253]) by fepE.post.tele.dk (InterMail vM.4.01.03.21 201-229-121-121-20010307) with SMTP id <20010626140711.SFPL24149.fepE.post.tele.dk@mekanix.my.domain>; Tue, 26 Jun 2001 16:07:11 +0200 Date: Tue, 26 Jun 2001 16:08:07 +0200 From: Bjarne Wichmann Petersen To: Rasputin Cc: stable@freebsd.org Subject: Re: XFree86-4.1.0+mga+dri+FreeBSD-4.3-stable == hang Message-Id: <20010626160807.6b78cd6b.mekanix@privat.dk> In-Reply-To: <20010625110619.A44348@dogma.freebsd-uk.eu.org> References: <200106140436.OAA20451@hadrian.staff.apnic.net> <20010614141859.B67187@node7.cluster.srrc.usda.gov> <20010625110619.A44348@dogma.freebsd-uk.eu.org> X-Mailer: Sylpheed version 0.4.64 (GTK+ 1.2.10; i386--freebsd4.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Jun 2001 11:06:20 +0100 Rasputin wrote: > you'l get a version of the port that *should* build the dri modules you > need. > You still need to preload agp.ko and mga.ko from /boot/loader.conf, and > load > the dri module in XF86Config , but you should be OK. Pardon me for budding in, but I've read about this "preload agp.ko/mga.ko"-stuff ever since I tried getting XFree 4.0.1 to work. I tried it to end up severely breaking X. The thing is drm/dri works just fine without preloading the kernelmodules (XFree 4.0.3 and STABLE), they seem to be loaded when needed! So why recommend something that isn't really needed? Or am I missing something here? Bjarne To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 7:13:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shaft.techsupport.co.uk (shaft.techsupport.co.uk [212.250.77.214]) by hub.freebsd.org (Postfix) with ESMTP id 347A637B401 for ; Tue, 26 Jun 2001 07:13:24 -0700 (PDT) (envelope-from rasputin@shaft.techsupport.co.uk) Received: from rasputin by shaft.techsupport.co.uk with local (Exim 3.22 #1) id 15EtcV-0005ER-00 for stable@freebsd.org; Tue, 26 Jun 2001 15:15:11 +0100 Date: Tue, 26 Jun 2001 15:15:11 +0100 From: Rasputin To: stable@freebsd.org Subject: Re: XFree86-4.1.0+mga+dri+FreeBSD-4.3-stable == hang Message-ID: <20010626151511.A20100@shaft.techsupport.co.uk> Reply-To: Rasputin Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Bjarne Wichmann Petersen [010626 15:11]: > On Mon, 25 Jun 2001 11:06:20 +0100 > Rasputin wrote: > > > you'l get a version of the port that *should* build the dri modules you > > need. > > You still need to preload agp.ko and mga.ko from /boot/loader.conf, and > > load > > the dri module in XF86Config , but you should be OK. > > Pardon me for budding in, but I've read about this "preload > agp.ko/mga.ko"-stuff ever since I tried getting XFree 4.0.1 to work. I > tried it to end up severely breaking X. > > The thing is drm/dri works just fine without preloading the kernelmodules > (XFree 4.0.3 and STABLE), they seem to be loaded when needed! So why > recommend something that isn't really needed? Or am I missing something > here? Well, I recommended it because I don't know any better :) And it's part of the only 'dri howto' for FreeBSD, but thanks for the advice, I'll try leaving them out. -- "These are the propulsion systems used by NASA for the moonshots," said Tom apologetically. Rasputin :: Jack of All Trades - Master of Nuns :: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 7:50:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail10.bigmailbox.com (mail10.bigmailbox.com [209.132.220.41]) by hub.freebsd.org (Postfix) with ESMTP id C8F9637B406 for ; Tue, 26 Jun 2001 07:50:23 -0700 (PDT) (envelope-from mujahidin@egypt.net) Received: œby mail10.bigmailbox.com (8.8.7/8.8.7) id HAA04036; Tue, 26 Jun 2001 07:50:23 -0700 Date: Tue, 26 Jun 2001 07:50:23 -0700 Message-Id: <200106261450.HAA04036@mail10.bigmailbox.com> Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary X-Mailer: MIME-tools 4.104 (Entity 4.116) Mime-Version: 1.0 X-Originating-Ip: [212.116.158.36] From: "Cheffo Izroda" To: stable@freebsd.org Subject: smbfs Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I try to install smbfs from ports but this error appear : >> smbfs-1.4.1.tar.gz doesn't seem to exist in /usr/ports/distfiles/. >> Attempting to fetch from ftp://ftp.butya.kz/pub/smbfs/. fetch: smbfs-1.4.1.tar.gz: Operation timed out >> Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: smbfs-1.4.1.tar.gz: File unavailable (e.g., file not found, no access) >> Couldn't fetch it - please try to retrieve this >> port manually into /usr/ports/distfiles/ and try again. *** Error code 1 Stop in /share/ports/net/smbfs. *** Error code 1 Then I tray to download manually but in ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/deistfiles/ exist only smbfst-1.3.4.tar.gz OK let's install old version but when I try to do it : root#make ===> kernel/modules ===> kernel/modules/dummy ===> kernel/modules/smbfs2 Warning: Object directory not changed from original /share/cheffo/smbfs-1.3.4/ke rnel/modules/smbfs2 cc -O -pipe -march=pentiumpro -I/share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/ ../../ -I/usr/src/sys -DSMB_CRYPTO -I/share/cheffo/smbfs-1.3.4/kernel/modules/s mbfs2/../../mysys -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-p rototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-e xtensions -ansi -DKLD_MODULE -nostdinc -I- -I/share/cheffo/smbfs-1.3.4/kernel/mo dules/smbfs2/../../ -I/usr/src/sys -I/share/cheffo/smbfs-1.3.4/kernel/modules/sm bfs2/../../mysys -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /share/ cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c : In function `iconv_xlat_lookup': /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :37: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :38: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :39: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c : In function `iconv_xlat_register_table': /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :51: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :51: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :53: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :53: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :53: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c : In function `iconv_xlat_unregister_table': /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :60: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :60: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :60: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :60: dereferencing pointer to incomplete type /share/cheffo .... and so on and ends with: :238: dereferencing pointer to incomplete type /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2/../../mysys/libkern/iconv_xlat.c :238: dereferencing pointer to incomplete type *** Error code 1 Stop in /share/cheffo/smbfs-1.3.4/kernel/modules/smbfs2. *** Error code 1 Stop in /share/cheffo/smbfs-1.3.4/kernel/modules. *** Error code 1 Stop in /share/cheffo/smbfs-1.3.4. So must I to precompile my KERNEL with : options NETSMB options NETSMBCRYPTO options SMBFS or the problem is not here? Regards, Cheffo P.S. I Have FreeBSD 4.3 -stable (updated before a week) -= Cheffo =- ------------------------------------------------------------ ------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 9:53:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from woody.ichilton.co.uk (woody.ichilton.co.uk [216.29.174.40]) by hub.freebsd.org (Postfix) with ESMTP id CA1A937B405 for ; Tue, 26 Jun 2001 09:53:32 -0700 (PDT) (envelope-from ian@woody.ichilton.co.uk) Received: by woody.ichilton.co.uk (Postfix, from userid 1000) id 46B007D1C; Tue, 26 Jun 2001 17:53:31 +0100 (BST) Date: Tue, 26 Jun 2001 17:53:31 +0100 From: Ian Chilton To: freebsd-stable@freebsd.org Subject: Mozilla Problem Message-ID: <20010626175331.A32636@woody.ichilton.co.uk> Reply-To: Ian Chilton Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.13i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Further to the last message, I tried again and got a different error: c++ -o BooleanExpr.o -c -DOSTYPE=\"FreeBSD4\" -DOSARCH=\"FreeBSD\" -DOJI -I../../../../dist/include -I../../../../dist/include -I/usr/ports/www/mozilla/work/mozilla/dist/include/nspr -I/usr/local/include -I/usr/local/include -I./../base -I./../xml -I./../xml/dom -I./../xml/util -I./../xslt -I./../xslt/util -I./../xslt/functions -I. -I/usr/X11R6/include -fPIC -I/usr/X11R6/include -I/usr/X11R6/include -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Wbad-function-cast -Wcast-align -Woverloaded-virtual -Wsynth -Wno-long-long -O -pipe -pipe -O -DNDEBUG -DTRIMMED -I/usr/X11R6/include -I/usr/X11R6/include -DMOZILLA_CLIENT -include ../../../../config-defs.h BooleanExpr.cpp In file included from /usr/include/g++/iostream.h:31, from ../base/TxString.h:33, from Expr.h:36, from BooleanExpr.cpp:40: /usr/include/g++/streambuf.h: In method `void ios::setstate(int)': /usr/include/g++/streambuf.h:216: implicit declaration of function `int _throw_failwre(...)' gmake[4]: *** [BooleanExpr.o] Error 1 gmake[4]: Leaving directory `/usr/ports/www/mozilla/work/mozilla/extensions/transformiix/source/xpath' gmake[3]: *** [install] Error 2 gmake[3]: Leaving directory `/usr/ports/www/mozilla/work/mozilla/extensions/transformiix/source' gmake[2]: *** [install] Error 2 gmake[2]: Leaving directory `/usr/ports/www/mozilla/work/mozilla/extensions/transformiix' gmake[1]: *** [install] Error 2 gmake[1]: Leaving directory `/usr/ports/www/mozilla/work/mozilla/extensions' gmake: *** [install] Error 2 *** Error code 2 Stop in /usr/ports/www/mozilla. *** Error code 1 Stop in /usr/ports/www/mozilla. *** Error code 1 Stop in /usr/ports/www/mozilla. Any ideas? Thanks Bye for Now, Ian \|||/ (o o) /-----------------------------ooO-(_)-Ooo----------------------------\ | Ian Chilton E-Mail: ian@ichilton.co.uk | | IRC Nick: GadgetMan Backup: ichilton@www.linux.org.uk | | ICQ: 16007717 / 104665842 Web : http://www.ichilton.co.uk | |--------------------------------------------------------------------| | For people who like peace and quiet: a phoneless cord | \--------------------------------------------------------------------/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 10:39: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from marble.sentex.ca (ns2.sentex.ca [199.212.134.2]) by hub.freebsd.org (Postfix) with ESMTP id 03A6F37B406 for ; Tue, 26 Jun 2001 10:38:54 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by marble.sentex.ca (8.11.1/8.11.1) with ESMTP id f5QHcmn36485 for ; Tue, 26 Jun 2001 13:38:48 -0400 (EDT) Message-Id: <5.1.0.14.0.20010626132049.04048e40@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 26 Jun 2001 13:32:51 -0400 To: freebsd-stable@freebsd.org From: Mike Tancsa Subject: More fxp problems (Different ?) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a stange one. It seems like a hardware issue as the same two nics on a 815 or 440BX chipset did have these problems. MB is an Asus CUV-4x-e Via82ct chipset 686b. Cards are 1 2940U 1 3Ware 2 port RAID-1 config (6x000 series) 2 Intel nics, both show inphy1: on miib inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto and both are from the same box. In short, all these parts do not play well together. If I pull the two nics and put in cheap old RealTeks the box works fine enough. But with the Intels (I have tried manual IRQs, auto, changing the slot order etc), I still get the nics locking up on a consistent basis. I even tried a card that was made a few years ago, but same results. Jun 26 08:52:02 granite /kernel: Timecounter "i8254" frequency 1193182 Hz Jun 26 08:52:02 granite /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (870.58-MHz 686-class CPU) Jun 26 08:52:02 granite /kernel: Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Jun 26 08:52:02 granite /kernel: Features=0x383f9ff un 26 08:52:02 granite /kernel: npx0: INT 16 interface Jun 26 08:52:02 granite /kernel: pcib0: on motherboard Jun 26 08:52:02 granite /kernel: pci0: on pcib0 Jun 26 08:52:02 granite /kernel: pcib2: at device 1.0 on pci0 Jun 26 08:52:02 granite /kernel: pci1: on pcib2 Jun 26 08:52:02 granite /kernel: isab0: at device 4.0 on pci0 Jun 26 08:52:02 granite /kernel: isa0: on isab0 Jun 26 08:52:02 granite /kernel: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 Jun 26 08:52:02 granite /kernel: ata0: at 0x1f0 irq 14 on atapci0 Jun 26 08:52:02 granite /kernel: ata1: at 0x170 irq 15 on atapci0 Jun 26 08:52:02 granite /kernel: pci0: at 4.2 irq 10 Jun 26 08:52:02 granite /kernel: pci0: at 4.3 irq 10 I have a very similar mix of parts in my news server and I have never seen this happen on the 440BX chipset. Is it something specific to the Via or this combo ? The errors were happening at 100 and 10Mb with various duplex settings. A few times the NIC totally locked up and I had to reboot the machine to recover. Jun 26 06:25:11 granite /kernel: fxp1: device timeout Jun 26 06:25:11 granite /kernel: fxp1: SCB timeout: 0x60, 0x0, 0x0 0x0 Jun 26 06:25:11 granite /kernel: fxp1: SCB timeout: 0x6, 0x0, 0x0 0x0 Jun 26 06:25:11 granite /kernel: fxp1: SCB timeout: 0x40, 0x0, 0x0 0x0 Jun 26 06:25:11 granite /kernel: fxp1: DMA timeout Jun 26 06:25:12 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 Jun 26 06:25:12 granite /kernel: fxp1: DMA timeout Jun 26 06:25:12 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 Jun 26 06:25:12 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 Jun 26 06:25:17 granite /kernel: fxp1: SCB timeout: 0x1, 0x0, 0x0 0x400 Jun 26 06:25:19 granite /kernel: fxp1: SCB timeout: 0x81, 0x0, 0x0 0x400 Jun 26 06:25:31 granite /kernel: fxp1: device timeout Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x60, 0x0, 0x0 0x0 Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x6, 0x0, 0x0 0x0 Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x40, 0x0, 0x0 0x0 Jun 26 06:25:31 granite /kernel: fxp1: DMA timeout Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 Jun 26 06:25:31 granite /kernel: fxp1: DMA timeout Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 Jun 26 08:39:46 granite /kernel: fxp1: Ethernet address 00:d0:b7:92:32:b4 Jun 26 08:40:09 granite /kernel: fxp1: device timeout Jun 26 08:40:24 granite /kernel: arp: 199.212.134.2 is on fxp1 but got reply from 00:90:27:b0:35:21 on fxp0 Jun 26 08:40:32 granite /kernel: fxp1: device timeout Jun 26 08:41:04 granite /kernel: fxp1: device timeout Jun 26 08:47:04 granite /kernel: fxp0: port 0xb400-0xb43f mem 0xfa000000-0xfa0fffff,0xfa800000-0xfa800fff irq 7 at device 9.0 on pci0 Jun 26 08:47:04 granite /kernel: fxp0: Ethernet address 00:d0:b7:92:32:b4 Jun 26 08:47:27 granite /kernel: fxp0: device timeout Jun 26 08:47:51 granite /kernel: fxp0: device timeout Jun 26 08:48:14 granite /kernel: fxp0: device timeout To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 13:21:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.targetnet.com (smtp.targetnet.com [205.150.0.125]) by hub.freebsd.org (Postfix) with ESMTP id 794E337B401; Tue, 26 Jun 2001 13:21:39 -0700 (PDT) (envelope-from tstrike@targetnet.com) Received: from gw-101.tor1.targetnet.com ([149.99.36.66] helo=wrk150) by smtp.targetnet.com with smtp (Exim 3.16 #1) id 15EzL8-000MQ1-00; Tue, 26 Jun 2001 16:21:39 -0400 From: "Tim Strike" To: "Freebsd-Stable" , Cc: "Brandon Gale" , Subject: mly driver ++ dell powervault 210S ++ eXtremeRaid 2000 Date: Tue, 26 Jun 2001 16:21:00 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike (& Folks), We've recently installed an eXtremeRaid 2000 with our dell powervault 210S (12 drives, only 11 allocated), running under FreeBSD 4.3. The driver appears to work okay, except during boot up. While booting, it looks at 3:15 consistently (3:15 is the controller of the PV210S), says that is is gone, sometimes marks it offline (and othertimes throws up some diagnostic information), and then pauses... for 2+ minutes. Then it boots, and everything operates normally. We didn't have this problem in our previous setup (with the DAC1100 and the mlx driver, everything worked fine). Does anyone know why it's pausing, and a way to avoid it? I have attempted to include the important information, if anything else is needed please let me know. -t. > uname -a FreeBSD cc-301.tor3.targetnet.pvt 4.3-STABLE-20010529-JPSNAP FreeBSD 4.3-STABLE-20010529-JPSNAP #0: Fri Jun 22 17:04:17 GMT 2001 root@:/usr/src/sys/compile/kernel.conf i386 > dmesg | grep mly mly0: port 0xec80-0xecff mem 0xf0000000-0xf3ffffff,0xf8000000-0xf9ffffff irq 2 at device 8.0 on pci1 mly0: eXtremeRAID 2000, 4 channels, firmware 6.00-9-00 (20010412), 64MB RAM mly0: physical device 3:15 gone mly0: enclosure 15 unit 0 access offlinemly0: physical device 3:15 gone mly0: physical device 3:15 gone mly0: physical device 3:15 gone mly0: physical device 3:15 gone da0 at mly0 bus 4 target 0 lun 0 da1 at mly0 bus 4 target 1 lun 0 [fyi: it "pauses" after the last mly0 line -- when it continues, it starts with the da0 line] -- Tim Strike (tstrike@targetnet.com) Director of Architecture, TargetNet Inc. T: +1 416 306 0466 extension 903 F: +1 416 306 0452 This information is confidential and for the exclusive use of the person to whom it is addressed. If you are not the intended recipient, please advise us by e-mail and destroy or return to us any copies. Targetnet accepts no liability for use by third parties or for errors or omissions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 14: 8: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 1FE7737B405 for ; Tue, 26 Jun 2001 14:07:59 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id OAA10045; Tue, 26 Jun 2001 14:06:50 -0700 (MST) (envelope-from chad) Date: Tue, 26 Jun 2001 14:06:50 -0700 From: "Chad R. Larson" To: Jordan Hubbard Cc: juha@saarinen.org, joe@zircon.seattle.wa.us, stable@FreeBSD.ORG Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010626140650.B9911@freeway.dcfinc.com> References: <15157.11221.593513.478892@zircon.zircon.seattle.wa.us> <00cf01c0fc40$c0348db0$0a01a8c0@den2> <20010624023403R.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010624023403R.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Sun, Jun 24, 2001 at 02:34:03AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jun 24, 2001 at 02:34:03AM -0700, Jordan Hubbard wrote: > From: "Juha Saarinen" > Subject: RE: Staying *really stable* in FreeBSD > Date: Sun, 24 Jun 2001 12:00:59 +1200 > >> "19.2.2.2. Who needs FreeBSD-STABLE? >> If you are a commercial user or someone who puts maximum stability of >> their FreeBSD system before all other concerns, you should consider >> tracking FreeBSD-STABLE. This is especially true if you have installed > > It's probably time to rewrite that paragraph substantially. It was > something of a tactical error to encourage certain interest groups to > run "work in progress" code, even if that work is very carefully > bounded and kept "in progress" for the shortest periods possible. I've been using FreeBSD, and reading the mailing lists since around 2.0.5, and this discussion comes up about three times a year. Each time the Powers That Be agressively reject the solution most obvious to someone not a PTB, which is to rename these branches. There have got to be several choices that more accurately reflect what the branches are used for, and that wouldn't confuse the newly converted. Actually, -CURRENT is "development" and -STABLE is "QA/BETA" and -RELEASE is what most folks would think of as "stable". So, why don't we name them like that? I wouldn't have a problem with -DEVEL, -BETA, -RELEASE, and perhaps putting -STABLE on the new RELENG_X_Y branch. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 14:12:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 585FA37B407 for ; Tue, 26 Jun 2001 14:12:18 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id OAA10072; Tue, 26 Jun 2001 14:11:13 -0700 (MST) (envelope-from chad) Date: Tue, 26 Jun 2001 14:11:13 -0700 From: "Chad R. Larson" To: Jordan Hubbard Cc: juha@saarinen.org, joe@zircon.seattle.wa.us, stable@FreeBSD.ORG Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010626141113.C9911@freeway.dcfinc.com> References: <15157.11221.593513.478892@zircon.zircon.seattle.wa.us> <00cf01c0fc40$c0348db0$0a01a8c0@den2> <20010624023403R.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010624023403R.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Sun, Jun 24, 2001 at 02:34:03AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jun 24, 2001 at 02:34:03AM -0700, Jordan Hubbard wrote: > As I said at the beginning, perhaps it's time to simply re-write the > Handbook paragraph which inadvertently "sells" -stable as a solution > for certain types of problems it was never meant to solve. Yes, the handbook paragraph was clearly written to suggest that if you run a production machine you should track -STABLE **in leiu of -CURRENT**, not as a general rule. That is, if you chose to track anything at all, it should be -STABLE. That should be easy to clarify. > - Jordan -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 14:36: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id C630637B405 for ; Tue, 26 Jun 2001 14:35:57 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15F0Tt-0002Az-00; Wed, 27 Jun 2001 09:34:45 +1200 Date: Wed, 27 Jun 2001 09:34:45 +1200 (NZST) From: Juha Saarinen To: "Chad R. Larson" Cc: Jordan Hubbard , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" Subject: Re: Staying *really stable* in FreeBSD In-Reply-To: <20010626140650.B9911@freeway.dcfinc.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 26 Jun 2001, Chad R. Larson wrote: > Actually, -CURRENT is "development" and -STABLE is "QA/BETA" and > -RELEASE is what most folks would think of as "stable". So, why > don't we name them like that? I wouldn't have a problem with > -DEVEL, -BETA, -RELEASE, and perhaps putting -STABLE on the new > RELENG_X_Y branch. I think that would clear up a lot of the confusion. It's kind of hard to accept that -STABLE doesn't necessarily mean "stable" (currently), if you see what I mean ;-). For a production environment, you'd install -RELEASE, and then apply the "hotfixes" which are part of -STABLE (ie. RELENG_X_Y); makes sense to me. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 15:52:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (dhcp44-21.dis.org [216.240.44.21]) by hub.freebsd.org (Postfix) with ESMTP id 0632937B405; Tue, 26 Jun 2001 15:52:14 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f5QN4J901604; Tue, 26 Jun 2001 16:04:20 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106262304.f5QN4J901604@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Tim Strike" Cc: "Freebsd-Stable" , msmith@FreeBSD.ORG, "Brandon Gale" , aschmidt@targetnet.com Subject: Re: mly driver ++ dell powervault 210S ++ eXtremeRaid 2000 In-reply-to: Your message of "Tue, 26 Jun 2001 16:21:00 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 Jun 2001 16:04:19 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is due to me trying to be smart and make the passthrough SCSI interface the default for this driver. Enclosure management controllers really mess things up. Unfortunately, I don't have a managed enclosure, so I can't test with one. 8( There is a driver at http://people.freebsd.org/~msmith/RAID/mylex/mly-20010618.tar.gz that should solve your problems. I have some issues to resolve with drives going away/coming back, but I'll be trying to get it into the tree sometime in the next couple of weeks. Please let me know if this helps. Regards, Mike > We've recently installed an eXtremeRaid 2000 with our dell powervault 210S > (12 drives, only 11 allocated), running under FreeBSD 4.3. The driver > appears to work okay, except during boot up. While booting, it looks at > 3:15 consistently (3:15 is the controller of the PV210S), says that is is > gone, sometimes marks it offline (and othertimes throws up some diagnostic > information), and then pauses... for 2+ minutes. Then it boots, and > everything operates normally. We didn't have this problem in our previous > setup (with the DAC1100 and the mlx driver, everything worked fine). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 16:15:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cokane.org (ip-216-23-48-4.adsl.one.net [216.23.48.4]) by hub.freebsd.org (Postfix) with ESMTP id ED8F437B405 for ; Tue, 26 Jun 2001 16:15:47 -0700 (PDT) (envelope-from cokane@cokane.org) Received: (from cokane@localhost) by cokane.org (8.11.4/8.11.4) id f5RBIG620819; Wed, 27 Jun 2001 07:18:16 -0400 (EDT) (envelope-from cokane) Date: Wed, 27 Jun 2001 07:18:16 -0400 From: Coleman Kane To: Rasputin Cc: stable@freebsd.org Subject: Re: XFree86-4.1.0+mga+dri+FreeBSD-4.3-stable == hang Message-ID: <20010627071816.A20063@evil.apt> References: <20010626151511.A20100@shaft.techsupport.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010626151511.A20100@shaft.techsupport.co.uk>; from rara.rasputin@virgin.net on Tue, Jun 26, 2001 at 03:15:11PM +0100 X-VIM-Settings: vim:ts=4:sw=4:tw=70: X-Operating-System: FreeBSD evil.apt 5.0-CURRENT FreeBSD 5.0-CURRENT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The reason they must be preloaded is that the kernel has already attached a pcib0 device to the agp0 device if it(agp.ko) is not preloaded. Therefore, you will not be able to get an agp device without it. The reason for preloading the mga/drm drivers is unknown to me, but I assume that it might be possible that they could be grabbed by another device during boot as well. On Tue, Jun 26, 2001 at 03:15:11PM +0100, Rasputin wrote, and it was proclaimed: > * Bjarne Wichmann Petersen [010626 15:11]: > > On Mon, 25 Jun 2001 11:06:20 +0100 > > Rasputin wrote: > > > > > you'l get a version of the port that *should* build the dri modules you > > > need. > > > You still need to preload agp.ko and mga.ko from /boot/loader.conf, and > > > load > > > the dri module in XF86Config , but you should be OK. > > > > Pardon me for budding in, but I've read about this "preload > > agp.ko/mga.ko"-stuff ever since I tried getting XFree 4.0.1 to work. I > > tried it to end up severely breaking X. > > > > The thing is drm/dri works just fine without preloading the kernelmodules > > (XFree 4.0.3 and STABLE), they seem to be loaded when needed! So why > > recommend something that isn't really needed? Or am I missing something > > here? > > Well, I recommended it because I don't know any better :) > And it's part of the only 'dri howto' for FreeBSD, but thanks for the > advice, I'll try leaving them out. > -- > "These are the propulsion systems used by NASA for the moonshots," > said Tom apologetically. > Rasputin :: Jack of All Trades - Master of Nuns :: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 19:52:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from alpha-1.extractionpoint.com (dsl-att1-118-109.sb.101freeway.net [12.44.118.109]) by hub.freebsd.org (Postfix) with ESMTP id 5183D37B407 for ; Tue, 26 Jun 2001 19:52:52 -0700 (PDT) (envelope-from tyrian@alpha-1.extractionpoint.com) Received: from localhost (tyrian@localhost) by alpha-1.extractionpoint.com (8.11.3/8.11.3) with ESMTP id f5R2rFM56327 for ; Tue, 26 Jun 2001 19:53:15 -0700 (PDT) (envelope-from tyrian@alpha-1.extractionpoint.com) Date: Tue, 26 Jun 2001 19:53:15 -0700 (PDT) From: "shaun c. walbridge" To: Message-ID: <20010626195235.V56320-100000@alpha-1.extractionpoint.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 19:53:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from Mail6.nc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 67FFC37B401 for ; Tue, 26 Jun 2001 19:53:14 -0700 (PDT) (envelope-from aa8vb@nc.rr.com) Received: from stealth.dummynet ([24.25.3.190]) by Mail6.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Tue, 26 Jun 2001 22:53:09 -0400 Received: (from rhh@localhost) by stealth.dummynet (8.11.4/8.11.1) id f5R2tur03403 for stable@freebsd.org; Tue, 26 Jun 2001 22:55:56 -0400 (EDT) (envelope-from aa8vb@nc.rr.com) X-Authentication-Warning: stealth.dummynet: rhh set sender to aa8vb@nc.rr.com using -f Date: Tue, 26 Jun 2001 22:55:56 -0400 From: Randall Hopper To: stable@freebsd.org Subject: Re: Problems with mergemaster Message-ID: <20010626225556.A3305@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Garrett Wollman: |Darren Gamble wrote: |> |> I have recently (finally) been able to do a make build/installworld on |> one of my test systems with the Stable tree. |> |> However, mergemaster does not appear to be working properly. ... |> For each file, I get |> |> *** Problem installing ./foo , it will remain to merge by hand | |That's because someone(tm) removed the `-c' options to `install' from |the -stable version of mergemaster, even though the -stable version of |`install' still needs them. Is there a work-around for this? I supped stable Monday and also saw this. Thanks, Randall -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 21:21:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail3.sdc1.sfba.home.com (femail3.sdc1.sfba.home.com [24.0.95.83]) by hub.freebsd.org (Postfix) with ESMTP id 5899637B405 for ; Tue, 26 Jun 2001 21:21:08 -0700 (PDT) (envelope-from sjr@home.com) Received: from cc158233-a.catv1.md.home.com ([24.3.25.17]) by femail3.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010627042107.VUAV4013.femail3.sdc1.sfba.home.com@cc158233-a.catv1.md.home.com> for ; Tue, 26 Jun 2001 21:21:07 -0700 Received: from istari.home.com (localhost [127.0.0.1]) by cc158233-a.catv1.md.home.com (8.11.4/8.11.4) with ESMTP id f5R4L4E00674 for ; Wed, 27 Jun 2001 00:21:05 -0400 (EDT) (envelope-from sjr@cc158233-a.catv1.md.home.com) Message-Id: <200106270421.f5R4L4E00674@cc158233-a.catv1.md.home.com> Date: Wed, 27 Jun 2001 00:21:03 -0400 (EDT) From: "Stephen J. Roznowski" Subject: Problem with PCI Faxmodem To: stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a PCI 3COM FaxModem, and when I attempt to tip to it, my system freezes (need to powercycle to clear). I'm running FreeBSD-stable from 26 June, and the relevent dmesg info is: sio0: <3COM PCI FaxModem> port 0xec00-0xec07 irq 10 at device 19.0 on pci0 sio0: moving to sio2 sio2: type 16550A Is anyone else seeing anything like this, and could someone give me some ideas on how to try to track down the problem? Thanks, -- Stephen J. Roznowski (sjr@home.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 21:58: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from maila.telia.com (maila.telia.com [194.22.194.231]) by hub.freebsd.org (Postfix) with ESMTP id 5C00C37B405 for ; Tue, 26 Jun 2001 21:58:01 -0700 (PDT) (envelope-from ertr1013@student.uu.se) Received: from d1o913.telia.com (d1o913.telia.com [195.252.44.241]) by maila.telia.com (8.11.2/8.11.0) with ESMTP id f5R4w0F16089 for ; Wed, 27 Jun 2001 06:58:00 +0200 (CEST) Received: from ertr1013.student.uu.se (h185n2fls20o913.telia.com [212.181.163.185]) by d1o913.telia.com (8.8.8/8.8.8) with SMTP id GAA09451 for ; Wed, 27 Jun 2001 06:57:59 +0200 (CEST) Received: (qmail 94975 invoked by uid 1001); 27 Jun 2001 04:57:24 -0000 Date: Wed, 27 Jun 2001 06:57:23 +0200 From: Erik Trulsson To: stable@FreeBSD.ORG Subject: Re: Problems with mergemaster Message-ID: <20010627065723.A94912@student.uu.se> Mail-Followup-To: stable@FreeBSD.ORG References: <20010626225556.A3305@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010626225556.A3305@nc.rr.com> User-Agent: Mutt/1.3.19i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jun 26, 2001 at 10:55:56PM -0400, Randall Hopper wrote: > Garrett Wollman: > |Darren Gamble wrote: > |> > |> I have recently (finally) been able to do a make build/installworld on > |> one of my test systems with the Stable tree. > |> > |> However, mergemaster does not appear to be working properly. ... > |> For each file, I get > |> > |> *** Problem installing ./foo , it will remain to merge by hand > | > |That's because someone(tm) removed the `-c' options to `install' from > |the -stable version of mergemaster, even though the -stable version of > |`install' still needs them. > > Is there a work-around for this? I supped stable Monday and also saw this. > The work-around is to ignore the error messages. Contrary to what the message says the files do get installed correctly. You can verify this by rerunning mergemaster and noticing that it ignores those files the second time (since they have already been updated.) -- Erik Trulsson ertr1013@student.uu.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 22:55:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f55.law7.hotmail.com [216.33.237.55]) by hub.freebsd.org (Postfix) with ESMTP id 7A0AF37B401 for ; Tue, 26 Jun 2001 22:55:55 -0700 (PDT) (envelope-from dimuthu@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 26 Jun 2001 22:55:55 -0700 Received: from 203.39.46.163 by lw7fd.law7.hotmail.msn.com with HTTP; Wed, 27 Jun 2001 05:55:55 GMT X-Originating-IP: [203.39.46.163] From: "Dimuthu Bandara" To: freebsd-stable@freebsd.org Subject: Mylex AcceleRaid 352! Date: Wed, 27 Jun 2001 05:55:55 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 27 Jun 2001 05:55:55.0449 (UTC) FILETIME=[D4926A90:01C0FECD] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I am going to change my ServeRaid 3L to mylex AcceleRaid 352 controller. Can anybody confirm me this controller works fine with FreeBSD 4.3?. It's really important I manage to convince my mamagement to buy a new controller. And i don't want to get busted if this one is giving problems :P Thanks Dim _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 26 23: 4:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.dis.org (dhcp44-21.dis.org [216.240.44.21]) by hub.freebsd.org (Postfix) with ESMTP id A14FF37B401 for ; Tue, 26 Jun 2001 23:04:54 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f5R6H1917626; Tue, 26 Jun 2001 23:17:02 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106270617.f5R6H1917626@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Dimuthu Bandara" Cc: freebsd-stable@freebsd.org Subject: Re: Mylex AcceleRaid 352! In-reply-to: Your message of "Wed, 27 Jun 2001 05:55:55." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 Jun 2001 23:17:01 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hi, > > I am going to change my ServeRaid 3L to mylex AcceleRaid 352 controller. Can > anybody confirm me this controller works fine with FreeBSD 4.3?. It's really > important I manage to convince my mamagement to buy a new controller. And i > don't want to get busted if this one is giving problems :P You'll want to update to the driver at http://people.freebsd.org/~msmith/RAID/mylex/mly-20010618.tar.gz but yes, this controller is supported and works just fine. In addition, the documentation I have from Mylex means that I can support this controller properly. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 0:51: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id A6F3137B401 for ; Wed, 27 Jun 2001 00:51:00 -0700 (PDT) (envelope-from dg@root.com) Received: (from dg@localhost) by root.com (8.11.2/8.11.2) id f5R7fQ553271; Wed, 27 Jun 2001 00:41:26 -0700 (PDT) (envelope-from dg) Date: Wed, 27 Jun 2001 00:41:26 -0700 From: David Greenman To: Mike Tancsa Cc: freebsd-stable@freebsd.org Subject: Re: More fxp problems (Different ?) Message-ID: <20010627004126.A53263@nexus.root.com> References: <5.1.0.14.0.20010626132049.04048e40@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.0.14.0.20010626132049.04048e40@marble.sentex.ca>; from mike@sentex.net on Tue, Jun 26, 2001 at 01:32:51PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >This is a stange one. It seems like a hardware issue as the same two nics >on a 815 or 440BX chipset did have these problems. ^ NOT? ...in any case, try this patch and let me know if the problem goes away: Index: if_fxp.c =================================================================== RCS file: /home/ncvs/src/sys/dev/fxp/if_fxp.c,v retrieving revision 1.110.2.4 diff -c -r1.110.2.4 if_fxp.c *** if_fxp.c 2001/06/08 20:36:57 1.110.2.4 --- if_fxp.c 2001/06/27 07:48:29 *************** *** 490,501 **** --- 490,503 ---- * If we are not a 82557 chip, we can enable extended features. */ if (sc->chip != FXP_CHIP_82557) { + #if 0 /* * If there is a valid cacheline size (8 or 16 dwords), * then turn on MWI. */ if (pci_read_config(dev, PCIR_CACHELNSZ, 1) != 0) sc->flags |= FXP_FLAG_MWI_ENABLE; + #endif /* turn on the extended TxCB feature */ sc->flags |= FXP_FLAG_EXT_TXCB; -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. >MB is an Asus CUV-4x-e Via82ct chipset 686b. Cards are >1 2940U >1 3Ware 2 port RAID-1 config (6x000 series) >2 Intel nics, both show inphy1: on miib >inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto >and both are from the same box. In short, all these parts do not play well >together. If I pull the two nics and put in cheap old RealTeks the box >works fine enough. But with the Intels (I have tried manual IRQs, auto, >changing the slot order etc), I still get the nics locking up on a >consistent basis. I even tried a card that was made a few years ago, but >same results. > > >Jun 26 08:52:02 granite /kernel: Timecounter "i8254" frequency 1193182 Hz >Jun 26 08:52:02 granite /kernel: CPU: Pentium III/Pentium III Xeon/Celeron >(870.58-MHz 686-class CPU) >Jun 26 08:52:02 granite /kernel: Origin = >"GenuineIntel" Id = 0x68a Stepping = 10 >Jun 26 08:52:02 granite /kernel: >Features=0x383f9ffSR,SSE> >un 26 08:52:02 granite /kernel: npx0: INT 16 interface >Jun 26 08:52:02 granite /kernel: pcib0: on motherboard >Jun 26 08:52:02 granite /kernel: pci0: on pcib0 >Jun 26 08:52:02 granite /kernel: pcib2: PCI-PCI (AGP) bridge> at device 1.0 on pci0 >Jun 26 08:52:02 granite /kernel: pci1: on pcib2 >Jun 26 08:52:02 granite /kernel: isab0: at >device 4.0 on pci0 >Jun 26 08:52:02 granite /kernel: isa0: on isab0 >Jun 26 08:52:02 granite /kernel: atapci0: >port 0xd800-0xd80f at device 4.1 on pci0 >Jun 26 08:52:02 granite /kernel: ata0: at 0x1f0 irq 14 on atapci0 >Jun 26 08:52:02 granite /kernel: ata1: at 0x170 irq 15 on atapci0 >Jun 26 08:52:02 granite /kernel: pci0: at 4.2 >irq 10 >Jun 26 08:52:02 granite /kernel: pci0: at 4.3 >irq 10 > >I have a very similar mix of parts in my news server and I have never seen >this happen on the 440BX chipset. Is it something specific to the Via or >this combo ? The errors were happening at 100 and 10Mb with various duplex >settings. A few times the NIC totally locked up and I had to reboot the >machine to recover. > > >Jun 26 06:25:11 granite /kernel: fxp1: device timeout >Jun 26 06:25:11 granite /kernel: fxp1: SCB timeout: 0x60, 0x0, 0x0 0x0 >Jun 26 06:25:11 granite /kernel: fxp1: SCB timeout: 0x6, 0x0, 0x0 0x0 >Jun 26 06:25:11 granite /kernel: fxp1: SCB timeout: 0x40, 0x0, 0x0 0x0 >Jun 26 06:25:11 granite /kernel: fxp1: DMA timeout >Jun 26 06:25:12 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 >Jun 26 06:25:12 granite /kernel: fxp1: DMA timeout >Jun 26 06:25:12 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 >Jun 26 06:25:12 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 >Jun 26 06:25:17 granite /kernel: fxp1: SCB timeout: 0x1, 0x0, 0x0 0x400 >Jun 26 06:25:19 granite /kernel: fxp1: SCB timeout: 0x81, 0x0, 0x0 0x400 >Jun 26 06:25:31 granite /kernel: fxp1: device timeout >Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x60, 0x0, 0x0 0x0 >Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x6, 0x0, 0x0 0x0 >Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x40, 0x0, 0x0 0x0 >Jun 26 06:25:31 granite /kernel: fxp1: DMA timeout >Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 >Jun 26 06:25:31 granite /kernel: fxp1: DMA timeout >Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 >Jun 26 06:25:31 granite /kernel: fxp1: SCB timeout: 0x10, 0x0, 0x0 0x0 >Jun 26 08:39:46 granite /kernel: fxp1: Ethernet address 00:d0:b7:92:32:b4 >Jun 26 08:40:09 granite /kernel: fxp1: device timeout >Jun 26 08:40:24 granite /kernel: arp: 199.212.134.2 is on fxp1 but got >reply from 00:90:27:b0:35:21 on fxp0 >Jun 26 08:40:32 granite /kernel: fxp1: device timeout >Jun 26 08:41:04 granite /kernel: fxp1: device timeout >Jun 26 08:47:04 granite /kernel: fxp0: >port 0xb400-0xb43f mem 0xfa000000-0xfa0fffff,0xfa800000-0xfa800fff irq 7 at >device 9.0 on pci0 >Jun 26 08:47:04 granite /kernel: fxp0: Ethernet address 00:d0:b7:92:32:b4 >Jun 26 08:47:27 granite /kernel: fxp0: device timeout >Jun 26 08:47:51 granite /kernel: fxp0: device timeout >Jun 26 08:48:14 granite /kernel: fxp0: device timeout > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 4:48:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 690FF37B401 for ; Wed, 27 Jun 2001 04:48:09 -0700 (PDT) (envelope-from mike@sentex.net) Received: (from root@localhost) by cage.simianscience.com (8.11.4/8.11.2) id f5RBm9p92807; Wed, 27 Jun 2001 07:48:09 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.4/8.11.2av) with ESMTP id f5RBm4A92799; Wed, 27 Jun 2001 07:48:05 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010627074616.037fd5b8@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 27 Jun 2001 07:48:03 -0400 To: David Greenman From: Mike Tancsa Subject: Re: More fxp problems (Different ?) Cc: freebsd-stable@freebsd.org In-Reply-To: <20010627004126.A53263@nexus.root.com> References: <5.1.0.14.0.20010626132049.04048e40@marble.sentex.ca> <5.1.0.14.0.20010626132049.04048e40@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 12:41 AM 6/27/2001 -0700, David Greenman wrote: > >This is a stange one. It seems like a hardware issue as the same two nics > >on a 815 or 440BX chipset did have these problems. > ^ NOT? Hi, Yes, my typo. The problem did not happen on the old chipset > ...in any case, try this patch and let me know if the problem goes >away: Thanks! I will have to order another board as the problem machine is currently my main production server. However, I will buy another MB this week and try and test it out on it. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 6: 4: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from casper.imasy.or.jp (casper.imasy.or.jp [202.227.24.9]) by hub.freebsd.org (Postfix) with ESMTP id 6C20D37B405 for ; Wed, 27 Jun 2001 06:04:00 -0700 (PDT) (envelope-from ume@imasy.or.jp) Received: from piano.mahoroba.org (IDENT:jab/CjhIqAnvkRmWzxB7gTxFORR/V5QN7059vw/IgZRxzYOm4JykB3OFekzbEuI7@piano.mob.spacecom.netspace.or.jp [3ffe:505:200f:2000:200:f4ff:fe5e:7147]) (authenticated as ume with DIGEST-MD5) by casper.imasy.or.jp (8.11.3/8.11.3/casper) with ESMTP/inet6 id f5RD3hR67892 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Wed, 27 Jun 2001 22:03:49 +0900 (JST) (envelope-from ume@imasy.or.jp) Received: from piano.mahoroba.org (IDENT:ChHoSMyjUrifyRSZs9kS4RqZeJnx5GeLzRsZJxcSJBhof1lsiuH/vZkCrnVtXS19@localhost [IPv6:::1]) by piano.mahoroba.org (8.12.0.Beta12/8.12.0.Beta12/piano) with ESMTP id f5RD2S0o049602 for ; Wed, 27 Jun 2001 22:02:29 +0900 (JST) (envelope-from ume@imasy.or.jp) Date: Wed, 27 Jun 2001 22:02:27 +0900 Message-ID: From: Hajimu UMEMOTO To: stable@FreeBSD.org Subject: HEAD UP: rtadvd_enable's default will be changed to NO User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.0 (=?ISO-2022-JP?B?GyRCMlYxYxsoQg==?=) X-Operating-System: FreeBSD 4.3-STABLE MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Currently, rtadvd_enable's default is YES. It means that IPv6 router runs rtadvd(8) by default. This breaks the following description in RFC2461: AdvSendAdvertisements A flag indicating whether or not the router sends periodic Router Advertisements and responds to Router Solicitations. Default: FALSE Note that AdvSendAdvertisements MUST be FALSE by default so that a node will not accidentally start acting as a router unless it is explicitly configured by system management to send Router Advertisements. The default value of rtadvd_enable was already changed to NO in -CURRENT. Then, I'll MFC it, soon. If you are running rtadvd(8) in your IPv6 router, please make sure to set rtadvd_enable to YES in your /etc/rc.conf. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 6: 6:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id 87DB537B407 for ; Wed, 27 Jun 2001 06:06:29 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: (qmail 25386 invoked from network); 27 Jun 2001 13:14:28 -0000 Received: from unknown (HELO geekland) (151.201.71.193) by mail.the-i-pa.com with SMTP; 27 Jun 2001 13:14:28 -0000 Received: by localhost with Microsoft MAPI; Wed, 27 Jun 2001 09:04:41 -0400 Message-ID: <01C0FEE8.33512E80.wmoran@iowna.com> From: Bill Moran To: "'Chad R. Larson'" , Jordan Hubbard Cc: "juha@saarinen.org" , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" Subject: RE: Staying *really stable* in FreeBSD Date: Wed, 27 Jun 2001 09:04:40 -0400 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [I'm going out on a limb here (using MS Outlook). I think I've got the formatting cleaned up, but if I don't, feel free to complain.] On Tuesday, June 26, 2001 5:11 PM, Chad R. Larson [SMTP:chad@DCFinc.com] wrote: > On Sun, Jun 24, 2001 at 02:34:03AM -0700, Jordan Hubbard wrote: > > As I said at the beginning, perhaps it's time to simply re-write the > > Handbook paragraph which inadvertently "sells" -stable as a solution > > for certain types of problems it was never meant to solve. > > Yes, the handbook paragraph was clearly written to suggest that if > you run a production machine you should track -STABLE **in leiu of > -CURRENT**, not as a general rule. That is, if you chose to track > anything at all, it should be -STABLE. I disagree completely. Did you read the handbook? If you are interested in tracking the FreeBSD development process, and you want early access to the features that will appear in the next ``point'' release of FreeBSD then you should consider following FreeBSD-STABLE. Tracking FreeBSD-STABLE also gives you easy access to security fixes for FreeBSD as they are released. However, you do not need to track FreeBSD-STABLE to do this, as every security advisory for FreeBSD explains how to fix the problem for the releases it affects. Seems pretty clear to me. If you're interested in the development process, or need a new feature, you should *consider* tracking stable. -STABLE is also a method for getting security fixes, although it is NOT the only method. Where exactly did you get the impression that -STABLE was for people who want to get all the bug fixes? > That should be easy to clarify. Looks clear to me already. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 6:13:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id D5C2137B406 for ; Wed, 27 Jun 2001 06:13:22 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: (qmail 25467 invoked from network); 27 Jun 2001 13:21:23 -0000 Received: from unknown (HELO geekland) (151.201.71.193) by mail.the-i-pa.com with SMTP; 27 Jun 2001 13:21:23 -0000 Received: by localhost with Microsoft MAPI; Wed, 27 Jun 2001 09:11:36 -0400 Message-ID: <01C0FEE9.2A9644A0.wmoran@iowna.com> From: Bill Moran To: "'Chad R. Larson'" , Jordan Hubbard Cc: "juha@saarinen.org" , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" Subject: RE: Staying *really stable* in FreeBSD Date: Wed, 27 Jun 2001 09:11:36 -0400 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, June 26, 2001 5:07 PM, Chad R. Larson [SMTP:chad@DCFinc.com] wrote: > On Sun, Jun 24, 2001 at 02:34:03AM -0700, Jordan Hubbard wrote: > > From: "Juha Saarinen" > > Subject: RE: Staying *really stable* in FreeBSD > > Date: Sun, 24 Jun 2001 12:00:59 +1200 > > > >> "19.2.2.2. Who needs FreeBSD-STABLE? > >> If you are a commercial user or someone who puts maximum stability of > >> their FreeBSD system before all other concerns, you should consider > >> tracking FreeBSD-STABLE. This is especially true if you have installed Hmmm ... I just realized that that paragraph had already changed. Did I miss some of the excitement? > > It's probably time to rewrite that paragraph substantially. It was > > something of a tactical error to encourage certain interest groups to > > run "work in progress" code, even if that work is very carefully > > bounded and kept "in progress" for the shortest periods possible. Apparently this has been done. While the change to the text is not "substantial", I think it does serve to clarify the situation very well. > Actually, -CURRENT is "development" and -STABLE is "QA/BETA" and > -RELEASE is what most folks would think of as "stable". So, why > don't we name them like that? I wouldn't have a problem with > -DEVEL, -BETA, -RELEASE, and perhaps putting -STABLE on the new > RELENG_X_Y branch. If anyone is taking votes, I disagree. The -STABLE branch is not -BETA in any way that I can see. It's simply a low key development branch. Changes are tested in -CURRENT before being merged into -STABLE, therefore there's nothing -BETA about it. The addition of the RELENG_X_Y branch should improve the situation for people who are paranoid and like to upgrade. Let's not make the problem worse, though. If you try to give people a way to "just fix it without paying any real attention to what's going on" you're going to have a lot of people mad at you if things don't go perfectly. This "I shouldn't have to make sure the software is safe, that's the developer's job" mentality is one of the main reasons that systems get cracked in the first place. Even Microsoft announced that there was a terrible hole in IIS that should be patched immediately, yet I wonder how many IIS installations still have this hole unpatched?? -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 7:20:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 5F73C37B407 for ; Wed, 27 Jun 2001 07:20:30 -0700 (PDT) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id QAA28829 for ; Wed, 27 Jun 2001 16:29:38 +0200 Message-ID: <3B39EC3A.63D8A166@i-clue.de> Date: Wed, 27 Jun 2001 16:22:50 +0200 From: Christoph Sold Reply-To: so@server.i-clue.de X-Mailer: Mozilla 4.75 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: stable@FreeBSD.org Subject: wi driver won't compile Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG CVSup'ed two hours ago, I cannot build a kernel including the wi driver. Will check again tomorrow. Error message was something like "...build kernel first." Strange. HTH -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 7:29:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (tserver.conference.usenix.org [199.103.159.3]) by hub.freebsd.org (Postfix) with ESMTP id 82ECE37B401 for ; Wed, 27 Jun 2001 07:29:38 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f5QMick04740; Tue, 26 Jun 2001 23:44:38 +0100 (BST) (envelope-from nik) Date: Tue, 26 Jun 2001 23:44:36 +0100 From: Nik Clayton To: Juha Saarinen Cc: "Chad R. Larson" , Jordan Hubbard , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010626234435.H461@canyon.nothing-going-on.org> References: <20010626140650.B9911@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="dDnEQgWzhgf+8aPe" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from juha@saarinen.org on Wed, Jun 27, 2001 at 09:34:45AM +1200 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --dDnEQgWzhgf+8aPe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 27, 2001 at 09:34:45AM +1200, Juha Saarinen wrote: > On Tue, 26 Jun 2001, Chad R. Larson wrote: > > Actually, -CURRENT is "development" and -STABLE is "QA/BETA" and > > -RELEASE is what most folks would think of as "stable". So, why > > don't we name them like that? I wouldn't have a problem with > > -DEVEL, -BETA, -RELEASE, and perhaps putting -STABLE on the new > > RELENG_X_Y branch. >=20 > I think that would clear up a lot of the confusion. It's kind of hard to > accept that -STABLE doesn't necessarily mean "stable" (currently), if you > see what I mean ;-). I've rewritten section 19.2.2.1 and 19.2.2.2 at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.= html Do people think this gets the point across any better? N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --dDnEQgWzhgf+8aPe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjs5EFIACgkQk6gHZCw343WnxwCggigt/NZZoMJ+s+V8UOcZW3dI C3QAoIDl9QgBj5QBlSIho6JfE5cSrrPf =08z8 -----END PGP SIGNATURE----- --dDnEQgWzhgf+8aPe-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 7:35:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mikea.ath.cx (okc-65-26-223-53.mmcable.com [65.26.223.53]) by hub.freebsd.org (Postfix) with ESMTP id 9B03237B406; Wed, 27 Jun 2001 07:35:44 -0700 (PDT) (envelope-from mikea@mikea.ath.cx) Received: (from mikea@localhost) by mikea.ath.cx (8.11.4/8.11.1) id f5REZhi66180; Wed, 27 Jun 2001 09:35:43 -0500 (CDT) (envelope-from mikea) Date: Wed, 27 Jun 2001 09:35:42 -0500 From: mikea To: Nik Clayton Cc: Juha Saarinen , "Chad R. Larson" , Jordan Hubbard , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010627093542.B66087@mikea.ath.cx> References: <20010626140650.B9911@freeway.dcfinc.com> <20010626234435.H461@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20010626234435.H461@canyon.nothing-going-on.org>; from nik@FreeBSD.ORG on Tue, Jun 26, 2001 at 11:44:36PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jun 26, 2001 at 11:44:36PM +0100, Nik Clayton wrote: > I've rewritten section 19.2.2.1 and 19.2.2.2 at > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html > > Do people think this gets the point across any better? Yes; I think that this is quite clear and explicit. [Apologies to those who get this twice; I don't know which of you subscribe to stable@] -- Mike Andrews mikea@mikea.ath.cx Tired old sysadmin since 1964 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 7:41:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from poontang.schulte.org (poontang.schulte.org [209.134.156.197]) by hub.freebsd.org (Postfix) with ESMTP id 98C2F37B401; Wed, 27 Jun 2001 07:41:26 -0700 (PDT) (envelope-from christopher@schulte.org) Received: from schulte-laptop.schulte.org (nb60.netbriefings.com [64.183.199.60]) by poontang.schulte.org (8.12.0.Beta10/8.12.0.Beta10) with ESMTP id f5REfLjU023112; Wed, 27 Jun 2001 09:41:22 -0500 (CDT) Message-Id: <5.1.0.14.0.20010627093802.03cf0308@pop.schulte.org> X-Sender: schulte@pop.schulte.org X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 27 Jun 2001 09:41:18 -0500 To: Nik Clayton , Juha Saarinen From: Christopher Schulte Subject: Re: Staying *really stable* in FreeBSD Cc: "Chad R. Larson" , Jordan Hubbard , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" In-Reply-To: <20010626234435.H461@canyon.nothing-going-on.org> References: <20010626140650.B9911@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 11:44 PM 6/26/2001 +0100, Nik Clayton wrote: >I've rewritten section 19.2.2.1 and 19.2.2.2 at > > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html > >Do people think this gets the point across any better? The patch branch (currently RELENG_4_3) should be introduced, perhaps mentioned here, in the paragraph I quote below. From the update: 'Tracking FreeBSD-STABLE also gives you easy access to security fixes for FreeBSD as they are released. However, you do not need to track FreeBSD-STABLE to do this, as every security advisory for FreeBSD explains how to fix the problem for the releases it affects.' --chris >N >-- >FreeBSD: The Power to Serve http://www.freebsd.org/ >FreeBSD Documentation Project http://www.freebsd.org/docproj/ > > --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 7:46:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id DAE6337B405 for ; Wed, 27 Jun 2001 07:46:08 -0700 (PDT) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id QAA29074; Wed, 27 Jun 2001 16:55:15 +0200 Message-ID: <3B39F23B.FA830EA1@i-clue.de> Date: Wed, 27 Jun 2001 16:48:27 +0200 From: Christoph Sold Reply-To: so@server.i-clue.de X-Mailer: Mozilla 4.75 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: so@server.ms-agentur.de Cc: stable@FreeBSD.ORG Subject: Re: wi driver won't compile References: <3B39EC3A.63D8A166@i-clue.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Christoph Sold schrieb: > > CVSup'ed two hours ago, I cannot build a kernel including the wi driver. > Will check again tomorrow. Error message was something like "...build > kernel first." Strange. Re-CVSuped, problem gone. Probably some bogus file after cvsup. -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 7:47: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gw2.dnepr.net (gw2.dnepr.net [217.198.131.97]) by hub.freebsd.org (Postfix) with ESMTP id EA47237B42F for ; Wed, 27 Jun 2001 07:46:53 -0700 (PDT) (envelope-from land@dnepr.net) Received: from dnepr.net (neon.dnepr.net [217.198.131.98]) by gw2.dnepr.net (8.11.4/8.6.18/01) with ESMTP id f5REkLA20775 for ; Wed, 27 Jun 2001 17:46:21 +0300 (EEST) Received: (from land@localhost) by dnepr.net (8.8.8/8.8.8) id RAA05244 for stable@freebsd.org; Wed, 27 Jun 2001 17:46:11 +0300 (EEST) X-POP3-RCPT: stable@freebsd.org Date: Wed, 27 Jun 2001 17:46:11 +0300 From: land@dnepr.net To: stable@freebsd.org Subject: Kernel error messages Message-ID: <20010627174611.A4962@dnepr.net> Mail-Followup-To: stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello ! Can you explain what does this messages mean and why it occured ? The system is Jun 21 -STABLE. Jun 27 13:28:18 host /kernel: negative proccnt for uid = 65534 Jun 27 13:28:18 host /kernel: freeing uidinfo: uid = 65534, sbsize =34306 Jun 27 13:28:18 host /kernel: freeing uidinfo: uid = 65534, proccnt =-1 Jun 27 13:28:18 host /kernel: negative sbsize for uid = 1 Jun 27 13:28:18 host /kernel: negative sbsize for uid = 1 Jun 27 13:28:18 host /kernel: negative sbsize for uid = -16777216 Jun 27 13:28:49 host last message repeated 520 times Jun 27 13:30:51 host last message repeated 2914 times Jun 27 13:40:50 host last message repeated 9813 times Jun 27 13:50:51 host last message repeated 10132 times -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 7:51: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kendra.ne.mediaone.net (kendra.ne.mediaone.net [24.218.227.234]) by hub.freebsd.org (Postfix) with ESMTP id 1DD9E37B406; Wed, 27 Jun 2001 07:51:06 -0700 (PDT) (envelope-from avatar+pop3@kew.com) Received: from xena (xena.hh.kew.com [192.168.203.148]) by kendra.ne.mediaone.net (Postfix) with SMTP id 0967715540; Wed, 27 Jun 2001 10:51:04 -0400 (EDT) Message-ID: <004701c0ff18$98dd45b0$94cba8c0@xena> From: "Drew Derbyshire" To: "Nik Clayton" Cc: References: <20010626140650.B9911@freeway.dcfinc.com> <20010626234435.H461@canyon.nothing-going-on.org> Subject: Re: Staying *really stable* in FreeBSD Date: Wed, 27 Jun 2001 10:51:07 -0400 Organization: Kendra Electronic Wonderworks (http://www.kew.com/kendra) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I've rewritten section 19.2.2.1 and 19.2.2.2 at > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.htm l > > Do people think this gets the point across any better? The section needs a pointer (the actual content need not be in this section) to the best way(s) for people running a release to get security fixes between releases if not tracking -stable. -ahd- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 8:46:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id 8D4F537B406 for ; Wed, 27 Jun 2001 08:46:30 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: (qmail 27129 invoked from network); 27 Jun 2001 15:54:31 -0000 Received: from unknown (HELO geekland) (151.201.71.193) by mail.the-i-pa.com with SMTP; 27 Jun 2001 15:54:31 -0000 Received: by localhost with Microsoft MAPI; Wed, 27 Jun 2001 11:44:43 -0400 Message-ID: <01C0FEFE.8EB2BA80.wmoran@iowna.com> From: Bill Moran To: "'mupi@Mknet.org'" Cc: "'freebsd-stable@freebsd.org'" Subject: RE: Staying *really stable* in FreeBSD Date: Wed, 27 Jun 2001 11:44:42 -0400 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there a reason why you took this off the list? On Wednesday, June 27, 2001 10:52 AM, Mike Porter [SMTP:mupi@mknet.org] wrote: > On Wednesday 27 June 2001 07:11, you wrote: > > On Tuesday, June 26, 2001 5:07 PM, Chad R. Larson [SMTP:chad@DCFinc.com] > wrote: > > > If anyone is taking votes, I disagree. > > The -STABLE branch is not -BETA in any way that I can see. It's simply a > > low key development branch. Changes are tested in -CURRENT before > > being merged into -STABLE, therefore there's nothing -BETA about it. > > > > While I agree with most of what you said, I disagree here. Just because > *some* testing has been done, doesn't mean it isn't BETA. BETA software is > generally believed to be pretty stable, just a few minor kinks to work out. > At that point, getting it into the hands of the largest possible > cross-section of users makes sense, becuase collectively they are more likely > to excercise all of the features. Further, some features may work as > intended when the user follows all the correct steps in the correct sequence, > but how easy is it to get out of the sequence and break things? (Example (ok, > its a bad/simplified example but it demonstrates the point): Actually ... it's a good example. > So BETA testing takes place after a good deal of > previous "in house" development happens. This is the "alpha" test stage. > Why do you think they use "beta" (the SECOND letter of the greek alphbet) to > denote the SECOND test? It implies that there is an "alpha" or "first" test > before. thus -CURRENT is ALPHA level code, STABLE is BETA. That's also a relevent point. "alpha" and "beta" are generally used to describe testing sequences in/out of the developer circle. In a company, alpha testing is done by the developers or other employees of the company, while beta testing is done by providing the software to a select group of customers who have volunteered to test the software. This particular model falls apart when you have the FreeBSD development model. Reasons: 1) anyone who wants to test -CURRENT can, thus it doesn't fit typical expectation of "alpha" 2) the developers are generally also the users 3) The -STABLE branch is not *intended* to be for testing purposed only. It is *intended* to be a useable product. In the commercial world, a "beta" is NOT INTENDED for regular use, but for testing only. Thus, renaming the -STABLE branch would be a misnomer. > Of course, if you assume that STABLE is BETA level code, then you can expect > some glitches, and sometimes things WILL slip through the cracks and cause > major headaches...but *in general* you should have fairly stable code, with a > few bugs in it. You EXPECT (or SHOULD EXPECT) there to be bugs in > it....that's part of the development effort. No, according the the handbook, you should not *expect* there to be bugs in -STABLE, You should be wary, as the handbook warns you, but my experience with -STABLE over the last two years is that it's generally pretty reliable. The handbook also states that you should subscribe to the stable mailing list if you intend to track -STABLE, so anyone following the hanbook is going to be well informed when breakage occurs. I believe the recent changes to the handbook did an excellent job of clearing this up. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 9: 7:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (tserver.conference.usenix.org [199.103.159.3]) by hub.freebsd.org (Postfix) with ESMTP id 1A2EC37B407 for ; Wed, 27 Jun 2001 09:07:44 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f5R0rfC05779; Wed, 27 Jun 2001 01:53:41 +0100 (BST) (envelope-from nik) Date: Wed, 27 Jun 2001 01:53:41 +0100 From: Nik Clayton To: Jordan Hubbard Cc: juha@saarinen.org, joe@zircon.seattle.wa.us, stable@freebsd.org Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010627015341.E5408@canyon.nothing-going-on.org> References: <15157.11221.593513.478892@zircon.zircon.seattle.wa.us> <00cf01c0fc40$c0348db0$0a01a8c0@den2> <20010624023403R.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="9crTWz/Z+Zyzu20v" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010624023403R.jkh@osd.bsdi.com>; from jkh@osd.bsdi.com on Sun, Jun 24, 2001 at 02:34:03AM -0700 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --9crTWz/Z+Zyzu20v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 24, 2001 at 02:34:03AM -0700, Jordan Hubbard wrote: > From: "Juha Saarinen" > Subject: RE: Staying *really stable* in FreeBSD > Date: Sun, 24 Jun 2001 12:00:59 +1200 >=20 > > "19.2.2.2. Who needs FreeBSD-STABLE? > > If you are a commercial user or someone who puts maximum stability of > > their FreeBSD system before all other concerns, you should consider > > tracking FreeBSD-STABLE. This is especially true if you have installed >=20 > It's probably time to rewrite that paragraph substantially. It was > something of a tactical error to encourage certain interest groups to > run "work in progress" code, even if that work is very carefully > bounded and kept "in progress" for the shortest periods possible. >=20 > You just can't have a code base which is actually going places and > having things actively updated (which is generally a really good idea, > especially when the updates involved fixing bugs) and also guarantee > that it's particularly usable for anything. Whether it builds > flawlessly without warnings or not, it still represents a fairly > significant unknown quantity until such time as you've frozen the code > and spent a few weeks, at minimum, collecting user reports and making > very carefully selected changes. >=20 > We've also heard any number of suggestions for "fixing" the problem, > from aggressive automated tagging (which would be tremendously > expensive with CVS and not fix the "builds but doesn't work" problem) > to extensive regression test suites that nobody seems to have time to > actually write. >=20 > As I said at the beginning, perhaps it's time to simply re-write the > Handbook paragraph which inadvertently "sells" -stable as a solution > for certain types of problems it was never meant to solve. Done. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --9crTWz/Z+Zyzu20v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjs5LpQACgkQk6gHZCw343X0agCfbK9WGhkBHYp7y5N6lLc4rKhz Vv4AnjRnz/xxOW498BKQ2h+FjOn6pf7b =y1nH -----END PGP SIGNATURE----- --9crTWz/Z+Zyzu20v-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 9: 8: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (tserver.conference.usenix.org [199.103.159.3]) by hub.freebsd.org (Postfix) with ESMTP id 49E0737B409; Wed, 27 Jun 2001 09:07:56 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f5R0QLQ05659; Wed, 27 Jun 2001 01:26:21 +0100 (BST) (envelope-from nik) Date: Wed, 27 Jun 2001 01:26:20 +0100 From: Nik Clayton To: Christopher Schulte Cc: Nik Clayton , Juha Saarinen , "Chad R. Larson" , Jordan Hubbard , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010627012620.B5408@canyon.nothing-going-on.org> References: <20010626140650.B9911@freeway.dcfinc.com> <20010626234435.H461@canyon.nothing-going-on.org> <5.1.0.14.0.20010627093802.03cf0308@pop.schulte.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="XOIedfhf+7KOe/yw" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.0.20010627093802.03cf0308@pop.schulte.org>; from christopher@schulte.org on Wed, Jun 27, 2001 at 09:41:18AM -0500 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --XOIedfhf+7KOe/yw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 27, 2001 at 09:41:18AM -0500, Christopher Schulte wrote: >=20 > At 11:44 PM 6/26/2001 +0100, Nik Clayton wrote: > >I've rewritten section 19.2.2.1 and 19.2.2.2 at > > > >=20 > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable= .html > > > >Do people think this gets the point across any better? >=20 > The patch branch (currently RELENG_4_3) should be introduced, perhaps=20 > mentioned here,=20 Not yet. AIUI, the RELENG_4_3 branch is an experiment, and gives us the option of providing security fixes this way. I haven't seen a commitment[1] from the security officer team that they will actually do this. Until that happens I don't think it should be documented. N [1] Not a slur on the fine efforts of the security team. I mean that I haven't seen an e-mail that says "Yes, any security fixes to RELENG_4 will *definitely* be made available on the RELENG_4_3 branch". --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --XOIedfhf+7KOe/yw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjs5KCsACgkQk6gHZCw343VX4QCcCi1sUSoNpCIJu848pYAij5uh fPUAn15q2sUkD4j7tAJaVnbpzW4wUAHj =lfwm -----END PGP SIGNATURE----- --XOIedfhf+7KOe/yw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 12:13:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c576194-a.saltlk1.ut.home.com (c576194-a.saltlk1.ut.home.com [65.5.60.246]) by hub.freebsd.org (Postfix) with SMTP id D6C8737B401 for ; Wed, 27 Jun 2001 12:13:47 -0700 (PDT) (envelope-from mupi@mknet.org) Received: (qmail 1120 invoked from network); 27 Jun 2001 19:13:46 -0000 Received: from localhost (HELO mukappa.home.com) (127.0.0.1) by localhost with SMTP; 27 Jun 2001 19:13:46 -0000 From: Mike Porter Reply-To: mupi@Mknet.org To: Bill Moran Subject: Re: Staying *really stable* in FreeBSD Date: Wed, 27 Jun 2001 13:13:45 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="us-ascii" Cc: "'freebsd-stable@freebsd.org'" References: <01C0FEFE.8EB2BA80.wmoran@iowna.com> In-Reply-To: <01C0FEFE.8EB2BA80.wmoran@iowna.com> MIME-Version: 1.0 Message-Id: <01062713134503.00453@mukappa.home.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday 27 June 2001 09:44, Bill Moran wrote: > Is there a reason why you took this off the list? > my mistake (or my mailer's depending on how you look at it). If the majordomo config file for the list included the line "reply-to: stable@freebsd.org" then all replies would by defualt go back to the list. While this isn't ALWAYS appropriate, it usually is.... > This particular model falls apart when you have the FreeBSD development > model. Reasons: > 1) anyone who wants to test -CURRENT can, thus it doesn't fit typical > expectation of "alpha" Although depending on your circle of friends, it is frequnetly possible to get alpha-level stuff. More so from some places than others. However, according the handbook, "FreeBSD-CURRENT is, quite literally, nothing more than a daily snapshot of the working sources for FreeBSD." and "FreeBSD-CURRENT is made generally available for 3 primary interest groups: 1.Members of the FreeBSD group who are actively working on some part of the source tree and for whom keeping ``current'' is an absolute requirement. 2.Members of the FreeBSD group who are active testers, willing to spend time working through problems in order to ensure that FreeBSD-CURRENT remains as sane as possible. These are also people who wish to make topical suggestions on changes and the general direction of FreeBSD. 3.Peripheral members of the FreeBSD (or some other) group who merely wish to keep an eye on things and use the current sources for reference purposes (e.g. for reading, not running). These people also make the occasional comment or contribute code." Item 1 is clearly developers, and thus traditionally falls under "alpha" any way you slice it. Number 2 is perhaps more of a stretch, but even alpha testing implies that some testing is done. Opening up the "alpha" test to more people doesn't necessarily make it not an alpha test, it simply makes the results more accurate. The more mistakes/bugs/problems you can catch before the beta-test stage, the less problems you will have in beta. The less beta trouble you have, the quicker you can release a product. > 2) the developers are generally also the users I don't necessarily see the relevance of that to testing. If anything, it means the tests will be somewhat more thorough, but again, when the developer is the user, the user will use the product as intended, and may never break something. When an end-user is the user, who doesn't know what the underlying data structures are, if the program isn't smart enough to compensate for a stupid user, the user is going to make the program crash. Again, I would point out that in many cases, yes, this is simple user-error, and should not necessarily be the job of the developer to fix stupid users (as my brother-in-law, a programmer, used to call those errors "User Headspace Error"). > 3) The -STABLE branch is not *intended* to be for testing purposed only. It > is *intended* to be a useable product. In the commercial world, a "beta" is > NOT INTENDED for regular use, but for testing only. Thus, renaming the > -STABLE branch would be a misnomer. > I don't necessarily recommend renaming things (especially when the current (no pun intended) naming scheme works fine for most people) I think the perception should perhaps be clarified becuase -stable isn't nearly as stable as one would understand from either the handbook pages or the name. The simplest solution would be to equate -current with "alpha" code and stable with "beta" > > Of course, if you assume that STABLE is BETA level code, then you can > > expect some glitches, and sometimes things WILL slip through the cracks > > and cause major headaches...but *in general* you should have fairly > > stable code, with a few bugs in it. You EXPECT (or SHOULD EXPECT) there > > to be bugs in it....that's part of the development effort. > > No, according the the handbook, you should not *expect* there to be bugs in > -STABLE, You should be wary, as the handbook warns you, but my experience > with -STABLE over the last two years is that it's generally pretty > reliable. The handbook also states that you should subscribe to the stable > mailing list if you intend to track -STABLE, so anyone following the > hanbook is going to be well informed when breakage occurs. > hmm...maybe we are reading different versions of the handbook? "FreeBSD-STABLE is our development branch for a more low-key and conservative set of changes intended for our next mainstream release. Any changes to this branch will have debuted in FreeBSD-CURRENT first, helping to reduce (but not eliminate) the chance that the changes will cause problems" (from the online handbook) note the "but not eliminate" phrase. There is the expectation that the code should be relatively bug free (since it has been through one set of tests already) but one set of testing isn't necessarily enough. There *will* be problems (as you pointed out in your comments you will be "well informed *when* breakage occurs." (emphasis added, in case anyone's keeping track). I agree, I haven't been tracking stable very long, and I have had no real problems with it except a couple of software compatibility issues (newer versions of whatever shared library sometimes breaks something compiled with a different one....but that's not really the fault of stable, either, at least not entirely). and upgrading a binary while it is in use can have odd consequences (but that was my fault for not following updateing and booting to single user mode, and easily corrected, too) Although I tend to agree with you that the alpha-beta-release model isn't a perfect fit with the freebsd development model, I think it is pretty close, and those are terms that everyone pretty much understands these days who uses computers. If pressed, I would say that current straddles the line between alpha and beta testing, and stable is more or less late beta towards early release candidate level code, when compared to most commercial software. > I believe the recent changes to the handbook did an excellent job of > clearing this up. > I agree, but I think that putting things in terms people can understand is also important, and mentioning something along the lines of the above paragraph might help some people better undrstand the relationship between -current, -stable, and -release. On the other hand.....I seem to recall the initial post in this sub-thread was something like "if we are taking votes...." 1) I don't think we really are taking votes and 2) even if we were, I think the majority by their failure to chime in is indicating their general pleasure with the status quo. well, back to my day job.... mike > -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 13:27: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 670FE37B401; Wed, 27 Jun 2001 13:26:58 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id NAA13599; Wed, 27 Jun 2001 13:26:52 -0700 (MST) (envelope-from chad) Date: Wed, 27 Jun 2001 13:26:52 -0700 From: "Chad R. Larson" To: Nik Clayton Cc: Juha Saarinen , "Chad R. Larson" , Jordan Hubbard , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010627132652.A13576@freeway.dcfinc.com> References: <20010626140650.B9911@freeway.dcfinc.com> <20010626234435.H461@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010626234435.H461@canyon.nothing-going-on.org>; from nik@freebsd.org on Tue, Jun 26, 2001 at 11:44:36PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jun 26, 2001 at 11:44:36PM +0100, Nik Clayton wrote: > On Wed, Jun 27, 2001 at 09:34:45AM +1200, Juha Saarinen wrote: >> On Tue, 26 Jun 2001, Chad R. Larson wrote: >>> Actually, -CURRENT is "development" and -STABLE is "QA/BETA" and >>> -RELEASE is what most folks would think of as "stable". So, why >>> don't we name them like that? I wouldn't have a problem with >>> -DEVEL, -BETA, -RELEASE, and perhaps putting -STABLE on the new >>> RELENG_X_Y branch. >> >> I think that would clear up a lot of the confusion. It's kind of hard to >> accept that -STABLE doesn't necessarily mean "stable" (currently), if you >> see what I mean ;-). > > I've rewritten section 19.2.2.1 and 19.2.2.2 at > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html > > Do people think this gets the point across any better? Yes. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 14:17:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 97FC537B405; Wed, 27 Jun 2001 14:17:33 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15FMgj-0002wc-00; Thu, 28 Jun 2001 09:17:29 +1200 Date: Thu, 28 Jun 2001 09:17:29 +1200 (NZST) From: Juha Saarinen To: Nik Clayton Cc: "Chad R. Larson" , Jordan Hubbard , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" Subject: Re: Staying *really stable* in FreeBSD In-Reply-To: <20010626234435.H461@canyon.nothing-going-on.org> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 26 Jun 2001, Nik Clayton wrote: > I've rewritten section 19.2.2.1 and 19.2.2.2 at > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html > > Do people think this gets the point across any better? Yep! It's now abundantly clear. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 14:29:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 4E33737B405 for ; Wed, 27 Jun 2001 14:29:50 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15FMsW-0002wq-00; Thu, 28 Jun 2001 09:29:40 +1200 Date: Thu, 28 Jun 2001 09:29:40 +1200 (NZST) From: Juha Saarinen To: Bill Moran Cc: "'mupi@Mknet.org'" , "'freebsd-stable@freebsd.org'" Subject: RE: Staying *really stable* in FreeBSD In-Reply-To: <01C0FEFE.8EB2BA80.wmoran@iowna.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 27 Jun 2001, Bill Moran wrote: > In a company, alpha testing is done by the developers or other > employees of the company, Once Upon A Time this was true, but no longer. Viz. Microsoft's "Technology Preview" editions of various pieces of software. Due to lengthening development cycles, companies feel compelled to issue some pretty raw code into the public eye, just to show that they're actually doing something. The mindshare game I guess. Anyway, code never gets out of the beta stage. ;-) Oh, and could you please wrap your lines? -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 14:32: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 0BC4437B403; Wed, 27 Jun 2001 14:32:02 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id OAA13852; Wed, 27 Jun 2001 14:31:45 -0700 (MST) (envelope-from chad) Date: Wed, 27 Jun 2001 14:31:45 -0700 From: "Chad R. Larson" To: Juha Saarinen Cc: Nik Clayton , "Chad R. Larson" , Jordan Hubbard , "joe@zircon.seattle.wa.us" , "stable@FreeBSD.ORG" Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010627143145.B13761@freeway.dcfinc.com> References: <20010626234435.H461@canyon.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from juha@saarinen.org on Thu, Jun 28, 2001 at 09:17:29AM +1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Jun 28, 2001 at 09:17:29AM +1200, Juha Saarinen wrote: >> Do people think this gets the point across any better? > > Yep! It's now abundantly clear. But, as the other guy said "If we're taking votes", I'd still vote we change the names. -CURRENT = -DEVEL (or maybe -ALPHA) -STABLE = -BETA -RELEASE = -RELEASE RELENG_X_Y = -STABLE But as far as I can tell, we're not taking votes. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.com DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 14:39: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id D267837B401 for ; Wed, 27 Jun 2001 14:38:59 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: (qmail 30659 invoked from network); 27 Jun 2001 21:47:02 -0000 Received: from unknown (HELO geekland) (151.201.71.193) by mail.the-i-pa.com with SMTP; 27 Jun 2001 21:47:02 -0000 Received: by localhost with Microsoft MAPI; Wed, 27 Jun 2001 17:37:11 -0400 Message-ID: <01C0FF2F.CC0FB0A0.wmoran@iowna.com> From: Bill Moran To: "'mupi@Mknet.org'" Cc: "'freebsd-stable@freebsd.org'" Subject: RE: Staying *really stable* in FreeBSD Date: Wed, 27 Jun 2001 17:37:10 -0400 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, June 27, 2001 3:14 PM, Mike Porter [SMTP:mupi@mknet.org] wrote: > On Wednesday 27 June 2001 09:44, Bill Moran wrote: > > Is there a reason why you took this off the list? > > > my mistake (or my mailer's depending on how you look at it). If the > majordomo config file for the list included the line "reply-to: > stable@freebsd.org" then all replies would by defualt go back to the list. > While this isn't ALWAYS appropriate, it usually is.... No problem. I expected as such ... looking back, I had intended that question to mean "Should I not be posting to -STABLE" but then I *did* post to -STABLE so it was pretty silly to bring it up at all ... > I agree, but I think that putting things in terms people can understand is > also important, and mentioning something along the lines of the above > paragraph might help some people better undrstand the relationship between > -current, -stable, and -release. To take all the specifics out and state my opinion in one general comment. The statement you make above is the exact reason I don't think that beta is a good name. Folks are used to seeing the label beta on some sort of static release that they can test and compare (beta1, beta2, etc) Whereas -STABLE is a constantly moving target. If you looked into it, there would be what? 20,000 possible versions of 4.3-STABLE so far? And you can grab any one of those versions if you want (like if you know a certain feature appeared after a certain date, but a certain bug didn't appear till a certain date) This is the biggest divergence from a beta type software that I see. > On the other hand.....I seem to recall the initial post in this sub-thread > was something like "if we are taking votes...." 1) I don't think we really > are taking votes and 2) even if we were, I think the majority by their > failure to chime in is indicating their general pleasure with the status quo. True. Considering the core team hasn't asked for a vote, I assume that they either know what they want to do, or they plan to discuss it amoung themselves. I will agree that -STABLE is somewhat misleading. If we had a single word that meant "conservative development", that would be the perfect label for that branch. I still think that beta is not that word, but as you put it, there seems to be general pleasure with the status quo. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 14:57:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.the-i-pa.com (mail.the-i-pa.com [151.201.71.132]) by hub.freebsd.org (Postfix) with SMTP id 1C22D37B401 for ; Wed, 27 Jun 2001 14:57:49 -0700 (PDT) (envelope-from wmoran@iowna.com) Received: (qmail 30777 invoked from network); 27 Jun 2001 22:05:51 -0000 Received: from unknown (HELO geekland) (151.201.71.193) by mail.the-i-pa.com with SMTP; 27 Jun 2001 22:05:51 -0000 Received: by localhost with Microsoft MAPI; Wed, 27 Jun 2001 17:56:01 -0400 Message-ID: <01C0FF32.6D3966E0.wmoran@iowna.com> From: Bill Moran To: 'Juha Saarinen' Cc: "'mupi@Mknet.org'" , "'freebsd-stable@freebsd.org'" Subject: RE: Staying *really stable* in FreeBSD Date: Wed, 27 Jun 2001 17:56:00 -0400 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wednesday, June 27, 2001 5:30 PM, Juha Saarinen [SMTP:juha@saarinen.org] wrote: > On Wed, 27 Jun 2001, Bill Moran wrote: > > > In a company, alpha testing is done by the developers or other > > employees of the company, > > Once Upon A Time this was true, but no longer. Viz. Microsoft's > "Technology Preview" editions of various pieces of software. Due to > lengthening development cycles, companies feel compelled to issue some > pretty raw code into the public eye, just to show that they're actually > doing something. The mindshare game I guess. True, but I guess it still just seems to me that "alpha" is a closed-source kinda word that doesn't fit in with any open-source type of development. Might just be my perception of the whole thing. > Anyway, code never gets out of the beta stage. ;-) I don't know. I mean, "beta" says to me, "we, as developers, can't find any problems, but this hasn't been tested in the real world yet." Whereas a "release" tag says "we've tested this under real world conditions and have not found any problems" I see where you're coming from with that statement, though. Especially open-source development, which is always under scrutiny for the purpose of improvement. > Oh, and could you please wrap your lines? Yeah ... I just realized that the only way to keep Outlook from mangling lines is to manually wrap. I'm working on site this week, far away from my comfortable FreeBSD desktop workstation :-( so I'm stuck with Outlook. I think I'll install mutt on one of the servers here and use it to get my email via ssh ... :-) Don't tell my boss. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 15:12:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from areilly.bpc-users.org (CPE-144-132-234-126.nsw.bigpond.net.au [144.132.234.126]) by hub.freebsd.org (Postfix) with SMTP id 4E83337B405 for ; Wed, 27 Jun 2001 15:12:39 -0700 (PDT) (envelope-from a.reilly@lake.com.au) Received: (qmail 17738 invoked by uid 1000); 27 Jun 2001 22:12:36 -0000 Message-ID: <20010627221236.17737.qmail@areilly.bpc-users.org> From: "Andrew Reilly" Date: Thu, 28 Jun 2001 08:12:36 +1000 (EST) Subject: Undesirable behaviour of burncd erase To: freebsd-stable@freebsd.org Cc: Soren Schmidt MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, but particularly Soren, I run FreeBSD 4.3-STABLE #5: Sat Jun 16 11:45:32 EST 2001 root@gurney.reilly.home:/usr/obj/usr/src/sys/GURNEY on a CPU: Pentium III/Pentium III Xeon/Celeron (499.15-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x387f9ff real memory = 134152192 (131008K bytes) avail memory = 126504960 (123540K bytes). Yesterday, I replaced my ordinary ATAPI Diamond Data CD player with one of these: acd0: CD-RW at ata1-slave using UDMA33 The other disks are masters on each of the two ATA controllers: ad0: 6149MB [13328/15/63] at ata0-master UDMA33 ad1: 6149MB [13328/15/63] at ata1-master UDMA33 After producing a non-working CD with burncd, probably because of the ill-advised placement of a "data" file, I tried to erase the CD-RW disk before trying again. So I did something like: burncd -e -f /dev/acd0c erase Over the next few seconds my X session locked-up hard, apart from the mouse, which could still move. I was also unable to connect to the box over my LAN, using ssh. Since the CD erase operation still seemed to be happening, I decided to just let it go for a while, to see if that would stop. Sure enough, many minutes later (I didn't time it), the disk ejected itself, and my X session restarted itself, probably because I had been madly pressing ctrl-alt-backspace while things were locked up. So the system did not actually crash at all, but it became unuseful for a very long time. Afterwards, the logs and the console were seen to contain these messages: > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 7936, size: 36864 > swap_pager: indefinite wait buffer: device: #ad/0x30009, blkno: 47904, size: 4096 I'm guessing that this is not expected behaviour. Is there anything that I can do to stop it from happening, besides just not using the burncd erase command? Should I have some part of my system configured differently? Thanks, -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 17:17: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ghostwheel.tribble.net (ghostwheel.tribble.net [206.124.26.66]) by hub.freebsd.org (Postfix) with ESMTP id 52ED037B401 for ; Wed, 27 Jun 2001 17:17:05 -0700 (PDT) (envelope-from tribble@ghostwheel.tribble.net) Received: (from tribble@localhost) by ghostwheel.tribble.net (8.11.3/8.11.1) id f5S0H0S56707 for freebsd-stable@freebsd.org; Wed, 27 Jun 2001 18:17:00 -0600 (MDT) (envelope-from tribble) Date: Wed, 27 Jun 2001 18:17:00 -0600 From: Paul To: freebsd-stable@freebsd.org Subject: make buildkernel and conventional kernel build fail Message-ID: <20010627181700.A56655@tribble.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is anyone else experiencing this problem? On two separate machines now, cvsup'd to -STABLE, I get the following error when trying to compile. Doesn't matter if it's GENERIC, or my customer kernel... i get the same thing either way: cc -c -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -I/usr/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 -fomit-frame-pointer /usr/src/sys/i386/i386/atomic.c In file included from /usr/src/sys/i386/i386/atomic.c:47: machine/atomic.h: In function `atomic_set_char': machine/atomic.h:106: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_char': machine/atomic.h:107: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_char': machine/atomic.h:108: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_char': machine/atomic.h:109: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_short': machine/atomic.h:111: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_short': machine/atomic.h:112: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_short': machine/atomic.h:113: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_short': machine/atomic.h:114: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_int': machine/atomic.h:116: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_int': machine/atomic.h:117: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_int': machine/atomic.h:118: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_int': machine/atomic.h:119: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_long': machine/atomic.h:121: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_long': machine/atomic.h:122: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_long': machine/atomic.h:123: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_long': machine/atomic.h:124: inconsistent operand constraints in an `asm' *** Error code 1 --snip-- I have tried with and without -march=pentiumpro, with and without optimizations... am I alone here? Regards, Paul http://www.tribble.net/ "Supreme Court says pornography is anything without artistic merit that causes sexual thought, that's their definition, essentially. No artistic merit, causes sexual thought. Hmm. Sounds like... every commercial on television, doesn't it?" -- Bill Hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 17:38:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 747AC37B401 for ; Wed, 27 Jun 2001 17:38:47 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: from hornet.unixfreak.org (hornet [63.198.170.140]) by bazooka.unixfreak.org (Postfix) with ESMTP id 3E7533E2F; Wed, 27 Jun 2001 17:38:46 -0700 (PDT) To: Paul Cc: freebsd-stable@freebsd.org Subject: Re: make buildkernel and conventional kernel build fail In-Reply-To: <20010627181700.A56655@tribble.net>; from tribble@tribble.net on "Wed, 27 Jun 2001 18:17:00 -0600" Date: Wed, 27 Jun 2001 17:38:46 -0700 From: Dima Dorfman Message-Id: <20010628003846.3E7533E2F@bazooka.unixfreak.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Paul writes: > Is anyone else experiencing this problem? On two separate machines now, > cvsup'd to -STABLE, I get the following error when trying to compile. > Doesn't matter if it's GENERIC, or my customer kernel... i get the same > thing either way: Have you done a buildworld? Did it succeed? > > cc -c -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys > -I/usr/src/sys/../include -I/usr/src/sys/contrib/ipfilter -D_KERNEL > -include opt_global.h -elf -mpreferred-stack-boundary=2 > -fomit-frame-pointer /usr/src/sys/i386/i386/atomic.c > In file included from /usr/src/sys/i386/i386/atomic.c:47: > machine/atomic.h: In function `atomic_set_char': > machine/atomic.h:106: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_clear_char': > machine/atomic.h:107: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_add_char': > machine/atomic.h:108: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_subtract_char': > machine/atomic.h:109: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_set_short': > machine/atomic.h:111: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_clear_short': > machine/atomic.h:112: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_add_short': > machine/atomic.h:113: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_subtract_short': > machine/atomic.h:114: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_set_int': > machine/atomic.h:116: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_clear_int': > machine/atomic.h:117: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_add_int': > machine/atomic.h:118: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_subtract_int': > machine/atomic.h:119: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_set_long': > machine/atomic.h:121: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_clear_long': > machine/atomic.h:122: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_add_long': > machine/atomic.h:123: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_subtract_long': > machine/atomic.h:124: inconsistent operand constraints in an `asm' > *** Error code 1 > --snip-- > > I have tried with and without -march=pentiumpro, with and without > optimizations... am I alone here? > > Regards, > Paul > > http://www.tribble.net/ > > "Supreme Court says pornography is anything without artistic merit that > causes sexual thought, that's their definition, essentially. No artistic > merit, causes sexual thought. Hmm. Sounds like... every commercial on > television, doesn't it?" -- Bill Hicks > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 18:22:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id 6C4B437B401; Wed, 27 Jun 2001 18:22:01 -0700 (PDT) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id LAA12428; Thu, 28 Jun 2001 11:21:59 +1000 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id LAA14713; Thu, 28 Jun 2001 11:20:44 +1000 (EST) Message-Id: <200106280120.LAA14713@lightning.itga.com.au> X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4 From: Gregory Bond To: stable@freebsd.org, bugs@freebsd.org, davidn@freebsd.org Subject: Whence Stallion support for -Stable? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Jun 2001 11:20:44 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Cc'd to stable and bugs. Please reply to bugs only] The driver for Stallion multiport cards in 4-Stable is quite old. It doesn't support many of the newer cards, in particular the EasyIO-PCI card, nor any card manufactured since about 1998, which have a newer and unsupported UART chip. The driver in -Current is much the same with a few current-isms, afaict. There is a newer driver in the unsupported section of the stallion FTP site: ftp://ftp.stallion.com/drivers/unsupported/FreeBSD/stalbsd-2.0.0.tar.gz This supports all the new hardware but seems to be written for old (3.x-vintage) kernels, because it doesn't go anywhere near compiling under 4-Stable. There is a PR (http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22967) submitted by Jan L. Peterson which gives a new version of the above driver that does compile with 4-Stable, and seems to operate as expected (tho I haven't explored all the corner cases with flow control, modem control etc). But this PR is less than ideal. It contains a link to the new driver (fortunately still valid!) rather than the data itself, it requires bits from the original Stallion tarball, and doesn't update MAKEDEV or man pages. And the driver was written for 4.1.1 and will need updating for a few things that have changed since then (kqueue). It also "is using old-style compatibility shims" (whatever that means). This PR has been untouched since it was submitted 12 months ago. A related PR from the same period (http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19890) has been assigned to davidn but also remains otherwise untouched. I am willing (and I hope able!) to provide a jumbo patch to tie all these pieces together and update this driver in a manner that should be easy for a comitter to commit to -Stable. But I am running -Stable only, and have no experience in porting device drivers to -Current, and cannot test this driver in -Current. Is it worth me putting together such a comprehensive patch, or will the need to run it in -Current first mean my effort would be wasted? Any device writer / committer gurus care to offer some guidance? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 19:34:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 52EF437B401 for ; Wed, 27 Jun 2001 19:34:11 -0700 (PDT) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 3865 invoked by uid 0); 28 Jun 2001 02:34:10 -0000 Received: from pd950885f.dip.t-dialin.net (HELO speedy.gsinet) (217.80.136.95) by mail.gmx.net (mp002-rz3) with SMTP; 28 Jun 2001 02:34:10 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id XAA04577 for freebsd-stable@freebsd.org; Wed, 27 Jun 2001 23:03:47 +0200 Date: Wed, 27 Jun 2001 23:03:47 +0200 From: Gerhard Sittig To: "'freebsd-stable@freebsd.org'" Subject: Re: Staying *really stable* in FreeBSD Message-ID: <20010627230347.I17514@speedy.gsinet> Mail-Followup-To: "'freebsd-stable@freebsd.org'" References: <01C0FEFE.8EB2BA80.wmoran@iowna.com> <01062713134503.00453@mukappa.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <01062713134503.00453@mukappa.home.com>; from mupi@mknet.org on Wed, Jun 27, 2001 at 01:13:45PM -0600 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jun 27, 2001 at 13:13 -0600, Mike Porter wrote: > On Wednesday 27 June 2001 09:44, Bill Moran wrote: > > > > Is there a reason why you took this off the list? > > my mistake (or my mailer's depending on how you look at it). > If the majordomo config file for the list included the line > "reply-to: stable@freebsd.org" then all replies would by > defualt go back to the list. While this isn't ALWAYS > appropriate, it usually is.... Argh, nooooo! Not again, please! Just do *one* search for "reply-to" and "harmful" in your favourite search engine and make sure you understand what's broken about this dumb down approach. This has been discussed recently (besides coming up again and again without getting any better by doing so). virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 20:16:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id B412E37B405; Wed, 27 Jun 2001 20:16:18 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.4/8.11.3) with ESMTP id f5S3Fht38164; Wed, 27 Jun 2001 20:15:43 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: nik@freebsd.org Cc: juha@saarinen.org, chad@DCFinc.com, joe@zircon.seattle.wa.us, stable@freebsd.org Subject: Re: Staying *really stable* in FreeBSD In-Reply-To: <20010626234435.H461@canyon.nothing-going-on.org> References: <20010626140650.B9911@freeway.dcfinc.com> <20010626234435.H461@canyon.nothing-going-on.org> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010627201543C.jkh@osd.bsdi.com> Date: Wed, 27 Jun 2001 20:15:43 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This looks really good! Ship that baby! :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 20:20:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 9FC2E37B403 for ; Wed, 27 Jun 2001 20:20:41 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 19956 invoked by uid 0); 28 Jun 2001 03:20:32 -0000 Received: from pd950a3bf.dip.t-dialin.net (HELO kiste) (217.80.163.191) by mail.gmx.net (mail08) with SMTP; 28 Jun 2001 03:20:32 -0000 Message-ID: <004a01c0ff81$3a3093a0$0408a8c0@kiste> From: "Michael Nottebrock" To: "Gerhard Sittig" , "'freebsd-stable@freebsd.org'" References: <01C0FEFE.8EB2BA80.wmoran@iowna.com> <01062713134503.00453@mukappa.home.com> <20010627230347.I17514@speedy.gsinet> Subject: Re: Staying *really stable* in FreeBSD Date: Thu, 28 Jun 2001 05:20:00 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Gerhard Sittig" wrote: > On Wed, Jun 27, 2001 at 13:13 -0600, Mike Porter wrote: > > On Wednesday 27 June 2001 09:44, Bill Moran wrote: > > > > > > Is there a reason why you took this off the list? > > > > my mistake (or my mailer's depending on how you look at it). > > If the majordomo config file for the list included the line > > "reply-to: stable@freebsd.org" then all replies would by > > defualt go back to the list. While this isn't ALWAYS > > appropriate, it usually is.... > > Argh, nooooo! Not again, please! Just do *one* search for > "reply-to" and "harmful" in your favourite search engine and make > sure you understand what's broken about this dumb down approach. > This has been discussed recently (besides coming up again and > again without getting any better by doing so). And read http://www.metasystema.org/essays/reply-to-useful.mhtml , too. Those two documents should make it very clear, that the whole thing is a typical nonsense religious war, with the only possible conclusion being "I am not the listowner. I can do nothing about it but hit the correct key/button in my mailer & shut up". Greetings, Michael Nottebrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 27 22:54:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hq1.tyfon.net (hq1.tyfon.net [217.27.162.35]) by hub.freebsd.org (Postfix) with ESMTP id 9FC2037B401 for ; Wed, 27 Jun 2001 22:54:45 -0700 (PDT) (envelope-from dl@tyfon.net) Received: from localhost (localhost [127.0.0.1]) by hq1.tyfon.net (Postfix) with ESMTP id 1DD3E1C7DB for ; Thu, 28 Jun 2001 07:54:44 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by hq1.tyfon.net (Postfix) with ESMTP id D80591C5C9 for ; Thu, 28 Jun 2001 07:54:39 +0200 (CEST) Date: Thu, 28 Jun 2001 07:54:39 +0200 (CEST) From: Dan Larsson To: FreeBSD Stable List Subject: orm device (Option ROMs)? Message-ID: <20010628075142.M11162-100000@hq1.tyfon.net> Organization: Tyfon Svenska AB X-NCC-NIC: DL1999-RIPE X-NCC-RegID: se.tyfon MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by hq1.tyfon.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG orm0: