From owner-freebsd-stable Sun Jan 14 0:28:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 4753537B400 for ; Sun, 14 Jan 2001 00:28:27 -0800 (PST) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by david.siemens.de (8.11.0/8.11.0) with ESMTP id f0E8SPu19192; Sun, 14 Jan 2001 09:28:26 +0100 (MET) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.11.0/8.11.0) with ESMTP id f0E8SPS14678; Sun, 14 Jan 2001 09:28:25 +0100 (MET) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.11.2/8.11.2/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id f0E8SOB22690; Sun, 14 Jan 2001 09:28:24 +0100 (CET) Received: (from ust@localhost) by alaska.cert.siemens.de (8.11.2/8.11.2/alaska [ $Revision: 1.5 ]) id f0E8SNB81004; Sun, 14 Jan 2001 09:28:23 +0100 (CET) Date: Sun, 14 Jan 2001 09:28:23 +0100 From: Udo Schweigert To: Jordan Hubbard Cc: stable@FreeBSD.ORG Subject: Re: Charlie Root: 4.x-stable build report for Sat Jan 13 02:16:35 CST 2001 Message-ID: <20010114092823.A80881@alaska.cert.siemens.de> References: <60224.979409061@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <60224.979409061@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Sat, Jan 13, 2001 at 10:04:21AM -0800 X-Operating-System: FreeBSD 4.2-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 13, 2001 at 10:04:21 -0800, Jordan Hubbard wrote: > Somebody broke the -stable release build yesterday, looks like. > > .... > sh -e /usr/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 2880 /R/stage/mfsfd 8000 minimum2 > mknod: /dev/vnn0: File exists This seems to be a little problem with src/release/scripts/doFS.sh This patch fixed it for me: --- doFS.sh.orig Fri Jan 12 15:05:02 2001 +++ doFS.sh Sun Jan 14 09:23:10 2001 @@ -26,8 +26,6 @@ rm -f /dev/*vnn* mknod /dev/rvnn${u} c 43 `expr 65538 + $u '*' 8` mknod /dev/rvnn${u}c c 43 `expr 2 + $u '*' 8` -mknod /dev/vnn${u} b 15 `expr 65538 + $u '*' 8` -mknod /dev/vnn${u}c b 15 `expr 2 + $u '*' 8` case `uname -r` in 5.*) mknod /dev/vnn${u} c 43 `expr 65538 + $u '*' 8` Mit freundlichen Grüßen/Best regards Udo Schweigert -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : Udo.Schweigert@cert.siemens.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 0:30:38 2001 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id 96B7137B400 for ; Sun, 14 Jan 2001 00:30:13 -0800 (PST) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.1/8.11.1) with ESMTP id f0E8Tb887400; Sun, 14 Jan 2001 19:29:39 +1100 (EST) (envelope-from marka@nominum.com) Message-Id: <200101140829.f0E8Tb887400@drugs.dv.isc.org> To: Jason F Wells Cc: Mike Andrews , stable@FreeBSD.ORG From: Mark.Andrews@nominum.com Subject: Re: Weird sporadic DNS resolution problems In-reply-to: Your message of "Sat, 13 Jan 2001 12:37:54 PDT." <20010113123754.B1299@fry.routermonkey.com> Date: Sun, 14 Jan 2001 19:29:37 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For what it's worth, I've also experienced problems with > Sendmail+BIND interaction. I've specifically had problems receiving > mail from dml.com, which hosts the zebra mailing list. > > I finally had to resort to putting an entry in /etc/hosts so that > I could get mail from the mailing list. > > Without the entry in /etc/hosts, I get the same sendmail error: > Domain of sender address owner-zebra@dml.com does not resolve > > The interesting difference in my problem (I think it's interesting...) > is that neither of the nameservers for dml.com are lame; They are lame. They are returning non-authoratative answers. Note the lack of a "aa" (authoratative answer) flag. If you query further you find other problems. ; <<>> DiG 8.3 <<>> mx dml.com @YEBISU.DIGITAL-MAGIC.CO.JP ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; QUERY SECTION: ;; dml.com, type = MX, class = IN ;; ANSWER SECTION: dml.com. 1D IN MX 10 mail.dml.com. ;; ADDITIONAL SECTION: mail.dml.com. 1D IN A 202.227.9.98 ;; Total query time: 552 msec ;; FROM: drugs.dv.isc.org to SERVER: YEBISU.DIGITAL-MAGIC.CO.JP 202.227.9.98 ;; WHEN: Sun Jan 14 19:27:58 2001 ;; MSG SIZE sent: 25 rcvd: 62 ; <<>> DiG 8.3 <<>> mx dml.com @RS.DIGITAL-MAGIC.CO.JP ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3 ;; QUERY SECTION: ;; dml.com, type = MX, class = IN ;; ANSWER SECTION: dml.com. 13h57m7s IN MX 10 mail.dml.com. ;; AUTHORITY SECTION: dml.com. 22h53m35s IN NS RS.DIGITAL-MAGIC.CO.JP. dml.com. 22h53m35s IN NS YEBISU.DIGITAL-MAGIC.CO.JP. ;; ADDITIONAL SECTION: mail.dml.com. 20h43m50s IN A 202.227.9.98 RS.DIGITAL-MAGIC.CO.JP. 13h28m35s IN A 203.181.89.7 YEBISU.DIGITAL-MAGIC.CO.JP. 13h28m15s IN A 202.227.9.98 ;; Total query time: 773 msec ;; FROM: drugs.dv.isc.org to SERVER: RS.DIGITAL-MAGIC.CO.JP 203.181.89.7 ;; WHEN: Sun Jan 14 19:26:13 2001 ;; MSG SIZE sent: 25 rcvd: 151 > they both > return valid A records for dml.com using dig, but my named seems to > think that there isn't an A record until I stop and restart named. > Then, when I do an nslookup / dig, it returns the correct result for > a while, until it stops working again. > > I'm pretty sure the problem is on my end (Sendmail and/or BIND) or > else a lot of people on the zebra mailing list would be complaining > about how dml.com doesn't resolve. > > On Fri, Jan 12, 2001 at 04:34:37PM -0500, Mike Andrews wrote: > > On Fri, 12 Jan 2001 Mark.Andrews@nominum.com wrote: > > > > > > When one (but not both) of the nameservers for a domain replies > > > > non-authoritatively, named will cache a negative response, rather than > > > > asking the other nameserver. > > > > > > No. It caches that the server is lame for the zone then tries > > > other servers. > > > > > > > Subsequent lookups return an immediate > > > > failure. > > > > > > And what is logged when that happens? > > > > At the time of those lookups, nothing from Bind. Sendmail logs "Domain of > > sender address foo@bar does not resolve". When it caches that the server > > is lame, bind does log the expected "Lame server on foo.blah" message. > > > > > > > > Restarting the nameserver, and then immediately querying the > > > > same problematic domain DOES work, but only the first query. After a f > ew > > > > minutes/hours the domain stops working again. > > > > > > This sounds more like a bad delegation, parent and child > > > zones dissagreeing on the nameserver RRset, than a lame > > > server. > > > > > Servers are supposed to be serving the zone *before* they are > > > delegated to. > > > > Either way, the other guys have their nameserver screwed up pretty badly. > > I knew this already, though... > > > > > > > Well both the servers for setel.com are lame as are se-tel.com. > > > > > > If all the sources of information are bad what do you expect > > > the namesever to do. > > > > Hm. My named thinks ns2.se-tel.com is definitely lame, but not ns1 (at > > least it's never logging ns1 as lame...) > > > > > > > > In one sense this is "not my problem" because their name server shouldn > 't > > > > be answering non-authoritatively in the first place. But the fact that > > > > this started happening after a make world a few months ago, and that I > > > > feel it should be a slight bit more tolerant of other people's sloppy > > > > configurations, makes it my problem. > > > > And this is the real question that remains: > > > > Why did receiving email from places with one lame and one not-lame > > nameserver work reliably in 4.1.1-RELEASE, and not in 4.2-STABLE? > > > > I realize (like in the farmersfrankfort.com) case that it's Qwest's > > problem (not mine) that the second nameserver for that domain is lame. But > > in 4.1.1-RELEASE it would still eventually get the right info from the one > > that did work. It doesn't anymore. What changed in Bind or Sendmail to > > make it less tolerant of everyone else's broken nameservers? I'm starting > > to wonder, like Mike Tancsa's earlier response, if this is maybe specific > > to Sendmail, or a Bind+Sendmail interaction... > > > > > > Mike Andrews * mandrews@dcr.net * mandrews@bit0.com * http://www.bit0.com > > VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY > > Internet access for Frankfort, Lexington, Louisville and surrounding counti > es > > www.fark.com: If it's not news, it's Fark. (Or something like that.) > > > > > > > > > > > > > > > > > > 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 -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 2:32:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 375FC37B401 for ; Sun, 14 Jan 2001 02:31:57 -0800 (PST) Received: from FreeBSD.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id CAA59215 for ; Sun, 14 Jan 2001 02:31:56 -0800 (PST) (envelope-from DougB@FreeBSD.org) Message-ID: <3A61801C.F66BC6AB@FreeBSD.org> Date: Sun, 14 Jan 2001 02:31:56 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Semi Head's Up: [Fwd: cvs commit: src/usr.sbin/adduser rmuser.perl] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings folks, I've updated the rmuser perl script as noted below. The script was tested under several different enviornments, and has had 7 weeks to mellow in -current. However, it's a pretty big change, and I felt it worthwhile to let folks know. This change won't affect a running system, the only possible failure is if you try to use the script to remove a user, and then it will either work or not work in an obvious way. :) Doug -------- Original Message -------- Subject: cvs commit: src/usr.sbin/adduser rmuser.perl Date: Sun, 14 Jan 2001 02:21:12 -0800 (PST) From: Doug Barton To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org dougb 2001/01/14 02:21:12 PST Modified files: (Branch: RELENG_4) usr.sbin/adduser rmuser.perl Log: MFC 1.11 and 1.12. Make sure that if a user is in the db rmuser can remove them. My fix is more aggressive than the originator's. PR: misc/22278 Submitted by: Kevin Way Revision Changes Path 1.8.2.2 +13 -43 src/usr.sbin/adduser/rmuser.perl PR: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=22278 http://www.FreeBSD.org/cgi/cvsweb.cgi/src/usr.sbin/adduser/rmuser.perl.diff?&r1=1.8.2.1&r2=1.8.2.2&f=h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 5:43:54 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 7781B37B400 for ; Sun, 14 Jan 2001 05:43:36 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0EDhUi29633; Sun, 14 Jan 2001 08:43:30 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0EDhNd29625; Sun, 14 Jan 2001 08:43:23 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010114083601.0178f2c8@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sun, 14 Jan 2001 08:43:22 -0500 To: Mark.Andrews@nominum.com, Jason F Wells From: Mike Tancsa Subject: Re: Weird sporadic DNS resolution problems Cc: Mike Andrews , stable@freebsd.org In-Reply-To: <200101140829.f0E8Tb887400@drugs.dv.isc.org> References: 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 X-Loop: FreeBSD.ORG At 07:29 PM 1/14/2001 +1100, Mark.Andrews@nominum.com wrote: > > The interesting difference in my problem (I think it's interesting...) > > is that neither of the nameservers for dml.com are lame; > > They are lame. They are returning non-authoratative answers. > Note the lack of a "aa" (authoratative answer) flag. If you > query further you find other problems. Yes, most definitely LAME. The question I have however is when did the behavior of rejecting mail from LAME domains take place? It was not always this way and seems specific to FreeBSD in that the same version of sendmail on LINUX does not reject mail from LAME domains, nor has a problem of sending mail to LAME domains using the same cf files. I hope gshapiro does not mind, but I will cc him as he might be able to shed some light on the specifics of the FreeBSD issue. ---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 Sun Jan 14 6:34:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from c007.snv.cp.net (c007-h008.c007.snv.cp.net [209.228.33.214]) by hub.freebsd.org (Postfix) with SMTP id D9AFC37B698 for ; Sun, 14 Jan 2001 06:34:34 -0800 (PST) Received: (cpmta 14595 invoked from network); 14 Jan 2001 06:34:33 -0800 Received: from dsl-216-227-91-85.telocity.com (HELO zoso) (216.227.91.85) by smtp.telocity.com (209.228.33.214) with SMTP; 14 Jan 2001 06:34:33 -0800 X-Sent: 14 Jan 2001 14:34:33 GMT From: "Otter" To: "Roman Shterenzon" , "Alessandro de Manzano" Cc: "stable@freebsd.org" Subject: RE: PR #24059 - USB still broken in SMP ! Date: Sun, 14 Jan 2001 09:39:42 -0500 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: <979434079.3a60fa5fc6469@webmail.harmonic.co.il> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG not sure about "relevant" upgrades to the bios version, but yeah. there is a newer one at http://cgi.asus.com.tw/cgi-bin/dl.asp?filename=mb/slot1/440bx/p2b-ds/b xds1009.zip. I just bought a p2b-ds for my nat box. i've got twin p2-300's and 320mb ram on it. it seems to be working fine for my needs, though i'm not using any usb devices. do you have any other comments or complaints about the board running under -stable? -Otter }-----Original Message----- }From: owner-freebsd-stable@FreeBSD.ORG }[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Roman }Shterenzon }Sent: Saturday, January 13, 2001 8:01 PM }To: Alessandro de Manzano }Cc: stable@freebsd.org }Subject: Re: PR #24059 - USB still broken in SMP ! } } }Quoting Alessandro de Manzano : } }> > Ok. I've got a P2B-DS motherboard (rev 1.06 I believe }with the latest }> BIOS) }> > and I'm running an SMP kernel using two 500Mhz Pentium }III's. I use }> USB to }> > connect to my Canon S10 digital camera all the time. No }problems. I've }> not }> > used USB for anything other than this though--no mice, keyboards, }> disks, }> > memory readers, etc. }> }> Thanks for the answer ! :-) }> }> I'm happy to hear USB works for you, so I could only guess }some things: }> }> 1) we have different USB controllers, the Asus P2B-DS (a MB I have }> where I work) use Intel chipset and my Microstar MS-6321 use an VIA }> one. }> }> 2) I tried with the mouse only, also if error reports are }reported by }> kernel also if the USB bus is "empty" and idle. }> }> I really hope my problem could be resolved in a future }evoltion of USB }> drivers.. ;-) }> }> Thanks a lot! }> } }Check if your motherboard vendor has some BIOS updates that }are relevant. } }--Roman Shterenzon, UNIX System Administrator and Consultant }[ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] } } }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 Jan 14 6:38:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 1006937B400 for ; Sun, 14 Jan 2001 06:37:52 -0800 (PST) Received: from hyperion.informatik.rwth-aachen.de (hyperion.Informatik.RWTH-Aachen.DE [137.226.112.212]) by nets5.rz.rwth-aachen.de (8.10.1/8.10.1/5) with ESMTP id f0EEbom16796 for ; Sun, 14 Jan 2001 15:37:50 +0100 (MET) 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 PAA27222 for ; Sun, 14 Jan 2001 15:36:52 +0100 (MET) Received: (from stolz@localhost) by agamemnon.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1-gb-2) id PAA11555 for freebsd-stable@FreeBSD.ORG; Sun, 14 Jan 2001 15:37:43 +0100 (MET) Date: Sun, 14 Jan 2001 15:37:43 +0100 From: Volker Stolz To: freebsd-stable@FreeBSD.ORG Subject: make -DNOPROFILE=true installworld fails via NFS Message-ID: <20010114153743.A11458@agamemnon.informatik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i Organization: Chair for CS II 1/2, Anomalous Programming Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While updating a 4.2-RELEASE client who mounts /usr/src & /usr/obj from a faster machine the following happens: make -DNOPROFILE=true -DNO_FORTRAN=true installworld ... ===> lib/libcom_err cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_err.h /usr/include cd /usr/src/lib/libcom_err && install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/../../contrib/com_err/com_right.h /usr/include install -c -o root -g wheel -m 444 libcom_err.a /usr/lib install -c -o root -g wheel -m 444 libcom_err_p.a /usr/lib install: libcom_err_p.a: No such file or directory *** Error code 71 What am I doing wrong? Running the same make as above with -k[eepgoing] shows the same error on (almost?) every library; the make on the server doesn´t show this behaviour at all?! -- \usepackage[latin1]{inputenc}! 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 Sun Jan 14 6:59:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 46FC137B400 for ; Sun, 14 Jan 2001 06:59:00 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id f0EEwvx79749; Sun, 14 Jan 2001 09:58:57 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200101141458.f0EEwvx79749@whizzo.transsys.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Bruce Burden Cc: freebsd-stable@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: /swap too large? What?? References: <20010113002643.A33278@tigerfish2.my.domain> <200101131927.f0DJRSS34276@earth.backplane.com> <20010113150956.B37497@tigerfish2.my.domain> In-reply-to: Your message of "Sat, 13 Jan 2001 15:09:56 CST." <20010113150956.B37497@tigerfish2.my.domain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Jan 2001 09:58:57 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hi Matt, > > > > The only thing that can cause this is if you have configured an > > absurdly large NSWAPDEV. > > > Well, I had NSWAPDEV set for 20 (why? I don't know!) but > according to my calculations, that should still allow a 3.4GB > swap, or 2x what I have. Probably for the same reason that I (until very recently did); it's 20 in sys/i386/conf/LINT and that got cloned while building a customized config. Possibly 20 is a "bad" example? louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 7:19: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id 0742737B400; Sun, 14 Jan 2001 07:18:31 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14Hou5-000EJ3-00; Sun, 14 Jan 2001 18:17:10 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14HjSv-000071-00; Sun, 14 Jan 2001 12:28:45 +0300 Date: Sun, 14 Jan 2001 12:28:45 +0300 From: Odhiambo Washington To: FBSD-STABLE Cc: FBSD-Q Subject: Strange device probe behavior Message-ID: <20010114122845.A400@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , FBSD-STABLE , FBSD-Q Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD poeza.iconnect.co.ke 4.2-STABLE FreeBSD 4.2-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I accepted all types of flaming on this - the answer in most important. Below I attach the output of dmesg: This HP Netserver E60 box was running 3.5-STABLE. A few days back I decided to push it to 4.2-STABLE. Now some strange device (not quite strange though) takes the kernel about 15 seconds to probe, just as it leaves the for SCSI devices to settle..hmmm..I never saw this with 3.5-STABLE, so I was just wondering if maybe I missed some option when I compiled my 4.x kernel... I have indicated using ^^^^^ the device that scares my life.... Thanks in advance. ### DMESG OUTPUT ## Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Sat Jan 13 14:05:06 EAT 2001 root@poeza.iconnect.co.ke:/usr/obj/usr/src/sys/KERN4.x Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387fbff real memory = 67043328 (65472K bytes) avail memory = 61755392 (60308K bytes) Preloaded elf kernel "kernel" at 0xc0369000. VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc0306962 (1000022) VESA: ATI MACH64 Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0x1860-0x186f at device 4.1 on pci0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is where 15 or so seconds lapse before the probe continues!! ata0: at 0x1f0 irq 14 on atapci0 uhci0: port 0x1840-0x185f irq 11 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: port 0xe800-0xe80f at device 4.3 on pci0 ahc0: port 0x1000-0x10ff mem 0xfc100000-0xfc100fff irq 10 at device 5.0 on pci0 ahc0: Using left over BIOS settings aic7895C: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0x1400-0x14ff mem 0xfc101000-0xfc101fff irq 10 at device 5.1 on pci0 ahc1: Host Adapter Bios disabled. Using default SCSI device parameters aic7895C: Wide Channel B, SCSI Id=7, 32/255 SCBs fxp0: port 0x1800-0x183f mem 0xfc000000-0xfc0fffff,0xfc102000-0xfc102fff irq 11 at device 6.0 on pci0 fxp0: Ethernet address 00:e0:18:c2:61:69 pcib2: at device 12.0 on pci0 pci2: on pcib2 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 acd0: CDROM at ata0-master using WDMA2 Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8678MB (17773524 512 byte sectors: 64H 32S/T 8678C) Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8678MB (17773524 512 byte sectors: 64H 32S/T 8678C) ####################### -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. What the caterpillar calls the end of the world, the master calls a butterfly. -Richard Bach To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 8: 8:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cj409896-a.reston1.va.home.com (cj409896-a.reston1.va.home.com [24.23.165.156]) by hub.freebsd.org (Postfix) with ESMTP id 734CE37B401; Sun, 14 Jan 2001 08:08:12 -0800 (PST) Received: from localhost (dwagner@localhost) by cj409896-a.reston1.va.home.com (8.11.1/8.11.1) with ESMTP id f0EG84x47121; Sun, 14 Jan 2001 11:08:04 -0500 (EST) (envelope-from dawagner@vt.edu) Date: Sun, 14 Jan 2001 11:08:04 -0500 (EST) From: David Wagner X-X-Sender: To: Odhiambo Washington Cc: FBSD-STABLE , FBSD-Q Subject: Re: Strange device probe behavior In-Reply-To: <20010114122845.A400@poeza.iconnect.co.ke> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Jan 2001, Odhiambo Washington wrote: > atapci0: port 0x1860-0x186f at device > 4.1 on pci0 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > This is where 15 or so seconds lapse before the probe continues!! Well, if it makes you feel any better, my system does this too. It has: atapci0: port 0x18a0-0x18af at device 7.1 on pci0 Mine's a Gateway system I bought a couple years ago and recently turned into a FreeBSD box. I've never noticed any problems with it -- once the probe continues everything seems to be fine. I certainly have no idea _why_ it does it, but at least it doesn't seem to be cause for panic. :) ______________________________________________________________________ David Wagner dawagner@vt.edu Reston, Virginia ICQ: 9963339 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 8:41:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from routermonkey.com (fry.routermonkey.com [204.209.9.25]) by hub.freebsd.org (Postfix) with ESMTP id 07F8637B402 for ; Sun, 14 Jan 2001 08:41:30 -0800 (PST) Received: (from jason@localhost) by routermonkey.com (8.11.1/8.11.1) id f0EGfkY53595; Sun, 14 Jan 2001 09:41:46 -0700 (MST) (envelope-from jason) Date: Sun, 14 Jan 2001 09:41:46 -0700 From: Jason F Wells To: Mike Tancsa Cc: Mark.Andrews@nominum.com, Mike Andrews , stable@freebsd.org Subject: Re: Weird sporadic DNS resolution problems Message-ID: <20010114094146.A15583@fry.routermonkey.com> References: <200101140829.f0E8Tb887400@drugs.dv.isc.org> <4.2.2.20010114083601.0178f2c8@marble.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4.2.2.20010114083601.0178f2c8@marble.sentex.net>; from mike@sentex.net on Sun, Jan 14, 2001 at 08:43:22AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 14, 2001 at 08:43:22AM -0500, Mike Tancsa wrote: > At 07:29 PM 1/14/2001 +1100, Mark.Andrews@nominum.com wrote: > > > The interesting difference in my problem (I think it's interesting...) > > > is that neither of the nameservers for dml.com are lame; > > > > They are lame. They are returning non-authoratative answers. > > Note the lack of a "aa" (authoratative answer) flag. If you > > query further you find other problems. > > Yes, most definitely LAME. The question I have however is when did the > behavior of rejecting mail from LAME domains take place? It was not always > this way and seems specific to FreeBSD in that the same version of sendmail > on LINUX does not reject mail from LAME domains, nor has a problem of > sending mail to LAME domains using the same cf files. I hope gshapiro does > not mind, but I will cc him as he might be able to shed some light on the > specifics of the FreeBSD issue. > Yes, you are both right. I apologize for confusing the issue by saying they weren't. I didn't notice the aa flag wasn't set on the dig results. Like Mike Tansca, though, I'd like to know exactly what is happening here. It seems to me that it either should accept mail, or not accept mail (I don't know what the "right" behaviour is if you only have a non-authoritative result), but instead it accepts mail for a bit, and then stops. Jason. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 9:13:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id B97FF37B402 for ; Sun, 14 Jan 2001 09:13:30 -0800 (PST) Received: from hagbard (p3E9B9542.dip.t-dialin.net [62.155.149.66]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id SAA02702 for ; Sun, 14 Jan 2001 18:13:28 +0100 (MET) Reply-To: From: "Bernd Fuerwitt" To: Subject: serial console Date: Sun, 14 Jan 2001 18:13:29 +0100 Message-ID: <918447C44E5CD31196740060B01A681602C190@leviathan.illu42.de> 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 CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, I just updated one of our routers from 4.0-RELEASE to 4.2-RELEASE (using cvsup and buildworld) and now the serial console doesn't work anymore. The file /boot.config contains -P and /boot/loader.conf contains console=comconsole. I get a login prompt at ttyd0, but no console. Messages stop after the kernel starts booting. Meanwhile I have updated to 4.2-STABLE but nothing changed. What am I doing wrong ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 9:56: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id E72FA37B402 for ; Sun, 14 Jan 2001 09:55:38 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id DBAB61360C; Sun, 14 Jan 2001 12:55:32 -0500 (EST) Date: Sun, 14 Jan 2001 12:55:32 -0500 From: Chris Faulhaber To: Volker Stolz Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make -DNOPROFILE=true installworld fails via NFS Message-ID: <20010114125532.A4811@peitho.fxp.org> Mail-Followup-To: Chris Faulhaber , Volker Stolz , freebsd-stable@FreeBSD.ORG References: <20010114153743.A11458@agamemnon.informatik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010114153743.A11458@agamemnon.informatik.rwth-aachen.de>; from stolz@I2.Informatik.RWTH-Aachen.DE on Sun, Jan 14, 2001 at 03:37:43PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 14, 2001 at 03:37:43PM +0100, Volker Stolz wrote: > While updating a 4.2-RELEASE client who mounts /usr/src & /usr/obj from > a faster machine the following happens: > > make -DNOPROFILE=true -DNO_FORTRAN=true installworld > make NOPROFILE=true NO_FORTRAN=true installworld -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 10: 4:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from uvika.dn.ua (unknown [195.184.223.26]) by hub.freebsd.org (Postfix) with ESMTP id E959537B69C for ; Sun, 14 Jan 2001 10:04:02 -0800 (PST) Received: from uvika.dn.ua (i-ris.donbass.com [195.184.222.22]) by uvika.dn.ua (8.11.1/8.11.1) with SMTP id f0EI3Q899851 for ; Sun, 14 Jan 2001 20:03:27 +0200 (EET) Message-Id: <200101141803.f0EI3Q899851@uvika.dn.ua> From: "Igor E. Segal" To: Subject: Momentary readout information Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sun, 14 Jan 2001 20:03:51 +0200 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sears! We are glad to propose You the unique opportunity of fundamental life changing with the consultation of Universe Informational Center. We suggest momentary readout information from any animate and inanimate object independently from time and distance. Diagnostics of everything alive, that exists on the Earth and in the Space. It's enough for you to name the living being and the age or the object of your interest, its number and what you'd like to find out about it. The exactness of answer depends on the exactness of an asked question. Everything occurs as in computer system. You formulate your question, briefly and exactly, and receive a brief and exact answer. SCIENCE, TECHNICS, ASTRONAUTICS We can diagnose any facilities, buildings, constructions, examine the lands for construction. We can analyse of expedience and prospects of developed scientific, military and state programs, scientific hypothesis and discoveries. Drawing conclusions about all future positive and negative qualities of an invention, including every detail of a future machine. If it is a vehicle for Mars or Venus - we'll describe its mode of work and its service life at this planet. We'll say beforehand what detail will go out of service and why, what is desirable to improve, to change and so on. At the same time we can already now describe not only what your vehicle will find there, but also what is really exists there: kind of vegetation, its color, growth, taste, smell, presence of water, minerals, forms of intellect, etc. We know the time of contact failure with any apparatus at any planet, we can find the reason and re-establish the contact. For military, navy, space and other subdivisions of state and united forces without departure to the location we can instantly look through the technical condition of any fighting unit, warship, spaceship of any country, professional training of any separate serviceman, an expedience of war actions and their final result, and we can give answers to other questions of interest. Complete examination of all military and civil planes, rockets, etc. As to their security and a state of wear at the whole territory of any country. Instant checking of service ability of all devices, reactors, control instruments and sensors at any sections independently of its distance and location. Prediction of the any spaceship launch result 3-4 days before the event. In case of unsuccessful launch we can locate the cause of a fault in a spaceship beforehand. It's possible to invent the machines of the far future (XXI, XXII c.) now. Several minutes it is enough to form future staff of designers, scientists, leaders - to choose the most talented of all students of high schools (in any branch). It's possible to talk to any archaeological finding, to go with it deep through decades, centuries, millennium, etc. An instant answer whether there is a virus in your computer. Answers to the questions of science: structure of the Universe, genesis of human and all animate, the secrets of microcosm, of gene structures and activity of human brain, search of new sources of energy, mysteries of time, etc. Examination of the Earth, the Sun, the Moon, any planet, etc. in section. Questions should be asked by specialists, the answers will be given instantly and at once to any question. PUBLIC HEALTH, ECOLOGY According to your wish we can examine the state of each organ separately: blond circulatory, nervous and other systems. Complete diagnostics of any person health during several minutes independently of distance and location. ( It's enough to point out name and age). We can analyze suitability of any medicine to a definite person, expedience of an impending operation and its reasons. If you are still going to be operated, I can prompt a favorable dale and hour for a perfect operation. ( It's enough to point out a doctor's name and place of operation). We can predict and examine the course of pregnancy, sex and growth of a baby, etc. For specialists - the medicine of future, the methods of struggle with cancer, viruses, ageing, vaccine against AIDS and other questions. Examination of territory and food as to their ecological safety. ECONOMICS, POLITICS Prediction of real chances of victory in pre-election and election campaigns of this or that candidate. Any member of government can instantly find out what is dune in other government establishments, their true attitude to governments and to the country in the whole. It is possible to find out what is done in any town of country, etc. In case you have to lead business meetings, you may know it beforehand how negotiations will go what can be expected from your partners, to financial state, the results of negotiations, future deals, credit rating of your partners and whether al all they have that what they offer you. You may know it beforehand whether your money or credit you are going to lend be returnable. (It is enough to name a debtor). If you hire a man for work, it is enough for you to name a position he is hired for and you may know all about his professional, business and human qualities, etc. For the leaders of all levels - all questions related their life and activity, including the questions of security. PRIVATE With our help you may talk to any relatives and acquaintances at any distance, find out their true attitude towards you, their thoughts, thoughts and attitude to you of your pets, trees and flowers in your garden, your cars - of all animate and inanimate objects. You may know what name is suitable for your child, what occupation your child is intended for, whether it is worth for him or her to marry (expedience of this or that marriage and its reasons). Your past (including your last lives), present and future. Your predestination and tasks in this life. The ways of solving problems. You'll get assistance in buying any immovable property. It is possible to examine quality of any selected wares, safety of your trips, flights and voyages. If you want to know about the weather in a day of your interest, it is enough for you to point out a day of week, month, year and You will get all necessary information. We have a favour to ask for You don`t ask the questions about non-existent objects and criminal or heated - playing features. Our work is being constructed at the base of agreement or contract. Please, ask You first three questions for free and, if You will satisfied by the results, we shell sign agreement about consultation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 11:25:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from realtime.net (dragon.realtime.net [205.238.128.89]) by hub.freebsd.org (Postfix) with SMTP id A722537B401 for ; Sun, 14 Jan 2001 11:24:56 -0800 (PST) Received: from tigerfish2.my.domain ([205.238.153.161]) by realtime.net ; Sun, 14 Jan 2001 13:24:45 -0600 Received: (from brucegb@localhost) by tigerfish2.my.domain (8.11.1/8.11.1) id f0EJPKZ20987 for freebsd-stable@freebsd.org; Sun, 14 Jan 2001 13:25:20 -0600 (CST) (envelope-from brucegb) Date: Sun, 14 Jan 2001 13:25:20 -0600 From: Bruce Burden To: freebsd-stable@freebsd.org Subject: Re: /swap too large? What?? Message-ID: <20010114132520.A79824@tigerfish2.my.domain> References: <20010113002643.A33278@tigerfish2.my.domain> <200101131927.f0DJRSS34276@earth.backplane.com> <20010113150956.B37497@tigerfish2.my.domain> <200101132205.f0DM5pJ35749@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101132205.f0DM5pJ35749@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Jan 13, 2001 at 02:05:51PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you for the replies, folks. > > : I have dropped things back to NSWAPDEV=3, and see if that > : does anything. > > That will fix it. > Indeed it did. While have rarely seen swapping take place under normal situations (GIMP, as I mentioned, will swap), it was a bit nerve-wracking to see free memory dropping somewhat low w/out any swap space. On the other hand, I did note that garbage collection is much more aggressive when you don't have any swap space! Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 11:27:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 96C6E37B401 for ; Sun, 14 Jan 2001 11:27:15 -0800 (PST) Received: from hagbard (p3E9B9542.dip.t-dialin.net [62.155.149.66]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id UAA09042; Sun, 14 Jan 2001 20:27:03 +0100 (MET) Reply-To: From: "Bernd Fuerwitt" To: "'Roger'" Cc: Subject: RE: Serial Console Date: Sun, 14 Jan 2001 20:27:05 +0100 Message-ID: <918447C44E5CD31196740060B01A681602C191@leviathan.illu42.de> 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 CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <918447C44E5CD31196740060B01A681604D2A6@leviathan.illu42.de> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi > -----Original Message----- > From: rmsavard@Haydn.henoc.com [mailto:rmsavard@Haydn.henoc.com]On > Behalf Of Roger > Sent: Sonntag, 14. Januar 2001 20:20 > To: Furwitt, Bernd > Subject: Serial Console > > > Hi Bernd, > > I use the 3 following files and it works fine. > I'm not sure if you should build another kernel, but > I would assume so. > > You know : cd /usr/src; make buildkernel KERNEL=HAYDN; make > installkernel KERNEL=HAYDN > I build a kernel this way and several others afterwards. I have tried the flags 0x10, 0x20 and 0x30 for Port Com1 in the kernel config file, but nothing changed. From the moment the kernel starts to boot, i get no messages on the serial console To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 11:32: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whiterose.net (whiterose.net [199.245.105.145]) by hub.freebsd.org (Postfix) with ESMTP id 2AD4A37B401; Sun, 14 Jan 2001 11:31:43 -0800 (PST) Received: from ccrider2k (adsl-141-151-201-154.cptl.adsl.bellatlantic.net [141.151.201.154]) by whiterose.net (8.10.1/8.10.1) with SMTP id f0EJVYt30261; Sun, 14 Jan 2001 14:31:35 -0500 From: "Robert Myers" To: "'Morten Seeberg'" , "'Bob Purdon'" Cc: , Subject: RE: Compaq RAID? Date: Sun, 14 Jan 2001 12:55:00 -0500 Message-ID: <000001c07e60$49057af0$0201a8c0@ccrider2k> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <002f01c07bfa$e6e917d0$c8280c0a@sos> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did you try booting a smartstart CD and configuring from there? Robert Myers Systems Administrator http://whiterose.net (717)439-1478 > > > FYI for the mailinglists > > I haven´t had time or the oppotunity to test the new models, > but I do know > that Compaq will not support newer controllers for FreeBSD > (or Linux at the > moment). They talked about supporting their controllers in > other kinds of > hardware than Compaq, but that never happened (and probably > never will now), > so you actually need an NT partition on your server or a > Compaq server (and > the use the SmartStart CD) :( > > ----- Original Message ----- > From: "Bob Purdon" > To: > Sent: Thursday, January 11, 2001 11:59 AM > Subject: Compaq RAID? > > > > > > Hi, > > > > Been checking out your IDA RAID web pages and was hoping > you might have > > some useful information... > > > > I have a Compaq SMART Array 3200 controller (the dual > channel unit), but > > can't find any software to configure the actual arrays. > The software your > > site links to (the Softpaq - the one that extracts a copy of Win > > 3.11 and runs in that) doesn't detect the card. > > > > The BIOS detects the card, and it runs it's power up > diagnostics fine - > > it's just the Compaq software that can't find it. > > > > I've tried downloading their newer ADU utility, but it only > runs on NT or > > Win-2000, and installing either of those just so I can > configure an array > > to install BSD on seems just a little drastic. > > > > Do you have any ideas I could try? > > > > Cheers, > > > > Bob. > > > > > > > > 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 Jan 14 11:43: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from priv-edtnes11-hme0.telusplanet.net (fepout3.telus.net [199.185.220.238]) by hub.freebsd.org (Postfix) with ESMTP id C9C7537B400; Sun, 14 Jan 2001 11:42:43 -0800 (PST) Received: from Q ([209.53.59.203]) by priv-edtnes11-hme0.telusplanet.net (InterMail vM.4.01.03.13 201-229-121-113) with SMTP id <20010114194243.MSGZ667.priv-edtnes11-hme0.telusplanet.net@Q>; Sun, 14 Jan 2001 12:42:43 -0700 Message-ID: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net> From: "Peter" To: Cc: Subject: sshd not working after upgrade to 4.2S from 4.1R HELP Date: Sun, 14 Jan 2001 11:42:03 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0012_01C07E1F.03A67360" 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 X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0012_01C07E1F.03A67360 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello=20 I have a little problems after I cvsup my src and post. Then build = and install a new kernel. BTW im was on 4.1R now 4.2S. Everything run = great now but i can't seem to login ssh. =20 this is the error msg i got under /var/log/messages Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service Jan 14 11:28:23 crazie sshd[209]: fatal: PAM session setup failed[6]: = Permission denied Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service everytime i tried to login=20 the password prompt up and if i enter the wrong password it will ask me = again=20 but when i enter the right pass work it logged me out. =20 Cuz someone suggestion or point me to how to fix it. I tried = reinstalling it. but still given me the same problems. Thank you=20 Peter ------=_NextPart_000_0012_01C07E1F.03A67360 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello
 
    I have a little = problems after I=20 cvsup my src and post.  Then build and install a new kernel.  = BTW im=20 was on 4.1R now 4.2S.   Everything run great now but i can't = seem to=20 login ssh. 
 
this is the error msg i got under=20 /var/log/messages
 
Jan 14 11:28:23 crazie sshd[209]: no = modules loaded=20 for `sshd' service
Jan 14 11:28:23 crazie sshd[209]: fatal: PAM = session setup=20 failed[6]: Permission denied
Jan 14 11:28:23 crazie sshd[209]: no = modules=20 loaded for `sshd' service
everytime i tried to login =
 
the password prompt up and if i enter = the wrong=20 password it will ask me again
but when i enter the right pass work it = logged me=20 out. 
 
Cuz someone suggestion or point me to = how to fix=20 it.   I tried reinstalling it. but still given me the same=20 problems.  Thank you
 
Peter
------=_NextPart_000_0012_01C07E1F.03A67360-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 11:43:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from libero.sunshine.ale (ppp-182-113.33-151.iol.it [151.33.113.182]) by hub.freebsd.org (Postfix) with ESMTP id 65D5837B401 for ; Sun, 14 Jan 2001 11:43:04 -0800 (PST) Received: by libero.sunshine.ale (Postfix, from userid 1001) id DF1195EC6; Sun, 14 Jan 2001 20:43:25 +0100 (CET) Date: Sun, 14 Jan 2001 20:43:25 +0100 From: Alessandro de Manzano To: Roman Shterenzon Cc: "stable@freebsd.org" Subject: Re: PR #24059 - USB still broken in SMP ! Message-ID: <20010114204325.A1000@libero.sunshine.ale> Reply-To: Alessandro de Manzano References: <20010112171919.B67D1D60F9@viger.playstos.com> <14943.16761.965760.182463@hip186.ch.intel.com> <20010112213610.E615@libero.sunshine.ale> <979434079.3a60fa5fc6469@webmail.harmonic.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <979434079.3a60fa5fc6469@webmail.harmonic.co.il>; from roman@harmonic.co.il on Sun, Jan 14, 2001 at 03:01:19AM +0200 X-Operating-System: FreeBSD 4.2-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 14, 2001 at 03:01:19AM +0200, Roman Shterenzon wrote: > Check if your motherboard vendor has some BIOS updates that are relevant. I checked few days ago and there were not upgrades available. The very strange thing is that with a non-SMP kernel my USB works fine! So I guess it's something related to the SMP-ness of kernels :-) -- bye! Ale aledema@iol.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 11:49:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from menzor.org (menzor.org [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id 49F4337B402; Sun, 14 Jan 2001 11:49:08 -0800 (PST) Received: from sos (userhost.mdes.dk [130.228.127.200]) by menzor.org (8.8.8/8.8.8) with SMTP id VAA24784; Sun, 14 Jan 2001 21:01:12 +0100 (CET) (envelope-from morten@seeberg.dk) Message-ID: <02cf01c07e63$488dab80$deff58c1@sos> From: "Morten Seeberg" To: "Robert Myers" , "'Bob Purdon'" Cc: , References: <000001c07e60$49057af0$0201a8c0@ccrider2k> Subject: Re: Compaq RAID? Date: Sun, 14 Jan 2001 20:50:41 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I dont have a Compaq system, I use my controllers in regular Clone systems (but my controllers are old enough to be supported by the SP described on my webpage). But i have configured 50 controllers via the SmartStart CD in Compaq systems without any problems. The software started on the SmartStart CD is the same as the software you install in Windows NT. ----- Original Message ----- From: "Robert Myers" To: "'Morten Seeberg'" ; "'Bob Purdon'" Cc: ; Sent: Sunday, January 14, 2001 6:55 PM Subject: RE: Compaq RAID? > Did you try booting a smartstart CD and configuring from there? > > Robert Myers > Systems Administrator > http://whiterose.net > (717)439-1478 > > > > > > > > FYI for the mailinglists > > > > I haven´t had time or the oppotunity to test the new models, > > but I do know > > that Compaq will not support newer controllers for FreeBSD > > (or Linux at the > > moment). They talked about supporting their controllers in > > other kinds of > > hardware than Compaq, but that never happened (and probably > > never will now), > > so you actually need an NT partition on your server or a > > Compaq server (and > > the use the SmartStart CD) :( > > > > ----- Original Message ----- > > From: "Bob Purdon" > > To: > > Sent: Thursday, January 11, 2001 11:59 AM > > Subject: Compaq RAID? > > > > > > > > > > Hi, > > > > > > Been checking out your IDA RAID web pages and was hoping > > you might have > > > some useful information... > > > > > > I have a Compaq SMART Array 3200 controller (the dual > > channel unit), but > > > can't find any software to configure the actual arrays. > > The software your > > > site links to (the Softpaq - the one that extracts a copy of Win > > > 3.11 and runs in that) doesn't detect the card. > > > > > > The BIOS detects the card, and it runs it's power up > > diagnostics fine - > > > it's just the Compaq software that can't find it. > > > > > > I've tried downloading their newer ADU utility, but it only > > runs on NT or > > > Win-2000, and installing either of those just so I can > > configure an array > > > to install BSD on seems just a little drastic. > > > > > > Do you have any ideas I could try? > > > > > > Cheers, > > > > > > Bob. > > > > > > > > > > > > > > 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 Jan 14 11:51:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.cb21.co.jp (ns1.cb21.co.jp [203.140.149.254]) by hub.freebsd.org (Postfix) with SMTP id D2AA337B401 for ; Sun, 14 Jan 2001 11:51:10 -0800 (PST) Received: (qmail 49104 invoked from network); 15 Jan 2001 04:50:59 +0900 Received: from localhost.cb21.co.jp (HELO localhost) (127.0.0.1) by localhost.cb21.co.jp with SMTP; 15 Jan 2001 04:50:59 +0900 Date: Mon, 15 Jan 2001 04:50:59 +0900 (JST) From: Sys Admin To: freebsd-stable@freebsd.org Subject: New features in 4.3-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, We currently have 4.1 machines and are planning to upgrade soon mainly to get improved AMI RAID support. Is it worthwhile to wait for 4.3-R ? Any pointers to the new features coming in 4.3R (particularly RAID support) ? TIA. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 11:52:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 3B4E437B402; Sun, 14 Jan 2001 11:51:56 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id 53E891360C; Sun, 14 Jan 2001 14:51:55 -0500 (EST) Date: Sun, 14 Jan 2001 14:51:55 -0500 From: Chris Faulhaber To: Peter Cc: questions@freebsd.org, stable@freebsd.org Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP Message-ID: <20010114145155.A46882@peitho.fxp.org> References: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net>; from peter@a3.ca on Sun, Jan 14, 2001 at 11:42:03AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 14, 2001 at 11:42:03AM -0800, Peter wrote: > Hello > > I have a little problems after I cvsup my src and post. Then build and install a new kernel. BTW im was on 4.1R now 4.2S. Everything run great now but i can't seem to login ssh. > > this is the error msg i got under /var/log/messages > > Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service > Jan 14 11:28:23 crazie sshd[209]: fatal: PAM session setup failed[6]: Permission denied > Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service > > everytime i tried to login > Consider running mergemaster to update your configuration files (esp. /etc/pam.conf). -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 12: 9:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id B4EF737B698 for ; Sun, 14 Jan 2001 12:09:13 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0EK9Ah51097; Sun, 14 Jan 2001 12:09:10 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Jan 2001 12:09:10 -0800 (PST) From: Matt Dillon Message-Id: <200101142009.f0EK9Ah51097@earth.backplane.com> To: Bruce Burden Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /swap too large? What?? References: <20010113002643.A33278@tigerfish2.my.domain> <200101131927.f0DJRSS34276@earth.backplane.com> <20010113150956.B37497@tigerfish2.my.domain> <200101132205.f0DM5pJ35749@earth.backplane.com> <20010114132520.A79824@tigerfish2.my.domain> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> : I have dropped things back to NSWAPDEV=3, and see if that :> : does anything. :> :> That will fix it. :> : Indeed it did. While have rarely seen swapping take place : under normal situations (GIMP, as I mentioned, will swap), it : was a bit nerve-wracking to see free memory dropping somewhat : low w/out any swap space. On the other hand, I did note that : garbage collection is much more aggressive when you don't have : any swap space! : : Bruce Both -current and 4.x have the low-memory deadlock patches, which also cleanup the pageout daemon to the point where it is very close to perfect. Another thing that helps for systems with no swap is to set the 'H' malloc.conf flag (e.g. ln -s H /etc/malloc.conf). This allows the system to more aggressively revert dirty pages free()'d by malloc back to demand-zero pages. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 12:47:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 10BC037B699 for ; Sun, 14 Jan 2001 12:46:52 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id D9C45177EF1 for ; Sun, 14 Jan 2001 14:46:49 -0600 (CST) Message-ID: <00ad01c07e6b$1b80cc00$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "stable" Subject: SCSI Tape Drive support Date: Sun, 14 Jan 2001 14:46:45 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know if FreeBSD supports VXA 33/66gig tape drives by Ecrix? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 13:13:27 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 79B2137B6A3 for ; Sun, 14 Jan 2001 13:13:06 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0ELD5A30254 for stable@freebsd.org; Sun, 14 Jan 2001 16:13:05 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0ELCxd30246 for ; Sun, 14 Jan 2001 16:13:00 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010114161134.0336a730@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sun, 14 Jan 2001 16:12:59 -0500 To: stable@freebsd.org From: Mike Tancsa Subject: broken pipes on make world 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 X-Loop: FreeBSD.ORG Does anyone else get this ? -------------------------------------------------------------- >>> Rebuilding man page indices -------------------------------------------------------------- cd /usr/src/share/man; make makedb makewhatis /usr/share/man gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe . . gzcat: stdout: Broken pipe makewhatis /usr/share/perl/man gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe gzcat: stdout: Broken pipe rm -rf /tmp/install.80458 -------------------------------------------------------------- >>> elf make world completed on Sun Jan 14 14:52:59 EST 2001 (started Sun Jan 14 13:49:01 EST 2001) -------------------------------------------------------------- -------------------------------------------------------------------- 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 Sun Jan 14 13:58:42 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 CC60B37B400 for ; Sun, 14 Jan 2001 13:58:24 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id WAA24114; Sun, 14 Jan 2001 22:58:20 +0100 (CET) (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: Mike Tancsa Cc: stable@FreeBSD.ORG Subject: Re: broken pipes on make world References: <4.2.2.20010114161134.0336a730@marble.sentex.net> From: Dag-Erling Smorgrav Date: 14 Jan 2001 22:58:20 +0100 In-Reply-To: Mike Tancsa's message of "Sun, 14 Jan 2001 16:12:59 -0500" Message-ID: Lines: 8 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Tancsa writes: > Does anyone else get this ? Lemme guess - full disk? 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 Jan 14 14:13: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id 6E0DB37B401; Sun, 14 Jan 2001 14:12:42 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sun, 14 Jan 2001 14:10:57 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.1/8.11.0) id f0EMCfr39379; Sun, 14 Jan 2001 14:12:41 -0800 (PST) (envelope-from cjc) Date: Sun, 14 Jan 2001 14:12:40 -0800 From: "Crist J. Clark" To: Odhiambo Washington Cc: FBSD-STABLE , FBSD-Q Subject: Re: Strange device probe behavior Message-ID: <20010114141240.O97980@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <20010114122845.A400@poeza.iconnect.co.ke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010114122845.A400@poeza.iconnect.co.ke>; from wash@iconnect.co.ke on Sun, Jan 14, 2001 at 12:28:45PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 14, 2001 at 12:28:45PM +0300, Odhiambo Washington wrote: [snip] > atapci0: port 0x1860-0x186f at device 4.1 on pci0 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > This is where 15 or so seconds lapse before the probe continues!! That's just your ATA (IDE) controller. > ata0: at 0x1f0 irq 14 on atapci0 > acd0: CDROM at ata0-master using WDMA2 -- 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 Jan 14 14:22:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 4A5AE37B401 for ; Sun, 14 Jan 2001 14:22:09 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id B0D10177E9F; Sun, 14 Jan 2001 16:22:12 -0600 (CST) Message-ID: <018601c07e78$6e640d80$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Fred Condo" Cc: References: <150360.3188470738@[192.168.1.5]> Subject: Re: SCSI Tape Drive support Date: Sun, 14 Jan 2001 16:22:07 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sure they would love to claim so, just wondering if anyone knows for sure that the drivers do exist in the source tree somewhere or has tested it. ----- Original Message ----- From: "Fred Condo" To: "David W. Chapman Jr." Sent: Sunday, January 14, 2001 4:18 PM Subject: Re: SCSI Tape Drive support > --On Sunday, January 14, 2001 2:46 PM -0600 "David W. Chapman Jr." > wrote: > > > Does anyone know if FreeBSD supports VXA 33/66gig tape drives by Ecrix? > > Ecrix so claims. > > -- > fred@condo.chico.ca.us Don't look at me: I voted for Nader. > ------------------------------> Listen to the phryd lyn at > http://live365.com/cgi-bin/directory.cgi?autostart=djphryd > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 14:33:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from level3.dynacom.net (level3.dynacom.net [206.107.213.213]) by hub.freebsd.org (Postfix) with SMTP id E851937B400 for ; Sun, 14 Jan 2001 14:33:03 -0800 (PST) Received: (qmail 8022 invoked by uid 0); 14 Jan 2001 22:32:57 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 14 Jan 2001 22:32:57 -0000 Message-ID: <3A622919.53B84AB3@urx.com> Date: Sun, 14 Jan 2001 14:32:57 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: Mike Tancsa , stable@FreeBSD.ORG Subject: Re: broken pipes on make world References: <4.2.2.20010114161134.0336a730@marble.sentex.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Mike Tancsa writes: > > Does anyone else get this ? > > Lemme guess - full disk? Nope, it also did it to me and my df is Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s2a 99183 38785 52464 43% / /dev/ad0s2f 988852 87 909657 0% /tmp /dev/ad1s3e 28860174 2402087 24149274 9% /usr /dev/ad0s2e 992239 5105 907755 1% /var procfs 4 4 0 100% /proc It was mods from the last 8 hours. I had one finish at 8am and it was ok. One that just finished was broken. Kent > > 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 -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 14:40: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id B98E137B400 for ; Sun, 14 Jan 2001 14:39:49 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id 0C1E61360C; Sun, 14 Jan 2001 17:39:47 -0500 (EST) Date: Sun, 14 Jan 2001 17:39:47 -0500 From: Chris Faulhaber To: Mike Tancsa Cc: stable@freebsd.org Subject: Re: broken pipes on make world Message-ID: <20010114173946.A11809@peitho.fxp.org> References: <4.2.2.20010114161134.0336a730@marble.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4.2.2.20010114161134.0336a730@marble.sentex.net>; from mike@sentex.net on Sun, Jan 14, 2001 at 04:12:59PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 14, 2001 at 04:12:59PM -0500, Mike Tancsa wrote: > > Does anyone else get this ? > > -------------------------------------------------------------- > >>> Rebuilding man page indices > -------------------------------------------------------------- > cd /usr/src/share/man; make makedb > makewhatis /usr/share/man > gzcat: stdout: Broken pipe > gzcat: stdout: Broken pipe I am also seeing this using makewhatis (during installworld or otherwise) when logged in remotely via ssh using sudo or su. I do not see it if I login locally or over telnet as root or a normal user. -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 14:40:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yez.hyperreal.org (3ff8f8da.dsl.flashcom.net [63.248.248.218]) by hub.freebsd.org (Postfix) with SMTP id 276C037B401 for ; Sun, 14 Jan 2001 14:39:58 -0800 (PST) Received: (qmail 85840 invoked by uid 1000); 14 Jan 2001 22:40:08 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Jan 2001 22:40:08 -0000 Date: Sun, 14 Jan 2001 14:40:08 -0800 (PST) From: Brian Behlendorf X-Sender: brian@localhost To: Matt Dillon Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /swap too large? What?? In-Reply-To: <200101142009.f0EK9Ah51097@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 14 Jan 2001, Matt Dillon wrote: > Both -current and 4.x have the low-memory deadlock patches, which > also cleanup the pageout daemon to the point where it is very close > to perfect. What's the status of those getting committed? Waiting for feedback? Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 14:52: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from level3.dynacom.net (level3.dynacom.net [206.107.213.213]) by hub.freebsd.org (Postfix) with SMTP id 88B1A37B402 for ; Sun, 14 Jan 2001 14:51:49 -0800 (PST) Received: (qmail 10397 invoked by uid 0); 14 Jan 2001 22:51:48 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 14 Jan 2001 22:51:48 -0000 Message-ID: <3A622D84.36117276@urx.com> Date: Sun, 14 Jan 2001 14:51:48 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Chris Faulhaber Cc: Mike Tancsa , stable@freebsd.org Subject: Re: broken pipes on make world References: <4.2.2.20010114161134.0336a730@marble.sentex.net> <20010114173946.A11809@peitho.fxp.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Faulhaber wrote: > > On Sun, Jan 14, 2001 at 04:12:59PM -0500, Mike Tancsa wrote: > > > > Does anyone else get this ? > > > > -------------------------------------------------------------- > > >>> Rebuilding man page indices > > -------------------------------------------------------------- > > cd /usr/src/share/man; make makedb > > makewhatis /usr/share/man > > gzcat: stdout: Broken pipe > > gzcat: stdout: Broken pipe > > I am also seeing this using makewhatis (during installworld or > otherwise) when logged in remotely via ssh using sudo or su. > I do not see it if I login locally or over telnet as root or > a normal user. Both of my builds were done using ssh sessions with "su - root"'s to do the builds. The one at 8am PST worked and the one started at 1330 PST failed. When I walked down to the console and did an installworld as root, the makewhatis didn't have any problems. Kent > > -- > Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org > -------------------------------------------------------- > FreeBSD: The Power To Serve - http://www.FreeBSD.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 15: 2:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id 10D4737B400 for ; Sun, 14 Jan 2001 15:02:01 -0800 (PST) Received: from ufl.edu (neti.eng.ufl.edu [128.227.235.15]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id SAA243430; Sun, 14 Jan 2001 18:01:59 -0500 Message-ID: <3A623025.1232B44C@ufl.edu> Date: Sun, 14 Jan 2001 18:03:01 -0500 From: Bob Johnson X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en, eo MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rats. Copied this to the wrong list (questions). Here it is, for the record. - Bob -------- Original Message -------- Subject: sshd not working after upgrade to 4.2S from 4.1R HELP Date: Sun, 14 Jan 2001 17:57:33 -0500 From: Bob Johnson To: peter@a3.ca > > > Date: Sun, 14 Jan 2001 11:42:03 -0800 > From: "Peter" > Subject: sshd not working after upgrade to 4.2S from 4.1R HELP > > This is a multi-part message in MIME format. > > - ------=_NextPart_000_0012_01C07E1F.03A67360 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > Hello=20 > > I have a little problems after I cvsup my src and post. Then build = > and install a new kernel. BTW im was on 4.1R now 4.2S. Everything run = > great now but i can't seem to login ssh. =20 > > this is the error msg i got under /var/log/messages > > Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service > Jan 14 11:28:23 crazie sshd[209]: fatal: PAM session setup failed[6]: = > Permission denied > Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service > I had a similar problem once caused by a change in /etc/pam.conf, but I don't think it has changed between 4.1R and 4.2S. In my case, I needed the "other" section at the end of the file. I would look at /etc/pam.conf and /etc/ssh/sshd_config to see if anything changed that might explain this. I think the 4.2S versions will be in /usr/src/etc and /usr/src/crypto/openssh: compare them to your backup copies of the old ones to see what changed. You might also make sure the files /etc/nologin and /var/run/nologin do not exist: if they do you will be logged out immediately after you log in, which you describe below (but that doesn't explain the PAM error messages). - Bob > everytime i tried to login=20 > > the password prompt up and if i enter the wrong password it will ask me = > again=20 > but when i enter the right pass work it logged me out. =20 > > Cuz someone suggestion or point me to how to fix it. I tried = > reinstalling it. but still given me the same problems. Thank you=20 > > Peter > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 15:56:44 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 5428437B400 for ; Sun, 14 Jan 2001 15:56:24 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0ENuNn30435; Sun, 14 Jan 2001 18:56:23 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0ENuHd30427; Sun, 14 Jan 2001 18:56:18 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010114185423.01dd8858@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sun, 14 Jan 2001 18:56:17 -0500 To: Dag-Erling Smorgrav From: Mike Tancsa Subject: Re: broken pipes on make world Cc: stable@freebsd.org In-Reply-To: References: <4.2.2.20010114161134.0336a730@marble.sentex.net> 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 X-Loop: FreeBSD.ORG At 10:58 PM 1/14/2001 +0100, Dag-Erling Smorgrav wrote: >Mike Tancsa writes: > > Does anyone else get this ? > >Lemme guess - full disk? No, I have plenty of disk space on all 4 machines. I didnt see this on builds from Friday. Only today. ---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 Sun Jan 14 16: 0:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 4E41637B401 for ; Sun, 14 Jan 2001 16:00:30 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0ENxwK64983; Sun, 14 Jan 2001 15:59:58 -0800 (PST) (envelope-from dillon) Date: Sun, 14 Jan 2001 15:59:58 -0800 (PST) From: Matt Dillon Message-Id: <200101142359.f0ENxwK64983@earth.backplane.com> To: Brian Behlendorf Cc: freebsd-stable@FreeBSD.ORG Subject: Re: /swap too large? What?? References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Sun, 14 Jan 2001, Matt Dillon wrote: :> Both -current and 4.x have the low-memory deadlock patches, which :> also cleanup the pageout daemon to the point where it is very close :> to perfect. : :What's the status of those getting committed? Waiting for feedback? : : Brian They were committed after christmas, and a minor update was comitted a week or two ago. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 16: 4:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 8EC2E37B400 for ; Sun, 14 Jan 2001 16:04:00 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id QAA14403; Sun, 14 Jan 2001 16:05:03 -0800 Date: Sun, 14 Jan 2001 16:05:03 -0800 From: Kris Kennaway To: Peter Cc: stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP Message-ID: <20010114160503.B14278@citusc.usc.edu> References: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="LyciRD1jyfeSSjG0" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net>; from peter@a3.ca on Sun, Jan 14, 2001 at 11:42:03AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --LyciRD1jyfeSSjG0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 14, 2001 at 11:42:03AM -0800, Peter wrote: > this is the error msg i got under /var/log/messages >=20 > Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service The correct upgrade procedure involves running mergemaster after installworld and installkernel. This would have avoided your problem - please see the handbook for a full description of the upgrade procedure. Kris --LyciRD1jyfeSSjG0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6Yj6vWry0BWjoQKURAugFAJ9i5+3fQP5vg+hORfxJJmS3mFtcawCgqoZg Fl6/uM6Ovc2Pwewi4lrwpTs= =pjP4 -----END PGP SIGNATURE----- --LyciRD1jyfeSSjG0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 16: 5:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 7A85E37B401 for ; Sun, 14 Jan 2001 16:04:55 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id QAA14421; Sun, 14 Jan 2001 16:06:12 -0800 Date: Sun, 14 Jan 2001 16:06:12 -0800 From: Kris Kennaway To: Sys Admin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: New features in 4.3-RELEASE Message-ID: <20010114160612.C14278@citusc.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="jy6Sn24JjFx/iggw" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from admin@cb21.co.jp on Mon, Jan 15, 2001 at 04:50:59AM +0900 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --jy6Sn24JjFx/iggw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 15, 2001 at 04:50:59AM +0900, Sys Admin wrote: >=20 > Hello, >=20 > We currently have 4.1 machines and are planning to upgrade soon mainly to > get improved AMI RAID support. Is it worthwhile to wait for 4.3-R ?=20 >=20 > Any pointers to the new features coming in 4.3R (particularly RAID > support) ? See the release notes in /usr/src/release/texts/{i386,alpha}/RELNOTES.TXT in 4.2-STABLE for features added since 4.2-R Kris --jy6Sn24JjFx/iggw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6Yj7zWry0BWjoQKURAn+OAKCwu9PIq/+VNbh8wx6icPMr2obERQCdEfw5 Kuqw7WACHgwJFXhkwkGect4= =Nf1M -----END PGP SIGNATURE----- --jy6Sn24JjFx/iggw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 17:19:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 241A937B400; Sun, 14 Jan 2001 17:19:00 -0800 (PST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:H13Tb0aKUcX1kBRXnMA99AMoiWQ7y3Us@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.11.0/3.7Wpl2) with ESMTP id f0F1IqM00959; Mon, 15 Jan 2001 10:18:52 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:+reANrE8Ka67rctX4Sfj0gOgYNmEJS/5@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id KAA00198; Mon, 15 Jan 2001 10:26:37 +0900 (JST) Message-Id: <200101150126.KAA00198@zodiac.mech.utsunomiya-u.ac.jp> To: Stephen Montgomery-Smith Cc: freebsd-stable@FreeBSD.ORG, freebsd-mobile@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: disable mousepad taps on Dell Inspiron In-reply-to: Your message of "Fri, 12 Jan 2001 21:50:40 CST." <3A5FD090.E035557F@math.missouri.edu> References: <3A5FD090.E035557F@math.missouri.edu> Date: Mon, 15 Jan 2001 10:26:35 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have submitted another PR describing how to do this: > >http://www.freebsd.org/cgi/query-pr.cgi?pr=24299 > >I now know quite a few people who would like something like this. >The old PR I submitted regarding this is now out of date. Could >someone please commit this (and the required co-PR: >http://www.freebsd.org/cgi/query-pr.cgi?pr=20352 ) >or something like this? > >Thanks, Stephen Hi, We exchanged mails quite a while ago and discussed about your proposed patch. I am sorry that I haven't written to you since then. The reason why I didn't commit your patch straight away at that time wasn't that I saw problems in your patch, but rather that the psm driver has gotten so bloat over the years and now have full of various model-specific code in it. It's getting more and more difficult to maintain. In addition, nowadays there are so many arcane PS/2 mice which require special attention by the driver on the market. We need to add support for those mice as well. Because of that, I decided to reorganize the psm driver a bit. I will split the model-specific code from the main body of the driver, and create a set of sub-drivers each of which will support a specific PS/2 mouse model. I promise that the TouchPad support will be one of the first sub-drivers to be added. I am almost there and commit the new code to the -CURRENT tree in a couple of weeks. IMHO, the PS/2 mouse is a dying beast, in that the USB mouse is the way to go. But, for the time being (well, a couple of years? three year?), we need to keep the psm driver in good shape. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 17:24:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2a.ispchannel.com (smtp.ispchannel.com [24.142.63.7]) by hub.freebsd.org (Postfix) with ESMTP id 007E637B404; Sun, 14 Jan 2001 17:23:53 -0800 (PST) Received: from cm-206-31-81-96.gulfbreeze.mediacom.ispchannel.com ([206.31.81.96]) by smtp2a.ispchannel.com (InterMail vK.4.02.00.00 201-232-116 license 7d3764cdaca754bf8ae20adf0db2aa60) with ESMTP id <20010115012707.NTGO382.smtp2a@cm-206-31-81-96.gulfbreeze.mediacom.ispchannel.com>; Sun, 14 Jan 2001 17:27:07 -0800 Date: Sun, 14 Jan 2001 19:23:59 -0600 (CST) From: Steve X-Sender: vandena@testbed.com To: Peter Cc: questions@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP In-Reply-To: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Related issue...I had 4.2R running (although slowly). Added a hard drive, did a complete re-install, and ssh would not run. Sshd was already running but tried to bind to incorrect addresses. For S&G's, I installed OpenSSH and everything since then has been working just fine. May want to look at installing OpenSSH if that app will work for you. Just a thought... ____ _ / ___|| |_ _____ _____ \___ \| __/ _ \ \ / / _ \ ___) | || __/\ V / __/ |____/ \__\___| \_/ \___| ========================= vandena@ispchannel.com On Sun, 14 Jan 2001, Peter wrote: > Hello > > I have a little problems after I cvsup my src and post. Then build and install a new kernel. BTW im was on 4.1R now 4.2S. Everything run great now but i can't seem to login ssh. > > this is the error msg i got under /var/log/messages > > Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service > Jan 14 11:28:23 crazie sshd[209]: fatal: PAM session setup failed[6]: Permission denied > Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service > > everytime i tried to login > > the password prompt up and if i enter the wrong password it will ask me again > but when i enter the right pass work it logged me out. > > Cuz someone suggestion or point me to how to fix it. I tried reinstalling it. but still given me the same problems. Thank you > > Peter > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 17:36:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from home.dwave.net (home.dwave.net [207.0.68.7]) by hub.freebsd.org (Postfix) with ESMTP id E673037B401 for ; Sun, 14 Jan 2001 17:36:33 -0800 (PST) Received: from home ([206.176.218.3]) by home.dwave.net (8.9.3/8.9.3) with SMTP id TAA21992 for ; Sun, 14 Jan 2001 19:33:39 -0600 Message-ID: <000801c07e95$011c1b60$03dab0ce@Home> From: "Jon" To: Subject: please put me on your mailing list. THank you Date: Sun, 14 Jan 2001 19:46:39 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C07E62.B5F4FBC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C07E62.B5F4FBC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0005_01C07E62.B5F4FBC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0005_01C07E62.B5F4FBC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 18:42: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from level3.dynacom.net (level3.dynacom.net [206.107.213.213]) by hub.freebsd.org (Postfix) with SMTP id 4E58137B400 for ; Sun, 14 Jan 2001 18:41:50 -0800 (PST) Received: (qmail 6819 invoked by uid 0); 15 Jan 2001 02:41:49 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 15 Jan 2001 02:41:49 -0000 Message-ID: <3A62636D.4DB982AD@urx.com> Date: Sun, 14 Jan 2001 18:41:49 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Tancsa Cc: Dag-Erling Smorgrav , stable@freebsd.org Subject: Re: broken pipes on make world References: <4.2.2.20010114161134.0336a730@marble.sentex.net> <4.2.2.20010114185423.01dd8858@marble.sentex.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Tancsa wrote: > > At 10:58 PM 1/14/2001 +0100, Dag-Erling Smorgrav wrote: > >Mike Tancsa writes: > > > Does anyone else get this ? > > > >Lemme guess - full disk? > > No, I have plenty of disk space on all 4 machines. I didnt see this on > builds from Friday. Only today. Green made a number of changes to OpenSSH on Saturday. I only have problems if I log in and do a make world using ssh with those changes. What is interesting is to use both telnet and ssh to do the following. The output from the ssh session is seriously truncated when it is doing some of the traverses. cd /usr/src/share/man makewhatis -v /usr/share/man It didn't have problems with man9 but there are 5 broken pipes traversing man8. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jan 14 21:26:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 265AB37B400 for ; Sun, 14 Jan 2001 21:26:36 -0800 (PST) Received: from randy by rip.psg.com with local (Exim 3.16 #1) id 14I2A7-000DOj-00 for freebsd-stable@freebsd.org; Sun, 14 Jan 2001 21:26:35 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Stable Subject: odd mouse button behavior Message-Id: Date: Sun, 14 Jan 2001 21:26:35 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG just cvsupped to 4.2-stable as of today xfree 4.0.2 and all of a sudden my mouse does not react to a button until the mosue travels. this is most strange. the accelleration also went to max. but i was able to slow that with xset mouse 4 running moused on a ps/2 mouse. dmesg below. randy ---- Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Sat Jan 13 11:03:22 PST 2001 root@rip.psg.com:/usr/obj/usr/src/sys/RIP Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 800034279 Hz CPU: Pentium III/Pentium III Xeon/Celeron (800.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 536850432 (524268K bytes) avail memory = 519380992 (507208K bytes) Preloaded elf kernel "kernel" at 0xc0334000. ccd0-5: Concatenated disk drivers Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 fxp0: port 0xd800-0xd83f mem 0xfc000000-0xfc0fffff,0xfc800000-0xfc800fff irq 5 at device 2.0 on pci0 fxp0: Ethernet address 00:e0:18:02:6e:c9 bktr0: mem 0xfe000000-0xfe000fff irq 11 at device 4.0 on pci0 iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus0: on bti2c0 bktr0: Hauppauge Model 61111 A M bktr0: Detected a MSP3430G-A1 at 0x80 bktr0: Hauppauge WinCast/TV, Philips NTSC tuner, msp3400c stereo. pci0: (vendor=0x109e, dev=0x0878) at 4.1 irq 11 pcm0: port 0xd400-0xd43f irq 10 at device 5.0 on pci0 pci0: at 7.0 isab0: at device 15.0 on pci0 isa0: on isab0 pci0: at 15.1 pci0: at 15.2 irq 9 pcib1: on motherboard pci1: on pcib1 sym0: <896> port 0xb400-0xb4ff mem 0xf9000000-0xf9001fff,0xf9800000-0xf98003ff irq 9 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym1: <896> port 0xb000-0xb0ff mem 0xf8000000-0xf8001fff,0xf8800000-0xf88003ff irq 9 at device 5.1 on pci1 sym1: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A Waiting 5 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. Mounting root from ufs:/dev/da0a da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 1:34:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc2.il.home.com (ha2.rdc2.il.home.com [24.2.1.36]) by hub.freebsd.org (Postfix) with ESMTP id E8EFD37B401; Mon, 15 Jan 2001 01:34:32 -0800 (PST) Received: from marx.marvic.chum ([24.17.229.11]) by mail.rdc2.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010115093427.MBWO25219.mail.rdc2.il.home.com@marx.marvic.chum>; Mon, 15 Jan 2001 01:34:27 -0800 Received: (from vcardona@localhost) by marx.marvic.chum (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id DAA31775; Mon, 15 Jan 2001 03:34:59 -0600 Date: Mon, 15 Jan 2001 03:34:59 -0600 From: "Victor R. Cardona" To: freebsd-questions@freebsd.org Cc: freebsd-stable@freebsd.org Subject: 4.2-STABLE keeps locking up Message-ID: <20010115033459.A31750@home.com> Mail-Followup-To: freebsd-questions@freebsd.org, freebsd-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 X-Loop: FreeBSD.ORG Hi everyone, I am having a problem with my 4.2-STABLE box. A couple of days ago I noticed that it started locking up on me. I have not been able to find any error messages. The only thing I have noticed is that when I use ncftp, and the client is logging in to the remote server, then the box locks up. The FreeBSD box is acting as my firewall. Does anyone have any suggestions as to how I can diagnose what the problem is? I have already remade world to see if that would help. It did not. I am running IPFilter, Bind, DHCPd, and Apache on this box. Thanks, Victor Cardona -- GnuPG Key fingerprint = 62B1 7995 A830 432C 74E8 1337 EDDB E682 3C76 7404 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 1:44:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id ECDD637B400 for ; Mon, 15 Jan 2001 01:44:28 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id BAA20554; Mon, 15 Jan 2001 01:44:33 -0800 Date: Mon, 15 Jan 2001 01:44:33 -0800 From: Kris Kennaway To: Steve Cc: Peter , stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP Message-ID: <20010115014433.A20550@citusc.usc.edu> References: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from vandena@ispchannel.com on Sun, Jan 14, 2001 at 07:23:59PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 14, 2001 at 07:23:59PM -0600, Steve wrote: > Related issue...I had 4.2R running (although slowly). Added a hard drive, > did a complete re-install, and ssh would not run. Sshd was already > running but tried to bind to incorrect addresses. For S&G's, I installed > OpenSSH and everything since then has been working just fine. >=20 > May want to look at installing OpenSSH if that app will work for > you. Just a thought... Umm. 4.2-R _includes_ openssh. Kris --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6YsaBWry0BWjoQKURAoqZAKCyp7tfI2CK0UOfXasStq7nu8swzgCeIzBU POQpN+18QizBDCOHvNh1Zt8= =xXPU -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 2: 7:34 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 D248E37B400 for ; Mon, 15 Jan 2001 02:07:15 -0800 (PST) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by serenity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14I6Xi-0003ce-00 for freebsd-stable@freebsd.org; Mon, 15 Jan 2001 10:07:14 +0000 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f0FA7AA30094 for freebsd-stable@freebsd.org; Mon, 15 Jan 2001 10:07:10 GMT (envelope-from rasputin) Date: Mon, 15 Jan 2001 10:07:09 +0000 From: Rasputin To: freebsd-stable@freebsd.org Subject: Anyone else seeing this? Message-ID: <20010115100709.A30062@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CVSupped 4-X-STABLE on Saturday, build world and kernel and rebooted, and the new kernel couldn't see the IDE drive at all. Error message? Um, it was the 'trying to fall back to PIO one' that was all the rage a couple of months ago. (Yeah, I know. This was around 2.30 am, so I was too knackered to grab dmesg output.) Anyway, the old kernel boots fine, so I'm still up and running, but I wondered if anyone else had seen a problem. I'll leave it for a week or so then try again, if no joy I'll send a PR. Incidentally, would anyone know an easy way of finding out what code has changed in the ata drivers since Christmas - other than mailing Soren of course :) -- 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 Jan 15 2:34:36 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 D56D537B400 for ; Mon, 15 Jan 2001 02:34:18 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0FAYHR31883; Mon, 15 Jan 2001 05:34:17 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0FAYCd31875; Mon, 15 Jan 2001 05:34:13 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010115053326.01c64f00@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 15 Jan 2001 05:34:12 -0500 To: Rasputin , freebsd-stable@freebsd.org From: Mike Tancsa Subject: Re: Anyone else seeing this? In-Reply-To: <20010115100709.A30062@dogma.freebsd-uk.eu.org> 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 X-Loop: FreeBSD.ORG At 10:07 AM 1/15/2001 +0000, Rasputin wrote: >Incidentally, would anyone know an easy way of finding out >what code has changed in the ata drivers since Christmas - >other than mailing Soren of course :) http://www.freebsd.org/cgi/cvsweb.cgi/ will show you what has been committed. ---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 Mon Jan 15 3:29:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sina.com (unknown [202.106.187.156]) by hub.freebsd.org (Postfix) with SMTP id 7A68E37B699 for ; Mon, 15 Jan 2001 03:29:22 -0800 (PST) Received: (qmail 42886 invoked from network); 15 Jan 2001 11:23:50 -0000 Received: from unknown (HELO localhost) (202.105.12.29) by 202.106.187.156 with SMTP; 15 Jan 2001 11:23:50 -0000 X-Sender: hangersales@sina.com From: Trend Hanger To: stable@freebsd.org Date: Mon, 15 Jan 2001 19:28:15 +0800 Subject: We are exporting quality Hanger for cloth, pants Reply-To: hangersales@sina.com Organization: Trend Hanger Co. MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20010115112922.7A68E37B699@hub.freebsd.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sir or Madam, Happy New Year! Here we send all the best wish to you. Trend Hanger, as a professional hanger manufacturer in China specializes in producing and designing various kinds of non-slip coated and chrome-plated metal frame clothes hangers. The company has been in the business for almost 10 years now. With experienced staff and workers, we always provide our customers from all over the world with good service, excellent quality and competitively-priced products. Today, people care a lot about environmental protection, and more and more people would choose to use low-waste materials, impressive and well-designed products. We are proud to say ours are among them. For this reason, during the past several years our selling records are quite well, and now the business is growing even faster than before--simply because our series of products are proven to be reliable and worthwhile in our consumers' eyes. Furthermore, we always observe a strict quality control system all throughout our production process. Each product must be carefully examined and tested in each stage so as to ensure excellent quality and nice packing order for our customers. If you are interested in our products, please do not hesitate to contact us. We are anxious to establish long-term, equal and mutual beneficial business relationship with you. Best wishes, Trend Hanger Manufacturer Contact Person: Mr Steve, Phoenix Sales Manager Zhen An Industrial Zone, Foshan City, Guangdong Province, China 528000 Tel: (86 757) 3982666 Fax: (86 757) 2282667 Email: brianced@21cn.com http://www.bosunnet.com/trendhanger/index/contacts.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 3:39:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xlr82xs.shacknet.nu (bri2-56k-134.tpgi.com.au [203.29.144.134]) by hub.freebsd.org (Postfix) with ESMTP id D8BB137B698 for ; Mon, 15 Jan 2001 03:38:39 -0800 (PST) Received: (from xlr82xs@localhost) by xlr82xs.shacknet.nu (8.11.1/8.11.1) id f0FBbmV82510; Mon, 15 Jan 2001 21:37:48 +1000 (EST) (envelope-from xlr82xs) Date: Mon, 15 Jan 2001 21:37:40 +1000 From: xlr82xs To: Trend Hanger Cc: freebsd-stable@freebsd.org Subject: Re: We are exporting quality Hanger for cloth, pants Message-ID: <20010115213740.C580@xlr82xs.shacknet.nu> References: <20010115112922.7A68E37B699@hub.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010115112922.7A68E37B699@hub.freebsd.org>; from hangersales@sina.com on Mon, Jan 15, 2001 at 07:28:15PM +0800 X-Operating-System: FreeBSD 4.2-STABLE on an i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable ummmmmm wtf is this doing on the freebsd-stable mailing list ? sorry for the implied language, and lack of written manner, but this came i= n and confused the hell out of me.. Trend Hanger [hangersales@sina.com] wrote: > Dear Sir or Madam, >=20 > Happy New Year! Here we send all the best wish to you. >=20 > Trend Hanger, as a professional hanger manufacturer in China specializes = in producing=20 > and designing various kinds of non-slip coated and chrome-plated metal fr= ame=20 > clothes hangers. The company has been in the business for almost 10 years= now.=20 > With experienced staff and workers, we always provide our customers from = all=20 > over the world with good service, excellent quality and competitively-pri= ced=20 > products. >=20 > Today, people care a lot about environmental protection, and more and mor= e people=20 > would choose to use low-waste materials, impressive and well-designed pro= ducts.=20 > We are proud to say ours are among them. For this reason, during the past= several=20 > years our selling records are quite well, and now the business is growing= even=20 > faster than before--simply because our series of products are proven to b= e reliable=20 > and worthwhile in our consumers' eyes.=20 >=20 > Furthermore, we always observe a strict quality control system all throug= hout=20 > our production process. Each product must be carefully examined and teste= d in=20 > each stage so as to ensure excellent quality and nice packing order for o= ur customers. >=20 > If you are interested in our products, please do not hesitate to contact = us.=20 > We are anxious to establish long-term, equal and mutual beneficial busin= ess=20 > relationship with you. >=20 > Best wishes, >=20 > Trend Hanger Manufacturer > Contact Person:=20 > Mr Steve, Phoenix > Sales Manager >=20 > Zhen An Industrial Zone,=20 > Foshan City, Guangdong Province, > China 528000 > Tel: (86 757) 3982666 > Fax: (86 757) 2282667 >=20 > Email: brianced@21cn.com > =20 > http://www.bosunnet.com/trendhanger/index/contacts.html >=20 >=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message >=20 --=20 Intel: where Quality is job number 0.9998782345! -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d- s:+ !a c++++ UB++++ P+ L- E W++ N o+ K++ w-- O- M-- V-=20 PS+++ PE Y++ PGP+++ t 5- X+ R* tv+ b+++ DI++ D+ G+ e* h! r z++=20 ------END GEEK CODE BLOCK------ --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjpi4QMACgkQcBR/Vvf1G2ahIQCeLQY+PM2YtIKgRnSBhrr2XRAi rKMAniO0QymWmTTbJ+L97Br6Jod7xyJr =FeI5 -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 3:48:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www3.infolink.com.br (www3.infolink.com.br [200.255.108.4]) by hub.freebsd.org (Postfix) with ESMTP id A1E2C37B698 for ; Mon, 15 Jan 2001 03:48:02 -0800 (PST) Received: from infolink.com.br (unverified [200.255.108.32]) by www3.infolink.com.br (Vircom SMTPRS 4.2.181) with SMTP id for ; Mon, 15 Jan 2001 09:48:00 -0200 From: "Antonio Carlos Pina" Reply-To: apina@infolink.com.br To: freebsd-stable@freebsd.org Date: Mon, 15 Jan 2001 09:48:00 est Subject: Dummynet stopping ? Message-id: <3a62e370.5b5.0@infolink.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Sorry if it was discussed before, but I couldn't find. Today, after 2 months working like a charm, one of my dummynet pipes stopped to pipe. The IP Address that it takes care was online and I could even ping it from within my bridge machine, through his own interface, but I couldn't ping or whatever from that ip address. I have something like this: ipfw pipe 3 64Kbit/s ipfw pipe 4 64Kbit/s ipfw add pipe ip from xxx.xxx.xxx.xxx to any via ep0 ipfw add pipe ip from any to xxx.xxx.xxx.xxx via ep0 (I'm sorry, these commands may be wrong since I can't access the bridge machine now. But it is working) As soon as I destroied the pipe and reapplied it, everything went fine again. I took a little look in ipfw pipe list, but I couldn't understand the data that was showed (drps I presume are drops, it was increasing while I was looking) Does anybody have seen this ? I'm running 4.2-STABLE and I've been thinking about cvsup the whole thing. I'm a bit concern because as I can ping the IP address from within the bridge machine, I can't even do a little script to test this situation and rebuild the pipes... :-/ Thank you for any help, Best Regards, Antonio Carlos Pina apina@infolink.com.br To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 3:53:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 6BCB837B404 for ; Mon, 15 Jan 2001 03:53:24 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 1AF3231BA; Mon, 15 Jan 2001 11:53:23 +0000 (GMT) Date: Mon, 15 Jan 2001 11:53:22 +0000 From: Josef Karthauser To: xlr82xs Cc: Trend Hanger , freebsd-stable@FreeBSD.org Subject: Re: We are exporting quality Hanger for cloth, pants Message-ID: <20010115115322.C3578@tao.org.uk> Mail-Followup-To: Josef Karthauser , xlr82xs , Trend Hanger , freebsd-stable@FreeBSD.org References: <20010115112922.7A68E37B699@hub.freebsd.org> <20010115213740.C580@xlr82xs.shacknet.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010115213740.C580@xlr82xs.shacknet.nu>; from xlr82xs@sdf.lonestar.org on Mon, Jan 15, 2001 at 09:37:40PM +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 09:37:40PM +1000, xlr82xs wrote: > > ummmmmm wtf is this doing on the freebsd-stable mailing list ? > > sorry for the implied language, and lack of written manner, but this came in and confused the hell out of me.. It's been widespread spammed across a whole chunk of the net - it's not just _ALL_ the freebsd lists it's gone to :). Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 4: 7:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 43B4D37B69E for ; Mon, 15 Jan 2001 04:07:21 -0800 (PST) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14I8Pw-0008bw-00 for freebsd-stable@freebsd.org; Mon, 15 Jan 2001 12:07:20 +0000 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f0FC7Kv31253 for freebsd-stable@freebsd.org; Mon, 15 Jan 2001 12:07:20 GMT (envelope-from rasputin) Date: Mon, 15 Jan 2001 12:07:20 +0000 From: Rasputin To: freebsd-stable@freebsd.org Subject: Re: Anyone else seeing this? Message-ID: <20010115120719.A31194@dogma.freebsd-uk.eu.org> References: <20010115100709.A30062@dogma.freebsd-uk.eu.org> <4.2.2.20010115053326.01c64f00@marble.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <4.2.2.20010115053326.01c64f00@marble.sentex.net>; from mike@sentex.net on Mon, Jan 15, 2001 at 05:34:12AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 05:34:12AM -0500, Mike Tancsa wrote: > At 10:07 AM 1/15/2001 +0000, Rasputin wrote: > >Incidentally, would anyone know an easy way of finding out > >what code has changed in the ata drivers since Christmas - > >other than mailing Soren of course :) > > http://www.freebsd.org/cgi/cvsweb.cgi/ > > will show you what has been committed. > > ---Mike Thanks Mike, think I spotted the change in question (this is an Aladdin mobo, and /sys/dev/ata/ata-all.c says: "Revision 1.50.2.15, Thu Jan 4 09:08:56 2001 UTC (11 days, 2 hours ago) by sos Branch: RELENG_4 Changes since 1.50.2.14: +5 -2 lines MFC: Proberly back down DMA modes on the Acer Aladdin." ) I take it from RELENG_4 that this is the STABLE tree, yes? -- 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 Jan 15 4:23:14 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 56C8937B69E for ; Mon, 15 Jan 2001 04:22:53 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0FCMq132081; Mon, 15 Jan 2001 07:22:52 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0FCMkd32073; Mon, 15 Jan 2001 07:22:47 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010115072149.01cc5bf0@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 15 Jan 2001 07:22:46 -0500 To: Rasputin , freebsd-stable@freebsd.org From: Mike Tancsa Subject: Re: Anyone else seeing this? In-Reply-To: <20010115120719.A31194@dogma.freebsd-uk.eu.org> References: <4.2.2.20010115053326.01c64f00@marble.sentex.net> <20010115100709.A30062@dogma.freebsd-uk.eu.org> <4.2.2.20010115053326.01c64f00@marble.sentex.net> 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 X-Loop: FreeBSD.ORG At 12:07 PM 1/15/2001 +0000, Rasputin wrote: >I take it from RELENG_4 that this is the STABLE tree, yes? Correct. ---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 Mon Jan 15 4:28: 5 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 07F0637B400 for ; Mon, 15 Jan 2001 04:27:47 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id EAA28854; Mon, 15 Jan 2001 04:26:30 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda28852; Mon Jan 15 04:26:24 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0FCQIK04497; Mon, 15 Jan 2001 04:26:18 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdds4494; Mon Jan 15 04:25:36 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f0FCPZF05945; Mon, 15 Jan 2001 04:25:35 -0800 (PST) Message-Id: <200101151225.f0FCPZF05945@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdfl5936; Mon Jan 15 04:25:28 2001 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.2-RELEASE X-Sender: cy To: kstewart@urx.com Cc: Mike Tancsa , Dag-Erling Smorgrav , stable@FreeBSD.ORG Subject: Re: broken pipes on make world In-reply-to: Your message of "Sun, 14 Jan 2001 18:41:49 PST." <3A62636D.4DB982AD@urx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Jan 2001 04:25:28 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A62636D.4DB982AD@urx.com>, Kent Stewart writes: > > > Mike Tancsa wrote: > > > > At 10:58 PM 1/14/2001 +0100, Dag-Erling Smorgrav wrote: > > >Mike Tancsa writes: > > > > Does anyone else get this ? > > > > > >Lemme guess - full disk? > > > > No, I have plenty of disk space on all 4 machines. I didnt see this on > > builds from Friday. Only today. > > Green made a number of changes to OpenSSH on Saturday. I only have > problems if I log in and do a make world using ssh with those changes. > What is interesting is to use both telnet and ssh to do the following. > The output from the ssh session is seriously truncated when it is > doing some of the traverses. > > cd /usr/src/share/man > makewhatis -v /usr/share/man > > It didn't have problems with man9 but there are 5 broken pipes > traversing man8. I you're using X, you can su -, then xterm -ls. This creates a session (from a process sense -- see Kirk's 4.4BSD book for details). If you're not using X, su - and temporarily create a /root/.rhosts file allowing localhost access to the machine then rlogin localhost. This will have the same effect as above. I personally haven't had the problems because I use krb5 rlogin and telnet directly to root, depending on whether the packets are NATed and VPNed or not, e.g krlogin -x -l root host or ktelnet -a -x -l root host. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 4:47:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 1F87437B402 for ; Mon, 15 Jan 2001 04:47:20 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id dorsaaaa for ; Mon, 15 Jan 2001 23:55:49 +1100 Message-ID: <3A62F16E.9A06E0C7@quake.com.au> Date: Mon, 15 Jan 2001 23:47:42 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rasputin Cc: freebsd-stable@freebsd.org Subject: Re: Anyone else seeing this? References: <20010115100709.A30062@dogma.freebsd-uk.eu.org> <4.2.2.20010115053326.01c64f00@marble.sentex.net> <20010115120719.A31194@dogma.freebsd-uk.eu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rasputin wrote: > > On Mon, Jan 15, 2001 at 05:34:12AM -0500, Mike Tancsa wrote: > > At 10:07 AM 1/15/2001 +0000, Rasputin wrote: > > >Incidentally, would anyone know an easy way of finding out > > >what code has changed in the ata drivers since Christmas - > > >other than mailing Soren of course :) > > > > http://www.freebsd.org/cgi/cvsweb.cgi/ > > > > will show you what has been committed. > > > > ---Mike > > Thanks Mike, think I spotted the change in question > (this is an Aladdin mobo, and /sys/dev/ata/ata-all.c says: > > "Revision 1.50.2.15, Thu Jan 4 09:08:56 2001 UTC (11 days, 2 hours ago) by sos > Branch: RELENG_4 > Changes since 1.50.2.14: +5 -2 lines > > MFC: > Proberly back down DMA modes on the Acer Aladdin." > ) > > I take it from RELENG_4 that this is the STABLE tree, yes? Ahh yes the *wonderfull* Aladdin chipset... Ever since 4.2S I have had timeout problems with that thing... I got a patch from Soren that fixed it, but I dont think its a very good chipset... Soren siad he would MFC that patch in, so ether this is another problem with the Aladdin or he hasnt MFC the patch in yet... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 5: 6:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from anarchy.io.com (anarchy.io.com [199.170.88.101]) by hub.freebsd.org (Postfix) with ESMTP id 7F5C537B402 for ; Mon, 15 Jan 2001 05:06:04 -0800 (PST) Received: from dumpster.io.com.io.com (aus-as3-122.io.com [208.2.106.122]) by anarchy.io.com (8.9.3/8.9.3) with SMTP id HAA21740; Mon, 15 Jan 2001 07:06:01 -0600 To: Josef Karthauser Cc: xlr82xs , Trend Hanger , freebsd-stable@FreeBSD.ORG Subject: Re: We are exporting quality Hanger for cloth, pants References: <20010115112922.7A68E37B699@hub.freebsd.org> <20010115213740.C580@xlr82xs.shacknet.nu> <20010115115322.C3578@tao.org.uk> From: Lars Eighner Date: 15 Jan 2001 07:16:16 -0600 In-Reply-To: Josef Karthauser's message of "Mon, 15 Jan 2001 11:53:22 +0000" Message-ID: <867l3x7y73.fsf@dumpster.io.com> Lines: 20 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Capitol Reef" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In our last episode, <20010115115322.C3578@tao.org.uk>, the lovely and talented Josef Karthauser > On Mon, Jan 15, 2001 at 09:37:40PM +1000, xlr82xs wrote: >> ummmmmm wtf is this doing on the freebsd-stable mailing list ? >> >> sorry for the implied language, and lack of written manner, but >> this came in and confused the hell out of me.. > It's been widespread spammed across a whole chunk of the net - it's > not just _ALL_ the freebsd lists it's gone to :). Okay, who sold spamming technology to the Red Chinese? I think the FBI needs to lock up Mr. Steve in Phoenix until this is thoroughly investigated. -- Lars Eighner eighner@io.com http://www.io.com/~eighner/ Cole's Law: Thinly sliced cabbage. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 5: 9:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 9819137B699 for ; Mon, 15 Jan 2001 05:09:14 -0800 (PST) Received: from [195.11.243.26] (helo=Debug) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 14I9Nk-0007OS-00; Mon, 15 Jan 2001 13:09:08 +0000 To: Lars Eighner , Josef Karthauser , xlr82xs , Trend Hanger , freebsd-stable@FreeBSD.ORG From: Cliff Sarginson Subject: Re: We are exporting quality Hanger for cloth, pants Date: Mon, 15 Jan 2001 13:09:08 GMT X-Mailer: www.webmail.nl.demon.net X-Sender: postmaster@btvs.demon.nl X-Originating-IP: 192.250.24.58 Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As spam goes, it is rather cute :) Cliff > In our last episode, <20010115115322.C3578@tao.org.uk>, > the lovely and talented Josef Karthauser > > > On Mon, Jan 15, 2001 at 09:37:40PM +1000, xlr82xs wrote: > >> ummmmmm wtf is this doing on the freebsd-stable mailing list ? > >> > >> sorry for the implied language, and lack of written manner, but > >> this came in and confused the hell out of me.. > > > It's been widespread spammed across a whole chunk of the net - it's > > not just _ALL_ the freebsd lists it's gone to :). > > > Okay, who sold spamming technology to the Red Chinese? I think the FBI > needs to lock up Mr. Steve in Phoenix until this is thoroughly investigated. > > > -- > Lars Eighner eighner@io.com http://www.io.com/~eighner/ > Cole's Law: Thinly sliced cabbage. > > > > 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 Jan 15 5:25:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id C529837B404 for ; Mon, 15 Jan 2001 05:25:32 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id FAA03137; Mon, 15 Jan 2001 05:24:56 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151324.FAA03137@spammie.svbug.com> Date: Mon, 15 Jan 2001 05:24:55 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: We are exporting quality Hanger for cloth, pants To: joe@tao.org.uk Cc: xlr82xs@sdf.lonestar.org, freebsd-stable@FreeBSD.ORG In-Reply-To: <20010115115322.C3578@tao.org.uk> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Jan, Josef Karthauser wrote: > On Mon, Jan 15, 2001 at 09:37:40PM +1000, xlr82xs wrote: >> >> ummmmmm wtf is this doing on the freebsd-stable mailing list ? >> >> sorry for the implied language, and lack of written manner, but this came in and confused the hell out of me.. > > It's been widespread spammed across a whole chunk of the net - it's not > just _ALL_ the freebsd lists it's gone to :). > Yes, someday we'll find a good countermeasure to this. In the mean time, a good cup of coffee will do. :-) (BTW, it's 5:23am here.) Oh, and I trimmed the spammer.... no use confirming our addresses directly. ;=> Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 5:49:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wilson.acpub.duke.edu (wilson.acpub.duke.edu [152.3.233.69]) by hub.freebsd.org (Postfix) with ESMTP id 7737137B699 for ; Mon, 15 Jan 2001 05:48:58 -0800 (PST) Received: from bobzilla.adsl.duke.edu (bobzilla.adsl.duke.edu [152.16.67.15]) by wilson.acpub.duke.edu (8.9.3/8.9.3/Duke-5.0.0) with ESMTP id IAA18426; Mon, 15 Jan 2001 08:48:25 -0500 (EST) Received: (from sto@localhost) by bobzilla.adsl.duke.edu (8.11.1/8.11.1) id f0FDmFl01470; Mon, 15 Jan 2001 08:48:15 -0500 (EST) (envelope-from sto) Date: Mon, 15 Jan 2001 08:48:15 -0500 From: "Sean O'Connell" To: freebsd-stable@FreeBSD.ORG Cc: Rasputin Subject: Re: Anyone else seeing this? Message-ID: <20010115084815.B1388@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: Sean O'Connell , freebsd-stable@FreeBSD.ORG, Rasputin References: <20010115100709.A30062@dogma.freebsd-uk.eu.org> <4.2.2.20010115053326.01c64f00@marble.sentex.net> <20010115120719.A31194@dogma.freebsd-uk.eu.org> <3A62F16E.9A06E0C7@quake.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A62F16E.9A06E0C7@quake.com.au>; from kaltorak@quake.com.au on Mon, Jan 15, 2001 at 11:47:42PM +1100 X-Organization: House of Schmutzli X-Kitties: Bitty Maya CJ Keisha Jacob Hopey X-Hounds: Bob Sheana X-OS-of-Choice: FreeBSD Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kal Torak stated: : Rasputin wrote: : > : > On Mon, Jan 15, 2001 at 05:34:12AM -0500, Mike Tancsa wrote: : > > At 10:07 AM 1/15/2001 +0000, Rasputin wrote: : > > >Incidentally, would anyone know an easy way of finding out : > > >what code has changed in the ata drivers since Christmas - : > > >other than mailing Soren of course :) : > > : > > http://www.freebsd.org/cgi/cvsweb.cgi/ : > > : > > will show you what has been committed. : > > : > > ---Mike : > : > Thanks Mike, think I spotted the change in question : > (this is an Aladdin mobo, and /sys/dev/ata/ata-all.c says: : > : > "Revision 1.50.2.15, Thu Jan 4 09:08:56 2001 UTC (11 days, 2 hours ago) by sos : > Branch: RELENG_4 : > Changes since 1.50.2.14: +5 -2 lines : > : > MFC: : > Proberly back down DMA modes on the Acer Aladdin." : > ) : > : > I take it from RELENG_4 that this is the STABLE tree, yes? : : : Ahh yes the *wonderfull* Aladdin chipset... : Ever since 4.2S I have had timeout problems with that thing... : I got a patch from Soren that fixed it, but I dont think its : a very good chipset... : : Soren siad he would MFC that patch in, so ether this is another : problem with the Aladdin or he hasnt MFC the patch in yet... I think there was a "more proper" patch for the Aladdin that came out shortly after this one. I think that if you were to patch in the difference between the -current versions 1.54 and 1.53 of /sys/dev/ata/ata-all.c, you'd be in business. Try using http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/ata-dma.c.diff?r1=1.53&r2=1.54 S -- 1--------01---------01--------01--------01--------01--------01--------0 Sean O'Connell sean@stat.Duke.EDU To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 6:28:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.clones.com (unknown [216.70.178.182]) by hub.freebsd.org (Postfix) with ESMTP id CE89637B401; Mon, 15 Jan 2001 06:27:50 -0800 (PST) Received: from clones.com ([10.1.1.50]) by mail.clones.com (8.9.3/8.9.3) with ESMTP id GAA23073; Mon, 15 Jan 2001 06:28:38 -0800 Message-ID: <3A6309B1.50CB392D@clones.com> Date: Mon, 15 Jan 2001 06:31:13 -0800 From: "Glendon M. Gross" X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: "Victor R. Cardona" Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: 4.2-STABLE keeps locking up References: <20010115033459.A31750@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll bet there's an IRQ conflict between the ethernet card and some other device in the system. Sometimes I have been able to fix these kinds of problems by recompiling the kernel without support for devices that I don't need. Just my 2 cents. Regards, Glendon Gross Victor R. Cardona wrote: > > Hi everyone, > > I am having a problem with my 4.2-STABLE box. A couple of days ago I > noticed that it started locking up on me. I have not been able to find > any error messages. The only thing I have noticed is that when I use > ncftp, and the client is logging in to the remote server, then the box > locks up. The FreeBSD box is acting as my firewall. Does anyone have any > suggestions as to how I can diagnose what the problem is? > > I have already remade world to see if that would help. It did not. I am > running IPFilter, Bind, DHCPd, and Apache on this box. > > Thanks, > Victor Cardona > -- > GnuPG Key fingerprint = 62B1 7995 A830 432C 74E8 1337 EDDB E682 3C76 7404 > > 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 Jan 15 7:21:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.rdc1.il.home.com (mail2.rdc1.il.home.com [24.2.1.77]) by hub.freebsd.org (Postfix) with ESMTP id B4B2437B400; Mon, 15 Jan 2001 07:21:03 -0800 (PST) Received: from marx.marvic.chum ([24.17.229.11]) by mail2.rdc1.il.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010115152103.UDF849.mail2.rdc1.il.home.com@marx.marvic.chum>; Mon, 15 Jan 2001 07:21:03 -0800 Received: (from vcardona@localhost) by marx.marvic.chum (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id JAA32720; Mon, 15 Jan 2001 09:21:37 -0600 Date: Mon, 15 Jan 2001 09:21:36 -0600 From: "Victor R. Cardona" To: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: 4.2-STABLE keeps locking up Message-ID: <20010115092136.A32717@home.com> Mail-Followup-To: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG References: <20010115033459.A31750@home.com> <3A6309B1.50CB392D@clones.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6309B1.50CB392D@clones.com>; from gross@clones.com on Mon, Jan 15, 2001 at 06:31:13AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 06:31:13AM -0800, Glendon M. Gross wrote: > I'll bet there's an IRQ conflict between the ethernet card and some > other device in the system. > Sometimes I have been able to fix these kinds of problems by recompiling > the kernel without support for devices that I don't need. > Just my 2 cents. Thanks. I don't know what else I can strip out of the kernel config though. As it is, I took out just about everything. Victor Cardona -- GnuPG Key fingerprint = 62B1 7995 A830 432C 74E8 1337 EDDB E682 3C76 7404 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 8: 9: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from knock.econ.vt.edu (knock.econ.vt.edu [128.173.172.240]) by hub.freebsd.org (Postfix) with ESMTP id EFFD437B400; Mon, 15 Jan 2001 08:08:46 -0800 (PST) Received: (from rdmurphy@localhost) by knock.econ.vt.edu (8.11.1/8.11.1) id f0FG8TI12260; Mon, 15 Jan 2001 11:08:29 -0500 (EST) (envelope-from rdmurphy) From: "Russell D. Murphy Jr." MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14947.8317.578727.362433@knock.econ.vt.edu> Date: Mon, 15 Jan 2001 11:08:29 -0500 (EST) To: Kris Kennaway Cc: Peter , stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP In-Reply-To: <20010114160503.B14278@citusc.usc.edu> References: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net> <20010114160503.B14278@citusc.usc.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: rdmurphy@vt.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I upgraded from STABLE as of last Friday. I *did* run mergemaster, but I'm also having this problem (ssh fails; scp does not): Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service Jan 14 14:37:59 knock sshd[9674]: fatal: PAM session setup failed[6]: Permission denied Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service knock [rdmurphy]% ls -l /var/tmp | grep temproot drwxr-xr-x 14 root wheel 512 Jan 12 11:25 temproot knock [rdmurphy]% uptime 10:59AM up 2 days, 23:31, 2 users, load averages: 0.01, 0.05, 0.06 knock [rdmurphy]% uname -a FreeBSD knock.econ.vt.edu 4.2-STABLE FreeBSD 4.2-STABLE #0: Fri Jan 12 09:41:19 EST 2001 rdmurphy@knock.econ.vt.edu:/disk1/obj/usr/src/sys/KNOCK i386 knock [rdmurphy]% diff /usr/src/crypto/openssh/sshd_config /etc/ssh/sshd_config 6c6,7 < #Protocol 2,1 --- > Protocol 2,1 > # Protocol 1,2 14c15,16 < PermitRootLogin no --- > # PermitRootLogin no > PermitRootLogin yes The most recent notice in UPDATING is: 20001120: FreeBSD 4.2 RELEASE. That's not to say that I merged in whatever the changes were appropriately (evidently I didn't. . .). I'd be grateful for some pointers; "read UPDATING" is not, at this point, a use suggestion. Thanks- Russ According to Kris Kennaway (January 14, 2001): | | The correct upgrade procedure involves running mergemaster after | installworld and installkernel. This would have avoided your problem - | please see the handbook for a full description of the upgrade | procedure. | | Kris -- Russell D. Murphy Department of Economics Virginia Polytechnic Institute and State University 3034 Pamplin Hall Blacksburg, Virginia 24061-0316 (540) 231-4537 rdmurphy@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 8:17:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 95ECD37B400 for ; Mon, 15 Jan 2001 08:17:22 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id 543581360C; Mon, 15 Jan 2001 11:17:22 -0500 (EST) Date: Mon, 15 Jan 2001 11:17:22 -0500 From: Chris Faulhaber To: rdmurphy@vt.edu Cc: stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP Message-ID: <20010115111722.B43912@peitho.fxp.org> References: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net> <20010114160503.B14278@citusc.usc.edu> <14947.8317.578727.362433@knock.econ.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14947.8317.578727.362433@knock.econ.vt.edu>; from rdmurphy@knock.econ.vt.edu on Mon, Jan 15, 2001 at 11:08:29AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 11:08:29AM -0500, Russell D. Murphy Jr. wrote: > > I upgraded from STABLE as of last Friday. I *did* run mergemaster, > but I'm also having this problem (ssh fails; scp does not): > > Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service > Jan 14 14:37:59 knock sshd[9674]: fatal: PAM session setup failed[6]: Permission denied > Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service > When did you update Friday? RELENG_4 src/etc/pam.conf was updated for sshd: =================================================================== RCS file: /home/ncvs/src/etc/pam.conf,v retrieving revision 1.6.2.2 retrieving revision 1.6.2.3 diff -u -p -r1.6.2.2 -r1.6.2.3 --- src/etc/pam.conf 2000/12/07 15:16:12 1.6.2.2 +++ src/etc/pam.conf 2001/01/12 10:13:59 1.6.2.3 @@ -7,7 +7,7 @@ # work quite right. If you delete the final entry, be sure to change # "sufficient" to "required" in the entry before it. # -# $FreeBSD: /home/ncvs/src/etc/pam.conf,v 1.6.2.2 2000/12/07 15:16:12 ru Exp $ +# $FreeBSD: /home/ncvs/src/etc/pam.conf,v 1.6.2.3 2001/01/12 10:13:59 ps Exp $ # If the user can authenticate with S/Key, that's sufficient; allow clear # password. Try kerberos, then try plain unix password. @@ -21,6 +21,12 @@ ftpd auth sufficient pam_skey.so ftpd auth requisite pam_cleartext_pass_ok.so #ftpd auth sufficient pam_kerberosIV.so try_first_pass ftpd auth required pam_unix.so try_first_pass + +# OpenSSH with PAM support requires similar modules. The session one is +# a bit strange, though... +sshd auth sufficient pam_skey.so +sshd auth required pam_unix.so try_first_pass +sshd session required pam_permit.so # Don't break startx xserver auth required pam_permit.so -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 8:34:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from knock.econ.vt.edu (knock.econ.vt.edu [128.173.172.240]) by hub.freebsd.org (Postfix) with ESMTP id 71EA137B401 for ; Mon, 15 Jan 2001 08:33:59 -0800 (PST) Received: (from rdmurphy@localhost) by knock.econ.vt.edu (8.11.1/8.11.1) id f0FGXtK12347; Mon, 15 Jan 2001 11:33:55 -0500 (EST) (envelope-from rdmurphy) From: "Russell D. Murphy Jr." MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14947.9843.490701.117192@knock.econ.vt.edu> Date: Mon, 15 Jan 2001 11:33:55 -0500 (EST) To: Chris Faulhaber Cc: stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP In-Reply-To: <20010115111722.B43912@peitho.fxp.org> References: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net> <20010114160503.B14278@citusc.usc.edu> <14947.8317.578727.362433@knock.econ.vt.edu> <20010115111722.B43912@peitho.fxp.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: rdmurphy@vt.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like I missed it: knock [rdmurphy]% ident /usr/src/etc/pam.conf /usr/src/etc/pam.conf: $FreeBSD: src/etc/pam.conf,v 1.6.2.2 2000/12/07 15:16:12 ru Exp $ According to Chris Faulhaber (January 15, 2001): | | When did you update Friday? RELENG_4 src/etc/pam.conf was updated for sshd: | | =================================================================== | RCS file: /home/ncvs/src/etc/pam.conf,v | retrieving revision 1.6.2.2 | retrieving revision 1.6.2.3 That should do it, thanks- Russ -- Russell D. Murphy Department of Economics Virginia Polytechnic Institute and State University 3034 Pamplin Hall Blacksburg, Virginia 24061-0316 (540) 231-4537 rdmurphy@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 10:12:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 91A2D37B401; Mon, 15 Jan 2001 10:12:28 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id KAA24217; Mon, 15 Jan 2001 10:13:29 -0800 Date: Mon, 15 Jan 2001 10:13:29 -0800 From: Kris Kennaway To: rdmurphy@vt.edu Cc: Kris Kennaway , Peter , stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP Message-ID: <20010115101329.A24211@citusc.usc.edu> References: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net> <20010114160503.B14278@citusc.usc.edu> <14947.8317.578727.362433@knock.econ.vt.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14947.8317.578727.362433@knock.econ.vt.edu>; from rdmurphy@knock.econ.vt.edu on Mon, Jan 15, 2001 at 11:08:29AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 15, 2001 at 11:08:29AM -0500, Russell D. Murphy Jr. wrote: >=20 > I upgraded from STABLE as of last Friday. I *did* run mergemaster, > but I'm also having this problem (ssh fails; scp does not): >=20 > Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service > Jan 14 14:37:59 knock sshd[9674]: fatal: PAM session setup failed[6]: Per= mission denied > Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service If you are still getting this message, then your pam.conf is out of date. Since you also have an out of date sshd_config and both of these are installed by mergemaster, I'm led to suspect you haven't run mergemaster with the latest sources. Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6Yz3JWry0BWjoQKURAtLOAJ9ehHnozfgw+3tsfg+1xbV0Vgpw0wCfdPUk M90SInnVD19gGc8Vzf/U7Po= =2M4a -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 10:43: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id DC77F37B400 for ; Mon, 15 Jan 2001 10:42:41 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id KAA00407; Mon, 15 Jan 2001 10:42:22 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151842.KAA00407@spammie.svbug.com> Date: Mon, 15 Jan 2001 10:42:19 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support To: keichii@peorth.iteration.net Cc: roman@harmonic.co.il, freebsd-stable@FreeBSD.ORG In-Reply-To: <20010101133411.B51028@peorth.iteration.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1 Jan, Michael C . Wu wrote: > On Mon, Jan 01, 2001 at 12:09:30PM +0200, Roman Shterenzon scribbled: > | On Thu, 28 Dec 2000 opentrax@email.com wrote: > | > On 28 Dec, Gerald Pfeifer wrote: > | > > Having been hit by this today, how about MFCing the following change? > | > > > | > > revision 1.289 > | > > date: 2000/11/14 01:11:13; author: jkh; state: Exp; lines: +4 -1 > | > > In the year 2000, I think it's perfectly reasonable to include audio > | > > support by default in GENERIC. > | > > > | > I can't answer for JKH or others but audio has had a history > | > of problems, especially durning the boot-up probe stage. > | > Problems such that it might lock up the machine under > | > certain conditions. Perhaps this is the reason sound may > | > never make it into GENERIC. > > I do not recall ever having such trouble with newpcm, nor > has newpcm been troublesome for people. If newpcm > does not probe, the boot process continues on. There is no > "probe problem." > > JMJr: Stop spreading baseless, false information like this, please. > What the hell are you talking about? I've never said such a thing. But for the record, putting sound in GENERIC is not a good idea. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 10:48:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id 93D2937B404 for ; Mon, 15 Jan 2001 10:48:03 -0800 (PST) Received: from HP2500B (veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id 053C78C13 for ; Mon, 15 Jan 2001 12:47:20 -0600 (CST) Message-ID: <02c501c07f23$6df9e350$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: References: <200101151842.KAA00407@spammie.svbug.com> Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support Date: Mon, 15 Jan 2001 12:46:10 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What the hell are you talking about? > I've never said such a thing. > But for the record, putting sound in GENERIC is not a good idea. :-) > > It is there in current. I assume it will be there when 5.0 is released. Tom Veldhouse veldy@veldy.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 10:55:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id 52C9037B401 for ; Mon, 15 Jan 2001 10:55:09 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id KAA00430; Mon, 15 Jan 2001 10:54:49 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151854.KAA00430@spammie.svbug.com> Date: Mon, 15 Jan 2001 10:54:46 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) To: keichii@peorth.iteration.net Cc: roman@harmonic.co.il, freebsd-stable@FreeBSD.ORG In-Reply-To: <20010101133411.B51028@peorth.iteration.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From my last post, Your right I was wrong. I did say that... Can't read my own quote. :-) On 1 Jan, Michael C . Wu wrote: > On Mon, Jan 01, 2001 at 12:09:30PM +0200, Roman Shterenzon scribbled: > | On Thu, 28 Dec 2000 opentrax@email.com wrote: > | > On 28 Dec, Gerald Pfeifer wrote: > | > > Having been hit by this today, how about MFCing the following change? > | > > > | > > revision 1.289 > | > > date: 2000/11/14 01:11:13; author: jkh; state: Exp; lines: +4 -1 > | > > In the year 2000, I think it's perfectly reasonable to include audio > | > > support by default in GENERIC. > | > > > | > I can't answer for JKH or others but audio has had a history > | > of problems, especially durning the boot-up probe stage. > | > Problems such that it might lock up the machine under > | > certain conditions. Perhaps this is the reason sound may > | > never make it into GENERIC. > > I do not recall ever having such trouble with newpcm, nor > has newpcm been troublesome for people. If newpcm > does not probe, the boot process continues on. There is no > "probe problem." > > JMJr: Stop spreading baseless, false information like this, please. > Baseless, my eye you pinhead. Our company has been doing sound for over 10 years. I've witnessed this lockup many times. So get off it. :-) > | Yes, I really hope that it doesn't make it into the GENERIC. > | GENERIC kernel should provide fully functional and stable machine without > | bells and whistles. Sound is a luxury. > > "Fully functional" for a desktop implies a working sound card too. > This is one of of those things that does not really matter very much. > A good server admin will recompile and customize his kernel. > And a desktop user probably does not know how to compile a kernel. > Are you telling me that, in your consultancy, you just keep GENERIC? > > There is no need for this bikeshed. Whether pcm is included in GEERIC > or not does not really hurt anybody either way. > Someone suggested that it go into KLM. That's a good suggestion. Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 10:57:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.ufl.edu (sp28fe.nerdc.ufl.edu [128.227.128.108]) by hub.freebsd.org (Postfix) with ESMTP id 5512A37B400 for ; Mon, 15 Jan 2001 10:57:29 -0800 (PST) Received: from ufl.edu (neti.eng.ufl.edu [128.227.235.15]) by smtp.ufl.edu (8.9.3/8.9.3/2.2.1) with ESMTP id NAA165382; Mon, 15 Jan 2001 13:57:19 -0500 Message-ID: <3A63484B.6E0D1253@ufl.edu> Date: Mon, 15 Jan 2001 13:58:19 -0500 From: Bob Johnson X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en, eo MIME-Version: 1.0 To: peter@a3.ca Cc: stable@freebsd.org Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP References: <3A622EDD.2572DEE9@ufl.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob Johnson wrote: > > > > > > > Date: Sun, 14 Jan 2001 11:42:03 -0800 > > From: "Peter" > > Subject: sshd not working after upgrade to 4.2S from 4.1R HELP > > > > This is a multi-part message in MIME format. > > > > - ------=_NextPart_000_0012_01C07E1F.03A67360 > > Content-Type: text/plain; > > charset="iso-8859-1" > > Content-Transfer-Encoding: quoted-printable > > > > Hello=20 > > > > I have a little problems after I cvsup my src and post. Then build = > > and install a new kernel. BTW im was on 4.1R now 4.2S. Everything run = > > great now but i can't seem to login ssh. =20 > > > > this is the error msg i got under /var/log/messages > > > > Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service > > Jan 14 11:28:23 crazie sshd[209]: fatal: PAM session setup failed[6]: = > > Permission denied > > Jan 14 11:28:23 crazie sshd[209]: no modules loaded for `sshd' service > > > > I had a similar problem once caused by a change in /etc/pam.conf, but > I don't think it has changed between 4.1R and 4.2S. In my case, I > needed the "other" section at the end of the file. > > I would look at /etc/pam.conf and /etc/ssh/sshd_config to see if > anything changed that might explain this. I think the 4.2S versions > will be in /usr/src/etc and /usr/src/crypto/openssh: compare them > to your backup copies of the old ones to see what changed. > I just upgraded a system to 4.2-STABLE and it does indeed have a new sshd entry in /etc/pam.conf. You need to add that to your pam.conf. In general, you need to run mergemaster after upgrading. It steps through the various configuration files, shows you which ones have changed, and helps you merge your customizations into the new versions. - Bob > You might also make sure the files /etc/nologin and /var/run/nologin > do not exist: if they do you will be logged out immediately after > you log in, which you describe below (but that doesn't explain the > PAM error messages). > > - Bob > > > everytime i tried to login=20 > > > > the password prompt up and if i enter the wrong password it will ask me = > > again=20 > > but when i enter the right pass work it logged me out. =20 > > > > Cuz someone suggestion or point me to how to fix it. I tried = > > reinstalling it. but still given me the same problems. Thank you=20 > > > > Peter > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 10:58:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id 2971A37B401 for ; Mon, 15 Jan 2001 10:58:05 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id SAA67739 for freebsd-stable@freebsd.org; Mon, 15 Jan 2001 18:57:58 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101151857.SAA67739@ns.a1.org.uk> Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP In-Reply-To: <20010115101329.A24211@citusc.usc.edu> from Kris Kennaway at "Jan 15, 2001 10:13:29 am" To: freebsd-stable@freebsd.org Date: Mon, 15 Jan 2001 18:57:58 +0000 (GMT) Reply-To: 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 X-Loop: FreeBSD.ORG > On Mon, Jan 15, 2001 at 11:08:29AM -0500, Russell D. Murphy Jr. wrote: > > > > I upgraded from STABLE as of last Friday. I *did* run mergemaster, > > but I'm also having this problem (ssh fails; scp does not): > > > > Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service > > Jan 14 14:37:59 knock sshd[9674]: fatal: PAM session setup failed[6]: Permission denied > > Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service > > If you are still getting this message, then your pam.conf is out of > date. Since you also have an out of date sshd_config and both of these > are installed by mergemaster, I'm led to suspect you haven't run > mergemaster with the latest sources. > > Kris I had exactly this problem. I track stable at home and work, and build/install world regularly. I did a new installation from the 4.2R CD on Friday, and immediatly cvsup'd from uk2 I had the problem with pam (after mergemaster) but only realised on Saturday. I did a new cvsup build/install merge and everything was fine! Bap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 11:11:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id 5835137B400 for ; Mon, 15 Jan 2001 11:11:26 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id TAA67779 for freebsd-stable@freebsd.org; Mon, 15 Jan 2001 19:11:25 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101151911.TAA67779@ns.a1.org.uk> Subject: My xterm has broken :( To: freebsd-stable@freebsd.org Date: Mon, 15 Jan 2001 19:11:24 +0000 (GMT) Reply-To: freebsd-stable@freebsd.org.uk 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 X-Loop: FreeBSD.ORG Hi, Can anyone help with this one? I have STABLE from this afternoon, but have also upgraded to XFree86 4 It seems to be okay, except when I try to get an xterm, I get nothing! This is the log message generated: /usr/libexec/ld-elf.so.1: Undefined symbol "_XA_UTF8_STRING" referenced from COP Y relocation in xterm Can anyone help? Bap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 11:16:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id AE73437B400 for ; Mon, 15 Jan 2001 11:16:22 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id TAA67801 for freebsd-stable@freebsd.org; Mon, 15 Jan 2001 19:16:21 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101151916.TAA67801@ns.a1.org.uk> Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP In-Reply-To: <3A63484B.6E0D1253@ufl.edu> from Bob Johnson at "Jan 15, 2001 01:58:19 pm" To: freebsd-stable@freebsd.org Date: Mon, 15 Jan 2001 19:16:21 +0000 (GMT) Reply-To: 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 X-Loop: FreeBSD.ORG > Bob Johnson wrote: > I just upgraded a system to 4.2-STABLE and it does indeed have a > new sshd entry in /etc/pam.conf. You need to add that to your > pam.conf. > > In general, you need to run mergemaster after upgrading. It steps > through the various configuration files, shows you which ones have > changed, and helps you merge your customizations into the new > versions. > > - Bob Yes, but there was an "issue" sometime on Friday that was sorted by Sat lunch. I always run mergemaster, but I was hit with this one too. Bap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 11:20:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id 771BF37B400 for ; Mon, 15 Jan 2001 11:20:06 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id LAA00472; Mon, 15 Jan 2001 11:19:52 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200101151919.LAA00472@spammie.svbug.com> Date: Mon, 15 Jan 2001 11:19:47 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support To: veldy@veldy.net Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <02c501c07f23$6df9e350$3028680a@tgt.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Jan, Thomas T. Veldhouse wrote: > >> What the hell are you talking about? >> I've never said such a thing. >> But for the record, putting sound in GENERIC is not a good idea. :-) >> >> > It is there in current. I assume it will be there when 5.0 is released. > Looks like a good reason not to move to 5.0. :-) BTW, none of my machines run STABLE or CURRENT, only RELEASE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 11:33:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from knock.econ.vt.edu (knock.econ.vt.edu [128.173.172.240]) by hub.freebsd.org (Postfix) with ESMTP id 2306837B402; Mon, 15 Jan 2001 11:33:28 -0800 (PST) Received: (from rdmurphy@localhost) by knock.econ.vt.edu (8.11.1/8.11.1) id f0FJXKU13009; Mon, 15 Jan 2001 14:33:20 -0500 (EST) (envelope-from rdmurphy) From: "Russell D. Murphy Jr." MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14947.20608.318737.611142@knock.econ.vt.edu> Date: Mon, 15 Jan 2001 14:33:20 -0500 (EST) To: Kris Kennaway Cc: Peter , stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP In-Reply-To: <20010115101329.A24211@citusc.usc.edu> References: <001501c07e62$26beb0e0$cb3b35d1@bconnected.net> <20010114160503.B14278@citusc.usc.edu> <14947.8317.578727.362433@knock.econ.vt.edu> <20010115101329.A24211@citusc.usc.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: rdmurphy@vt.edu Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Kris Kennaway (January 15, 2001): | | If you are still getting this message, then your pam.conf is out of | date. Since you also have an out of date sshd_config and both of these | are installed by mergemaster, I'm led to suspect you haven't run | mergemaster with the latest sources. | | Kris Now I'm really confused -- in particular by your comment about an out of date sshd_config. Why do you think so? What version *should* I have? Chris F. pointed out that my pam.conf was probably out of date; that does seem to be the case. Adding the new lines to pam.conf seems to have fixed the problem (which was caused by missing the change to pam.conf, not by not running mergemaster). Cvsup ran at 5:30am Friday (east coast): ===== Fri Jan 12 05:30:03 EST 2001: Getting CVSup updates ===== Fri Jan 12 05:31:06 EST 2001: Build world I have: knock [rdmurphy]% ident /usr/src/crypto/openssh/sshd_config /usr/src/crypto/openssh/sshd_config: $FreeBSD: src/crypto/openssh/sshd_config,v 1.4.2.4 2001/01/12 04:25:59 green Exp $ But, from the cvsweb (http://www.FreeBSD.org/cgi/cvsweb.cgi) page, I find that the current version of sshd_config is 1.2.2.3: Default branch: MAIN Current tag: RELENG_4 Revision 1.2.2.3 / (download) - annotate - [select for diffs], Sat Oct 28 23:00:50 2000 UTC (2 months, 2 weeks ago) by kris Branch: RELENG_4 CVS Tags: RELENG_4_2_0_RELEASE Changes since 1.2.2.2: +1 -1 lines Diff to previous 1.2.2.2 (colored) to branchpoint 1.2 (colored) next main 1.3 (colored) How did I get 1.4.2.4? My cvs supfile is: *default tag=RELENG_4 *default host=cvsup4.FreeBSD.org *default prefix=/usr *default base=/usr/local/etc/cvsup *default release=cvs delete use-rel-suffix src-all doc-all tag=. From the cvsup checkouts file: knock [src-all]% grep 'sshd_config' checkouts.cvs:RELENG_4 | head -1 C src/crypto/openssh/sshd_config,v RELENG_4 . 2#871#19#9792735594#81273#444 1.4. 2.4 2001.01.12.04.25.59 2#871#19#9792954314#16013#644 and the most recent cvsup log file: Edit src/crypto/openssh/sshd_config Add delta 1.4.2.4 2001.01.12.04.25.59 green On the other hand, the versions of pam.conf all seem as expected: knock [rdmurphy]% ident /usr/src/etc/pam.conf /usr/src/etc/pam.conf: $FreeBSD: src/etc/pam.conf,v 1.6.2.2 2000/12/07 15:16:12 ru Exp $ knock [rdmurphy]% ident /etc/pam.conf /etc/pam.conf: $FreeBSD: src/etc/pam.conf,v 1.6.2.2 2000/12/07 15:16:12 ru Exp $ and the cvsweb interface lists 1.6.2.3 (which I was missing): Default branch: MAIN Current tag: RELENG_4 Revision 1.6.2.3 / (download) - annotate - [select for diffs], Fri Jan 12 10:13:59 2001 UTC (3 days, 9 hours ago) by ps Branch: RELENG_4 Changes since 1.6.2.2: +7 -1 lines Diff to previous 1.6.2.2 (colored) to branchpoint 1.6 (colored) next main 1.7 (colored) I'm not trying to complain, I'd just like to understand what's going on. Thanks- Russ -- Russell D. Murphy Department of Economics Virginia Polytechnic Institute and State University 3034 Pamplin Hall Blacksburg, Virginia 24061-0316 (540) 231-4537 rdmurphy@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 11:50: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 13CB837B402 for ; Mon, 15 Jan 2001 11:49:39 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0FJmdN83621; Mon, 15 Jan 2001 11:48:39 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: opentrax@email.com Cc: keichii@peorth.iteration.net, roman@harmonic.co.il, freebsd-stable@FreeBSD.ORG Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support In-Reply-To: Message from opentrax@email.com of "Mon, 15 Jan 2001 10:42:19 PST." <200101151842.KAA00407@spammie.svbug.com> Date: Mon, 15 Jan 2001 11:48:39 -0800 Message-ID: <83617.979588119@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But for the record, putting sound in GENERIC is not a good idea. :-) Why? Don't just make assertions like this, back them up with evidence. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 11:52:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id A810B37B400 for ; Mon, 15 Jan 2001 11:52:18 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0FJprN83649; Mon, 15 Jan 2001 11:51:53 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: opentrax@email.com Cc: keichii@peorth.iteration.net, roman@harmonic.co.il, freebsd-stable@FreeBSD.ORG Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) In-Reply-To: Message from opentrax@email.com of "Mon, 15 Jan 2001 10:54:46 PST." <200101151854.KAA00430@spammie.svbug.com> Date: Mon, 15 Jan 2001 11:51:52 -0800 Message-ID: <83645.979588312@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Baseless, my eye you pinhead. > Our company has been doing sound for over 10 years. > I've witnessed this lockup many times. So get off it. :-) I have never seen the pcm driver lock up and can only conclude that your company simply needs to get better engineers. :) > Someone suggested that it go into KLM. That's a good suggestion. We don't use LKMs (LKM is an airline) anymore. You know, it really would be good if you went away and studied what FreeBSD is actually doing for, say, a couple of years and then and came back and started posting again. Both parties could use the break anyway. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 12: 4:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gershwin.tera.com (gershwin.cray.com [207.224.230.28]) by hub.freebsd.org (Postfix) with ESMTP id AB53F37B400 for ; Mon, 15 Jan 2001 12:04:11 -0800 (PST) Received: from thought.org (tao.sea.tera.com [207.108.223.55]) by gershwin.tera.com (8.9.3/8.9.3) with ESMTP id MAA10484 for ; Mon, 15 Jan 2001 12:04:10 -0800 (PST) Received: (from kline@localhost) by thought.org (8.11.0/8.11.0) id f0FK42O22536 for freebsd-stable@FreeBSD.ORG; Mon, 15 Jan 2001 12:04:02 -0800 (PST) (envelope-from kline) From: Gary Kline Message-Id: <200101152004.f0FK42O22536@thought.org> Subject: AWE64 on FreeBSD-4.1 To: freebsd-stable@FreeBSD.ORG Date: Mon, 15 Jan 2001 12:04:01 -0800 (PST) Organization: <> thought.org: pvblic service Unix since 1986... <> X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a strange one. A program I've been working on for some time uses sound generated and played thru /dev/dsp. Before my program starts, the error-checking routines make sure that the sound card is configured; if not, then the program pops up an error-window. Here, on this old platform, my ISA soundcard went south and the program does what it is supposed to. It pops up the error-window and quits. My second FreeBSD system has an AWE64 which is configured into my KERNEL config file. When I exec my program on this second system, and when I try to use the soundcard, no-joy. The message from the driver is that /dev/dsp is "Busy". Anybody know what's going on? Any ideas on how to fix this problem? TIA, guys, gary -- Gary D. Kline kline@tao.thought.org Public service Unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 12: 6:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 802A937B402 for ; Mon, 15 Jan 2001 12:06:34 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0FK58191732; Mon, 15 Jan 2001 12:05:08 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101151854.KAA00430@spammie.svbug.com> Date: Mon, 15 Jan 2001 12:06:40 -0800 (PST) From: John Baldwin To: opentrax@email.com Subject: RE: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support Cc: freebsd-stable@FreeBSD.org, roman@harmonic.co.il, keichii@peorth.iteration.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Jan-01 opentrax@email.com wrote: > On 1 Jan, Michael C . Wu wrote: >> On Mon, Jan 01, 2001 at 12:09:30PM +0200, Roman Shterenzon scribbled: >> | On Thu, 28 Dec 2000 opentrax@email.com wrote: >> | > On 28 Dec, Gerald Pfeifer wrote: >> | > > Having been hit by this today, how about MFCing the following change? >> | > > >> | > > revision 1.289 >> | > > date: 2000/11/14 01:11:13; author: jkh; state: Exp; lines: +4 -1 >> | > > In the year 2000, I think it's perfectly reasonable to include audio >> | > > support by default in GENERIC. >> | > > >> | > I can't answer for JKH or others but audio has had a history >> | > of problems, especially durning the boot-up probe stage. >> | > Problems such that it might lock up the machine under >> | > certain conditions. Perhaps this is the reason sound may >> | > never make it into GENERIC. >> >> I do not recall ever having such trouble with newpcm, nor >> has newpcm been troublesome for people. If newpcm >> does not probe, the boot process continues on. There is no >> "probe problem." >> >> JMJr: Stop spreading baseless, false information like this, please. >> > Baseless, my eye you pinhead. > Our company has been doing sound for over 10 years. > I've witnessed this lockup many times. So get off it. :-) So this code infringes on your market and its in your best interest to discredit it. Ok. FWIW, Cameron Grant has been writing sound drivers for 10 years, so this isn't an amateurish attempt. Also, I have _yet_ to have a problem with pcm hanging during probe. Ever. On both ISA and PCI cards. >> | Yes, I really hope that it doesn't make it into the GENERIC. >> | GENERIC kernel should provide fully functional and stable machine without >> | bells and whistles. Sound is a luxury. >> >> "Fully functional" for a desktop implies a working sound card too. >> This is one of of those things that does not really matter very much. >> A good server admin will recompile and customize his kernel. >> And a desktop user probably does not know how to compile a kernel. >> Are you telling me that, in your consultancy, you just keep GENERIC? >> >> There is no need for this bikeshed. Whether pcm is included in GEERIC >> or not does not really hurt anybody either way. >> > Someone suggested that it go into KLM. That's a good suggestion. That has been done. GENERIC and kld's (d, not m) are two different things however. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 12:19:49 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 D26F637B402 for ; Mon, 15 Jan 2001 12:19:28 -0800 (PST) Received: (qmail 6129 invoked by uid 0); 15 Jan 2001 20:19:27 -0000 Received: from p3ee2166d.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.109) by mail.gmx.net (mp004-rz3) with SMTP; 15 Jan 2001 20:19:27 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id SAA09281 for freebsd-stable@freebsd.org; Mon, 15 Jan 2001 18:45:00 +0100 Date: Mon, 15 Jan 2001 18:45:00 +0100 From: Gerhard Sittig To: FreeBSD Stable Subject: Re: odd mouse button behavior Message-ID: <20010115184459.X253@speedy.gsinet> Mail-Followup-To: FreeBSD Stable References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from randy@psg.com on Sun, Jan 14, 2001 at 09:26:35PM -0800 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 14, 2001 at 21:26 -0800, Randy Bush wrote: > just cvsupped to > 4.2-stable as of today > xfree 4.0.2 > > and all of a sudden my mouse does not react to a button until > the mosue travels. this is most strange. You don't have your third button emulated by any chance? Check your configuration and especially the *missing* settings which might be set to non appropriate defaults. When in doubt, explicitely state your wishes. 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 Mon Jan 15 13: 7:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 8A34737B404 for ; Mon, 15 Jan 2001 13:06:58 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0FL6l487391; Mon, 15 Jan 2001 13:06:47 -0800 (PST) (envelope-from dillon) Date: Mon, 15 Jan 2001 13:06:47 -0800 (PST) From: Matt Dillon Message-Id: <200101152106.f0FL6l487391@earth.backplane.com> To: Jordan Hubbard Cc: opentrax@email.com, keichii@peorth.iteration.net, roman@harmonic.co.il, freebsd-stable@FreeBSD.ORG Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) References: <83645.979588312@winston.osd.bsdi.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think it would be a bad idea to put sound in GENERIC, not so much because the concept is a bad idea, but because there are a huge number of sound chips on the market with varying levels of compatibility and complexity and probing for them in GENERIC could result in GENERIC not working on as wide a range of machines as it would otherwise. When I install on a workstation, I always install without sound first to get the thing working, then I mess around with the sound drivers. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 13:14:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 0501437B404 for ; Mon, 15 Jan 2001 13:14:13 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0FLBSN84039; Mon, 15 Jan 2001 13:11:29 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: Matt Dillon Cc: opentrax@email.com, keichii@peorth.iteration.net, roman@harmonic.co.il, freebsd-stable@FreeBSD.ORG Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) In-Reply-To: Message from Matt Dillon of "Mon, 15 Jan 2001 13:06:47 PST." <200101152106.f0FL6l487391@earth.backplane.com> Date: Mon, 15 Jan 2001 13:11:28 -0800 Message-ID: <84035.979593088@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think it would be a bad idea to put sound in GENERIC, not so much > because the concept is a bad idea, but because there are a huge number > of sound chips on the market with varying levels of compatibility and Well, sound is *already* in GENERIC in -current and has been for awhile with no complaints at all from the snapshot users, so the sky hasn't fallen yet. There are also certainly a lot of drivers currently in GENERIC which would cause me far more concern if I was worried about things breaking during the probe. That's not to say that we shouldn't do such a "potential impact audit" for GENERIC at some point, but I wouldn't start first with the pcm driver if we were to do so. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 13:17:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 2A0F037B402 for ; Mon, 15 Jan 2001 13:17:20 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f0FLFp193103; Mon, 15 Jan 2001 13:15:51 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101152106.f0FL6l487391@earth.backplane.com> Date: Mon, 15 Jan 2001 13:17:23 -0800 (PST) From: John Baldwin To: Matt Dillon Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support Cc: freebsd-stable@FreeBSD.org, roman@harmonic.co.il, keichii@peorth.iteration.net, opentrax@email.com, Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15-Jan-01 Matt Dillon wrote: > I think it would be a bad idea to put sound in GENERIC, not so much > because the concept is a bad idea, but because there are a huge number > of sound chips on the market with varying levels of compatibility and > complexity and probing for them in GENERIC could result in GENERIC not > working on as wide a range of machines as it would otherwise. When > I install on a workstation, I always install without sound first to > get the thing working, then I mess around with the sound drivers. Umm, by default there are no ISA drivers configured, so the only sound cards that would be probed are PnP and PCI cards. These probes are non destructive and won't cause problems. I agree that any ISA probes should be disabled by default. > -Matt -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 13:17:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id D909A37B401 for ; Mon, 15 Jan 2001 13:17:21 -0800 (PST) Received: from jking (jking.lgc.com [134.132.76.82]) by cgi.sstar.com (8.11.1/8.11.1) with SMTP id f0FLGZ933232 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Mon, 15 Jan 2001 15:16:40 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <01d201c07f38$76d52470$524c8486@jking> From: "Jim King" To: "Matt Dillon" , "Jordan Hubbard" Cc: , , , References: <83645.979588312@winston.osd.bsdi.com> <200101152106.f0FL6l487391@earth.backplane.com> Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) Date: Mon, 15 Jan 2001 15:16:35 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matt Dillon" : > I think it would be a bad idea to put sound in GENERIC, not so much > because the concept is a bad idea, but because there are a huge number > of sound chips on the market with varying levels of compatibility and > complexity and probing for them in GENERIC could result in GENERIC not > working on as wide a range of machines as it would otherwise. When > I install on a workstation, I always install without sound first to > get the thing working, then I mess around with the sound drivers. Just a suggestion: Distribute 3 or 4 kernels and let the user pick which one they want install. Have one be like the current state of GENERIC, one tuned for servers (with RAID drivers, etc.), one tuned for modern workstations (sound, etc.). Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 13:18:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 5AC6337B699 for ; Mon, 15 Jan 2001 13:18:23 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id F36C3177E9F; Mon, 15 Jan 2001 15:18:25 -0600 (CST) Message-ID: <035101c07f38$b4a6cba0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Matt Dillon" , "Jordan Hubbard" Cc: , , , References: <84035.979593088@winston.osd.bsdi.com> Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) Date: Mon, 15 Jan 2001 15:18:29 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it even necessary to have pcm in GENERIC since its a kld in -current too? > Well, sound is *already* in GENERIC in -current and has been for > awhile with no complaints at all from the snapshot users, so the sky > hasn't fallen yet. There are also certainly a lot of drivers > currently in GENERIC which would cause me far more concern if I was > worried about things breaking during the probe. That's not to say > that we shouldn't do such a "potential impact audit" for GENERIC at > some point, but I wouldn't start first with the pcm driver if we were > to do so. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 13:23:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id E366837B402 for ; Mon, 15 Jan 2001 13:22:53 -0800 (PST) Received: (qmail 6270 invoked from network); 15 Jan 2001 21:20:35 -0000 Received: from acs-24-154-26-81.zoominternet.net (HELO cvzoom.net) (24.154.26.81) by scully.zoominternet.net with SMTP; 15 Jan 2001 21:20:35 -0000 Message-ID: <3A636A2D.2C731772@cvzoom.net> Date: Mon, 15 Jan 2001 16:22:53 -0500 From: Donn Miller X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jim King Cc: Matt Dillon , Jordan Hubbard , opentrax@email.com, keichii@peorth.iteration.net, roman@harmonic.co.il, freebsd-stable@FreeBSD.ORG Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) References: <83645.979588312@winston.osd.bsdi.com> <200101152106.f0FL6l487391@earth.backplane.com> <01d201c07f38$76d52470$524c8486@jking> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim King wrote: > Just a suggestion: Distribute 3 or 4 kernels and let the user pick which > one they want install. Have one be like the current state of GENERIC, one > tuned for servers (with RAID drivers, etc.), one tuned for modern > workstations (sound, etc.). Or, only statically link the "essential" drivers into the kernel. "Luxury" items such as pcm could be loaded via a KLD, as someone else suggested. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 13:42:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (dhcp45-24.dis.org [216.240.45.24]) by hub.freebsd.org (Postfix) with ESMTP id 88B6E37B400 for ; Mon, 15 Jan 2001 13:41:53 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0FLu9s00932; Mon, 15 Jan 2001 13:56:09 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101152156.f0FLu9s00932@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "David W. Chapman Jr." Cc: freebsd-stable@FreeBSD.ORG Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) In-reply-to: Your message of "Mon, 15 Jan 2001 15:18:29 CST." <035101c07f38$b4a6cba0$931576d8@inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Jan 2001 13:56:08 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is it even necessary to have pcm in GENERIC since its a kld in -current too? No; putting sound support in GENERIC is entirely unnecessary where the KLD is available. If you want sound, load the KLD either through /boot/ loader.conf, or add a "sound_enable" knob to /etc/rc.conf. > > Well, sound is *already* in GENERIC in -current and has been for > > awhile with no complaints at all from the snapshot users, so the sky > > hasn't fallen yet. There are also certainly a lot of drivers > > currently in GENERIC which would cause me far more concern if I was > > worried about things breaking during the probe. That's not to say > > that we shouldn't do such a "potential impact audit" for GENERIC at > > some point, but I wouldn't start first with the pcm driver if we were > > to do so. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- ... 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 Jan 15 13:44: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id E047937B401; Mon, 15 Jan 2001 13:43:29 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 1AE55177E9F; Mon, 15 Jan 2001 15:43:29 -0600 (CST) Message-ID: <038e01c07f3c$3480de80$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Mike Smith" Cc: References: <200101152156.f0FLu9s00932@mass.osd.bsdi.com> Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) Date: Mon, 15 Jan 2001 15:43:32 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That is exactly what I was thinking, just making sure there wasn't anything I was missing. ----- Original Message ----- From: "Mike Smith" To: "David W. Chapman Jr." Cc: Sent: Monday, January 15, 2001 3:56 PM Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) > > Is it even necessary to have pcm in GENERIC since its a kld in -current too? > > No; putting sound support in GENERIC is entirely unnecessary where the KLD > is available. If you want sound, load the KLD either through /boot/ > loader.conf, or add a "sound_enable" knob to /etc/rc.conf. > > > > Well, sound is *already* in GENERIC in -current and has been for > > > awhile with no complaints at all from the snapshot users, so the sky > > > hasn't fallen yet. There are also certainly a lot of drivers > > > currently in GENERIC which would cause me far more concern if I was > > > worried about things breaking during the probe. That's not to say > > > that we shouldn't do such a "potential impact audit" for GENERIC at > > > some point, but I wouldn't start first with the pcm driver if we were > > > to do so. > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > -- > ... 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 Jan 15 14: 8:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id E1D6B37B400 for ; Mon, 15 Jan 2001 14:08:12 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id WAA68138 for freebsd-stable@freebsd.org; Mon, 15 Jan 2001 22:08:11 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101152208.WAA68138@ns.a1.org.uk> Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) In-Reply-To: <200101152156.f0FLu9s00932@mass.osd.bsdi.com> from Mike Smith at "Jan 15, 2001 01:56:08 pm" To: freebsd-stable@freebsd.org Date: Mon, 15 Jan 2001 22:08:11 +0000 (GMT) Reply-To: 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 X-Loop: FreeBSD.ORG > > Is it even necessary to have pcm in GENERIC since its a kld in -current too? > > No; putting sound support in GENERIC is entirely unnecessary where the KLD > is available. If you want sound, load the KLD either through /boot/ > loader.conf, or add a "sound_enable" knob to /etc/rc.conf. I thought the whole point of the GENERIC kernel is to support enough to allow an install on the majority of systems and allow the PC to be operable. I always compile a new GENERIC kernel when upgrading, as well as the hosts own kernel, but, only for disaster recovery. I just don't see any point at all in having sound in the GENERIC kernel. Maybe people are just too lazy to compile their own kernels. Bap. > > > > Well, sound is *already* in GENERIC in -current and has been for > > > awhile with no complaints at all from the snapshot users, so the sky > > > hasn't fallen yet. There are also certainly a lot of drivers > > > currently in GENERIC which would cause me far more concern if I was > > > worried about things breaking during the probe. That's not to say > > > that we shouldn't do such a "potential impact audit" for GENERIC at > > > some point, but I wouldn't start first with the pcm driver if we were > > > to do so. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 14:12:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 977E937B401 for ; Mon, 15 Jan 2001 14:12:12 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 92ABE5756B; Mon, 15 Jan 2001 16:09:30 -0600 (CST) Date: Mon, 15 Jan 2001 16:09:30 -0600 From: "Michael C . Wu" To: freebsd-stable@freebsd.org Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) Message-ID: <20010115160930.A59752@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , freebsd-stable@freebsd.org References: <200101152156.f0FLu9s00932@mass.osd.bsdi.com> <200101152208.WAA68138@ns.a1.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101152208.WAA68138@ns.a1.org.uk>; from aer001@a1.org.uk on Mon, Jan 15, 2001 at 10:08:11PM +0000 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can we please stop this bikeshed? -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 14:21: 6 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id E30E737B401 for ; Mon, 15 Jan 2001 14:20:47 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id JAA04313; Tue, 16 Jan 2001 09:20:43 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01JYYXHSJRS0EMXV9L@cim.alcatel.com.au>; Tue, 16 Jan 2001 09:20:42 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.0/8.11.0) id f0FMKHB38355; Tue, 16 Jan 2001 09:20:17 +1100 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 16 Jan 2001 09:20:17 +1100 From: Peter Jeremy Subject: Re: Dummynet stopping ? In-reply-to: <3a62e370.5b5.0@infolink.com.br>; from apina@infolink.com.br on Mon, Jan 15, 2001 at 09:48:00AM -0500 To: Antonio Carlos Pina Cc: freebsd-stable@FreeBSD.ORG Mail-followup-to: Antonio Carlos Pina , freebsd-stable@FreeBSD.ORG Message-id: <20010116092017.G91029@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <3a62e370.5b5.0@infolink.com.br> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2001-Jan-15 09:48:00 -0500, Antonio Carlos Pina wrote: >Today, after 2 months working like a charm, one of my dummynet pipes >stopped to pipe. The IP Address that it takes care was online and I >could even ping it from within my bridge machine, through his own >interface, but I couldn't ping or whatever from that ip address. That's really weird. The rules you posted are symmetrical, as is a ping - if you can ping his IP address, he should be able to ping your IP address. Did you check for other network problems (correct routes in both machines, appropriate ARP entries in both machines)? Did netstat or tcpdump show any traffic to/from that address via ep0? I presume there were no messages from the kernel. I'm also using dummynet and haven't noticed any similar problem (the machine in question has been up for just under 62 days). >I took a little look in ipfw pipe list, but I couldn't understand the >data that was showed (drps I presume are drops, it was increasing >while I was looking) The format is fairly self-explanatory. Since you aren't doing any address masking inside the pipe (the mask line is all zeroes), you should have a single bucket (BKT 0) on each pipe. The protocol, source and destination fields can be ignored. The remaining fields represent (in order) the total packets through the pipe, total bytes through the pipe, current packets queued in the pipe, current bytes queued in the pipe and number of packets dropped. If you created a pipe using "ipfw pipe 3 config bw 64Kbit/s", then your pipe can hold 50 packets (if the pipe has 50 packets in it, any extra packets sent to the pipe will be dropped). The bandwidth you specify is internally stored as bits per second (not bytes per tick as documented). An outgoing packet will be sent N ticks after the previous packet (where N = (packet_length * 8 * hz) / bandwidth). Obvious causes for the pipe not working are: - The dummynet scheduler has stopped. This can be checked with the sysctl net.inet.ip.dummynet.curr_time, which should be incrementing at HZ counts/sec. (This will affect all pipes). - Dummynet can't allocate memory for queued packets. This can be checked with "vmstat -m | grep IpFw". > I'm a bit concern because as I >can ping the IP address from within the bridge machine, I can't even >do a little script to test this situation and rebuild the pipes... :-/ The alternative would be to monitor the dropped packets and if the drop rate exceeds some limit, re-create the pipe. Your problem here is that you can't distinguish a drop because the pipe isn't working from a drop because the bandwidth is exceeded. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 14:38: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 8DE6C37B401 for ; Mon, 15 Jan 2001 14:37:39 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 1B72A177E9F for ; Mon, 15 Jan 2001 16:37:42 -0600 (CST) Message-ID: <03f701c07f43$c75a63a0$931576d8@inethouston.net> From: "David W. Chapman Jr." To: References: <200101152208.WAA68138@ns.a1.org.uk> Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) Date: Mon, 15 Jan 2001 16:37:44 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You don't even have to compile it into the kernel, just kldload pcm > I just don't see any point at all in having sound in the GENERIC kernel. > Maybe people are just too lazy to compile their own kernels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 15:45:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tzeench.dhs.org (h24-70-93-66.ed.shawcable.net [24.70.93.66]) by hub.freebsd.org (Postfix) with ESMTP id 776D337B69C for ; Mon, 15 Jan 2001 15:44:53 -0800 (PST) Received: from localhost (darren@localhost) by tzeench.dhs.org (8.11.1/8.11.1) with ESMTP id f0FNix901075 for ; Mon, 15 Jan 2001 16:44:59 -0700 (MST) (envelope-from darren@tzeench.dhs.org) Date: Mon, 15 Jan 2001 16:44:58 -0700 (MST) From: Darrern To: Subject: sound support Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG just wondering if theres any word as of yet on our sound driver having 4 channel output?(surround sound 4 speaker output) I have an oss liscence which is about to expire and cost about the same as the sound card. pci128. -Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 15:58:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tk212017121218.teleweb.at (TK212017121218.teleweb.at [212.17.121.218]) by hub.freebsd.org (Postfix) with SMTP id 4D08E37B401 for ; Mon, 15 Jan 2001 15:58:24 -0800 (PST) Received: (qmail 10776 invoked from network); 15 Jan 2001 23:58:21 -0000 Received: from unknown (HELO freebsd2.rocks) (192.168.1.3) by 192.168.1.1 with SMTP; 15 Jan 2001 23:58:21 -0000 Received: (qmail 1364 invoked by uid 1001); 15 Jan 2001 23:58:20 -0000 Date: Tue, 16 Jan 2001 00:58:20 +0100 From: Herbert To: freebsd-questions@freebsd.org Subject: Epox 8KTA2 Message-ID: <20010116005820.A797@freebsd2.rocks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I have replaced a MSI K7T Pro2 mainboard with an Epox 8KTA72 today and now I have problems running my FreeBSD-4.2 STABLE system. The drives fall back from UDMA66 into PIO4 mode and the system is very unstable. XWindow, netscape and other apps crash randomly and when I try to compile the system or a kernel my kernel panics. :( I testet this system under m$ win me I have no such problems? Is this only a problem with the ata controller? Or do you think I should also check some other parts of my computer? What if I buy a promise ata 100 controller? Will this solve my problems? There is a cheap one available from promise (not the fastrak 100) ... is this one also supported under FreeBSD 4.2 STABLE? Or only the Fastrak 100? My cdrom drive seems to run fine in UDMA33 mode ... strange, isn't it? Hope anybody on the list can help me! Thanks a lot! Regards! Herbert J. Skuhra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 16:12:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id A115337B6A4; Mon, 15 Jan 2001 16:12:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f0G0C2R82581; Mon, 15 Jan 2001 18:12:02 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101160012.f0G0C2R82581@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Victor R. Cardona" Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG From: David Kelly Subject: Re: 4.2-STABLE keeps locking up In-reply-to: Message from "Victor R. Cardona" of "Mon, 15 Jan 2001 09:21:36 CST." <20010115092136.A32717@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Jan 2001 18:12:02 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Victor R. Cardona" writes: > On Mon, Jan 15, 2001 at 06:31:13AM -0800, Glendon M. Gross wrote: > > I'll bet there's an IRQ conflict between the ethernet card and some > > other device in the system. > > Sometimes I have been able to fix these kinds of problems by recompiling > > the kernel without support for devices that I don't need. > > Just my 2 cents. > > Thanks. I don't know what else I can strip out of the kernel config > though. As it is, I took out just about everything. Then maybe the problem isn't in FreeBSD. My computer had to be rebuilt last month after a lightning strike. Went from an Asus P6NP5 and PPro-166/512k to an Asus A7V and 800MHz AMD Thunderbird Athlon. Never had so much trouble with a MB that assigned my Symbios SCSI card to IRQ 3... But IRQ's were not the final solution to the system locking up under heavy SCSI, ATA-100, and ethernet activity (FreeBSD, of course). "BIOS Defaults" was the cure, in addition to changing a performance setting from "Optimal" to "Standard" (think "Optimal" was the default). Manual said "Optimal" was PCI 2.2. My PCI cards are years old so this is probably a bad setting for me. It works now and I'm not interested enough to go back and see if "Optimal" works. The biggest change I saw was "PCI Master Read Caching" and "Delayed Transaction" were disabled while the PC shop apparently enabled them. Way back in the -questions archive you may find where my P6NP5 was having floppy problems. As in, "Doesn't work in FreeBSD but does in DOS and NT4SP3." That too was cured with "BIOS Defaults" altho I manually went back and restored everything the same afterwards. Apparently there are hidden items that can be cleared to sane default, but set only with a special utility. Don't know how they got set un-sane in the first place. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 16:23:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from spammie.svbug.com (unknown [198.79.110.2]) by hub.freebsd.org (Postfix) with ESMTP id 66EA937B6A4 for ; Mon, 15 Jan 2001 16:23:30 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id QAA00791; Mon, 15 Jan 2001 16:15:33 -0800 (PST) (envelope-from jessem@spammie.mozie.org) Message-Id: <200101160015.QAA00791@spammie.svbug.com> Date: Mon, 15 Jan 2001 16:15:29 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: MFC? src/sys/i386/conf/GENERIC and sound support To: jkh@winston.osd.bsdi.com Cc: keichii@peorth.iteration.net, roman@harmonic.co.il, freebsd-stable@FreeBSD.ORG In-Reply-To: <83617.979588119@winston.osd.bsdi.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Jan, Jordan Hubbard wrote: >> But for the record, putting sound in GENERIC is not a good idea. :-) > > Why? Don't just make assertions like this, back them up with > evidence. > Sure, What kind of evidence would satify you? Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 16:34:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lorne.arm.org (64-40-71-66.mebtel.net [64.40.71.66]) by hub.freebsd.org (Postfix) with ESMTP id 2D7CE37B6B0 for ; Mon, 15 Jan 2001 16:34:18 -0800 (PST) Received: (from dlt@localhost) by lorne.arm.org (8.11.1/8.11.1) id f0G0Mro02822; Mon, 15 Jan 2001 19:22:53 -0500 (EST) (envelope-from dlt@mebtel.net) X-Authentication-Warning: lorne.arm.org: dlt set sender to dlt@mebtel.net using -f To: FreeBSD-stable@FreeBSD.org Reply-To: dlt@mebtel.net Subject: Athlon and 4.2 Release From: Derek Tattersall Date: 15 Jan 2001 19:22:52 -0500 Message-ID: <867l3wfiqr.fsf@lorne.arm.org> Lines: 14 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 X-Loop: FreeBSD.ORG I have a 1 GHz Thunderbird (Athlon) on an ASUS A7V Via KT133 chipset with an IBM ultra 100 30 Gig Hard drive. If I let the HDD be auto detected, 4.2 Release terminates at the point it is going to partition the drive. If I set the HDD for LBA with all the options disabled, it reboots in the middle of the boot sequence, after the "press enter to boot now prompt". Has anybody got configuration suggestions for this combination that could get FreeBSD installed? Thanks in advance... -- Derek Tattersall dlt@mebtel.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 16:40:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xlr82xs.shacknet.nu (unknown [202.7.185.21]) by hub.freebsd.org (Postfix) with ESMTP id 9AF0337B6B9 for ; Mon, 15 Jan 2001 16:40:33 -0800 (PST) Received: (from xlr82xs@localhost) by xlr82xs.shacknet.nu (8.11.1/8.11.1) id f0G0e0d24889; Tue, 16 Jan 2001 10:40:00 +1000 (EST) (envelope-from xlr82xs) Date: Tue, 16 Jan 2001 10:39:56 +1000 From: xlr82xs To: Derek Tattersall Cc: freebsd-stable@freebsd.org Subject: Re: Athlon and 4.2 Release Message-ID: <20010116103956.D580@xlr82xs.shacknet.nu> References: <867l3wfiqr.fsf@lorne.arm.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="uZ3hkaAS1mZxFaxD" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <867l3wfiqr.fsf@lorne.arm.org>; from dlt@mebtel.net on Mon, Jan 15, 2001 at 07:22:52PM -0500 X-Operating-System: FreeBSD 4.2-STABLE on an i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --uZ3hkaAS1mZxFaxD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable purely out of interest, and i'm not sure what this would do, and this is as= sumeing you can install it useing lba have you tried switching it to auto mode after installation ? though if your talking about halting in the boot off the install disk/cd th= is is a moot question. Derek Tattersall [dlt@mebtel.net] wrote: > I have a 1 GHz Thunderbird (Athlon) on an ASUS A7V Via KT133 chipset > with an IBM ultra 100 30 Gig Hard drive. If I let the HDD be auto > detected, 4.2 Release terminates at the point it is going to partition=20 > the drive. If I set the HDD for LBA with all the options disabled, > it reboots in the middle of the boot sequence, after the "press enter > to boot now prompt". >=20 > Has anybody got configuration suggestions for this combination that > could get FreeBSD installed? >=20 > Thanks in advance... >=20 > --=20 > Derek Tattersall dlt@mebtel.net >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message >=20 --=20 Where do you think you're going today? -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d- s:+ !a c++++ UB++++ P+ L- E W++ N o+ K++ w-- O- M-- V-=20 PS+++ PE Y++ PGP+++ t 5- X+ R* tv+ b+++ DI++ D+ G+ e* h! r z++=20 ------END GEEK CODE BLOCK------ --uZ3hkaAS1mZxFaxD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjpjmFoACgkQcBR/Vvf1G2aLJACfdb05+kI4pbJ9nAlX9bRkY8Gp y/0An1Hy5X6HIa922T/78sRYkHHBSre+ =sXYN -----END PGP SIGNATURE----- --uZ3hkaAS1mZxFaxD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 17: 5:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www3.infolink.com.br (www3.infolink.com.br [200.255.108.4]) by hub.freebsd.org (Postfix) with ESMTP id 1963037B6C4 for ; Mon, 15 Jan 2001 17:04:56 -0800 (PST) Received: from diala11 (unverified [200.255.108.11]) by www3.infolink.com.br (Vircom SMTPRS 4.2.181) with SMTP id ; Mon, 15 Jan 2001 23:04:54 -0200 Message-ID: <003701c07f58$567b88c0$0b6cffc8@infolink.com.br> From: "Antonio Carlos Pina" To: "Peter Jeremy" Cc: References: <3a62e370.5b5.0@infolink.com.br> <20010116092017.G91029@gsmx07.alcatel.com.au> Subject: Re: Dummynet stopping ? Date: Mon, 15 Jan 2001 23:04:54 -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.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Peter, Thank you for your kind reply. > That's really weird. The rules you posted are symmetrical, as is a > ping - if you can ping his IP address, he should be able to ping your > IP address. Did you check for other network problems (correct routes > in both machines, appropriate ARP entries in both machines)? Did > netstat or tcpdump show any traffic to/from that address via ep0? > I presume there were no messages from the kernel. I think I didn't make myself clear, sorry. I can ping his IP address from WITHIN the Bridge and I believe he can ping the bridge too (of course, since there aren't rules to forbid this). But, I can NOT ping his IP address from my machine (for instance) neither he can ping me. Oh yes, under normal circunstances we can ping each other throught the pipes. I think I found something at least interesting: 00003: 128.000 Kbit/s 0 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp 200.xxx.xxx.xx/110 200.yyy.yyy.yy/64905 48150 41482697 0 0 0 00004: 128.000 Kbit/s 0 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp 200.yyy.yyy.yy/64905 200.xxx.xxx.xx/110 41463 6912193 0 0 0 yyy.yyy.yyy is my IP while xxx.xxx.xxx is a POP server outside our network (it's not smart to show IP addresses like I did before ;-)). Apparently our IP is reading a 40MB message or something (the number is growing) but this connection DOESN'T appears in tcpdump ! It's seems to me that our IP has closed the connection, and the pipe is still piping something. This is the position after the time I took to write this explanation above: 00003: 128.000 Kbit/s 0 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp 200.xxx.xxx.xx/110 200.yyy.yyy.yy/64905 48243 41515518 0 0 0 00004: 128.000 Kbit/s 0 ms 50 sl. 1 queues (1 buckets) droptail mask: 0x00 0x00000000/0x0000 -> 0x00000000/0x0000 BKT Prot ___Source IP/port____ ____Dest. IP/port____ Tot_pkt/bytes Pkt/Byte Drp 0 tcp 200.yyy.yyy.yy/64905 200.xxx.xxx.xx/110 41545 6917583 0 0 0 Perhaps this will cause memory allocation errors ? > Obvious causes for the pipe not working are: > - The dummynet scheduler has stopped. This can be checked with the > sysctl net.inet.ip.dummynet.curr_time, which should be incrementing > at HZ counts/sec. (This will affect all pipes). > - Dummynet can't allocate memory for queued packets. This can be > checked with "vmstat -m | grep IpFw". I will look deeper into this. Thank you very much for your answer. Best regards, Antonio Carlos Pina apina@infolink.com.br To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 17: 5:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from unbeat.com (unknown [66.9.8.88]) by hub.freebsd.org (Postfix) with ESMTP id 609EF37B6C5 for ; Mon, 15 Jan 2001 17:05:11 -0800 (PST) Received: (from moxie@localhost) by unbeat.com (8.11.1/8.11.0) id f0G14r201396; Mon, 15 Jan 2001 20:04:53 -0500 (EST) (envelope-from --) Date: Mon, 15 Jan 2001 20:04:53 -0500 From: JT To: Bernd Fuerwitt Cc: freebsd-stable@FreeBSD.ORG Subject: Re: serial console Message-ID: <20010115200452.I280@zed.unbeat.com> Mail-Followup-To: Bernd Fuerwitt , freebsd-stable@FreeBSD.ORG References: <918447C44E5CD31196740060B01A681602C190@leviathan.illu42.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <918447C44E5CD31196740060B01A681602C190@leviathan.illu42.de>; from bf@fuerwitt.de on Sun, Jan 14, 2001 at 06:13:29PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Serial console needs something like this in /etc/ttys: console "/usr/libexec/getty std.9600" vt100 on secure You probably stomped the change during mergemaster? On Sun, Jan 14, 2001 at 06:13:29PM +0100, Bernd Fuerwitt wrote: > hi all, > > I just updated one of our routers from 4.0-RELEASE to 4.2-RELEASE (using > cvsup and buildworld) > and now the serial console doesn't work anymore. > The file /boot.config contains -P and /boot/loader.conf contains > console=comconsole. > I get a login prompt at ttyd0, but no console. Messages stop after the > kernel starts booting. > Meanwhile I have updated to 4.2-STABLE but nothing changed. > > What am I doing wrong ? > > > > > > 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 Jan 15 17:15:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.evil.2y.net (ip-216-23-54-242.adsl.one.net [216.23.54.242]) by hub.freebsd.org (Postfix) with ESMTP id 96DF237B6C9 for ; Mon, 15 Jan 2001 17:15:32 -0800 (PST) Received: (from cokane@localhost) by www.evil.2y.net (8.11.1/8.11.1) id f0G1SFI11162 for freebsd-stable@FreeBSD.ORG; Mon, 15 Jan 2001 20:28:15 -0500 (EST) (envelope-from cokane) Date: Mon, 15 Jan 2001 20:28:15 -0500 From: Coleman Kane To: freebsd-stable@FreeBSD.ORG Subject: Re: sound support Message-ID: <20010115202815.A11103@cokane.yi.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from darren@tzeench.dhs.org on Mon, Jan 15, 2001 at 06:45:27PM -0500 X-Vim: vim:tw=70:ts=4:sw=4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, I just got a Sound Blaster Live! and was happy to see it working on my system. I saw the 7 /dev/dsp devices created by the pcm driver and was happy to see them all working. I would like to know if there is any work being down on four channel audio. Darrern had the audacity to say: > > just wondering if theres any word as of yet on our sound driver having 4 > channel output?(surround sound 4 speaker output) I have an oss liscence > which is about to expire and cost > about the same as the sound card. pci128. > > -Darren > > > > 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 Jan 15 17:23:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 5729B37B69D for ; Mon, 15 Jan 2001 17:23:37 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0G1N7N85142; Mon, 15 Jan 2001 17:23:07 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: "David W. Chapman Jr." Cc: "Matt Dillon" , opentrax@email.com, keichii@peorth.iteration.net, roman@harmonic.co.il, freebsd-stable@FreeBSD.ORG Subject: Re: OOPS.. (Re: MFC? src/sys/i386/conf/GENERIC and sound support) In-Reply-To: Message from "David W. Chapman Jr." of "Mon, 15 Jan 2001 15:18:29 CST." <035101c07f38$b4a6cba0$931576d8@inethouston.net> Date: Mon, 15 Jan 2001 17:23:06 -0800 Message-ID: <85139.979608186@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, maybe if it would load automatically on first open.. :) We need some stub loader technology... - Jordan > Is it even necessary to have pcm in GENERIC since its a kld in -current too? > > > > Well, sound is *already* in GENERIC in -current and has been for > > awhile with no complaints at all from the snapshot users, so the sky > > hasn't fallen yet. There are also certainly a lot of drivers > > currently in GENERIC which would cause me far more concern if I was > > worried about things breaking during the probe. That's not to say > > that we shouldn't do such a "potential impact audit" for GENERIC at > > some point, but I wouldn't start first with the pcm driver if we were > > to do so. > > > > > 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 Jan 15 17:24:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id EDBD537B69E for ; Mon, 15 Jan 2001 17:24:24 -0800 (PST) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id 3F2B015551; Mon, 15 Jan 2001 17:24:24 -0800 (PST) Date: Mon, 15 Jan 2001 17:24:24 -0800 From: Ron 'The InSaNe One' Rosson To: freebsd-stable@freebsd.org Cc: snort-users@lists.sourceforge.net, ipfilter@coombs.anu.edu.au Subject: Server locks up every 5-6 days Message-ID: <20010115172424.A79430@lunatic.oneinsane.net> Reply-To: Ron Rosson Mail-Followup-To: freebsd-stable@freebsd.org, snort-users@lists.sourceforge.net, ipfilter@coombs.anu.edu.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD lunatic.oneinsane.net 4.1.1-STABLE X-Moon: The Moon is Waning Gibbous (56% of Full) X-Opinion: What you read here is my IMHO X-WWW: http://www.oneinsane.net X-GPG-FINGERPRINT: 3F11 DB43 F080 C037 96F0 F8D3 5BD2 652B 171C 86DB X-Uptime: 4:57PM up 78 days, 19:12, 1 user, load averages: 0.11, 0.08, 0.01 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a server running at a clients that has a problem of rebooting every 5-6 days. It duties are as follows: Provide NAT for 25 workstations Be a Network Firewall Be a Network IDS Run a Web server for easy viewing for the Higher-ups The Server is FreeBSD 4.2-STABLE as of Dec 21, 2000 running on a k6-2 400 (mobo has the pcib2: . The internal and externla interfaces are Intel Pro 10/100B/100+ Ethernet cards. Machine has 64megs of RAM The NAT and Firewall chores are being handled by ipfilter 3.4.8 The IDS is snort version 1.7 logging to a mysql database (localhost) running the vision.conf ruleset (http://whitehats.com/ids) The webserver is Apach version 1.3.14 with mod_php4 (to allow ACID for snort to be viewed proplerly). The only public port open to this box is 22 (ssh) for administrative purposes. All other ports are blocked or filtered. From looking at the /var/log/messages and the ACID interface the box seems to get bombarded with the following log entires: Jan 11 18:26:30 mybox snort: IDS193/ddos-stacheldraht server-spoof: xxx.xxx.xxx.xxx -> xxx.xxx.xxx.xxx Anyone have any ideas what could be causing this.. The Lockups are in such a way that the only choice you have is to hit the reset button. TIA -- ------------------------------------------------------------------------------ Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------------------ I yield to Abdul Alhazred's superior knowledge of Cthulhu! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 17:37:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www3.infolink.com.br (www3.infolink.com.br [200.255.108.4]) by hub.freebsd.org (Postfix) with ESMTP id 846F237B69E for ; Mon, 15 Jan 2001 17:37:10 -0800 (PST) Received: from diala11 (unverified [200.255.108.11]) by www3.infolink.com.br (Vircom SMTPRS 4.2.181) with SMTP id ; Mon, 15 Jan 2001 23:37:08 -0200 Message-ID: <000701c07f5c$d75e3c90$0b6cffc8@infolink.com.br> From: "Antonio Carlos Pina" To: "Ben Jackson" Cc: References: <200101160109.f0G19N249067@saturn.home.ben.com> Subject: Re: Dummynet stopping ? Date: Mon, 15 Jan 2001 23:37:09 -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.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Ben, Nope, because everything is broken ;-) tcp, udp and icmp. Thanks anyway. Best Regards, Antonio Carlos Pina apina@infolink.com.br ----- Original Message ----- From: "Ben Jackson" To: "Antonio Carlos Pina" Sent: Monday, January 15, 2001 11:08 PM Subject: Re: Dummynet stopping ? > > If only ping is broken, could it be related to ICMP_BANDLIM? > > --Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 18:41:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id 9B93737B400 for ; Mon, 15 Jan 2001 18:41:06 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f0G2eNR95008; Mon, 15 Jan 2001 20:40:26 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101160240.f0G2eNR95008@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: dlt@mebtel.net Cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: Athlon and 4.2 Release In-Reply-To: Message from Derek Tattersall of "15 Jan 2001 19:22:52 EST." <867l3wfiqr.fsf@lorne.arm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Jan 2001 20:40:23 -0600 From: David Kelly Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Derek Tattersall writes: > I have a 1 GHz Thunderbird (Athlon) on an ASUS A7V Via KT133 chipset > with an IBM ultra 100 30 Gig Hard drive. If I let the HDD be auto > detected, 4.2 Release terminates at the point it is going to partition > the drive. If I set the HDD for LBA with all the options disabled, > it reboots in the middle of the boot sequence, after the "press enter > to boot now prompt". I boot my 800 MHz A7V from SCSI. And replaced the MB out from under an installed system. 9G on SCSI, 45G Maxtor on the on-board ATA-100. For this MB to run reliably under load I had to select "BIOS Defaults", and maybe also "System Performance Setting" from "Optimal" to "Normal". Also disabled "PCI Master Read Caching" and "Delayed Transaction". Something in there was causing problems under load. The situation might also surface during installation. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 19:30:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id AEF7037B69D for ; Mon, 15 Jan 2001 19:30:12 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id f0G3UAE03875; Mon, 15 Jan 2001 22:30:10 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200101160330.f0G3UAE03875@whizzo.transsys.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Gerhard Sittig Cc: FreeBSD Stable X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: odd mouse button behavior References: <20010115184459.X253@speedy.gsinet> In-reply-to: Your message of "Mon, 15 Jan 2001 18:45:00 +0100." <20010115184459.X253@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Jan 2001 22:30:10 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Jan 14, 2001 at 21:26 -0800, Randy Bush wrote: > > just cvsupped to > > 4.2-stable as of today > > xfree 4.0.2 > > > > and all of a sudden my mouse does not react to a button until > > the mosue travels. this is most strange. > > You don't have your third button emulated by any chance? Check > your configuration and especially the *missing* settings which > might be set to non appropriate defaults. When in doubt, > explicitely state your wishes. Huh, and I thought it was just me. I've had this same sort of thing going on recently too. I believe that the button-up (or button release) event is getting "lost". I see this when I click in a scroll bar, and sometimes it appears it's as if I still have the left button down. And producing a move event probably flushes something out..? This is with a 3 button wheel mouse, connected via USB and moused with the XFree4 port installed. I thought that perhaps the switch on the button had started to fail, but given that it's a fairly new mouse and someone else is seeing this, I'll have to investigate further. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 19:33:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lynx.aba.net.au (lynx.esec.com.au [203.21.84.1]) by hub.freebsd.org (Postfix) with SMTP id F205C37B69D for ; Mon, 15 Jan 2001 19:33:00 -0800 (PST) Received: (qmail 12870 invoked from network); 16 Jan 2001 03:32:58 -0000 Received: from swun.esec.com.au (HELO esec.com.au) (203.21.85.207) by lynx.esec.com.au with SMTP; 16 Jan 2001 03:32:58 -0000 Message-ID: <3A63C1FD.330CB59@esec.com.au> Date: Tue, 16 Jan 2001 14:37:33 +1100 From: Sam Wun Organization: eSec Limited X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ron Rosson Cc: freebsd-stable@freebsd.org, snort-users@lists.sourceforge.net, ipfilter@coombs.anu.edu.au Subject: Re: [Snort-users] Server locks up every 5-6 days References: <20010115172424.A79430@lunatic.oneinsane.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you show your df result? Ron 'The InSaNe One' Rosson wrote: > I have a server running at a clients that has a problem of rebooting > every 5-6 days. It duties are as follows: > > Provide NAT for 25 workstations > Be a Network Firewall > Be a Network IDS > Run a Web server for easy viewing for the Higher-ups > > The Server is FreeBSD 4.2-STABLE as of Dec 21, 2000 running on a k6-2 > 400 (mobo has the pcib2: . The > internal and externla interfaces are Intel Pro 10/100B/100+ Ethernet > cards. Machine has 64megs of RAM > > The NAT and Firewall chores are being handled by ipfilter 3.4.8 > > The IDS is snort version 1.7 logging to a mysql database (localhost) > running the vision.conf ruleset (http://whitehats.com/ids) > > The webserver is Apach version 1.3.14 with mod_php4 (to allow ACID for > snort to be viewed proplerly). > > The only public port open to this box is 22 (ssh) for administrative > purposes. All other ports are blocked or filtered. > > >From looking at the /var/log/messages and the ACID interface the box > seems to get bombarded with the following log entires: > > Jan 11 18:26:30 mybox snort: IDS193/ddos-stacheldraht server-spoof: xxx.xxx.xxx.xxx -> xxx.xxx.xxx.xxx > > Anyone have any ideas what could be causing this.. The Lockups are in > such a way that the only choice you have is to hit the reset button. > > TIA > -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 19:48: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41]) by hub.freebsd.org (Postfix) with ESMTP id 2F91F37B400 for ; Mon, 15 Jan 2001 19:47:49 -0800 (PST) Received: from [129.250.38.61] (helo=dfw-mmp1.email.verio.net) by dfw-smtpout1.email.verio.net with esmtp id 14IN64-0004Sm-00; Tue, 16 Jan 2001 03:47:48 +0000 Received: from [168.143.2.191] (helo=leviathan.clark.net) by dfw-mmp1.email.verio.net with esmtp id 14IN63-0004VE-00; Tue, 16 Jan 2001 03:47:47 +0000 Message-Id: <5.0.2.1.2.20010115224747.020d4ad0@mail.clark.net> X-Sender: thomas@mail.clark.net X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 15 Jan 2001 22:48:53 -0500 To: David Kelly , dlt@mebtel.net From: Mark Thomas Subject: Re: Athlon and 4.2 Release Cc: FreeBSD-stable@FreeBSD.ORG In-Reply-To: <200101160240.f0G2eNR95008@grumpy.dyndns.org> References: <867l3wfiqr.fsf@lorne.arm.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:40 PM 1/15/01 -0600, David Kelly wrote: >Derek Tattersall writes: >> I have a 1 GHz Thunderbird (Athlon) on an ASUS A7V Via KT133 chipset >> with an IBM ultra 100 30 Gig Hard drive. If I let the HDD be auto >> detected, 4.2 Release terminates at the point it is going to partition >> the drive. If I set the HDD for LBA with all the options disabled, >> it reboots in the middle of the boot sequence, after the "press enter >> to boot now prompt". > >I boot my 800 MHz A7V from SCSI. And replaced the MB out from under an >installed system. 9G on SCSI, 45G Maxtor on the on-board ATA-100. > >For this MB to run reliably under load I had to select "BIOS Defaults", >and maybe also "System Performance Setting" from "Optimal" to "Normal". >Also disabled "PCI Master Read Caching" and "Delayed Transaction". >Something in there was causing problems under load. The situation might >also surface during installation. I had issues with this MB under W98 that a BIOS flash helped resolve (I think up to 1004). It seems very picky about shared interrupts, particularly with the ATA/100 controller. Mark --- thomas@clark.net ---> http://www.clark.net/pub/thomas PBEM Eldritch --------> http://www.pbegames.com [TM4463-ORG] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 20:20:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from larry.compuage.com (larry.compuage.com [208.233.246.4]) by hub.freebsd.org (Postfix) with ESMTP id D646337B400 for ; Mon, 15 Jan 2001 20:20:13 -0800 (PST) Received: from hnet04.hendrix.net (unverified [208.233.247.37]) by larry.compuage.com (Vircom SMTPRS 4.0.179) with ESMTP id ; Tue, 16 Jan 2001 00:09:33 -0500 Date: Mon, 15 Jan 2001 23:19:28 +0000 (GMT) From: Kelly Hendrix To: Lars Eighner Cc: Josef Karthauser , xlr82xs , Trend Hanger , freebsd-stable@FreeBSD.ORG Subject: Re: We are exporting quality Hanger for cloth, pants In-Reply-To: <867l3x7y73.fsf@dumpster.io.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmmmmm....could this have anything to do with the missing hard drives at Los Alamos? Kelly On 15 Jan 2001, Lars Eighner had this to say about Re: We are exporting...: >In our last episode, <20010115115322.C3578@tao.org.uk>, >the lovely and talented Josef Karthauser > >> On Mon, Jan 15, 2001 at 09:37:40PM +1000, xlr82xs wrote: >>> ummmmmm wtf is this doing on the freebsd-stable mailing list ? >>> >>> sorry for the implied language, and lack of written manner, but >>> this came in and confused the hell out of me.. > >> It's been widespread spammed across a whole chunk of the net - it's >> not just _ALL_ the freebsd lists it's gone to :). > > >Okay, who sold spamming technology to the Red Chinese? I think the FBI >needs to lock up Mr. Steve in Phoenix until this is thoroughly investigated. > > > -- ______________________________________________________________________ | There are two ways to live your life. One is as though nothing is a | | miracle. The other is as though everything is a miracle. | | | | Albert Einstein (1879-1955) | |______________________________________________________________________| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 21:54:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shasta.joescanner.com (rfx-64-6-196-149.users.reflexcom.com [64.6.196.149]) by hub.freebsd.org (Postfix) with ESMTP id 54AC937B400 for ; Mon, 15 Jan 2001 21:54:17 -0800 (PST) Received: from rainier.wstein.com (rainier.wstein.com [192.168.250.14]) by shasta.joescanner.com (8.11.1/8.11.1) with ESMTP id f0G5sGT81637 for ; Mon, 15 Jan 2001 21:54:16 -0800 (PST) (envelope-from joes@joescanner.com) Date: Mon, 15 Jan 2001 21:54:16 -0800 (Pacific Standard Time) From: Joseph Stein To: Subject: 4.2-STABLE /dev/MAKEDEV broken Message-ID: X-X-Sender: joes@joescanner.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG @ line 1578, the ';;' to close the case are missing. joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jan 15 23:15:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from xlr82xs.shacknet.nu (unknown [203.12.164.43]) by hub.freebsd.org (Postfix) with ESMTP id 3933B37B401 for ; Mon, 15 Jan 2001 23:15:27 -0800 (PST) Received: by xlr82xs.shacknet.nu (8.11.1/8.11.1) id f0G7FKa75277 for stable@freebsd.org; Tue, 16 Jan 2001 17:15:21 +1000 (EST) (envelope-from xlr82xs) From: xlr82xs To: stable@freebsd.org Subject: Graphics Card Date: Tue, 16 Jan 2001 17:15:10 +1000 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01011617151006.71301@xlr82xs.shacknet.nu> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hrmm, i know this question probably isn't relavent, but still.. I've looked through the fbsd handbook for supported graphics cards, and i cant find anything, so i assume that everything is supported by freebsd atleast. I'm thinking about replaceing my old s3 trio dx graphics card, but i'm also kind of poor..and australian which hampers things even more... and i was wondering if anyone could suggest a nice graphics card (hopefully something capable of more than 16bit 800x600 under x11) that could be picked up fairly cheap, but still is compatable ? or if not, what i should spend the next few years saveing for. regards, David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjpj9QUACgkQcBR/Vvf1G2YoswCfYPABE5aKs27K2R8w/xJAGusN m94AoImFbXIiXed7T5Arjv+3maLiO574 =pURB -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 0: 9:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 5646A37B69E for ; Tue, 16 Jan 2001 00:08:52 -0800 (PST) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id SAA19850; Tue, 16 Jan 2001 18:38:38 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <01011617151006.71301@xlr82xs.shacknet.nu> Date: Tue, 16 Jan 2001 18:38:38 +1030 (CST) From: "Daniel O'Connor" To: xlr82xs Subject: RE: Graphics Card Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Jan-01 xlr82xs wrote: > I've looked through the fbsd handbook for supported graphics cards, and i > cant find anything, so i assume that everything is supported by freebsd > atleast. Try the Xfree86 documentation. All video cards will do text and most will do VESA which is the limit of FreeBSD's graphical capabilities :) > I'm thinking about replaceing my old s3 trio dx graphics card, but i'm also > kind of poor..and australian which hampers things even more... It's not that bad ;) > and i was wondering if anyone could suggest a nice graphics card (hopefully > something capable of more than 16bit 800x600 under x11) that could be picked > up fairly cheap, but still is compatable ? Well, a newer S3.. You can get a TNT2 M64 PCI for ~AU$120, and an AGP version for ~AU$110. (32Mb RAM blah blah blah). These work pretty well in X.. You *will* have trouble finding PCI cards :( You can get ATI Rage Pro Turbo's for ~AU$80. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 1: 6:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 8E25737B401 for ; Tue, 16 Jan 2001 01:06:29 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.1+3.4W/8.11.1) with ESMTP/inet id f0G96M878452 for ; Tue, 16 Jan 2001 18:06:23 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Persephone) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 37 From: Makoto MATSUSHITA To: stable@freebsd.org Subject: Broken kern.flp? Date: Tue, 16 Jan 2001 18:06:09 +0900 Message-Id: <20010116180609O.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just got a report that current 4-stable's floppy image, kern.flp is broken and it can't boot. Here is a sample session: *** BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 637/kB/48128kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 (root@usw3.freebsd.org, Mon Jan 15 11:41:27 GMT 2001) /kernel text=0x24113b data=0x2fdac+0x201ec elf_loadexec: cannot seek can't load module '/kernel': input/output error | Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel]... /kernel text=0x24113b data=0x2fdac+0x201ec elf_loadexec: cannot seek can't load 'kernel' can't load 'kernel.old' Type '?' for a list of commands, 'help' for more detailed help. ok *** What's going wrong? P.S.: I've confirmed this on VMware Workstation so there is no possibility that floppy drive and/or floppy media are broken :-) -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 1: 8: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tzeench.dhs.org (h24-70-93-66.ed.shawcable.net [24.70.93.66]) by hub.freebsd.org (Postfix) with ESMTP id C1BF237B402 for ; Tue, 16 Jan 2001 01:07:43 -0800 (PST) Received: from localhost (darren@localhost) by tzeench.dhs.org (8.11.1/8.11.1) with ESMTP id f0G97dx02070 for ; Tue, 16 Jan 2001 02:07:39 -0700 (MST) (envelope-from darren@tzeench.dhs.org) Date: Tue, 16 Jan 2001 02:07:39 -0700 (MST) From: Darrern To: Subject: network lag Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG alright, not sure if this is the place for this, but no one seems to know whats going on and I seem to have confused a lot of people. and we've even sat down for 6 hours on irc trying to solve it one on one. I've replaced connectors, etc.. just to clear up my network setup here it is: Windows Me:-----UTP----:HUB:----BNC----:FreeBSD:----BNC----:Win98 FreeBSD of course is my gateway. my FreeBSD machine has 2 ethernet cards. one xl0 and one ed0. or 3comm and lynksys. 3com is the outside world, lynksys is the internal lan. my problem is that at times when there is absolutely no internal lan traffic I can't reach above 60kps between 192.168.1.1(bsd) and 192.168.1.5(win me). I can't track the variable I need to fix. I run natd, and routed(which hasn't helped fix the problem yet). I have seen my internal net the way it is setup right now go as high as 800kps. nothing is changed and I can't find the variable I need to fix, anyone else experiencing this or have any idea how to fix it? -Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 1:34:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id 44A9A37B404 for ; Tue, 16 Jan 2001 01:33:52 -0800 (PST) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0G9Xkq82188 for ; Tue, 16 Jan 2001 10:33:51 +0100 (CET) Received: from rose.lpthe.jussieu.fr (root@[134.157.10.102]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0G9Xj323902 for ; Tue, 16 Jan 2001 10:33:45 +0100 (MET) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.11.1/8.11.1) id f0G9Xj800543 for freebsd-stable@FreeBSD.ORG; Tue, 16 Jan 2001 10:33:45 +0100 (CET) (envelope-from michel) Date: Tue, 16 Jan 2001 10:33:45 +0100 From: Michel Talon To: freebsd-stable@FreeBSD.ORG Subject: Re: My xterm has broken :( Message-ID: <20010116103345.A503@lpthe.jussieu.fr> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <200101151911.TAA67779@ns.a1.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200101151911.TAA67779@ns.a1.org.uk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 07:11:24PM +0000, Catch-all m-box wrote: > Hi, > Can anyone help with this one? > > I have STABLE from this afternoon, but have also upgraded to XFree86 4 > It seems to be okay, except when I try to get an xterm, I get nothing! > > This is the log message generated: > /usr/libexec/ld-elf.so.1: Undefined symbol "_XA_UTF8_STRING" referenced from COP > Y relocation in xterm I have also seen that on my machine. What i have done: fetched XFree 4.02 from www.xfree86.org make World, make install and all was solved. -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 1:42:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id 5B18137B699 for ; Tue, 16 Jan 2001 01:42:03 -0800 (PST) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0G9g2q85058 for ; Tue, 16 Jan 2001 10:42:02 +0100 (CET) Received: from rose.lpthe.jussieu.fr (root@[134.157.10.102]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0G9g1324186 for ; Tue, 16 Jan 2001 10:42:01 +0100 (MET) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.11.1/8.11.1) id f0G9g1a00569 for FreeBSD-stable@FreeBSD.ORG; Tue, 16 Jan 2001 10:42:01 +0100 (CET) (envelope-from michel) Date: Tue, 16 Jan 2001 10:42:01 +0100 From: Michel Talon To: FreeBSD-stable@FreeBSD.ORG Subject: Re: Athlon and 4.2 Release Message-ID: <20010116104201.B503@lpthe.jussieu.fr> Mail-Followup-To: FreeBSD-stable@FreeBSD.ORG References: <200101160240.f0G2eNR95008@grumpy.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200101160240.f0G2eNR95008@grumpy.dyndns.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 08:40:23PM -0600, David Kelly wrote: > Derek Tattersall writes: > > I have a 1 GHz Thunderbird (Athlon) on an ASUS A7V Via KT133 chipset > > with an IBM ultra 100 30 Gig Hard drive. If I let the HDD be auto > > detected, 4.2 Release terminates at the point it is going to partition > > the drive. If I set the HDD for LBA with all the options disabled, > > it reboots in the middle of the boot sequence, after the "press enter > > to boot now prompt". > > I boot my 800 MHz A7V from SCSI. And replaced the MB out from under an > installed system. 9G on SCSI, 45G Maxtor on the on-board ATA-100. > > For this MB to run reliably under load I had to select "BIOS Defaults", > and maybe also "System Performance Setting" from "Optimal" to "Normal". > Also disabled "PCI Master Read Caching" and "Delayed Transaction". > Something in there was causing problems under load. The situation might > also surface during installation. Strange because i have here installed FreeBSD 4.2-Stable on an Abit KT7 Raid which has the same chipset, and runs an Athlon 1.1 Ghz. I have loaded all optimal settings in the Bios to enhance speed, and all works beautifully, including UDMA speed for the disk (here a Western Digital). -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 1:47:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id 025EF37B69B for ; Tue, 16 Jan 2001 01:47:11 -0800 (PST) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0G9l9q86882 for ; Tue, 16 Jan 2001 10:47:09 +0100 (CET) Received: from rose.lpthe.jussieu.fr (root@[134.157.10.102]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0G9l9324254 for ; Tue, 16 Jan 2001 10:47:09 +0100 (MET) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.11.1/8.11.1) id f0G9l8400590 for stable@FreeBSD.ORG; Tue, 16 Jan 2001 10:47:08 +0100 (CET) (envelope-from michel) Date: Tue, 16 Jan 2001 10:47:08 +0100 From: Michel Talon To: stable@FreeBSD.ORG Subject: Re: Broken kern.flp? Message-ID: <20010116104708.C503@lpthe.jussieu.fr> Mail-Followup-To: stable@FreeBSD.ORG References: <20010116180609O.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20010116180609O.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 16, 2001 at 06:06:09PM +0900, Makoto MATSUSHITA wrote: > > I've just got a report that current 4-stable's floppy image, kern.flp > is broken and it can't boot. Here is a sample session: > > *** > > BTX loader 1.00 BTX version is 1.01 > Console: internal video/keyboard > BIOS drive A: is disk0 > BIOS drive C: is disk1 > BIOS 637/kB/48128kB available memory > > FreeBSD/i386 bootstrap loader, Revision 0.8 > (root@usw3.freebsd.org, Mon Jan 15 11:41:27 GMT 2001) > /kernel text=0x24113b data=0x2fdac+0x201ec > elf_loadexec: cannot seek > can't load module '/kernel': input/output error > | > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [kernel]... > /kernel text=0x24113b data=0x2fdac+0x201ec > elf_loadexec: cannot seek > can't load 'kernel' > can't load 'kernel.old' > I have seen that also trying to install 4.2-Release on my new machine. Fortunately the cdrom booted OK. I thought it was bad floppy, but apparently not. -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 1:51:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from paperboy.sixforty.co.uk (paperboy.sixforty.co.uk [195.10.242.11]) by hub.freebsd.org (Postfix) with ESMTP id 4B3F437B699 for ; Tue, 16 Jan 2001 01:51:12 -0800 (PST) Received: (from root@localhost) by paperboy.sixforty.co.uk (8.11.1/8.11.1) id f0G9p5o58523 for freebsd-stable@freebsd.org; Tue, 16 Jan 2001 09:51:05 GMT (envelope-from lawrence@epcdirect.co.uk) Delivered-To: Received: from lfarr (daisy.sixforty.co.uk [195.10.242.200]) by paperboy.sixforty.co.uk (8.11.1/8.11.1av) with SMTP id f0G9p2A58515 for ; Tue, 16 Jan 2001 09:51:02 GMT (envelope-from lawrence@epcdirect.co.uk) From: "Lawrence Farr" To: Subject: RE: Athlon and 4.2 Release Date: Tue, 16 Jan 2001 09:51:04 -0000 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.4133.2400 Importance: Normal X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I also have a 950 Athlon on an A7v with cheap PC133 ram, and a seagate Barracuda IDE drive on the UDMA66 channel at home. Rock stable, does a buildworld in 45 minutes!. Sat next to me is an A7v with cheap PC133 ram, a Quantum drive on the UDMA100 channel that also is rock stable. Both the 1004 BIOS, set to optimal, and running 4-STABLE. Only time I had problems was when I left the squidgy pink thermal paste on the heatsink that made it overheat. Cleaning it off resulted in a stable system. Oh and as to load, it ran 10 consecutive buildworlds with -j4 as a test with no problems. Lawrence Farr EPC Direct Limited mailto:lawrence@epcdirect.co.uk T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 1:55:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dns.comrax.com (dns.comrax.com [194.90.246.124]) by hub.freebsd.org (Postfix) with ESMTP id 867A237B699 for ; Tue, 16 Jan 2001 01:55:06 -0800 (PST) Received: from NOOR (unknown [156.27.243.27]) by dns.comrax.com (Postfix) with SMTP id 1A9F672501 for ; Tue, 16 Jan 2001 11:55:02 +0200 (IST) From: "Noor Dawod" To: "FreeBSD-STABLE Mailing List" Subject: Threads and latest FreeBSD Date: Tue, 16 Jan 2001 11:53:57 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" 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.00.2919.6700 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, A while back, there were few threads about a known problem in FreeBSD (concerning threads, and affecting few programs, one is MySQL). To solve it, one had to compile the code in c++ and not gcc. I was wondering if this problem was resolved in the recent STABLE version, and if so, is there any other known problems when compiling MySQL? If the problem was not solved, is there an ET of fix? Thanks Noor P.S.: Please CC me on your replies. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 2: 0:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from matrix.42.org (matrix.42.org [194.246.250.200]) by hub.freebsd.org (Postfix) with ESMTP id 36A4F37B401; Tue, 16 Jan 2001 02:00:03 -0800 (PST) Received: (from sec@localhost) by matrix.42.org (8.8.8/8.8.5) id KAA01794 (sender ); Tue, 16 Jan 2001 10:59:46 +0100 (CET) Date: Tue, 16 Jan 2001 10:59:45 +0100 From: Stefan `Sec` Zehl To: Stephen Montgomery-Smith Cc: freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: disable mousepad taps on Dell Inspiron Message-ID: <20010116105945.A803@matrix.42.org> Mail-Followup-To: Stephen Montgomery-Smith , freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG References: <3A5FD090.E035557F@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A5FD090.E035557F@math.missouri.edu>; from stephen@math.missouri.edu on Fri, Jan 12, 2001 at 09:50:40PM -0600 I-love-doing-this: really X-Modeline: vim:set ts=8 sw=4 smarttab tw=72 si noic notitle: Accept-Languages: de, en X-URL: http://sec.42.org/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 12, 2001 at 09:50:40PM -0600, Stephen Montgomery-Smith wrote: > I have submitted another PR describing how to do this: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=24299 I wanted to disable the 'tap' functionality on my vaio laptop. After reading the moused-manpage I realized that it might be possible without hacking the psm source if my pad sends the tap as button 4 and tried moused -m 4=0 which works like a charm for me. I'm very happy now :) CU, Sec -- You haven't seen _multitasking_ until you have seen Doom and Quake run side by side. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 2:28:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.tripos.com (gatekeeper.tripos.com [192.160.145.62]) by hub.freebsd.org (Postfix) with ESMTP id 9A21F37B400 for ; Tue, 16 Jan 2001 02:27:54 -0800 (PST) Received: (from uucp@localhost) by tripos.com (8.8.8+Sun) id EAA05808; Tue, 16 Jan 2001 04:27:46 -0600 (CST) Received: from unknown(172.20.5.15) by gatekeeper.tripos.com via smap (V5.5) id xma005785; Tue, 16 Jan 01 04:27:42 -0600 Received: from wolf ([172.20.152.158]) by tripos.com (980919.SGI.STAND) via SMTP id EAA61179; Tue, 16 Jan 2001 04:27:29 -0600 (CST) From: "Steve Coles" To: "Herbert" , "FreeBSD-Stable" Subject: RE: Epox 8KTA2 Date: Tue, 16 Jan 2001 10:27:10 -0000 Message-ID: <017101c07fa6$e2a4e550$9e9814ac@wolf.tripos.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 In-Reply-To: <20010116005820.A797@freebsd2.rocks> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is my experience with Promise controllers (a torrid time indeed): Both the Promise Controllers you mention are recognised by FreeBSD. The Ultra-100 is reliable and compatible with all of my MOBOs - I have a selection of low-mid-range ( PCChips, GigaByte ), and ATA-66 and ATA-100 disks, using FreeBSD and WinNt. The FastTrak-100 has ~never~ been reliable across MOBOs and Disks - on NT and FreeBSD. I have tried flashing the BIOS ( most recent and dummy-bios ), different channel combinations, different drive combinations, different MOBOs... My experience with this controller is that if you use two fast disks at the same time, then one of them will time-out ( FreeBSD and WinNT )or there will be massive file-system corruption ( WinNT ). Only one MOBO, running with a bus-speed of 66Mhz worked reliably with multiple writers to a hardware/software stripe. The problem normally manifests itself as one of the disks attached to the controller just timing-out, this happens on WinNT and FreeBSD - only FreeBSD recovers more gracefully. WinNT appears to not reset the drive and just waits. Typical example: Last night I had a 32Mb AMD K2 450 ( wow !) machine with the Fastrak-100, with 3 disks. Using just the first (boot) disk (ATA-33) it had been building-world happily for weeks using CTM deltas of src-4, no problems, ad4 and ad5 were recognised but just not used. Then I switched /usr/src to /dev/ad4s1e and /usr/obj to /dev/ad5s1e - the FastTrak controlled drives As soon as I tried to do something using both ATA-100 disks I got read/write timeouts on one or the other disk. These timeouts were followed by spontaneous reboots. So I reloaded the machine from the 12-1-2001 stable snapshot and now there are just kernel panics. I couldn't even unpack the source ( I use CTM ) into /use/src without a panic. The panic was in a variety of functions, but most functions were named ffs_*. (Sorry for the level of detail, I have a 30-second memory) If it is a driver problem then I would like to help out, but I don't know whether it is the driver or controller, or MOBO. I'm tempted just to save the grey hairs and buy a new Mobo / ditch the FastTrak. I'm just fed up with this controller, so I would welcome ~any~ positive experiences using this controller with -STABLE and >1 ATA-100 disks so that I can reduce some of the variables and get a working configuration using this controller. Steve > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Herbert > Sent: 15 January 2001 23:58 > To: freebsd-questions@FreeBSD.ORG > Subject: Epox 8KTA2 > > > Hello! > > I have replaced a MSI K7T Pro2 mainboard with an Epox 8KTA72 today and > now I have problems running my FreeBSD-4.2 STABLE system. > The drives fall back from UDMA66 into PIO4 mode and the system is very > unstable. XWindow, netscape and other apps crash randomly and when I try > to compile the system or a kernel my kernel panics. :( > I testet this system under m$ win me I have no such problems? > > Is this only a problem with the ata controller? Or do you think I should > also check some other parts of my computer? What if I buy a promise ata > 100 controller? Will this solve my problems? There is a cheap one > available from promise (not the fastrak 100) ... is this one also > supported under FreeBSD 4.2 STABLE? Or only the Fastrak 100? > > My cdrom drive seems to run fine in UDMA33 mode ... strange, isn't it? > Hope anybody on the list can help me! Thanks a lot! > > Regards! > Herbert J. Skuhra > > > 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 Jan 16 2:35:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from oberon.tpgi.com.au (oberon.tpgi.com.au [203.12.160.2]) by hub.freebsd.org (Postfix) with ESMTP id 91C6537B400 for ; Tue, 16 Jan 2001 02:34:46 -0800 (PST) Received: (from smtpd@localhost) by oberon.tpgi.com.au (8.8.7/8.8.7) id VAA06573; Tue, 16 Jan 2001 21:34:36 +1100 Received: from buffy.tpgi.com.au(203.12.160.34) via SMTP by oberon.tpgi.com.au, id smtpda06516; Tue Jan 16 21:34:28 2001 Received: (from smtpd@localhost) by buffy.tpgi.com.au (8.9.3/8.9.3) id VAA06855; Tue, 16 Jan 2001 21:31:28 +1100 Received: from tar-56k-248.tpgi.com.au(203.26.26.248), claiming to be "tpgi.com.au" via SMTP by buffy.tpgi.com.au, id smtpdgFIddY; Tue Jan 16 21:31:19 2001 Message-ID: <3A642379.8D443367@tpgi.com.au> Date: Tue, 16 Jan 2001 21:33:30 +1100 From: eirvine X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Darrern Cc: freebsd-stable@FreeBSD.ORG Subject: Re: network lag References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Darrern, Darrern wrote: > > alright, not sure if this is the place for this, but no one seems to know > whats going on and I seem to have confused a lot of people. and we've questions@freebsd.org is probably more appropriate. > even sat down for 6 hours on irc trying to solve it one on one. I've > replaced connectors, etc.. just to clear up my network setup here it is: > > Windows Me:-----UTP----:HUB:----BNC----:FreeBSD:----BNC----:Win98 > > FreeBSD of course is my gateway. my FreeBSD machine has 2 ethernet cards. > one xl0 and one ed0. or 3comm and lynksys. 3com is the outside world, > lynksys is the internal lan. my problem is that at times when there is > absolutely no internal lan traffic I can't reach above 60kps between > 192.168.1.1(bsd) and 192.168.1.5(win me). I can't track the variable I > need to fix. I run natd, and routed(which hasn't helped fix the problem > yet). I have seen my internal net the way it is setup right now go as > high as 800kps. nothing is changed and I can't find the variable I need > to fix, anyone else experiencing this or have any idea how to fix it? OK. The most common cause of problems like this is incorrect duplexing. Unless all your hub is a switch, you probably want half duplex. So you want to make sure all the cards in the internal network are set to half duplex. I used to use a ms-dos utility for ed0 cards. If you've already done this, what is your ftp speed like? Eddie. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 2:37:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C1CD37B699 for ; Tue, 16 Jan 2001 02:37:09 -0800 (PST) Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 795A86E2AEF for ; Tue, 16 Jan 2001 02:36:25 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14ITJD-0000eM-00; Tue, 16 Jan 2001 13:25:50 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14IDz4-0000HZ-00; Mon, 15 Jan 2001 21:03:58 +0300 Date: Mon, 15 Jan 2001 21:03:58 +0300 From: Odhiambo Washington To: David Wagner Cc: FBSD-STABLE Subject: Re: Strange device probe behavior Message-ID: <20010115210358.A693@poeza.iconnect.co.ke> Mail-Followup-To: Odhiambo Washington , David Wagner , FBSD-STABLE References: <20010114122845.A400@poeza.iconnect.co.ke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from "David Wagner" on Sun, Jan 14, 2001 at 11:08:04AM -0500 X-Operating-System: FreeBSD poeza.iconnect.co.ke 4.2-STABLE FreeBSD 4.2-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * David Wagner [20010114 19:35]: writing on the subject 'Re: Strange device probe behavior' David> On Sun, 14 Jan 2001, Odhiambo Washington wrote: David> David> > atapci0: port 0x1860-0x186f at device David> > 4.1 on pci0 David> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ David> > This is where 15 or so seconds lapse before the probe continues!! David> David> Well, if it makes you feel any better, my system does this too. It has: David> David> atapci0: port 0x18a0-0x18af at device 7.1 David> on pci0 David> David> Mine's a Gateway system I bought a couple years ago and recently turned David> into a FreeBSD box. I've never noticed any problems with it -- once the David> probe continues everything seems to be fine. I certainly have no idea David> _why_ it does it, but at least it doesn't seem to be cause for panic. :) Well, and does your system end up detecting ata1 (or it doesn't exist in yours, maybe) ? Someone suspects that the 'momentary stall' at that stage could be s'thing to do with probe for ata1 (a couple others have it - I have it too on a clone that I run and no stall) but even a kernel compile without ata1 still yields no difference. TIA -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. Sooner or later I'm going to die, but I'm not going to retire. -Margaret Mead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 2:52:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clove.rp.lan (unknown [212.74.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 0558337B400; Tue, 16 Jan 2001 02:52:26 -0800 (PST) Received: (from dom@localhost) by clove.rp.lan (8.9.3/8.8.7) id KAA00331; Tue, 16 Jan 2001 10:51:56 GMT X-Authentication-Warning: clove.rp.lan: dom set sender to dom@semantico.com using -f Date: Tue, 16 Jan 2001 10:51:56 +0000 From: Dominic Mitchell To: Stefan `Sec` Zehl Cc: Stephen Montgomery-Smith , freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: disable mousepad taps on Dell Inspiron Message-ID: <20010116105156.A32711@semantico.com> References: <3A5FD090.E035557F@math.missouri.edu> <20010116105945.A803@matrix.42.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us In-Reply-To: <20010116105945.A803@matrix.42.org> X-Warning: Incoming message from The Big Giant Head! X-OS: Linux 2.2.13 i686 X-Uptime: 10:50am up 18 days, 22:10, 4 users, load average: 1.17, 1.19, 1.10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 16, 2001 at 10:59:45AM +0100, Stefan `Sec` Zehl wrote: > On Fri, Jan 12, 2001 at 09:50:40PM -0600, Stephen Montgomery-Smith wrote: > > I have submitted another PR describing how to do this: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=24299 > > I wanted to disable the 'tap' functionality on my vaio laptop. After > reading the moused-manpage I realized that it might be possible without > hacking the psm source if my pad sends the tap as button 4 and tried > > moused -m 4=0 > > which works like a charm for me. I'm very happy now :) How odd. My Vaio (Z600TEK) doesn't respond to taps at all unless I suspend and resume. Maybe I should play with the moused flags some more... -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 3: 5:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mgate11.so-net.ne.jp (mgate11.so-net.ne.jp [210.139.254.158]) by hub.freebsd.org (Postfix) with ESMTP id 0D32037B400 for ; Tue, 16 Jan 2001 03:04:57 -0800 (PST) Received: from mail.ya3.so-net.ne.jp (mspool11.so-net.ne.jp [210.139.248.11]) by mgate11.so-net.ne.jp (8.9.3/3.7W00122022) with ESMTP id UAA20195; Tue, 16 Jan 2001 20:02:25 +0900 (JST) Received: from localhost (p84ea8a.ykh2.ap.so-net.ne.jp [210.132.234.138]) by mail.ya3.so-net.ne.jp (8.9.3/3.7W99092111) with ESMTP id UAA12624; Tue, 16 Jan 2001 20:02:24 +0900 (JST) To: matusita@jp.FreeBSD.org Cc: stable@freebsd.org Subject: Re: Broken kern.flp? In-Reply-To: <20010116180609O.matusita@jp.FreeBSD.org> References: <20010116180609O.matusita@jp.FreeBSD.org> From: Yoshihiro Koya X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010116200501A.ipfw@ya3.so-net.ne.jp> Date: Tue, 16 Jan 2001 20:05:01 +0900 X-Dispatcher: imput version 990905(IM130) Lines: 16 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, > I've just got a report that current 4-stable's floppy image, kern.flp > is broken and it can't boot. Here is a sample session: I tried to boot from my kern.flp which was built on Jan 13. I didn't have any kind of problems. I was asked to insert mfsroot.flp as usual, and I saw the installer which works fine. The sources of that kern.flp was CVSup'd on Jan 12 or 13 from cvsup.jp.FreeBSD.org. # I had to make release on the last Sunday, because I have a machine # to be installed the latest 4-stable. koya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 3:28:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from reticent.troll.no (reticent.troll.no [213.203.59.28]) by hub.freebsd.org (Postfix) with SMTP id 645CE37B69D for ; Tue, 16 Jan 2001 03:28:34 -0800 (PST) Received: (qmail 55439 invoked by uid 1001); 16 Jan 2001 11:28:27 -0000 Content-Type: text/plain; charset="CP 1255" From: Bradley T.Hughes Organization: Trolltech AS To: "Noor Dawod" , "FreeBSD-STABLE Mailing List" Subject: Re: Threads and latest FreeBSD Date: Tue, 16 Jan 2001 12:28:27 +0100 X-Mailer: KMail [version 1.2] References: In-Reply-To: MIME-Version: 1.0 Message-Id: <01011612282703.32713@reticent.troll.no> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday 16 January 2001 10:53, Noor Dawod wrote: > Hello, > > A while back, there were few threads about a known problem in FreeBSD > (concerning threads, and affecting few programs, one is MySQL). To solve > it, one had to compile the code in c++ and not gcc. > > I was wondering if this problem was resolved in the recent STABLE > version, and if so, is there any other known problems when compiling > MySQL? If the problem was not solved, is there an ET of fix? The problem has been fixed. All of my threaded C++ programs work when compiled with a recent -STABLE. > Thanks > > Noor > > P.S.: Please CC me on your replies. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- -- Bradley T. Hughes Trolltech AS - Waldemar Thranes gt. 98B N-0175 Oslo, Norway Office: +47 21604892 Mobile: +47 92019781 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 4:19:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 8748937B69F for ; Tue, 16 Jan 2001 04:19:23 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 5E5EF31BA; Tue, 16 Jan 2001 12:19:21 +0000 (GMT) Date: Tue, 16 Jan 2001 12:19:21 +0000 From: Josef Karthauser To: stable@freebsd.org Subject: cdcontrol and environment vars - opinions please. Message-ID: <20010116121921.A632@tao.org.uk> Mail-Followup-To: Josef Karthauser , 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 X-Loop: FreeBSD.ORG How many people are using cdcontrol and defining the drive name using one of the following environment variables: MUSIC_CD, CD_DRIVE, DISC and CDPLAY? I've no idea why there are so many different options - it seems a bit daft to me. Recently we added another one: CDROM. What I'd like to do is deprecate use of the others and adopt CDROM as standard. My question to anyone using the others is whether you'd especially mind if cdcontrol still worked with the other env names, but complained a bit that CDROM should be used instead? Does this sound sensible? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 4:40:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id 36E9D37B6A4 for ; Tue, 16 Jan 2001 04:40:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.1+3.4W/8.11.1) with ESMTP/inet id f0GCeQ879996; Tue, 16 Jan 2001 21:40:26 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: stable@FreeBSD.ORG In-Reply-To: <20010116200501A.ipfw@ya3.so-net.ne.jp> References: <20010116180609O.matusita@jp.FreeBSD.org> <20010116180609O.matusita@jp.FreeBSD.org> <20010116200501A.ipfw@ya3.so-net.ne.jp> X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Persephone) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 11 From: Makoto MATSUSHITA To: Yoshihiro.Koya@math.yokohama-cu.ac.jp Subject: Re: Broken kern.flp? Date: Tue, 16 Jan 2001 21:40:06 +0900 Message-Id: <20010116214006X.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've already confirmed that kern.flp as of Jan/13/2001 works as it should be. Yoshihiro.Koya> I tried to boot from my kern.flp which was built on Jan 13. But you should know that today is Jan/16/2001. I've checked today's kern.flp image. Would you please check it again? -- - Makoto MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 4:52:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from brainy.ilsmart.com (brainy.ilsmart.com [206.175.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 5E7D137B6A0 for ; Tue, 16 Jan 2001 04:52:36 -0800 (PST) Received: from svr03.ilsmart.com (ilsinet.ilsmart.com [206.175.69.228]) by brainy.ilsmart.com (8.11.1/8.11.1) with ESMTP id f0GCqL261424 for ; Tue, 16 Jan 2001 06:52:22 -0600 (CST) Received: from NT2NOTES.ilsmart.com ([209.154.176.3]) by svr03.ilsmart.com (Lotus Domino Release 5.0.2c (Intl)) with ESMTP id 2001011606533855:40816 ; Tue, 16 Jan 2001 06:53:38 -0600 To: stable@FreeBSD.ORG Subject: Re: Broken kern.flp? X-Mailer: Lotus Notes Release 5.0.5 September 22, 2000 Message-ID: From: bgoering@ilsmart.com Date: Tue, 16 Jan 2001 06:53:32 -0600 X-MIMETrack: S/MIME Sign by Notes Client on Bill Goering/ILS(Release 5.0.5 |September 22, 2000) at 01/16/2001 06:52:17 AM, Serialize by Notes Client on Bill Goering/ILS(Release 5.0.5 |September 22, 2000) at 01/16/2001 06:52:17 AM, Serialize complete at 01/16/2001 06:52:17 AM, S/MIME Sign failed at 01/16/2001 06:52:17 AM: The cryptographic key was not found, Serialize by Router on NT2NOTES/ILS(Release 5.0.2c (Intl)|2 February 2000) at 01/16/2001 06:53:37 AM, Serialize complete at 01/16/2001 06:53:37 AM, Itemize by SMTP Server on ILSINET/ILS(Release 5.0.2c (Intl)|2 February 2000) at 01/16/2001 06:53:38 AM, Serialize by Router on ILSINET/ILS(Release 5.0.2c (Intl)|2 February 2000) at 01/16/2001 06:53:39 AM, Serialize complete at 01/16/2001 06:53:39 AM MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I experienced this yesterday with the Jan/15/2001 kern.flp also... Bill Goering Makoto MATSUSHITA Sent by: owner-freebsd-stable@FreeBSD.ORG 01/16/2001 06:40 AM To: Yoshihiro.Koya@math.yokohama-cu.ac.jp cc: stable@FreeBSD.ORG Subject: Re: Broken kern.flp? I've already confirmed that kern.flp as of Jan/13/2001 works as it should be. Yoshihiro.Koya> I tried to boot from my kern.flp which was built on Jan 13. But you should know that today is Jan/16/2001. I've checked today's kern.flp image. Would you please check it again? -- - Makoto MATSUSHITA 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 Jan 16 4:54:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clove.rp.lan (unknown [212.74.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 967CB37B401 for ; Tue, 16 Jan 2001 04:54:27 -0800 (PST) Received: (from dom@localhost) by clove.rp.lan (8.9.3/8.8.7) id MAA11028; Tue, 16 Jan 2001 12:54:25 GMT X-Authentication-Warning: clove.rp.lan: dom set sender to dom@semantico.com using -f Date: Tue, 16 Jan 2001 12:54:25 +0000 From: Dominic Mitchell To: Josef Karthauser Cc: stable@FreeBSD.ORG Subject: Re: cdcontrol and environment vars - opinions please. Message-ID: <20010116125425.A10823@semantico.com> References: <20010116121921.A632@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us In-Reply-To: <20010116121921.A632@tao.org.uk> X-Warning: Incoming message from The Big Giant Head! X-OS: Linux 2.2.13 i686 X-Uptime: 12:52pm up 19 days, 12 min, 4 users, load average: 0.17, 0.60, 0.97 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 16, 2001 at 12:19:21PM +0000, Josef Karthauser wrote: > How many people are using cdcontrol and defining the drive name > using one of the following environment variables: MUSIC_CD, CD_DRIVE, > DISC and CDPLAY? > > I've no idea why there are so many different options - it seems a > bit daft to me. > > Recently we added another one: CDROM. What I'd like to do is > deprecate use of the others and adopt CDROM as standard. > > My question to anyone using the others is whether you'd especially > mind if cdcontrol still worked with the other env names, but > complained a bit that CDROM should be used instead? > > Does this sound sensible? Damned right. I was totally confused the last time that I looked at it. Are there any other programs in the tree which should be changed to fall into line? I can't think of any off hand, but there may be some. Also, what precedent do various ports set? I'm sure that xmcd has it's own list of variables that it uses... -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 5: 8:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.sanda.gr.jp (ns.sanda.gr.jp [210.232.122.18]) by hub.freebsd.org (Postfix) with ESMTP id AAE8837B401 for ; Tue, 16 Jan 2001 05:08:36 -0800 (PST) Received: from ever.sanda.gr.jp (epoch [10.93.63.51]) by ns.sanda.gr.jp (8.9.3/3.7W) with ESMTP id WAA05343 for ; Tue, 16 Jan 2001 22:08:34 +0900 (JST) From: non@ever.sanda.gr.jp Received: from localhost (localhost [127.0.0.1]) by ever.sanda.gr.jp (8.8.8/3.3W9) with ESMTP id WAA27551 for ; Tue, 16 Jan 2001 22:08:33 +0900 (JST) To: stable@FreeBSD.org Subject: Geometry transrated IDE HDD with ad driver X-Mailer: Mew version 1.94 on Emacs 19.28 / Mule 2.3 =?iso-2022-jp?B?KBskQkt2RSYyVhsoQik=?= Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010116220833I.non@ever.sanda.gr.jp> Date: Tue, 16 Jan 2001 22:08:33 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 20 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a notebook which the geometry of HDD in BIOS is not compatible with the one on the HDD. I could install 4.2-stable without a problem, but after installation at boot up I got the message like, Mounting root from ufs:/dev/ad0s1a ad0s1: type 0xa5 start 62, end = 333143, size 333081 : OK ad0: cannot find label (no disk label) ad0s1: cannot find label (no disk label) Root mount failed: 22 Manual root filesystem specification: : With the wd driver and changes in /etc/fstab, I could boot with geometry transration. I also heard that some guy had same kind of trouble with Digital Hinote. He didn't try wd driver. Any suggestion to use ad driver ? // Noriaki Mitsunaga // To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 6:14:28 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 BFDFF37B401 for ; Tue, 16 Jan 2001 06:14:10 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA37326; Tue, 16 Jan 2001 15:14:03 +0100 (CET) (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: Josef Karthauser Cc: stable@FreeBSD.ORG Subject: Re: cdcontrol and environment vars - opinions please. References: <20010116121921.A632@tao.org.uk> From: Dag-Erling Smorgrav Date: 16 Jan 2001 15:14:03 +0100 In-Reply-To: Josef Karthauser's message of "Tue, 16 Jan 2001 12:19:21 +0000" Message-ID: Lines: 22 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser writes: > How many people are using cdcontrol and defining the drive name > using one of the following environment variables: MUSIC_CD, CD_DRIVE, > DISC and CDPLAY? > > I've no idea why there are so many different options - it seems a > bit daft to me. > > Recently we added another one: CDROM. What I'd like to do is > deprecate use of the others and adopt CDROM as standard. Heh - I'm the one who added suport for $CDROM, and I had no idea the others were supported - $CDROM was so self-evident (think of $TAPE, used by pax(1), mt(1), tar(1), dump(8) and restore(8)) that it didn't occur to me to check if it already supported other variables (plus, they weren't documented). I totally agree with the idea of deprecating all but $CDROM. 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 Tue Jan 16 6:54:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id EDDE937B401 for ; Tue, 16 Jan 2001 06:54:38 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id E78D83222; Tue, 16 Jan 2001 14:54:34 +0000 (GMT) Date: Tue, 16 Jan 2001 14:54:34 +0000 From: Josef Karthauser To: Dag-Erling Smorgrav Cc: stable@FreeBSD.ORG Subject: Re: cdcontrol and environment vars - opinions please. Message-ID: <20010116145434.B3073@tao.org.uk> Mail-Followup-To: Josef Karthauser , Dag-Erling Smorgrav , stable@FreeBSD.ORG References: <20010116121921.A632@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Tue, Jan 16, 2001 at 03:14:03PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 16, 2001 at 03:14:03PM +0100, Dag-Erling Smorgrav wrote: > Josef Karthauser writes: > > How many people are using cdcontrol and defining the drive name > > using one of the following environment variables: MUSIC_CD, CD_DRIVE, > > DISC and CDPLAY? > > > > I've no idea why there are so many different options - it seems a > > bit daft to me. > > > > Recently we added another one: CDROM. What I'd like to do is > > deprecate use of the others and adopt CDROM as standard. > > Heh - I'm the one who added suport for $CDROM, and I had no idea the > others were supported - $CDROM was so self-evident (think of $TAPE, > used by pax(1), mt(1), tar(1), dump(8) and restore(8)) that it didn't > occur to me to check if it already supported other variables (plus, > they weren't documented). I thought that they weren't also, (I even added CDROM to the man page without noticing the others ;). In fact they're described in the second paragraph! :). Joe > > I totally agree with the idea of deprecating all but $CDROM. > > 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 Tue Jan 16 6:59:35 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 9A4CB37B400 for ; Tue, 16 Jan 2001 06:59:17 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA37521; Tue, 16 Jan 2001 15:59:11 +0100 (CET) (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: Josef Karthauser Cc: stable@FreeBSD.ORG Subject: Re: cdcontrol and environment vars - opinions please. References: <20010116121921.A632@tao.org.uk> <20010116145434.B3073@tao.org.uk> From: Dag-Erling Smorgrav Date: 16 Jan 2001 15:59:11 +0100 In-Reply-To: Josef Karthauser's message of "Tue, 16 Jan 2001 14:54:34 +0000" Message-ID: Lines: 10 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser writes: > I thought that they weren't also, (I even added CDROM to the man page > without noticing the others ;). In fact they're described in the second > paragraph! :). Well, here's to standardizing the man page layout... 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 Tue Jan 16 7:11: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42]) by hub.freebsd.org (Postfix) with ESMTP id 3350C37B401 for ; Tue, 16 Jan 2001 07:10:45 -0800 (PST) Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net) by dfw-smtpout2.email.verio.net with esmtp id 14IXks-0002lt-00; Tue, 16 Jan 2001 15:10:38 +0000 Received: from [168.143.2.191] (helo=leviathan.clark.net) by dfw-mmp4.email.verio.net with esmtp id 14IXkq-00002U-00; Tue, 16 Jan 2001 15:10:36 +0000 Message-Id: <5.0.2.1.2.20010116100905.00a69e30@mail.clark.net> X-Sender: thomas@mail.clark.net X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 16 Jan 2001 10:11:37 -0500 To: Dag-Erling Smorgrav , Josef Karthauser From: Mark Thomas Subject: Re: cdcontrol and environment vars - opinions please. Cc: stable@FreeBSD.ORG In-Reply-To: References: <20010116121921.A632@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:14 PM 1/16/01 +0100, Dag-Erling Smorgrav wrote: >Josef Karthauser writes: >> How many people are using cdcontrol and defining the drive name >> using one of the following environment variables: MUSIC_CD, CD_DRIVE, >> DISC and CDPLAY? >> >> I've no idea why there are so many different options - it seems a >> bit daft to me. >> >> Recently we added another one: CDROM. What I'd like to do is >> deprecate use of the others and adopt CDROM as standard. > >Heh - I'm the one who added suport for $CDROM, and I had no idea the >others were supported - $CDROM was so self-evident (think of $TAPE, >used by pax(1), mt(1), tar(1), dump(8) and restore(8)) that it didn't >occur to me to check if it already supported other variables (plus, >they weren't documented). > >I totally agree with the idea of deprecating all but $CDROM. To be picky, CD-ROM is not equal to CD-DA. I don't know if it really matters though. Mark --- thomas@clark.net ---> http://www.clark.net/pub/thomas PBEM Eldritch --------> http://www.pbegames.com [TM4463-ORG] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 7:17:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id BA71737B402 for ; Tue, 16 Jan 2001 07:16:59 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id DF926323F; Tue, 16 Jan 2001 15:16:54 +0000 (GMT) Date: Tue, 16 Jan 2001 15:16:54 +0000 From: Josef Karthauser To: Mark Thomas Cc: Dag-Erling Smorgrav , stable@FreeBSD.ORG Subject: Re: cdcontrol and environment vars - opinions please. Message-ID: <20010116151654.C3073@tao.org.uk> Mail-Followup-To: Josef Karthauser , Mark Thomas , Dag-Erling Smorgrav , stable@FreeBSD.ORG References: <5.0.2.1.2.20010116100905.00a69e30@mail.clark.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.2.1.2.20010116100905.00a69e30@mail.clark.net>; from thomas@clark.net on Tue, Jan 16, 2001 at 10:11:37AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 16, 2001 at 10:11:37AM -0500, Mark Thomas wrote: > At 03:14 PM 1/16/01 +0100, Dag-Erling Smorgrav wrote: > >Josef Karthauser writes: > >> How many people are using cdcontrol and defining the drive name > >> using one of the following environment variables: MUSIC_CD, CD_DRIVE, > >> DISC and CDPLAY? > >> > >> I've no idea why there are so many different options - it seems a > >> bit daft to me. > >> > >> Recently we added another one: CDROM. What I'd like to do is > >> deprecate use of the others and adopt CDROM as standard. > > > >Heh - I'm the one who added suport for $CDROM, and I had no idea the > >others were supported - $CDROM was so self-evident (think of $TAPE, > >used by pax(1), mt(1), tar(1), dump(8) and restore(8)) that it didn't > >occur to me to check if it already supported other variables (plus, > >they weren't documented). > > > >I totally agree with the idea of deprecating all but $CDROM. > > To be picky, CD-ROM is not equal to CD-DA. I don't know if it really matters though. Not at this point I would think. Most DVD style drives also support CD operations :), and it's not as if the CD is going to disappear over night. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 7:24:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id E8D7537B699 for ; Tue, 16 Jan 2001 07:23:44 -0800 (PST) Received: by arg1.demon.co.uk (Postfix, from userid 300) id 2E0269B17; Tue, 16 Jan 2001 15:23:40 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by arg1.demon.co.uk (Postfix) with ESMTP id 24C835D15 for ; Tue, 16 Jan 2001 15:23:40 +0000 (GMT) Date: Tue, 16 Jan 2001 15:23:40 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: freebsd-stable@freebsd.org Subject: Vinum incidents. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a server with 5 identical SCSI drives, arranged as a single RAID-5 volume using vinum (and softupdates). This is exported with NFS/Samba/Netatalk/Econet to clients of various types; the root,usr,var partitions are on a small IDE drive (there are no local users or application processes). The machine has a serial console. This has been working reliably for a couple of months, running -stable from around the time of 4.2-release. On 1st January, I took advantage of the low load to do an upgrade to the latest -stable. Since then, there have been two incidents (probably not in fact related to the upgrade) where vinum has not behaved as expected: 1) Phantom disc error --------------------- Vinum logged: Jan 2 01:59:26 serv20 /kernel: home.p0.s0: fatal write I/O error Jan 2 01:59:26 serv20 /kernel: vinum: home.p0.s0 is stale by force Jan 2 01:59:26 serv20 /kernel: vinum: home.p0 is degraded However, there was no evidence of any actual disc error - nothing was logged on the console, in dmesg or any other log files. The system would have been substantially idle at that time of night, except that the daily cron jobs would just been starting at that time. A "vinum start home.p0.s0" some time later successfully revived the plex and the system then ran uninterrupted for two weeks. Does this suggest some sort of out-of-range block number bug somewhere? 2) Recovery problems -------------------- This morning, a technician accidentally(!) unplugged the cable between the SCSI card and the drive enclosure while the system was busy. The console showed a series of SCSI errors, culminating in a panic. Although it is configured to dump to the IDE drive, no dump was saved (possibly due to someone locally pressing the reset button). In any case, this panic was probably not very interesting. On reboot, it failed automatic fsck due to unexpected softupdates inconstencies, but a manual fsck worked OK with only a modest number of incorrect block count/unref file errors, but a huge number of "allocated block/frag marked free" errors. A second fsck produced no errors, so I mounted the filesystem and continued. Sometime during this, the following occurred: (da3:ahc0:0:3:0): READ(10). CDB: 28 0 0 22 1d d6 0 0 2 0 (da3:ahc0:0:3:0): MEDIUM ERROR info:221dd6 asc:11,0 (da3:ahc0:0:3:0): Unrecovered read error sks:80,35 Jan 16 09:17:40 serv20 /kernel: home.p0.s3: fatal read I/O error Jan 16 09:17:40 serv20 /kernel: vinum: home.p0.s3 is crashed by force Jan 16 09:17:40 serv20 /kernel: vinum: home.p0 is degraded (da3:ahc0:0:3:0): READ(10). CDB: 28 0 0 22 8 3a 0 0 2 0 (da3:ahc0:0:3:0): MEDIUM ERROR info:22083a asc:11,0 (da3:ahc0:0:3:0): Unrecovered read error sks:80,35 Jan 16 09:17:41 serv20 /kernel: home.p0.s3: fatal read I/O error Jan 16 09:17:42 serv20 /kernel: vinum: home.p0.s3 is stale by force These were real errors (reproducible by reading from da3s1a with 'dd'), so I fixed them by writing zeros over most of the drive, and verified by dd-ing /dev/da3s1a to /dev/null. Since this now read OK, I tried to revive the subdisk with "vinum start home.p0.s3". Vinum reported that it was reviving, then reported all the working drives "crashed by force", and the machine locked solid (no panic or dump, required the reset button). Jan 16 09:48:28 serv20 /kernel: vinum: drive drive3 is up Jan 16 09:48:46 serv20 /kernel: vinum: home.p0.s0 is crashed by force Jan 16 09:48:46 serv20 /kernel: vinum: home.p0 is corrupt Jan 16 09:48:46 serv20 /kernel: vinum: home.p0.s1 is crashed by force Jan 16 09:48:46 serv20 /kernel: vinum: home.p0.s2 is crashed by force Jan 16 09:48:46 serv20 /kernel: vinum: home.p0.s4 is crashed by force Jan 16 09:48:46 serv20 /kernel: vinum: home.p0 is faulty Jan 16 09:48:46 serv20 /kernel: vinum: home is down On reboot, the vinum volume was broken: vinum: /dev is mounted read-only, not rebuilding /dev/vinum Warning: defective objects V home State: down Plexes: 1 Size: 68 GB P home.p0 R5 State: faulty Subdisks: 5 Size: 68 GB S home.p0.s0 State: crashed PO: 0 B Size: 17 GB S home.p0.s1 State: crashed PO: 512 kB Size: 17 GB S home.p0.s2 State: crashed PO: 1024 kB Size: 17 GB S home.p0.s3 State: R 0% PO: 1536 kB Size: 17 GB *** Start home.p0.s3 with 'start' command *** S home.p0.s4 State: crashed PO: 2048 kB Size: 17 GB I used 'vinum start' on home.p0.s[0124], and the plex came back in degraded mode; after fsck it mounted OK. On booting to multi-user mode, I noticed that all the drives were marked as 'down', even though the volume and most of the subdisks were 'up' (and a quick check in the console scroll-back showed that it was also in this state before the previous attempt to revive: vinum -> l 5 drives: D drive0 State: down Device /dev/da0s1a Avail: 0/17500 MB (0%) D drive1 State: down Device /dev/da1s1a Avail: 0/17500 MB (0%) D drive2 State: down Device /dev/da2s1a Avail: 0/17500 MB (0%) D drive3 State: down Device /dev/da3s1a Avail: 0/17500 MB (0%) D drive4 State: down Device /dev/da4s1a Avail: 0/17500 MB (0%) 1 volumes: V home State: up Plexes: 1 Size: 68 GB 1 plexes: P home.p0 R5 State: degraded Subdisks: 5 Size: 68 GB 5 subdisks: S home.p0.s0 State: up PO: 0 B Size: 17 GB S home.p0.s1 State: up PO: 512 kB Size: 17 GB S home.p0.s2 State: up PO: 1024 kB Size: 17 GB S home.p0.s3 State: R 0% PO: 1536 kB Size: 17 GB *** Start home.p0.s3 with 'start' command *** S home.p0.s4 State: up PO: 2048 kB Size: 17 GB This time, I used 'vinum start' on drive[0-4] before doing vinum start on home.p0.s3, and this time it successfully revived, taking 10 minutes or so. Some minutes later, the machine paniced (this time saving a dump): IdlePTD 3166208 initial pcb at 282400 panicstr: softdep_lock: locking against myself panic messages: --- panic: softdep_setup_inomapdep: found inode (kgdb) where #0 0xc014dd1a in dumpsys () #1 0xc014db3b in boot () #2 0xc014deb8 in poweroff_wait () #3 0xc01e6b49 in acquire_lock () #4 0xc01eae02 in softdep_fsync_mountdev () #5 0xc01eef0e in ffs_fsync () #6 0xc01edc16 in ffs_sync () #7 0xc017b42b in sync () #8 0xc014d916 in boot () #9 0xc014deb8 in poweroff_wait () #10 0xc01e792c in softdep_setup_inomapdep () #11 0xc01e44a4 in ffs_nodealloccg () #12 0xc01e352b in ffs_hashalloc () #13 0xc01e3186 in ffs_valloc () #14 0xc01f4e6f in ufs_makeinode () #15 0xc01f2824 in ufs_create () #16 0xc01f5029 in ufs_vnoperate () #17 0xc01b1e43 in nfsrv_create () #18 0xc01c6b2e in nfssvc_nfsd () #19 0xc01c6483 in nfssvc () #20 0xc022b949 in syscall2 () #21 0xc02207b5 in Xint0x80_syscall () #22 0x8048135 in ?? () After this reboot (again requiring manual fsck) the system appears to be working normally, but again the drives are all marked 'down': serv20[arg]% vinum l 5 drives: D drive0 State: down Device /dev/da0s1a Avail: 0/17500 MB(0%) D drive1 State: down Device /dev/da1s1a Avail: 0/17500 MB(0%) D drive2 State: down Device /dev/da2s1a Avail: 0/17500 MB(0%) D drive3 State: down Device /dev/da3s1a Avail: 0/17500 MB(0%) D drive4 State: down Device /dev/da4s1a Avail: 0/17500 MB(0%) 1 volumes: V home State: up Plexes: 1 Size: 68 GB 1 plexes: P home.p0 R5 State: up Subdisks: 5 Size: 68 GB 5 subdisks: S home.p0.s0 State: up PO: 0 B Size: 17 GB S home.p0.s1 State: up PO: 512 kB Size: 17 GB S home.p0.s2 State: up PO: 1024 kB Size: 17 GB S home.p0.s3 State: up PO: 1536 kB Size: 17 GB S home.p0.s4 State: up PO: 2048 kB Size: 17 GB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 7:57: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pro.fais.net (mail.fais.net [208.249.141.254]) by hub.freebsd.org (Postfix) with ESMTP id 6B79937B698 for ; Tue, 16 Jan 2001 07:56:47 -0800 (PST) Received: from drnet.fais.net (root@drnet.fais.net [208.249.141.246]) by pro.fais.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id KAA01296 for ; Tue, 16 Jan 2001 10:40:21 -0600 Received: from wks01.drnet.fais.net (wks01.drnet.fais.net [10.0.0.10]) by drnet.fais.net (8.11.0/8.11.0) with SMTP id f0GFuYw51879 for ; Tue, 16 Jan 2001 09:56:39 -0600 (CST) (envelope-from jwpauler@jwpages.com) From: "Justin W. Pauler" Reply-To: jwpauler@jwpages.com Date: Tue, 16 Jan 2001 09:56:32 -0600 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" To: freebsd-stable@freebsd.org Subject: mdoc MIME-Version: 1.0 Message-Id: <01011609563201.98287@wks01.drnet.fais.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've noticed alot of committs over the last hours of mdoc stuff, like man -> mdoc and such. Can someone explain what mdoc is and what is happening to the man pages? -- jwp -- Justin W. Pauler FlexiShell Internet Services E-Mail: jwpauler@jwpages.com WWW: http://www.jwpages.com IRC: drnet@#EggDrop, Undernet IRC Network ----------------------------------------------------------------------- I must have slipped a disk -- my pack hurts To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 8: 8: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id 10B3137B401 for ; Tue, 16 Jan 2001 08:07:46 -0800 (PST) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0GG7iq14900 for ; Tue, 16 Jan 2001 17:07:44 +0100 (CET) Received: from rose.lpthe.jussieu.fr (root@[134.157.10.102]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0GG7i300242 for ; Tue, 16 Jan 2001 17:07:44 +0100 (MET) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.11.1/8.11.1) id f0GG7i801208 for freebsd-stable@FreeBSD.ORG; Tue, 16 Jan 2001 17:07:44 +0100 (CET) (envelope-from michel) Date: Tue, 16 Jan 2001 17:07:43 +0100 From: Michel Talon To: FBSD-STABLE Subject: Re: Strange device probe behavior Message-ID: <20010116170743.A1189@lpthe.jussieu.fr> Mail-Followup-To: FBSD-STABLE References: <20010114122845.A400@poeza.iconnect.co.ke> <20010115210358.A693@poeza.iconnect.co.ke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20010115210358.A693@poeza.iconnect.co.ke> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 09:03:58PM +0300, Odhiambo Washington wrote: > * David Wagner [20010114 19:35]: writing on the subject 'Re: Strange device probe behavior' > David> On Sun, 14 Jan 2001, Odhiambo Washington wrote: > David> > David> > atapci0: port 0x1860-0x186f at device > David> > 4.1 on pci0 > David> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > David> > This is where 15 or so seconds lapse before the probe continues!! > David> > David> Well, if it makes you feel any better, my system does this too. It has: > David> > David> atapci0: port 0x18a0-0x18af at device 7.1 > David> on pci0 > David> > David> Mine's a Gateway system I bought a couple years ago and recently turned > David> into a FreeBSD box. I've never noticed any problems with it -- once the > David> probe continues everything seems to be fine. I certainly have no idea > David> _why_ it does it, but at least it doesn't seem to be cause for panic. :) > > Well, and does your system end up detecting ata1 (or it doesn't exist in > yours, maybe) ? Someone suspects that the 'momentary stall' at that > stage could be s'thing to do with probe for ata1 (a couple others have > it - I have it too on a clone that I run and no stall) but even a kernel > compile without ata1 still yields no difference. I have also this stall problem on a 3 years old machine using an Asus P2L97 mobo. It has an IDE disk on first ata channel and an atapi cdrom on the second one, plus a SCSI disk. There is a ~ 30s delay at boot probing the ata controller. This never occured under 3.* and began with 4.0 I have emailed the info to S.S. but the "bug" was never solved. Here are the relevant dmesg lines: atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 1222MB [2484/16/63] at ata0-master WDMA2 acd0: CDROM at ata1-master using PIO3 There are also some ata resetting messages in the logs but not much and they seem innocuous. -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 8:17:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hunterftp.hunter.com (hunterftp.hunter.com [128.242.141.2]) by hub.freebsd.org (Postfix) with ESMTP id 4E07937B404 for ; Tue, 16 Jan 2001 08:16:59 -0800 (PST) Received: from mailbox.hunter.com (mailbox.hunter.com [10.2.1.21]) by hunterftp.hunter.com (8.11.1/8.11.1) with ESMTP id f0GGGUo70698; Tue, 16 Jan 2001 10:16:30 -0600 (CST) (envelope-from KHamilton@Hunter.COM) Received: by mailbox.Hunter.COM with Internet Mail Service (5.5.2650.21) id ; Tue, 16 Jan 2001 10:16:30 -0600 Message-ID: <508F01B47A2BD411844500A0C9C83B440B6F44@mailbox.Hunter.COM> From: "Hamilton, Kent" To: "'Andrew Gordon'" Cc: "'freebsd-stable@freebsd.org'" Subject: RE: Vinum incidents. Date: Tue, 16 Jan 2001 10:16:28 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen both of these problems on my home system as well. If someone has a solution I'd love to hear about it. My system is a Dual P-III 500 with two Adaptec controllers, 4 Seagate Barracuda 9Gb disks, Vinum RAID-5 and softupdates. A Futitsu 2Gb standalone, a CD-RW, a CD-ROM a DVD-Writer, and a HP Tape drive are also on the SCSI busses. > -----Original Message----- > From: Andrew Gordon [mailto:arg@arg1.demon.co.uk] > Sent: Tuesday, January 16, 2001 9:24 AM > To: freebsd-stable@FreeBSD.ORG > Subject: Vinum incidents. > > > > I have a server with 5 identical SCSI drives, arranged as a > single RAID-5 > volume using vinum (and softupdates). This is exported with > NFS/Samba/Netatalk/Econet to clients of various types; the > root,usr,var > partitions are on a small IDE drive (there are no local users or > application processes). The machine has a serial console. > > This has been working reliably for a couple of months, running -stable > from around the time of 4.2-release. On 1st January, I took > advantage of > the low load to do an upgrade to the latest -stable. > > Since then, there have been two incidents (probably not in > fact related to > the upgrade) where vinum has not behaved as expected: > > 1) Phantom disc error > --------------------- > > Vinum logged: > > Jan 2 01:59:26 serv20 /kernel: home.p0.s0: fatal write I/O error > Jan 2 01:59:26 serv20 /kernel: vinum: home.p0.s0 is stale by force > Jan 2 01:59:26 serv20 /kernel: vinum: home.p0 is degraded > > However, there was no evidence of any actual disc error - nothing was > logged on the console, in dmesg or any other log files. The > system would > have been substantially idle at that time of night, except > that the daily > cron jobs would just been starting at that time. > > A "vinum start home.p0.s0" some time later successfully > revived the plex > and the system then ran uninterrupted for two weeks. > > Does this suggest some sort of out-of-range block number bug > somewhere? > > 2) Recovery problems > -------------------- > > This morning, a technician accidentally(!) unplugged the > cable between the > SCSI card and the drive enclosure while the system was busy. > The console > showed a series of SCSI errors, culminating in a panic. > Although it is > configured to dump to the IDE drive, no dump was saved > (possibly due to > someone locally pressing the reset button). In any case, > this panic was > probably not very interesting. > > On reboot, it failed automatic fsck due to unexpected softupdates > inconstencies, but a manual fsck worked OK with only a modest > number of > incorrect block count/unref file errors, but a huge number of > "allocated > block/frag marked free" errors. A second fsck produced no > errors, so I > mounted the filesystem and continued. > > Sometime during this, the following occurred: > > (da3:ahc0:0:3:0): READ(10). CDB: 28 0 0 22 1d d6 0 0 2 0 > (da3:ahc0:0:3:0): MEDIUM ERROR info:221dd6 asc:11,0 > (da3:ahc0:0:3:0): Unrecovered read error sks:80,35 > Jan 16 09:17:40 serv20 /kernel: home.p0.s3: fatal read I/O error > Jan 16 09:17:40 serv20 /kernel: vinum: home.p0.s3 is > crashed by force > Jan 16 09:17:40 serv20 /kernel: vinum: home.p0 is degraded > (da3:ahc0:0:3:0): READ(10). CDB: 28 0 0 22 8 3a 0 0 2 0 > (da3:ahc0:0:3:0): MEDIUM ERROR info:22083a asc:11,0 > (da3:ahc0:0:3:0): Unrecovered read error sks:80,35 > Jan 16 09:17:41 serv20 /kernel: home.p0.s3: fatal read I/O error > Jan 16 09:17:42 serv20 /kernel: vinum: home.p0.s3 is stale by force > > These were real errors (reproducible by reading from da3s1a > with 'dd'), so > I fixed them by writing zeros over most of the drive, and verified by > dd-ing /dev/da3s1a to /dev/null. Since this now read OK, I tried to > revive the subdisk with "vinum start home.p0.s3". Vinum > reported that it > was reviving, then reported all the working drives "crashed > by force", and > the machine locked solid (no panic or dump, required the > reset button). > > Jan 16 09:48:28 serv20 /kernel: vinum: drive drive3 is up > Jan 16 09:48:46 serv20 /kernel: vinum: home.p0.s0 is crashed by force > Jan 16 09:48:46 serv20 /kernel: vinum: home.p0 is corrupt > Jan 16 09:48:46 serv20 /kernel: vinum: home.p0.s1 is crashed by force > Jan 16 09:48:46 serv20 /kernel: vinum: home.p0.s2 is crashed by force > Jan 16 09:48:46 serv20 /kernel: vinum: home.p0.s4 is crashed by force > Jan 16 09:48:46 serv20 /kernel: vinum: home.p0 is faulty > Jan 16 09:48:46 serv20 /kernel: vinum: home is down > > > On reboot, the vinum volume was broken: > > vinum: /dev is mounted read-only, not rebuilding /dev/vinum > Warning: defective objects > > V home State: down Plexes: 1 Size: > 68 GB > P home.p0 R5 State: faulty Subdisks: 5 Size: > 68 GB > S home.p0.s0 State: crashed PO: 0 B Size: > 17 GB > S home.p0.s1 State: crashed PO: 512 kB Size: > 17 GB > S home.p0.s2 State: crashed PO: 1024 kB Size: > 17 GB > S home.p0.s3 State: R 0% PO: 1536 kB Size: > 17 GB > *** Start home.p0.s3 with 'start' command *** > S home.p0.s4 State: crashed PO: 2048 kB Size: > 17 GB > > I used 'vinum start' on home.p0.s[0124], and the plex came back in > degraded mode; after fsck it mounted OK. > > On booting to multi-user mode, I noticed that all the drives > were marked > as 'down', even though the volume and most of the subdisks > were 'up' (and > a quick check in the console scroll-back showed that it was > also in this > state before the previous attempt to revive: > > vinum -> l > 5 drives: > D drive0 State: down Device /dev/da0s1a Avail: > 0/17500 MB (0%) > D drive1 State: down Device /dev/da1s1a Avail: > 0/17500 MB (0%) > D drive2 State: down Device /dev/da2s1a Avail: > 0/17500 MB (0%) > D drive3 State: down Device /dev/da3s1a Avail: > 0/17500 MB (0%) > D drive4 State: down Device /dev/da4s1a Avail: > 0/17500 MB (0%) > 1 volumes: > V home State: up Plexes: 1 Size: 68 GB > 1 plexes: > P home.p0 R5 State: degraded Subdisks: 5 Size: 68 GB > 5 subdisks: > S home.p0.s0 State: up PO: 0 B Size: 17 GB > S home.p0.s1 State: up PO: 512 kB Size: 17 GB > S home.p0.s2 State: up PO: 1024 kB Size: 17 GB > S home.p0.s3 State: R 0% PO: 1536 kB Size: 17 GB > *** Start home.p0.s3 with 'start' command *** > S home.p0.s4 State: up PO: 2048 kB Size: 17 GB > > > This time, I used 'vinum start' on drive[0-4] before doing > vinum start on > home.p0.s3, and this time it successfully revived, taking 10 > minutes or > so. Some minutes later, the machine paniced (this time > saving a dump): > > IdlePTD 3166208 > initial pcb at 282400 > panicstr: softdep_lock: locking against myself > panic messages: > --- > panic: softdep_setup_inomapdep: found inode > (kgdb) where > #0 0xc014dd1a in dumpsys () > #1 0xc014db3b in boot () > #2 0xc014deb8 in poweroff_wait () > #3 0xc01e6b49 in acquire_lock () > #4 0xc01eae02 in softdep_fsync_mountdev () > #5 0xc01eef0e in ffs_fsync () > #6 0xc01edc16 in ffs_sync () > #7 0xc017b42b in sync () > #8 0xc014d916 in boot () > #9 0xc014deb8 in poweroff_wait () > #10 0xc01e792c in softdep_setup_inomapdep () > #11 0xc01e44a4 in ffs_nodealloccg () > #12 0xc01e352b in ffs_hashalloc () > #13 0xc01e3186 in ffs_valloc () > #14 0xc01f4e6f in ufs_makeinode () > #15 0xc01f2824 in ufs_create () > #16 0xc01f5029 in ufs_vnoperate () > #17 0xc01b1e43 in nfsrv_create () > #18 0xc01c6b2e in nfssvc_nfsd () > #19 0xc01c6483 in nfssvc () > #20 0xc022b949 in syscall2 () > #21 0xc02207b5 in Xint0x80_syscall () > #22 0x8048135 in ?? () > > After this reboot (again requiring manual fsck) the system > appears to be > working normally, but again the drives are all marked 'down': > > serv20[arg]% vinum l > 5 drives: > D drive0 State: down Device /dev/da0s1a Avail: > 0/17500 MB(0%) > D drive1 State: down Device /dev/da1s1a Avail: > 0/17500 MB(0%) > D drive2 State: down Device /dev/da2s1a Avail: > 0/17500 MB(0%) > D drive3 State: down Device /dev/da3s1a Avail: > 0/17500 MB(0%) > D drive4 State: down Device /dev/da4s1a Avail: > 0/17500 MB(0%) > > 1 volumes: > V home State: up Plexes: 1 Size: 68 GB > > 1 plexes: > P home.p0 R5 State: up Subdisks: 5 Size: 68 GB > > 5 subdisks: > S home.p0.s0 State: up PO: 0 B Size: 17 GB > S home.p0.s1 State: up PO: 512 kB Size: 17 GB > S home.p0.s2 State: up PO: 1024 kB Size: 17 GB > S home.p0.s3 State: up PO: 1536 kB Size: 17 GB > S home.p0.s4 State: up PO: 2048 kB Size: 17 GB > > > > > 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 Jan 16 8:22: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clove.rp.lan (unknown [212.74.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 8A92037B402 for ; Tue, 16 Jan 2001 08:21:48 -0800 (PST) Received: (from dom@localhost) by clove.rp.lan (8.9.3/8.8.7) id QAA28824; Tue, 16 Jan 2001 16:21:39 GMT X-Authentication-Warning: clove.rp.lan: dom set sender to dom@semantico.com using -f Date: Tue, 16 Jan 2001 16:21:39 +0000 From: Dominic Mitchell To: "Justin W. Pauler" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mdoc Message-ID: <20010116162139.A28585@semantico.com> References: <01011609563201.98287@wks01.drnet.fais.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us In-Reply-To: <01011609563201.98287@wks01.drnet.fais.net> X-Warning: Incoming message from The Big Giant Head! X-OS: Linux 2.2.13 i686 X-Uptime: 4:19pm up 19 days, 3:39, 4 users, load average: 0.10, 0.08, 0.06 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 16, 2001 at 09:56:32AM -0600, Justin W. Pauler wrote: > I've noticed alot of committs over the last hours of mdoc stuff, like man -> > mdoc and such. Can someone explain what mdoc is and what is happening to the > man pages? I don't know what changes are being made, but mdoc is a BSD enhanced version of the traditional troff -man macro set. It's basically a lot more flexible with regards to output. It's also slower, but that's of little consequence these days. For more details see mdoc(7) or mdoc.samples(7). -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 8:23:18 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 1C12A37B69C for ; Tue, 16 Jan 2001 08:22:49 -0800 (PST) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.0/8.11.0) id f0GGFsJ71655; Tue, 16 Jan 2001 18:15:54 +0200 (EET) (envelope-from ru) Date: Tue, 16 Jan 2001 18:15:54 +0200 From: Ruslan Ermilov To: "Justin W. Pauler" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mdoc Message-ID: <20010116181554.A67837@sunbay.com> Mail-Followup-To: "Justin W. Pauler" , freebsd-stable@FreeBSD.ORG References: <01011609563201.98287@wks01.drnet.fais.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01011609563201.98287@wks01.drnet.fais.net>; from jwpauler@jwpages.com on Tue, Jan 16, 2001 at 09:56:32AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 16, 2001 at 09:56:32AM -0600, Justin W. Pauler wrote: > I've noticed alot of committs over the last hours of mdoc stuff, like man -> > mdoc and such. Can someone explain what mdoc is and what is happening to the > man pages? > ``mdoc'' is the *roff macro package used for writing *BSD manuals; see mdoc(7) manpage for details. The new release of mdoc(7) macro package will soon be released. Some manpages require (minor) fixing in order to be properly displayed with the new mdoc(7) and/or contained minor formatting bugs that (now) detected by mdoc(7). There is also another (less powerful) macro package called man(7). The ``man(7) -> mdoc(7)'' commits convert manpages from one format to another. 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 Tue Jan 16 8:25:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 27A1837B401 for ; Tue, 16 Jan 2001 08:25:08 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 779193223; Tue, 16 Jan 2001 16:25:06 +0000 (GMT) Date: Tue, 16 Jan 2001 16:25:06 +0000 From: Josef Karthauser To: Dag-Erling Smorgrav Cc: stable@FreeBSD.ORG Subject: Re: cdcontrol and environment vars - opinions please. Message-ID: <20010116162506.A608@tao.org.uk> Mail-Followup-To: Josef Karthauser , Dag-Erling Smorgrav , stable@FreeBSD.ORG References: <20010116121921.A632@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Tue, Jan 16, 2001 at 03:14:03PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 16, 2001 at 03:14:03PM +0100, Dag-Erling Smorgrav wrote: > Josef Karthauser writes: > > How many people are using cdcontrol and defining the drive name > > using one of the following environment variables: MUSIC_CD, CD_DRIVE, > > DISC and CDPLAY? > > > > I've no idea why there are so many different options - it seems a > > bit daft to me. > > > > Recently we added another one: CDROM. What I'd like to do is > > deprecate use of the others and adopt CDROM as standard. > > Heh - I'm the one who added suport for $CDROM, and I had no idea the > others were supported - $CDROM was so self-evident (think of $TAPE, > used by pax(1), mt(1), tar(1), dump(8) and restore(8)) that it didn't > occur to me to check if it already supported other variables (plus, > they weren't documented). > > I totally agree with the idea of deprecating all but $CDROM. How about the following. Joe Index: cdcontrol.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/cdcontrol/cdcontrol.c,v retrieving revision 1.29 diff -u -r1.29 cdcontrol.c --- cdcontrol.c 2000/12/18 14:35:54 1.29 +++ cdcontrol.c 2001/01/16 16:22:40 @@ -159,18 +159,29 @@ exit (1); } +char *use_cdrom_instead(char *old_envvar) { + char *device; + + device = getenv(old_envvar); + if (device) + warnx("%s environment variable deprecated, " + "please use CDROM in the future.", old_envvar); + return device; +} + + int main (int argc, char **argv) { int cmd; char *arg; - cdname = getenv ("MUSIC_CD"); + cdname = use_cdrom_instead("MUSIC_CD"); if (! cdname) - cdname = getenv ("CD_DRIVE"); + cdname = use_cdrom_instead("CD_DRIVE"); if (! cdname) - cdname = getenv ("DISC"); + cdname = use_cdrom_instead("DISC"); if (! cdname) - cdname = getenv ("CDPLAY"); + cdname = use_cdrom_instead("CDPLAY"); for (;;) { switch (getopt (argc, argv, "svhf:")) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 9:44:31 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 639A937B400 for ; Tue, 16 Jan 2001 09:44:12 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id JAA03505; Tue, 16 Jan 2001 09:44:07 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda03503; Tue Jan 16 09:43:54 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f0GHhnW14550; Tue, 16 Jan 2001 09:43:49 -0800 (PST) Message-Id: <200101161743.f0GHhnW14550@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdB14541; Tue Jan 16 09:43:39 2001 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.2-RELEASE X-Sender: cschuber To: netch@lucky.net Cc: freebsd-stable@freebsd.org Subject: Re: no newgroup/newgrp in FreeBSD? In-reply-to: Your message of "Tue, 16 Jan 2001 19:13:07 +0200." <20010116191307.A33899@lucky.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Jan 2001 09:43:39 -0800 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010116191307.A33899@lucky.net>, Valentin Nechayev writes: > Hello Cy Schubert - ITSD Open Systems Group! > > Tue, Jan 16, 2001 at 07:28:04, Cy.Schubert wrote about "Re: no newgroup/newg > rp in FreeBSD?": > > > Newgrp(1) is a SYSV thing and doesn't fit in the Berkeley paradigm. > > Under SYSV files/directories are created with the primary group that a > > process is running under. Under BSD (and SYSV under a directory with > > the sticky bit set) the group ownership of a created file/directory is > ~~~~~~ > sgid? Silly me. I knew that. 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 10:13:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.rsmi.com (smtp.rsmi.com [12.17.126.7]) by hub.freebsd.org (Postfix) with ESMTP id CD19537B401 for ; Tue, 16 Jan 2001 10:13:12 -0800 (PST) Received: from Lotus Notes by smtp.rsmi.com (IMA Internet Exchange 3.14) id 003A0286; Tue, 16 Jan 2001 12:12:32 -0600 Mime-Version: 1.0 Date: Tue, 16 Jan 2001 12:11:39 -0600 Message-ID: <003A0286.N22121@fers.com> From: bwilson@fers.com Subject: Subscribe To: freebsd-stable@FreeBSD.org Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Content-Description: Memo Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG __ Bruce Wilson, Manager, FERS Business Services bwilson@fers.com, 312.245.1750, http://www.fers.com/ PGP KeyID: 5430B995, http://www.lasthome.net/~bwilson/ "A difference that makes no difference is no difference." --Spock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 11: 5:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5485537B6A4; Tue, 16 Jan 2001 11:05:09 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0GJ58s30294; Tue, 16 Jan 2001 12:05:08 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101161905.f0GJ58s30294@harmony.village.org> To: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: sysinstall.8 Breaking buildworld In-reply-to: Your message of "Thu, 11 Jan 2001 17:43:32 PST." <20010111174332.B74480@dragon.nuxi.com> References: <20010111174332.B74480@dragon.nuxi.com> <20010111220021.C79365@strontium.scientia.demon.co.uk> Date: Tue, 16 Jan 2001 12:05:08 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010111174332.B74480@dragon.nuxi.com> "David O'Brien" writes: : But disklabel/fdisk can't even accept MB's as a unit. Until they grow : the functionality of the NetBSD and OpenBSD versions of them, sysinstall : is really the only tolerable disk label manipulation tool our users have. : This includes those with a bummed /usr that needs to install a new disk : to get it back. I have patches in my tree from someone to do this the last time this issue came up. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 11:34: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9D44D37B404; Tue, 16 Jan 2001 11:33:36 -0800 (PST) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f0GJXP757881; Tue, 16 Jan 2001 14:33:25 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 16 Jan 2001 14:33:24 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: bgoering@ilsmart.com Cc: stable@FreeBSD.ORG, developers@FreeBSD.ORG Subject: RELENG_4 kern.flp broken (was: Re: Broken kern.flp?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just started running into the same thing using the Jan 16, 2001 kernel floppy disk. The same error: (root@usw3.freebsd.org, Tue Jan 16 11:46:50 GMT 2001) /kernel text=0x24113b data=0x2fdac+0x201ec elf_loadexec: cannot seek can't load module '/kernel': input/output error | Hit [Enter] to boot immediately, or any other key for command prompt. Booting [kernel] /kernel text=0x24113b data=0x2fdac+0x201ec elf_loadexec: cannot seek can't load 'kernel' can't load 'kernel.old' Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Tue, 16 Jan 2001 bgoering@ilsmart.com wrote: > I experienced this yesterday with the Jan/15/2001 kern.flp also... > Bill Goering > > > > > Makoto MATSUSHITA > Sent by: owner-freebsd-stable@FreeBSD.ORG > 01/16/2001 06:40 AM > > > To: Yoshihiro.Koya@math.yokohama-cu.ac.jp > cc: stable@FreeBSD.ORG > Subject: Re: Broken kern.flp? > > > I've already confirmed that kern.flp as of Jan/13/2001 works as it > should be. > > Yoshihiro.Koya> I tried to boot from my kern.flp which was built on Jan > 13. > > But you should know that today is Jan/16/2001. I've checked today's > kern.flp image. Would you please check it again? > > -- - > Makoto MATSUSHITA > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 12:17:56 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 A75DA37B400 for ; Tue, 16 Jan 2001 12:17:36 -0800 (PST) Received: (qmail 7815 invoked by uid 0); 16 Jan 2001 20:17:34 -0000 Received: from p3ee21611.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.17) by mail.gmx.net (mp006-rz3) with SMTP; 16 Jan 2001 20:17:34 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id SAA12044 for freebsd-stable@FreeBSD.ORG; Tue, 16 Jan 2001 18:04:23 +0100 Date: Tue, 16 Jan 2001 18:04:23 +0100 From: Gerhard Sittig To: FreeBSD Stable Subject: Re: odd mouse button behavior Message-ID: <20010116180423.A253@speedy.gsinet> Mail-Followup-To: FreeBSD Stable References: <20010115184459.X253@speedy.gsinet> <200101160330.f0G3UAE03875@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200101160330.f0G3UAE03875@whizzo.transsys.com>; from louie@TransSys.COM on Mon, Jan 15, 2001 at 10:30:10PM -0500 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 15, 2001 at 22:30 -0500, Louis A. Mamakos wrote: > > On Sun, Jan 14, 2001 at 21:26 -0800, Randy Bush wrote: > > > > > > and all of a sudden my mouse does not react to a button > > > until the mosue travels. this is most strange. > > > > You don't have your third button emulated by any chance? > > [...] > > I've had this same sort of thing going on recently too. I > believe that the button-up (or button release) event is getting > "lost". No, in case you have the third button emulated, the "down" event starts to wait for - a movement event - an up event - the other button within a certain time interval or - the interval to timeout Without any of these happening the machine (mouse driver) won't know if this "down" event was meant to be a "down" event or just the introduction of the emulation special case. If you don't move your mouse or don't release the button / press the other button too, you will have to wait for the timeout (some 50 ms). This is when users experience delayed menu popup and the like. Unless I got your description wrong and you do release the button and X doesn't notice. Then I couldn't help you. But it might be helpful to have the above emulation "discussion" and its side effect of delay in the archive "for the record". :) 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 Tue Jan 16 12:41:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.eastlink.ca (syd.eastlink.ca [24.222.47.133]) by hub.freebsd.org (Postfix) with ESMTP id DF5E437B401 for ; Tue, 16 Jan 2001 12:41:17 -0800 (PST) Received: from process.dhs.org (dest@u56n134.syd.eastlink.ca [24.222.56.134] (may be forged)) by mail.eastlink.ca (8.9.3/8.9.3) with SMTP id QAA15123 for ; Tue, 16 Jan 2001 16:41:07 -0400 From: Dest To: freebsd-stable@FreeBSD.org Subject: Odd Console/X behaviour Date: Tue, 16 Jan 2001 16:40:57 -0400 X-Mailer: KMail [version 1.1.99] Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Message-Id: <01011616405700.00691@process.dhs.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I was wondering if someone could perhaps shed some light on the following bug. When my system is under high load and I go to switch to vtty from X, the system locks for a second. This is what's to be expected for a system under a high load. However, when the load disappears it always takes a second or so to switch vttys. Also, the keyboard lights disappear, no scroll-lock, numlock, or capslock light. Also strange is that it only happens when switching out of X. It doesn't matter what version, I've had this happen under 3.3.6 and 4.0.0-4.0.2. getty isn't swapped out, and it only happens once I get a day or so of uptime. It can't be fixed by dropping to single user, and going multi-user again, it requires a reboot to be fixed. I hope you can help, this has been happening since I installed 4.0-RELEASE, which was some time ago. uname -a says: FreeBSD process.dhs.org 4.2-STABLE FreeBSD 4.2-STABLE #0: Tue Jan 2 23:06:54 AST 2001 root@process.dhs.org:/usr/src/sys/compile/DEST i386 I cvsupped/made world the day before the kernel was built. Hope you can help. Craig Hawco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 12:44:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id 1CD5F37B400 for ; Tue, 16 Jan 2001 12:44:35 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id UAA70265 for stable@freebsd.org; Tue, 16 Jan 2001 20:44:30 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101162044.UAA70265@ns.a1.org.uk> Subject: Where to put sysctl command To: stable@freebsd.org Date: Tue, 16 Jan 2001 20:44:30 +0000 (GMT) Reply-To: 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 X-Loop: FreeBSD.ORG Just wondering if anyone has any suggestions on this; One of my machines cannot keep time unless using timecounter.method 1 I know many places to put the sysctl command, but would like to know the best - or is there an option somewhere I can set which will take effect on boot. If anyone has any ideas (and reasons) please tell. I repeat, it's not that I don't know how to do it, it's "what's the best way to do it?" TIA Bap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 12:48:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (Postfix) with ESMTP id AE95937B400 for ; Tue, 16 Jan 2001 12:48:37 -0800 (PST) Received: from feta.isds.duke.edu (feta.isds.duke.edu [152.3.22.76]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id PAA06195 for ; Tue, 16 Jan 2001 15:48:36 -0500 (EST) Received: (from sto@localhost) by feta.isds.duke.edu (8.11.1/8.11.1) id f0GKmaO43232 for stable@FreeBSD.ORG; Tue, 16 Jan 2001 15:48:36 -0500 (EST) (envelope-from sto) Date: Tue, 16 Jan 2001 15:48:36 -0500 From: "Sean O'Connell" To: stable@FreeBSD.ORG Subject: Re: Where to put sysctl command Message-ID: <20010116154836.S42411@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mail-Followup-To: Sean O'Connell , stable@FreeBSD.ORG References: <200101162044.UAA70265@ns.a1.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101162044.UAA70265@ns.a1.org.uk>; from aer001@a1.org.uk on Tue, Jan 16, 2001 at 08:44:30PM +0000 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Catch-all m-box stated: : Just wondering if anyone has any suggestions on this; : : One of my machines cannot keep time unless using timecounter.method 1 : : I know many places to put the sysctl command, but would like to know the best - : or is there an option somewhere I can set which will take effect on boot. : : If anyone has any ideas (and reasons) please tell. : : I repeat, it's not that I don't know how to do it, it's "what's the best way : to do it?" Take a look at rc.sysctl. It uses /etc/sysctl.conf .. there is man 5 page for one or the other of these. S -- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 12:50:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27]) by hub.freebsd.org (Postfix) with ESMTP id B7C6837B404 for ; Tue, 16 Jan 2001 12:49:54 -0800 (PST) Received: from le.adsl.cc.univie.ac.at (le.adsl.cc.univie.ac.at [193.171.3.9]) by mailbox.univie.ac.at (8.9.3/8.9.3) with ESMTP id VAA51264 for ; Tue, 16 Jan 2001 21:49:53 +0100 Date: Tue, 16 Jan 2001 21:49:57 +0100 (CET) From: Lukas Ertl X-X-Sender: To: Subject: Re: Where to put sysctl command In-Reply-To: <200101162044.UAA70265@ns.a1.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Jan 2001, Catch-all m-box wrote: > I know many places to put the sysctl command, but would like to know the = best - > or is there an option somewhere I can set which will take effect on boot. I'd say you best put it into /etc/sysctl.conf. See /etc/sysctl.conf and /etc/rc.sysctl. lg, le --=20 Lukas Ertl eMail: l.ertl@univie.ac.at WWW-Redaktion Tel.: (+43 1) 4277-14073 Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140 der Universit=E4t Wien To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 12:56: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id 48B4637B400 for ; Tue, 16 Jan 2001 12:55:51 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id UAA70322 for stable@freebsd.org; Tue, 16 Jan 2001 20:55:50 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101162055.UAA70322@ns.a1.org.uk> Subject: Re: Where to put sysctl command In-Reply-To: <20010116154836.S42411@stat.Duke.EDU> from "Sean O'Connell" at "Jan 16, 2001 03:48:36 pm" To: stable@freebsd.org Date: Tue, 16 Jan 2001 20:55:49 +0000 (GMT) Reply-To: 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 X-Loop: FreeBSD.ORG Thanks both, that's just what I was looking for :) Bap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 13:37:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pacman.redwoodsoft.com (www.redwoodsoft.com [63.203.215.63]) by hub.freebsd.org (Postfix) with SMTP id 49C7337B401 for ; Tue, 16 Jan 2001 13:37:07 -0800 (PST) Received: (qmail 15390 invoked from network); 16 Jan 2001 21:37:06 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 16 Jan 2001 21:37:06 -0000 Date: Tue, 16 Jan 2001 13:37:06 -0800 (PST) From: Dru Nelson To: stable@freebsd.org Subject: Re: Where to put sysctl command In-Reply-To: <200101162055.UAA70322@ns.a1.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I didn't check it out yet. I will respond to you about that today. Dru Nelson San Mateo, California On Tue, 16 Jan 2001, Catch-all m-box wrote: > Thanks both, that's just what I was looking for :) > > Bap. > > > 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 Jan 16 14:16:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vega.uli.it (vega.uli.it [62.212.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 25DE937B698 for ; Tue, 16 Jan 2001 14:16:06 -0800 (PST) Received: from olgeni.localdomain.net (olgeni.uli.it [62.212.0.22]) by vega.uli.it (Postfix) with ESMTP id 810A932E9E; Tue, 16 Jan 2001 23:15:58 +0100 (CET) Received: from olgeni.localdomain.net (olgeni.localdomain.net [192.168.1.1]) by olgeni.localdomain.net (8.11.1/8.11.1) with ESMTP id f0GMGQ137960; Tue, 16 Jan 2001 23:16:32 +0100 (CET) (envelope-from olgeni@uli.it) Date: Tue, 16 Jan 2001 23:16:26 +0100 (CET) From: Jimmy Olgeni X-X-Sender: To: Gerhard Sittig Cc: FreeBSD Stable Subject: Re: odd mouse button behavior In-Reply-To: <20010116180423.A253@speedy.gsinet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Unless I got your description wrong and you do release the button > and X doesn't notice. Then I couldn't help you. But it might be > helpful to have the above emulation "discussion" and its side > effect of delay in the archive "for the record". :) It does this: Press mouse button Release mouse button See button widget go down (that is, mouse-down event) (nothing happens if I keep the mouse still: there is no timeout!) Move mouse See widget go up and activate UI action... it happens in WING, gtk and qt. I told XFree that Option "Emulate3Buttons" "off" Option "Emulate3Timeout" "0" Option "Buttons" "3" but it has the same behavior without these options. So I'm puzzled. Any hints anyone? -- jimmy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 14:32: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by hub.freebsd.org (Postfix) with ESMTP id 2ECFA37B400 for ; Tue, 16 Jan 2001 14:31:47 -0800 (PST) Received: from rover (dialup-24-0-25-60.corp.home.net [24.0.25.60]) by zipcode.corp.home.net (8.9.3/8.9.3) with SMTP id OAA15520; Tue, 16 Jan 2001 14:31:27 -0800 (PST) From: "Sameer R. Manek" To: "xlr82xs" , Subject: RE: Graphics Card Date: Tue, 16 Jan 2001 14:31:25 -0800 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) In-Reply-To: <01011617151006.71301@xlr82xs.shacknet.nu> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG freebsd will support almost any graphics card. What your question really should be is does XFree86 support the card or not. That question can be answered by either going to http://www.xfree86.org. Note that there is XFree86 3 and 4, please consult the documentation as appropriate. Sameer > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of xlr82xs > Sent: Monday, January 15, 2001 11:15 PM > To: stable@freebsd.org > Subject: Graphics Card > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hrmm, i know this question probably isn't relavent, but still.. > > I've looked through the fbsd handbook for supported graphics cards, and i > cant find anything, so i assume that everything is supported by freebsd > atleast. > > I'm thinking about replaceing my old s3 trio dx graphics card, > but i'm also > kind of poor..and australian which hampers things even more... > > and i was wondering if anyone could suggest a nice graphics card > (hopefully > something capable of more than 16bit 800x600 under x11) that > could be picked > up fairly cheap, but still is compatable ? > > or if not, what i should spend the next few years saveing for. > > > regards, > David > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.3 (FreeBSD) > Comment: For info see http://www.gnupg.org > > iEYEARECAAYFAjpj9QUACgkQcBR/Vvf1G2YoswCfYPABE5aKs27K2R8w/xJAGusN > m94AoImFbXIiXed7T5Arjv+3maLiO574 > =pURB > -----END PGP SIGNATURE----- > > > 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 Jan 16 14:33:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from raffles-it.com (raffles.demon.co.uk [158.152.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 50CE437B402 for ; Tue, 16 Jan 2001 14:33:28 -0800 (PST) Received: from dribble.lan.raffles-it.com (dribble.lan.raffles-it.com [192.168.100.50]) by raffles-it.com (8.11.1/8.11.1) with ESMTP id f0GMMB803353; Tue, 16 Jan 2001 22:22:11 GMT (envelope-from dpd@lan.raffles-it.com) Received: from dribble.lan.raffles-it.com (localhost [127.0.0.1]) by dribble.lan.raffles-it.com (8.11.1/8.11.1) with ESMTP id f0GMZXc09778; Tue, 16 Jan 2001 22:35:33 GMT (envelope-from dpd@lan.raffles-it.com) Message-Id: <200101162235.f0GMZXc09778@dribble.lan.raffles-it.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrew Gordon Cc: freebsd-stable@FreeBSD.ORG, dpd@dribble.lan.raffles-it.com Subject: Re: Vinum incidents. In-Reply-To: Message from Andrew Gordon of "Tue, 16 Jan 2001 15:23:40 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Jan 2001 22:35:33 +0000 From: David Dooley Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew, I am afraid that I had the same problems with a Raid 5 vinum disk using 7 9GB Compaq/Segate drives. I created a 50GB volume for user home directories and it had very low traffic volumes. I managed to recover a stale drive on several occasions, but every couple of days it would go stale again. I have now moved the data from the Raid 5 Volume to another volume that is built with mirrored drives. I rebuilt the raid volume a several more times, made a file system on it and mounted it and that was it, after several days with no traffic to the drives no messages saying that there were any problems it still went stale. The system stayed up through out and nothing appeared in any logs that I could find. The annoying thing to me was that a different drive or combination of drives went stale each time so I couldn't pin the problem down to a drive. I did try alternate termination and cables with no luck. I even swapped the termination with a an identically configured system the same problem reappeared, but didn't move across the systems with the changed hardware so I don't think the problem is with the hardware. At some point I will follow Greg Lehey's web site requirements for trouble shooting and send the required info to him for analysis. Greg's web site is at http://www.vinumvm.org/vinum/how-to- debug.html David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 14:51:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 2BDB237B401 for ; Tue, 16 Jan 2001 14:50:56 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id D1D066AC21; Wed, 17 Jan 2001 09:20:53 +1030 (CST) Date: Wed, 17 Jan 2001 09:20:53 +1030 From: Greg Lehey To: Andrew Gordon Cc: freebsd-stable@freebsd.org Subject: Re: Vinum incidents. Message-ID: <20010117092053.C16555@wantadilla.lemis.com> 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 arg@arg1.demon.co.uk on Tue, Jan 16, 2001 at 03:23:40PM +0000 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 16 January 2001 at 15:23:40 +0000, Andrew Gordon wrote: > > I have a server with 5 identical SCSI drives, arranged as a single RAID-5 > volume using vinum (and softupdates). This is exported with > NFS/Samba/Netatalk/Econet to clients of various types; the root,usr,var > partitions are on a small IDE drive (there are no local users or > application processes). The machine has a serial console. > > This has been working reliably for a couple of months, running -stable > from around the time of 4.2-release. On 1st January, I took advantage of > the low load to do an upgrade to the latest -stable. > > Since then, there have been two incidents (probably not in fact related to > the upgrade) where vinum has not behaved as expected: > > 1) Phantom disc error > --------------------- > > Vinum logged: > > Jan 2 01:59:26 serv20 /kernel: home.p0.s0: fatal write I/O error > Jan 2 01:59:26 serv20 /kernel: vinum: home.p0.s0 is stale by force > Jan 2 01:59:26 serv20 /kernel: vinum: home.p0 is degraded > > However, there was no evidence of any actual disc error - nothing was > logged on the console, in dmesg or any other log files. The system would > have been substantially idle at that time of night, except that the daily > cron jobs would just been starting at that time. Hmm. In view of what followed, I'd still suspect that you've had some kind of I/O error. > > A "vinum start home.p0.s0" some time later successfully revived the plex > and the system then ran uninterrupted for two weeks. > > Does this suggest some sort of out-of-range block number bug somewhere? Not a priori. I think I'll get Vinum to report the block number, and that will give us more information. > 2) Recovery problems > -------------------- > > I've never seen anything like this before. Can you take a look at http://www.vinumvm.org/vinum/how-to-debug.html and send me the information I asked for there? I know you've supplied some of it, but the uninterrupted logs over the complete time would help a lot. > On booting to multi-user mode, I noticed that all the drives were > marked as 'down', even though the volume and most of the subdisks > were 'up' (and a quick check in the console scroll-back showed that > it was also in this state before the previous attempt to revive: This in particular puzzles me. My best bet is that Vinum reacted in an unfriendly manner to something you said to it. The Vinum history will help there. > This time, I used 'vinum start' on drive[0-4] before doing vinum start on > home.p0.s3, and this time it successfully revived, taking 10 minutes or > so. Some minutes later, the machine paniced (this time saving a dump): > > IdlePTD 3166208 > initial pcb at 282400 > panicstr: softdep_lock: locking against myself > panic messages: > --- > panic: softdep_setup_inomapdep: found inode > (kgdb) where > #0 0xc014dd1a in dumpsys () > #1 0xc014db3b in boot () > #2 0xc014deb8 in poweroff_wait () > #3 0xc01e6b49 in acquire_lock () > #4 0xc01eae02 in softdep_fsync_mountdev () > #5 0xc01eef0e in ffs_fsync () > #6 0xc01edc16 in ffs_sync () > #7 0xc017b42b in sync () > #8 0xc014d916 in boot () > #9 0xc014deb8 in poweroff_wait () > #10 0xc01e792c in softdep_setup_inomapdep () > #11 0xc01e44a4 in ffs_nodealloccg () > #12 0xc01e352b in ffs_hashalloc () > #13 0xc01e3186 in ffs_valloc () > #14 0xc01f4e6f in ufs_makeinode () > #15 0xc01f2824 in ufs_create () > #16 0xc01f5029 in ufs_vnoperate () > #17 0xc01b1e43 in nfsrv_create () > #18 0xc01c6b2e in nfssvc_nfsd () > #19 0xc01c6483 in nfssvc () > #20 0xc022b949 in syscall2 () > #21 0xc02207b5 in Xint0x80_syscall () > #22 0x8048135 in ?? () This is a soft updates panic. It's not beyond the bounds of possibility that it's caused by Vinum, but the fact that you've had these problems since the upgrade suggests that it could also be a result of some recent commits to the soft update code. Please keep the dump, just in case. Have you compiled the kernel with debug symbols? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 14:53:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id E1C5537B400 for ; Tue, 16 Jan 2001 14:53:30 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 66B796AC20; Wed, 17 Jan 2001 09:23:29 +1030 (CST) Date: Wed, 17 Jan 2001 09:23:29 +1030 From: Greg Lehey To: Kent Hamilton , David Dooley Cc: Andrew Gordon , freebsd-stable@freebsd.org, dpd@dribble.lan.raffles-it.com Subject: Re: Vinum incidents. Message-ID: <20010117092329.D16555@wantadilla.lemis.com> References: <200101162235.f0GMZXc09778@dribble.lan.raffles-it.com> <508F01B47A2BD411844500A0C9C83B440B6F44@mailbox.Hunter.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <508F01B47A2BD411844500A0C9C83B440B6F44@mailbox.Hunter.COM>; from KHamilton@Hunter.COM on Tue, Jan 16, 2001 at 10:16:28AM -0600 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 16 January 2001 at 10:16:28 -0600, Kent Hamilton wrote: > I've seen both of these problems on my home system as well. If someone has a > solution I'd love to hear about it. On Tuesday, 16 January 2001 at 22:35:33 +0000, David Dooley wrote: > Andrew, > > I am afraid that I had the same problems with a Raid 5 vinum disk using 7 9GB > Compaq/Segate drives. I created a 50GB volume for user home directories and it > had very low traffic volumes. I managed to recover a stale drive on several > occasions, but every couple of days it would go stale again. I have now moved > the data from the Raid 5 Volume to another volume that is built with mirrored > drives. I rebuilt the raid volume a several more times, made a file system on > it and mounted it and that was it, after several days with no traffic to the > drives no messages saying that there were any problems it still went stale. > The system stayed up through out and nothing appeared in any logs that I could > find. The annoying thing to me was that a different drive or combination of > drives went stale each time so I couldn't pin the problem down to a drive. I > did try alternate termination and cables with no luck. I even swapped the > termination with a an identically configured system the same problem > reappeared, but didn't move across the systems with the changed hardware so I > don't think the problem is with the hardware. Please don't assume that just because you've had problems, that they've had the same cause. I'd prefer to treat all problems as unrelated until I see proof that they're related, and so far I haven't seen this. > At some point I will follow Greg Lehey's web site requirements for > trouble shooting and send the required info to him for > analysis. Greg's web site is at > http://www.vinumvm.org/vinum/how-to-debug.html Please do. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 15:35:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [194.242.131.94]) by hub.freebsd.org (Postfix) with ESMTP id 9CB0837B404 for ; Tue, 16 Jan 2001 15:35:10 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id 6D7263244; Tue, 16 Jan 2001 23:35:10 +0000 (GMT) Date: Tue, 16 Jan 2001 23:35:10 +0000 From: Josef Karthauser To: Dag-Erling Smorgrav Cc: stable@FreeBSD.ORG Subject: Re: cdcontrol and environment vars - opinions please. Message-ID: <20010116233510.F1731@tao.org.uk> Mail-Followup-To: Josef Karthauser , Dag-Erling Smorgrav , stable@FreeBSD.ORG References: <20010116121921.A632@tao.org.uk> <20010116162506.A608@tao.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010116162506.A608@tao.org.uk>; from joe@tao.org.uk on Tue, Jan 16, 2001 at 04:25:06PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 16, 2001 at 04:25:06PM +0000, Josef Karthauser wrote: > On Tue, Jan 16, 2001 at 03:14:03PM +0100, Dag-Erling Smorgrav wrote: > > I totally agree with the idea of deprecating all but $CDROM. > > How about the following. > Joe > > > Index: cdcontrol.c > =================================================================== > RCS file: /home/ncvs/src/usr.sbin/cdcontrol/cdcontrol.c,v > retrieving revision 1.29 > diff -u -r1.29 cdcontrol.c > --- cdcontrol.c 2000/12/18 14:35:54 1.29 > +++ cdcontrol.c 2001/01/16 16:22:40 > @@ -159,18 +159,29 @@ > exit (1); Committed to -current. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 16:55:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bsd.ivytech7.cc.in.us (unknown [165.138.38.6]) by hub.freebsd.org (Postfix) with ESMTP id 6106037B400 for ; Tue, 16 Jan 2001 16:55:11 -0800 (PST) Received: from a191016 ([168.91.170.134]) by bsd.ivytech7.cc.in.us (8.11.1/8.11.1) with SMTP id f0H0wG202351 for ; Tue, 16 Jan 2001 19:58:16 -0500 (EST) (envelope-from dmac@bsd.ivytech7.cc.in.us) Message-ID: <000a01c0801f$6cb64540$86aa5ba8@ivy07bit> Reply-To: "Dave McCammon" From: "Dave McCammon" To: Subject: Fw: make installword failure Date: Tue, 16 Jan 2001 19:49:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >cleaned out /usr/obj/ > cvsup'd all 1/14/01 > did make buildworld-ok > errored on make installworld as follows (twice) > > > > ln -sf ../sys/joystick.h /usr/include/machine/joystick.h > cd /usr/src/include; install -C -o root -g wheel -m 444 a.out.h ar.h assert.h bitstring.h ctype.h db.h dirent.h disktab.h dlfcn.h elf.h err.h fnmatch.h fstab.h fts.h glob.h grp.h strhash.h histedit.h ieeefp.h ifaddrs.h iso646.h libgen.h limits.h link.h locale.h malloc.h memory.h mpool.h ndbm.h netdb.h nl_types.h nlist.h objformat.h paths.h pthread.h pthread_np.h pwd.h ranlib.h regex.h regexp.h resolv.h rune.h runetype.h search.h setjmp.h sgtty.h signal.h stab.h stddef.h stdio.h stdlib.h string.h stringlist.h strings.h struct.h sysexits.h tar.h time.h timers.h ttyent.h unistd.h utime.h utmp.h vis.h /usr/include > cd /usr/src/include/arpa; install -C -o root -g wheel -m 444 ftp.h inet.h nameser.h nameser_compat.h telnet.h tftp.h /usr/include/arpa > cd /usr/src/include/protocols; install -C -o root -g wheel -m 444 dumprestore.h routed.h rwhod.h talkd.h timed.h /usr/include/protocols > cd /usr/src/include/rpc; install -C -o root -g wheel -m 444 auth.h auth_unix.h clnt.h pmap_clnt.h pmap_prot.h pmap_rmt.h rpc.h rpc_com.h rpc_msg.h svc.h svc_auth.h types.h xdr.h auth_des.h des.h des_crypt.h /usr/include/rpc > install -C -o root -g wheel -m 444 /usr/src/include/osreldate.h /usr/include > install: /usr/src/include/osreldate.h: No such file or directory > *** Error code 71 > > Stop in /usr/src/include. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 16:58:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from bsd.ivytech7.cc.in.us (unknown [165.138.38.6]) by hub.freebsd.org (Postfix) with ESMTP id 32EB837B698 for ; Tue, 16 Jan 2001 16:58:23 -0800 (PST) Received: from a191016 ([168.91.170.134]) by bsd.ivytech7.cc.in.us (8.11.1/8.11.1) with SMTP id f0H11S202369 for ; Tue, 16 Jan 2001 20:01:28 -0500 (EST) (envelope-from dmac@bsd.ivytech7.cc.in.us) Message-ID: <000f01c0801f$de9ac3c0$86aa5ba8@ivy07bit> Reply-To: "Dave McCammon" From: "Dave McCammon" To: Subject: make install failure Date: Tue, 16 Jan 2001 19:53:07 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01C07FF5.F2344200" 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 X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C07FF5.F2344200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable currently running 4.2 stable tracking 4.2 stable ------=_NextPart_000_000C_01C07FF5.F2344200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
currently running 4.2 stable
tracking 4.2 stable
------=_NextPart_000_000C_01C07FF5.F2344200-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 17:13:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.hccnet.nl (smtp.hccnet.nl [193.172.127.93]) by hub.freebsd.org (Postfix) with ESMTP id 3FE2137B69D for ; Tue, 16 Jan 2001 17:13:38 -0800 (PST) Received: from parmenides.utp.xnet by smtp.hccnet.nl via uds14-123.dial.hccnet.nl [193.173.123.14] with ESMTP id CAA04660 (8.8.5/1.13); Wed, 17 Jan 2001 02:13:28 +0100 (MET) Received: by parmenides.utp.xnet (Postfix, from userid 1005) id 874BB148; Wed, 17 Jan 2001 02:12:13 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by parmenides.utp.xnet (Postfix) with ESMTP id 50BFB101; Wed, 17 Jan 2001 02:12:13 +0100 (CET) Date: Wed, 17 Jan 2001 02:12:13 +0100 (CET) From: Janko van Roosmalen X-Sender: acs@parmenides.utp.xnet To: "Ron 'The InSaNe One' Rosson" Cc: freebsd-stable@freebsd.org, snort-users@lists.sourceforge.net, ipfilter@coombs.anu.edu.au Subject: Re: Server locks up every 5-6 days In-Reply-To: <20010115172424.A79430@lunatic.oneinsane.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 15 Jan 2001, Ron 'The InSaNe One' Rosson wrote: > I have a server running at a clients that has a problem of rebooting > every 5-6 days. It duties are as follows: > > Provide NAT for 25 workstations > Be a Network Firewall > Be a Network IDS > Run a Web server for easy viewing for the Higher-ups > > The Server is FreeBSD 4.2-STABLE as of Dec 21, 2000 running on a k6-2 > 400 (mobo has the pcib2: . The > internal and externla interfaces are Intel Pro 10/100B/100+ Ethernet > cards. Machine has 64megs of RAM > > The NAT and Firewall chores are being handled by ipfilter 3.4.8 > > The IDS is snort version 1.7 logging to a mysql database (localhost) > running the vision.conf ruleset (http://whitehats.com/ids) > > The webserver is Apach version 1.3.14 with mod_php4 (to allow ACID for > snort to be viewed proplerly). > > The only public port open to this box is 22 (ssh) for administrative > purposes. All other ports are blocked or filtered. > > >From looking at the /var/log/messages and the ACID interface the box > seems to get bombarded with the following log entires: > > Jan 11 18:26:30 mybox snort: IDS193/ddos-stacheldraht server-spoof: xxx.xxx.xxx.xxx -> xxx.xxx.xxx.xxx > Stacheldraht (German for barbed wire) is a tool used for distributed DOS attacks. Either you are a target or used as a launchpad for Stacheldraht DOS attacks. This type of attack brought down yahoo and amazon last year. You can find information about Stacheldraht on www.cert.org. You also could report this incident to CERT at www.cert.org. > > Anyone have any ideas what could be causing this.. The Lockups are in > such a way that the only choice you have is to hit the reset button. > ===Janko van Roosmalen - Vught - Netherlands=== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 17:25:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id 1EEF637B6A0 for ; Tue, 16 Jan 2001 17:25:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f0H1PPE15678; Tue, 16 Jan 2001 19:25:25 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101170125.f0H1PPE15678@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Mark Thomas Cc: FreeBSD-stable@FreeBSD.ORG From: David Kelly Subject: Re: Athlon and 4.2 Release In-reply-to: Message from Mark Thomas of "Mon, 15 Jan 2001 22:48:53 EST." <5.0.2.1.2.20010115224747.020d4ad0@mail.clark.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Jan 2001 19:25:25 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Thomas writes: > At 08:40 PM 1/15/01 -0600, David Kelly wrote: > >For this MB to run reliably under load I had to select "BIOS Defaults", > >and maybe also "System Performance Setting" from "Optimal" to "Normal". > >Also disabled "PCI Master Read Caching" and "Delayed Transaction". > >Something in there was causing problems under load. The situation might > >also surface during installation. > > I had issues with this MB under W98 that a BIOS flash helped resolve > (I think up to 1004). It seems very picky about shared interrupts, > particularly with the ATA/100 controller. Once FreeBSD is running what does the BIOS have to do with it? Or does the BIOS initialize something that FreeBSD otherwise doesn't mess with? Don't know how but managed to juggle IRQ's until the onboard ATA-100 got IRQ 10 all to itself. Altho it didn't seem to matter. Its running solid now so I'm not going to mess with it. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 17:28:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id ABC9237B69F for ; Tue, 16 Jan 2001 17:27:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f0H1RjE15693; Tue, 16 Jan 2001 19:27:45 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101170127.f0H1RjE15693@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Michel Talon Cc: FreeBSD-stable@FreeBSD.ORG From: David Kelly Subject: Re: Athlon and 4.2 Release In-reply-to: Message from Michel Talon of "Tue, 16 Jan 2001 10:42:01 +0100." <20010116104201.B503@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Jan 2001 19:27:45 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michel Talon writes: > On Mon, Jan 15, 2001 at 08:40:23PM -0600, David Kelly wrote: > > For this MB to run reliably under load I had to select "BIOS Defaults", > > and maybe also "System Performance Setting" from "Optimal" to "Normal". > > Also disabled "PCI Master Read Caching" and "Delayed Transaction". > > Something in there was causing problems under load. The situation might > > also surface during installation. > > Strange because i have here installed FreeBSD 4.2-Stable on an Abit KT7 Raid > which has the same chipset, and runs an Athlon 1.1 Ghz. I have loaded all > optimal settings in the Bios to enhance speed, and all works beautifully, > including UDMA speed for the disk (here a Western Digital). I probably incorrectly placed the blame completely on the MB when I don't really know my PCI cards are PCI 2.2 compliant, or what that involves. I think the BIOS values I tweaked to produce a reliable system were PCI related. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 17:53: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from benzine.rootprompt.net (mail.rootprompt.net [208.53.161.252]) by hub.freebsd.org (Postfix) with ESMTP id 4C2DF37B402 for ; Tue, 16 Jan 2001 17:52:45 -0800 (PST) From: "Robert Banniza" To: Subject: RE: sshd not working after upgrade to 4.2S from 4.1R HELP Date: Tue, 16 Jan 2001 19:53:32 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <200101151857.SAA67739@ns.a1.org.uk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Guys, I just cvsup'ed 4.2R to 4.2 stable as of today and like others I'm getting errors with the libssl portion. This is also causing Apache not to startup as well as causing problems with ssh. I saw on the list where other had mentioned running merge master and I did but it didn't seem to help. Can anyone tell me the exact steps they took to fix this? Any help greatly appreciated. Robert -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Catch-all m-box Sent: Monday, January 15, 2001 10:58 AM To: freebsd-stable@freebsd.org Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP > On Mon, Jan 15, 2001 at 11:08:29AM -0500, Russell D. Murphy Jr. wrote: > > > > I upgraded from STABLE as of last Friday. I *did* run mergemaster, > > but I'm also having this problem (ssh fails; scp does not): > > > > Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service > > Jan 14 14:37:59 knock sshd[9674]: fatal: PAM session setup failed[6]: Permission denied > > Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service > > If you are still getting this message, then your pam.conf is out of > date. Since you also have an out of date sshd_config and both of these > are installed by mergemaster, I'm led to suspect you haven't run > mergemaster with the latest sources. > > Kris I had exactly this problem. I track stable at home and work, and build/install world regularly. I did a new installation from the 4.2R CD on Friday, and immediatly cvsup'd from uk2 I had the problem with pam (after mergemaster) but only realised on Saturday. I did a new cvsup build/install merge and everything was fine! Bap. 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 Jan 16 18:16:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shell.i-sphere.com (shell.i-sphere.com [209.249.146.70]) by hub.freebsd.org (Postfix) with ESMTP id C11C837B401 for ; Tue, 16 Jan 2001 18:16:14 -0800 (PST) Received: (from fasty@localhost) by shell.i-sphere.com (8.11.1/8.11.0) id f0H2J7p14459; Tue, 16 Jan 2001 18:19:07 -0800 (PST) (envelope-from fasty) Date: Tue, 16 Jan 2001 18:19:07 -0800 From: faSty To: Robert Banniza Cc: freebsd-stable@freebsd.org Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP Message-ID: <20010116181907.A14407@i-sphere.com> References: <200101151857.SAA67739@ns.a1.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from robert@rootprompt.net on Tue, Jan 16, 2001 at 07:53:32PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, It happened to my server same situation today and I got the tip from someone told me do copy /usr/src/etc/pam.conf to /etc IE. cp -p /usr/src/etc/pam.conf /etc/. make sure the /usr/src/etc/pam.conf contain sshd statement inside. I reseted sshd and got it work very well. -trev On Tue, Jan 16, 2001 at 07:53:32PM -0800, Robert Banniza wrote: > Guys, > I just cvsup'ed 4.2R to 4.2 stable as of today and like others I'm getting > errors with the libssl portion. This is also causing Apache not to startup > as well as causing problems with ssh. I saw on the list where other had > mentioned running merge master and I did but it didn't seem to help. Can > anyone tell me the exact steps they took to fix this? Any help greatly > appreciated. > > Robert > > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Catch-all m-box > Sent: Monday, January 15, 2001 10:58 AM > To: freebsd-stable@freebsd.org > Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP > > > > On Mon, Jan 15, 2001 at 11:08:29AM -0500, Russell D. Murphy Jr. wrote: > > > > > > I upgraded from STABLE as of last Friday. I *did* run mergemaster, > > > but I'm also having this problem (ssh fails; scp does not): > > > > > > Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service > > > Jan 14 14:37:59 knock sshd[9674]: fatal: PAM session setup failed[6]: > Permission denied > > > Jan 14 14:37:59 knock sshd[9674]: no modules loaded for `sshd' service > > > > If you are still getting this message, then your pam.conf is out of > > date. Since you also have an out of date sshd_config and both of these > > are installed by mergemaster, I'm led to suspect you haven't run > > mergemaster with the latest sources. > > > > Kris > > I had exactly this problem. I track stable at home and work, and > build/install > world regularly. > > I did a new installation from the 4.2R CD on Friday, and immediatly cvsup'd > from uk2 > > I had the problem with pam (after mergemaster) but only realised on > Saturday. > I did a new cvsup build/install merge and everything was fine! > > Bap. > > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 18:55: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id BC89637B401 for ; Tue, 16 Jan 2001 18:54:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f0H2sYE17644; Tue, 16 Jan 2001 20:54:35 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101170254.f0H2sYE17644@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Robert Banniza" Cc: freebsd-stable@FreeBSD.ORG From: David Kelly Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP In-reply-to: Message from "Robert Banniza" of "Tue, 16 Jan 2001 19:53:32 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Jan 2001 20:54:34 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Robert Banniza" writes: > Guys, > I just cvsup'ed 4.2R to 4.2 stable as of today and like others I'm gett ing > errors with the libssl portion. This is also causing Apache not to startup > as well as causing problems with ssh. I saw on the list where other had > mentioned running merge master and I did but it didn't seem to help. Can > anyone tell me the exact steps they took to fix this? Any help greatly > appreciated. Uh, "mergemaster followed by a reboot?" Noticed some ssh changes in make.conf. Not sure how much ssh and ssl share in the libraries but that might make a difference when building apache (which I presume you built with ssl?). -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 20:22:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail1.sdc1.sfba.home.com (femail1.sdc1.sfba.home.com [24.0.95.81]) by hub.freebsd.org (Postfix) with ESMTP id A90AC37B400; Tue, 16 Jan 2001 20:22:02 -0800 (PST) Received: from math.missouri.edu ([24.12.197.197]) by femail1.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010117042132.HUUG2567.femail1.sdc1.sfba.home.com@math.missouri.edu>; Tue, 16 Jan 2001 20:21:32 -0800 Message-ID: <3A651DE9.9D801139@math.missouri.edu> Date: Tue, 16 Jan 2001 22:22:01 -0600 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Stefan `Sec` Zehl Cc: freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: disable mousepad taps on Dell Inspiron References: <3A5FD090.E035557F@math.missouri.edu> <20010116105945.A803@matrix.42.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stefan `Sec` Zehl wrote: > > On Fri, Jan 12, 2001 at 09:50:40PM -0600, Stephen Montgomery-Smith wrote: > > I have submitted another PR describing how to do this: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=24299 > > I wanted to disable the 'tap' functionality on my vaio laptop. After > reading the moused-manpage I realized that it might be possible without > hacking the psm source if my pad sends the tap as button 4 and tried > > moused -m 4=0 > > which works like a charm for me. I'm very happy now :) > I got an error: invalid argument '4=0' when I tried it. -- 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 Tue Jan 16 20:27:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail1.sdc1.sfba.home.com (femail1.sdc1.sfba.home.com [24.0.95.81]) by hub.freebsd.org (Postfix) with ESMTP id 754F137B400; Tue, 16 Jan 2001 20:27:03 -0800 (PST) Received: from math.missouri.edu ([24.12.197.197]) by femail1.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010117042633.HZDQ2567.femail1.sdc1.sfba.home.com@math.missouri.edu>; Tue, 16 Jan 2001 20:26:33 -0800 Message-ID: <3A651F16.B83DE07F@math.missouri.edu> Date: Tue, 16 Jan 2001 22:27:02 -0600 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: disable mousepad taps on Dell Inspiron References: <3A5FD090.E035557F@math.missouri.edu> <200101150126.KAA00198@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks. I appreciate your response. I probably won't see your fine upcoming work for a while because I use Stable. But if people know about my patch and port, they can be steered towards that until your patch makes it into STABLE, and finally into release. Thanks, Stephen Kazutaka YOKOTA wrote: > > >I have submitted another PR describing how to do this: > > > >http://www.freebsd.org/cgi/query-pr.cgi?pr=24299 > > > >I now know quite a few people who would like something like this. > >The old PR I submitted regarding this is now out of date. Could > >someone please commit this (and the required co-PR: > >http://www.freebsd.org/cgi/query-pr.cgi?pr=20352 ) > >or something like this? > > > >Thanks, Stephen > > Hi, > > We exchanged mails quite a while ago and discussed about your > proposed patch. I am sorry that I haven't written to you since then. > > The reason why I didn't commit your patch straight away at that time > wasn't that I saw problems in your patch, but rather that the psm > driver has gotten so bloat over the years and now have full of > various model-specific code in it. It's getting more and more difficult > to maintain. > > In addition, nowadays there are so many arcane PS/2 mice which require > special attention by the driver on the market. We need to add support > for those mice as well. > > Because of that, I decided to reorganize the psm driver a bit. > I will split the model-specific code from the main body of the driver, > and create a set of sub-drivers each of which will support a specific > PS/2 mouse model. I promise that the TouchPad support will be one of the > first sub-drivers to be added. I am almost there and commit the > new code to the -CURRENT tree in a couple of weeks. > > IMHO, the PS/2 mouse is a dying beast, in that the USB mouse is > the way to go. But, for the time being (well, a couple of years? > three year?), we need to keep the psm driver in good shape. > > Kazu -- 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 Tue Jan 16 20:32:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail8.sdc1.sfba.home.com (femail8.sdc1.sfba.home.com [24.0.95.88]) by hub.freebsd.org (Postfix) with ESMTP id 91A9137B400; Tue, 16 Jan 2001 20:32:01 -0800 (PST) Received: from math.missouri.edu ([24.12.197.197]) by femail8.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010117043200.ELRJ8655.femail8.sdc1.sfba.home.com@math.missouri.edu>; Tue, 16 Jan 2001 20:32:00 -0800 Message-ID: <3A652040.F20BB4F8@math.missouri.edu> Date: Tue, 16 Jan 2001 22:32:00 -0600 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Kazutaka YOKOTA , freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: disable mousepad taps on Dell Inspiron References: <3A5FD090.E035557F@math.missouri.edu> <200101150126.KAA00198@zodiac.mech.utsunomiya-u.ac.jp> <3A651F16.B83DE07F@math.missouri.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Montgomery-Smith wrote: > > Thanks. I appreciate your response. I probably won't see > your fine upcoming work for a while because I use Stable. > But if people know about my patch and port, they can be steered > towards that until your patch makes it into STABLE, and finally > into release. > Oops read that and the tone was not what I intended - I meant that if people ask, I will tell them about the patch - not that anyone else should feel the need to take on this task themselves. -- 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 Tue Jan 16 20:35: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id E5B3837B400 for ; Tue, 16 Jan 2001 20:34:43 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id f0H4YWE18257; Tue, 16 Jan 2001 23:34:36 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200101170434.f0H4YWE18257@whizzo.transsys.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jimmy Olgeni Cc: Gerhard Sittig , FreeBSD Stable X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: odd mouse button behavior References: In-reply-to: Your message of "Tue, 16 Jan 2001 23:16:26 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Jan 2001 23:34:32 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Unless I got your description wrong and you do release the button > > and X doesn't notice. Then I couldn't help you. But it might be > > helpful to have the above emulation "discussion" and its side > > effect of delay in the archive "for the record". :) > > > > It does this: > > Press mouse button > Release mouse button > > See button widget go down (that is, mouse-down event) > > (nothing happens if I keep the mouse still: there is no timeout!) > > Move mouse > > See widget go up and activate UI action... it happens in WING, gtk and > qt. > > > > I told XFree that > > Option "Emulate3Buttons" "off" > Option "Emulate3Timeout" "0" > Option "Buttons" "3" > > but it has the same behavior without these options. > > So I'm puzzled. Any hints anyone? Same here, I don't have 3 button emulation enabled. I'm using XFree 4 and no mention of 3 button emulation in the X server config file. My moused also does not attempt to do 3rd button emulation, either. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 21: 4:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rm-rstar.sfu.ca (rm-rstar.sfu.ca [142.58.120.21]) by hub.freebsd.org (Postfix) with ESMTP id 1406C37B401 for ; Tue, 16 Jan 2001 21:03:54 -0800 (PST) Received: from fraser.sfu.ca (tmchow@fraser.sfu.ca [142.58.101.25]) by rm-rstar.sfu.ca (8.10.1/8.10.1/SFU-5.0H) with ESMTP id f0H53mi03230 for ; Tue, 16 Jan 2001 21:03:48 -0800 (PST) Received: from localhost (tmchow@localhost) by fraser.sfu.ca (8.9.2/8.9.2/SFU-5.0C) with ESMTP id VAA18616 for ; Tue, 16 Jan 2001 21:03:47 -0800 (PST) X-Authentication-Warning: fraser.sfu.ca: tmchow owned process doing -bs Date: Tue, 16 Jan 2001 21:03:47 -0800 (PST) From: Trevin Chow To: FreeBSD Stable Subject: Can't Telnet but can SSH? In-Reply-To: <200101170434.f0H4YWE18257@whizzo.transsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I'm having some problems with my firewall rules regarding telnet and it may have to do with my NS setup. 1) Whenever I try to telnet to 2 external hosts (my university and another host), I connect, and right before it displays the "login:" prompt, it says "Connection closed by foreign host". However, I can SSH to these same hosts. 2) I'm acting as my own NS for my domain. On my freebsd box, if I do an `nslookup` and `set type=SOA`, and enter my domain, everything is okay and it reports everything as expected. However, on an external system, if I do the same thing, it says: "can't find mydomain.com: Non-existent host/domain". It should also be noted that if I do a regular `nslookup` WITHOUT `set type=SOA`, then then it resolves to my correct IP on both internal and external boxes. Is there some type of firewall traffic that maybe I'm denying? I'm using a default deny based firewalling system and the onyl rule I have to allow DNS traffic in /etc/rc.firewall is: add pass udp from any to ${oip} 53 Maybe I'm missing something? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jan 16 21:15:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id A06B437B400; Tue, 16 Jan 2001 21:15:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.1+3.4W/8.11.1) with ESMTP/inet id f0H5F2888896; Wed, 17 Jan 2001 14:15:03 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: References: X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Persephone) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 20 From: Makoto MATSUSHITA To: stable@FreeBSD.ORG, developers@FreeBSD.ORG Subject: Re: RELENG_4 kern.flp broken (was: Re: Broken kern.flp?) Date: Wed, 17 Jan 2001 14:14:45 +0900 Message-Id: <20010117141445A.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rwatson> I just started running into the same thing using the Jan 16, rwatson> 2001 kernel floppy disk. The same error: I don't know why, but the latest floppy image available at current.jp.FreeBSD.org, works fine to me. doesn't work, but we can easily assume that next coming kern.flp (maybe labeled as 4.2-20010117-STABLE) will work again. Something is changed by somebody, and floppy problem is fixed (?). -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 0:47:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [192.215.234.86]) by hub.freebsd.org (Postfix) with SMTP id 1361837B400 for ; Wed, 17 Jan 2001 00:47:25 -0800 (PST) Received: (qmail 17047 invoked by uid 1078); 17 Jan 2001 08:47:32 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Jan 2001 08:47:32 -0000 Date: Wed, 17 Jan 2001 00:47:32 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: Trevin Chow Cc: FreeBSD Stable Subject: Re: Can't Telnet but can SSH? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Jan 2001, Trevin Chow wrote: > I think I'm having some problems with my firewall rules > regarding telnet and it may have to do with my NS setup. > > 1) Whenever I try to telnet to 2 external hosts (my university and another > host), I connect, and right before it displays the "login:" prompt, > it says "Connection closed by foreign host". > > However, I can SSH to these same hosts. > > 2) I'm acting as my own NS for my domain. > > On my freebsd box, if I do an `nslookup` and `set type=SOA`, and > enter my domain, everything is okay and it reports everything as expected. > > However, on an external system, if I do the same thing, it says: > "can't find mydomain.com: Non-existent host/domain". > > It should also be noted that if I do a regular `nslookup` WITHOUT `set > type=SOA`, then then it resolves to my correct IP on both internal and > external boxes. > > Is there some type of firewall traffic that maybe I'm denying? > I'm using a default deny based firewalling system and the onyl rule I have > to allow DNS traffic in /etc/rc.firewall is: > > add pass udp from any to ${oip} 53 > > Maybe I'm missing something? The most obvious answer would be that the hosts don't allow telnet from external networks (at least, I wouldn't). You need to add some other rules for dns, here's mine: allow tcp from any to ${oip} 53 setup allow udp from any to ${oip} 53 allow udp from ${oip} 53 to any Remember that DNS _can_ be tcp. Also, you need to allow both directions for udp DNS otherwise it most definitly will not work. See below... Also make sure your named.conf has the following line enabled: options { query-source address * port 53; }; At least, that's what I did. I hope it helps. YMMV. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 1:24:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 962AD37B402 for ; Wed, 17 Jan 2001 01:24:19 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0H9Rb955324; Wed, 17 Jan 2001 01:27:37 -0800 (PST) (envelope-from kris) Date: Wed, 17 Jan 2001 01:27:37 -0800 From: Kris Kennaway To: faSty Cc: Robert Banniza , freebsd-stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP Message-ID: <20010117012737.A55253@citusc17.usc.edu> References: <200101151857.SAA67739@ns.a1.org.uk> <20010116181907.A14407@i-sphere.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010116181907.A14407@i-sphere.com>; from fasty@i-sphere.com on Tue, Jan 16, 2001 at 06:19:07PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 16, 2001 at 06:19:07PM -0800, faSty wrote: > Hi there, >=20 > It happened to my server same situation today and I got the tip from som= eone > told me do copy /usr/src/etc/pam.conf to /etc This should have happened as part of running mergemaster, which is an important part of the upgrade process you should follow with every source update and rebuild. Please see the handbook for full instructions on how to safely update your system. Kris --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6ZWWJWry0BWjoQKURAq/OAKC6B1Zems3KI1IZ+M+WyUIDc08INACglgQo fcUbIOcAFrxZBPP8ru/mz9A= =1N8B -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 3:39:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id EEC7E37B401 for ; Wed, 17 Jan 2001 03:38:50 -0800 (PST) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.11.1/8.11.0) with ESMTP id f0HBgeu03897 for ; Wed, 17 Jan 2001 12:42:41 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Wed, 17 Jan 2001 12:42:39 +0100 (CET) From: "O. Hartmann" To: freebsd-stable@freebsd.org Subject: shutdown problems in 4.2-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Sirs. One of our UNIX machines running FreeBSD 4.2-STABLE (cvsupdated today) has permanent shutdown problems. The phenomenon: When typing "shutdown -r now" the system reports shutting down immediately. But it never shuts down. There is also no shutdown process. The only way to reboot is "reboot". Otherwise system is always up, without reporting anymore that it will be shutting down. This is the dmesg output: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Wed Jan 17 10:54:41 CET 2001 root@wetter.physik.uni-mainz.de:/usr/local/obj/usr/src/sys/WETTER Timecounter "i8254" frequency 1193191 Hz CPU: AMD Athlon(tm) Processor (807.19-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> real memory = 268353536 (262064K bytes) avail memory = 257703936 (251664K bytes) Preloaded elf kernel "kernel" at 0xc0351000. Preloaded elf module "agp.ko" at 0xc035109c. Pentium Pro MTRR support enabled apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xe4000000-0xe7ffffff at device 0.0 on pci0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 5 pci0: at 4.3 irq 5 fxp0: port 0xa400-0xa43f mem 0xdf000000-0xdf0fffff,0xdf800000-0xdf800fff irq 10 at device 11.0 on pci0 fxp0: Ethernet address 00:02:b3:17:99:90 atapci1: port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem 0xde800000-0xde81ffff irq 10 at device 17.0 on pci0 ata2: at 0xa000 on atapci1 ata3: at 0x9400 on atapci1 pcib1: on motherboard pci2: on pcib1 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <8 virtual consoles, flags=0x200> fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port DUMMYNET initialized (000608) IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, unlimited logging IPsec: Initialized Security Association Processing. ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ata3-slave: ata_command: timeout waiting for intr ata3-slave: identify failed ata3-master: ata_command: timeout waiting for intr ata3-master: identify failed ad4: 29314MB [59560/16/63] at ata2-master UDMA100 acd0: CDROM at ata1-master using WDMA2 Mounting root from ufs:/dev/ad4s1a Does anyone have any idea what's going on? Thanks in advance, Oliver - MfG O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver-Abteilung des IPA IT Netz- und Systembetreuung Johannes Gutenberg-Universitaet Mainz Becherweg 21 D-55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 3:53:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lynx.aba.net.au (lynx.esec.com.au [203.21.84.1]) by hub.freebsd.org (Postfix) with SMTP id AD4DD37B400 for ; Wed, 17 Jan 2001 03:53:16 -0800 (PST) Received: (qmail 2801 invoked from network); 17 Jan 2001 11:53:07 -0000 Received: from melb-dialin21.esec.com.au (HELO esec.com.au) (203.25.253.85) by lynx.esec.com.au with SMTP; 17 Jan 2001 11:53:07 -0000 Message-ID: <3A65868E.2CE114AD@esec.com.au> Date: Wed, 17 Jan 2001 22:48:31 +1100 From: sam wun Organization: eSec Limited X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "O. Hartmann" Cc: freebsd-stable@freebsd.org Subject: Re: shutdown problems in 4.2-STABLE References: Content-Type: multipart/alternative; boundary="------------AADDAFA1BB5852766D9DF480" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --------------AADDAFA1BB5852766D9DF480 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit You will need to recomplie your kernel config file with the following options: device apm0 at nexus? flags 0x20 # Advanced Power Management "O. Hartmann" wrote: > Dear Sirs. > > One of our UNIX machines running FreeBSD 4.2-STABLE (cvsupdated today) > has permanent shutdown problems. > > The phenomenon: > > When typing "shutdown -r now" the system reports shutting down immediately. > But it never shuts down. There is also no shutdown process. The only way to > reboot is "reboot". Otherwise system is always up, without reporting anymore > that it will be shutting down. > > This is the dmesg output: > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.2-STABLE #0: Wed Jan 17 10:54:41 CET 2001 > root@wetter.physik.uni-mainz.de:/usr/local/obj/usr/src/sys/WETTER > Timecounter "i8254" frequency 1193191 Hz > CPU: AMD Athlon(tm) Processor (807.19-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 > Features=0x183f9ff > AMD Features=0xc0440000<,AMIE,DSP,3DNow!> > real memory = 268353536 (262064K bytes) > avail memory = 257703936 (251664K bytes) > Preloaded elf kernel "kernel" at 0xc0351000. > Preloaded elf module "agp.ko" at 0xc035109c. > Pentium Pro MTRR support enabled > apm0: on motherboard > apm: found APM BIOS v1.2, connected at v1.2 > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > agp0: mem 0xe4000000-0xe7ffffff at device 0.0 on pci0 > pcib2: at device 1.0 on pci0 > pci1: on pcib2 > pci1: at 0.0 irq 11 > isab0: at device 4.0 on pci0 > isa0: on isab0 > atapci0: port 0xd800-0xd80f at device 4.1 on pci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: at 4.2 irq 5 > pci0: at 4.3 irq 5 > fxp0: port 0xa400-0xa43f mem 0xdf000000-0xdf0fffff,0xdf800000-0xdf800fff irq 10 at device 11.0 on pci0 > fxp0: Ethernet address 00:02:b3:17:99:90 > atapci1: port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem 0xde800000-0xde81ffff irq 10 at device 17.0 on > pci0 > ata2: at 0xa000 on atapci1 > ata3: at 0x9400 on atapci1 > pcib1: on motherboard > pci2: on pcib1 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <8 virtual consoles, flags=0x200> > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/8 bytes threshold > lpt0: on ppbus0 > lpt0: Interrupt-driven port > DUMMYNET initialized (000608) > IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, unlimited logging > IPsec: Initialized Security Association Processing. > ata1-slave: ata_command: timeout waiting for intr > ata1-slave: identify failed > ata3-slave: ata_command: timeout waiting for intr > ata3-slave: identify failed > ata3-master: ata_command: timeout waiting for intr > ata3-master: identify failed > ad4: 29314MB [59560/16/63] at ata2-master UDMA100 > acd0: CDROM at ata1-master using WDMA2 > Mounting root from ufs:/dev/ad4s1a > > Does anyone have any idea what's going on? > > Thanks in advance, > > Oliver > > - > MfG > O. Hartmann > ------------------------------------------------------------------- > ohartman@ipamzlx.physik.uni-mainz.de > > Klimadatenserver-Abteilung des IPA > IT Netz- und Systembetreuung > Johannes Gutenberg-Universitaet Mainz > Becherweg 21 > D-55099 Mainz > > Tel: +496131/3924662 (Maschinensaal) > Tel: +496131/3924144 > FAX: +496131/3923532 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Sam Wun Firewalls / Security Software Engineer (Snr) Electronic Commerce eSec Limited Phone: +61 3 83715376 (Direct) Mobile: 0403 381 621 mailto:swun@eSec.com.au C++/JAVA/UNIX/OOP/OOD --------------AADDAFA1BB5852766D9DF480 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit You will need to recomplie your kernel config file with the following options:
device          apm0    at nexus? flags 0x20 # Advanced Power Management

"O. Hartmann" wrote:

Dear Sirs.

One of our UNIX machines running FreeBSD 4.2-STABLE (cvsupdated today)
has permanent shutdown problems.

The phenomenon:

When typing "shutdown -r now" the system reports shutting down immediately.
But it never shuts down. There is also no shutdown process. The only way to
reboot is "reboot". Otherwise system is always up, without reporting anymore
that it will be shutting down.

This is the dmesg output:

Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD 4.2-STABLE #0: Wed Jan 17 10:54:41 CET 2001
    root@wetter.physik.uni-mainz.de:/usr/local/obj/usr/src/sys/WETTER
Timecounter "i8254"  frequency 1193191 Hz
CPU: AMD Athlon(tm) Processor (807.19-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x642  Stepping = 2
  Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
  AMD Features=0xc0440000<<b18>,AMIE,DSP,3DNow!>
real memory  = 268353536 (262064K bytes)
avail memory = 257703936 (251664K bytes)
Preloaded elf kernel "kernel" at 0xc0351000.
Preloaded elf module "agp.ko" at 0xc035109c.
Pentium Pro MTRR support enabled
apm0: <APM BIOS> on motherboard
apm: found APM BIOS v1.2, connected at v1.2
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
agp0: <VIA Generic host to PCI bridge> mem 0xe4000000-0xe7ffffff at device 0.0 on pci0
pcib2: <PCI to PCI bridge (vendor=1106 device=8305)> at device 1.0 on pci0
pci1: <PCI bus> on pcib2
pci1: <NVidia Riva TNT2 graphics accelerator> at 0.0 irq 11
isab0: <VIA 82C686 PCI-ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C686 ATA66 controller> port 0xd800-0xd80f at device 4.1 on pci0
ata1: at 0x170 irq 15 on atapci0
pci0: <VIA 83C572 USB controller> at 4.2 irq 5
pci0: <VIA 83C572 USB controller> at 4.3 irq 5
fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xa400-0xa43f mem 0xdf000000-0xdf0fffff,0xdf800000-0xdf800fff irq 10 at device 11.0 on pci0
fxp0: Ethernet address 00:02:b3:17:99:90
atapci1: <Promise ATA100 controller> port 0x8800-0x883f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem 0xde800000-0xde81ffff irq 10 at device 17.0 on
pci0
ata2: at 0xa000 on atapci1
ata3: at 0x9400 on atapci1
pcib1: <Host to PCI bridge> on motherboard
pci2: <PCI bus> on pcib1
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> on isa0
sc0: VGA <8 virtual consoles, flags=0x200>
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
DUMMYNET initialized (000608)
IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to deny, unlimited logging
IPsec: Initialized Security Association Processing.
ata1-slave: ata_command: timeout waiting for intr
ata1-slave: identify failed
ata3-slave: ata_command: timeout waiting for intr
ata3-slave: identify failed
ata3-master: ata_command: timeout waiting for intr
ata3-master: identify failed
ad4: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata2-master UDMA100
acd0: CDROM <CD-ROM 48X/AKH> at ata1-master using WDMA2
Mounting root from ufs:/dev/ad4s1a

Does anyone have any idea what's going on?

Thanks in advance,

Oliver

-
MfG
O. Hartmann
-------------------------------------------------------------------
ohartman@ipamzlx.physik.uni-mainz.de

Klimadatenserver-Abteilung des IPA
IT Netz- und Systembetreuung
Johannes Gutenberg-Universitaet Mainz
Becherweg 21
D-55099 Mainz

Tel: +496131/3924662 (Maschinensaal)
Tel: +496131/3924144
FAX: +496131/3923532

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message

-- 
Sam Wun                         Firewalls / Security
Software Engineer (Snr)         Electronic Commerce
eSec Limited                    Phone: +61 3 83715376 (Direct)
                                Mobile: 0403 381 621
mailto:swun@eSec.com.au         C++/JAVA/UNIX/OOP/OOD
  --------------AADDAFA1BB5852766D9DF480-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 4:19:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 8271D37B401 for ; Wed, 17 Jan 2001 04:19:35 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 17 Jan 2001 12:17:32 +0000 (GMT) Date: Wed, 17 Jan 2001 12:17:31 +0000 From: David Malone To: sam wun Cc: "O. Hartmann" , freebsd-stable@freebsd.org Subject: Re: shutdown problems in 4.2-STABLE Message-ID: <20010117121731.A31988@walton.maths.tcd.ie> References: <3A65868E.2CE114AD@esec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A65868E.2CE114AD@esec.com.au>; from swun@esec.com.au on Wed, Jan 17, 2001 at 10:48:31PM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 17, 2001 at 10:48:31PM +1100, sam wun wrote: > You will need to recomplie your kernel config file with the following options: > device apm0 at nexus? flags 0x20 # Advanced Power Management If "reboot" works but "shutdown -r" doesn't, thent I don't see how it could be a kernel problem 'cos shutdown just runs reboot. It sounds like some sort of problem in the userland shutdown program. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 4:20:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.cb21.co.jp (ns1.cb21.co.jp [203.140.149.254]) by hub.freebsd.org (Postfix) with SMTP id F39C337B404 for ; Wed, 17 Jan 2001 04:20:00 -0800 (PST) Received: (qmail 61726 invoked from network); 17 Jan 2001 21:19:59 +0900 Received: from localhost.cb21.co.jp (HELO localhost) (127.0.0.1) by localhost.cb21.co.jp with SMTP; 17 Jan 2001 21:19:59 +0900 To: kris@FreeBSD.ORG Cc: freebsd-stable@FreeBSD.ORG Subject: Re: New features in 4.3-RELEASE From: Sys Admin In-Reply-To: <20010114160612.C14278@citusc.usc.edu> References: <20010114160612.C14278@citusc.usc.edu> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010117211959G.admin@cb21.co.jp> Date: Wed, 17 Jan 2001 21:19:59 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 25 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Kris, > > We currently have 4.1 machines and are planning to upgrade soon mainly to > > get improved AMI RAID support. Is it worthwhile to wait for 4.3-R ? > > > > Any pointers to the new features coming in 4.3R (particularly RAID > > support) ? > > See the release notes in > /usr/src/release/texts/{i386,alpha}/RELNOTES.TXT in 4.2-STABLE for > features added since 4.2-R > Do I need to track stable to get this file ? I have checked the stable branche at the ftp serevr and couldn't find a 4.2-STABLE. (Haven't I looked hard enough?) In 4.x-STABLE, RELENOTES.TXT is nearly the same as one in 4.0-RELEASE. ftp.freebsd.org/pub.FreeBSD/FreeBSD-Stable/src/release/texts/i386/RELENOTES.TXT has a datestamp of 3/18. Am I looking at the wrong file ? Thanks. Tad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 5:49:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rhymer.cogsci.ed.ac.uk (rhymer.cogsci.ed.ac.uk [129.215.144.8]) by hub.freebsd.org (Postfix) with ESMTP id 57CE337B400; Wed, 17 Jan 2001 05:48:53 -0800 (PST) Received: (from richard@localhost) by rhymer.cogsci.ed.ac.uk (8.9.3+Sun/8.9.3) id NAA15355; Wed, 17 Jan 2001 13:48:41 GMT Date: Wed, 17 Jan 2001 13:48:41 GMT Message-Id: <200101171348.NAA15355@rhymer.cogsci.ed.ac.uk> From: Richard Tobin Subject: Re: New features in 4.3-RELEASE To: Sys Admin , kris@FreeBSD.ORG In-Reply-To: Sys Admin's message of Wed, 17 Jan 2001 21:19:59 +0900 Organization: just say no Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > See the release notes in > > /usr/src/release/texts/{i386,alpha}/RELNOTES.TXT in 4.2-STABLE for > > features added since 4.2-R > > > > Do I need to track stable to get this file ? Go to http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/texts/i386/?only_with_tag=RELENG_4 And select the displayed revision of RELNOTES.TXT. -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 6:28:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.cb21.co.jp (ns1.cb21.co.jp [203.140.149.254]) by hub.freebsd.org (Postfix) with SMTP id 3B48637B699 for ; Wed, 17 Jan 2001 06:28:25 -0800 (PST) Received: (qmail 79948 invoked from network); 17 Jan 2001 23:28:22 +0900 Received: from localhost.cb21.co.jp (HELO localhost) (127.0.0.1) by localhost.cb21.co.jp with SMTP; 17 Jan 2001 23:28:22 +0900 To: richard@cogsci.ed.ac.uk Cc: kris@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: New features in 4.3-RELEASE From: Sys Admin In-Reply-To: <200101171348.NAA15355@rhymer.cogsci.ed.ac.uk> References: <200101171348.NAA15355@rhymer.cogsci.ed.ac.uk> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010117232822F.admin@cb21.co.jp> Date: Wed, 17 Jan 2001 23:28:22 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 24 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Richard, > > > See the release notes in > > > /usr/src/release/texts/{i386,alpha}/RELNOTES.TXT in 4.2-STABLE for > > > features added since 4.2-R > > > > > > > Do I need to track stable to get this file ? > > Go to > > http://www.FreeBSD.org/cgi/cvsweb.cgi/src/release/texts/i386/?only_with_tag=RELENG_4 > > And select the displayed revision of RELNOTES.TXT. Thank you very much. I got all the info I wanted. Getting to know about the ability to search through the entire source tree is indeed great. This should drastically cut down the number of questions that I may have in the future! Thanks again. Tad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 7:19:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id AE66337B400; Wed, 17 Jan 2001 07:19:22 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14IuLS-000AI0-00; Wed, 17 Jan 2001 18:18:02 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14IuMv-0004j4-00; Wed, 17 Jan 2001 18:19:25 +0300 Date: Wed, 17 Jan 2001 18:19:24 +0300 From: Courvette To: FBSD-Q Cc: FBSD-STABLE Subject: Help with Tape Drive Message-ID: <20010117181924.A18085@poeza.iconnect.co.ke> Mail-Followup-To: Courvette , FBSD-Q , FBSD-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD poeza.iconnect.co.ke 4.2-STABLE FreeBSD 4.2-STABLE X-Location: Mombasa, KE, East Africa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello Pals, Someone can help me with this one. After an upgrade to 4.2-STABLE from 3.5-STABLE I am unable to use my tape drive -and consequently can't do backups - we all know how serious that is.... I am in a dilemna:: wash:~$ mt status mt: /dev/nsa0: Device not configured +++++ wash:~$ cd /dev/ wash:/dev$ ls -al *sa0 crw-rw---- 4 root operator 14, 2 Jan 17 18:10 ersa0 crw-rw---- 4 root operator 14, 2 Jan 17 18:10 esa0 crw-rw---- 4 root operator 14, 1 Jan 17 18:10 nrsa0 crw-rw---- 4 root operator 14, 1 Jan 17 18:10 nsa0 crw-rw---- 4 root operator 14, 0 Jan 17 18:10 rsa0 crw-rw---- 4 root operator 14, 0 Jan 17 18:10 sa0 wash:/dev$ -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. Men for the sake of getting a living forget to live. -Margaret Fuller To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 7:28: 9 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 194A037B404; Wed, 17 Jan 2001 07:27:48 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id QAA42700; Wed, 17 Jan 2001 16:26:15 +0100 (CET) (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: Courvette Cc: FBSD-Q , FBSD-STABLE Subject: Re: Help with Tape Drive References: <20010117181924.A18085@poeza.iconnect.co.ke> From: Dag-Erling Smorgrav Date: 17 Jan 2001 16:26:14 +0100 In-Reply-To: Courvette's message of "Wed, 17 Jan 2001 18:19:24 +0300" Message-ID: Lines: 13 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Courvette writes: > I am in a dilemna:: No, you're not. A dilemma is a situation with several possible outcomes, all of which are deemed equally unfavorable. You're in a quandary, or possibly a predicament, not a dilemma. If you want help with your predicament, please provide the output from dmesg and a copy of your kernel config. 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 Wed Jan 17 7:48:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kciLink.com [208.184.13.195]) by hub.freebsd.org (Postfix) with ESMTP id 8644437B69B for ; Wed, 17 Jan 2001 07:48:31 -0800 (PST) Received: by yertle.kciLink.com (Postfix, from userid 100) id B29692E440; Wed, 17 Jan 2001 10:48:30 -0500 (EST) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14949.48846.652776.97393@yertle.kciLink.com> Date: Wed, 17 Jan 2001 10:48:30 -0500 To: freebsd-stable@freebsd.org Subject: RE: sshd not working after upgrade to 4.2S from 4.1R HELP In-Reply-To: References: <200101151857.SAA67739@ns.a1.org.uk> X-Mailer: VM 6.88 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "RB" == Robert Banniza writes: RB> I just cvsup'ed 4.2R to 4.2 stable as of today and like others I'm getting RB> errors with the libssl portion. This is also causing Apache not to startup RB> as well as causing problems with ssh. I saw on the list where other had RB> mentioned running merge master and I did but it didn't seem to help. Can For mod_ssl, you need to recompile it. There is a binary incompatibility with the SSL libs at some point between 4.2-R and some time in December. As for ssh not working, what errors are you getting (assuming it is not the pam errors.) I did an upgrade on monday and had no problems because the pam config lines were added. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 8:27:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.inorth.com (natted.inscriber.com [209.167.77.135]) by hub.freebsd.org (Postfix) with ESMTP id 40F6037B401 for ; Wed, 17 Jan 2001 08:27:19 -0800 (PST) Received: from kakkoii.inorth.com ([10.0.0.29]) by mail.inorth.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id VNW6GL7H; Wed, 17 Jan 2001 11:27:14 -0500 Received: (from gdunn@localhost) by kakkoii.inorth.com (8.11.1/8.11.1) id f0HGSMk57669 for stable@FreeBSD.ORG; Wed, 17 Jan 2001 11:28:22 -0500 (EST) (envelope-from gdunn) Date: Wed, 17 Jan 2001 11:28:22 -0500 From: Graham To: stable@FreeBSD.ORG Subject: Problems with make buildworld on RELENG-3 alpha. Message-ID: <20010117112821.A56298@inscriber.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-RELEASE X-PGP-Fingerprint: 3F 56 12 9B 8A E1 77 CB F0 62 94 B0 93 06 1E 88 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable tracking RELENG_3 via cvsup (src-all, scr-crypto, src-secure, ports-all) for the alpha platform. make buildworld dies at this point: cc -O -pipe -DVINUMDEBUG -g -O -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/vinum -I/usr/obj/usr/src/sys/modules/vinum/@ -I/usr/obj/usr/src/tmp/usr/include -mno-fp-regs -Wa,-mev56 -c /usr/src/sys/modules/vinum/../../dev/vinum/vinummemory.c /usr/src/sys/modules/vinum/../../dev/vinum/vinummemory.c: In function `MMalloc': /usr/src/sys/modules/vinum/../../dev/vinum/vinummemory.c:154: `intr_nesting_level' undeclared (first use this function) /usr/src/sys/modules/vinum/../../dev/vinum/vinummemory.c:154: (Each undeclared identifier is reported only once /usr/src/sys/modules/vinum/../../dev/vinum/vinummemory.c:154: for each function it appears in.) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Any ideas? --=20 gdunn@inscriber.com Graham Dunn || ||| | ||| |||| | |||| |=20 --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQCVAwUBOmXII2kO9W16Wx1FAQG3pAQAoqAAeuVhIBc7IzNfzOPnGD/e9pmo6/Pl ZQ7yS37AtlBSknCmnYaE1rRoimzVR5WbF0mdpRc/lKAsYP9CTJjOearRB9K3icvH IwQboRuht9JoSpTQK2ptTmedMJF6wsZMZMb5Oe6oKQQ76+pgSA2MWQByaJh4kWVr TaJLIW/mcmw= =rbeC -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 8:30: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 6B34B37B69B; Wed, 17 Jan 2001 08:29:34 -0800 (PST) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14IvSk-0002PP-00; Wed, 17 Jan 2001 16:29:30 +0000 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f0HGTTc58536; Wed, 17 Jan 2001 16:29:29 GMT (envelope-from rasputin) Date: Wed, 17 Jan 2001 16:29:29 +0000 From: Rasputin To: freebsd-mobile@freebsd.org Cc: freebsd-stable@freebsd.org Subject: BSD box as Airport replacement? Message-ID: <20010117162929.A58519@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's plan of the month; fit a cablemodem-connected BSD box with a wireless NIC and run it as a gateway for iBooks. I know nothing about wireless networking, just thought it would be cool. Are there any gotchas with regard to the clients (iBook, maybe a Vaio)? And what NICs would people recommend? (Range required is < 50 ft if that matters; BSD box is upstairs, I'll be in the garden with a beer..) Thanks a lot. -- 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 Wed Jan 17 8:42: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from drella.dilex.net (unknown [64.94.143.193]) by hub.freebsd.org (Postfix) with ESMTP id C363B37B400; Wed, 17 Jan 2001 08:41:40 -0800 (PST) Received: (wyllie@drella.newsof.com) by drella.newsof.com id ; Wed, 17 Jan 2001 08:41:16 -0800 Date: Wed, 17 Jan 2001 08:41:16 -0800 From: Andrew Wyllie To: Rasputin Cc: freebsd-mobile@freebsd.org, freebsd-stable@freebsd.org Subject: Re: BSD box as Airport replacement? Message-ID: <20010117084116.A22875@drella.newsof.com> Reply-To: wyllie@dilex.net References: <20010117162929.A58519@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: <20010117162929.A58519@dogma.freebsd-uk.eu.org>; from rasputin@FreeBSD-uk.eu.org on Wed, Jan 17, 2001 at 04:29:29PM +0000 Organization: Dilex Networks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Rasputin, I bought the Orinoco (Lucent WaveLAN cards - the "Gold" version ). I used an old 486/100 with 16MB ram and a 500MB drive and this paper: http://www.live.com/wireless/unix-base-station.html It works great. My base station is in the basement and I can use it from all over the house and part way down the street ( the cards say they work up to 1700 feet - outside ). have fun andrew On Wed, 17 Jan 2001, Rasputin wrote: > That's plan of the month; > fit a cablemodem-connected BSD box with a wireless NIC and > run it as a gateway for iBooks. > > I know nothing about wireless networking, just thought it would be cool. > Are there any gotchas with regard to the clients (iBook, maybe a Vaio)? > > And what NICs would people recommend? > (Range required is < 50 ft if that matters; > BSD box is upstairs, I'll be in the > garden with a beer..) > > Thanks a lot. > > -- > 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 ............................................................................... Andrew Wyllie Open Source Integrator v.206.729.7439 __We can catify or stringify, c.206.851.9876 separately or together!__ perl-5.005_03 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 8:50:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 5A2BE37B401; Wed, 17 Jan 2001 08:50:14 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0HGnm422364; Wed, 17 Jan 2001 08:49:48 -0800 (PST) Date: Wed, 17 Jan 2001 08:49:48 -0800 From: Alfred Perlstein To: Dag-Erling Smorgrav Cc: Courvette , FBSD-Q , FBSD-STABLE Subject: Re: Help with Tape Drive Message-ID: <20010117084948.N7240@fw.wintelcom.net> References: <20010117181924.A18085@poeza.iconnect.co.ke> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Wed, Jan 17, 2001 at 04:26:14PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dag-Erling Smorgrav [010117 07:28] wrote: > Courvette writes: > > I am in a dilemna:: > > No, you're not. A dilemma is a situation with several possible > outcomes, all of which are deemed equally unfavorable. You're in a > quandary, or possibly a predicament, not a dilemma. > > If you want help with your predicament, please provide the output from > dmesg and a copy of your kernel config. I think he could might at a favorable outcome if he was to read /usr/src/UPDATING, specifically the section about device nodes changes from 3.x->4.x. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 8:53:25 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 E9C2437B400; Wed, 17 Jan 2001 08:53:05 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA43112; Wed, 17 Jan 2001 17:53:02 +0100 (CET) (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: Alfred Perlstein Cc: Courvette , FBSD-Q , FBSD-STABLE Subject: Re: Help with Tape Drive References: <20010117181924.A18085@poeza.iconnect.co.ke> <20010117084948.N7240@fw.wintelcom.net> From: Dag-Erling Smorgrav Date: 17 Jan 2001 17:53:02 +0100 In-Reply-To: Alfred Perlstein's message of "Wed, 17 Jan 2001 08:49:48 -0800" Message-ID: Lines: 10 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein writes: > I think he could might at a favorable outcome if he was to read > /usr/src/UPDATING, specifically the section about device nodes > changes from 3.x->4.x. No, his device nodes are correct. See the first mail in the thread. 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 Wed Jan 17 8:59: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 2D05E37B400; Wed, 17 Jan 2001 08:58:45 -0800 (PST) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 2.05 #4) id 14Ivv2-0002wT-00; Wed, 17 Jan 2001 16:58:44 +0000 Received: (from rasputin@localhost) by dogma.freebsd-uk.eu.org (8.11.1/8.11.1) id f0HGwiZ58969; Wed, 17 Jan 2001 16:58:44 GMT (envelope-from rasputin) Date: Wed, 17 Jan 2001 16:58:43 +0000 From: Rasputin To: freebsd-stable@freebsd.org Cc: freebsd-mobile@freebsd.org Subject: Re: BSD box as Airport replacement? Message-ID: <20010117165843.A58911@dogma.freebsd-uk.eu.org> References: <20010117162929.A58519@dogma.freebsd-uk.eu.org> <20010117084116.A22875@drella.newsof.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010117084116.A22875@drella.newsof.com>; from wyllie@dilex.net on Wed, Jan 17, 2001 at 08:41:16AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Andrew Wyllie [010117 16:43]: > Hi Rasputin, > > I bought the Orinoco (Lucent WaveLAN cards - the "Gold" version ). > I used an old 486/100 with 16MB ram and a 500MB drive and this paper: > > http://www.live.com/wireless/unix-base-station.html > > It works great. My base station is in the basement and I can use it > from all over the house and part way down the street ( the cards say > they work up to 1700 feet - outside ). > Cheers Andrew, that'll do me fine. One more question: With a range like that, how do you stop Evil Granny Smith at number 23 from sniffing your network traffic? Is there crypto built into the IEEE802.11 spec? And is it any good? -- 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 Wed Jan 17 9: 6:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from post.smarty.net (unknown [195.12.1.12]) by hub.freebsd.org (Postfix) with SMTP id C07E637B402 for ; Wed, 17 Jan 2001 09:06:18 -0800 (PST) Received: (qmail 47515 invoked from network); 17 Jan 2001 17:07:45 -0000 Received: from herculeez.demon.co.uk (HELO athena.hq.herculeez.com) (158.152.217.198) by hercules.hiway.co.uk with SMTP; 17 Jan 2001 17:07:45 -0000 Received: (qmail 42221 invoked from network); 17 Jan 2001 17:05:38 -0000 Received: from madoka.hq.herculeez.com (HELO herculeez.com) (192.168.0.23) by athena.hq.herculeez.com with SMTP; 17 Jan 2001 17:05:38 -0000 Message-ID: <3A65D103.D815E92@herculeez.com> Date: Wed, 17 Jan 2001 17:06:11 +0000 From: Simon Loader Reply-To: simon@surf.org.uk Organization: simon@surf.org.uk X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.2-RELEASE i386) X-Accept-Language: en, fr, de, cs MIME-Version: 1.0 To: Rasputin Cc: freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: BSD box as Airport replacement? References: <20010117162929.A58519@dogma.freebsd-uk.eu.org> <20010117084116.A22875@drella.newsof.com> <20010117165843.A58911@dogma.freebsd-uk.eu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rasputin wrote: > > * Andrew Wyllie [010117 16:43]: > > Hi Rasputin, > > > > I bought the Orinoco (Lucent WaveLAN cards - the "Gold" version ). > > I used an old 486/100 with 16MB ram and a 500MB drive and this paper: > > > > http://www.live.com/wireless/unix-base-station.html > > > > It works great. My base station is in the basement and I can use it > > from all over the house and part way down the street ( the cards say > > they work up to 1700 feet - outside ). > > > > Cheers Andrew, that'll do me fine. One more question: > With a range like that, how do you stop Evil Granny Smith > at number 23 from sniffing your network traffic? > > Is there crypto built into the IEEE802.11 spec? > And is it any good? > With the gold version there is I think silver doesnt -- Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:16:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from isris.pair.com (isris.pair.com [209.68.2.39]) by hub.freebsd.org (Postfix) with SMTP id C50B837B401 for ; Wed, 17 Jan 2001 09:16:27 -0800 (PST) Received: (qmail 83056 invoked by uid 3130); 17 Jan 2001 17:16:26 -0000 Date: Wed, 17 Jan 2001 12:16:26 -0500 From: Garrett Rooney To: simon@surf.org.uk Cc: Rasputin , freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: BSD box as Airport replacement? Message-ID: <20010117121626.A87600@electricjellyfish.net> Mail-Followup-To: Garrett Rooney , simon@surf.org.uk, Rasputin , freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org References: <20010117162929.A58519@dogma.freebsd-uk.eu.org> <20010117084116.A22875@drella.newsof.com> <20010117165843.A58911@dogma.freebsd-uk.eu.org> <3A65D103.D815E92@herculeez.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A65D103.D815E92@herculeez.com>; from simon@herculeez.com on Wed, Jan 17, 2001 at 05:06:11PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 17, 2001 at 05:06:11PM +0000, Simon Loader wrote: > Rasputin wrote: > > > > * Andrew Wyllie [010117 16:43]: > > > Hi Rasputin, > > > > > > I bought the Orinoco (Lucent WaveLAN cards - the "Gold" version ). > > > I used an old 486/100 with 16MB ram and a 500MB drive and this paper: > > > > > > http://www.live.com/wireless/unix-base-station.html > > > > > > It works great. My base station is in the basement and I can use it > > > from all over the house and part way down the street ( the cards say > > > they work up to 1700 feet - outside ). > > > > > > > Cheers Andrew, that'll do me fine. One more question: > > With a range like that, how do you stop Evil Granny Smith > > at number 23 from sniffing your network traffic? > > > > Is there crypto built into the IEEE802.11 spec? > > And is it any good? > > > > With the gold version there is I think silver doesnt Silver and Gold both have crypto, although the silver is lower strength. Bronze is the version that does not. -garrett -- garrett rooney my pid is inigo montoya. rooneg@electricjellyfish.net you kill -9 my parent process. http://electricjellyfish.net/ prepare to vi. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:17:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tao.org.uk (unknown [194.128.198.234]) by hub.freebsd.org (Postfix) with ESMTP id 7BD9937B699; Wed, 17 Jan 2001 09:16:58 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id BF50F31BA; Wed, 17 Jan 2001 17:16:58 +0000 (GMT) Date: Wed, 17 Jan 2001 17:16:58 +0000 From: Josef Karthauser To: simon@surf.org.uk Cc: Rasputin , freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: BSD box as Airport replacement? Message-ID: <20010117171658.B3832@tao.org.uk> Mail-Followup-To: Josef Karthauser , simon@surf.org.uk, Rasputin , freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG References: <20010117162929.A58519@dogma.freebsd-uk.eu.org> <20010117084116.A22875@drella.newsof.com> <20010117165843.A58911@dogma.freebsd-uk.eu.org> <3A65D103.D815E92@herculeez.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A65D103.D815E92@herculeez.com>; from simon@herculeez.com on Wed, Jan 17, 2001 at 05:06:11PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 17, 2001 at 05:06:11PM +0000, Simon Loader wrote: > > With the gold version there is I think silver doesnt > I thought that the silver version _did_ have but the bronze doesn't. Difference between silver and gold is the amount of crypt and of course speed. Dave Doolie or Brian Somers may know more -> guys? Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:20:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hobbiton.shire.net (frogmorton.shire.net [204.228.145.136]) by hub.freebsd.org (Postfix) with ESMTP id 5E18437B404; Wed, 17 Jan 2001 09:20:04 -0800 (PST) Received: from [216.64.45.172] (helo=[192.168.99.123]) by hobbiton.shire.net with esmtp (Exim 2.04 #5) id 14IwFa-00047P-00; Wed, 17 Jan 2001 10:19:58 -0700 Date: Wed, 17 Jan 2001 12:12:29 -0500 From: "Chad Leigh, Pengar Enterprises, Inc & Shire.Net LLC" Reply-To: chad@pengar.com To: simon@surf.org.uk, Rasputin Cc: freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: BSD box as Airport replacement? Message-ID: <481005824.979733549@[192.168.99.123]> In-Reply-To: <3A65D103.D815E92@herculeez.com> X-Mailer: Mulberry/2.0.5 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --On Wednesday, January 17, 2001 5:06 PM +0000 Simon Loader wrote: > Rasputin wrote: >> >> >> Cheers Andrew, that'll do me fine. One more question: >> With a range like that, how do you stop Evil Granny Smith >> at number 23 from sniffing your network traffic? >> >> Is there crypto built into the IEEE802.11 spec? >> And is it any good? >> > > With the gold version there is I think silver doesnt > The silver and gold both have encryption. SIlver has weaker version of encryption. At least that was the way it was last summer when I bought my gold . chad Pengar Enterprises, Inc. and Shire.Net LLC Web and Macintosh Consulting -- full service web hosting Chad Leigh chad@pengar.com chad@shire.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:22:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id BE9D837B404; Wed, 17 Jan 2001 09:22:29 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0HHL5s38482; Wed, 17 Jan 2001 10:21:05 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101171721.f0HHL5s38482@harmony.village.org> To: simon@surf.org.uk Subject: Re: BSD box as Airport replacement? Cc: Rasputin , freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG In-reply-to: Your message of "Wed, 17 Jan 2001 17:06:11 GMT." <3A65D103.D815E92@herculeez.com> References: <3A65D103.D815E92@herculeez.com> <20010117162929.A58519@dogma.freebsd-uk.eu.org> <20010117084116.A22875@drella.newsof.com> <20010117165843.A58911@dogma.freebsd-uk.eu.org> Date: Wed, 17 Jan 2001 10:21:05 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A65D103.D815E92@herculeez.com> Simon Loader writes: : With the gold version there is I think silver doesnt Gold is 128 bits of encryption. Silver is only 64 or 96. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:26:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from romeo.rtfm.com (c1274607-a.stcla1.sfba.home.com [65.0.252.29]) by hub.freebsd.org (Postfix) with ESMTP id 3B6A137B6A4; Wed, 17 Jan 2001 09:25:50 -0800 (PST) Received: (ekr@localhost) by romeo.rtfm.com (8.9.3/8.6.4) id JAA18304; Wed, 17 Jan 2001 09:29:58 -0800 (PST) To: simon@surf.org.uk Cc: Rasputin , freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: BSD box as Airport replacement? References: <20010117162929.A58519@dogma.freebsd-uk.eu.org> <20010117084116.A22875@drella.newsof.com> <20010117165843.A58911@dogma.freebsd-uk.eu.org> <3A65D103.D815E92@herculeez.com> Reply-To: EKR Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Eric Rescorla Date: 17 Jan 2001 09:29:58 -0800 In-Reply-To: Simon Loader's message of "Wed, 17 Jan 2001 17:06:11 +0000" Message-ID: Lines: 32 X-Mailer: Gnus v5.6.45/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Simon Loader writes: > Rasputin wrote: > > > > * Andrew Wyllie [010117 16:43]: > > > Hi Rasputin, > > > > > > I bought the Orinoco (Lucent WaveLAN cards - the "Gold" version ). > > > I used an old 486/100 with 16MB ram and a 500MB drive and this paper: > > > > > > http://www.live.com/wireless/unix-base-station.html > > > > > > It works great. My base station is in the basement and I can use it > > > from all over the house and part way down the street ( the cards say > > > they work up to 1700 feet - outside ). > > > > > > > Cheers Andrew, that'll do me fine. One more question: > > With a range like that, how do you stop Evil Granny Smith > > at number 23 from sniffing your network traffic? > > > > Is there crypto built into the IEEE802.11 spec? > > And is it any good? > > > > With the gold version there is I think silver doesnt They both have it but it's not very good. The silver is ostensibly 56-bit and the gold is ostensibly 128 bit but it's done badly and thus relatively easy to compromise. -Ekr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:27:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.6.9.33]) by hub.freebsd.org (Postfix) with ESMTP id 56EF237B69F; Wed, 17 Jan 2001 09:27:04 -0800 (PST) Received: from msgrel1.and.agilent.com (msgrel1.and.agilent.com [130.30.33.104]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id D95034FB; Wed, 17 Jan 2001 10:27:03 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.and.agilent.com (Postfix) with ESMTP id 7E6EB18F; Wed, 17 Jan 2001 12:27:02 -0500 (EST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id JAA28206; Wed, 17 Jan 2001 09:27:00 -0800 (PST) Message-Id: <200101171727.JAA28206@mina.soco.agilent.com> To: Rasputin Cc: freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: BSD box as Airport replacement? Reply-To: Darryl Okahata In-Reply-To: Your message of "Wed, 17 Jan 2001 16:58:43 GMT." <20010117165843.A58911@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 (generated by tm-edit 1.6) Content-Type: text/plain; charset=US-ASCII Date: Wed, 17 Jan 2001 09:27:00 -0800 From: Darryl Okahata Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rasputin wrote: > Is there crypto built into the IEEE802.11 spec? Yes. > And is it any good? No. Please search the archives. This topic, and the ones before it, have been beat to death. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:42: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id BEA1A37B400; Wed, 17 Jan 2001 09:41:45 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id JAA27000; Wed, 17 Jan 2001 09:41:45 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id JAA13702; Wed, 17 Jan 2001 09:41:45 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200101171741.JAA13702@curve.dellroad.org> Subject: Re: BSD box as Airport replacement? In-Reply-To: <20010117165843.A58911@dogma.freebsd-uk.eu.org> "from Rasputin at Jan 17, 2001 04:58:43 pm" To: Rasputin Date: Wed, 17 Jan 2001 09:41:44 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rasputin writes: > Is there crypto built into the IEEE802.11 spec? Yes. > And is it any good? Sort of. One problem is that all clients must have the same shared secret, which means it's not much of a secret. Also there are known-plaintext attacks in certain situations, like mixed cells (some clients encrypting, some not). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:42:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 3DA0237B402; Wed, 17 Jan 2001 09:42:10 -0800 (PST) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f0HHeVW01464; Wed, 17 Jan 2001 11:40:31 -0600 (CST) Message-Id: <200101171740.f0HHeVW01464@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: Warner Losh Cc: simon@surf.org.uk, Rasputin , freebsd-stable@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: BSD box as Airport replacement? In-reply-to: Your message of "Wed, 17 Jan 2001 10:21:05 MST." <200101171721.f0HHL5s38482@harmony.village.org> Date: Wed, 17 Jan 2001 11:40:31 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101171721.f0HHL5s38482@harmony.village.org>, Warner Losh writes: >In message <3A65D103.D815E92@herculeez.com> Simon Loader writes: >: With the gold version there is I think silver doesnt >Gold is 128 bits of encryption. Silver is only 64 or 96. As I understand it, 64, except you only get to pick 40 of them, which makes it very confusing. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:54:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 9B3C737B400 for ; Wed, 17 Jan 2001 09:53:47 -0800 (PST) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id JAA01492 for ; Wed, 17 Jan 2001 09:53:46 -0800 (PST) Message-ID: <3A65DC2A.8A15BEE1@isi.edu> Date: Wed, 17 Jan 2001 09:53:46 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: SMP & signal 11 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms9B910C130C3A51300512CD21" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms9B910C130C3A51300512CD21 Content-Type: multipart/mixed; boundary="------------9D5494D50E260A9994CE1B32" This is a multi-part message in MIME format. --------------9D5494D50E260A9994CE1B32 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit [extended repost from -questions, no response there] Hi, processes get killed (signal 11) on a new Dell Precision 620 under moderate load (kernel recompilation). This only happens if I enable the second CPU in the BIOS, and the kernel has SMP enabled. This machine runs FreeBSD 4.2-RELEASE. I know signal 11 is usually an indication of bad RAM or cache memory, but I've been running the Dell system test for over 24 hours, and it shows no defects there. I searched the mailing list, and it seems one other person had a similar problem with a Dell Precision (different model though); in their case, it seemed to be temperature-related. If this is the case here, how would I verify/fix this? Thanks, Lars PS: Attached are the kernel config file and a verbose boot output. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------9D5494D50E260A9994CE1B32 Content-Type: text/plain; charset=us-ascii; name="KERNEL" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="KERNEL" # This allows you to actually store this configuration file into # the kernel binary itself, where it may be later read by saying: # strings -aout -n 3 /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL options INCLUDE_CONFIG_FILE # Include this file in kernel makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU # for our notebooks (Solos/Librettos) cpu I686_CPU # for all other machines ident "KERNEL-1.10" maxusers 128 # Note: Enabling SMP on non-SMP motherboards causes kernel panic early # during boot. To built an automatically-updated kernel for an SMP system, # create /etc/kernel.patch.local (ask Lars for details.) options SMP options APIC_IO #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem #options MD_ROOT #MD is a potential root device options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, NFS required #options MSDOSFS #MSDOS Filesystem #options CD9660 #ISO 9660 Filesystem #options CD9660_ROOT #CD-ROM usable as root, CD9660 required #options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=0 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console #options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device fd1 at fdc0 drive 1 # Libretto PCMCIA floppy drive support device fdc1 at isa? disable port ? irq ? device fd2 at fdc1 drive 0 #device fd3 at fdc1 drive 1 # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives #options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices options ATA_ENABLE_TAGS # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device dpt # DPT Smartcache - See LINT for options! #device isp # Qlogic family #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets) #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device cd # CD #device pass # Passthrough device (direct SCSI access) # RAID controllers #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? disable device pcic1 at isa? disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x90 irq 4 device sio1 at isa? port IO_COM2 irq 3 # Parallel-Port Bus # # Parallel port bus support is provided by the `ppbus' device. # Multiple devices may be attached to the parallel port, devices # are automatically probed and attached when found. # # Supported devices: # vpo Iomega Zip Drive # Requires SCSI disk support ('scbus' and 'da'), best # performance is achieved with ports in EPP 1.9 mode. # lpt Parallel Printer # plip Parallel network interface # ppi General-purpose I/O ("Geek Port") + IEEE1284 I/O # pps Pulse per second Timing Interface # lpbb Philips official parallel port I2C bit-banging interface # # Supported interfaces: # ppc ISA-bus parallel port interfaces. # options PPC_PROBE_CHIPSET # Enable chipset specific detection # (see flags in ppc(4)) #options DEBUG_1284 # IEEE1284 signaling protocol debug #options PERIPH_1284 # Makes your computer act as a IEEE1284 # compliant peripheral #options DONTPROBE_1284 # Avoid boot detection of PnP parallel devices #options VP0_DEBUG # ZIP/ZIP+ debug #options LPT_DEBUG # Printer driver debug #options PPC_DEBUG # Parallel chipset level debug #options PLIP_DEBUG # Parallel network IP interface debug #options PCFCLOCK_VERBOSE # Verbose pcfclock driver #options PCFCLOCK_MAX_RETRIES=5 # Maximum read tries (default 10) device ppc0 at isa? irq 7 device ppbus #device vpo device lpt #device plip #device ppi #device pps #device lpbb #device pcfclock # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device tx # SMC 9432TX (83c170 ``EPIC'') device vx # 3Com 3c590, 3c595 (``Vortex'') device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device ste # Sundance ST201 (D-Link DFE-550TX) #device tl # Texas Instruments ThunderLAN #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 device ed #device ex device ep # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. device an # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device fe0 at isa? port 0x300 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) #pseudo-device md # Memory "disks" # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support # UHCI controller device uhci # OHCI controller device ohci # General USB code (mandatory for USB) device usb # Generic USB device driver device ugen # Human Interface Device (anything with buttons and dials) device uhid # USB keyboard device ukbd # USB printer #device ulpt # USB Iomega Zip 100 Drive #device umass # USB mouse device ums # CPU_FASTER_5X86_FPU enables faster FPU exception handler. #options CPU_FASTER_5X86_FPU # Allow user-mode programs to manipulate their local descriptor tables. # This option is required for the WINE Windows(tm) emulator, and is # not used by anything else (that we know of)# #options USER_LDT #allow user-level control of i386 ldt # TCP_RESTRICT_RST adds support for blocking the emission of TCP RST packets. # This is useful on systems which are exposed to SYN floods (e.g. IRC servers) # or any system which one does not want to be easily portscannable. #options TCP_RESTRICT_RST #restrict emission of TCP RST options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options INET6 #IPv6 communications protocols #options IPSEC_IPV6FWD #IP security tunnel for IPv6 # The `gif' pseudo-device implements IPv6 over IP4 tunneling, # IPv4 over IPv6 tunneling, IPv4 over IPv4 tunneling and # IPv6 over IPv6 tunneling. pseudo-device gif 64 #IPv6 and IPv4 tunneling # The `faith' pseudo-device captures packets sent to it and diverts them # to the IPv4/IPv6 translation daemon. #pseudo-device faith 1 #for IPv6 and IPv4 translation # IPFIREWALL enables support for IP firewall construction, in # conjunction with the `ipfw' program. IPFIREWALL_VERBOSE sends # logged packets to the system logger. IPFIREWALL_VERBOSE_LIMIT # limits the number of times a matching entry can be logged. options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets #options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=1000 #limit verbosity #options IPV6FIREWALL #firewall for IPv6 #options IPV6FIREWALL_VERBOSE #options IPV6FIREWALL_VERBOSE_LIMIT=1000 # IPFIREWALL_DEFAULT_TO_ACCEPT causes the default rule (at boot) to # allow everything. Use with care, if a cracker can crash your # firewall machine, they can get to your protected machines. However, # if you are using it as an as-needed filter for specific problems as # they arise, then this may be for you. Changing the default to 'allow' # means that you won't get stuck if the kernel and /sbin/ipfw binary get # out of sync. options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default #options IPV6FIREWALL_DEFAULT_TO_ACCEPT # ICMP_BANDLIM enables icmp error response bandwidth limiting. You # typically want this option as it will help protect the machine from # D.O.S. packet attacks. options ICMP_BANDLIM # DUMMYNET enables the "dummynet" bandwidth limiter. You need # IPFIREWALL as well. See the dummynet(4) manpage for more info. options DUMMYNET # BRIDGE enables bridging between ethernet cards -- see bridge(4). # You can use IPFIREWALL and dummynet together with bridging. #options BRIDGE # IPDIVERT enables the divert IP sockets, used by ``ipfw divert'' options IPDIVERT #divert sockets # MROUTING enables the kernel multicast packet forwarder, which works # with mrouted(8). options MROUTING # Multicast routing # IPSTEALTH enables code to support stealth forwarding (i.e., forwarding # packets without touching the ttl). This can be useful to hide firewalls # from traceroute and similar tools. #options IPSTEALTH #support for stealth forwarding #options IPFILTER #ipfilter support #options IPFILTER_LOG #ipfilter logging # Soft updates is technique for improving file system speed and # making abrupt shutdown less risky. options SOFTUPDATES pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) # To include support for VESA video modes options VESA options SC_HISTORY_SIZE=2000 # number of history buffer lines options SC_PIXEL_MODE # add support for the raster text mode # If you have a two button mouse, you may want to add the following option # to use the right button of the mouse to paste text. options SC_TWOBUTTON_MOUSE # The newpcm driver (use INSTEAD of snd0 and all VOXWARE drivers!). # Note that motherboard sound devices may require options PNPBIOS. # # Supported cards include: # Creative SoundBlaster ISA PnP/non-PnP # Supports ESS and Avance ISA chips as well. # Gravis UltraSound ISA PnP/non-PnP # Crystal Semiconductor CS461x/428x PCI # Neomagic 256AV (ac97) # Most of the more common ISA/PnP sb/mss/ess compatable cards. # For PnP/PCI sound cards device pcm device sbc options PNPBIOS device joy0 at isa? port IO_GAME # Add support for the EXT2FS filesystem of Linux fame. Be a bit # careful with this - the ext2fs code has a tendency to lag behind # changes and not be exercised very much, so mounting read/write could # be dangerous (and even mounting read only could result in panics.) options EXT2FS # Enable the kernel debugger. options DDB # Options for psm: options PSM_HOOKRESUME #hook the system resume event, useful #for some laptops options PSM_RESETAFTERSUSPEND #reset the device at the resume event # ATM related options # # The `en' device provides support for Efficient Networks (ENI) # ENI-155 PCI midway cards, and the Adaptec 155Mbps PCI ATM cards (ANA-59x0). # # atm pseudo-device provides generic atm functions and is required for # atm devices. # NATM enables the netnatm protocol family that can be used to # bypass TCP/IP. # # the current driver supports only PVC operations (no atm-arp, no multicast). # for more details, please read the original documents at # http://www.ccrc.wustl.edu/pub/chuck/tech/bsdatm/bsdatm.html # pseudo-device atm device en options NATM # The 'bktr' device is a PCI video capture device using the Brooktree # bt848/bt848a/bt849a/bt878/bt879 chipset. When used with a TV Tuner it forms a # TV card, eg Miro PC/TV, Hauppauge WinCast/TV WinTV, VideoLogic Captivator, # Intel Smart Video III, AverMedia, IMS Turbo, FlyVideo. # # Brooktree driver has been ported to the new I2C framework. Thus, # you'll need to have the following 3 lines in the kernel config. # device smbus device iicbus device iicbb # The iic and smb devices are only needed if you want to control other # I2C slaves connected to the external connector of some cards. device bktr # The aic7xxx driver will attempt to use memory mapped I/O for all PCI # controllers that have it configured only if this option is set. Unfortunately, # this doesn't work on some motherboards, which prevents it from being the # default. #options AHC_ALLOW_MEMIO # PERFMON causes the driver for Pentium/Pentium Pro performance counters # to be compiled. See perfmon(4) for more information. options PERFMON # pca: PCM audio through your PC speaker # Not controlled by `snd' device pca0 at isa? port IO_TIMER1 device agp # netgraph(4). Enable the base netgraph code with the NETGRAPH option. # Individual node types can be enabled with the corresponding option # listed below; however, this is not strictly necessary as netgraph # will automatically load the corresponding KLD module if the node type # is not already compiled into the kernel. Each type below has a # corresponding man page, e.g., ng_async(8). options NETGRAPH #netgraph(4) system #options NETGRAPH_ASYNC #options NETGRAPH_BPF #options NETGRAPH_CISCO #options NETGRAPH_ECHO #options NETGRAPH_FRAME_RELAY #options NETGRAPH_HOLE #options NETGRAPH_IFACE #options NETGRAPH_KSOCKET #options NETGRAPH_LMI # MPPC compression requires proprietary files (not included) #options NETGRAPH_MPPC_COMPRESSION #options NETGRAPH_MPPC_ENCRYPTION #options NETGRAPH_PPP #options NETGRAPH_PPPOE #options NETGRAPH_PPTPGRE #options NETGRAPH_RFC1490 #options NETGRAPH_SOCKET #options NETGRAPH_TEE #options NETGRAPH_TTY #options NETGRAPH_UI #options NETGRAPH_VJC # SMB bus # # System Management Bus support is provided by the 'smbus' device. # Access to the SMBus device is via the 'smb' device (/dev/smb*), # which is a child of the 'smbus' device. # # Supported devices: # smb standard io through /dev/smb* # # Supported SMB interfaces: # iicsmb I2C to SMB bridge with any iicbus interface # bktr brooktree848 I2C hardware interface # intpm Intel PIIX4 Power Management Unit # alpm Acer Aladdin-IV/V/Pro2 Power Management Unit # ichsmb Intel ICH SMBus controller chips (82801AA, 82801AB, 82801BA) device smbus # Bus support, required for smb below. device intpm #device alpm device ichsmb device smb --------------9D5494D50E260A9994CE1B32 Content-Type: text/plain; charset=us-ascii; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #0: Tue Jan 16 15:12:48 PST 2001 root@dum.isi.edu:/usr/src/sys/compile/KERNEL-1.10 Calibrating clock(s) ... TSC clock: 997448496 Hz, i8254 clock: 1193175 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium III/Pentium III Xeon/Celeron (997.46-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbff real memory = 536469504 (523896K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x0046f000 - 0x1ff95fff, 531787776 bytes (129831 pages) avail memory = 517488640 (505360K bytes) Changing APIC ID for IO APIC #0 from 0 to 2 on chip Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170020, at 0xfec00000 bios32: Found BIOS32 Service Directory header at 0xc00ffe80 bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xc03e pnpbios: Found PnP BIOS data at 0xc00fe2d0 pnpbios: Entry = f0000:e2f4 Rev = 1.0 Other BIOS signatures found: ACPI: 000fd720 Preloaded elf kernel "kernel" at 0xc0453000. VESA: information block 56 45 53 41 00 02 ca 6c 00 c0 01 00 00 00 74 69 00 c0 00 02 05 01 df 6c 00 c0 e6 6c 00 c0 f2 6c 00 c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 11 mode(s) found VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6974 (c0006974) VESA: Matrox Graphics Inc. VESA: Matrox Matrox G400 00 Pentium Pro MTRR support enabled SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x80010014 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=1a218086) apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=1a218086) pcib0: on motherboard found-> vendor=0x8086, dev=0x1a21, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base f0000000, size 26 found-> vendor=0x8086, dev=0x1a23, revid=0x01 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x1a24, revid=0x01 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=3 secondarybus=2 found-> vendor=0x8086, dev=0x2418, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=4 secondarybus=4 found-> vendor=0x8086, dev=0x2410, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x2411, revid=0x02 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000ffa0, size 4 Freeing (NOT implemented) redirected PCI irq 14. found-> vendor=0x8086, dev=0x2412, revid=0x02 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=19 map[20]: type 1, range 32, base 0000ff80, size 5 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x8086, dev=0x2413, revid=0x02 class=0c-05-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=b, irq=17 map[20]: type 1, range 32, base 0000dcd0, size 4 pci0: on pcib0 agp0: mem 0xf0000000-0xf3ffffff at device 0.0 on pci0 agp0: allocating GATT for aperture of size 64M pcib1: at device 1.0 on pci0 Freeing (NOT implemented) redirected PCI irq 9. found-> vendor=0x102b, dev=0x0525, revid=0x04 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 1, range 32, base f4000000, size 25 map[14]: type 1, range 32, base fcffc000, size 14 map[18]: type 1, range 32, base fc000000, size 23 pci1: on pcib1 pci1: (vendor=0x102b, dev=0x0525) at 0.0 irq 16 pcib2: at device 2.0 on pci0 found-> vendor=0x8086, dev=0x1360, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=3 secondarybus=3 pci2: on pcib2 pcib3: at device 31.0 on pci2 found-> vendor=0x8086, dev=0x1161, revid=0x01 class=08-00-20, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 Freeing (NOT implemented) redirected PCI irq 9. found-> vendor=0x8086, dev=0x1001, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 1, range 32, base fafe0000, size 17 map[14]: type 1, range 32, base fafd0000, size 16 pci3: on pcib3 pci3: (vendor=0x8086, dev=0x1161) at 0.0 wx0: mem 0xfafd0000-0xfafdffff,0xfafe0000-0xfaffffff irq 16 at device 4.0 on pci3 wx0: Ethernet address 00:03:47:07:e7:4e bpf: wx0 attached pcib4: at device 30.0 on pci0 Freeing (NOT implemented) redirected PCI irq 9. found-> vendor=0x1013, dev=0x6003, revid=0x01 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 1, range 32, base f7fff000, size 12 map[14]: type 1, range 32, base f7e00000, size 20 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x9005, dev=0x00cf, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=17 map[10]: type 1, range 32, base 0000ec00, size 8 map[14]: type 1, range 64, base f7ffe000, size 12 Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x9005, dev=0x00cf, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=18 map[10]: type 1, range 32, base 0000e800, size 8 map[14]: type 1, range 64, base f7ffd000, size 12 Freeing (NOT implemented) redirected PCI irq 14. found-> vendor=0x10b7, dev=0x9200, revid=0x78 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=19 map[10]: type 1, range 32, base 0000e480, size 7 map[14]: type 1, range 32, base f7ffcc00, size 7 pci4: on pcib4 csa0: mem 0xf7e00000-0xf7efffff,0xf7fff000-0xf7ffffff irq 16 at device 4.0 on pci4 using shared irq16. pcm0: on csa0 pcm0: ac97 codec id 0x43525914 pcm0: ac97 codec features headphone, 20 bit DAC, 18 bit ADC, 6 bit master volume, Crystal Semi 3D Stereo Enhancement pcm0: ac97 primary codec extended features AMAP pcm: setmap 1f99b000, 1000; 0xc1c27000 -> 1f99b000 pcm: setmap 1f980000, 1000; 0xc1c2c000 -> 1f980000 ahc0: port 0xec00-0xecff mem 0xf7ffe000-0xf7ffefff irq 17 at device 5.0 on pci4 ahc0: Reading SEEPROM...done. ahc0: Manual LVD Termination ahc0: BIOS eeprom is present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: Downloading Sequencer Program... 415 instructions downloaded aic7899: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xe800-0xe8ff mem 0xf7ffd000-0xf7ffdfff irq 18 at device 5.1 on pci4 ahc1: Reading SEEPROM...done. ahc1: Manual LVD Termination ahc1: BIOS eeprom is present ahc1: Secondary High byte termination Enabled ahc1: Secondary Low byte termination Enabled ahc1: Primary Low Byte termination Enabled ahc1: Primary High Byte termination Enabled ahc1: Downloading Sequencer Program... 415 instructions downloaded aic7899: Wide Channel B, SCSI Id=7, 32/255 SCBs xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xe480-0xe4ff mem 0xf7ffcc00-0xf7ffcc7f irq 19 at device 7.0 on pci4 xl0: Ethernet address: 00:b0:d0:78:c8:cc xl0: media options word: a xl0: found MII/AUTO miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: xl0 attached isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xffa0 ata0: mask=00 status0=ff status1=ff ata0: probe allocation failed ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xffa8 ata1: mask=03 status0=50 status1=00 ata1: mask=03 ostat0=50 ostat2=00 ata1-master: ATAPI probe a=14 b=eb ata1-slave: ATAPI probe a=7f b=7f ata1: mask=03 status0=00 status1=00 ata1: devices=04 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xff80-0xff9f irq 19 at device 31.2 on pci0 using shared irq19. usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ichsmb0: port 0xdcd0-0xdcdf irq 17 at device 31.3 on pci0 using shared irq17. smbus0: on ichsmb0 smb0: on smbus0 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 pnpbios: 17 devices, largest 248 bytes PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0x100000-0x1ff9dfff, size=0x1fe9e000 PNP0c01: adding fixed memory32 range 0xffc00000-0xffffffff, size=0x400000 PNP0c01: adding fixed memory32 range 0xf0000-0xfffff, size=0x10000 PNP0c01: adding io range 0x800-0x8df, size=0xe0, align=0x1 PNP0c01: adding io range 0xc00-0xc7f, size=0x80, align=0x1 PNP0c01: adding io range 0x62-0x63, size=0x2, align=0x1 PNP0c01: adding io range 0x65-0x6f, size=0xb, align=0x1 PNP0c01: adding io range 0xe0-0xef, size=0x10, align=0x1 PNP0c01: end config pnpbios: handle 0 device ID PNP0c01 (010cd041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 PNP0501: end config pnpbios: handle 1 device ID PNP0501 (0105d041) PNP0501: adding irq mask 00x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0x8 PNP0501: end config pnpbios: handle 2 device ID PNP0501 (0105d041) PNP0400: adding dma mask 00 PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x378-0x37f, size=0x8, align=0x8 PNP0400: adding io range 0x778-0x77f, size=0x8, align=0x8 PNP0400: end config pnpbios: handle 3 device ID PNP0400 (0004d041) PNP0700: adding irq mask 0x40 PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x8 PNP0700: adding dma mask 0x4 PNP0700: end config pnpbios: handle 4 device ID PNP0700 (0007d041) PNP0f13: adding irq mask 0x1000 PNP0f13: end config pnpbios: handle 5 device ID PNP0f13 (130fd041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0a03: end config pnpbios: handle 6 device ID PNP0a03 (030ad041) PNP0003: adding fixed memory32 range 0xfee00000-0xfee0ffff, size=0x10000 PNP0003: adding fixed memory32 range 0xfec00000-0xfec0ffff, size=0x10000 PNP0003: end config pnpbios: handle 8 device ID PNP0003 (0300d041) PNP0100: adding irq mask 00x1 PNP0100: adding io range 0x40-0x5f, size=0x20, align=0x1 PNP0100: end config pnpbios: handle 9 device ID PNP0100 (0001d041) PNP0200: adding io range 0x80-0x9f, size=0x20, align=0x1 PNP0200: adding io range 0-0x1f, size=0x20, align=0x1 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 PNP0200: end config pnpbios: handle 10 device ID PNP0200 (0002d041) PNP0303: adding irq mask 00x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 PNP0303: end config pnpbios: handle 11 device ID PNP0303 (0303d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: end config pnpbios: handle 12 device ID PNP0800 (0008d041) INT0800: adding fixed memory32 range 0xffb00000-0xffbfffff, size=0x100000 INT0800: end config pnpbios: handle 13 device ID INT0800 (0008d425) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x7f, size=0x10, align=0x1 PNP0b00: end config pnpbios: handle 14 device ID PNP0b00 (000bd041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: end config pnpbios: handle 15 device ID PNP0c04 (040cd041) PNP0c02: adding fixed memory32 range 0x1ff9e000-0x1fffffff, size=0x62000 PNP0c02: end config pnpbios: handle 16 device ID PNP0c02 (020cd041) isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fdc1: not probed (disabled) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 06 06 psm: data 08 01 01 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00006000, flags:00000000, packet size:4 psm0: syncmask:08, syncbits:08 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic0: not probed (disabled) pcic1: not probed (disabled) sio0: irq maps: 0x8041 0x8051 0x8041 0x8041 sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A sio1: irq maps: 0x8041 0x8049 0x8041 0x8041 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: using extended I/O port range PC873xx probe at 0x2e got unknown ID 0x0 ppc0: ECP SPP ECP+EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port joy0 at port 0x201 on isa0 pca0 at port 0x40 on isa0 isa_probe_children: probing PnP devices unknown: failed to probe at port 0x800-0x8df,0xc00-0xc7f,0x62-0x63,0x65-0x6f,0xe0-0xef iomem 0-0x9ffff,0x100000-0x1ff9dfff,0xffc00000-0xffffffff,0xf0000-0xfffff on isa0 unknown: can't assign resources unknown: at port 0x3f8-0x3ff on isa0 unknown: can't assign resources unknown: at port 0x2f8-0x2ff on isa0 unknown: can't assign resources unknown: at port 0x378-0x37f on isa0 unknown: can't assign resources unknown: at port 0x3f0-0x3f5 on isa0 unknown: can't assign resources unknown: at irq 12 on isa0 unknown: failed to probe at port 0xcf8-0xcff on isa0 unknown: failed to probe at iomem 0xfee00000-0xfee0ffff,0xfec00000-0xfec0ffff on isa0 unknown: failed to probe at port 0x40-0x5f irq 0 on isa0 unknown: failed to probe at port 0x80-0x9f,0-0x1f,0xc0-0xdf drq 4 on isa0 unknown: can't assign resources unknown: at port 0x60 on isa0 pca1: at port 0x61 on isa0 unknown: failed to probe at iomem 0xffb00000-0xffbfffff on isa0 unknown: failed to probe at port 0x70-0x7f irq 8 on isa0 unknown: failed to probe at port 0xf0-0xff irq 13 on isa0 unknown: failed to probe at iomem 0x1ff9e000-0x1fffffff on isa0 SMP: enabled INTs: 1, 3, 4, 6, 7, 12, 15, 16, 17, 18, 19, apic_imen: 0x00f06f25 BIOS Geometries: 0:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 1:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 2:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 3:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging limited to 1000 packets/entry by default bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: gif4 attached bpf: gif5 attached bpf: gif6 attached bpf: gif7 attached bpf: gif8 attached bpf: gif9 attached bpf: gif10 attached bpf: gif11 attached bpf: gif12 attached bpf: gif13 attached bpf: gif14 attached bpf: gif15 attached bpf: gif16 attached bpf: gif17 attached bpf: gif18 attached bpf: gif19 attached bpf: gif20 attached bpf: gif21 attached bpf: gif22 attached bpf: gif23 attached bpf: gif24 attached bpf: gif25 attached bpf: gif26 attached bpf: gif27 attached bpf: gif28 attached bpf: gif29 attached bpf: gif30 attached bpf: gif31 attached bpf: gif32 attached bpf: gif33 attached bpf: gif34 attached bpf: gif35 attached bpf: gif36 attached bpf: gif37 attached bpf: gif38 attached bpf: gif39 attached bpf: gif40 attached bpf: gif41 attached bpf: gif42 attached bpf: gif43 attached bpf: gif44 attached bpf: gif45 attached bpf: gif46 attached bpf: gif47 attached bpf: gif48 attached bpf: gif49 attached bpf: gif50 attached bpf: gif51 attached bpf: gif52 attached bpf: gif53 attached bpf: gif54 attached bpf: gif55 attached bpf: gif56 attached bpf: gif57 attached bpf: gif58 attached bpf: gif59 attached bpf: gif60 attached bpf: gif61 attached bpf: gif62 attached bpf: gif63 attached bpf: lo0 attached DUMMYNET initialized (000608) IPsec: Initialized Security Association Processing. SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff ata1-master: piomode=4 dmamode=2 udmamode=2 dmaflag=1 ata1-master: success setting PIO4 on generic chip acd0: CDROM drive at ata1 as master acd0: read 8268KB/s (8268KB/s), 120KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (ahc0:A:0:0): Sending PPR bus_width 1, period 9, offset 7f, ppr_options 2 (ahc0:A:0:0): Received PPR width 9, period 1, offset 7f,options 2 Filtered to width 1, period 9, offset 7f, options 2 ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 80.0MHz DT, offset = 0x7f (ahc0:A:3:0): Sending PPR bus_width 1, period 9, offset 7f, ppr_options 2 (ahc0:A:3:0): Received PPR width 9, period 1, offset 7f,options 2 Filtered to width 1, period 9, offset 7f, options 2 ahc0: target 3 using 16bit transfers ahc0: target 3 synchronous at 80.0MHz DT, offset = 0x7f (ahc0:A:2:0): Sending PPR bus_width 1, period 9, offset 7f, ppr_options 2 (ahc0:A:2:0): Received PPR width 9, period 1, offset 7f,options 2 Filtered to width 1, period 9, offset 7f, options 2 ahc0: target 2 using 16bit transfers ahc0: target 2 synchronous at 80.0MHz DT, offset = 0x7f (ahc0:A:1:0): Sending PPR bus_width 1, period 9, offset 7f, ppr_options 2 (ahc0:A:1:0): Received PPR width 9, period 1, offset 7f,options 2 Filtered to width 1, period 9, offset 7f, options 2 ahc0: target 1 using 16bit transfers ahc0: target 1 synchronous at 80.0MHz DT, offset = 0x7f Creating DISK da0 Creating DISK da1 Creating DISK da2 Creating DISK da3 da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: Serial Number 161023810178 da0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 17366MB (35566478 512 byte sectors: 255H 63S/T 2213C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-4 device da1: Serial Number 50011869 da1: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da1: 17366MB (35566478 512 byte sectors: 255H 63S/T 2213C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-4 device da2: Serial Number 50010891 da2: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da2: 17366MB (35566478 512 byte sectors: 255H 63S/T 2213C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-4 device da3: Serial Number 50011745 da3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit), Tagged Queueing Enabled da3: 17366MB (35566478 512 byte sectors: 255H 63S/T 2213C) Mounting root from ufs:/dev/da0s2a da0s1: type 0x7, start 63, end = 16787924, size 16787862 : OK da0s2: type 0xa5, start 16787925, end = 35551844, size 18763920 : OK start_init: trying /sbin/init wx0: swdpio1 did not clear- check for reversed or disconnected cable wx0: swdpio1 did not clear- check for reversed or disconnected cable wx0: swdpio1 did not clear- check for reversed or disconnected cable wx0: swdpio1 did not clear- check for reversed or disconnected cable splash: image decoder found: green_saver Linux-ELF exec handler installed (da0:ahc0:0:0:0): tagged openings now 64 --------------9D5494D50E260A9994CE1B32-- --------------ms9B910C130C3A51300512CD21 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDExNzE3NTM0NlowIwYJKoZIhvcNAQkEMRYE FC4ypnuv9APBS3YjzSNL/4VuJ+JtMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGACXhTJWOtIqLUJmdjhhDbB7h1bqzK9VeWUzzkDKccYi67zr5XT8Pk L16Dqc5NxBRX7YoNuE6ZG9MNmT7JLaoJ0N22THNvRywUZkwp72vXJWc71OeDz5DejhEXEyEf qwmj7zPQkLohqbNqBS4w50J7TiH7bNIWPSvg58rE06FtI1Y= --------------ms9B910C130C3A51300512CD21-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:57:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from snics.com (snics.com [206.230.153.97]) by hub.freebsd.org (Postfix) with ESMTP id 7D70A37B402 for ; Wed, 17 Jan 2001 09:57:34 -0800 (PST) Received: from net1 (net1.snics.com [206.230.153.98]) by snics.com (8.9.3/8.9.3) with SMTP id MAA00102 for ; Wed, 17 Jan 2001 12:57:31 -0500 (EST) (envelope-from stevemcn@snics.com) Message-Id: <200101171757.MAA00102@snics.com> X-Sender: stevemcn@snics.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Wed, 17 Jan 2001 12:57:57 -0500 To: freebsd-stable@FreeBSD.ORG From: Steve McNelly Subject: Buildworld Fails Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG =A0 I'm Trying To Upgrade 3.4-RELEASE To 3.X-STABLE. I used *default=A0 tag=3DRELENG_3 In My cvsupfile. Buildworld Always Fails At This Point.=20 Checked The Updating File, Nothing There. I Have Checked The Mail=20 Archives And Found Nothing. Can Anyone Point Me In The Right=20 Direction?=20 /usr/obj/usr/dest/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all;=A0 /usr/obj/usr/dest/usr/src/tmp/usr/bin/make -DNOINFO= -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install cleandir obj rm -f .depend /usr/obj/usr/dest/usr/src/usr.bin/compile_et/GPATH /usr/obj/usr/dest/usr/src/usr.bin/compile_et/GRTAGS=A0 /usr/obj/usr/dest/usr/src/usr.bin/compile_et/GSYMS /usr/obj/usr/dest/usr/src/usr.bin/compile_et/GTAGS rm -f .depend /usr/obj/usr/dest/usr/src/usr.bin/compile_et/GPATH /usr/obj/usr/dest/usr/src/usr.bin/compile_et/GRTAGS=A0 /usr/obj/usr/dest/usr/src/usr.bin/compile_et/GSYMS /usr/obj/usr/dest/usr/src/usr.bin/compile_et/GTAGS yacc -d -o parse.c /usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err/parse.y cc -O -pipe -I.= -I/usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err=A0=A0 -I/usr/obj/usr/dest/usr/src/tmp/usr/include -c /usr/dest/usr/src/usr.bin/compile_et/compile_et.c cc -O -pipe -I.= -I/usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err=A0=A0 -I/usr/obj/usr/dest/usr/src/tmp/usr/include -c parse.c lex -t=A0 /usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err/lex.l > lex.c cc -O -pipe -I.= -I/usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err=A0=A0 -I/usr/obj/usr/dest/usr/src/tmp/usr/include -c lex.c cc -O -pipe -I.= -I/usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err=A0=A0 -I/usr/obj/usr/dest/usr/src/tmp/usr/include -c /usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err/getarg.c /usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err/getarg.c: In function `add_string': /usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err/getarg.c:178: warning: assignment makes pointer from integer without a cast /usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err/getarg.c: In function `arg_match_long': /usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err/getarg.c:197: warning: assignment makes pointer from integer without a cast cc -O -pipe -I.= -I/usr/dest/usr/src/usr.bin/compile_et/../../contrib/com_err=A0=A0 -I/usr/obj/usr/dest/usr/src/tmp/usr/include=A0 -static -o compile_et compile_et.o parse.o lex.o getarg.o=A0=20 parse.o: In function `yyerror': parse.o(.text+0x78): multiple definition of `yyerror' compile_et.o(.text+0x600): first defined here /usr/libexec/elf/ld: Warning: size of symbol `yyerror' changed from 47 to 18 in parse.o compile_et.o: In function `main': compile_et.o(.text+0x4c2): undefined reference to `current' compile_et.o(.text+0x4c8): undefined reference to `table_number' compile_et.o(.text+0x58e): undefined reference to `table_number' compile_et.o: In function `yyerror': compile_et.o(.text+0x612): undefined reference to `current_token' compile_et.o(.text+0x618): undefined reference to `yylineno' parse.o: In function `yyparse': parse.o(.text+0x3f4): undefined reference to `id_str' parse.o(.text+0x40d): undefined reference to `base' parse.o(.text+0x41e): undefined reference to `name' parse.o(.text+0x429): undefined reference to `name' parse.o(.text+0x452): undefined reference to `base' parse.o(.text+0x463): undefined reference to `name' parse.o(.text+0x46e): undefined reference to `name' parse.o(.text+0x49c): undefined reference to `number' parse.o(.text+0x4c3): undefined reference to `prefix' parse.o(.text+0x4d0): undefined reference to `prefix' parse.o(.text+0x4e8): undefined reference to `prefix' parse.o(.text+0x50c): undefined reference to `prefix' parse.o(.text+0x516): undefined reference to `prefix' parse.o(.text+0x539): undefined reference to `number' parse.o(.text+0x544): undefined reference to `prefix' parse.o(.text+0x54d): undefined reference to `prefix' parse.o(.text+0x582): undefined reference to `codes' parse.o(.text+0x5af): undefined reference to `codes' parse.o(.text+0x5b7): undefined reference to `codes' parse.o(.text+0x5c1): undefined reference to `codes' parse.o(.text+0x5cd): undefined reference to `number' lex.o: In function `error_message': lex.o(.text+0xdc0): undefined reference to `numerror' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Steve McNelly stevemcn@snics.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 9:58:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id D23E037B404; Wed, 17 Jan 2001 09:57:59 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id JAA27093; Wed, 17 Jan 2001 09:57:59 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.9.3/8.9.3) id JAA13772; Wed, 17 Jan 2001 09:57:58 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200101171757.JAA13772@curve.dellroad.org> Subject: Re: BSD box as Airport replacement? In-Reply-To: <200101171740.f0HHeVW01464@guild.plethora.net> "from Peter Seebach at Jan 17, 2001 11:40:31 am" To: Peter Seebach Date: Wed, 17 Jan 2001 09:57:58 -0800 (PST) Cc: Warner Losh , simon@surf.org.uk, Rasputin , freebsd-stable@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Seebach writes: > >Gold is 128 bits of encryption. Silver is only 64 or 96. > > As I understand it, 64, except you only get to pick 40 of them, which makes > it very confusing. And with "128 bit", you only get to pick 104 of them. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 10:12:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.cb21.co.jp (ns1.cb21.co.jp [203.140.149.254]) by hub.freebsd.org (Postfix) with SMTP id 6FAB437B6C1 for ; Wed, 17 Jan 2001 10:12:25 -0800 (PST) Received: (qmail 2620 invoked from network); 18 Jan 2001 03:12:21 +0900 Received: from localhost.cb21.co.jp (HELO localhost) (127.0.0.1) by localhost.cb21.co.jp with SMTP; 18 Jan 2001 03:12:21 +0900 Date: Thu, 18 Jan 2001 03:12:20 +0900 (JST) From: Sys Admin To: freebsd-stable@freebsd.org Subject: RAID configuration for a mail server (1 or 5) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ** I sent this same mail to isp list. But I am yet to get a response. Hoping that I will have some luck here. If this is not the right list to ask, please redirect ** Hello all, We have a mail server that supports few hundred domains supporting few thousand pop accounts. What kind of RAID configuration suits a fairly busy mail server ? It is my understanding that RAID 5 is little bit slow for an active server. What are the performance issues that needs to be thought of when selecting a RAID configuration ? Thanks in advance for any useful input. Tad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 10:22: 9 2001 Delivered-To: freebsd-stable@freebsd.org Received: from firewall.telesyscom.com (firewall.telesyscom.com [207.113.164.11]) by hub.freebsd.org (Postfix) with ESMTP id 6D54037B6BE for ; Wed, 17 Jan 2001 10:21:43 -0800 (PST) Received: from anybodyLAP (ci533211-b.nash1.tn.home.com [65.8.169.26]) by firewall.telesyscom.com (8.9.3/8.9.3) with SMTP id NAA86425 for ; Wed, 17 Jan 2001 13:21:39 -0500 (EST) (envelope-from scott@e-comsultant.net) Message-ID: <004201c080b2$44ecfd90$0d00a8c0@anybodyLAP> From: "Scott Milliken" To: References: <20010117162929.A58519@dogma.freebsd-uk.eu.org> <20010117084116.A22875@drella.newsof.com> <20010117165843.A58911@dogma.freebsd-uk.eu.org> <3A65D103.D815E92@herculeez.com> Subject: Re: BSD box as Airport replacement? Date: Wed, 17 Jan 2001 12:20:37 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have implemented another option that works rather well... especially since I didn't want to buy wireless NICs for all of the machines behind my NAT gateway. Several vendors provide Access Points that simply bridge the traffic from wireless to wireline. Personally I have the D-Link DWL-1000AP access point and DWL-650 PCMCIA wireless NIC. The D-Link system (and many others) utilize several methods for access control. First, all devices on the wireless LAN have to be set to the same SSID in order to work. Secondly, you can limit access to a list of MAC addresses. Finally, if you're really paranoid, you can enter a hex value for an encryption key on each card and the traffic itself will be encrypted. I can't testify as to whether or not the D-Link PCMCIA card works in FreeBSD, but it wasn't quite clear in your message if more than the gateway itself was running FreeBSD. Anybody out there know for sure if it does work? Scott Milliken ----- Original Message ----- From: "Simon Loader" To: "Rasputin" Cc: ; Sent: Wednesday, January 17, 2001 11:06 AM Subject: Re: BSD box as Airport replacement? > Rasputin wrote: > > > > * Andrew Wyllie [010117 16:43]: > > > Hi Rasputin, > > > > > > I bought the Orinoco (Lucent WaveLAN cards - the "Gold" version ). > > > I used an old 486/100 with 16MB ram and a 500MB drive and this paper: > > > > > > http://www.live.com/wireless/unix-base-station.html > > > > > > It works great. My base station is in the basement and I can use it > > > from all over the house and part way down the street ( the cards say > > > they work up to 1700 feet - outside ). > > > > > > > Cheers Andrew, that'll do me fine. One more question: > > With a range like that, how do you stop Evil Granny Smith > > at number 23 from sniffing your network traffic? > > > > Is there crypto built into the IEEE802.11 spec? > > And is it any good? > > > > With the gold version there is I think silver doesnt > > -- > Simon > > > 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 Jan 17 10:51:28 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yez.hyperreal.org (gate.sp.collab.net [64.211.228.36]) by hub.freebsd.org (Postfix) with SMTP id EE9B237B6B7 for ; Wed, 17 Jan 2001 10:51:05 -0800 (PST) Received: (qmail 13320 invoked by uid 1000); 17 Jan 2001 18:51:13 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Jan 2001 18:51:13 -0000 Date: Wed, 17 Jan 2001 10:51:12 -0800 (PST) From: Brian Behlendorf X-Sender: brian@localhost To: Kris Kennaway Cc: freebsd-stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP In-Reply-To: <20010117012737.A55253@citusc17.usc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Jan 2001, Kris Kennaway wrote: > On Tue, Jan 16, 2001 at 06:19:07PM -0800, faSty wrote: > > Hi there, > > > > It happened to my server same situation today and I got the tip from someone > > told me do copy /usr/src/etc/pam.conf to /etc > > This should have happened as part of running mergemaster, which is an > important part of the upgrade process you should follow with every > source update and rebuild. Please see the handbook for full > instructions on how to safely update your system. Hmm - I ran mergemaster after my last make world, and it didn't pick up the differences between /etc/pam.conf and /usr/src/etc/pam.conf either. The /etc/pam.conf I had hadn't been changed since my last full install, though I'd done a make world/mergemaster 3 times since then. Curious. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 10:55:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 6DF2037B6AC for ; Wed, 17 Jan 2001 10:55:32 -0800 (PST) Received: from hyperion.informatik.rwth-aachen.de (hyperion.Informatik.RWTH-Aachen.DE [137.226.112.212]) by nets5.rz.rwth-aachen.de (8.10.1/8.10.1/5) with ESMTP id f0HItUm27707 for ; Wed, 17 Jan 2001 19:55:30 +0100 (MET) 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 TAA14271 for ; Wed, 17 Jan 2001 19:54:27 +0100 (MET) Received: (from stolz@localhost) by agamemnon.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1-gb-2) id TAA27872 for stable@freebsd.org; Wed, 17 Jan 2001 19:55:18 +0100 (MET) Date: Wed, 17 Jan 2001 19:55:17 +0100 From: Volker Stolz To: stable@freebsd.org Subject: Freeze at/before login-prompt on 4.2S since yesterday Message-ID: <20010117195517.A27827@agamemnon.informatik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i Organization: Chair for CS II 1/2, Anomalous Programming Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been running a maybe 3 days old STABLE-box, but when I rebuilt just the kernel yesterday to include some stuff which I was loading as modules before the machine freezes just before or on issuing the console login. It´s network stack is running as I can still ping it. However, when I reverted the kernel-config to what it was before the upgrade (i.e. ng_pppoe & ipfw as modules) the new kernel shows the same behaviour :| What´s worse, the original kernel got "expired" by several calls of mv /kernel /kernel.old. So I´m back to 4-2-RELEASE-GENERIC now, the modules with the exception of ipfw still work. Any suggestions whats going on? It can´t possibly be because of userland and kernel going out ouf sync in a few days and even locking up the machine, can it? It´d like to avoid having to buildworld again... -- \usepackage[latin1]{inputenc}! 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 Wed Jan 17 15:36:20 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 6E8F837B404 for ; Wed, 17 Jan 2001 15:36:02 -0800 (PST) Received: from pir by moek.pir.net with local (Exim) id 14J27Q-0001WL-00 for freebsd-stable@FreeBSD.ORG; Wed, 17 Jan 2001 18:35:56 -0500 Date: Wed, 17 Jan 2001 18:35:55 -0500 From: Peter Radcliffe To: freebsd-stable@FreeBSD.ORG Message-ID: <20010117183555.F1446@pir.net> Reply-To: freebsd-stable@freebsd.org Mail-Followup-To: freebsd-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 X-Loop: FreeBSD.ORG I've been playing with moving to ssh V2 by default and discovered that the freebsd-stable openssh doesn't appear to forward the authentication agent connection, even when turned on and specificly told to. ssh v1 in the same situation with the same machines works perfectly. Has anyone else seen this ? Is it intentional ? P. ---------------------------------------------------------------- pir@mrow> uname -a FreeBSD mrow 4.2-STABLE FreeBSD 4.2-STABLE #18: Wed Jan 3 17:41:30 EST 2001 pir@mrow:/usr/src/sys/compile/MROW i386 pir@mrow> ssh -v moek SSH Version OpenSSH_2.2.0, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). [...] debug: Trying RSA authentication via agent with 'pir@mrow' debug: Received RSA challenge from server. debug: Sending response to RSA challenge. debug: Remote: RSA authentication accepted. debug: RSA authentication accepted by server. debug: Requesting pty. debug: Requesting X11 forwarding with authentication spoofing. debug: Requesting authentication agent forwarding. debug: Requesting shell. debug: Entering interactive session. [...] pir@moek> echo $SSH_AUTH_SOCK /tmp/ssh-gQdO5061/agent.5061 pir@moek> lo q pir@mrow> ssh -A -2 -v moek SSH Version OpenSSH_2.2.0, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). [...] Enabling compatibility mode for protocol 2.0 debug: Local version string SSH-2.0-OpenSSH_2.2.0 [...] debug: trying DSA agent key /home/pir/.ssh/id_dsa debug: ssh-userauth2 successfull debug: no set_nonblock for tty fd 4 debug: no set_nonblock for tty fd 5 debug: no set_nonblock for tty fd 6 debug: channel 0: new [client-session] debug: send channel open 0 debug: Entering interactive session. debug: callback start debug: client_init id 0 arg 0 debug: Requesting X11 forwarding with authentication spoofing. debug: channel request 0: shell [...] pir@moek> echo $SSH_AUTH_SOCK SSH_AUTH_SOCK: Undefined variable. ---------------------------------------------------------------- -- 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 Wed Jan 17 15:42:29 2001 Delivered-To: freebsd-stable@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id 2D51837B400 for ; Wed, 17 Jan 2001 15:42:12 -0800 (PST) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.33 2000/11/21 19:27:27 smothers Exp $) with ESMTP id XAA03281 for ; Wed, 17 Jan 2001 23:45:07 GMT Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.14 2001/01/02 18:39:59 steved Exp $) with ESMTP id QAA08114 for ; Wed, 17 Jan 2001 16:42:06 -0700 (MST) X-Envelope-To: X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id SAA28116; Wed, 17 Jan 2001 18:42:06 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14950.11726.379481.344754@hip186.ch.intel.com> Date: Wed, 17 Jan 2001 16:42:06 -0700 (MST) To: freebsd-stable@freebsd.org In-Reply-To: <20010117183555.F1446@pir.net> References: <20010117183555.F1446@pir.net> X-Mailer: VM 6.75 under Emacs 20.6.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Wednesday, January 17, Peter Radcliffe wrote: ] > I've been playing with moving to ssh V2 by default and discovered that > the freebsd-stable openssh doesn't appear to forward the > authentication agent connection, even when turned on and specificly > told to. ssh v1 in the same situation with the same machines works > perfectly. I have no idea if it will help, but a more recent -stable will get you OpenSSH 2.3.0 instead of what you're using (2.2.0). dolphin [~]<104>% uname -a FreeBSD dolphin 4.2-STABLE FreeBSD 4.2-STABLE #0: Wed Jan 10 15:30:37 MST 2001 root@dolphin:/usr/obj/usr/src/sys/DOLPHIN i386 dolphin [~]<105>% ssh -v SSH Version OpenSSH_2.3.0, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f). -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 15:50:23 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 85BD237B402 for ; Wed, 17 Jan 2001 15:50:06 -0800 (PST) Received: from pir by moek.pir.net with local (Exim) id 14J2L7-0001dP-00 for freebsd-stable@freebsd.org; Wed, 17 Jan 2001 18:50:05 -0500 Date: Wed, 17 Jan 2001 18:50:04 -0500 From: Peter Radcliffe To: freebsd-stable@freebsd.org Subject: Re: your mail Message-ID: <20010117185004.H1446@pir.net> Reply-To: stable@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org References: <20010117183555.F1446@pir.net> <14950.11726.379481.344754@hip186.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14950.11726.379481.344754@hip186.ch.intel.com>; from jreynold@sedona.ch.intel.com on Wed, Jan 17, 2001 at 04:42:06PM -0700 X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Reynolds~ probably said: > I have no idea if it will help, but a more recent -stable will get > you OpenSSH 2.3.0 instead of what you're using (2.2.0). *checks* My laptop has 2.3.0, built world more recently, same problem. Thanks, 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 Wed Jan 17 16:25:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ukexchange.avantgo.com (unknown [62.41.97.90]) by hub.freebsd.org (Postfix) with ESMTP id 86BDF37B69C for ; Wed, 17 Jan 2001 16:25:17 -0800 (PST) Received: by ukexchange.ldn.avantgo.com with Internet Mail Service (5.5.2650.21) id ; Thu, 18 Jan 2001 00:25:04 -0000 Received: from nayarit.avantgo.com ([10.1.30.1]) by sampnt500.avantgo.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id CN0QW86P; Wed, 17 Jan 2001 16:24:57 -0800 Received: from nayarit.avantgo.com (localhost.avantgo.com [127.0.0.1]) by nayarit.avantgo.com (Postfix) with ESMTP id 119C5F80D for ; Wed, 17 Jan 2001 16:25:07 -0800 (PST) From: Michael Kiernan To: stable@FreeBSD.ORG X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Subject: Re: your mail In-Reply-To: Your message of "Wed, 17 Jan 2001 18:50:04 EST." <20010117185004.H1446@pir.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Jan 2001 16:25:07 -0800 Message-Id: <20010118002508.119C5F80D@nayarit.avantgo.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Radcliffe wrote: > My laptop has 2.3.0, built world more recently, same problem. You may have to use a more recent snapshot if you want to use agent forwarding with V2 of the protocol: http://marc.theaimsgroup.com/?l=openssh-unix-dev&m=97808769828106&w=2 There are a few other messages regarding this topic in the openshh-unix-dev archive. Mike -- Michael Kiernan mkiernan@avantgo.com +1-650-638-7581 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 16:40:30 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 A193837B6A0 for ; Wed, 17 Jan 2001 16:40:12 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0I0eBo37317; Wed, 17 Jan 2001 19:40:11 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0I0e4d37309; Wed, 17 Jan 2001 19:40:06 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010117193231.03731950@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 17 Jan 2001 19:40:03 -0500 To: Sys Admin , freebsd-stable@freebsd.org From: Mike Tancsa Subject: Re: RAID configuration for a mail server (1 or 5) 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 X-Loop: FreeBSD.ORG At 03:12 AM 1/18/2001 +0900, Sys Admin wrote: >** I sent this same mail to isp list. But I am yet to get a >response. Hoping that I will have some luck here. If this is not the >right list to ask, please redirect ** Questions is more appropriate. Also, you may want to scan through the archives, as questions like this have been asked and answered before. www.dejanews.com is your friend and Oracle! We have a mail server that supports few hundred domains supporting few >thousand pop accounts. What kind of RAID configuration suits a fairly >busy mail server ? For speed, reliability and cost, have a look at the 4port 3ware card (www.3ware.com) in RAID 10 config. Two RAID0 sets mirrored together. Get yourself some inexpensive drawers ( eg http://www.startech.com/ststore/ItemDetail.cfm?Product_ID=IDE66BASIC) and you have a fairly fast, reliable and cost effective setup. Hot swapable SCSI RAID is also nice, something like the AMIMegaRAID, or the supported Adapec will do as well. Decide what fits your budget. The final price does not necessarily linearly scale with the protection/benefits level for your situation. Also, lots of RAM so that mailboxes can be cached as they are being read helps a lot. With the price of RAM these days, 512MB will make any server happy. ---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 Jan 17 17:19: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id C29CE37B401 for ; Wed, 17 Jan 2001 17:18:39 -0800 (PST) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA11944 for ; Wed, 17 Jan 2001 17:18:39 -0800 (PST) Message-ID: <3A66446F.51A10752@isi.edu> Date: Wed, 17 Jan 2001 17:18:39 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: SMP & signal 11 References: <3A65DC2A.8A15BEE1@isi.edu> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms5CE1F9A3C4FFD49FFF6D0AC5" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms5CE1F9A3C4FFD49FFF6D0AC5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I repeated this on a second, identical machine, so it doesn't seem to be a hardware issue. (Or it affects the whole series.) Is anyone running 4.2 successfully on a SMP Dell Precision 620? Lars Eggert wrote: > processes get killed (signal 11) on a new Dell Precision 620 under moderate > load (kernel recompilation). This only happens if I enable the second CPU > in the BIOS, and the kernel has SMP enabled. This machine runs FreeBSD > 4.2-RELEASE. > > I know signal 11 is usually an indication of bad RAM or cache memory, but > I've been running the Dell system test for over 24 hours, and it shows no > defects there. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms5CE1F9A3C4FFD49FFF6D0AC5 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDExODAxMTgzOVowIwYJKoZIhvcNAQkEMRYE FFX271d2d4ClTI0zFY+2bFkAdWxhMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAH55VCh62I0schnuftjkdOVkPraFYQeMbeXmxHjp/4RQtvESaruKa grl5LssrGmtep3660+dqpfw1vXPw3/x/wbumrbyGV7SpDCO3bDH8JvJWZrlvNyLQxqouMXV0 UrWPe7Et0+xYMDlpPRoUiCp/rHEDRQ1WjucyN95MUqtfO4Q= --------------ms5CE1F9A3C4FFD49FFF6D0AC5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 17:43:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scribe.pobox.com (scribe.pobox.com [208.210.124.35]) by hub.freebsd.org (Postfix) with ESMTP id 43C9C37B401 for ; Wed, 17 Jan 2001 17:43:34 -0800 (PST) Received: from pobox.com (unknown [207.8.144.30]) by scribe.pobox.com (Postfix) with ESMTP id 0540932591; Wed, 17 Jan 2001 20:43:32 -0500 (EST) Message-ID: <3A664A43.F54854C@pobox.com> Date: Wed, 17 Jan 2001 20:43:31 -0500 From: Jamil Taylor X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Lars Eggert Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SMP & signal 11 References: <3A65DC2A.8A15BEE1@isi.edu> <3A66446F.51A10752@isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running 4.2 STABLE on an SMP Precision 420. AFAIK, the 420 and 620 use the same chipsets (my verbose boot looks similar to yours). My kernel is different (simpler), however. I do not know if this could be the cause of the problem, but I have never had to disable SMP on my machine. Only strange things that have happened to me is removing `device ATA' from kernel causes an immediate panic (machine is all SCSI). Lars Eggert wrote: > > I repeated this on a second, identical machine, so it doesn't seem to be a > hardware issue. (Or it affects the whole series.) Is anyone running 4.2 > successfully on a SMP Dell Precision 620? > > Lars Eggert wrote: > > processes get killed (signal 11) on a new Dell Precision 620 under moderate > > load (kernel recompilation). This only happens if I enable the second CPU > > in the BIOS, and the kernel has SMP enabled. This machine runs FreeBSD > > 4.2-RELEASE. > > > > I know signal 11 is usually an indication of bad RAM or cache memory, but > > I've been running the Dell system test for over 24 hours, and it shows no > > defects there. > -- > Lars Eggert Information Sciences Institute > http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 17:48:56 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 9451C37B400 for ; Wed, 17 Jan 2001 17:48:36 -0800 (PST) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA21608; Wed, 17 Jan 2001 17:48:30 -0800 (PST) Message-ID: <3A664B6E.5291BD15@isi.edu> Date: Wed, 17 Jan 2001 17:48:30 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Jamil Taylor Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SMP & signal 11 References: <3A65DC2A.8A15BEE1@isi.edu> <3A66446F.51A10752@isi.edu> <3A664A43.F54854C@pobox.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms56B2522F34F46D6EF75835FA" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms56B2522F34F46D6EF75835FA Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jamil Taylor wrote: > > I am running 4.2 STABLE on an SMP Precision 420. AFAIK, the 420 and 620 > use the same chipsets (my verbose boot looks similar to yours). My > kernel is different (simpler), however. I do not know if this could be > the cause of the problem, but I have never had to disable SMP on my > machine. We have a bunch of uniprocessor 420's that also run fine. Maybe it's an issue with the processors? They're 1Ghz Xeons. What do you run in the 420's? Could this be due to overheating? Do you still have that kernel config file handy? Maybe I'll try it on our 620s. > Only strange things that have happened to me is removing `device ATA' > from kernel causes an immediate panic (machine is all SCSI). I've never tried that. Did you disable the ATA controllers in the BIOS, too? Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms56B2522F34F46D6EF75835FA Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDExODAxNDgzMFowIwYJKoZIhvcNAQkEMRYE FKdduz2vMMDsdeutGkEWECZehBsgMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAa0Uz59+Jqt4gHcmTPmDW6vzZqk06xEHhDk3biS/GDGKxxBeE2muB ti8sh09p1tTymaWr0k2HtVUNOM9caYUQaZOlJFdRXY6xpOjhBn5WOeo09R2ilxGfy0ALojaX 3TZ5ED2wY/IwGw337S239pDlvyhEszrkgUOA6dAQUqcBQ9k= --------------ms56B2522F34F46D6EF75835FA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 17:58:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scribe.pobox.com (scribe.pobox.com [208.210.124.35]) by hub.freebsd.org (Postfix) with ESMTP id 354F737B400 for ; Wed, 17 Jan 2001 17:58:04 -0800 (PST) Received: from pobox.com (unknown [207.8.144.30]) by scribe.pobox.com (Postfix) with ESMTP id F20AD32593; Wed, 17 Jan 2001 20:58:02 -0500 (EST) Message-ID: <3A664DAA.35E2635C@pobox.com> Date: Wed, 17 Jan 2001 20:58:02 -0500 From: Jamil Taylor X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Lars Eggert Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SMP & signal 11 References: <3A65DC2A.8A15BEE1@isi.edu> <3A66446F.51A10752@isi.edu> <3A664A43.F54854C@pobox.com> <3A664B6E.5291BD15@isi.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lars Eggert wrote: > We have a bunch of uniprocessor 420's that also run fine. Maybe it's an > issue with the processors? They're 1Ghz Xeons. What do you run in the > 420's? Could this be due to overheating? My 420 does not have Xeons, so that's another difference. It has two 933 P3's. I have not run into heat issues with mine, so I cannot say if it's heat related. > Do you still have that kernel config file handy? Maybe I'll try it on our > 620s. I will send my kernel config under separate email. > > Only strange things that have happened to me is removing `device ATA' > > from kernel causes an immediate panic (machine is all SCSI). > > I've never tried that. Did you disable the ATA controllers in the BIOS, > too? Although there is an option in the setup screen to disable the controller, it still seems to leave the device active. The controller just is not assigned IRQs, it seems. I just left ATA in the kernel config. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 18:29:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 4A40637B401 for ; Wed, 17 Jan 2001 18:29:15 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0I2WWT69410; Wed, 17 Jan 2001 18:32:32 -0800 (PST) (envelope-from kris) Date: Wed, 17 Jan 2001 18:32:32 -0800 From: Kris Kennaway To: Brian Behlendorf Cc: freebsd-stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP Message-ID: <20010117183232.B69328@citusc17.usc.edu> References: <20010117012737.A55253@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="s2ZSL+KKDSLx8OML" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from brian@collab.net on Wed, Jan 17, 2001 at 10:51:12AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --s2ZSL+KKDSLx8OML Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 17, 2001 at 10:51:12AM -0800, Brian Behlendorf wrote: > On Wed, 17 Jan 2001, Kris Kennaway wrote: > > On Tue, Jan 16, 2001 at 06:19:07PM -0800, faSty wrote: > > > Hi there, > > >=20 > > > It happened to my server same situation today and I got the tip from= someone > > > told me do copy /usr/src/etc/pam.conf to /etc > >=20 > > This should have happened as part of running mergemaster, which is an > > important part of the upgrade process you should follow with every > > source update and rebuild. Please see the handbook for full > > instructions on how to safely update your system. >=20 > Hmm - I ran mergemaster after my last make world, and it didn't pick up > the differences between /etc/pam.conf and /usr/src/etc/pam.conf > either. The /etc/pam.conf I had hadn't been changed since my last full > install, though I'd done a make world/mergemaster 3 times since > then. Curious. It only compares $FreeBSD$ revisions by default (there's an option to do a full diff), so if you have done a partial merge in mergemaster and only updated the $FreeBSD$ hunk, it won't prompt you again in future runs until the next time someone commits to the file. Other than that, I'm not sure what it could be. Kris --s2ZSL+KKDSLx8OML Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6ZlXAWry0BWjoQKURAkNRAJwMNovy16a146LK8BsIaqbN7evXhgCfYFCh w9j15WM9dLhu0QToQbFed1Q= =rolP -----END PGP SIGNATURE----- --s2ZSL+KKDSLx8OML-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 19: 0:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 2634437B401 for ; Wed, 17 Jan 2001 19:00:42 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0I3Ewj00549; Wed, 17 Jan 2001 19:14:59 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101180314.f0I3Ewj00549@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: Sys Admin , freebsd-stable@freebsd.org Subject: Re: RAID configuration for a mail server (1 or 5) In-reply-to: Your message of "Wed, 17 Jan 2001 19:40:03 EST." <4.2.2.20010117193231.03731950@marble.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Jan 2001 19:14:58 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For speed, reliability and cost, have a look at the 4port 3ware card > (www.3ware.com) in RAID 10 config. Two RAID0 sets mirrored together. Get > yourself some inexpensive drawers ( eg > http://www.startech.com/ststore/ItemDetail.cfm?Product_ID=IDE66BASIC) and > you have a fairly fast, reliable and cost effective setup. Hot swapable > SCSI RAID is also nice... Just to point out that you can hot-swap drives on the 3ware controller as well. I'm quite liking the InClose ATA-100 bays at the moment; the switched power is nice, although I wish that the keys would stay in the locks rather than popping out. 3ware also have a list of recommended bays/pods/drawers/whatever on their support website. -- ... 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 Jan 17 21:21:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f78.law10.hotmail.com [64.4.15.78]) by hub.freebsd.org (Postfix) with ESMTP id 128DB37B400 for ; Wed, 17 Jan 2001 21:21:03 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 17 Jan 2001 21:21:02 -0800 Received: from 144.80.62.80 by lw10fd.law10.hotmail.msn.com with HTTP; Thu, 18 Jan 2001 05:21:02 GMT X-Originating-IP: [144.80.62.80] From: "Nader Turki" To: freebsd-stable@FreeBSD.org Subject: ports Date: Thu, 18 Jan 2001 00:21:02 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 18 Jan 2001 05:21:02.0816 (UTC) FILETIME=[732BF600:01C0810E] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I just updated my ports and i've been getting errors. i installed screen it worked fine, but with pine and wget i got something like: ===> Returning to build of wget-1.6_1 ===> Patching for wget-1.6_1 ===> Applying FreeBSD patches for wget-1.6_1 5 out of 8 hunks failed--saving rejects to src/url.c.rej >>Patch patch-ab failed to apply cleanly. *** Error code 1 Stop in /usr/ports/ftp/wget. *** Error code 1 Stop in /usr/ports/ftp/wget. *** Error code 1 Stop in /usr/ports/ftp/wget. *** Error code 1 Stop in /usr/ports/ftp/wget. *** Error code 1 Stop in /usr/ports/ftp/wget. Thanks, Nader _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 21:26:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from odin.egate.net (as2.dm.egate.net [216.235.1.5]) by hub.freebsd.org (Postfix) with ESMTP id 030BC37B401 for ; Wed, 17 Jan 2001 21:26:09 -0800 (PST) Received: from localhost (buff@localhost) by odin.egate.net (8.9.3/8.9.1) with ESMTP id AAA37475 for ; Thu, 18 Jan 2001 00:26:08 -0500 (EST) X-Authentication-Warning: odin.egate.net: buff owned process doing -bs Date: Thu, 18 Jan 2001 00:26:05 -0500 (EST) From: William Denton X-Sender: buff@odin.egate.net To: freebsd-stable@freebsd.org Subject: Perl's CGI.pm in the source tree Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I saw someone ask about this last year, but I don't think there was a reply, and the situation hasn't changed. Are there any plans to upgrade the version of Perl's CGI.pm in the source tree? | $CGI::revision = '$Id: CGI.pm,v 1.5 1998/12/06 10:19:48 lstein Exp $'; | $CGI::VERSION='2.46'; The current version is 2.74, dated 13 Sep 2000. Bill -- William Denton : Toronto, Canada : http://www.miskatonic.org/ : Caveat lector. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 22: 6:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nairobi.networkers.com.au (mail.networkers.com.au [203.9.245.98]) by hub.freebsd.org (Postfix) with ESMTP id 9BB3F37B400 for ; Wed, 17 Jan 2001 22:05:58 -0800 (PST) Received: from Ruddee (berlin.networkers.com.au [203.9.245.100]) by nairobi.networkers.com.au (8.11.0/8.11.0) with SMTP id f0I5xUV56175 for ; Thu, 18 Jan 2001 15:59:32 +1000 (EST) (envelope-from sys.admin@networkers.com.au) Message-ID: <00e101c08115$feb44fe0$fb01010a@networkers.com.au> From: "Ruddee Harris" To: Subject: subscribe Date: Thu, 18 Jan 2001 16:15:00 +1000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DE_01C08169.CEDE53C0" 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 X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00DE_01C08169.CEDE53C0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Kind Regards, Ruddee Harris Technical Services Manager NETworkers Pty Ltd http://www.networkers.com.au ------=_NextPart_000_00DE_01C08169.CEDE53C0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
 
Kind Regards,
 
Ruddee Harris
Technical Services = Manager
 
NETworkers Pty Ltd
http://www.networkers.com.au
------=_NextPart_000_00DE_01C08169.CEDE53C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 22:14:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pinnacle.schulte.org (pinnacle.schulte.org [209.134.156.220]) by hub.freebsd.org (Postfix) with ESMTP id 48FC637B402 for ; Wed, 17 Jan 2001 22:14:40 -0800 (PST) Received: (from schulte@localhost) by pinnacle.schulte.org (8.11.1/8.11.1) id f0I6E3W60889; Thu, 18 Jan 2001 00:14:03 -0600 (CST) (envelope-from schulte) Date: Thu, 18 Jan 2001 00:14:03 -0600 From: Christopher Schulte To: jason@routermonkey.com Cc: Mark.Andrews@nominum.com, Mike Andrews , stable@freebsd.org Subject: Re: Weird sporadic DNS resolution problems Message-ID: <20010118001402.A60881@schulte.org> References: <20010113123754.B1299@fry.routermonkey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010113123754.B1299@fry.routermonkey.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The interesting difference in my problem (I think it's interesting...) > is that neither of the nameservers for dml.com are lame; they both > return valid A records for dml.com using dig, but my named seems to > think that there isn't an A record until I stop and restart named. > Then, when I do an nslookup / dig, it returns the correct result for > a while, until it stops working again. For what it's worth, my take: This could be broken down into a 2-part problem. One being bind not returning DNS data to sendmail, and two being that sendmail then defers the message based on the assumption that the lack of DNS data is in fact real. Sendmail is doing exactly what it should, IMHO. It relies on correct information from its nameserver(s), which in this case I don't think it's getting. I ran into the *exact* same problem with bind on a Linux machine. I then had several FreeBSD (and other *nixes like Solaris, OpenBSD, etc) fail with sendmail because my linux server would not give out data on domains for which: 1) the master servers did not set the authority bit in their DNS responses. 2) the TTL on the MX record for the domain was set to some low value, like 3600 seconds. Every single domain which sendmail had these delivery problems matched those two criteria points. What would happen is that on a bind restart, the MX data would be correctly cached for the TTL period (usually one hour) and then subsequent MX record lookups after the TTL expired would return serverfail, and from that point on sendmail would defer the mail because it thought the sender domain did not exist (and thus probably spam). Now, It seems like this problem sprouted its head when I moved up to bind 8.2.2-P7 from 8.2.2-P5. The BSD (Open, Free) boxes all had either 822p7, or some 823. Could this be a result of broken master nameservers and a change in how bind handled their responses? Flame away if I'm totally wrong. -- christopher matthew schulte geek boy gone bad christopher@schulte.org http://www.schulte.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 22:16: 2 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 75E9D37B69B for ; Wed, 17 Jan 2001 22:15:45 -0800 (PST) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 14J8MJ-000NQK-00; Wed, 17 Jan 2001 22:15:43 -0800 Date: Wed, 17 Jan 2001 22:15:37 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: William Denton Cc: freebsd-stable@freebsd.org Subject: Re: Perl's CGI.pm in the source tree In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Jan 2001, William Denton wrote: > reply, and the situation hasn't changed. Are there any plans to upgrade > the version of Perl's CGI.pm in the source tree? FAQ: the CGI.pm that is in the tree is the one that comes with the version of Perl that is in the tree. It is not going to be separately maintained. When the bug fixed perl 5.6 is available (right now?), and imported into the tree, whatever CGI.pm (if any) is included with it will be in the tree. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jan 17 23:18:22 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 F0EA337B400 for ; Wed, 17 Jan 2001 23:18:04 -0800 (PST) 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 SAA76962; Thu, 18 Jan 2001 18:17:52 +1100 (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 SAA27712; Thu, 18 Jan 2001 18:17:51 +1100 (EST) Message-Id: <200101180717.SAA27712@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Christopher Schulte Cc: stable@FreeBSD.ORG Subject: Re: Weird sporadic DNS resolution problems In-reply-to: Your message of Thu, 18 Jan 2001 00:14:03 -0600. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jan 2001 18:17:51 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For what it's worth, my take: This matches some of the things we've noticed here, but in our case sendmail was on a Solaris box using the FreeBSD box as a caching DNS server.... but it's slippery enough that I'm not confident what's going on. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 1: 0:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kyra.unloved.org (kyra.unloved.org [62.58.62.162]) by hub.freebsd.org (Postfix) with ESMTP id AE4AB37B400 for ; Thu, 18 Jan 2001 00:59:58 -0800 (PST) Received: from ashp by kyra.unloved.org with local (Exim 3.20 #1) id 14JAv9-00035s-00 for freebsd-stable@freebsd.org; Thu, 18 Jan 2001 09:59:51 +0100 Date: Thu, 18 Jan 2001 09:59:51 +0100 From: Ashley Penney To: freebsd-stable@freebsd.org Subject: Urgh, buildworld errors. Message-ID: <20010118095951.A11812@kyra.unloved.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 X-Loop: FreeBSD.ORG Hiya, I upgraded the box to -STABLE, because of problems with the ida device in 4.2-RELEASE. I noticed it failed to build ssh, so I figured I'd just buildworld again. Now I get: -------------------------------------------------------------- >>> Rebuilding the temporary build tree -------------------------------------------------------------- rm -rf /usr/obj/usr/src/i386 mkdir -p /usr/obj/usr/src/i386/usr/bin mkdir -p /usr/obj/usr/src/i386/usr/lib/compat/aout mkdir -p /usr/obj/usr/src/i386/usr/games mkdir -p /usr/obj/usr/src/i386/usr/libdata/ldscripts mkdir -p /usr/obj/usr/src/i386/usr/libexec/elf mkdir -p /usr/obj/usr/src/i386/usr/sbin mkdir -p /usr/obj/usr/src/i386/usr/share/misc mkdir -p /usr/obj/usr/src/i386/usr/include/arpa mkdir -p /usr/obj/usr/src/i386/usr/include/g++/std mkdir -p /usr/obj/usr/src/i386/usr/include/objc mkdir -p /usr/obj/usr/src/i386/usr/include/protocols mkdir -p /usr/obj/usr/src/i386/usr/include/readline mkdir -p /usr/obj/usr/src/i386/usr/include/rpc mkdir -p /usr/obj/usr/src/i386/usr/include/rpcsvc mkdir -p /usr/obj/usr/src/i386/usr/include/openssl mkdir -p /usr/obj/usr/src/i386/usr/include/security mkdir -p /usr/obj/usr/src/i386/usr/include/ss ln -sf /usr/src/sys /usr/obj/usr/src/i386/sys -------------------------------------------------------------- >>> stage 1: bootstrap tools -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" MACHINE_ARCH=i386 TOOLS_PREFIX=/usr/obj/usr/src/i386 PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML bootstrap-tools cd /usr/src/games/fortune/strfile; make obj; make depend; make all; make install /usr/obj/usr/src/i386/usr/src/games/fortune/strfile created for /usr/src/games/fortune/strfile rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/i386/usr/include /usr/src/games/fortune/strfile/strfile.c cd /usr/src/games/fortune/strfile; make _EXTRADEPEND echo strfile: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend cc -O -pipe -Wall -I/usr/obj/usr/src/i386/usr/include -c /usr/src/games/fortune/strfile/strfile.c cc -O -pipe -Wall -I/usr/obj/usr/src/i386/usr/include -o strfile strfile.o /usr/lib/crtbegin.o: In function `_init': /usr/lib/crtbegin.o(.init+0x0): multiple definition of `_init' /usr/lib/crti.o(.init+0x0): first defined here /usr/lib/crtbegin.o: In function `_fini': /usr/lib/crtbegin.o(.fini+0x0): multiple definition of `_fini' /usr/lib/crti.o(.fini+0x0): first defined here *** Error code 1 Stop in /usr/src/games/fortune/strfile. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. daphne# ---------------------------------------------------------------------- Do we really require fortune to build the world? What the hell is happening to me? I made sure /usr/obj was gone before trying to buildworld. :) -- "Go to Heaven for the climate, Hell for the company." -- Mark Twain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 2:10:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from level3.dynacom.net (level3.dynacom.net [206.107.213.213]) by hub.freebsd.org (Postfix) with SMTP id C04A137B400 for ; Thu, 18 Jan 2001 02:10:14 -0800 (PST) Received: (qmail 23737 invoked by uid 0); 18 Jan 2001 10:10:13 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 18 Jan 2001 10:10:13 -0000 Message-ID: <3A66C105.108DA108@urx.com> Date: Thu, 18 Jan 2001 02:10:13 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Ashley Penney Cc: freebsd-stable@freebsd.org Subject: Re: Urgh, buildworld errors. References: <20010118095951.A11812@kyra.unloved.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ashley Penney wrote: > > Hiya, > > I upgraded the box to -STABLE, because of problems with the ida device > in 4.2-RELEASE. I noticed it failed to build ssh, so I figured I'd just > buildworld again. Now I get: > > -------------------------------------------------------------- > >>> Rebuilding the temporary build tree > -------------------------------------------------------------- > rm -rf /usr/obj/usr/src/i386 > mkdir -p /usr/obj/usr/src/i386/usr/bin > mkdir -p /usr/obj/usr/src/i386/usr/lib/compat/aout > mkdir -p /usr/obj/usr/src/i386/usr/games > mkdir -p /usr/obj/usr/src/i386/usr/libdata/ldscripts > mkdir -p /usr/obj/usr/src/i386/usr/libexec/elf > mkdir -p /usr/obj/usr/src/i386/usr/sbin > mkdir -p /usr/obj/usr/src/i386/usr/share/misc > mkdir -p /usr/obj/usr/src/i386/usr/include/arpa > mkdir -p /usr/obj/usr/src/i386/usr/include/g++/std > mkdir -p /usr/obj/usr/src/i386/usr/include/objc > mkdir -p /usr/obj/usr/src/i386/usr/include/protocols > mkdir -p /usr/obj/usr/src/i386/usr/include/readline > mkdir -p /usr/obj/usr/src/i386/usr/include/rpc > mkdir -p /usr/obj/usr/src/i386/usr/include/rpcsvc > mkdir -p /usr/obj/usr/src/i386/usr/include/openssl > mkdir -p /usr/obj/usr/src/i386/usr/include/security > mkdir -p /usr/obj/usr/src/i386/usr/include/ss > ln -sf /usr/src/sys /usr/obj/usr/src/i386/sys > > -------------------------------------------------------------- > >>> stage 1: bootstrap tools > -------------------------------------------------------------- > cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" MACHINE_ARCH=i386 TOOLS_PREFIX=/usr/obj/usr/src/i386 PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 -DNOMAN -DNOINFO -DNOHTML bootstrap-tools > cd /usr/src/games/fortune/strfile; make obj; make depend; make all; make install > /usr/obj/usr/src/i386/usr/src/games/fortune/strfile created for /usr/src/games/fortune/strfile > rm -f .depend > mkdep -f .depend -a -I/usr/obj/usr/src/i386/usr/include /usr/src/games/fortune/strfile/strfile.c > cd /usr/src/games/fortune/strfile; make _EXTRADEPEND > echo strfile: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend > cc -O -pipe -Wall -I/usr/obj/usr/src/i386/usr/include -c /usr/src/games/fortune/strfile/strfile.c > cc -O -pipe -Wall -I/usr/obj/usr/src/i386/usr/include -o strfile strfile.o > /usr/lib/crtbegin.o: In function `_init': > /usr/lib/crtbegin.o(.init+0x0): multiple definition of `_init' > /usr/lib/crti.o(.init+0x0): first defined here > /usr/lib/crtbegin.o: In function `_fini': > /usr/lib/crtbegin.o(.fini+0x0): multiple definition of `_fini' > /usr/lib/crti.o(.fini+0x0): first defined here > *** Error code 1 You can check the archives around 10/30/2000 for a number of threads on this. O'Brien had to change the initialization stuff to keep the gcc people considering our system. The are a number of fixes. If the csu directory only has the Makefile in it, the following worked for me cd /usr/src/gnu/lib/csu make make install Then do your buildworld again. Some people had to do 2 "make cleandir"'s before the first make. Then the buildworld would finish. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 3: 6:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id 13A8737B6ED for ; Thu, 18 Jan 2001 03:05:57 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14JCrq-000O7j-00 for freebsd-stable@freebsd.org; Thu, 18 Jan 2001 14:04:36 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14JCtQ-0009Xw-00 for freebsd-stable@freebsd.org; Thu, 18 Jan 2001 14:06:12 +0300 Date: Thu, 18 Jan 2001 14:06:11 +0300 From: Courvette To: FBSD-STABLE Subject: Tape CANNOT be accessed after 3.5 --> 4.2-STABLE UPDATE Message-ID: <20010118140611.A36529@poeza.iconnect.co.ke> Mail-Followup-To: Courvette , FBSD-STABLE Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD poeza.iconnect.co.ke 4.2-STABLE FreeBSD 4.2-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I recently cvsupped and updated my 3.5-STABLE box to 4.2_STABLE. I had quite a few problems initially when doing buildworld but a good samaritan came to my rescue and sent me precise details that had worked for one of 'us'. I attach the e-mail below as it details the steps that I followed. I am not suggesting they could be flawed because my system is running - I'm only doing this so that whoever volunteers to help me will have a clear reference for my deeds. At the moment I seem to be in a bad fix because I cannot access my tape drive, an HP T20. What I mean is that mt returns an error /dev/nsa0: device not configured. I posted this to the -quetsions and I got overwhelming response but all the suggestions I received did not yield the solution I was looking for. So please pardon me if this is considered a double post. I am only anxious for a solution. Without a backup, we all know where I stand - on the firing line. I am running an HP Netserver E20 and here is a section of my dmesg.boot: ## [snip] ahc0: port 0x1000-0x10ff mem 0xfc100000-0xfc100fff irq 10 at device 5.0 on pci0 ahc0: Using left over BIOS settings aic7895C: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0x1400-0x14ff mem 0xfc101000-0xfc101fff irq 10 at device 5.1 on pci0 ahc1: Host Adapter Bios disabled. Using default SCSI device parameters aic7895C: Wide Channel B, SCSI Id=7, 32/255 SCBs . . . Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 3.300MB/s transfers da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8678MB (17773524 512 byte sectors: 64H 32S/T 8678C) Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8678MB (17773524 512 byte sectors: 64H 32S/T 8678C) [snip] and here is some output from /dev wash:~$ cd /dev/ wash:/dev$ ls -al *sa0 crw-rw---- 4 root operator 14, 2 Jan 18 12:18 ersa0 crw-rw---- 4 root operator 14, 2 Jan 18 12:18 esa0 crw-rw---- 4 root operator 14, 1 Jan 18 12:18 nrsa0 crw-rw---- 4 root operator 14, 1 Jan 18 12:18 nsa0 crw-rw---- 4 root operator 14, 0 Jan 18 12:18 rsa0 crw-rw---- 4 root operator 14, 0 Jan 18 12:18 sa0 ...and a little bit more... wash:/dev$ mt status mt: /dev/nsa0: Device not configured And I followed the procedure below to go to 4.2_STABLE... All help welcome. Thanks. I went from 3.5-STABLE to 4.1.1-STABLE using these instructions and it worked great. Good luck, ####################################################################### Upgrading from FreeBSD 3.5-STABLE to FreeBSD 4.1-STABLE ###################################################################### Ralf S. Engelschall , August 2000 o boot the old FreeBSD 3.x in multi-user mode o provide a particular build environment $ vi /etc/make.conf NOPERL=true # else Perl would fail to build under 3.x initially NOPROFILE=true # to speed up building MAKE_RSAINTL=YES # for non-US USA_RESIDENT=NO # dito. CFLAGS= -O -pipe # standard optimization COPTFLAGS=-O -pipe # dito. COMPAT1X=yes # install compatibility libraries COMPAT20=yes # dito. COMPAT21=yes # dito. COMPAT22=yes # dito. COMPAT3X=yes # dito. o provide boot-strapping run-time environment $ mkdir -p /usr/obj/usr/src/lib/libc $ ldconfig -R /usr/obj/usr/src/lib/libc o build the world initially (still under FreeBSD 3.x run-time) $ cd /usr/obj $ chflags -R noschg * $ rm -rf * $ cd /usr/src $ make buildworld o build and install new GENERIC kernel+modules $ make buildkernel KERNEL=GENERIC $ make installkernel KERNEL=GENERIC $ chflags noschg /kernel.GENERIC /GENERIC $ mv /kernel.GENERIC /kernel.GENERIC.3 $ mv /GENERIC /kernel.GENERIC $ chflags schg /kernel.GENERIC o upgrade FOO kernel config from 3.x to 4.x $ vi /sys/i386/conf/FOO - remove "config kernel ...", "bio", "tty", "net", "conflicts" - remove unnecessary quotations - remove "pnp" device - remove "acd0" device - remove obsolete options (check output of "config FOO") - replace some "xxx0" with "xxx" (compare LINT for details) - replace "controller" & "disk" with "device" - replace "wdc0" with "ata0" plus more "ata*" from GENERIC - replace "bpfilter" with "bpf" - replace "isa?" with "atkbdc?" for "atkbd0" and "psm0" device o build and install new FOO kernel+modules $ make buildkernel KERNEL=FOO $ make installkernel KERNEL=FOO $ chflags noschg /kernel /FOO $ mv /kernel /kernel.3 $ mv /FOO /kernel $ chflags schg /kernel o upgrade devices $ cd /usr/src/sbin/mknod && make install $ cp /usr/src/etc/MAKEDEV* /dev $ cd /dev $ sh MAKEDEV all - make sure really all devices for disks exists: for N in the list of disks sh MAKEDEV N # eg ad0 for M in the list of slices sh MAKEDEV NsMa # eg ad0s1a - edit /etc/fstab and replace "wd0" with "ad0" o upgrade boot blocks and loader $ cd /sys/boot && make install o boot FreeBSD 4.x kernel (still with 3.x user-land) in single-user mode $ shutdown -r now > boot -s $ mount -a o install the world $ cd /usr/src/gnu/usr.bin/texinfo/install-info=20 $ make install $ ldconfig -R /usr/obj/usr/src/lib/libc $ cd /usr/src $ make installworld $ cd /usr/src/release/sysinstall && make all install o upgrade /etc $ cp -rp /etc /etc.old $ mergemaster -v -s o final adjustments for new FreeBSD 4.x user-land $ touch /var/log/security $ touch /var/log/cron $ rm /var/cron/log* o switch to new shipped OpenSSH [OPTIONAL!] $ ssh-keygen -f /etc/ssh/ssh_host_key $ ssh-keygen -d -f /etc/ssh/ssh_host_dsa_key $ vi /etc/rc.conf sshd_enable="YES" $ pkg_delete ssh-1.2.27 o boot FreeBSD 4.x kernel and user-land in multi-user mode $ shutdown -r now o rebuild some criticial programs to avoid spurious segfaults under the forthcoming final "buildworld/installworld" step $ vi /etc/make.conf #NOPERL=true $ cd /usr/src/gnu/usr.bin/perl=20 $ (cd libperl && make all install) $ (cd perl && make all install) $ make clean all install $ cd /usr/src/usr.bin/lex && make clean all install $ cd /usr/src/usr.bin/yacc && make clean all install $ cd /usr/src/gnu/usr.bin/as && make clean all install $ cd /usr/src/gnu/usr.bin/cc && make clean all install $ cd /usr/src/gnu/lib/libgcc && make clean all install o build and install the world finally from scratch (under FreeBSD 4.x run-= time) $ cd /usr/obj $ chflags -R noschg * $ rm -rf * $ cd /usr/src $ make buildworld $ make installworld o rebuild the kernel with the final tools $ cd /sys/i386/conf $ config FOO $ cd /sys/compile/FOO $ make depend all $ make install o reboot to switch to the final FreeBSD 4.x system $ shutdown -r now -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. Good friends, good books and a sleepy conscience: this is the ideal life. -Mark Twain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 3:58:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 9B48C37B400 for ; Thu, 18 Jan 2001 03:58:16 -0800 (PST) Received: from jamestown.enteract.com (207-229-151-11.d.enteract.com [207.229.151.11]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id FAA67978 for ; Thu, 18 Jan 2001 05:58:15 -0600 (CST) (envelope-from jtm@enteract.com) Received: by jamestown.enteract.com (8.9.3/8.9.3) id FAA02699 for freebsd-stable@freebsd.org; Thu, 18 Jan 2001 05:56:58 -0600 (CST) (envelope-from jtm) From: James McNaughton Reply-To: jtm63@enteract.com To: freebsd-stable@freebsd.org Subject: Re: cdcontrol and environment vars - opinions please. Date: Thu, 18 Jan 2001 05:52:05 -0600 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <20010116121921.A632@tao.org.uk> In-Reply-To: <20010116121921.A632@tao.org.uk> MIME-Version: 1.0 Message-Id: <01011805565800.01371@jamestown.enteract.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 16 Jan 2001, you wrote: > How many people are using cdcontrol and defining the drive name > using one of the following environment variables: MUSIC_CD, CD_DRIVE, > DISC and CDPLAY? I prefer to have MUSIC_CD since that makes sense to me. I have two such devices and this environment variable points to the one that plays music. Is it really such a problem that it needs to be changed? Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 4:30:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.147.224.201]) by hub.freebsd.org (Postfix) with ESMTP id 2ADDC37B401; Thu, 18 Jan 2001 04:30:08 -0800 (PST) Received: from thehousleys.net (baby.int.thehousleys.net [192.168.0.24]) by thehousleys.net (8.11.1/8.11.1) with ESMTP id f0ICU0f54837; Thu, 18 Jan 2001 07:30:01 -0500 (EST) (envelope-from jim@thehousleys.net) Message-ID: <3A66E1C8.E07626A4@thehousleys.net> Date: Thu, 18 Jan 2001 07:30:00 -0500 From: James Housley X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brian Behlendorf Cc: Kris Kennaway , freebsd-stable@FreeBSD.ORG Subject: Re: sshd not working after upgrade to 4.2S from 4.1R HELP References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Behlendorf wrote: > Hmm - I ran mergemaster after my last make world, and it didn't pick up > the differences between /etc/pam.conf and /usr/src/etc/pam.conf > either. The /etc/pam.conf I had hadn't been changed since my last full > install, though I'd done a make world/mergemaster 3 times since > then. Curious. > Try running mergemaster -s, this will force a full comparison of the files. By default mergemaster only compare the $FreeBSD$ strings at the top to speed up comparison. Jim -- /"\ ASCII Ribbon Campaign . \ / - NO HTML/RTF in e-mail . X - NO Word docs in e-mail . / \ ----------------------------------------------------------------- jeh@FreeBSD.org http://www.FreeBSD.org The Power to Serve jim@TheHousleys.Net http://www.TheHousleys.net --------------------------------------------------------------------- Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 4:47:33 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 9F52D37B400 for ; Thu, 18 Jan 2001 04:47:15 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0IClEX38774; Thu, 18 Jan 2001 07:47:14 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0ICl8d38766; Thu, 18 Jan 2001 07:47:08 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010118074255.01fc96e8@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 18 Jan 2001 07:47:07 -0500 To: Gregory Bond , Christopher Schulte From: Mike Tancsa Subject: Re: Weird sporadic DNS resolution problems Cc: stable@freebsd.org In-Reply-To: <200101180717.SAA27712@lightning.itga.com.au> References: 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 X-Loop: FreeBSD.ORG At 06:17 PM 1/18/2001 +1100, Gregory Bond wrote: > > For what it's worth, my take: > >This matches some of the things we've noticed here, but in our case sendmail >was on a Solaris box using the FreeBSD box as a caching DNS server.... but >it's slippery enough that I'm not confident what's going on. Actually, this sounds very familiar, especially with the BIND revs. Looking through its CHANGES entry, the only thing I could find that would vaguely refer to such a change is 941. [bug] lame server detection wasn't checking for SOA record. I wonder if using BIND 9.x fixes this "bug" ---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 Thu Jan 18 5:26:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from server.localdomain.net (unknown [194.244.229.102]) by hub.freebsd.org (Postfix) with ESMTP id AFF3F37B400 for ; Thu, 18 Jan 2001 05:26:06 -0800 (PST) Received: from server.localdomain.net (server.localdomain.net [192.168.1.1]) by server.localdomain.net (8.9.3/8.8.7) with ESMTP id OAA23883; Thu, 18 Jan 2001 14:23:30 +0100 Date: Thu, 18 Jan 2001 14:23:30 +0100 (CET) From: Jimmy Olgeni X-Sender: To: "Louis A. Mamakos" Cc: Gerhard Sittig , FreeBSD Stable Subject: Re: odd mouse button behavior In-Reply-To: <200101160330.f0G3UAE03875@whizzo.transsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Latest discovery: the mouse will work fine if you choose "/dev/pms0" and "auto" as mouse device and protocol type. But you have to kill "moused". Looks like XFree-4 does not like moused for some reason... -- jimmy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 6: 4: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 5CBF537B400 for ; Thu, 18 Jan 2001 06:03:47 -0800 (PST) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id f0IE3dQ57993; Thu, 18 Jan 2001 09:03:39 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200101181403.f0IE3dQ57993@whizzo.transsys.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jimmy Olgeni Cc: Gerhard Sittig , FreeBSD Stable X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: odd mouse button behavior References: In-reply-to: Your message of "Thu, 18 Jan 2001 14:23:30 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jan 2001 09:03:39 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Latest discovery: the mouse will work fine if you choose "/dev/pms0" > and "auto" as mouse device and protocol type. But you have to kill > "moused". > > Looks like XFree-4 does not like moused for some reason... It sounds then like some weird moused interaction. Not using moused is probably not an option for me, as I'm using a USB mouse. But it does give me a place to start looking. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 6:54:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 1539637B400 for ; Thu, 18 Jan 2001 06:53:53 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id D37C757587; Thu, 18 Jan 2001 08:53:59 -0600 (CST) Date: Thu, 18 Jan 2001 08:53:59 -0600 From: "Michael C . Wu" To: "Louis A. Mamakos" Cc: Jimmy Olgeni , Gerhard Sittig , FreeBSD Stable Subject: Re: odd mouse button behavior Message-ID: <20010118085359.B19987@peorth.iteration.net> Reply-To: "Michael C . Wu" Mail-Followup-To: "Michael C . Wu" , "Louis A. Mamakos" , Jimmy Olgeni , Gerhard Sittig , FreeBSD Stable References: <200101181403.f0IE3dQ57993@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101181403.f0IE3dQ57993@whizzo.transsys.com>; from louie@TransSys.COM on Thu, Jan 18, 2001 at 09:03:39AM -0500 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 18, 2001 at 09:03:39AM -0500, Louis A. Mamakos scribbled: | > Latest discovery: the mouse will work fine if you choose "/dev/pms0" | > and "auto" as mouse device and protocol type. But you have to kill | > "moused". | > | > Looks like XFree-4 does not like moused for some reason... Of course, you are trying to run a mouse driver on XFree86 when the mouse device is being used by moused. | It sounds then like some weird moused interaction. Not using moused | is probably not an option for me, as I'm using a USB mouse. But it does | give me a place to start looking. XFree has always had a mouse driver of its own. You've unearthed the original missing link's wheel prototype. :) You can modify /etc/usbd.conf to not start moused for you. Simply replace "/dev/psm0" in XF86Config with "/dev/ums0" -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 7: 4:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lorne.arm.org (64-40-71-66.mebtel.net [64.40.71.66]) by hub.freebsd.org (Postfix) with ESMTP id C5C3537B401 for ; Thu, 18 Jan 2001 07:04:22 -0800 (PST) Received: (from dlt@localhost) by lorne.arm.org (8.11.1/8.11.1) id f0IF39A07685; Thu, 18 Jan 2001 10:03:10 -0500 (EST) (envelope-from dlt@mebtel.net) X-Authentication-Warning: lorne.arm.org: dlt set sender to dlt@mebtel.net using -f To: Drew Sanford Cc: FreeBSD-stable@FreeBSD.org Subject: Re: Athlon and 4.2 Release References: <867l3wfiqr.fsf@lorne.arm.org> <3A63B70E.40306@planetwe.com> From: Derek Tattersall Date: 18 Jan 2001 10:03:09 -0500 In-Reply-To: <3A63B70E.40306@planetwe.com> Message-ID: <86wvbsrjgy.fsf@lorne.arm.org> Lines: 39 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 X-Loop: FreeBSD.ORG Drew Sanford writes: > I strongly suspect its an IRQ conflict. Every problem of this sort > that I've seen with the A7V has been an IRQ conflict, including the > problem I had with my own. Specificly I had to hard set the IRQ on my > NIC through the PCI management section of the bios. > > Derek Tattersall wrote: > > > I have a 1 GHz Thunderbird (Athlon) on an ASUS A7V Via KT133 chipset > > with an IBM ultra 100 30 Gig Hard drive. If I let the HDD be auto > > detected, 4.2 Release terminates at the point it is going to > > partition the drive. If I set the HDD for LBA with all the options > > disabled, > > it reboots in the middle of the boot sequence, after the "press enter > > to boot now prompt". > > Has anybody got configuration suggestions for this combination that > > could get FreeBSD installed? > > Thanks in advance... > > > -- > Drew Sanford > Systems Administrator > drew@planetwe.com > It certainly is an IRQ conflict between the 3C905B NIC and the promise controller. I could install and reboot just fine with the NIC removed. I tried setting different IRQs for the NIC (in slot 3) but the BIOS always put the promise controller on the same IRQ. More research is required. I think I'll see if I can borrow a NIC from work, a totally different brand and see what happens. -- Derek Tattersall dlt@mebtel.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 7: 7:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.a1.org.uk (ns.a1.org.uk [194.105.64.163]) by hub.freebsd.org (Postfix) with ESMTP id 7EC7337B400 for ; Thu, 18 Jan 2001 07:07:06 -0800 (PST) Received: (from aer001@localhost) by ns.a1.org.uk (8.9.3/8.9.3) id PAA74417 for stable@freebsd.org; Thu, 18 Jan 2001 15:07:00 GMT (envelope-from aer001) From: Catch-all m-box Message-Id: <200101181507.PAA74417@ns.a1.org.uk> Subject: Re: odd mouse button behavior In-Reply-To: <20010118085359.B19987@peorth.iteration.net> from "Michael C . Wu" at "Jan 18, 2001 08:53:59 am" To: stable@freebsd.org Date: Thu, 18 Jan 2001 15:06:59 +0000 (GMT) Reply-To: 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 X-Loop: FreeBSD.ORG > On Thu, Jan 18, 2001 at 09:03:39AM -0500, Louis A. Mamakos scribbled: > | > Latest discovery: the mouse will work fine if you choose "/dev/pms0" > | > and "auto" as mouse device and protocol type. But you have to kill > | > "moused". > | > > | > Looks like XFree-4 does not like moused for some reason... > > Of course, you are trying to run a mouse driver on XFree86 when > the mouse device is being used by moused. > > | It sounds then like some weird moused interaction. Not using moused > | is probably not an option for me, as I'm using a USB mouse. But it does > | give me a place to start looking. > > XFree has always had a mouse driver of its own. > You've unearthed the original missing link's wheel prototype. :) > > You can modify /etc/usbd.conf to not start moused for you. > Simply replace "/dev/psm0" in XF86Config with "/dev/ums0" > I run moused and have a working mouse with X 4. ( MS Intelli and clones ) I use Section "Pointer" #Protocol "Microsoft" Protocol "auto" Device "/dev/mouse" EndSection in XF86Config ( have not bothered to goto InputDevice yet! ) and a ps ax|grep mouse 225 ?? Ss 0:09.18 moused -p /dev/psm0 -t auto Bap. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 7:32:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id 1233D37B402 for ; Thu, 18 Jan 2001 07:31:58 -0800 (PST) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0IFVuq59445 for ; Thu, 18 Jan 2001 16:31:56 +0100 (CET) Received: from rose.lpthe.jussieu.fr (root@[134.157.10.102]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0IFVu315744 for ; Thu, 18 Jan 2001 16:31:56 +0100 (MET) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.11.1/8.11.1) id f0IFVsv00938 for freebsd-stable@FreeBSD.ORG; Thu, 18 Jan 2001 16:31:54 +0100 (CET) (envelope-from michel) Date: Thu, 18 Jan 2001 16:31:54 +0100 From: Michel Talon To: FreeBSD Stable Subject: Re: odd mouse button behavior Message-ID: <20010118163154.A919@lpthe.jussieu.fr> Mail-Followup-To: FreeBSD Stable References: <200101160330.f0G3UAE03875@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 18, 2001 at 02:23:30PM +0100, Jimmy Olgeni wrote: > > Latest discovery: the mouse will work fine if you choose "/dev/pms0" > and "auto" as mouse device and protocol type. But you have to kill > "moused". > > Looks like XFree-4 does not like moused for some reason... > > -- Sure not true. I have several FreeBSD installs (including laptop with touchpad) using XFree 4.02 and moused. You need to declare /dev/sysmouse for the device, and auto for the protocol. -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 7:39:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id B16C737B401 for ; Thu, 18 Jan 2001 07:39:28 -0800 (PST) Received: from jking (jking.lgc.com [134.132.76.82]) by cgi.sstar.com (8.11.1/8.11.1) with SMTP id f0IFch998020 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Thu, 18 Jan 2001 09:38:50 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <002901c08164$c14f3440$524c8486@jking> From: "Jim King" To: "Michel Talon" , "FreeBSD Stable" References: <200101160330.f0G3UAE03875@whizzo.transsys.com> <20010118163154.A919@lpthe.jussieu.fr> Subject: Re: odd mouse button behavior Date: Thu, 18 Jan 2001 09:38:43 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Michel Talon" wrote: > On Thu, Jan 18, 2001 at 02:23:30PM +0100, Jimmy Olgeni wrote: > > > > Latest discovery: the mouse will work fine if you choose "/dev/pms0" > > and "auto" as mouse device and protocol type. But you have to kill > > "moused". > > > > Looks like XFree-4 does not like moused for some reason... > > > > -- > > > Sure not true. I have several FreeBSD installs (including laptop with > touchpad) using XFree 4.02 and moused. You need to declare > /dev/sysmouse for the device, and auto for the protocol. On my desktop system with a Logitech PS/2 mouse, XF 4.0.2 worked with moused, but the mouse pointer seemed to move very oddly (sort of a choppy motion) and clicks sometimes didn't register. I killed moused and switched XF to PS/2 protocol and it works fine now. There's definitely something going on between moused and XF 4.0.2. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 8:31:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by hub.freebsd.org (Postfix) with ESMTP id A200C37B698; Thu, 18 Jan 2001 08:31:34 -0800 (PST) Received: from manor.msen.com (wayne@localhost [127.0.0.1]) by manor.msen.com (8.9.3/8.9.3) with ESMTP id LAA32357; Thu, 18 Jan 2001 11:31:33 -0500 (EST) (envelope-from wayne@manor.msen.com) Message-Id: <200101181631.LAA32357@manor.msen.com> To: freebsd-isp@freebsd.org, freebsd-stable@freebsd.org Subject: No OSPF with gated 3.6 on FreeBSD 4.2 stable Date: Thu, 18 Jan 2001 11:31:33 -0500 From: "Michael R. Wayne" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We brought up a new box on a January 9th build of 4.2 stable. Everything seemed fine until we fired up gated 3.6 public (current port). gated comes up properly but it won't talk OSPF at all (other OSPF routers never see any OSPF packets and gated_dump shows no OSPF activity). The config file is a clone from a working 3.3 system with only the IP address changed to that of the new machine. Replaced the binary with the one from the 3.3 machine (and installed the required shared library) - same result. So the culprit appears to be the kernel. I did not notice anything on freebsd-stable regarding this lately but it's possible that it was buried under something else and I missed it. Any ideas? /\/\ \/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 8:43: 5 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id C3A3D37B401; Thu, 18 Jan 2001 08:42:42 -0800 (PST) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.1/8.11.1) with ESMTP id f0IGgdW82993; Thu, 18 Jan 2001 11:42:39 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.0.20010118113308.025eeb00@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Thu, 18 Jan 2001 11:36:11 -0500 To: "Michael R. Wayne" , freebsd-isp@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: No OSPF with gated 3.6 on FreeBSD 4.2 stable In-Reply-To: <200101181631.LAA32357@manor.msen.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:31 AM 1/18/01 -0500, Michael R. Wayne wrote: >I did not notice anything on freebsd-stable regarding this lately but >it's possible that it was buried under something else and I missed it. I have gated running OSPF on a bunch of 4.x boxes. Are you sure you have all the correct kernel params ? Is ipforwarding turned on as well ? ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 8:46:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from yertle.kciLink.com (yertle.kciLink.com [208.184.13.195]) by hub.freebsd.org (Postfix) with ESMTP id DA6E137B401 for ; Thu, 18 Jan 2001 08:46:07 -0800 (PST) Received: from onceler.kciLink.com (onceler.kciLink.com [208.184.13.196]) by yertle.kciLink.com (Postfix) with ESMTP id 1BE512E443 for ; Thu, 18 Jan 2001 11:46:07 -0500 (EST) Received: (from khera@localhost) by onceler.kciLink.com (8.11.1/8.11.1) id f0IGk7b76865; Thu, 18 Jan 2001 11:46:07 -0500 (EST) (envelope-from khera) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14951.7630.955650.431804@onceler.kciLink.com> Date: Thu, 18 Jan 2001 11:46:06 -0500 To: freebsd-stable@freebsd.org Subject: Re: Perl's CGI.pm in the source tree In-Reply-To: References: X-Mailer: VM 6.88 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "WD" == William Denton writes: WD> Hi, WD> I saw someone ask about this last year, but I don't think there was a WD> reply, and the situation hasn't changed. Are there any plans to upgrade WD> the version of Perl's CGI.pm in the source tree? I don't think it should be updated. If you did so, you could then argue that all sorts of things that are more up-to-date on the CPAN should be merged back as well. This is a dangerous path to tread. Having perl 5.005_03 on the system should imply just that -- nothing more and nothing less and nothing substantially different. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 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 Thu Jan 18 10:16:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f186.law10.hotmail.com [64.4.15.186]) by hub.freebsd.org (Postfix) with ESMTP id 027F937B400 for ; Thu, 18 Jan 2001 10:16:27 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 18 Jan 2001 10:16:26 -0800 Received: from 24.50.187.142 by lw10fd.law10.hotmail.msn.com with HTTP; Thu, 18 Jan 2001 18:16:26 GMT X-Originating-IP: [24.50.187.142] From: "Nader Turki" To: freebsd-stable@FreeBSD.org Subject: ports Date: Thu, 18 Jan 2001 13:16:26 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 18 Jan 2001 18:16:26.0722 (UTC) FILETIME=[C594A420:01C0817A] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I updated my ports, and wheni try installing pine i get an error. ===> Extracting for pine-4.31 >>Checksum OK for pine4.31.tar.gz. ===> pine-4.31 depends on shared library: c-client4.8 - not found ===> Verifying install for c-client4.8 in /usr/ports/mail/cclient ===> Extracting for cclient-4.8 >>Checksum OK for imap-2000a.tar.Z. ===> Patching for cclient-4.8 ===> Applying FreeBSD patches for cclient-4.8 1 out of 1 hunks failed--saving rejects to src/osdep/unix/mx.c.rej >>Patch patch-ad failed to apply cleanly. >>Patch(es) patch-aa patch-ab patch-ac applied cleanly. *** Error code 1 Stop in /usr/ports/mail/cclient. *** Error code 1 Stop in /usr/ports/mail/cclient. *** Error code 1 Stop in /usr/ports/mail/cclient. *** Error code 1 Stop in /usr/ports/mail/cclient. *** Error code 1 Stop in /usr/ports/mail/cclient. *** Error code 1 Stop in /usr/ports/mail/cclient. *** Error code 1 Stop in /usr/ports/mail/pine4. *** Error code 1 Stop in /usr/ports/mail/pine4. *** Error code 1 Stop in /usr/ports/mail/pine4. *** Error code 1 Stop in /usr/ports/mail/pine4. *** Error code 1 Stop in /usr/ports/mail/pine4. *** Error code 1 Stop in /usr/ports/mail/pine4. Hope someone can help me with this problem. Thanks, Nader _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 11:31:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from veldy.net (w028.z064001117.msp-mn.dsl.cnc.net [64.1.117.28]) by hub.freebsd.org (Postfix) with ESMTP id 01DDF37B400 for ; Thu, 18 Jan 2001 11:31:28 -0800 (PST) Received: from HP2500B (veldy.net [64.1.117.28]) by veldy.net (Postfix) with SMTP id 48DED8C13; Thu, 18 Jan 2001 13:30:58 -0600 (CST) Message-ID: <024201c08185$44c5efb0$3028680a@tgt.com> From: "Thomas T. Veldhouse" To: "Nader Turki" , References: Subject: Re: ports Date: Thu, 18 Jan 2001 13:31:32 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hate that when that happens. It has happened with a lot of ports lately (i.e. unixODBC). I usually figure the port was upgraded but the patches weren't removed - so I remove them. It usually works :( Tom Veldhouse veldy@veldy.net ----- Original Message ----- From: "Nader Turki" To: Sent: Thursday, January 18, 2001 12:16 PM Subject: ports > Hi guys, > > I updated my ports, and wheni try installing pine i get an error. > > ===> Extracting for pine-4.31 > >>Checksum OK for pine4.31.tar.gz. > ===> pine-4.31 depends on shared library: c-client4.8 - not found > ===> Verifying install for c-client4.8 in /usr/ports/mail/cclient > ===> Extracting for cclient-4.8 > >>Checksum OK for imap-2000a.tar.Z. > ===> Patching for cclient-4.8 > ===> Applying FreeBSD patches for cclient-4.8 > 1 out of 1 hunks failed--saving rejects to src/osdep/unix/mx.c.rej > >>Patch patch-ad failed to apply cleanly. > >>Patch(es) patch-aa patch-ab patch-ac applied cleanly. > *** Error code 1 > > Stop in /usr/ports/mail/cclient. > *** Error code 1 > > Stop in /usr/ports/mail/cclient. > *** Error code 1 > > Stop in /usr/ports/mail/cclient. > *** Error code 1 > > Stop in /usr/ports/mail/cclient. > *** Error code 1 > > Stop in /usr/ports/mail/cclient. > *** Error code 1 > > Stop in /usr/ports/mail/cclient. > *** Error code 1 > > Stop in /usr/ports/mail/pine4. > *** Error code 1 > > Stop in /usr/ports/mail/pine4. > *** Error code 1 > > Stop in /usr/ports/mail/pine4. > *** Error code 1 > > Stop in /usr/ports/mail/pine4. > *** Error code 1 > > Stop in /usr/ports/mail/pine4. > *** Error code 1 > > Stop in /usr/ports/mail/pine4. > > Hope someone can help me with this problem. > > Thanks, > > Nader > _________________________________________________________________ > Get your FREE download of MSN Explorer at http://explorer.msn.com > > > > 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 Thu Jan 18 11:34:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (unknown [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 918CA37B402 for ; Thu, 18 Jan 2001 11:34:07 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0IJmXQ00714; Thu, 18 Jan 2001 11:48:34 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101181948.f0IJmXQ00714@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Derek Tattersall Cc: Drew Sanford , FreeBSD-stable@FreeBSD.org Subject: Re: Athlon and 4.2 Release In-reply-to: Your message of "18 Jan 2001 10:03:09 EST." <86wvbsrjgy.fsf@lorne.arm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jan 2001 11:48:33 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I strongly suspect its an IRQ conflict. Every problem of this sort > > that I've seen with the A7V has been an IRQ conflict, including the > > problem I had with my own. Specificly I had to hard set the IRQ on my > > NIC through the PCI management section of the bios. ... > It certainly is an IRQ conflict between the 3C905B NIC and the promise > controller. I could install and reboot just fine with the NIC > removed. Er, folks, no. You can share IRQs just fine with PCI. You don't have "IRQ conflicts" just because two devices are driving the same interrupt. There are plenty of other possibilites for trouble, but having the same IRQ is not in and of itself going to do this. -- ... 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 Thu Jan 18 11:55:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 01A7E37B404 for ; Thu, 18 Jan 2001 11:55:10 -0800 (PST) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id LAA10283; Thu, 18 Jan 2001 11:55:04 -0800 (PST) Message-ID: <3A674A18.E6F413EB@isi.edu> Date: Thu, 18 Jan 2001 11:55:04 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Jamil Taylor Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SMP & signal 11 References: <3A65DC2A.8A15BEE1@isi.edu> <3A66446F.51A10752@isi.edu> <3A664A43.F54854C@pobox.com> <3A664B6E.5291BD15@isi.edu> <3A664DAA.35E2635C@pobox.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msCF2951F7379EE5A564CB63FE" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------msCF2951F7379EE5A564CB63FE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jamil Taylor wrote: > > Do you still have that kernel config file handy? Maybe I'll try it on our > > 620s. > > I will send my kernel config under separate email. Now we're getting somewhere! Running a kernel compiled from your config file, the system runs stable with both CPUs turned on. I'm trying to figure out which entry in my config file breaks things; I'll post when I have it. Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------msCF2951F7379EE5A564CB63FE Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDExODE5NTUwNFowIwYJKoZIhvcNAQkEMRYE FNlS2oURzr3ooSD5OWsS7aPygqVwMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAPWbOZaZCLTaN0NPV8x2CRzZjpQz87V9hiHYYMSmBMfFjJ/rjQBzG OvUDPwdaKephi+0GOH7lNNX3k0xzyr0W9cEFX2HN9wvGtkvGfPe4dM5ICAgjRpeFFV3k0KAb uorRLT3zMzwxHwUg+fWs4tTWeuU1wS/21qa2aYx7CNefS64= --------------msCF2951F7379EE5A564CB63FE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 11:58:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.cb21.co.jp (ns1.cb21.co.jp [203.140.149.254]) by hub.freebsd.org (Postfix) with SMTP id 19ABC37B400 for ; Thu, 18 Jan 2001 11:58:41 -0800 (PST) Received: (qmail 55027 invoked from network); 19 Jan 2001 04:58:29 +0900 Received: from localhost.cb21.co.jp (HELO localhost) (127.0.0.1) by localhost.cb21.co.jp with SMTP; 19 Jan 2001 04:58:29 +0900 To: mike@sentex.net Cc: freebsd-stable@freebsd.org Subject: Re: RAID configuration for a mail server (1 or 5) From: Sys Admin In-Reply-To: <4.2.2.20010117193231.03731950@marble.sentex.net> References: <4.2.2.20010117193231.03731950@marble.sentex.net> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010119045829R.admin@cb21.co.jp> Date: Fri, 19 Jan 2001 04:58:29 +0900 X-Dispatcher: imput version 20000228(IM140) Lines: 25 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From Mike Tancsa ... > Questions is more appropriate. Also, you may want to scan through the I really had a difficulty in decideing which list is the most appropriate. scsi, hardware all came to mind since the question is not specific to either of the lists , I thought stable or isp would be better as I thought people runing real stable systems must be on those lists! > archives, as questions like this have been asked and answered > before. www.dejanews.com is your friend and Oracle! This indeed is true. A search for "Raid Mail Server" resulted in 7000 odd responses! > For speed, reliability and cost, have a look at the 4port 3ware card > (www.3ware.com) in RAID 10 config. Two RAID0 sets mirrored together. Get > yourself some inexpensive drawers ( eg > http://www.startech.com/ststore/ItemDetail.cfm?Product_ID=IDE66BASIC) and Thanks for the info. I will have a look. Tad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 12:39:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id D9FD737B401 for ; Thu, 18 Jan 2001 12:39:17 -0800 (PST) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.1/8.11.1) with ESMTP id f0IKdEI34899; Thu, 18 Jan 2001 15:39:14 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.0.20010118153121.0221a480@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Thu, 18 Jan 2001 15:32:44 -0500 To: Sys Admin From: Mike Tancsa Subject: Re: RAID configuration for a mail server (1 or 5) Cc: freebsd-stable@freebsd.org In-Reply-To: <20010119045829R.admin@cb21.co.jp> References: <4.2.2.20010117193231.03731950@marble.sentex.net> <4.2.2.20010117193231.03731950@marble.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:58 AM 1/19/01 +0900, Sys Admin wrote: >to either of the lists , I thought stable or isp would be better as I thought >people runing real stable systems must be on those lists! ISP is fine... I would have answered your question there later in the evening. This list about STABLE, not stable (i.e. the stability of FreeBSD). The term STABLE in this case refers to issues around the tracking of FreeBSD through cvsup between releases. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 13: 5:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wgate.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 96EC837B400 for ; Thu, 18 Jan 2001 13:05:25 -0800 (PST) Received: from way95.eng.tvol.net ([10.32.1.145]) by mail.wgate.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id CX5HQP9S; Thu, 18 Jan 2001 16:05:28 -0500 Received: from kway by way95.eng.tvol.net with local (Exim 3.20 #1 (Debian)) id 14JMFH-0000Se-00; Thu, 18 Jan 2001 16:05:23 -0500 Date: Thu, 18 Jan 2001 16:05:23 -0500 From: Kevin Way To: Jimmy Olgeni Cc: freebsd-stable@freebsd.org Subject: Re: odd mouse button behavior Message-ID: <20010118160523.A1634@way95.eng.tvol.net> References: <200101160330.f0G3UAE03875@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.12i In-Reply-To: ; from olgeni@uli.it on Thu, Jan 18, 2001 at 02:23:30PM +0100 Organization: WorldGate Communications [www.wgate.com] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Looks like XFree-4 does not like moused for some reason... I use XFree-4 with moused, and a usb mouse, no problem. rc.conf: moused_enable="YES" moused_port="/dev/ums0" moused_type="auto" XF86Config: Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" EndSection works like a champ. --Kevin -- kevin way worldgate communications software engineer +1 215 354 5287 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 13:15: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 6F58737B401 for ; Thu, 18 Jan 2001 13:14:39 -0800 (PST) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id NAA22028; Thu, 18 Jan 2001 13:14:33 -0800 (PST) Message-ID: <3A675CB9.53261A6E@isi.edu> Date: Thu, 18 Jan 2001 13:14:33 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Jamil Taylor Cc: freebsd-stable@FreeBSD.ORG Subject: SMP & APM (was Re: SMP & signal 11) References: <3A65DC2A.8A15BEE1@isi.edu> <3A66446F.51A10752@isi.edu> <3A664A43.F54854C@pobox.com> <3A664B6E.5291BD15@isi.edu> <3A664DAA.35E2635C@pobox.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms6CBBF722917A79E97C9EB118" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms6CBBF722917A79E97C9EB118 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Having both the SMP options options SMP options APIC_IO and APM device apm0 at nexus? # Advanced Power Management enabled in a kernel config file causes spurious signal 11's under FreeBSD-4.2 when more than one CPU is present in the system. Is this a known conflict? I could not find this mentioned in related man pages or LINT. (Thanks to Jamil Taylor for helping me track this down.) Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms6CBBF722917A79E97C9EB118 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDExODIxMTQzM1owIwYJKoZIhvcNAQkEMRYE FKWsX96y7L1gEH75NHl3Ohcj/W1JMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAcxj9QIoKFYGN8J77OVeWRGN15desR9BKkrZKYykGEzPV9MjJpBnR eD5zfZh6Svcbu9HJJhiz8W8/J6eJ+F0Iehfz3m8r2I+/7QDnpEGAU4xx+rE5JguwK9ECP6UA 4iWcAFAgEPl+qeUOIv7vb0oHuiG0WiJ2RyZQ+NygXiBg0Xs= --------------ms6CBBF722917A79E97C9EB118-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 13:26:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (unknown [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 0BF9737B699 for ; Thu, 18 Jan 2001 13:26:29 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0ILf2Q01268; Thu, 18 Jan 2001 13:41:06 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101182141.f0ILf2Q01268@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Lars Eggert Cc: Jamil Taylor , freebsd-stable@FreeBSD.ORG Subject: Re: SMP & APM (was Re: SMP & signal 11) In-reply-to: Your message of "Thu, 18 Jan 2001 13:14:33 PST." <3A675CB9.53261A6E@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jan 2001 13:41:02 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Having both the SMP options > > options SMP > options APIC_IO > > and APM > > device apm0 at nexus? # Advanced Power Management > > enabled in a kernel config file causes spurious signal 11's under > FreeBSD-4.2 when more than one CPU is present in the system. > > Is this a known conflict? I could not find this mentioned in related man > pages or LINT. (Thanks to Jamil Taylor for helping me track this down.) It's not supported, no. Having said that, it's theoretically *meant* to work, but I suspect that there are unconsidered issues which mean that APM and SMP just aren't going to mix. -- ... 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 Thu Jan 18 13:29:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 2073737B400; Thu, 18 Jan 2001 13:28:52 -0800 (PST) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id NAA23566; Thu, 18 Jan 2001 13:28:50 -0800 (PST) Message-ID: <3A676012.F919953@isi.edu> Date: Thu, 18 Jan 2001 13:28:50 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: Mike Smith Cc: Jamil Taylor , freebsd-stable@FreeBSD.ORG Subject: Re: SMP & APM (was Re: SMP & signal 11) References: <200101182141.f0ILf2Q01268@mass.osd.bsdi.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msB9842313746E64DE4FB25711" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------msB9842313746E64DE4FB25711 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mike Smith wrote: > > > Having both the SMP options > > > > options SMP > > options APIC_IO > > > > and APM > > > > device apm0 at nexus? # Advanced Power Management > > > > enabled in a kernel config file causes spurious signal 11's under > > FreeBSD-4.2 when more than one CPU is present in the system. > > > > Is this a known conflict? I could not find this mentioned in related man > > pages or LINT. (Thanks to Jamil Taylor for helping me track this down.) > > It's not supported, no. Having said that, it's theoretically *meant* to > work, but I suspect that there are unconsidered issues which mean that > APM and SMP just aren't going to mix. Could this be documented somewhere? Maybe the next person to encounter this doesn't have to spend a day tracking it down themselves... :-) By the way, it works fine as long as there's only one CPU enabled. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------msB9842313746E64DE4FB25711 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDExODIxMjg1MFowIwYJKoZIhvcNAQkEMRYE FAZ50TDbYzxG0KZR8tu0lSvfYkDEMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAHhzodU6NxvsDZZ85PFLC3jpBDOi+JYOwyhX6+kLXEEcuUlcwl539 QgKZLy97LzS1VYpYzmLw2d25Ljyol6e2YSFEY1pp1WSiAvWQHaVgcoeam1QMEmYrdhfYbJY8 Zk21eMENfykDl57HGiesI+Asm3GnUpy6/MHhq0USFE6v0/I= --------------msB9842313746E64DE4FB25711-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 13:48:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from n4cnw.dyndns.org (user-24-214-101-2.knology.net [24.214.101.2]) by hub.freebsd.org (Postfix) with ESMTP id 08E2637B400; Thu, 18 Jan 2001 13:48:36 -0800 (PST) Received: (from n4cnw@localhost) by n4cnw.dyndns.org (8.11.1/8.11.1) id f0ILmZm05084; Thu, 18 Jan 2001 15:48:35 -0600 (CST) (envelope-from n4cnw) Date: Thu, 18 Jan 2001 15:48:34 -0600 From: Mike Murphree To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Athlon and 4.2 Release Message-ID: <20010118154834.A5024@n4cnw.dyndns.org> References: <86wvbsrjgy.fsf@lorne.arm.org> <200101181948.f0IJmXQ00714@mass.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: <200101181948.f0IJmXQ00714@mass.osd.bsdi.com>; from msmith@FreeBSD.ORG on Thu, Jan 18, 2001 at 11:48:33AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 18, 2001 at 11:48:33AM -0800, Mike Smith wrote: > > > I strongly suspect its an IRQ conflict. Every problem of this sort > > > that I've seen with the A7V has been an IRQ conflict, including the > > > problem I had with my own. Specificly I had to hard set the IRQ on my > > > NIC through the PCI management section of the bios. > ... > > It certainly is an IRQ conflict between the 3C905B NIC and the promise > > controller. I could install and reboot just fine with the NIC > > removed. > > Er, folks, no. You can share IRQs just fine with PCI. You don't have > "IRQ conflicts" just because two devices are driving the same interrupt. > > There are plenty of other possibilites for trouble, but having the same > IRQ is not in and of itself going to do this. This is the same VIA Southbridge chip as was used in the Socket 7 motherboards. On those motherboards, I have needed to change BIOS settings and shuffle cards between PCI slots to prevent shared interrupts on a Symbios 53C875 card and on the first IDE controller for proper operation in both FreeBSD and Win NT 4. Other PCI cards and devices seem to do okay sharing interrupts. I never resolved whether this was a chipset problem or card problem, but can vouch for its existence in some circumstances. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 13:52:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 6F93437B400; Thu, 18 Jan 2001 13:52:41 -0800 (PST) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.1/8.11.1) with ESMTP id f0ILqe149522; Thu, 18 Jan 2001 16:52:40 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.0.20010118164411.0217d230@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Thu, 18 Jan 2001 16:46:11 -0500 To: Mike Murphree , Mike Smith From: Mike Tancsa Subject: Re: Athlon and 4.2 Release Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <20010118154834.A5024@n4cnw.dyndns.org> References: <200101181948.f0IJmXQ00714@mass.osd.bsdi.com> <86wvbsrjgy.fsf@lorne.arm.org> <200101181948.f0IJmXQ00714@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:48 PM 1/18/01 -0600, Mike Murphree wrote: >This is the same VIA Southbridge chip as was used in the Socket 7 >motherboards. On those motherboards, I have needed to change BIOS >settings and shuffle cards between PCI slots to prevent shared >interrupts on a Symbios 53C875 card and on the first IDE controller >for proper operation in both FreeBSD and Win NT 4. Other PCI cards >and devices seem to do okay sharing interrupts. I never resolved >whether this was a chipset problem or card problem, but can vouch >for its existence in some circumstances. Are you sure its an IRQ issue in the slot, or a DMA issue ? I had similar motherboard problems a while back and I had to rearrange cards as well. But I think it was more of a DMA issue, as thats what the particular card complained about at the time. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 14:23:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 38ED737B401; Thu, 18 Jan 2001 14:23:07 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f0IMN6s08371; Thu, 18 Jan 2001 14:23:06 -0800 Date: Thu, 18 Jan 2001 14:23:06 -0800 From: Brooks Davis To: Mike Smith Cc: Lars Eggert , Jamil Taylor , freebsd-stable@FreeBSD.ORG Subject: Re: SMP & APM (was Re: SMP & signal 11) Message-ID: <20010118142306.B7247@Odin.AC.HMC.Edu> References: <3A675CB9.53261A6E@isi.edu> <200101182141.f0ILf2Q01268@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200101182141.f0ILf2Q01268@mass.osd.bsdi.com>; from msmith@FreeBSD.ORG on Thu, Jan 18, 2001 at 01:41:02PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 18, 2001 at 01:41:02PM -0800, Mike Smith wrote: > It's not supported, no. Having said that, it's theoretically *meant* to > work, but I suspect that there are unconsidered issues which mean that > APM and SMP just aren't going to mix. I could swear I saw posts a year or so ago that SMP and APM won't ever get along due to BIOS code that isn't SMP safe. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 14:30:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from darkstar.bsdguru.com (unknown [165.24.155.244]) by hub.freebsd.org (Postfix) with ESMTP id 1BEC137B401 for ; Thu, 18 Jan 2001 14:29:52 -0800 (PST) Received: from venus.n2.net (venus [165.24.156.101]) by darkstar.bsdguru.com (Postfix) with ESMTP id C5C8D1DDC for ; Thu, 18 Jan 2001 14:29:46 -0800 (PST) Received: by venus.n2.net (Postfix, from userid 1002) id AB84E3CC7; Thu, 18 Jan 2001 14:29:45 -0800 (PST) Date: Thu, 18 Jan 2001 14:29:44 -0800 From: Ben Lovett To: stable@freebsd.org Subject: Pagefaults occuring randomly Message-ID: <20010118142944.A580@bsdguru.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Organization: San Diego BSD Users Group [http://www.sdbug.org] X-Disclaimer: All messages are the opinion of my employer.. They just don't know it yet. X-Operating-System: FreeBSD venus 4.2-STABLE X-Moon: The Moon is Waning Crescent (27% of Full) X-GPG-Key: http://www.oneinsane.net/~blovett/blovett.pgp X-GPG-Fingerprint: C75F A722 1518 03B8 26C3 77A1 7C76 8AFA EBAB 2004 X-Uptime: 2:22PM up 5 mins, 4 users, load averages: 1.33, 0.42, 0.15 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello, Recently, I have been having random page faults, and the application that caused the fault is always random, or none at all, just idle. These can occur after 2 days uptime, to 5 hours.. This is on a Toshiba Satellite 2505CDS running 4.2-STABLE as of Sunday, January 14, 2001. They also occured on this same system running 4.2-STABLE as of about a month and a half ago. I don't remember the exact date I cvsup'd. Attached is a output of the most recent dmesg log with the reason it page faulted. I hope this can help, and if there is *anything* somebody would like me to show them, within reason of course, I'd be more than happy to oblige. Thanks for your time! -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Ben Lovett printf("Hello world!); don4r return 0; don4r@bsdguru.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Speak softly and carry a cellular phone. --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg-log Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Mon Jan 15 18:43:35 PST 2001 root@luna:/usr/obj/usr/src/sys/VENUS Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (quarter-micron) (233.29-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x581 Stepping = 1 Features=0x8001bf real memory = 33619968 (32832K bytes) avail memory = 28626944 (27956K bytes) Preloaded elf kernel "kernel" at 0xc0425000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 4.0 pci0: at 11.0 irq 11 chip1: port 0xffe0-0xffff irq 11 at device 17.0 on pci0 isa0: on motherboard fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: parallel port not found. pcm0: at port 0x530-0x537,0x370-0x371 irq 5 drq 1 flags 0xc100 on isa0 IPsec: Initialized Security Association Processing. IP Filter: v3.4.8 initialized. Default = pass all, Logging = enabled pccard: card inserted, slot 0 pccard: card inserted, slot 1 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 2067MB [4200/16/63] at ata0-master BIOSPIO acd0: CDROM at ata1-master using BIOSPIO Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted ed0 at port 0x320-0x33f irq 3 slot 0 on pccard0 ed0: address 00:e0:98:78:fc:6d, type Linksys (16 bit) sio4 at port 0x2f8-0x2ff irq 9 slot 1 on pccard1 sio4: type 16550A acd0: START_STOP - ILLEGAL REQUEST asc=24 ascq=00 error=04 ed0: detached stray irq 3 pccard: card disabled, slot 0 sio4: unloaded sio4: detached pccard: card disabled, slot 1 resumed from suspended mode (slept 00:37:31) ata0: resetting devices .. done ata1: resetting devices .. done pccard: card inserted, slot 0 pccard: card inserted, slot 1 sio4 at port 0x2f8-0x2ff irq 9 slot 1 on pccard1 sio4: type 16550A ed0 at port 0x320-0x33f irq 3 slot 0 on pccard0 ed0: address 00:e0:98:78:fc:6d, type Linksys (16 bit) ed0: detached stray irq 3 pccard: card disabled, slot 0 sio4: unloaded sio4: detached pccard: card disabled, slot 1 resumed from suspended mode (slept 02:07:02) ata0: resetting devices .. done ata1: resetting devices .. done pccard: card inserted, slot 0 pccard: card inserted, slot 1 sio4 at port 0x2f8-0x2ff irq 9 slot 1 on pccard1 sio4: type 16550A ed0 at port 0x320-0x33f irq 3 slot 0 on pccard0 ed0: address 00:e0:98:78:fc:6d, type Linksys (16 bit) ed0: detached stray irq 3 pccard: card disabled, slot 0 sio4: unloaded sio4: detached pccard: card disabled, slot 1 resumed from suspended mode (slept 01:35:49) ata0: resetting devices .. done ata1: resetting devices .. done pccard: card inserted, slot 0 pccard: card inserted, slot 1 sio4 at port 0x2f8-0x2ff irq 9 slot 1 on pccard1 sio4: type 16550A ed0 at port 0x320-0x33f irq 3 slot 0 on pccard0 ed0: address 00:e0:98:78:fc:6d, type Linksys (16 bit) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x6f792080 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01e221e stack pointer = 0x10:0xc033fbcc frame pointer = 0x10:0xc033fc1c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = trap number = 12 panic: page fault syncing disks... 22 22 20 14 5 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up on 1 buffers Uptime: 2h35m11s Automatic reboot in 15 seconds - press a key on the console to abort --NzB8fVQJ5HfG6fxh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 14:32:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mass.osd.bsdi.com (unknown [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 050C337B401 for ; Thu, 18 Jan 2001 14:32:16 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0IMkvQ01626; Thu, 18 Jan 2001 14:46:57 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101182246.f0IMkvQ01626@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brooks Davis Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SMP & APM (was Re: SMP & signal 11) In-reply-to: Your message of "Thu, 18 Jan 2001 14:23:06 PST." <20010118142306.B7247@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Jan 2001 14:46:57 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Jan 18, 2001 at 01:41:02PM -0800, Mike Smith wrote: > > It's not supported, no. Having said that, it's theoretically *meant* to > > work, but I suspect that there are unconsidered issues which mean that > > APM and SMP just aren't going to mix. > > I could swear I saw posts a year or so ago that SMP and APM won't ever > get along due to BIOS code that isn't SMP safe. The issue is a bit more complicated than that, but basically there's a lot of APM stuff that you can't safely do in MP mode, yes. I recall a commit which enabled a limited, assumed-OK subset of APM for SMP systems, but I don't remember whether it was in 4.x or 5.x. -- ... 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 Thu Jan 18 14:47:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 3006737B401 for ; Thu, 18 Jan 2001 14:47:14 -0800 (PST) Received: from mira1.cisco.com (mira1.cisco.com [171.71.208.193]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA06801; Thu, 18 Jan 2001 14:47:27 -0800 (PST) Received: from cisco.com (ptlm1-dhcp-254.cisco.com [171.71.210.254]) by mira1.cisco.com (Mirapoint) with ESMTP id AAC05264; Thu, 18 Jan 2001 14:47:13 -0800 (PST) Message-ID: <3A6772B4.4E9FBE74@cisco.com> Date: Thu, 18 Jan 2001 22:48:20 +0000 From: W Gerald Hicks Organization: Cisco Systems X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Thomas T. Veldhouse" Cc: Nader Turki , freebsd-stable@FreeBSD.ORG Subject: Re: ports References: <024201c08185$44c5efb0$3028680a@tgt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This syndrome is often caused when one uses CVSup to update their ports tree a long time after installing from a release. CVSup will not normally delete any file it didn't create. Sometimes this will cause a stale patch file to be left in a port. Cheers, Jerry Hicks gehicks@cisco.com "Thomas T. Veldhouse" wrote: > > I hate that when that happens. It has happened with a lot of ports lately > (i.e. unixODBC). I usually figure the port was upgraded but the patches > weren't removed - so I remove them. It usually works :( > > Tom Veldhouse > veldy@veldy.net > > ----- Original Message ----- > From: "Nader Turki" > To: > Sent: Thursday, January 18, 2001 12:16 PM > Subject: ports > > > Hi guys, > > > > I updated my ports, and wheni try installing pine i get an error. > > > > ===> Extracting for pine-4.31 > > >>Checksum OK for pine4.31.tar.gz. > > ===> pine-4.31 depends on shared library: c-client4.8 - not found > > ===> Verifying install for c-client4.8 in /usr/ports/mail/cclient > > ===> Extracting for cclient-4.8 > > >>Checksum OK for imap-2000a.tar.Z. > > ===> Patching for cclient-4.8 > > ===> Applying FreeBSD patches for cclient-4.8 > > 1 out of 1 hunks failed--saving rejects to src/osdep/unix/mx.c.rej > > >>Patch patch-ad failed to apply cleanly. > > >>Patch(es) patch-aa patch-ab patch-ac applied cleanly. > > *** Error code 1 > > > > Stop in /usr/ports/mail/cclient. > > *** Error code 1 > > > > Stop in /usr/ports/mail/cclient. > > *** Error code 1 > > > > Stop in /usr/ports/mail/cclient. > > *** Error code 1 > > > > Stop in /usr/ports/mail/cclient. > > *** Error code 1 > > > > Stop in /usr/ports/mail/cclient. > > *** Error code 1 > > > > Stop in /usr/ports/mail/cclient. > > *** Error code 1 > > > > Stop in /usr/ports/mail/pine4. > > *** Error code 1 > > > > Stop in /usr/ports/mail/pine4. > > *** Error code 1 > > > > Stop in /usr/ports/mail/pine4. > > *** Error code 1 > > > > Stop in /usr/ports/mail/pine4. > > *** Error code 1 > > > > Stop in /usr/ports/mail/pine4. > > *** Error code 1 > > > > Stop in /usr/ports/mail/pine4. > > > > Hope someone can help me with this problem. > > > > Thanks, > > > > Nader > > _________________________________________________________________ > > Get your FREE download of MSN Explorer at http://explorer.msn.com > > > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 14:49:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sydney.worldwide.lemis.com (unknown [129.94.172.186]) by hub.freebsd.org (Postfix) with ESMTP id 1AB9D37B699 for ; Thu, 18 Jan 2001 14:49:01 -0800 (PST) Received: (from grog@localhost) by sydney.worldwide.lemis.com (8.11.1/8.9.3) id f0HDWMY11579; Thu, 18 Jan 2001 00:32:22 +1100 (EST) (envelope-from grog) Date: Thu, 18 Jan 2001 00:32:22 +1100 From: Greg Lehey To: Jamil Taylor Cc: Lars Eggert , freebsd-stable@freebsd.org Subject: IDE panics on Dell Precision 420 (was: SMP & signal 11) Message-ID: <20010118003222.C10950@sydney.worldwide.lemis.com> References: <3A65DC2A.8A15BEE1@isi.edu> <3A66446F.51A10752@isi.edu> <3A664A43.F54854C@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3A664A43.F54854C@pobox.com>; from jamil_taylor@pobox.com on Wed, Jan 17, 2001 at 08:43:31PM -0500 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 17 January 2001 at 20:43:31 -0500, Jamil Taylor wrote: > Lars Eggert wrote: >> Lars Eggert wrote: >>> processes get killed (signal 11) on a new Dell Precision 620 under moderate >>> load (kernel recompilation). This only happens if I enable the second CPU >>> in the BIOS, and the kernel has SMP enabled. This machine runs FreeBSD >>> 4.2-RELEASE. >>> >>> I know signal 11 is usually an indication of bad RAM or cache memory, but >>> I've been running the Dell system test for over 24 hours, and it shows no >>> defects there. >> >> I repeated this on a second, identical machine, so it doesn't seem to be a >> hardware issue. (Or it affects the whole series.) Is anyone running 4.2 >> successfully on a SMP Dell Precision 620? >> > I am running 4.2 STABLE on an SMP Precision 420. AFAIK, the 420 and 620 > use the same chipsets (my verbose boot looks similar to yours). My > kernel is different (simpler), however. I do not know if this could be > the cause of the problem, but I have never had to disable SMP on my > machine. > > Only strange things that have happened to me is removing `device ATA' > from kernel causes an immediate panic (machine is all SCSI). If you can supply a dump for this panic, we can probably fix it relatively easily. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 14:50:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c0039.upc-c.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 0696137B401 for ; Thu, 18 Jan 2001 14:49:44 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id XAA76094 for ; Thu, 18 Jan 2001 23:49:43 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A677307.96B6B373@nisser.com> Date: Thu, 18 Jan 2001 23:49:43 +0100 From: Roelof Osinga Organization: Nisser - Nr. 1 in Veiligheid X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Mutt still a no go Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed 4.2-RELEASE on a pristine machine only to run into the mutt problem. But I spotted an announce stating that it had been solved. So I cvsup'd. But lo and behold: nl:/usr/ports/mail/mutt# script /root/Logs/ports/ports-2001.01.18a cvsup /root/cv sup/ports-supfile Script started, output file is /root/Logs/ports/ports-2001.01.18a Connected to cvsup.uk.FreeBSD.org Updating collection ports-all/cvs Edit ports/japanese/rskkserv/Makefile Edit ports/japanese/rskkserv/distinfo Checkout ports/japanese/rskkserv/files/patch-Makefile Checkout ports/japanese/rskkserv/files/patch-rskkserv.conf Edit ports/japanese/rskkserv/pkg-plist Checkout ports/mail/mutt/files/extra-patch-doc-ref Checkout ports/mail/mutt/files/patch-01 Checkout ports/mail/mutt/files/patch-02 Checkout ports/mail/mutt/files/patch-03 Checkout ports/mail/mutt/files/patch-04 Checkout ports/mail/mutt/files/patch-05 Checkout ports/mail/mutt/files/patch-08 Checkout ports/mail/mutt/files/patch-Makefile.in Finished successfully Script done, output file is /root/Logs/ports/ports-2001.01.18a nl:/usr/ports/mail/mutt# make -DWITH_SSL build Error: your port uses an old layout. Please update it to match this bsd.port.mk. *** Error code 1 Stop in /usr/ports/mail/mutt. *** Error code 1 Stop in /usr/ports/mail/mutt. *** Error code 1 Stop in /usr/ports/mail/mutt. *** Error code 1 Stop in /usr/ports/mail/mutt. nl:/usr/ports/mail/mutt# ls -l total 34 drwxr-xr-x 4 root wheel 512 Jan 18 22:31 ./ drwxr-xr-x 168 root wheel 3584 Jan 18 22:31 ../ -rw-r--r-- 1 root wheel 3820 Jan 18 22:31 Makefile -rw-r--r-- 1 root wheel 1040 Nov 20 11:13 README.html -rw-r--r-- 1 root wheel 208 Oct 31 11:51 distinfo drwxr-xr-x 2 root wheel 512 Jan 18 23:32 files/ drwxr-xr-x 2 root wheel 512 Jan 18 23:30 patches/ -rw-r--r-- 1 root wheel 65 Jul 30 10:56 pkg-comment -rw-r--r-- 1 root wheel 531 Nov 22 1999 pkg-descr -rw-r--r-- 1 root wheel 6525 Jan 18 22:31 pkg-plist -rw-r--r-- 1 root wheel 10920 Jul 11 2000 pkg-plist.htmlfiles nl:/usr/ports/mail/mutt# ls -l files/ total 14 drwxr-xr-x 2 root wheel 512 Jan 18 23:32 ./ drwxr-xr-x 4 root wheel 512 Jan 18 22:31 ../ -rw-r--r-- 1 root wheel 500 Oct 1 1998 extra-patch-doc-ref -rw-r--r-- 1 root wheel 551 May 13 2000 patch-01 -rw-r--r-- 1 root wheel 2273 Jul 11 2000 patch-02 -rw-r--r-- 1 root wheel 290 May 13 2000 patch-03 -rw-r--r-- 1 root wheel 565 Feb 29 2000 patch-04 -rw-r--r-- 1 root wheel 2318 May 13 2000 patch-05 -rw-r--r-- 1 root wheel 289 May 13 2000 patch-08 -rw-r--r-- 1 root wheel 478 May 13 2000 patch-Makefile.in nl:/usr/ports/mail/mutt# ls -l patches/ total 2 drwxr-xr-x 2 root wheel 512 Jan 18 23:30 ./ drwxr-xr-x 4 root wheel 512 Jan 18 22:31 ../ The latter because I just read a message stating that rm'ing the patches often did the trick. So I tried it, then cvsup'd again. Then tried to make, ehm, out? again. With pitifully results. (Hm. would've though pitifying to be an existing word. Alas). So... How Now? Roelof -- Home is where the (@) http://eboa.com/ is. Nisser home -- http://www.Nisser.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 15:29:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id DF42637B401 for ; Thu, 18 Jan 2001 15:29:39 -0800 (PST) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.1/8.11.1) with ESMTP id f0INTGF67162; Fri, 19 Jan 2001 10:29:22 +1100 (EST) (envelope-from marka@nominum.com) Message-Id: <200101182329.f0INTGF67162@drugs.dv.isc.org> To: Mike Tancsa Cc: Gregory Bond , Christopher Schulte , stable@freebsd.org From: Mark.Andrews@nominum.com Subject: Re: Weird sporadic DNS resolution problems In-reply-to: Your message of "Thu, 18 Jan 2001 07:47:07 CDT." <4.2.2.20010118074255.01fc96e8@marble.sentex.net> Date: Fri, 19 Jan 2001 10:29:16 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a *human* problem not a software problem. Garbage In, Garbage Out. The best solution is check the DNS servers of all the Fortune 500/1000 companies and then call the Wall Stree Journal (adjust for your locale) and give them a list of the companies that have misconfigured DNS servers. A bit of publicity at this level might just attract the attention of other CEO's to ensure that their servers are checked. Mark > At 06:17 PM 1/18/2001 +1100, Gregory Bond wrote: > > > For what it's worth, my take: > > > >This matches some of the things we've noticed here, but in our case sendmail > >was on a Solaris box using the FreeBSD box as a caching DNS server.... but > >it's slippery enough that I'm not confident what's going on. > > Actually, this sounds very familiar, especially with the BIND > revs. Looking through its CHANGES entry, the only thing I could find that > would vaguely refer to such a change is > 941. [bug] lame server detection wasn't checking for SOA record > . > > > I wonder if using BIND 9.x fixes this "bug" > > ---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 -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 15:51:26 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 4195237B402 for ; Thu, 18 Jan 2001 15:51:05 -0800 (PST) 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 KAA82314; Fri, 19 Jan 2001 10:51:01 +1100 (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 KAA17112; Fri, 19 Jan 2001 10:50:59 +1100 (EST) Message-Id: <200101182350.KAA17112@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Mark.Andrews@nominum.com Cc: Mike Tancsa , Christopher Schulte , stable@freebsd.org Subject: Re: Weird sporadic DNS resolution problems In-reply-to: Your message of Fri, 19 Jan 2001 10:29:16 +1100. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Jan 2001 10:50:59 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a *human* problem not a software problem. I don't think so. I've investigated cases where the MX record is fine, the name servers are all responding with AA, but sendmail still refuses to deliver the mail. I suspect some sort of negative caching but I can't work out where. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 16: 7: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 12E9E37B402 for ; Thu, 18 Jan 2001 16:06:32 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0J064Y87542; Thu, 18 Jan 2001 16:06:04 -0800 (PST) (envelope-from dillon) Date: Thu, 18 Jan 2001 16:06:04 -0800 (PST) From: Matt Dillon Message-Id: <200101190006.f0J064Y87542@earth.backplane.com> To: Gregory Bond Cc: Mark.Andrews@nominum.com, Mike Tancsa , Christopher Schulte , stable@FreeBSD.ORG Subject: Re: Weird sporadic DNS resolution problems References: <200101182350.KAA17112@lightning.itga.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> This is a *human* problem not a software problem. : :I don't think so. I've investigated cases where the MX record is fine, the :name servers are all responding with AA, but sendmail still refuses to deliver :the mail. I suspect some sort of negative caching but I can't work out where. This is the only caching sendmail does: # persistent host status directory #O HostStatusDirectory=.hoststat Sendmail also stores stores the last error in the spool file, and you can give it the MinQueueAge option: # minimum time in queue before retry #O MinQueueAge=30m To cause it to skip a failed queue file for X minutes before trying again. This prevents a single queue file from stalling all of the sendmail's running the queue. That's it. Sendmail doesn't cache anything else between connection attempts. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 16:17:40 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 189AB37B698 for ; Thu, 18 Jan 2001 16:17:22 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0J0HKc39461; Thu, 18 Jan 2001 19:17:20 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0J0HEd39453; Thu, 18 Jan 2001 19:17:14 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010118190909.0387fa10@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 18 Jan 2001 19:17:13 -0500 To: Mark.Andrews@nominum.com From: Mike Tancsa Subject: Re: Weird sporadic DNS resolution problems Cc: Gregory Bond , Christopher Schulte , stable@freebsd.org In-Reply-To: <200101182329.f0INTGF67162@drugs.dv.isc.org> References: 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 X-Loop: FreeBSD.ORG At 10:29 AM 1/19/2001 +1100, Mark.Andrews@nominum.com wrote: > This is a *human* problem not a software problem. Yes and no. Yes, its a human problem... My problem in that our support staff get hit with "Why cant I email my when can."... So yeah, its my problem. It would be lovely in a perfect world if people cleaned up their DNS. But some people dont know how, some people have made honest mistakes. Either way, its pretty well a pointless exercise try to explain to the end user what a LAME delegation is. Its a software problem in that it has yet to be documented or I have yet to find the documentation, explaining when this behavior has changed. Someone mentioned that it started happening between P5 and P7 of BIND which sounds plausible. But there were also sendmail changes during that period as well, and the tuneable in sendmail # name resolver options #O ResolverOptions=+AAONLY does not seem to have any affect. I cc'd the FreeBSD sendmail maintainer a while back for his opinion, but have yet to hear from him. ---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 Thu Jan 18 16:28:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id A2D4C37B401 for ; Thu, 18 Jan 2001 16:28:12 -0800 (PST) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.1/8.11.1) with ESMTP id f0J0RtF67341; Fri, 19 Jan 2001 11:27:55 +1100 (EST) (envelope-from marka@nominum.com) Message-Id: <200101190027.f0J0RtF67341@drugs.dv.isc.org> To: Gregory Bond Cc: Mark.Andrews@nominum.com, Mike Tancsa , Christopher Schulte , stable@freebsd.org From: Mark.Andrews@nominum.com Subject: Re: Weird sporadic DNS resolution problems In-reply-to: Your message of "Fri, 19 Jan 2001 10:50:59 +1100." <200101182350.KAA17112@lightning.itga.com.au> Date: Fri, 19 Jan 2001 11:27:55 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > This is a *human* problem not a software problem. > > I don't think so. I've investigated cases where the MX record is fine, the > name servers are all responding with AA, but sendmail still refuses to delive > r > the mail. I suspect some sort of negative caching but I can't work out where > . But did the A record of the MX exist? Was the zone correctly delegated? There are quite a few configuration error case transient errors. I'm not saying that a software error is impossible. I am saying that in the vast majority of cases there is a configuration error. If we get a case where a answer has been mis-classified then we fix the code. This thread has not had a example of nameserver a mis-classification. It has had humans stating that servers were good when they were bad upon inspection. Note also nameserver error can be the result of unreachable servers. Mark -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 16:39:34 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 8580F37B401 for ; Thu, 18 Jan 2001 16:39:15 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0J0dEq39521; Thu, 18 Jan 2001 19:39:14 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0J0d7d39513; Thu, 18 Jan 2001 19:39:07 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010118193210.038e34d8@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 18 Jan 2001 19:39:06 -0500 To: Mark.Andrews@nominum.com, Gregory Bond From: Mike Tancsa Subject: Re: Weird sporadic DNS resolution problems Cc: Mark.Andrews@nominum.com, Christopher Schulte , stable@freebsd.org In-Reply-To: <200101190027.f0J0RtF67341@drugs.dv.isc.org> References: 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 X-Loop: FreeBSD.ORG At 11:27 AM 1/19/2001 +1100, Mark.Andrews@nominum.com wrote: > But did the A record of the MX exist? Was the zone correctly > delegated? There are quite a few configuration error case > transient errors. In the past, you were able to send email to LAME zones. i.e. a server which did not respond authoritatively. The question I have is when did this change, and if so, is it a tuneable. The example I gave was supercom.ca. Both their servers respond LAME in the classic sense. ns4# mail -v postmasterd@supercom.ca Subject: test ignore EOT postmasterd@supercom.ca... supercom.ca: Name server timeout postmasterd@supercom.ca... Transient parse error -- message queued for future delivery postmasterd@supercom.ca... queued ns4# From a LINUX box mail -v postmaster@supercom.ca Subject: test ignore Cc: postmaster@supercom.ca... Connecting to mail.supercom.ca. via esmtp... [root@devonium2 mdtancsa]# v220 mail.supercom.ca Lotus SMTP MTA Service Ready >>> EHLO devonium2.sentex.ca i250-mail.supercom.ca 250-SIZE 0 250 EXPN >>> MAIL From: SIZE=50 250 OK >>> RCPT To: 250 OK >>> DATA 354 Enter Mail, end by a line with only '.' >>> . /250 Message received OK. postmaster@supercom.ca... Sent (Message received OK.) Closing connection to mail.supercom.ca. >>> QUIT 221 GoodBye Same rev of sendmail, asking another earlier BIND. ---Mike ---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 Thu Jan 18 16:50:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (unknown [216.152.64.152]) by hub.freebsd.org (Postfix) with ESMTP id 69B7837B69C for ; Thu, 18 Jan 2001 16:50:34 -0800 (PST) Received: from whenever ([216.152.68.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Thu, 18 Jan 2001 16:50:02 -0800 From: "David Schwartz" To: "Mike Tancsa" , Cc: Subject: RE: Weird sporadic DNS resolution problems Date: Thu, 18 Jan 2001 16:50:28 -0800 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.2911.0) In-Reply-To: <4.2.2.20010118190909.0387fa10@marble.sentex.net> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 10:29 AM 1/19/2001 +1100, Mark.Andrews@nominum.com wrote: > Yes and no. Yes, its a human problem... My problem in that our support > staff get hit with "Why cant I email my large global conglomerate who could not possibly have bad DNS > entries> when > can."... So yeah, its my problem. It > would be lovely in a perfect world if people cleaned up their DNS. But > some people dont know how, some people have made honest mistakes. Either > way, its pretty well a pointless exercise try to explain to the end user > what a LAME delegation is. The simple response is that there's no way to determine definitively where the mail is supposed to go. 'supercom.ca' is a great example. There is no way to determine where mail to that domain is supposed to go, and it's much better that it not work than simply guess. Let me put this question another way: How can you tell the difference between a 'permanently' misconfigured site and one with a transient error? Do you want mail to be sent to the wrong place because of transient errors? DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 16:55:12 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 587B337B6A0 for ; Thu, 18 Jan 2001 16:54:54 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0J0srD39566; Thu, 18 Jan 2001 19:54:53 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0J0sld39558; Thu, 18 Jan 2001 19:54:47 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010118195152.013cf218@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 18 Jan 2001 19:54:46 -0500 To: "David Schwartz" , From: Mike Tancsa Subject: RE: Weird sporadic DNS resolution problems Cc: In-Reply-To: References: <4.2.2.20010118190909.0387fa10@marble.sentex.net> 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 X-Loop: FreeBSD.ORG At 04:50 PM 1/18/2001 -0800, David Schwartz wrote: > The simple response is that there's no way to determine > definitively where >the mail is supposed to go. 'supercom.ca' is a great example. There is no >way to determine where mail to that domain is supposed to go, and it's much >better that it not work than simply guess. > > Let me put this question another way: How can you tell the difference >between a 'permanently' misconfigured site and one with a transient error? >Do you want mail to be sent to the wrong place because of transient errors? Yes, it certainly makes sense to me. One problem is explaining it to customers. What I _dont_ understand is the different behavior. If more sites were running the same rev of BIND that FreeBSD does now, then the offending site would fix the issue. i.e. why does LINUX and its sendmail and BIND work when FreeBSD and its BIND do not... Or why is LINUX 'broken' and FreeBSD being more 'correct'. ---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 Thu Jan 18 16:58:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f264.law10.hotmail.com [64.4.14.139]) by hub.freebsd.org (Postfix) with ESMTP id 97BD137B6A0; Thu, 18 Jan 2001 16:57:52 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 18 Jan 2001 16:57:52 -0800 Received: from 209.94.198.170 by lw10fd.law10.hotmail.msn.com with HTTP; Fri, 19 Jan 2001 00:57:52 GMT X-Originating-IP: [209.94.198.170] From: "Stephan Weaver" To: questions@freebsd.org, stable@freebsd.org Subject: Upgrading. Date: Thu, 18 Jan 2001 20:57:52 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 19 Jan 2001 00:57:52.0376 (UTC) FILETIME=[D9BFC780:01C081B2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Is there another way to upgrade from 3.3-R to 4.2-S ? Please CC me because i am not on the list. Thank you alot! stephan _________________________________________________________________________ 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 Thu Jan 18 17:10:58 2001 Delivered-To: freebsd-stable@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id E28A537B6A6 for ; Thu, 18 Jan 2001 17:10:37 -0800 (PST) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.1/8.11.1) with ESMTP id f0J1ADF67470; Fri, 19 Jan 2001 12:10:13 +1100 (EST) (envelope-from marka@nominum.com) Message-Id: <200101190110.f0J1ADF67470@drugs.dv.isc.org> To: Mike Tancsa Cc: Mark.Andrews@nominum.com, Gregory Bond , Christopher Schulte , stable@freebsd.org From: Mark.Andrews@nominum.com Subject: Re: Weird sporadic DNS resolution problems In-reply-to: Your message of "Thu, 18 Jan 2001 19:39:06 CDT." <4.2.2.20010118193210.038e34d8@marble.sentex.net> Date: Fri, 19 Jan 2001 12:10:12 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 11:27 AM 1/19/2001 +1100, Mark.Andrews@nominum.com wrote: > > > But did the A record of the MX exist? Was the zone correctly > > delegated? There are quite a few configuration error case > > transient errors. > > In the past, you were able to send email to LAME zones. i.e. a server which > did not respond authoritatively. The question I have is when did this > change, and if so, is it a tuneable. The example I gave was supercom.ca. > Both their servers respond LAME in the classic sense. > > ns4# mail -v postmasterd@supercom.ca > Subject: test ignore > > EOT > postmasterd@supercom.ca... supercom.ca: Name server timeout > postmasterd@supercom.ca... Transient parse error -- message queued for > future delivery > postmasterd@supercom.ca... queued > ns4# > > From a LINUX box > mail -v postmaster@supercom.ca > Subject: test ignore > > Cc: > postmaster@supercom.ca... Connecting to mail.supercom.ca. via esmtp... > > [root@devonium2 mdtancsa]# v220 mail.supercom.ca Lotus SMTP MTA Service Ready > >>> EHLO devonium2.sentex.ca > i250-mail.supercom.ca > 250-SIZE 0 > 250 EXPN > >>> MAIL From: SIZE=50 > 250 OK > >>> RCPT To: > 250 OK > >>> DATA > 354 Enter Mail, end by a line with only '.' > >>> . > /250 Message received OK. > postmaster@supercom.ca... Sent (Message received OK.) > Closing connection to mail.supercom.ca. > >>> QUIT > 221 GoodBye > > > Same rev of sendmail, asking another earlier BIND. > > ---Mike > > > ---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 > So, you would rather have BIND pass on *bad/incomplete* data. From the outside I have no way of knowing if any RRset is complete. Some of this will become moot soon BIND 9 and BIND 8.2.3 refuse to serve bad zones. Mark -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 18: 1:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scribe.pobox.com (scribe.pobox.com [208.210.124.35]) by hub.freebsd.org (Postfix) with ESMTP id 7B34637B698 for ; Thu, 18 Jan 2001 18:01:10 -0800 (PST) Received: from pobox.com (unknown [207.8.144.30]) by scribe.pobox.com (Postfix) with ESMTP id 740EE32589; Thu, 18 Jan 2001 21:01:07 -0500 (EST) Message-ID: <3A679FE2.AB9C41FC@pobox.com> Date: Thu, 18 Jan 2001 21:01:06 -0500 From: Jamil Taylor X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Lars Eggert , freebsd-stable@freebsd.org Subject: Re: IDE panics on Dell Precision 420 (was: SMP & signal 11) References: <3A65DC2A.8A15BEE1@isi.edu> <3A66446F.51A10752@isi.edu> <3A664A43.F54854C@pobox.com> <20010118003222.C10950@sydney.worldwide.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > If you can supply a dump for this panic, we can probably fix it > relatively easily. I am unable to recreate the problem this time. Last time I tried it (about 6-7 weeks ago), it panic'ed. Whatever the problem was, it is fine now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 18:36:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tomts6-srv.bellnexxia.net (smtp.bellnexxia.net [209.226.175.26]) by hub.freebsd.org (Postfix) with ESMTP id 3455E37B69F for ; Thu, 18 Jan 2001 18:35:56 -0800 (PST) Received: from otterhole.yi.org ([64.229.134.175]) by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010119023555.OBXS6201.tomts6-srv.bellnexxia.net@otterhole.yi.org> for ; Thu, 18 Jan 2001 21:35:55 -0500 Received: (from morewood@localhost) by otterhole.yi.org (8.11.1/8.9.3) id f0J2Zst00983 for stable@freebsd.org; Thu, 18 Jan 2001 21:35:54 -0500 (EST) (envelope-from morewood) From: Al Message-Id: <200101190235.f0J2Zst00983@otterhole.yi.org> Subject: FreeBSD port: nmap-5-32 under 4.2-STABLE, No route to host To: obrien@freebsd.org Date: Thu, 18 Jan 2001 20:43:48 -0500 (EST) Cc: ports@freebsd.org, stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When nmap is run against a remote network host, as root, it will consistently return the message: sendto in send_tcp_raw: sendto(3, packet, 40, 0, XXX.XX.XX.XX, 16) => No rout\ e to host But when run without root privileges, it works fine. (Therefore the routing table is fine... there is a default route. I tried adding a host specific route, it did not help). nmap will also work fine if run as root, but with a destination host on my local network. In order to get to a remote network, I must pass through my high speed Internet circuit, which uses PPPoE (ppp and Netgraph). (I do security consultant work, really!) This used to work fine, but since Dec 30 when I cvsup'd a new version of FreeBSD 4.2-stable (*default release=cvs tag=RELENG_4) it has stopped working. I ran another cvsup/build world Jan 18, 2001, and things still do not work correctly. One difference between a ktrace of root/no root is that the root version has this in the trace: 10128 nmap CALL open(0x8066f2c,0,0x1b6) 10128 nmap NAMI "/proc/net/route" 10128 nmap RET open -1 errno 2 No such file or directory But the non-root version has no /proc/net call. I do not see any reference to /proc/net/ anywhere. There does not seem to be much in the ktrace which relates to the call. 10128 nmap CALL socket(0x2,0x3,0xff) 10128 nmap RET socket 3 10128 nmap CALL setsockopt(0x3,0xffff,0x20,0xbfbfc55c,0x4) 10128 nmap RET setsockopt 0 [...] 10128 nmap CALL setsockopt(0x3,0,0x2,0xbfbfc378,0x4) 10128 nmap RET setsockopt 0 10128 nmap CALL sendto(0x3,0x8076080,0x28,0,0xbfbfc480,0x10) 10128 nmap RET sendto -1 errno 65 No route to host 10128 nmap CALL write(0x2,0xbfbfbbc8,0x56) 10128 nmap GIO fd 2 wrote 86 bytes "sendto in send_tcp_raw: sendto(3, packet, 40, 0, 206.47.73.74, 16) => No rout\ e to host" Any ideas what can be done to make this functionality work again? al To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 18:45:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from envy.geekhouse.net (envy.geekhouse.net [64.81.6.50]) by hub.freebsd.org (Postfix) with ESMTP id 73F6D37B400 for ; Thu, 18 Jan 2001 18:45:30 -0800 (PST) Received: (from jim@localhost) by envy.geekhouse.net (8.11.1/8.11.1) id f0J2jH268690; Thu, 18 Jan 2001 18:45:17 -0800 (PST) (envelope-from jim) Date: Thu, 18 Jan 2001 18:45:16 -0800 From: Jim Mock To: Roelof Osinga Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Mutt still a no go Message-ID: <20010118184516.A68603@envy.geekhouse.net> Reply-To: jim@geekhouse.net References: <3A677307.96B6B373@nisser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.13i In-Reply-To: <3A677307.96B6B373@nisser.com>; from roelof@nisser.com on Thu, Jan 18, 2001 at 11:49:43PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Jan 2001 at 23:49:43 +0100, Roelof Osinga wrote: > I installed 4.2-RELEASE on a pristine machine only to run into the > mutt problem. But I spotted an announce stating that it had been > solved. So I cvsup'd. But lo and behold: [snip..] > So... How Now? What's in your ports-supfile? - jim -- jim mock work: jim@osd.bsdi.com | jim@FreeBSD.org http://soupnazi.org/ BSDi Open Source Div | http://bsdi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 18:50:48 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 C53AC37B404 for ; Thu, 18 Jan 2001 18:50:30 -0800 (PST) Received: (from root@localhost) by cage.simianscience.com (8.11.1/8.11.1) id f0J2oTd39758; Thu, 18 Jan 2001 21:50:29 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (fcage [192.168.0.2]) by cage.simianscience.com (8.11.1/8.11.1av) with ESMTP id f0J2oNd39750; Thu, 18 Jan 2001 21:50:24 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.2.2.20010118211835.01f24f08@marble.sentex.net> X-Sender: mdtancsa@marble.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 18 Jan 2001 21:50:23 -0500 To: Mark.Andrews@nominum.com From: Mike Tancsa Subject: Re: Weird sporadic DNS resolution problems Cc: stable@freebsd.org In-Reply-To: <200101190110.f0J1ADF67470@drugs.dv.isc.org> References: 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 X-Loop: FreeBSD.ORG At 12:10 PM 1/19/2001 +1100, Mark.Andrews@nominum.com wrote: > So, you would rather have BIND pass on *bad/incomplete* data. > From the outside I have no way of knowing if any RRset is complete. > > Some of this will become moot soon BIND 9 and BIND 8.2.3 refuse > to serve bad zones. I would rather have the choice as a tuneable. Considering I still see a lot of people running 4.x branches of BIND and 8.x as root, I would be surprised if all of a sudden everyone upgraded to BIND 9.x. ---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 Thu Jan 18 18:58:34 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id 5F50537B402; Thu, 18 Jan 2001 18:58:09 -0800 (PST) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 14JRkM-000LTF-00; Fri, 19 Jan 2001 02:57:50 +0000 Date: Fri, 19 Jan 2001 02:57:50 +0000 From: Tony Finch To: Al Cc: obrien@freebsd.org, ports@freebsd.org, stable@freebsd.org Subject: Re: FreeBSD port: nmap-5-32 under 4.2-STABLE, No route to host Message-ID: <20010119025750.V30538@hand.dotat.at> References: <200101190235.f0J2Zst00983@otterhole.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200101190235.f0J2Zst00983@otterhole.yi.org> Organization: Covalent Technologies, Inc Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Al wrote: > >One difference between a ktrace of root/no root is that the root >version has this in the trace: > > 10128 nmap CALL open(0x8066f2c,0,0x1b6) > 10128 nmap NAMI "/proc/net/route" > 10128 nmap RET open -1 errno 2 No such file or directory > >But the non-root version has no /proc/net call. I do not see any >reference to /proc/net/ anywhere. /proc/net/route is a linuxism so I guess the linuxulator is causing trouble. Is your PATH different for root and non-root? What does `which nmap` say for each user? Tony. -- f.a.n.finch fanf@covalent.net dot@dotat.at "Then they attacked a town. A small town, I'll admit. But nevertheless a town of people. People who died." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 19: 2:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kline-station.ckdhr.com (kline-station.ckdhr.com [209.192.160.22]) by hub.freebsd.org (Postfix) with SMTP id 6633D37B402 for ; Thu, 18 Jan 2001 19:02:35 -0800 (PST) Received: (qmail 9977 invoked by uid 139); 19 Jan 2001 03:02:23 -0000 To: freebsd-stable@FreeBSD.ORG Subject: Re: ports References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> X-Face: I8Alb*-ZdjN\/8k_QR,^l^m6GQB'S-B:}DVP].1HOw#tx:TX$k;Wl;4zqjWR|-jheM#? &beRf(!|0b0m=M~=%.Am>"QEY.(#Ys.%"s?z,hmwp&y0%p>9+T X-Attribution: ckd Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Christopher K Davis Date: 18 Jan 2001 22:02:23 -0500 In-Reply-To: W Gerald Hicks's message of "Thu, 18 Jan 2001 22:48:20 +0000" Message-ID: Lines: 14 X-Mailer: Gnus v5.6.44/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG W Gerald Hicks writes: > This syndrome is often caused when one uses CVSup to update their ports > tree a long time after installing from a release. CVSup will not > normally delete any file it didn't create. Sometimes this will cause a > stale patch file to be left in a port. Would a reasonable test/fix for this be deleting the entire port directory in question and re-cvsupping? (This should make cvsup recreate everything and update its file lists, right?) -- Christopher Davis * * Put location information in your DNS! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 19:46:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pinnacle.schulte.org (pinnacle.schulte.org [209.134.156.220]) by hub.freebsd.org (Postfix) with ESMTP id 36B2D37B400 for ; Thu, 18 Jan 2001 19:46:38 -0800 (PST) Received: (from schulte@localhost) by pinnacle.schulte.org (8.11.1/8.11.1) id f0J3jUI63243; Thu, 18 Jan 2001 21:45:30 -0600 (CST) (envelope-from schulte) Date: Thu, 18 Jan 2001 21:45:30 -0600 From: Christopher Schulte To: Christopher K Davis Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ports Message-ID: <20010118214530.A63218@schulte.org> References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.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 ckd@ckdhr.com on Thu, Jan 18, 2001 at 10:02:23PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is what I've done when cvsup didn't properly update an older ports tree.... mv ports ports.old ; cvsup ports-supfile Causing, as you guessed, cvsup to pull down a freshly current ports tree. My only concern would be if I wanted to come back at a later date and modify a port which was installed from ports.old.... would the pkg_* suite still be able to recognize and deal with this? Are there other dependency issues which one should be aware? On Thu, Jan 18, 2001 at 10:02:23PM -0500, Christopher K Davis wrote: > Would a reasonable test/fix for this be deleting the entire port directory > in question and re-cvsupping? (This should make cvsup recreate everything > and update its file lists, right?) > > -- > Christopher Davis * * > Put location information in your DNS! -- christopher matthew schulte geek boy gone bad christopher@schulte.org http://www.schulte.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 19:48:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 764A337B400 for ; Thu, 18 Jan 2001 19:48:13 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 32A33177E44; Thu, 18 Jan 2001 21:48:16 -0600 (CST) Message-ID: <020d01c081ca$a4e19d00$931576d8@inethouston.net> From: "David W. Chapman Jr." To: , "Christopher K Davis" References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> Subject: Re: ports Date: Thu, 18 Jan 2001 21:48:11 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yes, that has to be done sometimes and should fix the problem. ----- Original Message ----- From: "Christopher K Davis" To: Sent: Thursday, January 18, 2001 9:02 PM Subject: Re: ports > W Gerald Hicks writes: > > > This syndrome is often caused when one uses CVSup to update their ports > > tree a long time after installing from a release. CVSup will not > > normally delete any file it didn't create. Sometimes this will cause a > > stale patch file to be left in a port. > > Would a reasonable test/fix for this be deleting the entire port directory > in question and re-cvsupping? (This should make cvsup recreate everything > and update its file lists, right?) > > -- > Christopher Davis * * > Put location information in your DNS! > > > 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 Thu Jan 18 19:50:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from tomts8-srv.bellnexxia.net (tomts8.bellnexxia.net [209.226.175.52]) by hub.freebsd.org (Postfix) with ESMTP id 6C80937B400; Thu, 18 Jan 2001 19:49:51 -0800 (PST) Received: from otterhole.yi.org ([64.229.134.175]) by tomts8-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010119034950.JQLU9281.tomts8-srv.bellnexxia.net@otterhole.yi.org>; Thu, 18 Jan 2001 22:49:50 -0500 Received: (from morewood@localhost) by otterhole.yi.org (8.11.1/8.9.3) id f0J3nnR01417; Thu, 18 Jan 2001 22:49:49 -0500 (EST) (envelope-from morewood) From: Al Message-Id: <200101190349.f0J3nnR01417@otterhole.yi.org> Subject: Re: FreeBSD port: nmap-5-32 under 4.2-STABLE, No route to host -> IPFilter keep state problem In-Reply-To: <20010119025750.V30538@hand.dotat.at> from Tony Finch at "Jan 19, 2001 02:57:50 am" To: Tony Finch Date: Thu, 18 Jan 2001 22:49:49 -0500 (EST) Cc: obrien@freebsd.org, ports@freebsd.org, stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Al wrote: > > > >One difference between a ktrace of root/no root is that the root > >version has this in the trace: > > > > 10128 nmap CALL open(0x8066f2c,0,0x1b6) > > 10128 nmap NAMI "/proc/net/route" > > 10128 nmap RET open -1 errno 2 No such file or directory > > > >But the non-root version has no /proc/net call. I do not see any > >reference to /proc/net/ anywhere. > > /proc/net/route is a linuxism so I guess the linuxulator is causing > trouble. Is your PATH different for root and non-root? What does > `which nmap` say for each user? I'm betting that linux emulation is not the problem. I do not have COMPAT_LINUX in the kernel, nor do I have a kld module for linux loaded. The paths are not the problem, as after I built the kernel I build a new version of nmap, and ran it as root and not root from /usr/ports/security/nmap/work/nmap-2.53/ as ./nmap for both root and non root. Somebody else suggested it could be a firewall problem, and he is correct. I also have IPFilter installed, and I looked at a tcpdump of the problem shows that an echo request was getting out of my the box, but no echo reply. Replacing my IPFilter rules with "any any" allows nmap to work again. The IPFilter rules used to work just fine. My IPFilter rules include: pass out quick proto icmp from any to any keep state all the rules use quick, and no preceeding rules deny traffic. It looks like the keep state function on IPFilter is broken? I also changed the IPfilter default to deny traffic, may that broke something? I will test some more. Thanks for the help, al > > Tony. > -- > f.a.n.finch fanf@covalent.net dot@dotat.at > "Then they attacked a town. A small town, I'll admit. > But nevertheless a town of people. People who died." > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 19:58: 8 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 5D83D37B400 for ; Thu, 18 Jan 2001 19:57:51 -0800 (PST) Received: from peppy ([65.5.55.220]) by femail3.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010119035606.TOHT6045.femail3.sdc1.sfba.home.com@peppy> for ; Thu, 18 Jan 2001 19:56:06 -0800 Message-ID: <001c01c081cc$d5bb3060$0c00a8c0@saltlk1.ut.home.com> From: "Doug Scothorne" To: Subject: Updateing from 3.4 to STABLE Date: Thu, 18 Jan 2001 21:03:52 -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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to update my 3.4 system to RELENG_4. I have successfully (I think) used cvsup to pull the source. I then try to "make buildworld" and get this error: cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 - I/us r/obj/usr/src/gnu/usr.bin/perl/miniperl -L/usr/obj/usr/src/gnu/usr.bin/pe rl/m iniperl/../libperl -static -o miniperl miniperlmain.o opmini.o /usr/obj/usr/src /gnu/usr.bin/perl/miniperl/../libperl/libperl.a -lm -lcrypt -lutil /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a(pp_hot.o): In fu nction `Perl_pp_aassign': pp_hot.o(.text+0x16a1): undefined reference to `setresuid' pp_hot.o(.text+0x16d4): undefined reference to `setresgid' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error The cvsup looked OK and didn't give any errors. If someone could point me in the right direction I'd sure appreciate it. Thanks. ---Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 20: 7:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id 0D72C37B402 for ; Thu, 18 Jan 2001 20:07:39 -0800 (PST) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id 5BD4F177E44; Thu, 18 Jan 2001 22:07:45 -0600 (CST) Message-ID: <025501c081cd$5da5ce40$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Doug Scothorne" , References: <001c01c081cc$d5bb3060$0c00a8c0@saltlk1.ut.home.com> Subject: Re: Updateing from 3.4 to STABLE Date: Thu, 18 Jan 2001 22:07:40 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I remember seeing this one and it should be in the archives, but to give you an easy one did you read /usr/src/UPDATING and build your kernel reboot then do a make world and make your kernel again? ----- Original Message ----- From: "Doug Scothorne" To: Sent: Thursday, January 18, 2001 10:03 PM Subject: Updateing from 3.4 to STABLE > > I'm trying to update my 3.4 system to RELENG_4. I have successfully (I > think) used cvsup to pull the source. I then try to "make buildworld" and > get this error: > > cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 - > I/us > bj/usr/src/gnu/usr.bin/perl/miniperl -L/usr/obj/usr/src/gnu/usr.bin/pe > rl/m > iniperl/../libperl -static -o miniperl miniperlmain.o opmini.o > /usr/obj/usr/src > /gnu/usr.bin/perl/miniperl/../libperl/libperl.a -lm -lcrypt -lutil > /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a(pp_hot.o): > In fu > nction `Perl_pp_aassign': > pp_hot.o(.text+0x16a1): undefined reference to `setresuid' > pp_hot.o(.text+0x16d4): undefined reference to `setresgid' > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > The cvsup looked OK and didn't give any errors. If someone could point me in > the right direction I'd sure appreciate it. Thanks. > > ---Doug > > > > > 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 Thu Jan 18 20:23: 1 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 3429D37B400 for ; Thu, 18 Jan 2001 20:22:45 -0800 (PST) Received: from math.missouri.edu ([24.12.197.197]) by femail3.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20010119042056.UKSG6045.femail3.sdc1.sfba.home.com@math.missouri.edu>; Thu, 18 Jan 2001 20:20:56 -0800 Message-ID: <3A67C110.F54711CA@math.missouri.edu> Date: Thu, 18 Jan 2001 22:22:40 -0600 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Schulte Cc: Christopher K Davis , freebsd-stable@FreeBSD.ORG Subject: Re: ports References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> <20010118214530.A63218@schulte.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christopher Schulte wrote: > > This is what I've done when cvsup didn't properly update an older > ports tree.... > > mv ports ports.old ; cvsup ports-supfile > > Causing, as you guessed, cvsup to pull down a freshly current ports tree. > > My only concern would be if I wanted to come back at a later date and modify > a port which was installed from ports.old.... would the pkg_* suite > still be able to recognize and deal with this? Are there other dependency > issues which one should be aware? > I think that kind of info is stored in /var/db/pkg so doing what you do would create no (additional) problems. -- 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 Thu Jan 18 20:40:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 8876F37B401 for ; Thu, 18 Jan 2001 20:39:55 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0J4h6H93647; Thu, 18 Jan 2001 20:43:06 -0800 (PST) (envelope-from kris) Date: Thu, 18 Jan 2001 20:43:06 -0800 From: Kris Kennaway To: Roelof Osinga Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Mutt still a no go Message-ID: <20010118204306.B93541@citusc17.usc.edu> References: <3A677307.96B6B373@nisser.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="SkvwRMAIpAhPCcCJ" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A677307.96B6B373@nisser.com>; from roelof@nisser.com on Thu, Jan 18, 2001 at 11:49:43PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --SkvwRMAIpAhPCcCJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 18, 2001 at 11:49:43PM +0100, Roelof Osinga wrote: > Error: your port uses an old layout. Please update it to match this > bsd.port.mk. > drwxr-xr-x 2 root wheel 512 Jan 18 23:30 patches/ This directory is old and out of date - remove it. Check that you have the line=20 *default delete in your cvsupfile. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --SkvwRMAIpAhPCcCJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6Z8XZWry0BWjoQKURArqUAKDbYwuAXpDLmqy2lYI/rTrRDHdYugCfWR8o gFjlT73todZF9fUeVpWKLCI= =K93f -----END PGP SIGNATURE----- --SkvwRMAIpAhPCcCJ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 21:47:24 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mindcrime.bit0.com (mindcrime.bit0.com [216.7.69.69]) by hub.freebsd.org (Postfix) with ESMTP id F2DC737B400 for ; Thu, 18 Jan 2001 21:47:05 -0800 (PST) Received: from localhost (mandrews@localhost) by mindcrime.bit0.com (8.11.1/8.11.1) with ESMTP id f0J5gdK01636 for ; Fri, 19 Jan 2001 00:42:39 -0500 (EST) (envelope-from mandrews@bit0.com) Date: Fri, 19 Jan 2001 00:42:39 -0500 (EST) From: Mike Andrews To: Subject: RE: Weird sporadic DNS resolution problems In-Reply-To: <4.2.2.20010118195152.013cf218@marble.sentex.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Jan 2001, Mike Tancsa wrote: > At 04:50 PM 1/18/2001 -0800, David Schwartz wrote: > > > The simple response is that there's no way to determine > > definitively where > >the mail is supposed to go. 'supercom.ca' is a great example. There is no > >way to determine where mail to that domain is supposed to go, and it's much > >better that it not work than simply guess. > > > > Let me put this question another way: How can you tell the difference > >between a 'permanently' misconfigured site and one with a transient error? > >Do you want mail to be sent to the wrong place because of transient errors? > > > Yes, it certainly makes sense to me. One problem is explaining it to > customers. What I _dont_ understand is the different behavior. If more > sites were running the same rev of BIND that FreeBSD does now, then the > offending site would fix the issue. i.e. why does LINUX and its sendmail > and BIND work when FreeBSD and its BIND do not... Or why is LINUX 'broken' > and FreeBSD being more 'correct'. You could substitute "FreeBSD 4.1" in place of "Linux" above as well. Basically you hit on the real problem for us here. We all agree that the root cause of the problem is some sites are too damn stupid to set their nameservers up correctly. It would be nice if they all went to Bind 8.2.3 or Bind 9 and were forced to fix their problem. Unfortunately, this is the real world and people are likely to stay stupid, even when you tell them that their nameserver is broken -- they just don't care. Even more unfortunately and more importantly to me, we have customers that don't understand that it's the other people that are stupid, because "it worked before you upgraded, and they didn't change anything, therefore it must be your (my) problem and not theirs." That's what Mike Tancsa and myself are up against, and that's why I started this silly thread. :) Perhaps in the past Sendmail didn't know authoritatively where to send the mail... and might have had to take a guess. Makes sense. It guessed right in every case I know of, but I can see where it could get it wrong. I think what it boils down to is that FreeBSD 4.1 used to allow us to shoot ourselves in the foot there, something in the 4.1.1 and 4.2 releases won't let us shoot ourselves in the foot, and Mike and I want to be allowed to shoot ourselves in the foot if we so choose. It does make me feel slightly more sane to know that I'm not the only one... I did just do some digging around and found something interesting. I checked some old archived email to see what the exact date this problem started for us was. I compared that to FreeBSD release notes, commit logs, and UPDATING.TXT, to try to figure out if the culprit might be Bind or Sendmail. Turns out I guessed wrong: 03-Jul-2000: Bind upgraded to 8.2.3-T5B in RELENG_4 27-Jul-2000: FreeBSD 4.1-RELEASE 27-Aug-2000: Sendmail upgraded from 8.9.3 to 8.11.0 in RELENG_4 09-Sep-2000: PROBLEM STARTS after a make world from today's RELENG_4 27-Sep-2000: FreeBSD 4.1.1-RELEASE 02-Nov-2000: Bind upgraded to 8.2.3-T6B in RELENG_4 This certainly suggests that the culprit is Sendmail, not Bind. Which of course annoys me because I've been assuming this was a Bind issue up until now... heh. But it does explain why tweaking Bind's negative caching params didn't help. Maybe it'll help someone else track things down better than I've been able to. Short term, though, I liked the suggestion about stuffing an entry in /etc/hosts to work around the broken domains' DNS problems, and that does work for me for now. So at least I have an ugly workaround.. much less ugly than restarted named every few hours though. Next, I'm going to start comparing the sendmail.cf files built from my old 8.9.3 .mc file and my current 8.11.x .mc file and see if any big differences jump out at me... Mike Andrews * mandrews@dcr.net * mandrews@bit0.com * http://www.bit0.com VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY Internet access for Frankfort, Lexington, Louisville and surrounding counties www.fark.com: If it's not news, it's Fark. (Or something like that.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 22:18:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id 8E8D337B400 for ; Thu, 18 Jan 2001 22:18:16 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14JUqj-000CEF-00 for freebsd-stable@freebsd.org; Fri, 19 Jan 2001 09:16:40 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14JUsC-0001f3-00 for freebsd-stable@freebsd.org; Fri, 19 Jan 2001 09:18:08 +0300 Date: Fri, 19 Jan 2001 09:18:08 +0300 From: Corvette To: freebsd-stable@freebsd.org Subject: Re: Mutt still a no go Message-ID: <20010119091808.B6288@poeza.iconnect.co.ke> Mail-Followup-To: Corvette , freebsd-stable@freebsd.org References: <3A677307.96B6B373@nisser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A677307.96B6B373@nisser.com>; from "Roelof Osinga" on Thu, Jan 18, 2001 at 11:49:43PM +0100 X-Operating-System: FreeBSD poeza.iconnect.co.ke 4.2-STABLE FreeBSD 4.2-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Roelof Osinga [20010119 01:51]: writing on the subject 'Mutt still a no go' Roelof> I installed 4.2-RELEASE on a pristine machine only to run into the Roelof> mutt problem. But I spotted an announce stating that it had been Roelof> solved. So I cvsup'd. But lo and behold: Roelof> Roelof> nl:/usr/ports/mail/mutt# script /root/Logs/ports/ports-2001.01.18a cvsup Roelof> /root/cv Roelof> sup/ports-supfile Roelof> Script started, output file is /root/Logs/ports/ports-2001.01.18a Roelof> Connected to cvsup.uk.FreeBSD.org Roelof> Updating collection ports-all/cvs Roelof> Edit ports/japanese/rskkserv/Makefile Roelof> Edit ports/japanese/rskkserv/distinfo Roelof> Checkout ports/japanese/rskkserv/files/patch-Makefile Roelof> Checkout ports/japanese/rskkserv/files/patch-rskkserv.conf Roelof> Edit ports/japanese/rskkserv/pkg-plist Roelof> Checkout ports/mail/mutt/files/extra-patch-doc-ref Roelof> Checkout ports/mail/mutt/files/patch-01 Roelof> Checkout ports/mail/mutt/files/patch-02 Roelof> Checkout ports/mail/mutt/files/patch-03 Roelof> Checkout ports/mail/mutt/files/patch-04 Roelof> Checkout ports/mail/mutt/files/patch-05 Roelof> Checkout ports/mail/mutt/files/patch-08 Roelof> Checkout ports/mail/mutt/files/patch-Makefile.in Roelof> Finished successfully Roelof> Roelof> Script done, output file is /root/Logs/ports/ports-2001.01.18a Roelof> nl:/usr/ports/mail/mutt# make -DWITH_SSL build Roelof> Error: your port uses an old layout. Please update it to match this Roelof> bsd.port.mk. Roelof> *** Error code 1 Roelof> Roelof> Stop in /usr/ports/mail/mutt. Roelof> *** Error code 1 Roelof> Roelof> Stop in /usr/ports/mail/mutt. Roelof> *** Error code 1 Roelof> Roelof> Stop in /usr/ports/mail/mutt. Roelof> *** Error code 1 Roelof> Roelof> Stop in /usr/ports/mail/mutt. Roelof> nl:/usr/ports/mail/mutt# ls -l Arrggrr..your problem so simple. Just change the name of the cvsup server in the ports-supfile and do cvsup -g -L 2 ports-supfile After the cvsup build mutt. Did you see mins about the tape drive in this list? I am still stuck...and praying for a miracle. -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. ASHes to ASHes, DOS to DOS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 22:23:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from siafu.iconnect.co.ke (upagraha.iconnect.co.ke [209.198.248.2]) by hub.freebsd.org (Postfix) with ESMTP id BE3D137B400 for ; Thu, 18 Jan 2001 22:22:25 -0800 (PST) Received: from [64.110.74.50] (helo=poeza.iconnect.co.ke) by siafu.iconnect.co.ke with esmtp (Exim 2.12 #1) id 14JUuk-000CjW-00; Fri, 19 Jan 2001 09:20:51 +0300 Received: from wash by poeza.iconnect.co.ke with local (Exim 3.20 #1) id 14JUwA-0001hI-00; Fri, 19 Jan 2001 09:22:14 +0300 Date: Fri, 19 Jan 2001 09:22:14 +0300 From: Corvette To: freebsd-stable@freebsd.org Cc: doug-scothorne@home.com Subject: Re: Updateing from 3.4 to STABLE Message-ID: <20010119092214.C6288@poeza.iconnect.co.ke> Mail-Followup-To: Corvette , freebsd-stable@freebsd.org, doug-scothorne@home.com References: <001c01c081cc$d5bb3060$0c00a8c0@saltlk1.ut.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001c01c081cc$d5bb3060$0c00a8c0@saltlk1.ut.home.com>; from "Doug Scothorne" on Thu, Jan 18, 2001 at 09:03:52PM -0700 X-Operating-System: FreeBSD poeza.iconnect.co.ke 4.2-STABLE FreeBSD 4.2-STABLE X-Mailer: Mutt http://www.mutt.org/ X-Location: Mombasa, KE, East Africa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Doug Scothorne [20010119 06:59]: writing on the subject 'Updateing from 3.4 to STABLE' Doug> Doug> I'm trying to update my 3.4 system to RELENG_4. I have successfully (I Doug> think) used cvsup to pull the source. I then try to "make buildworld" and Doug> get this error: Doug> Doug> cc -O -pipe -I/usr/src/gnu/usr.bin/perl/miniperl/../../../../contrib/perl5 - Doug> I/us Doug> r/obj/usr/src/gnu/usr.bin/perl/miniperl -L/usr/obj/usr/src/gnu/usr.bin/pe Doug> rl/m Doug> iniperl/../libperl -static -o miniperl miniperlmain.o opmini.o Doug> /usr/obj/usr/src Doug> /gnu/usr.bin/perl/miniperl/../libperl/libperl.a -lm -lcrypt -lutil Doug> /usr/obj/usr/src/gnu/usr.bin/perl/miniperl/../libperl/libperl.a(pp_hot.o): Doug> In fu Doug> nction `Perl_pp_aassign': Doug> pp_hot.o(.text+0x16a1): undefined reference to `setresuid' Doug> pp_hot.o(.text+0x16d4): undefined reference to `setresgid' Doug> *** Error code 1 Doug> 1 error Doug> *** Error code 2 Doug> 1 error Doug> *** Error code 2 Doug> 1 error Doug> *** Error code 2 Doug> 1 error Doug> *** Error code 2 Doug> 1 error Doug> *** Error code 2 Doug> 1 error Doug> Doug> The cvsup looked OK and didn't give any errors. If someone could point me in Doug> the right direction I'd sure appreciate it. Thanks. Doug> Doug> ---Doug Find my posting in this list 2 days ago. Print it out and follow it to the letter. Only problem I encountered after shooting my 3.5-STABLE to 4.2-STABLE is wth my T20 tape drive which I still cannot access. HTH -Wash -- Odhiambo Washington Inter-Connect Ltd., wash@iconnect.co.ke 5th Flr Furaha Plaza Tel: 254 11 222604 Nkrumah Rd., Fax: 254 11 222636 PO Box 83613 MOMBASA, KE. When passenger of foot heave in sight, tootle the horn. Trumpet him melodiously at first, but if he still obstacles your passage then tootle him with vigor. -From a brochure of a car rental firm in Tokyo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 23:10:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (oldftp.webmaster.com [209.10.218.74]) by hub.freebsd.org (Postfix) with ESMTP id 1E2A437B401 for ; Thu, 18 Jan 2001 23:10:29 -0800 (PST) Received: from whenever ([216.152.68.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Thu, 18 Jan 2001 23:10:02 -0800 From: "David Schwartz" To: "Mike Andrews" , Subject: RE: Weird sporadic DNS resolution problems Date: Thu, 18 Jan 2001 23:10:28 -0800 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.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 18 Jan 2001, Mike Tancsa wrote: > Basically you hit on the real problem for us here. We all agree that the > root cause of the problem is some sites are too damn stupid to set their > nameservers up correctly. It would be nice if they all went to Bind 8.2.3 > or Bind 9 and were forced to fix their problem. Unfortunately, this is > the real world and people are likely to stay stupid, even when you tell > them that their nameserver is broken -- they just don't care. Even more > unfortunately and more importantly to me, we have customers that don't > understand that it's the other people that are stupid, because "it worked > before you upgraded, and they didn't change anything, therefore it must be > your (my) problem and not theirs." That's what Mike Tancsa and myself are > up against, and that's why I started this silly thread. :) First, as to the technical issues, I agree with both of you. It is certainly reasonable to figure out what the current behavior is, where it changed, and how to get it back for people who want the old behavior. After all, it could even be do to a bug. Nevertheless, I have a problem with people who cave in to irrational customers. I have been there more than once, and it's really not as hard as you might think to stand your ground. The more pain misconfigured sites suffer, the more likely they are to fix their misconfiguration. In this case, I would simply state, "The other sites are misconfigured. I will gladly show you the specifics of the misconfiguration and the relevant standards that they are violating. At some point, we may be able to work out a sane way to send mail to these sites without sending mail in the wrong place in the face of real transient problems. But at the moment, we simply have to insist that sites that wish to exchange email with us and our customers follow the relevant requirements. There is simply no other way for different people's networks to cooperate with each other." DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jan 18 23:53:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id DA7E437B401 for ; Thu, 18 Jan 2001 23:53:12 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0J7u5Y99122; Thu, 18 Jan 2001 23:56:05 -0800 (PST) (envelope-from kris) Date: Thu, 18 Jan 2001 23:56:05 -0800 From: Kris Kennaway To: Corvette Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Mutt still a no go Message-ID: <20010118235605.A99085@citusc17.usc.edu> References: <3A677307.96B6B373@nisser.com> <20010119091808.B6288@poeza.iconnect.co.ke> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010119091808.B6288@poeza.iconnect.co.ke>; from wash@iconnect.co.ke on Fri, Jan 19, 2001 at 09:18:08AM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 19, 2001 at 09:18:08AM +0300, Corvette wrote: > Arrggrr..your problem so simple. Just change the name of the cvsup server= in the ports-supfile > and do cvsup -g -L 2 ports-supfile How will this help? Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6Z/MVWry0BWjoQKURAt43AJ0WK5dJyFK650DkvlqKzIshNtgS7gCeJsZK kpYHaYnm/uM2KifEOGoSp5k= =nphT -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 0:30:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id C3E7337B402; Fri, 19 Jan 2001 00:30:02 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Fri, 19 Jan 2001 00:28:12 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0J8TwR78328; Fri, 19 Jan 2001 00:29:58 -0800 (PST) (envelope-from cjc) Date: Fri, 19 Jan 2001 00:29:57 -0800 From: "Crist J. Clark" To: Kris Kennaway Cc: Corvette , freebsd-stable@FreeBSD.ORG Subject: Re: Mutt still a no go Message-ID: <20010119002957.F66998@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <3A677307.96B6B373@nisser.com> <20010119091808.B6288@poeza.iconnect.co.ke> <20010118235605.A99085@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010118235605.A99085@citusc17.usc.edu>; from kris@FreeBSD.ORG on Thu, Jan 18, 2001 at 11:56:05PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 18, 2001 at 11:56:05PM -0800, Kris Kennaway wrote: > On Fri, Jan 19, 2001 at 09:18:08AM +0300, Corvette wrote: > > > Arrggrr..your problem so simple. Just change the name of the cvsup server in the ports-supfile > > and do cvsup -g -L 2 ports-supfile > > How will this help? *sigh* OK, do any of these exist, patches/ pkg/ files/md5 And what does, $ grep '\$FreeBSD' /usr/ports/Mk/bsd.port.* $ cat /usr/share/mk/bsd.port.* Return? -- 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 Fri Jan 19 0:45:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 711AB37B402 for ; Fri, 19 Jan 2001 00:45:06 -0800 (PST) Received: from hyperion.informatik.rwth-aachen.de (hyperion.Informatik.RWTH-Aachen.DE [137.226.112.212]) by nets5.rz.rwth-aachen.de (8.10.1/8.10.1/5) with ESMTP id f0J8ivm15586; Fri, 19 Jan 2001 09:44:57 +0100 (MET) 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 JAA00927; Fri, 19 Jan 2001 09:43:52 +0100 (MET) Received: (from stolz@localhost) by agamemnon.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1-gb-2) id JAA13853; Fri, 19 Jan 2001 09:44:56 +0100 (MET) Date: Fri, 19 Jan 2001 09:44:56 +0100 From: Volker Stolz To: larse@ISI.EDU, Jamil Taylor , freebsd-stable@FreeBSD.ORG Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SMP & APM (was Re: SMP & signal 11) Message-ID: <20010119094456.A13840@agamemnon.informatik.rwth-aachen.de> References: <3A65DC2A.8A15BEE1@isi.edu> <3A66446F.51A10752@isi.edu> <3A664A43.F54854C@pobox.com> <3A664B6E.5291BD15@isi.edu> <3A664DAA.35E2635C@pobox.com> <3A675CB9.53261A6E@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A675CB9.53261A6E@isi.edu> Organization: Chair for CS II 1/2, Anomalous Programming Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In local.freebsd-stable, you wrote: > options SMP > options APIC_IO > device apm0 at nexus? # Advanced Power Management > >enabled in a kernel config file causes spurious signal 11's under >FreeBSD-4.2 when more than one CPU is present in the system. Just on a specific machine? My dual Celerons are running fine w/o *any* sig-11 for about a year tracking -STABLE. -- \usepackage[latin1]{inputenc}! 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 Fri Jan 19 1: 2:18 2001 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id BB8FE37B699 for ; Fri, 19 Jan 2001 01:01:57 -0800 (PST) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.10.0/jtpda-5.3.3) with ESMTP id f0J91uq98334 for ; Fri, 19 Jan 2001 10:01:56 +0100 (CET) Received: from rose.lpthe.jussieu.fr (root@[134.157.10.102]) by parthe.lpthe.jussieu.fr (8.11.1/jtpda-5.3.1) with ESMTP id f0J91u320121 for ; Fri, 19 Jan 2001 10:01:56 +0100 (MET) Received: (from michel@localhost) by rose.lpthe.jussieu.fr (8.11.1/8.11.1) id f0J91uT00506 for stable@FreeBSD.ORG; Fri, 19 Jan 2001 10:01:56 +0100 (CET) (envelope-from michel) Date: Fri, 19 Jan 2001 10:01:55 +0100 From: Michel Talon To: stable@FreeBSD.ORG Subject: Re: FreeBSD port: nmap-5-32 under 4.2-STABLE, No route to host -> IPFilter keep state problem Message-ID: <20010119100155.A461@lpthe.jussieu.fr> Mail-Followup-To: stable@FreeBSD.ORG References: <20010119025750.V30538@hand.dotat.at> <200101190349.f0J3nnR01417@otterhole.yi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200101190349.f0J3nnR01417@otterhole.yi.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 18, 2001 at 10:49:49PM -0500, Al wrote: > My IPFilter rules include: > pass out quick proto icmp from any to any keep state > all the rules use quick, and no preceeding rules deny traffic. > It looks like the keep state function on IPFilter is broken? > I also changed the IPfilter default to deny traffic, may that > broke something? I will test some more. I may have misundesrstood, but i thought that keep state was only for TCP and UDP packets (and of short time validity for UDP). There are examples of managing ICMP in the IPFilter doc. -- Michel Talon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 2:17:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from clove.rp.lan (unknown [212.74.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 07E1E37B400 for ; Fri, 19 Jan 2001 02:17:11 -0800 (PST) Received: (from dom@localhost) by clove.rp.lan (8.9.3/8.8.7) id KAA29716; Fri, 19 Jan 2001 10:16:50 GMT X-Authentication-Warning: clove.rp.lan: dom set sender to dom@semantico.com using -f Date: Fri, 19 Jan 2001 10:16:50 +0000 From: Dominic Mitchell To: Christopher K Davis Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ports Message-ID: <20010119101650.A27757@semantico.com> References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us In-Reply-To: X-Warning: Incoming message from The Big Giant Head! X-OS: Linux 2.2.13 i686 X-Uptime: 9:40am up 21 days, 20:59, 7 users, load average: 0.11, 0.07, 0.01 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 18, 2001 at 10:02:23PM -0500, Christopher K Davis wrote: > W Gerald Hicks writes: > > > This syndrome is often caused when one uses CVSup to update their ports > > tree a long time after installing from a release. CVSup will not > > normally delete any file it didn't create. Sometimes this will cause a > > stale patch file to be left in a port. > > Would a reasonable test/fix for this be deleting the entire port directory > in question and re-cvsupping? (This should make cvsup recreate everything > and update its file lists, right?) Even better would be to use the cvsupchk tool that comes with cvsup (in the contrib directory) to get a list of files that shouldn't be there anyway. Then you can just pass a list to "xargs rm -f". It isn't installed by default, but if you still have a copy of the cvsup tarball in /usr/ports/distfiles, it will be in there. Even the "binary" distributions. -Dom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 3:12:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.merrion.nua.net (mail.merrion.nua.net [195.7.46.14]) by hub.freebsd.org (Postfix) with ESMTP id 9B1C037B400 for ; Fri, 19 Jan 2001 03:12:36 -0800 (PST) Received: from thoth (cerberus.merrion.nua.net [195.7.46.125]) by mail.merrion.nua.net (8.10.1/8.10.1) with SMTP id f0JBAYo45358 for ; Fri, 19 Jan 2001 11:10:35 GMT From: Tony Byrne To: freebsd-stable@freebsd.org Subject: Re: ports Date: Fri, 19 Jan 2001 11:17:12 +0000 Organization: Nua Ltd. Message-ID: References: <024201c08185$44c5efb0$3028680a@tgt.com> In-Reply-To: <024201c08185$44c5efb0$3028680a@tgt.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Jan 2001 13:31:32 -0600, you wrote: >I hate that when that happens. It has happened with a lot of ports = lately >(i.e. unixODBC). I usually figure the port was upgraded but the patches >weren't removed - so I remove them. It usually works :( Ditto with the port of qt22, which I tried to install this morning. Patch rejects some of the chunks, but if I check the reject file, I can't see why the chunk was rejected. Regards, Tony. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 3:46:40 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c0039.upc-c.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 54AFF37B400 for ; Fri, 19 Jan 2001 03:46:20 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id MAA79110; Fri, 19 Jan 2001 12:46:15 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A682907.3FBC2B3A@nisser.com> Date: Fri, 19 Jan 2001 12:46:15 +0100 From: Roelof Osinga Organization: Nisser - Nr. 1 in Veiligheid X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: jim@geekhouse.net Cc: freebsd-stable@FreeBSD.ORG Subject: Mutt's tail aswitching [was Re: Mutt still a no go] References: <3A677307.96B6B373@nisser.com> <20010118184516.A68603@envy.geekhouse.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Mock wrote: > > What's in your ports-supfile? nl:~$ cat /root/cvsup/ports-supfile # RO 18.01.2001 copied from /usr/share/examples/cvsup and patched from Forseti # *default host=cvsup.uk.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-all Not enough as it turned out. Had postponed the '*default delete' option, don't know why. Thanks! Roelof -- Home is where the (@) http://eboa.com/ is. Nisser home -- http://www.Nisser.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 3:53:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c0039.upc-c.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 9ACA137B400; Fri, 19 Jan 2001 03:53:18 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id MAA79127; Fri, 19 Jan 2001 12:53:17 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A682AAD.AC933E4D@nisser.com> Date: Fri, 19 Jan 2001 12:53:17 +0100 From: Roelof Osinga Organization: Nisser - Nr. 1 in Veiligheid X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Kris Kennaway Cc: freebsd-stable@FreeBSD.ORG Subject: Mutt abarking! [was Re: Mutt still a no go] References: <3A677307.96B6B373@nisser.com> <20010118204306.B93541@citusc17.usc.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Thu, Jan 18, 2001 at 11:49:43PM +0100, Roelof Osinga wrote: > ... > > drwxr-xr-x 2 root wheel 512 Jan 18 23:30 patches/ > > This directory is old and out of date - remove it. > > Check that you have the line > > *default delete > > in your cvsupfile. Hadn't, have now, installed smoothly. Thanks! Roelof -- Home is where the (@) http://eboa.com/ is. Nisser home -- http://www.Nisser.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 6: 6:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mail.clones.com (unknown [216.70.178.182]) by hub.freebsd.org (Postfix) with ESMTP id 78AB437B400 for ; Fri, 19 Jan 2001 06:06:27 -0800 (PST) Received: from localhost (gross@localhost) by mail.clones.com (8.9.3/8.9.3) with ESMTP id GAA07401; Fri, 19 Jan 2001 06:07:07 -0800 Date: Fri, 19 Jan 2001 06:07:07 -0800 (PST) From: Glendon Gross To: David Schwartz Cc: Mike Andrews , stable@FreeBSD.ORG Subject: RE: Weird sporadic DNS resolution problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You may not agree with this, but perhaps the latest BIND is just too anal in the way it does validation checks. This is not a perfect world, and some sites are likely to remain misconfigured. Does that mean they should not be permitted to send e-mail? For example, I built and installed Bind 9.1 and had to revert or else my site would be down until I can fix the DNS tables. DNS help is hard to find these days, so I'll put up with a functional, albeit misconfigured site until I can figure out how to satisfy all of BIND version 9's requirements. Regards, Glen Gross On Thu, 18 Jan 2001, David Schwartz wrote: > > > On Thu, 18 Jan 2001, Mike Tancsa wrote: > > > Basically you hit on the real problem for us here. We all agree that the > > root cause of the problem is some sites are too damn stupid to set their > > nameservers up correctly. It would be nice if they all went to Bind 8.2.3 > > or Bind 9 and were forced to fix their problem. Unfortunately, this is > > the real world and people are likely to stay stupid, even when you tell > > them that their nameserver is broken -- they just don't care. Even more > > unfortunately and more importantly to me, we have customers that don't > > understand that it's the other people that are stupid, because "it worked > > before you upgraded, and they didn't change anything, therefore it must be > > your (my) problem and not theirs." That's what Mike Tancsa and myself are > > up against, and that's why I started this silly thread. :) > > First, as to the technical issues, I agree with both of you. It is > certainly reasonable to figure out what the current behavior is, where it > changed, and how to get it back for people who want the old behavior. After > all, it could even be do to a bug. Nevertheless, I have a problem with > people who cave in to irrational customers. > > I have been there more than once, and it's really not as hard as you might > think to stand your ground. The more pain misconfigured sites suffer, the > more likely they are to fix their misconfiguration. > > In this case, I would simply state, "The other sites are misconfigured. I > will gladly show you the specifics of the misconfiguration and the relevant > standards that they are violating. At some point, we may be able to work out > a sane way to send mail to these sites without sending mail in the wrong > place in the face of real transient problems. But at the moment, we simply > have to insist that sites that wish to exchange email with us and our > customers follow the relevant requirements. There is simply no other way for > different people's networks to cooperate with each other." > > DS > > > > 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 Fri Jan 19 6:20:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from barry.mail.mindspring.net (barry.mail.mindspring.net [207.69.200.25]) by hub.freebsd.org (Postfix) with ESMTP id DD10937B401 for ; Fri, 19 Jan 2001 06:20:09 -0800 (PST) Received: from netcom1.netcom.com (user-2iniu18.dialup.mindspring.com [165.121.120.40]) by barry.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id JAA19439; Fri, 19 Jan 2001 09:19:59 -0500 (EST) Received: by netcom1.netcom.com (Postfix, from userid 1000) id 9CA21E6AB3; Fri, 19 Jan 2001 06:19:56 -0800 (PST) From: Mike Harding To: ckd@ckdhr.com Cc: freebsd-stable@FreeBSD.ORG In-reply-to: (message from Christopher K Davis on 18 Jan 2001 22:02:23 -0500) Subject: Re: ports References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> Message-Id: <20010119141956.9CA21E6AB3@netcom1.netcom.com> Date: Fri, 19 Jan 2001 06:19:56 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The CVSup port has a utility, in the port but not installed, which compares the tree you have with that on the CVS server and tells you what files and directories you have which are 'extra'. It does require Python. I occasionally run it from the ports tree entry as follows: # cd /usr/ports/net/cvsup-bin # make # cd work/cvsup-bin-16.1/contrib/cvsupchk # ./cvsupchk -d /usr -c /usr/sup/ports-all/checkouts.cvs:. EXTRA: /usr/ports/net/aim/work EXTRA: /usr/ports/net/cvsup/cvsup-16.1 EXTRA: /usr/ports/net/cvsup-bin/work EXTRA: /usr/ports/x11-toolkits/linux-gtk/work EXTRA: /usr/ports/distfiles This is a lot better than re-checking out the tree if you have a 56K modem. There are other examples in the README. - Mike H. Content-Type: text/plain; charset=US-ASCII From: Christopher K Davis Date: 18 Jan 2001 22:02:23 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Precedence: bulk W Gerald Hicks writes: > This syndrome is often caused when one uses CVSup to update their ports > tree a long time after installing from a release. CVSup will not > normally delete any file it didn't create. Sometimes this will cause a > stale patch file to be left in a port. Would a reasonable test/fix for this be deleting the entire port directory in question and re-cvsupping? (This should make cvsup recreate everything and update its file lists, right?) -- Christopher Davis * * Put location information in your DNS! 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 Fri Jan 19 7:40:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id B466A37B404; Fri, 19 Jan 2001 07:40:16 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id RAA16392; Fri, 19 Jan 2001 17:37:55 +0200 To: Al Subject: Re: FreeBSD port: nmap-5-32 under 4.2-STABLE, No route to host Message-ID: <979918675.3a685f537a96b@webmail.harmonic.co.il> Date: Fri, 19 Jan 2001 17:37:55 +0200 (IST) From: Roman Shterenzon Cc: ports@FreeBSD.ORG, stable@FreeBSD.ORG References: <200101190235.f0J2Zst00983@otterhole.yi.org> In-Reply-To: <200101190235.f0J2Zst00983@otterhole.yi.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.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You're probably using a linux binary instead of native FreeBSD binary. Quoting Al : > > > When nmap is run against a remote network host, as root, it will > consistently return the message: > > sendto in send_tcp_raw: sendto(3, packet, 40, 0, XXX.XX.XX.XX, 16) => > No rout\ > e to host > > But when run without root privileges, it works fine. > (Therefore the routing table is fine... there is a default route. > I tried adding a host specific route, it did not help). > > nmap will also work fine if run as root, but with a destination host on > my local network. > > In order to get to a remote network, I must pass through my high speed > Internet circuit, which uses PPPoE (ppp and Netgraph). > (I do security consultant work, really!) > > This used to work fine, but since Dec 30 when I cvsup'd a new version of > FreeBSD 4.2-stable (*default release=cvs tag=RELENG_4) it has stopped > working. I ran another cvsup/build world Jan 18, 2001, and things still > do not work correctly. > > > One difference between a ktrace of root/no root is that the root > version has this in the trace: > > 10128 nmap CALL open(0x8066f2c,0,0x1b6) > 10128 nmap NAMI "/proc/net/route" > 10128 nmap RET open -1 errno 2 No such file or directory > > But the non-root version has no /proc/net call. I do not see any > reference to /proc/net/ anywhere. > > There does not seem to be much in the ktrace which relates to the call. > 10128 nmap CALL socket(0x2,0x3,0xff) > 10128 nmap RET socket 3 > 10128 nmap CALL setsockopt(0x3,0xffff,0x20,0xbfbfc55c,0x4) > 10128 nmap RET setsockopt 0 > [...] > 10128 nmap CALL setsockopt(0x3,0,0x2,0xbfbfc378,0x4) > 10128 nmap RET setsockopt 0 > 10128 nmap CALL sendto(0x3,0x8076080,0x28,0,0xbfbfc480,0x10) > 10128 nmap RET sendto -1 errno 65 No route to host > 10128 nmap CALL write(0x2,0xbfbfbbc8,0x56) > 10128 nmap GIO fd 2 wrote 86 bytes > "sendto in send_tcp_raw: sendto(3, packet, 40, 0, 206.47.73.74, > 16) => No rout\ > e to host" > > Any ideas what can be done to make this functionality work again? > > al > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 7:44:12 2001 Delivered-To: freebsd-stable@freebsd.org Received: from moon.harmonic.co.il (moon.harmonic.co.il [192.116.140.65]) by hub.freebsd.org (Postfix) with ESMTP id 48CC037B698 for ; Fri, 19 Jan 2001 07:43:54 -0800 (PST) Received: (from nobody@localhost) by moon.harmonic.co.il (8.9.3/8.9.3) id RAA16395; Fri, 19 Jan 2001 17:41:38 +0200 To: Ben Lovett Subject: Re: Pagefaults occuring randomly Message-ID: <979918898.3a68603253893@webmail.harmonic.co.il> Date: Fri, 19 Jan 2001 17:41:38 +0200 (IST) From: Roman Shterenzon Cc: stable@FreeBSD.ORG References: <20010118142944.A580@bsdguru.com> In-Reply-To: <20010118142944.A580@bsdguru.com> 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.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please read http://www.freebsd.org/handbook/kerneldebug.html and create a PR with all the needed information. Quoting Ben Lovett : > Hello, > > Recently, I have been having random page faults, and the application > that caused the fault is always random, or none at all, just idle. > These can occur after 2 days uptime, to 5 hours.. This is on a Toshiba > Satellite 2505CDS running 4.2-STABLE as of Sunday, January 14, 2001. > They also occured on this same system running 4.2-STABLE as of about a > month and a half ago. I don't remember the exact date I cvsup'd. > > Attached is a output of the most recent dmesg log with the reason it > page faulted. I hope this can help, and if there is *anything* somebody > would like me to show them, within reason of course, I'd be more than > happy to oblige. > > Thanks for your time! > -- > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Ben Lovett printf("Hello world!); > don4r return 0; > don4r@bsdguru.com > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Speak softly and carry a cellular phone. > --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 9: 6:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 18C0C37B6A2 for ; Fri, 19 Jan 2001 09:06:27 -0800 (PST) Received: from [128.9.176.134] (ras34.isi.edu [128.9.176.134]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id JAA13664; Fri, 19 Jan 2001 09:06:15 -0800 (PST) User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Fri, 19 Jan 2001 09:06:14 -0800 Subject: Re: SMP & APM (was Re: SMP & signal 11) From: Lars Eggert To: Volker Stolz , , Jamil Taylor , Message-ID: In-Reply-To: <20010119094456.A13840@agamemnon.informatik.rwth-aachen.de> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In local.freebsd-stable, you wrote: >> options SMP >> options APIC_IO >> device apm0 at nexus? # Advanced Power Management >> >> enabled in a kernel config file causes spurious signal 11's under >> FreeBSD-4.2 when more than one CPU is present in the system. > > Just on a specific machine? My dual Celerons are running fine w/o *any* > sig-11 for about a year tracking -STABLE. I've tried it on two different (but identical) brand-new Dell Precision 620's. At first I believed it to be a hardware problem, but then thesecond machine showed the same problems, and not including APM fixes it reliably on both machines. I'd be willing to invest a little time tracking this down, if one of the SMP people told me what information to gather and/or patches to apply. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 9:10:17 2001 Delivered-To: freebsd-stable@freebsd.org Received: from donkeykong.gpcc.itd.umich.edu (donkeykong.gpcc.itd.umich.edu [141.211.2.163]) by hub.freebsd.org (Postfix) with ESMTP id E43BF37B6A6; Fri, 19 Jan 2001 09:09:51 -0800 (PST) Received: from battlezone.gpcc.itd.umich.edu (smtp@battlezone.gpcc.itd.umich.edu [141.211.2.140]) by donkeykong.gpcc.itd.umich.edu (8.8.8/4.3-mailhub) with ESMTP id MAA17259; Fri, 19 Jan 2001 12:09:51 -0500 (EST) Received: from localhost (timcm@localhost) by battlezone.gpcc.itd.umich.edu (8.8.8/5.1-client) with ESMTP id MAA24814; Fri, 19 Jan 2001 12:09:50 -0500 (EST) Date: Fri, 19 Jan 2001 12:09:50 -0500 (EST) From: Tim McMillen X-Sender: timcm@battlezone.gpcc.itd.umich.edu To: Stephan Weaver Cc: questions@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Upgrading. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are a couple ways. 1. Backup your data and reinstall 4.2 release then cvsup to 4.2-stable and do the recommended upgrade cycle as in the handbook at: http://www.freebsd.org/handbook/cutting-edge.html (especially chapter 4), and /usr/src/UPDAATING 2. Install a snapshot. For that see http://www.freebsd.org/releases/snapshots.html I don't actually know how to install one. 3. Upgrade completely by source. If you're going to do that, a lot of people reccommend cvsupping and upgrading to 3.5-stable then to 4.2-stable. That way you get the most current in each branch and it is least painful. Either way, pay attention to /usr/src/UPDAATING Tim On Thu, 18 Jan 2001, Stephan Weaver wrote: > Hello, > Is there another way to upgrade from 3.3-R to 4.2-S ? > Please CC me because i am not on the list. > Thank you alot! > stephan > _________________________________________________________________________ > 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-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 Fri Jan 19 11: 6:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nemesis.worldnet.net (nemesis.worldnet.net [195.3.3.18]) by hub.freebsd.org (Postfix) with ESMTP id 74C8D37B400 for ; Fri, 19 Jan 2001 11:05:58 -0800 (PST) Received: from m2.worldnet.net (m2.worldnet.net [195.3.3.6]) by nemesis.worldnet.net (8.9.3/8.9.3) with ESMTP id UAA01968 for ; Fri, 19 Jan 2001 20:10:34 +0100 (CET) Received: from greatoak.home (p14-019.province.worldnet.fr [195.3.14.19]) by m2.worldnet.net (8.9.3/8.9.3) with ESMTP id UAA08257 for ; Fri, 19 Jan 2001 20:05:56 +0100 (CET) Received: (from pcasidy@localhost) by greatoak.home (8.11.1/8.11.1) id f0JHoPW16503 for freebsd-stable@freebsd.org; Fri, 19 Jan 2001 18:50:25 +0100 (CET) (envelope-from pcasidy) Message-Id: <200101191750.f0JHoPW16503@greatoak.home> Date: Fri, 19 Jan 2001 18:50:25 +0100 (CET) From: Philippe CASIDY Subject: Re: What's new with xdm and 4.2 ? [FINAL] To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I just want to let you know that I have solved my problem by means of tcpdump. I have an old attempt in my Xservers file. As my DNS server was cleaned and I totally forget this attempt I was trying to reach a very old machine which is not part of my network anymore. Thanks. Phil. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 11:11:57 2001 Delivered-To: freebsd-stable@freebsd.org Received: from relay4.inwind.it (relay4.inwind.it [212.141.53.75]) by hub.freebsd.org (Postfix) with ESMTP id 9055137B400 for ; Fri, 19 Jan 2001 11:11:39 -0800 (PST) Received: from bartequi.ottodomain.org (62.98.170.92) by relay4.inwind.it (5.1.056) id 3A5C385100242973; Fri, 19 Jan 2001 20:10:24 +0100 From: Salvo Bartolotta Date: Fri, 19 Jan 2001 19:12:58 GMT Message-ID: <20010119.19125800@bartequi.ottodomain.org> Subject: Re: ports To: Dominic Mitchell Cc: Christopher K Davis , freebsd-stable@FreeBSD.ORG References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> <20010119101650.A27757@semantico.com> X-Mailer: SuperCalifragilis X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 1/19/01, 11:16:50 AM, Dominic Mitchell wrote regarding Re: ports: > On Thu, Jan 18, 2001 at 10:02:23PM -0500, Christopher K Davis wrote: > > W Gerald Hicks writes: > > > > > This syndrome is often caused when one uses CVSup to update their ports > > > tree a long time after installing from a release. CVSup will not > > > normally delete any file it didn't create. Sometimes this will ca= use a > > > stale patch file to be left in a port. > > > > Would a reasonable test/fix for this be deleting the entire port directory > > in question and re-cvsupping? (This should make cvsup recreate everything > > and update its file lists, right?) > Even better would be to use the cvsupchk tool that comes with cvsup > (in the contrib directory) to get a list of files that shouldn't be > there anyway. Then you can just pass a list to "xargs rm -f". > It isn't installed by default, but if you still have a copy of the cvsup > tarball in /usr/ports/distfiles, it will be in there. Even the "binary" > distributions. You may wish to take a look at the cvsup FAQ found on http://www.polstra.com, and pay attention to the discussion in Q12, Q13. Mutatis mutandis, the same holds for the ports tree. Since ports are tagged "." (ie -CURRENT), one can correctly "sync" them for the first time by adding the *date* keyword (cf cvsup(1) for the exact format): one should specify a date as close as possible to that of "shipping" of one's ports tree. After cvsup has correctly created the ports checkouts file, which is precisely the goal of this first special synch operation, the date field must be removed; all subsequent updates will (ahem, should :-) be performed smoothly. Both approaches (the tool and the correct synching procedure) have been discussed countless times on these lists but, as the saying goes, few people read man pages, and fewer still the mailing list archives... :-) Best regards, Salvo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 11:22: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from svaha.com (unknown [209.21.191.25]) by hub.freebsd.org (Postfix) with SMTP id 1BAA137B400 for ; Fri, 19 Jan 2001 11:21:47 -0800 (PST) Received: (qmail 17396 invoked by uid 108); 19 Jan 2001 19:22:11 -0000 Date: Fri, 19 Jan 2001 14:22:11 -0500 (EST) From: Mike Conlen X-Sender: meconlen@ducktape.svaha.com To: freebsd-stable@freebsd.org Subject: Problem with -stable and ata drives Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a problem that, because of the nature of the problem and the environment I can't give better details on. When I cvsup'ed to -stable last week, (I was at 4.2 stable as of sometime in December at that point) I rebooted after installing the new kernel and when attempting to mount the filesystems it would time out on read. After a few such attempts it would fall back to PIO mode (which happens anyway eventually on my machine) and it could read, but then it would timeout on write while (I'm guessing here) fsck was running. I could boot the old kernel just fine. For some reason the new ipfw did not like diverting to natd and my networking was a bit of a mess. In any case, I could get the machine back to 4.2-release, which is where I sit for now. I didn't find anything about this type of a problem in the research I did. I'm curious if this is a known issue before I try to take my router apart to get chip set and drive information to debug. -- Groove on Dude Michael Conlen meconlen@obfuscated.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 11:35: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from drama.navipath.com (drama.navipath.com [216.67.14.8]) by hub.freebsd.org (Postfix) with ESMTP id BDE2D37B400 for ; Fri, 19 Jan 2001 11:34:50 -0800 (PST) Received: (from forrie@localhost) by drama.navipath.com with id f0JJYi227389 for freebsd-stable@freebsd.org; Fri, 19 Jan 2001 14:34:44 -0500 (EST) Date: Fri, 19 Jan 2001 14:34:44 -0500 From: Forrest Aldrich To: freebsd-stable@freebsd.org Subject: TTY console Message-ID: <20010119143444.A27354@drama.navipath.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 X-Loop: FreeBSD.ORG I have a Dell PowerEdge server. Using FreeBSD-4.2 (recently built and updated), I can only force the serial console IF I have a keyboard plugged in. It doesn't matter what flags I use -P -D -h or just -h. Is this a bug, or? _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 11:48:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id F22BB37B402 for ; Fri, 19 Jan 2001 11:48:14 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0JJm7G96216; Fri, 19 Jan 2001 11:48:07 -0800 (PST) (envelope-from dillon) Date: Fri, 19 Jan 2001 11:48:07 -0800 (PST) From: Matt Dillon Message-Id: <200101191948.f0JJm7G96216@earth.backplane.com> To: Mike Andrews Cc: Subject: Re: RE: Weird sporadic DNS resolution problems References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Short term, though, I liked the suggestion about stuffing an entry in :/etc/hosts to work around the broken domains' DNS problems, and that does :work for me for now. So at least I have an ugly workaround.. much less :ugly than restarted named every few hours though. Next, I'm going to :start comparing the sendmail.cf files built from my old 8.9.3 .mc file and :my current 8.11.x .mc file and see if any big differences jump out at :me... : :Mike Andrews * mandrews@dcr.net * mandrews@bit0.com * http://www.bit0.com Don't do that! If the broken hosts have at least one working name server, then you can use options in named.conf to make bind ignore the broken servers. The bind documentation has all the information you need to make this work. This is a whole lot safer then creating static entries in /etc/hosts. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 12:52:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 8EB7237B402 for ; Fri, 19 Jan 2001 12:52:36 -0800 (PST) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.1/8.11.1) with ESMTP id f0JKqSk11727; Fri, 19 Jan 2001 15:52:28 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.1.4.0.20010119154445.01ec8bc0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.1 Date: Fri, 19 Jan 2001 15:45:52 -0500 To: Matt Dillon From: Mike Tancsa Subject: Re: RE: Weird sporadic DNS resolution problems Cc: In-Reply-To: <200101191948.f0JJm7G96216@earth.backplane.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:48 AM 1/19/01 -0800, Matt Dillon wrote: > Don't do that! > > If the broken hosts have at least one working name server, then you > can use options in named.conf to make bind ignore the broken servers. > The bind documentation has all the information you need to make this > work. This is a whole lot safer then creating static entries in > /etc/hosts. Are you referring to auth-nxdomain ? Or something else ? ---Mike > -Matt > > > >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 Fri Jan 19 13: 1: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 5CB8837B401 for ; Fri, 19 Jan 2001 13:00:43 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0JL0Z398099; Fri, 19 Jan 2001 13:00:35 -0800 (PST) (envelope-from dillon) Date: Fri, 19 Jan 2001 13:00:35 -0800 (PST) From: Matt Dillon Message-Id: <200101192100.f0JL0Z398099@earth.backplane.com> To: Mike Tancsa Cc: Subject: Re: RE: Weird sporadic DNS resolution problems References: <5.0.1.4.0.20010119154445.01ec8bc0@marble.sentex.ca> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :At 11:48 AM 1/19/01 -0800, Matt Dillon wrote: : :> Don't do that! :> :> If the broken hosts have at least one working name server, then you :> can use options in named.conf to make bind ignore the broken servers. :> The bind documentation has all the information you need to make this :> work. This is a whole lot safer then creating static entries in :> /etc/hosts. : :Are you referring to auth-nxdomain ? Or something else ? : : ---Mike Let me find it... ah, here, look at the 'server' option. file:/usr/share/doc/bind/html/server.html And also the 'blackhole' option: file:/usr/share/doc/bind/html/options.html -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 14:53:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 68CC537B400; Fri, 19 Jan 2001 14:53:05 -0800 (PST) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id OAA26858; Fri, 19 Jan 2001 14:53:05 -0800 (PST) Message-ID: <3A68C532.B90C4244@isi.edu> Date: Fri, 19 Jan 2001 14:52:34 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: freebsd-stable@freebsd.org, mjacob@FreeBSD.org Subject: Intel PRO/1000F NIC & wx driver Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms3D07B55214AD3E67EA98CCDE" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms3D07B55214AD3E67EA98CCDE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The Intel PRO/1000F NIC does not seem to be fully supported by the wx driver. I have directly connected two of these cards with a fiber patch cable, link lights are on, and the driver tells me "wx0: gigabit link now up". However, pings across the link fail, because packets are simply swallowed: For a ping, I can see the ARP request go out in tcpdump, the TX light flickers, but the remote end never receives anything. We're using FreeBSD 4.2-RELEASE. The same setup works fine under Windows 2000, so I doubt it's hardware-related. [larse@hbo: ~] dmesg | grep wx wx0: mem 0xfafd0000-0xfafdffff,0xfafe0000-0xfaffffff irq 16 at device 4.0 on pci3 wx0: Ethernet address 00:03:47:07:e8:10 bpf: wx0 attached wx0: gigabit link now up [larse@hbo: ~] ifconfig -L wx0 wx0: flags=8843 mtu 1500 inet6 fe80::203:47ff:fe07:e810%wx0 prefixlen 64 scopeid 0x1 inet 128.9.112.174 netmask 0xfffff000 broadcast 128.9.127.255 ether 00:03:47:07:e8:10 media: 1000baseSX (autoselect ) status: active supported media: 1000baseSX 1000baseSX Please let me know how I can help to track this down! Lars -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms3D07B55214AD3E67EA98CCDE Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDExOTIyNTIzNFowIwYJKoZIhvcNAQkEMRYE FAIR+tdl5zTCDkOK5NUPsUyAcQeWMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAPfyMrdgyW4VfP1PxGiXw7kkPfCry4iXCywxraGb4dwfYzRyoFEf0 WbpnrRenNHXVlZG/PVFZPhGHp0tt1yBTYCEcVt8ZD2v7z+2X3I4PjI3mGR9mJguH+lWoWeIH ccUZCAx3GWyjMKWDtsJVqdkIZlsHc+EYnRGFwiodcYb+054= --------------ms3D07B55214AD3E67EA98CCDE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 15: 1:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id F356E37B404; Fri, 19 Jan 2001 15:01:17 -0800 (PST) Received: from isi.edu (hbo.isi.edu [128.9.160.75]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA27805; Fri, 19 Jan 2001 15:01:17 -0800 (PST) Message-ID: <3A68C71F.D3168082@isi.edu> Date: Fri, 19 Jan 2001 15:00:47 -0800 From: Lars Eggert Organization: USC Information Sciences Institute X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en, de MIME-Version: 1.0 To: freebsd-stable@freebsd.org, mjacob@FreeBSD.org Subject: Re: Intel PRO/1000F NIC & wx driver References: <3A68C532.B90C4244@isi.edu> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms70158D74D6133BB821A445E2" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a cryptographically signed message in MIME format. --------------ms70158D74D6133BB821A445E2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lars Eggert wrote: > The Intel PRO/1000F NIC does not seem to be fully supported by the wx > driver. Sorry for not mentioning this in the original post: This card uses the Intel 82543GC chip. -- Lars Eggert Information Sciences Institute http://www.isi.edu/larse/ University of Southern California --------------ms70158D74D6133BB821A445E2 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIIIwYJKoZIhvcNAQcCoIIIFDCCCBACAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BfQwggLYMIICQaADAgECAgMDIwUwDQYJKoZIhvcNAQEEBQAwgZQxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxFDASBgNVBAcTC0R1cmJhbnZpbGxlMQ8wDQYDVQQKEwZU aGF3dGUxHTAbBgNVBAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25h bCBGcmVlbWFpbCBSU0EgMTk5OS45LjE2MB4XDTAwMDgyNDIwMzAwOFoXDTAxMDgyNDIwMzAw OFowVDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVn Z2VydDEcMBoGCSqGSIb3DQEJARYNbGFyc2VAaXNpLmVkdTCBnzANBgkqhkiG9w0BAQEFAAOB jQAwgYkCgYEAz1yfcNs53rvhuw8gSDvr2+/snP8GduYY7x7WkJdyvcwb4oipNpWYIkMGP214 Zv1KrgvntGaG+jeugAGQt0n64VusgcIzQ6QDRtnMgdQDTAkVSQ2eLRSQka+nAPx6SFKJg79W EEHmgKQBMtZdMBYtYv/mTOcpm7jTJVg+7W6n04UCAwEAAaN3MHUwKgYFK2UBBAEEITAfAgEA MBowGAIBBAQTTDJ1TXlmZkJOVWJOSkpjZFoyczAYBgNVHREEETAPgQ1sYXJzZUBpc2kuZWR1 MAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUiKvxYINmVfTkWMdGHcBhvSPXw4wwDQYJKoZI hvcNAQEEBQADgYEAi65fM/jSCaPhRoA9JW5X2FktSFhE5zkIpFVPpv33GWPPNrncsK13HfZm s0B1rNy2vU7UhFI/vsJQgBJyffkLFgMCjp3uRZvBBjGD1q4yjDO5yfMMjquqBpZtRp5op3lT d01faA58ZCB5sxCb0ORSxvXR8tc9DJO0JIpQILa6vIAwggMUMIICfaADAgECAgELMA0GCSqG SIb3DQEBBAUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYD VQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9D ZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0 ZS5jb20wHhcNOTkwOTE2MTQwMTQwWhcNMDEwOTE1MTQwMTQwWjCBlDELMAkGA1UEBhMCWkEx FTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoT BlRoYXd0ZTEdMBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNv bmFsIEZyZWVtYWlsIFJTQSAxOTk5LjkuMTYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGB ALNpWpfU0BYLerXFXekhnCNyzRJMS/d+z8f7ynIk9EJSrFeV43theheE5/1yOTiUtOrtZaeS Bl694GX2GbuUeXZMPrlocHWEHPQRdAC8BSxPCQMXMcz0QdRyxqZd4ohEsIsuxE3x8NaFPmzz lZR4kX5A6ZzRjRVXjsJz5TDeRvVPAgMBAAGjNzA1MBIGA1UdEwEB/wQIMAYBAf8CAQAwHwYD VR0jBBgwFoAUcknCczTGVfQLdnKBfnf0h+fGsg4wDQYJKoZIhvcNAQEEBQADgYEAa8ZZ6TH6 6bbssQPY33Jy/pFgSOrGVd178GeOxmFw523CpTfYnbcXKFYFi91cdW/GkZDGbGZxE9AQfGuR b4bgITYtwdfqsgmtzy1txoNSm/u7/pyHnfy36XSS5FyXrvx+rMoNb3J6Zyxrc/WG+Z31AG70 HQfOnZ6CYynvkwl+Vd4xggH3MIIB8wIBATCBnDCBlDELMAkGA1UEBhMCWkExFTATBgNVBAgT DFdlc3Rlcm4gQ2FwZTEUMBIGA1UEBxMLRHVyYmFudmlsbGUxDzANBgNVBAoTBlRoYXd0ZTEd MBsGA1UECxMUQ2VydGlmaWNhdGUgU2VydmljZXMxKDAmBgNVBAMTH1BlcnNvbmFsIEZyZWVt YWlsIFJTQSAxOTk5LjkuMTYCAwMjBTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzELBgkq hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTAxMDExOTIzMDA0N1owIwYJKoZIhvcNAQkEMRYE FKgvqjWY1T6+LYyWXw7dj0XmphPVMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYI KoZIhvcNAwICAgCAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgFAMA0GCCqGSIb3DQMCAgEoMA0G CSqGSIb3DQEBAQUABIGAvC8+3QchJvcBLaC0sPZP3lo/dEvS5HsFQio4NEBF/XivsDp8Y6fY v0wtC2bg3zqorncSVTqIEPz3bxIXFh6IrYdhl3kuh9N8WRe+kCcd3MsxKwv1cJuOCggY6mSe RmlX9srTxUoplrI1pPoNrNNaVjqgHsRPBu4ULVS9eCY2oHk= --------------ms70158D74D6133BB821A445E2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 16:20:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kline-station.ckdhr.com (kline-station.ckdhr.com [209.192.160.22]) by hub.freebsd.org (Postfix) with SMTP id 6666437B400 for ; Fri, 19 Jan 2001 16:19:57 -0800 (PST) Received: (qmail 18610 invoked by uid 139); 20 Jan 2001 00:19:55 -0000 To: freebsd-stable@FreeBSD.ORG Subject: Re: ports References: <024201c08185$44c5efb0$3028680a@tgt.com> <3A6772B4.4E9FBE74@cisco.com> <20010119101650.A27757@semantico.com> <20010119.19125800@bartequi.ottodomain.org> X-Face: I8Alb*-ZdjN\/8k_QR,^l^m6GQB'S-B:}DVP].1HOw#tx:TX$k;Wl;4zqjWR|-jheM#? &beRf(!|0b0m=M~=%.Am>"QEY.(#Ys.%"s?z,hmwp&y0%p>9+T X-Attribution: ckd Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII From: Christopher K Davis Date: 19 Jan 2001 19:19:54 -0500 In-Reply-To: Salvo Bartolotta's message of "Fri, 19 Jan 2001 19:12:58 GMT" Message-ID: Lines: 25 X-Mailer: Gnus v5.6.44/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Salvo Bartolotta writes: > You may wish to take a look at the cvsup FAQ found on > http://www.polstra.com, and pay attention to the discussion in Q12, > Q13. [...] > Both approaches (the tool and the correct synching procedure) have > been discussed countless times on these lists but, as the saying goes, > few people read man pages, and fewer still the mailing list > archives... :-) The tool isn't in the cvsupit package, nor is the "pump priming sync" technique in the Handbook (under any of current, synching, or cvsup). (Admittedly a link to the cvsup home page is there, so I could have found the FAQ that way. Mea culpa on that bit.) WIBNI the cvsupit package would do the pump priming for you? But then, it'd have to figure out what version of the source you were starting with (probably easy) *and* the date of the ports collection you're working with (probably not as easy). Hmm.... -- Christopher Davis * * Put location information in your DNS! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 16:32: 0 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 A504C37B400 for ; Fri, 19 Jan 2001 16:31:43 -0800 (PST) Received: from pir by moek.pir.net with local (Exim) id 14JlwP-0003pi-00 for freebsd-stable@freebsd.org; Fri, 19 Jan 2001 19:31:37 -0500 Date: Fri, 19 Jan 2001 19:31:36 -0500 From: Peter Radcliffe To: freebsd-stable@freebsd.org Subject: Re: Intel PRO/1000F NIC & wx driver Message-ID: <20010119193136.G5325@pir.net> Reply-To: freebsd-stable@freebsd.org Mail-Followup-To: freebsd-stable@freebsd.org References: <3A68C532.B90C4244@isi.edu> <3A68C71F.D3168082@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A68C71F.D3168082@isi.edu>; from larse@ISI.EDU on Fri, Jan 19, 2001 at 03:00:47PM -0800 X-fish: < X-Copy-On-Listmail: Please do NOT Cc: me on list mail. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lars Eggert probably said: > Lars Eggert wrote: > > The Intel PRO/1000F NIC does not seem to be fully supported by the wx > > driver. > Sorry for not mentioning this in the original post: This card uses the > Intel 82543GC chip. I realise this isn't very useful to you for getting that card working, but if you need gig ether working sooner than a fix I've been using the Netgear GA620, both fibre and copper versions; ti0: mem 0xf4000000-0xf4003fff irq 10 at device 15.0 on pci0 ti0: gigabit link up ti0: flags=8843 mtu 1500 inet 130.64.1.222 netmask 0xffffff00 broadcast 130.64.1.255 ether 00:02:e3:00:3d:a0 media: autoselect (1000baseTX ) status: active supported media: autoselect 1000baseTX 1000baseTX 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP Negotiates fine with the Foundry kit we use, at 100bT fdx and gbit fdx. 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 Fri Jan 19 17:39:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3C2D637B401 for ; Fri, 19 Jan 2001 17:39:34 -0800 (PST) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA06686; Fri, 19 Jan 2001 17:27:13 -0800 Date: Fri, 19 Jan 2001 17:39:31 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Lars Eggert Cc: freebsd-stable@freebsd.org Subject: Re: Intel PRO/1000F NIC & wx driver In-Reply-To: <3A68C532.B90C4244@isi.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll look at it when I next spend a couple of days on this NIC (hopefully next week). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 18:34:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from firebat.bushong.net (c128625-a.frmt1.sfba.home.com [24.176.225.90]) by hub.freebsd.org (Postfix) with ESMTP id B449637B402 for ; Fri, 19 Jan 2001 18:34:23 -0800 (PST) Received: (from dbushong@localhost) by firebat.bushong.net (8.11.0/8.11.0) id f0K2YNL49314 for freebsd-stable@freebsd.org; Fri, 19 Jan 2001 18:34:23 -0800 (PST) (envelope-from dbushong) Date: Fri, 19 Jan 2001 18:34:23 -0800 From: David Bushong To: freebsd-stable@freebsd.org Subject: sshd with ssh -t problems Message-ID: <20010119183423.F16505@bushong.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure if someone else has run into this, but with 4.2-STABLE circa 1/16/2000's sshd I get the following behavior: othermachine% ssh -t 4.2stable-box ls 4.2stable-box% That is, from any other machine (running ssh-1.2.27 or various versions of openssh), trying to run a command via ssh while using the -t flag (particularly useful for, say, screen), causes you to log in, instead of merely executing the command and exiting (it seems to ignore the command, in fact) Is this a known problem? (I'm using the stock sshd_config) --David Bushong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 18:43:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f12.law10.hotmail.com [64.4.15.12]) by hub.freebsd.org (Postfix) with ESMTP id EBD1C37B402 for ; Fri, 19 Jan 2001 18:43:02 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 19 Jan 2001 18:43:02 -0800 Received: from 196.3.147.168 by lw10fd.law10.hotmail.msn.com with HTTP; Sat, 20 Jan 2001 02:43:02 GMT X-Originating-IP: [196.3.147.168] From: "Stephan Weaver" To: stable@freebsd.org Subject: cvsup Date: Fri, 19 Jan 2001 22:43:02 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 20 Jan 2001 02:43:02.0615 (UTC) FILETIME=[B55B9670:01C0828A] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Upgrading from 3.3 - 4.2 at build world stage and i get this error: groff: illegal option -- U Any help please? Please CC me because i am not on the list (stephanweaver@hotmail.com) Thank you SO MUCH! stephan _________________________________________________________________________ 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 Fri Jan 19 18:46:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from svaha.com (unknown [209.21.191.25]) by hub.freebsd.org (Postfix) with SMTP id 7E73337B401 for ; Fri, 19 Jan 2001 18:46:27 -0800 (PST) Received: (qmail 23176 invoked by uid 108); 20 Jan 2001 02:46:51 -0000 Date: Fri, 19 Jan 2001 21:46:50 -0500 (EST) From: Mike Conlen X-Sender: meconlen@ducktape.svaha.com To: Stephan Weaver Cc: stable@freebsd.org Subject: Re: cvsup In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 19 Jan 2001, Stephan Weaver wrote: > Upgrading from 3.3 - 4.2 at build world stage and i get this error: groff: > illegal option -- U > Any help please? try upgrading from 3.3 to the last stable in 3, then to the 4 line. I've usually gone from 3.3 to 3 stable, to 4_0_release to whatever in 4 I'm looking for. -- Groove on Dude Michael Conlen meconlen@obfuscated.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 19:35: 1 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 3E41837B400 for ; Fri, 19 Jan 2001 19:34:43 -0800 (PST) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 20E773E02; Fri, 19 Jan 2001 19:34:39 -0800 (PST) Received: from unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 1A3133C10A; Fri, 19 Jan 2001 19:34:39 -0800 (PST) To: David Bushong Cc: freebsd-stable@freebsd.org Subject: Re: sshd with ssh -t problems In-Reply-To: Message from David Bushong of "Fri, 19 Jan 2001 18:34:23 PST." <20010119183423.F16505@bushong.net> Date: Fri, 19 Jan 2001 19:34:34 -0800 From: Dima Dorfman Message-Id: <20010120033439.20E773E02@bazooka.unixfreak.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not sure if someone else has run into this, but with 4.2-STABLE circa > 1/16/2000's sshd I get the following behavior: > > othermachine% ssh -t 4.2stable-box ls > > 4.2stable-box% I can reproduce this. The problem was introduced in OpenSSH 2.3.0, which was recently MFC'd. The patch below fixes the problem. I did *very* little testing on it, as the only host I have with -current (and thus, openssh 2.3.0) makes no substansial use of ssh. The problem is that the routine checks to see if a command was specified so it won't do things like print the motd if you're not running a shell, but fails to propogate it back to the rest of the program, which then assumes none was specified. In fact, I can't see why it compiles without warnings in the first place: the function is supposed to return a (char *), but the line I replaced clearly doesn't do that. The patch applies against src/crypto/openssh/session.c. To get a new sshd, you can either do a make world, or, if you don't have a fast CPU (which I don't, FWIW), you can run `make` in src/secure/lib/libssh and src/secure/usr.sbin/sshd, which will produce src/secure/usr.sbin/sshd/sshd. It would be nice if you could do some testing and report back. If there are no problems, I'll submit it to the OpenSSH people (if they haven't already fixed it). Thanks Dima Dorfman dima@unixfreak.org Index: session.c =================================================================== RCS file: /st/src/FreeBSD/src/crypto/openssh/session.c,v retrieving revision 1.12 diff -u -r1.12 session.c --- session.c 2000/12/06 10:55:44 1.12 +++ session.c 2001/01/20 03:29:26 @@ -705,7 +705,7 @@ /* Done if .hushlogin exists or a command given. */ if (command != NULL) - return; + return newcommand; snprintf(buf, sizeof(buf), "%.200s/.hushlogin", pw->pw_dir); #ifdef HAVE_LOGIN_CAP lc = login_getpwclass(pw); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 20:46:54 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id C634937B6A2 for ; Fri, 19 Jan 2001 20:46:36 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id zzssaaaa for ; Sat, 20 Jan 2001 15:55:07 +1100 Message-ID: <3A691823.A999C66D@quake.com.au> Date: Sat, 20 Jan 2001 15:46:27 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Conlen Cc: freebsd-stable@freebsd.org Subject: Re: Problem with -stable and ata drives References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Conlen wrote: > > I've got a problem that, because of the nature of the problem and the > environment I can't give better details on. > > When I cvsup'ed to -stable last week, (I was at 4.2 stable as of sometime > in December at that point) I rebooted after installing the new kernel and > when attempting to mount the filesystems it would time out on read. After > a few such attempts it would fall back to PIO mode (which happens anyway > eventually on my machine) and it could read, but then it would timeout on > write while (I'm guessing here) fsck was running. I could boot the old > kernel just fine. For some reason the new ipfw did not like diverting to > natd and my networking was a bit of a mess. In any case, I could get the > machine back to 4.2-release, which is where I sit for now. I didn't find > anything about this type of a problem in the research I did. I'm curious > if this is a known issue before I try to take my router apart to get chip > set and drive information to debug. Yes, this is a know problem with some ata controllers... What chip set is your controller? I had this happen with an Aladdin ata controller a few months back, I got a patch from Soren that fixed it up... I dont think he has MFC'd in the patch yet, maybe it still needs more testing... Anyway if you searched the stable archives I am sure you would find some posts about this... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 20:51:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 2F7CA37B6A4 for ; Fri, 19 Jan 2001 20:51:32 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id batsaaaa for ; Sat, 20 Jan 2001 16:00:03 +1100 Message-ID: <3A691942.8D655973@quake.com.au> Date: Sat, 20 Jan 2001 15:51:14 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Conlen , freebsd-stable@freebsd.org Subject: Re: Problem with -stable and ata drives References: <3A691823.A999C66D@quake.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually it looks like he just MFC'd the patch in yesterday.. Modified files: (Branch: RELENG_4) sys/dev/ata ata-dma.c Log: MFC: Properly backspeed DMA on the ACER chips. Revision Changes Path 1.35.2.8 +3 -3 src/sys/dev/ata/ata-dma.c Get the new ata-dma.c and recompile your kernel, that should fix the problem unless this is a new one... Good Luck! Kal. Kal Torak wrote: > > Mike Conlen wrote: > > > > I've got a problem that, because of the nature of the problem and the > > environment I can't give better details on. > > > > When I cvsup'ed to -stable last week, (I was at 4.2 stable as of sometime > > in December at that point) I rebooted after installing the new kernel and > > when attempting to mount the filesystems it would time out on read. After > > a few such attempts it would fall back to PIO mode (which happens anyway > > eventually on my machine) and it could read, but then it would timeout on > > write while (I'm guessing here) fsck was running. I could boot the old > > kernel just fine. For some reason the new ipfw did not like diverting to > > natd and my networking was a bit of a mess. In any case, I could get the > > machine back to 4.2-release, which is where I sit for now. I didn't find > > anything about this type of a problem in the research I did. I'm curious > > if this is a known issue before I try to take my router apart to get chip > > set and drive information to debug. > > Yes, this is a know problem with some ata controllers... What chip set is > your controller? I had this happen with an Aladdin ata controller a few months > back, I got a patch from Soren that fixed it up... I dont think he has MFC'd > in the patch yet, maybe it still needs more testing... > > Anyway if you searched the stable archives I am sure you would find some posts > about this... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 19 23:27:39 2001 Delivered-To: freebsd-stable@freebsd.org Received: from sm4.texas.rr.com (sm4.texas.rr.com [24.93.35.211]) by hub.freebsd.org (Postfix) with ESMTP id 4CFDA37B400 for ; Fri, 19 Jan 2001 23:27:22 -0800 (PST) Received: from nasby.net (cs16290-196.austin.rr.com [24.162.90.196]) by sm4.texas.rr.com (8.10.1/8.10.1) with ESMTP id f0K7QAW05103; Sat, 20 Jan 2001 01:26:20 -0600 Message-ID: <3A693D88.9D1F4E3D@nasby.net> Date: Sat, 20 Jan 2001 01:26:00 -0600 From: "Jim C. Nasby" Organization: distributed.net X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en-US,en MIME-Version: 1.0 To: Mike Tancsa Cc: Sys Admin , freebsd-stable@freebsd.org Subject: Re: RAID configuration for a mail server (1 or 5) References: <4.2.2.20010117193231.03731950@marble.sentex.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Tancsa wrote: > For speed, reliability and cost, have a look at the 4port 3ware card > (www.3ware.com) in RAID 10 config. Two RAID0 sets mirrored together. Get FWIW, a RAID0 of RAID1 sets is more desireable. When one of the drives fails, you only have to rebuild one drive, using it's mirrored counterpart. In the other case, you have to rebuild an entire RAID0 set from another set, tying up every drive in the system. Also, depending on how the mirroring is done, simultaneous failure of a drive on each mirror could render you without any data. While it would be really bad luck to lose two drives at once, the odds losing one on each mirror are far greater than losing both drives in a two-drive mirror that happens to be part of a stripe set. BTW, if memory serves, the downside that RAID 5 has over RAID 0 is that in order to update a segment of the set, you must first read the entire segment in, then recalculate it with the changed data, then write the changes back out. This will very often result in 2x the number of r/w operations as the number of drives. If you want more information, I suggest reading the excellent RAID overview at the vinum site. -- Jim C. Nasby (aka Decibel!) /^\ jim@nasby.net /___\ Freelance lighting designer and database developer / | \ Member: Triangle Fraternity, Sports Car Club of America /___|___\ Give your computer some brain candy! www.distributed.net Team #1828 Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 1: 3:26 2001 Delivered-To: freebsd-stable@freebsd.org Received: from firebat.bushong.net (c128625-a.frmt1.sfba.home.com [24.176.225.90]) by hub.freebsd.org (Postfix) with ESMTP id D330037B401 for ; Sat, 20 Jan 2001 01:03:06 -0800 (PST) Received: (from dbushong@localhost) by firebat.bushong.net (8.11.0/8.11.0) id f0K932M53560; Sat, 20 Jan 2001 01:03:02 -0800 (PST) (envelope-from dbushong) Date: Sat, 20 Jan 2001 01:03:02 -0800 From: David Bushong To: Dima Dorfman Cc: freebsd-stable@freebsd.org Subject: Re: sshd with ssh -t problems Message-ID: <20010120010302.G16505@bushong.net> References: <20010120033439.20E773E02@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010120033439.20E773E02@bazooka.unixfreak.org>; from dima@unixfreak.org on Fri, Jan 19, 2001 at 07:34:34PM -0800 X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yup, that fixed it. Thanks! BTW, in most source trees, doing the "make" in /usr/src/secure/usr.sbin/sshd will give you an sshd binary in /usr/obj/usr/src/secure/usr.sbin/sshd (depending on your paths, of course) Thanks again, --David Bushong On Fri, Jan 19, 2001 at 07:34:34PM -0800, Dima Dorfman wrote: > > Not sure if someone else has run into this, but with 4.2-STABLE circa > > 1/16/2000's sshd I get the following behavior: > > > > othermachine% ssh -t 4.2stable-box ls > > > > 4.2stable-box% > > I can reproduce this. The problem was introduced in OpenSSH 2.3.0, > which was recently MFC'd. > > The patch below fixes the problem. I did *very* little testing on it, > as the only host I have with -current (and thus, openssh 2.3.0) makes > no substansial use of ssh. > > The problem is that the routine checks to see if a command was > specified so it won't do things like print the motd if you're not > running a shell, but fails to propogate it back to the rest of the > program, which then assumes none was specified. In fact, I can't see > why it compiles without warnings in the first place: the function is > supposed to return a (char *), but the line I replaced clearly doesn't > do that. > > The patch applies against src/crypto/openssh/session.c. To get a new > sshd, you can either do a make world, or, if you don't have a fast CPU > (which I don't, FWIW), you can run `make` in src/secure/lib/libssh and > src/secure/usr.sbin/sshd, which will produce > src/secure/usr.sbin/sshd/sshd. > > It would be nice if you could do some testing and report back. If > there are no problems, I'll submit it to the OpenSSH people (if they > haven't already fixed it). > > Thanks > > Dima Dorfman > dima@unixfreak.org > > Index: session.c > =================================================================== > RCS file: /st/src/FreeBSD/src/crypto/openssh/session.c,v > retrieving revision 1.12 > diff -u -r1.12 session.c > --- session.c 2000/12/06 10:55:44 1.12 > +++ session.c 2001/01/20 03:29:26 > @@ -705,7 +705,7 @@ > > /* Done if .hushlogin exists or a command given. */ > if (command != NULL) > - return; > + return newcommand; > snprintf(buf, sizeof(buf), "%.200s/.hushlogin", pw->pw_dir); > #ifdef HAVE_LOGIN_CAP > lc = login_getpwclass(pw); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 6:41:34 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 C0EA837B402 for ; Sat, 20 Jan 2001 06:41:16 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA60746; Sat, 20 Jan 2001 15:41:06 +0100 (CET) (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: David Bushong Cc: Dima Dorfman , freebsd-stable@FreeBSD.ORG Subject: Re: sshd with ssh -t problems References: <20010120033439.20E773E02@bazooka.unixfreak.org> <20010120010302.G16505@bushong.net> From: Dag-Erling Smorgrav Date: 20 Jan 2001 15:41:06 +0100 In-Reply-To: David Bushong's message of "Sat, 20 Jan 2001 01:03:02 -0800" Message-ID: Lines: 11 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Bushong writes: > Yup, that fixed it. Thanks! BTW, in most source trees, doing the "make" > in /usr/src/secure/usr.sbin/sshd will give you an sshd binary in > /usr/obj/usr/src/secure/usr.sbin/sshd (depending on your paths, of course) Only if you've done a 'make obj' first, or have an obj tree left over from a 'make world' or something. 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 Sat Jan 20 9:56:13 2001 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id 453AC37B400 for ; Sat, 20 Jan 2001 09:55:56 -0800 (PST) Received: from marlowe (accord.grasslake.net [206.11.249.240]) by accord.grasslake.net (8.11.1/8.11.1) with SMTP id f0KHr8E57474 for ; Sat, 20 Jan 2001 11:53:08 -0600 (CST) (envelope-from swb@grasslake.net) Message-ID: <006301c0830a$65959f70$b8209fc0@marlowe> From: "Shawn Barnhart" To: Subject: Limit on the number of disklabel entries? Date: Sat, 20 Jan 2001 11:57:04 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a hard limit on the number of disk label entries? I have a disk slice defined with partitions a-h and would like to an 'i' entry to finish off the disk space. Is this not permitted? When I try to create the device, I get the following error: [root@ftp /dev] # sh ./MAKEDEV amrd0s1i bad partition for disk in: amrd0s1i A quick glance at MAKEDEV shows that it is only coded to create partitions up to 'h'. Is it a matter of editing MAKEDEV or are there other reasons to limit a slice to only 7 partition entries? disklabel /dev/amrd0s1 # size offset fstype [fsize bsize bps/cpg] a: 1024000 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 63*) b: 1319296 1024000 swap # (Cyl. 63*- 145*) c: 71119692 0 unused 0 0 # (Cyl. 0 - 4426*) e: 2097152 2343296 4.2BSD 1024 8192 16 # (Cyl. 145*- 276*) f: 12582912 4440448 4.2BSD 1024 8192 16 # (Cyl. 276*- 1059*) g: 16777216 17023360 4.2BSD 1024 8192 16 # (Cyl. 1059*- 2103*) h: 16777216 33800576 4.2BSD 1024 8192 16 # (Cyl. 2103*- 3148*) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 10:30:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 12E5537B404 for ; Sat, 20 Jan 2001 10:30:28 -0800 (PST) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id TAA26864 for stable@freebsd.org; Sat, 20 Jan 2001 19:30:16 +0100 (MET) >Received: from aklemm.klemm.gtn.com (aklemm.klemm.gtn.com [172.16.2.4]) by klemm.gtn.com (8.11.1/8.11.1) with ESMTP id f0KIMIi02576 for ; Sat, 20 Jan 2001 19:22:18 +0100 (CET) (envelope-from andreas@klemm.gtn.com) Received: (from andreas@localhost) by aklemm.klemm.gtn.com (8.11.1/8.11.1) id f0KIMIY00626 for stable@freebsd.org; Sat, 20 Jan 2001 19:22:18 +0100 (CET) (envelope-from andreas) Date: Sat, 20 Jan 2001 19:22:12 +0100 From: Andreas Klemm To: stable@freebsd.org Subject: =?iso-8859-1?Q?sound_doesn=B4t_work_anymore_after_upgrading_to_last_4=2E?= =?iso-8859-1?Q?2_STABLE?= Message-ID: <20010120192212.A551@aklemm.klemm.gtn.com> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 4.2-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi ! After upgrading my 4.2-STABLE from Jan. 09th 2001 to the last recent version and updating the kernel, my Laptops (Toshiba Satellite Pro 4360) soundcard doesn=B4t work anymore. During boot I see the follogin message: pcm0: ac97 codec invalid or not present (id =3D=3D 0) Error messages in the xconsole when trying to use the soundcard (mpg123): pcm0: play interrupt timeout, channel dead pcm0: play interrupt timeout, channel dead Below dmesg output and kernel config file. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Sat Jan 20 16:22:47 CET 2001 root@aklemm.klemm.gtn.com:/usr/src/sys/compile/AKLEMM Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (696.58-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x683 Stepping =3D 3 Features=3D0x383f9ff real memory =3D 201195520 (196480K bytes) avail memory =3D 192446464 (187936K bytes) Preloaded elf kernel "kernel" at 0xc0304000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc030409c. VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc02ad242 (1000022) VESA: S3 Incorporated. M7 BIOS Pentium Pro MTRR support enabled apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 isab0: at device 5.0 on pci0 isa0: on isab0 atapci0: port 0xfff0-0xffff at device 5.1 on= pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 5.2 irq 11 chip1: port 0xfe70-0xfe7f at de= vice 5.3 on pci0 pci0: (vendor=3D0x11c1, dev=3D0x0441) at 7.0 irq 3 pci0: (vendor=3D0x1179, dev=3D0x0d01) at 9.0 irq 11 chip2: at device 11.0= on pci0 chip3: at device 11.1= on pci0 pcm0: port 0xfefc-0xfeff,0xff00-0xff3f mem 0xefff80= 00-0xefffffff irq 11 at device 12.0 on pci0 pcm0: ac97 codec invalid or not present (id =3D=3D 0) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ !!!!!!!!!!!!!!!!!!!!!! fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <9 virtual consoles, flags=3D0x300> pcic0: at port 0x3e0 iomem 0xd0000 on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ppi0: on ppbus0 pccard: card inserted, slot 0 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 11513MB [23392/16/63] at ata0-master UDMA33 acd0: DVD-ROM at ata1-master using UDMA33 Mounting root from ufs:/dev/ad0s2a xe0 at port 0x2e8-0x2ef iomem 0xd0000-0xd0fff irq 10 slot 0 on pccard0 xe0: Xircom CEM56, bonding version 0x55, 100Mbps capable, with modem xe0: DingoID =3D 0x444b, RevisionID =3D 0x1, VendorID =3D 0 xe0: Ethernet address 00:10:a4:bb:11:e8 IP packet filtering initialized, divert disabled, rule-based forwarding dis= abled, default to deny, logging disabled xe0: watchdog timeout; resetting card uhci0: port 0xff80-0xff9f irq 11 = at device 5.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered /dev/vmmon: Module vmmon: registered with major=3D200 minor=3D0 tag=3D$Name= : build-570 $ /dev/vmmon: Module vmmon: initialized xe0: promiscuous mode enabled vmnet1: promiscuous mode enabled pcm0: play interrupt timeout, channel dead pcm0: play interrupt timeout, channel dead My kernel config: machine i386 cpu I686_CPU ident AKLEMM maxusers 100 options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MD_ROOT #MD is a potential root device options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options SHMSEG=3D150 options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev options PQ_NORMALCACHE options MROUTING device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? options MAXCONS=3D9 options SC_HISTORY_SIZE=3D1024 options SC_PIXEL_MODE options VESA # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? flags 0x20 # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device # Xircom Ethernet device xe # sound support device pcm # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device ppp 1 # Kernel PPP options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpf) pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gif 4 # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter Andreas /// --=20 Andreas Klemm - Powered by FreeBSD 4.2 SMP Need a magic printfilter today ? -> http://www.apsfilter.org/ --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Weitere Infos: siehe http://www.gnupg.org iD8DBQE6addTd3o+lGxvbLoRAvkkAJ0dmLzpMLWuZ0cIvCAW3ovWExotfQCgiAmj DywYcLXcq3FuFmha+SBIVQo= =+ALq -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 11: 9:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from forrie.net (forrie.net [216.67.14.69]) by hub.freebsd.org (Postfix) with ESMTP id C6C5937B400 for ; Sat, 20 Jan 2001 11:09:41 -0800 (PST) Received: from boom.forrie.com (forrie.ne.mediaone.net [24.147.132.133]) by forrie.net with id f0KJ9ej32868 for ; Sat, 20 Jan 2001 14:09:41 -0500 (EST) Message-Id: <5.0.0.25.2.20010120140820.02188bd0@216.67.14.69> X-Sender: forrie@216.67.14.69 X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 20 Jan 2001 14:09:31 -0500 To: freebsd-stable@freebsd.org From: Forrest Aldrich Subject: Required files for Linux emulation Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a third-party program (Interscan Viruswall, anyone using that on FreeBSD?) that seems to require an additional amount of info to determine the version of Linux supported: grep: /etc/redhat-release: No such file or directory InterScan 3.0.1 now only support running on Linux 6.0 or above How can we address this? Thanks, _F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 11:12: 8 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 69FF237B400 for ; Sat, 20 Jan 2001 11:11:50 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f0KJBaj33823; Sat, 20 Jan 2001 11:11:36 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: "Shawn Barnhart" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Limit on the number of disklabel entries? In-Reply-To: Message from "Shawn Barnhart" of "Sat, 20 Jan 2001 11:57:04 CST." <006301c0830a$65959f70$b8209fc0@marlowe> Date: Sat, 20 Jan 2001 11:11:36 -0800 Message-ID: <33819.980017896@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there a hard limit on the number of disk label entries? Yes. a-h is all you get (8) and of those, c is not usable unless you want to address the entire slice. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 11:32:11 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 8560837B400 for ; Sat, 20 Jan 2001 11:31:51 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0KJUKw08417; Sat, 20 Jan 2001 11:30:20 -0800 (PST) (envelope-from dillon) Date: Sat, 20 Jan 2001 11:30:20 -0800 (PST) From: Matt Dillon Message-Id: <200101201930.f0KJUKw08417@earth.backplane.com> To: Jordan Hubbard Cc: "Shawn Barnhart" , freebsd-stable@FreeBSD.ORG Subject: Re: Limit on the number of disklabel entries? References: <33819.980017896@winston.osd.bsdi.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Is there a hard limit on the number of disk label entries? : :Yes. a-h is all you get (8) and of those, c is not usable unless :you want to address the entire slice. : :- Jordan I researched this a few months ago. The only thing preventing us from increasing the number of partitions in a disklabel is our major/minor device numbering scheme. It isn't a minor fix, though. In the mean time, it is possible to quadruple the number of partitions you have by using all four fdisk slice entries. Each slice can have its own partition table. I do this on my home server's 18G HD: apollo:/home/dillon> df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 127023 61449 55413 53% / /dev/da0s1d 127023 39697 77165 34% /var /dev/da0s1e 127023 98 116764 0% /var/tmp /dev/da0s1f 1016303 842959 92040 90% /usr /dev/da0s1g 126322 28039 88178 24% /var/log /dev/da0s2a 1524463 631822 770684 45% /archive /dev/da0s2d 3048942 2040806 764221 73% /u1 /dev/da0s2e 5541549 3694467 1403759 72% /FreeBSD /dev/da0s2f 2032623 1201468 668546 64% /images /dev/da0s2g 3048942 531556 2273471 19% /usr/obj procfs 4 4 0 100% /proc -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 11:52:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from accord.grasslake.net (accord.grasslake.net [206.11.249.240]) by hub.freebsd.org (Postfix) with ESMTP id 7D33637B404 for ; Sat, 20 Jan 2001 11:51:53 -0800 (PST) Received: from marlowe (accord.grasslake.net [206.11.249.240]) by accord.grasslake.net (8.11.1/8.11.1) with SMTP id f0KJmxE57625; Sat, 20 Jan 2001 13:48:59 -0600 (CST) (envelope-from swb@grasslake.net) Message-ID: <009201c0831a$94db1cf0$b8209fc0@marlowe> From: "Shawn Barnhart" To: "Matt Dillon" Cc: References: <33819.980017896@winston.osd.bsdi.com> <200101201930.f0KJUKw08417@earth.backplane.com> Subject: Re: Limit on the number of disklabel entries? Date: Sat, 20 Jan 2001 13:52:55 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Matt Dillon" > In the mean time, it is possible to quadruple the number of partitions > you have by using all four fdisk slice entries. Each slice can have its > own partition table. I do this on my home server's 18G HD: This crossed my mind, but I decided against it as it would have meant re-slicing the disk, which I'm not sure I could have done without reinstalling. I just divided my free disk space into two rather than three as I had planned. Is this ever an issue for anyone with very, very large disks or arrays where a large number of logical filesystems might be desired? If my math is right, there's a limit of 24 filesystems per disk, which is really only 20 if you exclude /, swap, /var, and /usr. I'm not sure why it would be necessary or desirable to divide a disk into more filesystems than that, but it does seem like it would be annoying if there was no other way to atomically divide the disk (eg, large array). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 12:28:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from saturn.home.ben.com (c1058885-a.bvrtn1.or.home.com [24.12.186.106]) by hub.freebsd.org (Postfix) with ESMTP id 7B50F37B400 for ; Sat, 20 Jan 2001 12:28:30 -0800 (PST) Received: from saturn.home.ben.com (bjj@localhost) by saturn.home.ben.com (8.11.1/8.9.3) with ESMTP id f0KKSUr80758 for ; Sat, 20 Jan 2001 12:28:30 -0800 (PST) Message-Id: <200101202028.f0KKSUr80758@saturn.home.ben.com> To: freebsd-stable@FreeBSD.ORG Subject: preventing cvsup from replacing /usr/ports symlink? Date: Sat, 20 Jan 2001 12:28:14 -0800 From: Ben Jackson Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My /usr/ports is a symlink to another filesystem (/a/ports). Last night cvsup nuked that symlink and filled my root filesystem with ports. How do I avoid that? Do I need to add a line `*default prefix=/a' just before `ports-all' in the cvsupfile? --Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 12:36:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost01.reflexnet.net (mailhost01.reflexnet.net [64.6.192.82]) by hub.freebsd.org (Postfix) with ESMTP id BAA7437B400 for ; Sat, 20 Jan 2001 12:35:58 -0800 (PST) Received: from rfx-216-196-73-168.users.reflexcom.com ([216.196.73.168]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Sat, 20 Jan 2001 12:34:10 -0800 Received: (from cjc@localhost) by rfx-216-196-73-168.users.reflexcom.com (8.11.1/8.11.0) id f0KKZx021159; Sat, 20 Jan 2001 12:35:59 -0800 (PST) (envelope-from cjc) Date: Sat, 20 Jan 2001 12:35:58 -0800 From: "Crist J. Clark" To: Ben Jackson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: preventing cvsup from replacing /usr/ports symlink? Message-ID: <20010120123558.I10761@rfx-216-196-73-168.users.reflex> Reply-To: cjclark@alum.mit.edu References: <200101202028.f0KKSUr80758@saturn.home.ben.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200101202028.f0KKSUr80758@saturn.home.ben.com>; from ben@ben.com on Sat, Jan 20, 2001 at 12:28:14PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 20, 2001 at 12:28:14PM -0800, Ben Jackson wrote: > My /usr/ports is a symlink to another filesystem (/a/ports). Last night > cvsup nuked that symlink and filled my root filesystem with ports. How > do I avoid that? > > Do I need to add a line `*default prefix=/a' just before `ports-all' in > the cvsupfile? That should do it. -- 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 Sat Jan 20 12:44:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id EFFDF37B402 for ; Sat, 20 Jan 2001 12:44:30 -0800 (PST) Received: from hyperion.informatik.rwth-aachen.de (hyperion.Informatik.RWTH-Aachen.DE [137.226.112.212]) by nets5.rz.rwth-aachen.de (8.10.1/8.10.1/5) with ESMTP id f0KKiQm03628; Sat, 20 Jan 2001 21:44:26 +0100 (MET) 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 VAA22908; Sat, 20 Jan 2001 21:43:20 +0100 (MET) Received: (from stolz@localhost) by agamemnon.informatik.rwth-aachen.de (8.9.1b+Sun/8.9.1-gb-2) id VAA05036; Sat, 20 Jan 2001 21:44:25 +0100 (MET) Date: Sat, 20 Jan 2001 21:44:25 +0100 From: Volker Stolz To: ben@ben.com, freebsd-stable@FreeBSD.ORG Subject: Re: preventing cvsup from replacing /usr/ports symlink? Message-ID: <20010120214425.A5024@agamemnon.informatik.rwth-aachen.de> References: <200101202028.f0KKSUr80758@saturn.home.ben.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101202028.f0KKSUr80758@saturn.home.ben.com> Organization: Chair for CS II 1/2, Anomalous Programming Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In local.freebsd-stable, you wrote: >My /usr/ports is a symlink to another filesystem (/a/ports). Last night >cvsup nuked that symlink and filled my root filesystem with ports. How >do I avoid that? Are you sure? This usually happens to me on installworld, cvsup works fine. -- \usepackage[latin1]{inputenc}! 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 Sat Jan 20 12:48:52 2001 Delivered-To: freebsd-stable@freebsd.org Received: from westhost15.westhost.net (westhost15.westhost.net [216.71.84.69]) by hub.freebsd.org (Postfix) with ESMTP id F051D37B400 for ; Sat, 20 Jan 2001 12:48:33 -0800 (PST) Received: from beast (h0020af68b314.ne.mediaone.net [24.91.189.27]) by westhost15.westhost.net (8.8.5/8.8.5) with SMTP id OAA22017 for ; Sat, 20 Jan 2001 14:58:06 -0600 From: "Paul A. Howes" To: Subject: New Intel NICs... Date: Sat, 20 Jan 2001 15:48:23 -0500 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All- I know FreeBSD has great support for the Intel EtherExpress Pro 10 and 100B series cards. I was just checking Intel's web site, and they seem to have phased out the 100B in favor of a 100S, which incorporates harware-based encryption, and a "new-and-improved" version of the chip, dubbed the "82550". Are our drivers still compatible with the new card? Also, can our drivers take advantage of the encryption? Thanks! -- Paul A. Howes pahowes@fair-ware.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 13:19: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from firebat.bushong.net (c128625-a.frmt1.sfba.home.com [24.176.225.90]) by hub.freebsd.org (Postfix) with ESMTP id E064537B401 for ; Sat, 20 Jan 2001 13:18:50 -0800 (PST) Received: (from dbushong@localhost) by firebat.bushong.net (8.11.0/8.11.0) id f0KLIjN63588; Sat, 20 Jan 2001 13:18:45 -0800 (PST) (envelope-from dbushong) Date: Sat, 20 Jan 2001 13:18:45 -0800 From: David Bushong To: Volker Stolz Cc: ben@ben.com, freebsd-stable@FreeBSD.ORG Subject: Re: preventing cvsup from replacing /usr/ports symlink? Message-ID: <20010120131845.H16505@bushong.net> References: <200101202028.f0KKSUr80758@saturn.home.ben.com> <20010120214425.A5024@agamemnon.informatik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010120214425.A5024@agamemnon.informatik.rwth-aachen.de>; from stolz@I2.Informatik.RWTH-Aachen.DE on Sat, Jan 20, 2001 at 09:44:25PM +0100 X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This happens to me, too. Drove me insane at first.. thought someone else with root was doing something bad. --David Bushong On Sat, Jan 20, 2001 at 09:44:25PM +0100, Volker Stolz wrote: > In local.freebsd-stable, you wrote: > >My /usr/ports is a symlink to another filesystem (/a/ports). Last night > >cvsup nuked that symlink and filled my root filesystem with ports. How > >do I avoid that? > > Are you sure? This usually happens to me on installworld, cvsup works > fine. > -- > \usepackage[latin1]{inputenc}! > 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 Sat Jan 20 14:41: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from emma1.emma.line.org (p3EE3C727.dip.t-dialin.net [62.227.199.39]) by hub.freebsd.org (Postfix) with ESMTP id 0AF6237B402 for ; Sat, 20 Jan 2001 14:40:37 -0800 (PST) Received: by emma1.emma.line.org (Postfix, from userid 500) id A7F41A2002; Sat, 20 Jan 2001 23:40:24 +0100 (CET) Date: Sat, 20 Jan 2001 23:40:24 +0100 From: Matthias Andree To: Linux NFS mailing list , reiserfs-list@namesys.com, FreeBSD Stable Subject: Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, ReiserFS Message-ID: <20010120234024.A1771@emma1.emma.line.org> Mail-Followup-To: Linux NFS mailing list , reiserfs-list@namesys.com, FreeBSD Stable 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 X-Loop: FreeBSD.ORG I have troubles mounting a reiserfs (3.5.29) file system that is on a Linux 2.2.18 nfsv3 server with a FreeBSD 4.2-STABLE client, I'm getting bogus "read-only file system" errors even on just ls. If I mount the same system via NFS v2, everything goes smooth. If mount an ext2 file system from the same server on the same client, everything goes smooth, regardless if using NFS v3 (default) or v2 (mount_nfs -2). If I use a Solaris 7 or Linux client for mounting, everything goes smooth. I'm not quite sure if it's a Linux or a FreeBSD bug, and if Linux, if it's NFS-specific or reiserfs specific. There seem to be issues with NFS v3 serving reiserfs still. If you need further information (traced syscalls, more elicit network dump), please let me know. Here's a tcpdump 3.5 excerpt, the first two lines still from mount, the other ones from ls /mnt (not showing portmapper and mountd packets, there are unspectacular): 23:22:29.528242 freebsd.526363636 > emma1.nfs: 144 access fh 0,1/2 003f (ttl 64, id 44190) 23:22:29.528764 emma1.nfs > freebsd.526363636: reply ok 116 access ERROR: Read-only file system (ttl 64, id 12889) 23:22:31.516945 freebsd.526363637 > emma1.nfs: 144 access fh 0,1/2 003f (ttl 64, id 44202) 23:22:31.517484 emma1.nfs > freebsd.526363637: reply ok 116 access ERROR: Read-only file system (ttl 64, id 12907) Here's a tcpdump of a successful NFS v2 mount: 23:22:54.615412 freebsd.526363639 > emma1.nfs: 136 getattr fh 0,1/2 (ttl 64, id 44300) 23:22:54.615894 emma1.nfs > freebsd.526363639: reply ok 96 getattr DIR 41777 ids 0/0 sz 706 (ttl 64, id 13070) Here of a successful NFS v3 ext2 mount: 23:29:05.976285 freebsd.526363641 > emma1.nfs: 144 access fh Unknown/1 003f (ttl 64, id 44492) 23:29:05.976823 emma1.nfs > freebsd.526363641: reply ok 120 access attr: DIR 40755 ids 0/0 sz 1024 nlink 13 rdev 0/0 fsid 0 nodeid 0 a/m/ctime 980028529.000000 979555088.000000 979555088.000000 c 0003 (ttl 64, id 13585) -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 15:11:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from flux.ptc.spbu.ru (flux.ptc.spbu.ru [195.19.225.195]) by hub.freebsd.org (Postfix) with ESMTP id A7E6C37B400 for ; Sat, 20 Jan 2001 15:11:24 -0800 (PST) Received: from snark.ptc.spbu.ru (snark.ptc.spbu.ru [195.19.225.131]) by flux.ptc.spbu.ru (8.9.3/8.9.3/cf-1.0.rbl) with ESMTP id CAA07662 for ; Sun, 21 Jan 2001 02:11:18 +0300 (MSK) Received: (from uwe@localhost) by snark.ptc.spbu.ru (8.8.8+Sun/8.8.8) id CAA02304 for freebsd-stable@FreeBSD.ORG; Sun, 21 Jan 2001 02:11:17 +0300 (MSK) Date: Sun, 21 Jan 2001 02:11:17 +0300 From: "Valeriy E. Ushakov" To: freebsd-stable@FreeBSD.ORG Subject: Re: preventing cvsup from replacing /usr/ports symlink? Message-ID: <20010121021117.A2300@snark.ptc.spbu.ru> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <200101202028.f0KKSUr80758@saturn.home.ben.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.3i In-Reply-To: <200101202028.f0KKSUr80758@saturn.home.ben.com>; from "Ben Jackson" on Sat, Jan 20, 2001 at 12:28:14 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 20, 2001 at 12:28:14 -0800, Ben Jackson wrote: > My /usr/ports is a symlink to another filesystem (/a/ports). Last night > cvsup nuked that symlink and filled my root filesystem with ports. How > do I avoid that? Hmm, this happens to me sometimes. I usually cvsup my the ports tree weekly and it happens like, maybe, one cvsup out of five. SY, Uwe -- uwe@ptc.spbu.ru | Zu Grunde kommen http://www.ptc.spbu.ru/~uwe/ | Ist zu Grunde gehen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 15:57:49 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vilnya.demon.co.uk (vilnya.demon.co.uk [158.152.19.238]) by hub.freebsd.org (Postfix) with ESMTP id E666A37B400; Sat, 20 Jan 2001 15:57:27 -0800 (PST) Received: from darkstar (darkstar.rings [10.2.4.16]) by vilnya.demon.co.uk (Postfix) with SMTP id 80552D9B8; Sat, 20 Jan 2001 23:57:24 +0000 (GMT) Message-ID: <003401c0833c$39ac3f40$1004020a@darkstar> From: "Cameron Grant" To: , Subject: newpcm/kobj MFC Date: Sat, 20 Jan 2001 23:53:45 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this is a followup to my proposal some weeks ago which recieved no relevant commentary. unless vetoed for good reason, i intend to MFC kobj support into 4.x and update newpcm to use it in the next few days. this will not affect any other subsystems apart from kernel .m file expansion which will be changed to determine whether its source file is for kobj or device ops and invoke the relevant script. this change will change the newpcm dki again so modules maintained outside the tree will require updating, but will allow many improvements including the latency improvements now present in -current, and the addition of several new drivers, along with future developments. without this change, newpcm in -stable goes into maintenence mode as i have neither time or motivation to to development in two seperate trees. silence will be interpreted as assent. -cg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 16: 7:36 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 0396137B400 for ; Sat, 20 Jan 2001 16:07:19 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0L0ANi54701; Sat, 20 Jan 2001 16:10:23 -0800 (PST) (envelope-from kris) Date: Sat, 20 Jan 2001 16:10:23 -0800 From: Kris Kennaway To: Mike Conlen Cc: Stephan Weaver , stable@FreeBSD.ORG Subject: Re: cvsup Message-ID: <20010120161023.B54574@citusc17.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="yNb1oOkm5a9FJOVX" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from meconlen@obfuscated.net on Fri, Jan 19, 2001 at 09:46:50PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --yNb1oOkm5a9FJOVX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 19, 2001 at 09:46:50PM -0500, Mike Conlen wrote: > On Fri, 19 Jan 2001, Stephan Weaver wrote: >=20 > > Upgrading from 3.3 - 4.2 at build world stage and i get this error: gro= ff:=20 > > illegal option -- U > > Any help please? >=20 > try upgrading from 3.3 to the last stable in 3, then to the 4 line. I've > usually gone from 3.3 to 3 stable, to 4_0_release to whatever in 4 I'm > looking for. And be sure you're upgrading using the correct procedure when going to 4.0-R. See the handbook and /usr/src/UPDATING. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --yNb1oOkm5a9FJOVX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6aijuWry0BWjoQKURAkQ2AKDeze/t0tJ7Q3pRaUIT6ICbhUTyDgCeMFwR yc2IwFVghYQUQ6tqh/VYGS8= =KaS0 -----END PGP SIGNATURE----- --yNb1oOkm5a9FJOVX-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 16: 8:35 2001 Delivered-To: freebsd-stable@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id DADA137B400 for ; Sat, 20 Jan 2001 16:08:17 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0L0BMc54722; Sat, 20 Jan 2001 16:11:22 -0800 (PST) (envelope-from kris) Date: Sat, 20 Jan 2001 16:11:22 -0800 From: Kris Kennaway To: Forrest Aldrich Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Required files for Linux emulation Message-ID: <20010120161122.C54574@citusc17.usc.edu> References: <5.0.0.25.2.20010120140820.02188bd0@216.67.14.69> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="KN5l+BnMqAQyZLvT" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.2.20010120140820.02188bd0@216.67.14.69>; from forrie@forrie.com on Sat, Jan 20, 2001 at 02:09:31PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --KN5l+BnMqAQyZLvT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 20, 2001 at 02:09:31PM -0500, Forrest Aldrich wrote: > I have a third-party program (Interscan Viruswall, anyone using that on= =20 > FreeBSD?) that seems to require an additional amount of info to determine= =20 > the version of Linux supported: >=20 > grep: /etc/redhat-release: No such file or directory >=20 > InterScan 3.0.1 now only support running on Linux 6.0 or above >=20 > How can we address this? mollari# more /compat/linux/etc/redhat-release Red Hat Linux release 6.1 (Cartman) i.e. it's already put there by the linux_base package. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --KN5l+BnMqAQyZLvT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6aikqWry0BWjoQKURAtghAKDYWU0e79GNJVFcGPdi2D7TZ98+gwCg+an9 sR31ZcOHo6TOeCQWDUrPo5A= =JIzy -----END PGP SIGNATURE----- --KN5l+BnMqAQyZLvT-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 16:24: 7 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 270C937B400; Sat, 20 Jan 2001 16:23:48 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f0L0Nkk43785; Sat, 20 Jan 2001 16:23:46 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101210023.f0L0Nkk43785@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Cameron Grant" Cc: arch@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: newpcm/kobj MFC In-Reply-To: <003401c0833c$39ac3f40$1004020a@darkstar> Date: Sat, 20 Jan 2001 16:23:46 -0800 From: Peter Wemm Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Cameron Grant" wrote: > this is a followup to my proposal some weeks ago which recieved no relevant > commentary. > > unless vetoed for good reason, i intend to MFC kobj support into 4.x and > update newpcm to use it in the next few days. Please do. Since it doesn't affect anything else, there is no harm at all in this. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 16:46:27 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 2D14837B400 for ; Sat, 20 Jan 2001 16:45:23 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA26116; Sat, 20 Jan 2001 16:44:53 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id f0L0il715575; Sat, 20 Jan 2001 16:44:48 -0800 (PST) (envelope-from jdp) Date: Sat, 20 Jan 2001 16:44:48 -0800 (PST) Message-Id: <200101210044.f0L0il715575@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Reply-To: stable@freebsd.org Cc: ben@ben.com Subject: Re: preventing cvsup from replacing /usr/ports symlink? In-Reply-To: <200101202028.f0KKSUr80758@saturn.home.ben.com> References: <200101202028.f0KKSUr80758@saturn.home.ben.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200101202028.f0KKSUr80758@saturn.home.ben.com>, Ben Jackson wrote: > My /usr/ports is a symlink to another filesystem (/a/ports). Last night > cvsup nuked that symlink and filled my root filesystem with ports. How > do I avoid that? > > Do I need to add a line `*default prefix=/a' just before `ports-all' in > the cvsupfile? It would be better to change the ports-all line to: ports-all prefix=/a Remember, a "*default" line changes the setting for all of the collections following it in the supfile. 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 Sat Jan 20 16:47:52 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 8E6FE37B400 for ; Sat, 20 Jan 2001 16:47:35 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA26132; Sat, 20 Jan 2001 16:47:11 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id f0L0lBq15592; Sat, 20 Jan 2001 16:47:11 -0800 (PST) (envelope-from jdp) Date: Sat, 20 Jan 2001 16:47:11 -0800 (PST) Message-Id: <200101210047.f0L0lBq15592@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Reply-To: stable@freebsd.org Cc: uwe@ptc.spbu.ru Subject: Re: preventing cvsup from replacing /usr/ports symlink? In-Reply-To: <20010121021117.A2300@snark.ptc.spbu.ru> References: <200101202028.f0KKSUr80758@saturn.home.ben.com> <20010121021117.A2300@snark.ptc.spbu.ru> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20010121021117.A2300@snark.ptc.spbu.ru>, Valeriy E. Ushakov wrote: > On Sat, Jan 20, 2001 at 12:28:14 -0800, Ben Jackson wrote: > > > My /usr/ports is a symlink to another filesystem (/a/ports). Last night > > cvsup nuked that symlink and filled my root filesystem with ports. How > > do I avoid that? > > Hmm, this happens to me sometimes. I usually cvsup my the ports tree > weekly and it happens like, maybe, one cvsup out of five. I have gotten other reports of this in the past, but I have not been able to reproduce the problem myself. If you can figure out when it happens and when it doesn't, please let me know. 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 Sat Jan 20 18:12:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from saturn.home.ben.com (c1058885-a.bvrtn1.or.home.com [24.12.186.106]) by hub.freebsd.org (Postfix) with ESMTP id 32FEF37B400 for ; Sat, 20 Jan 2001 18:12:02 -0800 (PST) Received: (from bjj@localhost) by saturn.home.ben.com (8.11.1/8.9.3) id f0L2C1o82474; Sat, 20 Jan 2001 18:12:01 -0800 (PST) From: Ben Jackson Message-Id: <200101210212.f0L2C1o82474@saturn.home.ben.com> Subject: Re: preventing cvsup from replacing /usr/ports symlink? In-Reply-To: <200101210047.f0L0lBq15592@vashon.polstra.com> from John Polstra at "Jan 20, 2001 04:47:11 pm" To: stable@FreeBSD.ORG Date: Sat, 20 Jan 2001 18:11:54 -0800 (PST) Cc: uwe@ptc.spbu.ru X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <20010121021117.A2300@snark.ptc.spbu.ru>, > > Hmm, this happens to me sometimes. I usually cvsup my the ports tree > > weekly and it happens like, maybe, one cvsup out of five. > > I have gotten other reports of this in the past, but I have not been > able to reproduce the problem myself. If you can figure out when it > happens and when it doesn't, please let me know. It may be trying to delete /usr/ports when it's a directory, too, but FreeBSD's unlink() won't let the superuser delete directories. Be interesting to see what cvsup does on a platform that still does... --Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 19: 1:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c0039.upc-c.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2689937B402 for ; Sat, 20 Jan 2001 19:01:09 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id EAA91099 for ; Sun, 21 Jan 2001 04:01:07 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A6A50F3.307C9E06@nisser.com> Date: Sun, 21 Jan 2001 04:01:07 +0100 From: Roelof Osinga Organization: Nisser - Nr. 1 in Veiligheid X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: MAIL set by whom? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following is what i've got: nl:~$ grep MAIL /etc/* /etc/aliases:# See also RFC 2142, `MAILBOX NAMES FOR COMMON SERVICES, ROLES /etc/aliases:MAILER-DAEMON: postmaster /etc/aliases:# BUSINESS-RELATED MAILBOX NAMES /etc/aliases:# NETWORK OPERATIONS MAILBOX NAMES /etc/aliases:# SUPPORT MAILBOX NAMES FOR SPECIFIC INTERNET SERVICES grep: /etc/isdn: Permission denied /etc/login.conf:# :setenv=MAIL=/var/mail/$,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\ /etc/login.conf: :setenv=MAIL=/home/$/Maildir/,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\ /etc/login.conf:# :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\ /etc/make.conf:NO_SENDMAIL= true grep: /etc/master.passwd: Permission denied /etc/services:ni-mail 61/tcp #NI MAIL /etc/services:ni-mail 61/udp #NI MAIL grep: /etc/skeykeys: Permission denied grep: /etc/spwd.db: Permission denied grep: /etc/uucp: Permission denied nl:~$ grep MAIL * nl:~$ But what I need is /home/{$USER}/Maildir/ in order for Mutt to work with Maildirs. The above /etc/login.conf parts don't do the trick and other occurrences of MAIL I can't find. So what gives? (IOW please help! :) Roelof PS I've read about: nl:~$ cat .mutttrc set mbox_type="Maildir" set mbox="$HOME/Maildir/" set spoolfile="$HOME/Maildir/" but am wondering if that really is all there is? -- Home is where the (@) http://eboa.com/ is. Nisser home -- http://www.Nisser.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 19:25:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hex.databits.net (hex.databits.net [207.29.192.16]) by hub.freebsd.org (Postfix) with SMTP id C1E7937B404 for ; Sat, 20 Jan 2001 19:24:58 -0800 (PST) Received: (qmail 31504 invoked by uid 1001); 21 Jan 2001 03:25:45 -0000 Date: Sat, 20 Jan 2001 22:25:45 -0500 From: Pete Fritchman To: Roelof Osinga Cc: freebsd-stable@freebsd.org Subject: Re: MAIL set by whom? Message-ID: <20010120222545.A31387@databits.net> References: <3A6A50F3.307C9E06@nisser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6A50F3.307C9E06@nisser.com>; from roelof@nisser.com on Sun, Jan 21, 2001 at 04:01:07AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In csh, the default .cshrc (/usr/share/skel/dot.cshrc), it's set: set mail = (/var/mail/$USER) ... could be changed to: set mail = (~/Maildir) ++ 21/01/01 04:01 +0100 - Roelof Osinga: >[...] >:setenv=MAIL=/home/$/Maildir/,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\ Remember, this is overidden in system-wide profiles (/etc/profile and /etc/csh.cshrc) and user dotfiles (~/.[bash_]profile, ~/.cshrc, ~/.bashrc) all depending on the shell the user logs in with. What shell does the user have? >[...] >nl:~$ grep MAIL * >nl:~$ Note that the '*' pattern won't catch dot files. electron [292] % grep -i mail * grep: No match. electron [293] % grep mail .cshrc set mail = (/var/mail/$USER) electron [294] % > >[...] >PS I've read about: > >nl:~$ cat .mutttrc >set mbox_type="Maildir" >set mbox="$HOME/Maildir/" >set spoolfile="$HOME/Maildir/" >[...] Yes, that should work too. See also: http://www.mutt.org/doc/manual/manual-4.html#ss4.6 Regards, -pete >-- >Home is where the (@) http://eboa.com/ is. >Nisser home -- http://www.Nisser.com/ > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message -- Pete Fritchman Databits Network Services, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 20:21:20 2001 Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c0039.upc-c.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id AF59437B401 for ; Sat, 20 Jan 2001 20:20:59 -0800 (PST) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id FAA91363; Sun, 21 Jan 2001 05:20:53 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <3A6A63A5.94C2BC86@nisser.com> Date: Sun, 21 Jan 2001 05:20:53 +0100 From: Roelof Osinga Organization: Nisser - Nr. 1 in Veiligheid X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Pete Fritchman Cc: freebsd-stable@freebsd.org Subject: Re: MAIL set by whom? References: <3A6A50F3.307C9E06@nisser.com> <20010120222545.A31387@databits.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pete Fritchman wrote: > > In csh, the default .cshrc (/usr/share/skel/dot.cshrc), it's set: > set mail = (/var/mail/$USER) > > ... could be changed to: > set mail = (~/Maildir) Thanks. I always seem to forget about that one (the /usr/share/skel dir., that is). > ++ 21/01/01 04:01 +0100 - Roelof Osinga: > >[...] > >:setenv=MAIL=/home/$/Maildir/,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\ > > Remember, this is overidden in system-wide profiles (/etc/profile and > /etc/csh.cshrc) and user dotfiles (~/.[bash_]profile, ~/.cshrc, ~/.bashrc) > all depending on the shell the user logs in with. > > What shell does the user have? Bash in this case. Don't believe it was overridden, yet... > >[...] > >nl:~$ grep MAIL * > >nl:~$ > > Note that the '*' pattern won't catch dot files. You're right, of course. Another thing I keep forgetting. Got a lot of practice with forgetting stuff . > ... > Yes, that should work too. See also: > > http://www.mutt.org/doc/manual/manual-4.html#ss4.6 Doesn't say much. I don't like 'auto-anything'. Just a couple of hours ago I lost my bookmarks in my NT2K WS. All except for the NS toolbar on top, whatever it's called. Tx to installing an USB Epson 680 inkjet using some fancy auto thingum. That were a lot of bookmarks that went to greener pastures! I don't like auto thingums by whatever name . Things like "Mutt does not update these files, yet." make me nervous. Talking about nervous. The ol' 3.4 one says: nisser:~$ mutt -v Mutt 0.95.3i (1999-02-12) Copyright (C) 1996-8 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: FreeBSD 3.4-STABLE [usSystem: FreeBSD 4.2-RELEASE [using ncurses 5.1] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK -USE_FCNTL +USE_FLOCK +USE_IMAP -USE_GSS +USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS +COMPRESSED SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" ISPELL="/usr/local/bin/ispell" To contact the developers, please mail to . To report a bug, please use the muttbug utility. nisser:~$ set | grep MAIL MAIL=/home/roelof/Maildir MAILCHECK=60 MAILDIR=/home/roelof/Maildir The new one says: System: FreeBSD 4.2-RELEASE [using ncurses 5.1] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK -USE_FCNTL +USE_FLOCK +USE_IMAP -USE_GSS +USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS +COMPRESSED SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" ISPELL="/usr/local/bin/ispell" To contact the developers, please mail to . To report a bug, please use the muttbug utility. nl:~$ set | grep MAIL MAIL=/home/roelof/Maildir MAILCHECK=60 MAILDIR=/home/roelof/Maildir So where does that $MAILPATH enter things? Roelof PS talking about bugs. Did you know Chivas Regal has switched to screw caps? Try pulling those off. Sheesh! ;) -- ---------------------------------------------------------------- Het Slakke Huis van de TGV op http://SlakkeHuis.com/ ---------------------------------------------------------------- Home is where the (@) http://eboa.com/ is. Nisser home -- http://www.Nisser.com/ Beveiligingsverwijzingen -- http://Nisser.com/links.htm Overzicht bekende LijnMonitoren - http://www.SlakkeHuis.com/Werkgroepen/LM/monitoren.php3 ---------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 20:40:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hex.databits.net (hex.databits.net [207.29.192.16]) by hub.freebsd.org (Postfix) with SMTP id 3728937B401 for ; Sat, 20 Jan 2001 20:40:01 -0800 (PST) Received: (qmail 32721 invoked by uid 1001); 21 Jan 2001 04:40:48 -0000 Date: Sat, 20 Jan 2001 23:40:48 -0500 From: Pete Fritchman To: Roelof Osinga Cc: freebsd-stable@freebsd.org Subject: Re: MAIL set by whom? Message-ID: <20010120234048.A32228@databits.net> References: <3A6A50F3.307C9E06@nisser.com> <20010120222545.A31387@databits.net> <3A6A63A5.94C2BC86@nisser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A6A63A5.94C2BC86@nisser.com>; from roelof@nisser.com on Sun, Jan 21, 2001 at 05:20:53AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ++ 21/01/01 05:20 +0100 - Roelof Osinga: >[...] >Bash in this case. Don't believe it was overridden, yet... I assume you are executing bash as a login shell so it reads ~/.profile and ~/.bash_profile. If you are, make sure between ~/.profile and ~/.bash_profile you are only setting MAIL once, and to the correct value: export MAIL=~/Maildir If you are su'ing to the user without typing "su - user" to make the resulting shell a login shell, you will have to put that line in ~/.bashrc. >[...] >> http://www.mutt.org/doc/manual/manual-4.html#ss4.6 > >Doesn't say much. I don't like 'auto-anything'. Just a couple of >hours ago I lost my bookmarks in my NT2K WS. All except for the >NS toolbar on top, whatever it's called. Tx to installing an USB >Epson 680 inkjet using some fancy auto thingum. That were a lot >of bookmarks that went to greener pastures! I don't like auto thingums >by whatever name . Eek, that sucks :( I hate losing bookmarks! > >Things like "Mutt does not update these files, yet." make me nervous. > That's just for MH-style mailboxes. >[...] >[mutt -v output] >MAILPATH="/var/mail" >[...] >nl:~$ set | grep MAIL >MAIL=/home/roelof/Maildir >MAILCHECK=60 >MAILDIR=/home/roelof/Maildir > > >So where does that $MAILPATH enter things? [this may not be 100% correct, it's after a 30-second look at src] If you don't define a default spool in your .muttrc, and you don't define HOMESPOOL (like, ~/Mailbox or something), mutt will look in $MAILPATH/$USERNAME by default. > >Roelof Regards, -pete > >PS talking about bugs. Did you know Chivas Regal has switched to >screw caps? Try pulling those off. Sheesh! ;) :) > > >-- >---------------------------------------------------------------- >Het Slakke Huis van de TGV op http://SlakkeHuis.com/ >---------------------------------------------------------------- >Home is where the (@) http://eboa.com/ is. >Nisser home -- http://www.Nisser.com/ >Beveiligingsverwijzingen -- http://Nisser.com/links.htm >Overzicht bekende LijnMonitoren - > http://www.SlakkeHuis.com/Werkgroepen/LM/monitoren.php3 >---------------------------------------------------------------- -- Pete Fritchman Databits Network Services, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 20 21:54: 9 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 E757637B400 for ; Sat, 20 Jan 2001 21:53:49 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id GAA63905; Sun, 21 Jan 2001 06:53:44 +0100 (CET) (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: "Shawn Barnhart" Cc: "Matt Dillon" , Subject: Re: Limit on the number of disklabel entries? References: <33819.980017896@winston.osd.bsdi.com> <200101201930.f0KJUKw08417@earth.backplane.com> <009201c0831a$94db1cf0$b8209fc0@marlowe> From: Dag-Erling Smorgrav Date: 21 Jan 2001 06:53:44 +0100 In-Reply-To: "Shawn Barnhart"'s message of "Sat, 20 Jan 2001 13:52:55 -0600" Message-ID: Lines: 23 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Shawn Barnhart" writes: > Is this ever an issue for anyone with very, very large disks or arrays where > a large number of logical filesystems might be desired? If my math is > right, there's a limit of 24 filesystems per disk, which is really only 20 > if you exclude /, swap, /var, and /usr. No, it's seven times four = 28. Each slice can have eight partitions, one of which (c) is reserved. B doesn't have a special meaning anymore - you can swap and dump to any partition you like, and there's nothing to stop you from putting a filesystem on b. D isn't reserved any more, so you can use it for anything you like. A only has a special meaning insofar as the boot code will default to boot off the a partition on the first FreeBSD slice it finds, but otherwise you can use it for anything you like. If "very, very large disks or arrays" really are a problem, you can use a volume manager (such as vinum, or in a pinch, ccd) to split a partition into many logical volumes, each of which can hold a single partition. 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 Sat Jan 20 23:11:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hal9000.bsdonline.org (ffaxvawx3-4-047.cox.rr.com [24.168.203.47]) by hub.freebsd.org (Postfix) with ESMTP id B082337B400 for ; Sat, 20 Jan 2001 23:10:51 -0800 (PST) Received: by hal9000.bsdonline.org (Postfix, from userid 1001) id 4783C1F53; Sun, 21 Jan 2001 02:10:40 -0500 (EST) Date: Sun, 21 Jan 2001 02:10:40 -0500 From: Andrew J Caines To: FreeBSD Stable Subject: syslogd throwing a hissy fit Message-ID: <20010121021039.A442@hal9000.bsdonline.org> Reply-To: Andrew J Caines Mail-Followup-To: FreeBSD Stable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: H.A.L. Plant X-Powered-by: FreeBSD 4.2-STABLE Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, After the last of a very long line of trouble free updates in the prescribed manner, this last update has left me with a perfectly working system except for a posessed syslogd. The symptoms are that when I start syslogd, either during normal system startup or manually, it rapidly starts issuing reams of malformed kern.crit (and a few other) messages, not stopping until I kill syslogd, which isn't easy since *.crit messages go to all terminals. Here's a small sample. Note that these are not cut-n-paste errors. The messages really do look like this. hal9000 /kernel: Jan 21 01:21:56 halo> hal9000 /kernel: Jan 21 01:22:01 hal9000 /kernel: Jan 21 01:22:00 hal9000 /kernel: Jan 21 01 21 01:22:01 hal9000 /kernel: Jan 21 01:22:00 hal9000 /kernel: Jan 21 01:22:00 hal9000 /kernel: Jan 21 01:21:56 hal9000 /kernkernel: Jan 21 01:21:54sole.info> hal9000 /kernel: Jan 21 01:21:54 hal9000 /kernel: Jan 21 01:21:53 hal9000 /kernel: Jan 21 01:21:53 hal9000 /kernel: Jan 21 01:21:52 hal9000 /kernel: Jan 21 01:21:52 hal9000 /kernel: Jan 21 01:21:51 hal9000 /kernel: Jan 21 01:21:51 hal9000 /k Jan 21 01:22:06 hal9000 /kernel: nfo> hal9000 /kernel: Jan 21 01:21:57 hal9000 /kernel: :21:51 hal9000 /kernel: Jan 21 01:22:06 hal9000 /kernel: :04 hal9000 /kernel: :48 hal9000 /kernel: Jan 21 01:21:48 hal9000 /kernel: Jan 21 0 Sources were cvsup'ed from cvsup11 around midday EST yesterday (Jan 20th). The version of syslogd from /usr/src/usr.sbin/syslogd/syslogd.c is $FreeBSD: src/usr.sbin/syslogd/syslogd.c,v 1.59.2.4 2001/01/09 06:51:37 phk Exp $ CVSweb shows one change to syslogd.c since my last update: Revision 1.59.2.4 / (download) - annotate - [select for diffs], Tue Jan 9 06:51:37 2001 UTC (12 days ago) by phk Branch: RELENG_4 Changes since 1.59.2.3: +3 -1 lines Diff to previous 1.59.2.3 (colored) to branchpoint 1.59 (colored) next main 1.60 (colored) MFC: Add LOG_CONSOLE and make sure it doesn't end up on /dev/console. After mergemaster, I performed the requested MAKEDEV update and ran into a small problem with /dev/null losing go=rw, which I fixed manually. While I'm not sure how it's supposed to be, /dev/log is symlinked to /var/run/log, which does not exist. Is it supposed be be created by syslogd on startup? As another data point, dmesg does this: # dmesg :05 /var/run/log # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 63503 32353 26070 55% / procfs 4 4 0 100% /proc /dev/ad0s1f 508143 429630 37862 92% /usr /dev/ad0s1e 127023 18513 98349 16% /var /dev/ad0s1g 5081581 3609120 1065935 77% /usr/local /dev/da0s1 1990876 532873 1298733 29% /home /dev/da1s1 1984735 244184 1581773 13% /.disk mfs:33 15847 6 14574 0% /tmp mfs:35 959 68 815 8% /var/run For further information, I've put various files - boot massages, kernel config, rc.conf, make.conf, etc. -on my site to give extra information. See . I cvsup'ed a short time ago, but none of the few files which have been updated appeared relevant. -Andrew- -- _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@altavista.net | Jan 21 01:22:06 hal9000 /kernel: 00 /kernel: Jan 21 01:21:56 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message